On behalf of Mike Melnik N9PMO I have posted to the files section of this group a directory WinFBB 7.01 Setup which contains a setup guide written by Mike onMessage 1 of 45 , Nov 14, 2006View SourceOn behalf of Mike Melnik N9PMO I have posted to the files section of
this group a directory "WinFBB 7.01 Setup" which contains a setup
guide written by Mike on the use of BPQ32 with WinFBB 7.01.
With PROTOCOL=KISS, the FULLDUP parameter is passed to the TNC, and all the KISS implementations I know of will obey the param (ie not transmit if carrier isMessage 45 of 45 , Apr 7, 2008View SourceWith PROTOCOL=KISS, the FULLDUP parameter is passed to the TNC, and all the KISS implementations I know of will obey the param (ie not transmit if carrier is present and FULLDUP=0). Also all that I know will operate true full duplex (simultaneous transmit and receive) if the frequencies are far enough apart (probably crossband, but with good enough cavity filters could be in same band), No handshaking signals are used, so a 3 wire cable is fine.With PROTCOL=NETROM, FULLDUP controls the link between the PC and TNC(s). With BPQ32 it has to be set to 1, and only supports 1 TNC, but with the old DOS BPQCODE you could set FULLDUP=0, and connect a stack of NET/ROM TNC's via a diode matrix. In this case the RTS and CTS lines control the matrix.73,John G8BPQ-----Original Message-----
From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com]On Behalf Of Ron Stordahl
Sent: 07 April 2008 15:29
Subject: Re: [BPQ32] Full DCD signal but will still transmitI am quite interested in this issue. I have always used the JKISS or BPQKISS ROM, with minimal wiring (RX,TX and GND) and FULLDUP=0, and have never noticed the TNC (MFJ1270C's) stomp on a signal being received (with the DCD led illuminated) .
This does bring up the possibility that if the RX and TX frequencies are far removed, it may be possible to operate full duplex. I had thought the hardware prevented this, but perhaps not?
With PROTOCOL=NETROM is is necessary that FULLDUP=1 for the interface to function. Might it then transmit with DCD on and thus stomp on the received packet?
While I have always used the minimal cabling, might full cabling be required in some cases?
http://groups. yahoo.com/ group/BPQ32/ files/BPQ32_ RS232_Cabling/
----- Original Message ----
From: John Wiseman <john.wiseman@ ntlworld. com>
To: BPQ32@yahoogroups. com
Sent: Monday, April 7, 2008 2:56:06 AM
Subject: RE: [BPQ32] Full DCD signal but will still transmit
Dave,Setting FULLDUP=0 in the port definition should stop it, although this relies on the TNC obeying the relevant KISS command.73,John-----Original Message-----
From: BPQ32@yahoogroups. com [mailto:BPQ32@ yahoogroups. com]On Behalf Of David Calder
Sent: 06 April 2008 18:19
To: BPQ32@yahoogroups. com
Subject: [BPQ32] Full DCD signal but will still transmitMy BPQ ports will transmit on top of someone even if the TNC shows it havinga full good DCD. IT will just tromp on them anyway.In the old BPQ (which is on my dead machine) I seem to remember a portcommand to stop that. What was it?Thanks,73 Daven4zkf