bpqkiss eproms

[CB2SNK]

BPQKISS, JKISS, KISS & 220KISS

Several PROM images are supplied for use with TNC2 (or clones such as the
MFJ1270’s), and one for use with the TNC220:
KISS is as released with the TCPIP package. I have used this code, and it seems
to work, but it does have loopholes in its buffer management. As I have
experienced buffering problems with other KISS mode TNCs with BPQ, I've done a
version, named JKISS, which will reset if it runs out. This is a bit drastic,
but should keep the system going. (Higher level software will retry the
discarded messages). If it improves things, I'll refine it to discard the
oldest. The new eprom image is in the file JKISS and is recommended instead of
KISS.

220KISS is a version of JKISS, modified to run on the TNC220. This version only
supports the VHF port (port 2) at 1200 baud, and the async link to the PC is
fixed at 2400. The DCD led is driven by software, but is controlled by the DCD
signal from the modem (i.e. DCD processing is the same as with the TNC2 - the
SOFTDCD mode of the 220 is not implemented). Other versions are possible if
there is sufficient interest - the main problem is that the KISS command set
would have to be extended to include commands for port and speed switching. Note
the software is now set up to run with the clock speed jumper in the 'Low' speed
position - several people have had problems running in the 'Fast' mode.
The rarely used KISS and 220KISS binary images are in BPQ409D.zip in the
unlikely event that you should need them!

BPQKISS - A Multi-dropped KISS system. (TNC2 and clones only)
I have implemented a system to allow more than one KISS-like TNC to connect to a
single async port. This is primarily for those running machines with little
expansion capability, but can also enable the TNCs and transceivers to be
located remotely from the PC with a simple 3 wire link. A simple checksum is
also added to each packet, to reduce the risk of corruption if running on long
lines (or even over a modem link).
The system uses polling to prevent contention on the link. Each TNC must run the
BPQKISS program, and each must have a different 'address' byte patched in at
location 20hex. In the PORTS section of BPQCFG.TXT, PROTOCOL must be set to
KISS, KISSOPTIONS to POLLED,CHECKSUM,ACKMODE and CHANNEL set to correspond to
the address in the PROM -
CHANNEL Address (in byte 20h of PROM)
A 00h
B 10h
C 20h
D 30h etc
In theory you can have up to 16, but in practice the maximum will depend on the
power of the PC and the speed of the radio ports.

Example Wiring:
PC(25pin) PC(9pin) TNC 1 TNC 2
GROUND 7---------5-------------7-----7----- etc
TXD 2---------3-------------2-----2----- etc
RXD 3---------2------------------------- etc
| |
_ _
^ ^
| |
3 3
_
^ is a diode (1N914 or similar).
With some TNCs and serial cards, a pull-down resistor may be required from pin 3
on the PC (10k to -12v is suggested). Thanks to G3ZFJ for this information.
The protocol used for this multi-dropped option was changed from version 3.59a
onwards to be compatible with similar software produced by KANTRONICS for their
range of TNCs. The new version is called BPQKISS, and replaces the old JKISSP.
For those of you unfamiliar with KISS TNCs, the STA led indicates frames being
received from the PC and the CON led frames being sent to the PC. On power-up,
some LEDS should flash about 3 times - which depends on the version and the RAM
size in the TNC.

CWID
I have added optional CWID to my JKISS and BPQKISS EPROMs. The Call-sign to be
sent is patched into the EPROM image with the program PATCHID, which takes two
parameters, the required call-sign, and the file to patch (either JKISS or
BPQKISS). Note that the specified file is overwritten, so I suggest you make a
copy of the original first.
PATCHID G8BPQ JKISS - Note call must be in upper case
If the image is not patched with your call, no CWID will be sent. CWID is no
longer required with well known modes such as AX.25 packet in many countries,
including the U.S. It may be required in your country.
The CW pattern which will be sent is displayed on the screen – please check it,
just in case my translate table is wrong!
The ID is sent after one minute, then at 29 minute intervals, with a dot length
of 60ms. If my calculations are correct, this equates to 20 WPM
The ID is send in AFSK (assuming a normal AFSK modem), but because of the
hardware design it is not possible to control which tone corresponds to mark or
space - it depends on what was sent just before the ID starts. If you are using
a modem with a scrambler (eg G3RUH), then the system won’t work - the two tones
will sound the same. I'd like to know if a CWID facility for RUH modems would be
useful - if there is a significant demand I'll see if I can find a solution. A
simple on-off keying may be possible, but would depend on the PTT
characteristics of the TX. If you have a better idea, please let me know!

