Loading ...
Sorry, an error occurred while loading the content.

1099RE: [BPQ32] Re: BPQ & the PK-900

Expand Messages
  • David Calder n4zkf
    Jul 13, 2008
      John emailed me. I think we have it covered. But thanks for the return email.
       
      My 1278 Worked OK also but I'm just an old DRSI man. I like the things
      and have the external HF modem that plugs into port two.
       
      The PK900 works fine but it seems like the TX frequency on the HF modem
      is off a little bit.
      I have tweaked and tweaked and I'm over it.
       
      Dave
       


      From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Ron Stordahl N5IN
      Sent: Sunday, July 13, 2008 9:35 AM
      To: BPQ32@yahoogroups.com
      Subject: [BPQ32] Re: BPQ & the PK-900

      In posting #1049 John suggested there might be a possibility DRSI
      cards might work with Win98, however nobody appears to have reported
      trying.

      Another possibility would be to use a MFJ1270C with John's JKISS code.
      The 1270C has a switch on the rear to switch between a radio rate of
      1200 and 300 baud. This is almost certain to work.

      The trick will be finding a 1270C...they have become rare...with luck
      you could find one on eBay.

      Long ago I had a PK900 and recall they were buggy.

      Ron, N5IN

      --- In BPQ32@yahoogroups. com, "David Calder n4zkf" <n4zkf@...> wrote:
      >
      > Yesterday I gave up on the PK 900. I don't know what it is but have
      not had
      > a
      > long forwarding session on 14.098 since I put it online. I ordered a
      dual
      > core
      > motherboard with ISA slots and I'm going back to DRSI.
      >
      > I never did like anything else better. I'm dumping this version of
      FBB also.
      > Too many bugs. It copies people into the users multiple times, ect.
      After
      > 20 years of running this thing I thought about dumping it but Jerry has
      > talked
      > me out of it. The BPQ works great. 4.10.4 Did I not see in the messages
      > a interface file from John or someone to make this version work with
      DRSI's?
      >
      > Thanks 73 Dave
      > n4zkf
      > www.n4zkf.com
      >
      >
      >
      >
      >
      >
      > _____
      >
      > From: BPQ32@yahoogroups. com [mailto:BPQ32@yahoogroups. com] On Behalf
      Of Ron
      > Stordahl
      > Sent: Sunday, March 23, 2008 5:37 PM
      > To: BPQ32@yahoogroups. com
      > Subject: Re: [BPQ32] BPQ & the PK-900
      >
      >
      >
      >
      >
      > With respect to the PK900, it has to be something in it's firmware
      that is
      > switching, or not saving the radio baud rate. BPQ32 would have
      nothing to
      > do with that. All BPQ32 can do in this regard is set the baud rate
      of the
      > computers serial port, which it is obviously doing correctly.
      >
      > Now on to your second paragraph... you say that "AR nodes want to be the
      > 'main' application" . I think what you are referring to is the
      AR-Cluster
      > application needs to be the first positional parameter in the
      APPLICATIONS
      > parameter string? This is true if you are using the BPQ-OCX interface.
      > AR-Cluster sets this as 0x1 and you cannot do anything about it.
      That could
      > be satisfactory if your additional applications can be set for other
      than
      > the first position. If your only other application is FBB, it can
      be set as
      > position two (0x2).
      >
      > As an alternative you could use the AGWtoBPQ interface to AR-Cluster, in
      > which case you can set the applications mask as you wish, and thus
      > AR-Cluster will not be tied down to the first position.
      >
      > This is described in detail in my Installation Document which is
      part of the
      > current BPQ32 installer release.
      >
      > Ron, N5IN
      >
      >
      > ----- Original Message ----
      > From: David Calder <n4zkf@...>
      > To: BPQ32@yahoogroups. com
      > Sent: Sunday, March 23, 2008 1:03:28 PM
      > Subject: RE: [BPQ32] BPQ & the PK-900
      >
      >
      >
      >
      >
      > Got that. That's why it does communicate with both TNC ports. It's
      when I
      > set it to KISS (expanded) so I can use both ports it sticks port 1 back
      > to 1200 and won't leave it 300. I thought someone might have run
      across this
      > before. I'd like to use just the one TNC instead of tying up two.
      >
      > But, everything else is working good. Thanks for the help everyone.
      I also
      > have BPQ and FBB working on the same computer as my DX Cluster nodes.
      > I'd like to be able to access the nodes thru BPQ but AR node wants
      to be the
      > "main" application.
      >
      >
      >
      >
      > 73 Dave
      > n4zkf
      >
      >
      >
      > _____
      >
      > From: BPQ32@yahoogroups. com [mailto:BPQ32@ yahoogroups. com] On
      Behalf Of
      > Mike Melnik
      > Sent: Sunday, March 23, 2008 10:27 AM
      > To: BPQ32@yahoogroups. com
      > Subject: RE: [BPQ32] BPQ & the PK-900
      >
      >
      >
      >
      >
      > Dave
      >
      >
      >
      > The BAUD setting in BPQCFG.TXT is the communication speed between
      the com
      > port and TNC NOT the Radio speed
      >
      > That should remain at 9600BAUD I am not familiar with the AEA TNC?S but
      > there is another setting for the Radio Speed.
      >
      >
      >
      > Mike Melnik
      >
      > N9PMO
      >
      > -----Original Message-----
      > From: BPQ32@yahoogroups. com [mailto:BPQ32@ yahoogroups. com] On
      Behalf Of
      > David Calder
      > Sent: Sunday, March 23, 2008 8:55 AM
      > To: BPQ32@yahoogroups. com
      > Subject: [BPQ32] BPQ & the PK-900
      >
      >
      >
      > Good morning.
      >
      >
      >
      > I'm trying to get BOTH ports to work with BPQ. I have one port
      (radio port2)
      > on
      >
      > the PK-900 which is the default port on the TNC working fine on VHF
      (1200
      > baud)
      >
      >
      >
      > I want to add port one as 300Baud for my HF port and stop using my
      1278B. I
      >
      > take the PK-900 out of kiss mode, make sure that radio port one is
      using the
      >
      > 300 baud modem, radio port2 is running the 1200 baud modem. Put it in
      > extended
      >
      > kiss mode. Set up the bpqcfg.txt file, start it all up and all is
      well but
      > the 300 baud
      >
      > port is running 1200 baud! BPQ controls both ports as it should but
      the 300,
      > isn't
      >
      > 300.
      >
      >
      >
      > I did the command modem 10/4 which is the command for 300/1200. But it's
      > like
      >
      > when I put it in KISS is reverts back to 11/4 which is 1200/1200 modems.
      >
      >
      >
      > Anyone ever have a PK-900 and played with it?
      >
      >
      >
      > 73 Dave n4zkf
      >
      >
      >
      >
      >
      >
      > _____
      >
      >
      > From: BPQ32@yahoogroups. com [mailto:BPQ32@ yahoogroups. com] On
      Behalf Of
      > John Wiseman
      > Sent: Wednesday, January 02, 2008 3:06 PM
      > To: BPQ32@yahoogroups. com
      > Subject: RE: [BPQ32] AR Cluster, WInFBB,and BPQ Questions
      >
      > Hi Ron,
      >
      >
      >
      > Perhaps I wasn't very clear - only the BPQ32 interface has this
      restriction,
      > not the AGWPE interface in AR-Cluster.
      >
      >
      >
      > I don't think having to run ARCluster as the first application is
      much of a
      > problem, especially as BPQ32 now allows other applications to have
      NETROM
      > Calls and Aliases. I'm not aware of any other applications which
      have to be
      > APPL 1.
      >
      >
      >
      > 73,
      >
      > John
      >
      >
      >
      > -----Original Message-----
      > From: BPQ32@yahoogroups. com [mailto:BPQ32@ yahoogroups. com]On
      Behalf Of
      > Ron Stordahl
      > Sent: 02 January 2008 16:25
      > To: BPQ32@yahoogroups. com
      > Subject: Re: [BPQ32] AR Cluster, WInFBB,and BPQ Questions
      >
      > John, G8BPQ
      >
      > I think you meant that the BPQ-OCX interface in AR-Cluster requires
      that it
      > be the first application in APPLICATIONS= . I am successfully
      running both
      > CC-Cluster (as the first application) and AR-Cluster (as the 4th
      > application) , with both using AGWtoBPQ (and thus with an
      applications mask
      > of 0x9). Momentarily I will try the same using the BPQ-OCX interface in
      > AR-Cluster (with it still as the 4th application) . Perhaps that
      will not
      > work...I never considered this possibility. If it does not work
      certainly
      > this can be fixed, but probably would require a change in AR-Cluster
      code?
      >
      > Ron, N5IN
      >
      > ----- Original Message ----
      > From: John Wiseman <john.wiseman@ ntlworld. com>
      > To: BPQ32@yahoogroups. com
      > Sent: Wednesday, January 2, 2008 5:47:34 AM
      > Subject: RE: [BPQ32] AR Cluster, WInFBB,and BPQ Questions
      >
      > Mike,
      >
      >
      >
      > The BPQ32 interface in AR Cluster only allows it to be the first
      appliation,
      > so you need to swap round the DX ands BBS params in APPLICATIONS= .
      When you
      > add FBB, you need to tell it to use Application 2, You should
      probably also
      > change the BBSCALL to mach the ARCluster callsign.
      >
      >
      >
      > 73,
      >
      > John G8BPQ
      >
      >
      >
      >
      >
      >
      >
      > -----Original Message-----
      > From: BPQ32@yahoogroups. com [mailto:BPQ32@ yahoogroups. com]On
      Behalf Of
      > Michael J.Talkington
      > Sent: 02 January 2008 01:50
      > To: BPQ32@yahoogroups. com
      > Subject: [BPQ32] AR Cluster, WInFBB,and BPQ Questions
      >
      > I am running AR Cluster and BPQ node.I want to run WIN FBB also using
      > the bpq.I run ar cluster and bpq starts now when I connect to the
      > node then type dx it says all ports in use but if I type bbs it
      > connects to the cluster.I want to fix this before adding FBB to the
      > computer.also ar cluster is registered in the call KC8FWD-7 here is
      > my bpq config I am using a KPC 3 plus just bought thanks Mike KC8FWD
      >
      > ; CONFIGURATION FILE FOR BPQ32: G8BPQ SWITCH SOFTWARE
      >
      > ; Contains only a LOOPBACK port. Useful to verify that the minimal
      > system is
      > ; functional.
      >
      > ; To perform the basic test, compile this configuration file by
      > executing
      > ; bpqcfg.exe, which will generate bpqcfg.bin. Now execute
      > BPQTerminal. exe,
      > ; and in the lowest window enter:
      >
      > ; C 1 XXNODE v XX0XX
      >
      > ; You should receive the following response:
      >
      > ; XXNODE:XX0XX} Connected to XXNODE
      > ; This is the CTEXT.
      > ; XXNODE:XX0XX} DX CONNECT BYE INFO NODES ROUTES PORTS USERS MHEARD
      >
      > ; \Examples\Minimal
      >
      > HOSTINTERRUPT= 127 ; Interrupt used for BPQ host mode support
      > EMS=0 ; Doesn't use EMS RAM
      > DESQVIEW=0 ; DesqView unused
      > NODECALL=KC8FWD- 10 ; Node callsign
      > NODEALIAS=Clark ; Node alias (6 characters max)
      > BBSCALL=KC8FWD- 3 ; BBS callsign APPL1CALL if used overrides
      > BBSCALL
      > BBSALIAS=FWDBBS ; BBS alias APPL1ALIAS if used overrides
      > BBSALIAS
      > IDMSG: ; UI broadcast text from NODECALL to fixed
      > dest ID
      > Network NODE (Clark:KC8FWD- 7)
      > *** ; Denotes end of IDMSG text
      > BTEXT: ; UI broadcast text from BCALL to destination
      > UNPROTO=
      > This is the BTEXT text.
      > *** ; Denotes end of BTEXT text
      > INFOMSG: ; The INFO command text follows:
      > North Central West Virginia Packet Switch, Clarksburg, WV.
      > Supporting the FWDBBS (KC8FWD BBS), and the FWDDX (FWDDX KC8FWD DX
      > Cluster).
      > The Commands are basically the same as NET/ROM, but to connect to
      > another
      > normal station (not another Node), you must specify a port number
      > before
      > the Callsign. Use PORTS command to list available ports. The BBS
      > command
      > connects you to the associated mailbox,and DX command to the DX
      > Cluster.
      > *** ; Denotes end of INFOMSG text
      > CTEXT: ; The CTEXT text follows:
      > Welcome to the North Central West Virginia Packet Switch in
      > Clarksburg,WV
      > Type ? for a list of commands.
      > *** ; Denotes end of CTEXT text
      > FULL_CTEXT=0 ; 0=send CTEXT to L2 connects to NODEALIAS
      > only
      > ; 1=send CTEXT to all connectees
      >
      > ; Network System Parameters:
      >
      > OBSINIT=5 ; Initial obsolescence set when a node is
      > included
      > ; in a received nodes broadcast. This value
      > is then
      > ; decremented by 1 every NODESINTERVAL.
      > OBSMIN=4 ; When the obsolescence of a node falls below
      > this
      > ; value that node's information is not
      > included in
      > ; a subsequent nodes broadcast.
      > NODESINTERVAL= 60 ; Nodes broadcast interval in minutes
      > IDINTERVAL=10 ; 'IDMSG' UI broadcast interval in minutes,
      > 0=OFF
      > BTINTERVAL=0 ; The BTEXT broadcast interval in minutes,
      > 0=OFF
      > L3TIMETOLIVE= 25 ; Max L3 hops
      > L4RETRIES=3 ; Level 4 retry count
      > L4TIMEOUT=120 ; Level 4 timeout in seconds s/b > FRACK x
      > RETRIES
      > L4DELAY=10 ; Level 4 delayed ack timer in seconds
      > L4WINDOW=4 ; Level 4 window size
      > MAXLINKS=30 ; Max level 2 links
      > MAXNODES=120 ; Max nodes in nodes table
      > MAXROUTES=35 ; Max adjacent nodes
      > MAXCIRCUITS= 64 ; Max L4 circuits
      > MINQUAL=150 ; Minimum quality to add to nodes table
      > BBSQUAL=1 ; BBS quality multiplier, (BBSQUAL/256) ,
      > relative to
      > ; NODE. Used to limit spread of BBS node info
      > through
      > ; the network to your required service area.
      > [0,255].
      > ; APPL1QUAL if used overrides BBSQUAL.
      > BUFFERS=255 ; Packet buffers - 255 means allocate as many
      > as
      > ; possible, normally about 130, depending
      > upon other
      > ; table sizes.
      >
      > ; TNC default parameters:
      >
      > PACLEN=128 ; Max packet size (236 max for net/rom)
      >
      > ; PACLEN is a problem! The ideal size depends on the link(s) over
      > which a
      > ; packet will be sent. For a session involving another node, we have
      > no idea
      > ; what is at the far end. Ideally each node should have the
      > capability to
      > ; combine and then refragment messages to suit each link segment -
      > maybe when
      > ; there are more BPQ nodes about than 'other' ones, I'll do it. When
      > the node
      > ; is accessed directly, things are a bit easier, as we know at least
      > something
      > ; about the link. So, currently there are two PACLEN params, one here
      > and one
      > ; in the PORTS section. This one is used to set the initial value for
      > ; sessions via other nodes and for sessions initiated from here. The
      > other is
      > ; used for incoming direct (Level 2) sessions. In all cases the TNC
      > PACLEN
      > ; command can be used to override the defaults.
      >
      > TRANSDELAY=1 ; Transparent node send delay in seconds
      >
      > ; Level 2 Parameters:
      >
      > ; T1 (FRACK), T2 (RESPTIME) and N2 (RETRIES) are now in the PORTS
      > section
      >
      > T3=180 ; Link validation timer in seconds
      > IDLETIME=900 ; Idle link shutdown timer in seconds
      >
      > ; Configuration Options:
      >
      > AUTOSAVE=1 ; Saves BPQNODES.dat upon program exit
      > BBS=1 ; 1 = BBS support included, 0 = No BBS support
      > NODE=1 ; Include switch support
      > HIDENODES=1 ; If set to 1, nodes beginning with a #
      > ; require a 'N *' command to be displayed.
      >
      > ; The *** LINKED command is intended for use by gateway software, and
      > concern
      > ; has been expressed that it could be misused. It is recommended that
      > it be
      > ; disabled (=N) if unneeded.
      >
      > ENABLE_LINKED= N ; Controls processing of *** LINKED command
      > ; Y = allows unrestricted use
      > ; A = allows use by application program
      > ; N = disabled
      >
      > ; AX25 port definitions:
      >
      > ; The LOOPBACK port simulates a connection by looping input to output.
      > ; To test, start BPQTerminal and enter: 'C 1 XXNODE via XX0XX'
      > ; In this example '1' is the LOOPBACK port number. The LOOPBACK port
      > is
      > ; provided for testing purposes would rarely be included in an
      > established
      > ; system.
      >
      > PORT
      > PORTNUM=1 ; Optonal Number for use in Ports display.
      > ID=145.010 MHz ; Up to 30 Chars, appears on PORTS display
      > TYPE=ASYNC ; Hardware type.
      > PROTOCOL=KISS ; Protocol to be used on the link.
      > IOADDR=1 ; This is set to the com Port number.
      > SPEED=4800 ; Async link speed for KISS and NETROM links.
      > CHANNEL=A ;
      > QUALITY=0 ; Default quality for nodes heard on this
      > port.
      > MAXFRAME=7 ; Max outstanding frames (1 thru 7)
      > TXDELAY=300 ; TX Keyup delay in milliseconds.
      > SLOTTIME=100 ; CSMA interval timer (milliseconds) .
      > PERSIST=63 ; Probability to transmit' value (1-255).
      > FULLDUP=1 ;
      > SOFTDCD=1 ;
      > FRACK=4000 ; Level 2 timout in milliseconds
      > RESPTIME=1000 ; Level 2 delayed ack timer in milliseconds
      > RETRIES=10 ; Level 2 maximum retry value
      > PACLEN=236 ; Default maximum packet length for this port.
      > DIGIFLAG=0 ; Digipeat: 0=OFF, 1=ALL, 255=UI Only
      > DIGIPORT=0 ; Port to send digied frames on. Zero means
      > the port it was received on.
      > USERS=0 ; This limits the number of L2 sessions to
      > the supplied number.
      > UNPROTO=MAIL ; BTEXT broadcast addrs format:DEST[ ,digi1
      > [,digi2]]
      > ENDPORT
      >
      > ROUTES: ; Locked routes
      >
      > ; CALLSIGN,QUALITY, PORT[,MAXFRAME, FRACK,PACLEN]
      > ; The values in [...] if stated override the port defaults.
      >
      > ; No routes are specified, as they would be meaningless.
      >
      > *** ; Denotes end of locked routes
      >
      > ; Applications supported:
      >
      > ; The first three are reserved for BBS, HOST and REMOTE SYSOP. Five
      > ; additional applications, up to 12 bytes each, can be defined as you
      > wish.
      > ; Applications beginning with a * are not shown in the valid commands
      > display.
      >
      > APPLICATIONS= BBS,DX,*SYS ;no BBS, no host, remote sysop=*SYS
      >

    • Show all 24 messages in this topic