This driver allows BPQ32 applications to make and receive Pactor calls using the Kantronics KAM range of Controllers.
Normally the code sets TOR mode, which will also accept AMTOR nad GTOR calls, but if you have an old version of the KAM
that doesn't support the TOR command, it can be set to PACTOR mode by adding OLDMODE to the config file.
You can make (but not receive) packet calls on the HF port. Send the command HFPACKET after ATTACH. The port reverts to Pactor mode when you disconnect.
You can also use the VHF port of the KAM for ax.25 with some restrictions:
Only Level 2 calls are possible. It can't be used for NETROM Node<>Node links.
As the callsign can't be changed to that of an uplinking user, outgoing calls can only be made from programs, such as BPQTerminal and BPQMailChat, and not from users who have connected to your node. There are no restrictions on incoming calls
Note that Calls to the VHF port use the normal BPQ connect format - C PORT CALL, You don't have to ATTACH.
Traffic does not appear in the BPQTerminal monitor window, but calls will appear in the MHEARD list.
The driver configuration is specified in the bpq32.cfg file
MYCALL is set to the PORT config PORTCALL if specified, otherwise to NODECALL. Any MYCALL in the config file is ignored.
The VHF code obeys the USERS and MAXUSERS in the config. So if you set MAXUSERS 1/0 the VHF port is disabled. Setting USERS to 0/5, and MAXUSERS to 1/10 will allow up to 10 ax.25 calls on the VHF port, with a maximum of 5 incoming calls.
The driver is defined to BPQ32 as an External port, and needs some driver-specific configuration
The first line of the config defines what BPQ Application incoming calls should connect to. If omitted, calls go to the command handler.
APPL PMS ; Autoconnect to BPQ32 PMS Application
If you are using the Rig Control feature for scanning,
add the RIGCONTROL command next.
If you provide direct access to the WL2K system you can send Frequency info to the WINLINK database by including a
WL2KREPORT line. See here for details.
All commands that are essential to run with BPQ32 are sent automatically. You only need to include any special setup you need, such as setting levels, and ax.25 params, such as TXDELAY if you are using the packet port. Normally the TNC is set to TOR mode, which allows it to accept AMTOR and GTOR calls as well as PACTOR. If you have an older KAM that does not support the TOR command, include the OLDMODE command in the config.
The commands that are preset are in two groups. One set is sent before the commands you specify, so can be changed. The others are sent after your commands, as they are essential for correct operation with BPQ32.
Sent before your config: MARK 1400 SPACE 1600 SHIFT MODEM INV ON MAXUSERS 1/10 PTERRS 30 Sent after your config: ECHO OFF XMITECHO ON TXFLOW OFF XFLOW OFF TRFLOW OFF AUTOCR 0 AUTOLF OFF CRADD OFF CRSUP OFF CRSUP OFF/OFF LFADD OFF/OFF LFADD OFF LFSUP OFF/OFF LFSUP OFF RING OFF ARQBBS OFF MYCALL
Sample KAM Pactor Configuration
PORT ID=Pactor Link TYPE=EXTERNAL IOADDR=1; COM Port Address (Note this is in hex, so for COM20 enter 14 SPEED=19200; COM Port Speed DLLNAME=KAMPactor.DLL INTERLOCK=n; ; Optional - set if you have two ports sharing the same radio. ; Set the same Interlock value on both ports. CONFIG ; Driver-Specific Configuration APPL RMS ; Autoconnect to BPQ32 RMS Application RIGCONTROL COM2 19200 ICOM IC700 70 4 14.103/U1W 14.112/U1 18.1/U1N 10.12/L1
OLDMODE ; Optional - Causes controller to be set to PACTOR mode instead of TOR mode XMITLVL 50/35; ENDPORT
John Wiseman GM8BPQ/G8BPQ
Updated 20th October 2010