OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
K7IQI  > BPQ      01.11.95 02:03l 50 Lines 2716 Bytes #-11329 (0) @ WW
BID : KB7KBT2536
Read: DF5CH DH9MEC DG0EL GUEST
Subj: Data Eng & Multiple KPC-9612's
Path: DB0AAB<DB0KCP<DB0MWS<DB0RBS<DB0HOM<DB0GE<DB0ZDF<DB0SRS<DB0SIF<DB0EAM<
      DB0HBS<DB0OQ<OZ5BBS<OZ4PAC<OZ2BOS<OZ1PPN<N0RSE<KT0H<N0QCU<WB0TAX<
      VE4KV<VE7ROB<VE7DIE<KB7WE<KB7CNN<N7QDN<KA7AGH<KB7KBT
Sent: 951026/0837 @:KB7KBT.OR.USA.NOAM #:2536

    The Data Engine's ability to run an external TNC in addition to 
the two internal TNCs, makes a multiple port hilltop BPQ nodestack 
rather easy to configure.....without all the messy diode matrix 
problems associated with some other methods.  You can also add 
multiple TNC's to the Data Engine using the BPQ "Polled Kiss" 
configuration.  This has been done for some time.

    With the release of the KPC-9612's (and their dual port 1200/9600
design) I wanted to pair one or more of them up with a Data Engine 
for a remote hilltop BPQ Nodestack.  This proved to be a bit more 
difficult than imagined.  In fact, I found that a number of people 
had tried to get this combination to work, and had been unable to do 
it.  It took a lot of hair-pulling before the solution was found.  
Like most solutions, this one was rather easy AFTER being found!

    The configuration in the KANTNODE.DOC file of the BPQ package 
for the Data Engine is a bit misleading when it comes to this 
particular combination.  The docs show a 3-wire cable from the Data 
Engine to the TNC(s), as is typical in a Computer to TNC 
configuration for the BPQ Polled KISS arrangement, utilizing the 
normal Rx data, Tx data, and ground lines.  This apparently also 
does a fine job with the TNC2 clones in the past.  

     However, in matching the KPC-9612 and the Data Engine, this 
combination also "expects" RTS/CTS handshaking, even though it is 
really unnecessary with the BPQ Polled Kiss.  Simply running the 
3-wire cable will lead only to frustration and hair-pulling...as I 
can attest!  The best and simplest solution is to simply place a 
jumper from the RTS pin to the CTS pin on each individual unit.  
This will satisfy the hardware's "expectation" of handshaking.

    A second area of possible confusion is the wiring diagram itself
in the KANTNODE.DOCS.  This shows Data Engine pin numbers for Ground,
TXD, and RXD that are typical of what one would expect to find on a 
DB-25 serial connector.  At the time that document was written, the 
Data Engines apparently came provided with a serial cable that ended 
in a DB-25 connector.  However, the one I recently acquired came with
a serial cable with only an 8-pin modular connector (RJ-45) on one 
end to plug into the "serial" output on the Data Engine, and no 
connector on the other end.  The pin assignments on this connector 
are actually Ground 4, RXD 5, and TXD 6.  Be sure to consult the 
manuals for your hardware before blindly expecting any "standard" 
pin arrangement.
     
    With these two problem areas in mind, your marriage of a Data 
Engine and multiple KPC-9612's should be a "joyous experience".

    73....Ken   K7IQI@K7IQI.#NWOR.OR.USA.NOAM


Read previous mail | Read next mail


 07.11.2026 08:16:23lGo back Go up