Some time ago I posted a mail here that described how one can successfully use
CT version 9.xx and the inexpensive BAYCOM packet modem. So far I've received
a few responses, all saying it wasn't working for them... I would like to know
if there's somebody how was successfull and getting CT to do packet with the
BAYCOM modem according to the procedures in my earlier mail.
If you haven't read that mail and would like to know how I get CT to operate
packet with a BAYCOM modem, here are the things I did:
December 1997
This message is intended for those who have a BAYCOM packet modem and
want to use it in combination with CT version 9. CT normally assumes
a TNC or DRSI card for packet, no support for a simple packet modem.
But with a 'trick' it can be done!
The trick is to use some drivers that come with the PC/FlexNet
package. PC/FlexNet is node software developed fully in Germany and
meant for FlexNet digipeaters that don't use a RMNC controller. The
PC/FlexNet package is freely available for download at:
http://dl0td.afthd.th-darmstadt.de/~flexnet/
You will need the following .lzh archives:
- pcf.lzh
- ser12.lzh
- tfemu.lzh
Unpack these files (e.g. with lha.exe) in a directory. Start the
necessary drivers in the correct order. See the batch file that I use
(read the docs of each driver for more info):
@ECHO OFF
CD \
CD PACKET\PCFLEX
REM Load High the FlexNet kernel
LH FLEXNET
REM Load High the ax25 packet driver for the baycom modem which
REM is connected to com port 2
LH SER12 2
REM Load the previous drivers into memory
FLEX
REM Set some packet parameters; port 0 at 1200 baud with software
REM carrier detect (you can leave the squelch on the TRX open);
REM TXDELAY on port 0; DIGI call (the call that is used in the
REM ax25 frames, i.e. your call)
FSET MODE 0 1200C
FSET TXDELAY 0 40
FSET DIGI 0 PA3EZL
REM Start the driver that will simulate a DRSI card at hex address
REM 0xff
TFEMU -DR -I=0xff
REM Start CT
CD\
CD CONTEST\CT9-27
CT wwcw97 -VGA
Tell CT that a DRSI card is used for packet. That's basically it.
When hitting ALT-T keys you'll get into the talk window. The packet
user interface looks like WA8DED mode. All 'TNC' commands start with
hitting the ESCAPE key. The commands that you must enter before
attempting to connect are (each command is executed by hitting the
ENTER key):
ESC-i<call sign> between <> is your packet call sign,
no space between 'i' and <call sign>
ESC-s1 switch to channel 1; channel 0 (de-
fault) doesn't allow connects
ESC-c <node/cluster call> connect to your local node or cluster
Actually you could have MORE than one connect session. Suppose on
channel 1 you're connected to pi5ehv-8 cluster but want to connect to
another cluster as well, here is how you can do that:
ESC-s2 switch to channel 2
ESC-i<call sign-1> set the call sign on channel 2 with
SSID 1, e.g. pa3ezl-1
ESC-c <node> connect to the local node; from here
you can go to the other cluster
ESC-s# where # is the channel number switches between channels.
To disconnect a channel switch to that channel and type:
ESC-d followed by ENTER
The above procedure has been tested on a 486DX50, 8MB RAM with DOS
6.22, CT9.27 and baycom modem connected to COM port 2.
Hope you'll enjoy the combination of CT and a connection to a packet
DX-Cluster!
73 de Aurelio PA3EZL/AA2WH
e-mail address aurelio@esrac.ele.tue.nl
ax25 address pa3ezl@on5vl.#lg.bel.eu
--
Submissions: ct-user@contesting.com
Administrative requests: ct-user-REQUEST@contesting.com
WWW: http://www.contesting.com/ct/
Questions: owner-ct-user@contesting.com
|