The normal SLOTTIME/PERSISTENCE code is used to minimize collisions with other
stations (hence the interval of 29 minutes, allowing a bit of time for
congestion, without going over the statutory 30 minutes interval).
John Wiseman, G8BPQ
7 March 1991
Using KISS, JKISS, BPQKISS and XKISS with BPQ
When using a KISS or JKISS TNC the following line is used in the ports
definition:
PROTOCOL=KISS
CHANNEL=A

BPQKISS and XKISS (Kantronics implementation of BPQKISS) introduces a checksum
(to deal with errors on the RS232 interface which can be an issue with very long
lines) and polling (optional for a single TNC but needed for multiple TNC’s on a
single com port) and addressing.
The un-patched BPQKISS ROM is set for CHANNEL=A with polling active. This
corresponds to XKISS with XKPOLLED=ON and XKCHKSUM=ON. In the KPC3+ the channel
is fixed at A. When using such a device the configuration lines below are
required
PROTOCOL=KISS
KISSOPTIONS=POLLING,CHECKSUM,ACKMODE
CHANNEL=A
The un-patched BPQKISS ROM works well in a TNC2, but polling introduces unneeded
overhead with the TNC being polled at 10 times per second. In a modern machine
this overhead, while unneeded, is very small, a small fraction of one percent.
However the BPQKISS ROM can be patched to eliminate the need for polling, which
is appropriate for a single TNC on a com port. The needed patch consists of
changing the byte at offset 0221h from 01h (polling) to 00h (no polling). This
corresponds to XKISS with XKPOLLED=OFF.
PROTOCOL=KISS
KISSOPTIONS=CHECKSUM,ACKMODE
CHANNEL=A
Earlier in this document using multiple TNC’s with BPQKISS on a single com port
was described. For such a configuration polling is required and each BPQKISS
ROM must be patched for an appropriate address.
Patching JKISS
When used with BPQ32, the user may specify PERSIST, SLOTTTIME, TXDELAY and
TXTAIL in BPQ32’s configuration file bpqcfg.txt. However I do not know what
other applications which use the KISS mode may do, thus, if needed for a non-
BPQ32 use, you could patch these values at their locations as shown below:

0 1 2 3 4 5 6 7 8 9 A B C D E F
000340 FF 28 14 21 87 04 22 0A 80 21 70 17 22 12 80 3E
000350 01 32 03 80 32 3E 80 3E 32 32 14 80 3E 40 32 15
000360 80 3E 0A 32 16 80 3E 03 32 17 80 D9 E5 D9 D1 06
Addresses Parameter Current Value Current Value Parameter
Name (Hex) (Decimal) Value
----------------------------------------------------------------
000358 TXD 32 50 500 ms
00035D PERSISTENCE 40 64 64 ms
000362 SLOTTIME 0A 10 100 ms
000367 TXTAIL 03 03 30 ms
With BPQ32 these values are replaced by those programmed in the BPQ32
configuration within 30 seconds after BPQ32 starts, and thereafter every 5
minutes, to deal with the cases where the TNC may have been reset manually or
due to power fail/restore. As such there is no need to patch these locations
when used with BPQ32.
Pre-patched BPQKISS Images
While patching the ROM images is easy using a program such as the HxD Hex
Editor, available for free on the Internet, I have provided these pre-patched
BPQKISS images for your convenience:
Name Patched Channel Polling
BPQKISS No A Yes
BPQKISS1 Yes B Yes
BPQKISS2 Yes A No
Note that these are binary images. Some prom burners may expect an extension of
.bin to distinguish these from .hex and other formats. If needed, rename them.
Ron Stordahl, AE5E (ex-N5IN)
25 December 2010

[CB2SNK]

de originele file is in pdf beschikbaar evt.