Title: BPQ32_409r_Beta_20050914
Target: BPQ32 Beta Testers
Author: Ron Stordahl, N5IN
Date: September 14 2005
1.0 DESCRIPTION
BPQ32 software is a product of John Wiseman G8BPQ/GM8BPQ, to whom the amateur radio community owes a debt of gratitude.
BPQ32 is not in the public domain; however it may be freely used by licensed radio amateurs in amateur radio packet applications. Informal assistance in using BPQ32 can be obtained through participation in the BPQ32 Yahoo Group.
This document is intended to guide users in testing of the beta release of BPQ32_409r.
This new version, while retaining the ActiveX (OCX) interface, offers a new program interface, AGWtoBPQ, bringing the full capabilities of BPQ32 to existing user programs having an AGWPE compatible interface.
BPQ32 is an AX.25 NET/ROM switch, running under Microsoft Windows®, which interfaces via standard RS232 com ports to TNC’s supporting KISS, JKISS, multi-drop BPQKISS and NET/ROM interfaces. It also supports connections via AX/IP/UDP as well as interfacing with AGWPE. This later capability allows BPQ32 to provide AX.25 NET/ROM services via sound card modems, in fact all device supported by AGWPE.
It is expected that those who choose to test this beta release of BPQ32 are already familiar with its use and configuration. Until full documentation for BPQ32 is written, the documents in archive bpq408a.zip remain essential reading!
2.0 BPQ32 file suite:
Name Size Type Modified
agwbits.txt
3 KB Text Document
9/12/2005 5:22 PM
AGWtoBPQ.exe 32 KB Application 8/11/2005 4:25 PM
BPQCtrl.txt 1 KB Text Document 2/24/2005 9:40 PM
bpq32.dll 304
KB Application Extension 8/10/2005
7:36 PM
BPQ32.exe 20 KB Application 11/16/1999
11:16 PM
BPQ32_409r_Beta_20050914.doc 63 KB Microsoft Word Document 9/14/2005 4:47 PM
BPQ32_409r_Beta_20050914.htm 49 KB HTML Document 9/14/2005 4.47 PM
bpqaxip.cfg 2 KB CFG File 9/14/2005 3:39 PM
bpqaxip.dll
40 KB Application Extension
8/12/2005 9:18 PM
bpqaxip.doc
3 KB Microsoft Word Document
9/2/2001 8:57 PM
BPQCFG.BIN 4 KB BIN File 9/14/2005 3:40 PM
Bpqcfg.exe 42 KB Application 12/5/1999 5:03 PM
Bpqcfg.txt 6 KB Text Document 9/14/2005 3:40 PM
BPQCtrl.ocx
29 KB ActiveX Control
9/3/2001 2:35 AM
bpqmon32.exe
76 KB Application
1/2/2000 12:59 PM
BPQNODES 1 KB File 8/26/2005 9:10 AM
bpqnodes.exe
17 KB Application 3/1/2000 12:07 AM
BPQTelnetServer.exe 20 KB Application 8/12/2005 9:16 PM
BPQTelnetServer.ini 1 KB Configuration Settings 8/9/2005 2:49 PM
bpqterm.exe
29 KB Application
2/23/2005 2:54 PM
BPQTerminal.exe 15 KB Application 8/7/2005 8:10 PM
BPQtoAGW.dll 27 KB Application Extension 8/12/2005 9:09 PM
cswsk32.ocx
106 KB ActiveX Control
9/25/2003 10:00 AM
password.bpq 2 KB BPQ File 9/7/2005 3:00 PM
Regcswsk32.bat 1 KB MS-DOS Batch File 3/14/2005 7:08 PM
RegSvrBpqOcx.bat
1 KB MS-DOS Batch File
8/25/2001 6:26 PM
Vb40032.dll 706 KB Application Extension 1/12/1996 3:00 AM
26
file(s)
Before copying these files onto your system, backup your existing BPQ32 directory, so that you do not lose files specific to your configuration.
3.0 APPLICATIONS
BPQ32 has two new interfaces. The first, AGWtoBPQ, on the front end, implements an AGWPE like interface, thus existing programs which are AGWPE compatible can now immediately interface with BPQ32. The second new interface, BPQtoAGW, on the back end, as defined in the Ports section of bpqcfg.txt, allows BPQ32 to access all devices supported by AGWPE. While the principal application of BPQtoAGW is to enable BPQ32 access to sound card modems via AGWPE, in fact any device that AGWPE supports can be accessed using the BPQtoAGW interface.
All of this new flexibility means that there are multiple ways of accomplishing the same objective. If, for example, you run only AR-Cluster, then you can choose either the native BPQ32 (BPQ-OCX) interface or the new AGWtoBPQ interface. But if you are running multiple applications, you will likely need the new AGWtoBPQ interface. As an example, AR-Cluster requires the BPQ32 configuration files in c:..\AR-Cluster\BPQ32\, while UIView requires them in c:..\Peak Systems\UI-View32\. Perhaps there is another way around this, but switching to the AGWtoBPQ interface is an immediate solution.
On the backend BPQtoAGW can be used to access some or all of AGWPE compatible devices. If all the devices you care to access are directly accessible by BPQ32, there is little reason to call upon BPQtoAGW. I have done so primarily to confirm that this was possible and also to exhaustively test BPQtoAGW. While there is overlap in the devices each supports, only BPQ32 can access BPQKISS multidrop and NET/ROM devices while only AGWPE can access sound card modems. Your specific hardware will guide your configuration.
BPQ32 can be used stand alone or interfaced with a user application. User applications with which I have tested it include: AR-Cluster (ARC), UIView32 , UI-DX Bridge (UIDX) and AGWPE. I am anxious to hear of user’s BPQ32 experiences with other programs.
The supplied bpqcfg.txt and bpqaxip.cfg files contain useful information; however please save your existing bpqcfg.txt and bqpaxip.cfg files which contain data unique to your installation.
The provided bpqcfg.txt file contains many examples of port descriptions. I know there are redundant, but harmless, parameter settings in that configuration file. I will sort these out later.
3.01 AR-Cluster
A new release of ARC V4.4.20 has been issued to support BPQ32_409r. In ARC V4.4.20 (as was also the case in earlier versions), when BPQ32 (now displayed as BPQ-OCX in V4.4.20) is selected in the I/O panel, an entry is added to the Windows® registry which defines a path of c:\Program Files\AR-Cluster\Bpq32\ to BPQ32’s configuration files. In this case the entire suite of BPQ32 files must be in that subdirectory. In such an environment, ARC will likely be the principal user of BPQ32 program services.
With the new AGW interface to BPQ32 (AGWtoBPQ)
it is likely other user programs will simultaneously share the services of
BPQ32, and for that reason you may wish to place the entire BPQ32 suite of
files in its own folder. If you choose
to do so I would recommend c:\Program Files\BPQ32\. However, ARC users, who wish to be able to
easily switch between BPQ-OCX and AGWtoBPQ should
instead place the new BPQ32 program suite in the existing \AR-Cluster\BPQ32\
folder. I have been using the AGWtoBPQ interface with AR-Cluster (plus UiView32 and
To maintain compatibility for existing users who wish to continue to use ARC with the BPQ-OCX interface, ARC V4.4.20 changes the handling of the registry key thus:
If you select the BPQ-OCX, interface in the I/O panel of ARC, the key: “HKEY_LOCAL_MACHINE\SOFTWARE\G8BPQ\BPQ32\Config File Location” will be set as “c:\Program Files\AR-Cluster\Bpq32”. Upon starting ARC, BPQ32.exe will be automatically started from ..\AR-Cluster\BPQ32\ and will expect to find its configuration files (BPQCFG.BIN and potentially bpqaxip.cfg) in that same folder. This is unchanged from earlier versions of ARC and BPQ32, thus if you wish to use the existing OCX interface simply place the new BPQ32 files in ..\AR-Cluster\BPQ32\. Then follow this sequence: 1) If you use the AX/IP/UDP interface you must have a valid bpqaxip.cfg file in the folder. 2) Execute bpqcfg.exe to compile bpqcfg.txt into BPQCFG.BIN. 3). Run, by double clicking, the two batch files: RegSvcBpqOcx.bat and Regcswsk32.bat. These enable the OCX interface, permit the new user utilities to function and are needed even if you only intend to use AGWtoBPQ.
If in ARC 4.4.20 you deselect BPQ-OCX, then the registry path information described above is nulled and the new BPQ32 will expect to find its configuration files in the same directory from which it was started, perhaps c:\Program Files\BPQ32 or c:\Program Files\AR-Cluster\BPQ32\. This will also be the case if the key is missing from the registry, which will be the case for systems which have never run ARC with BPQ32. ARC users should now start and end ARC with BPQ-OCX deselected to properly prep the registry. Follow the configuration process in the preceding paragraph. With BPQ-OCX deselected from the ARC I/O panel, ARC will no longer automatically start BPQ32, this is now up to you. Later in this document I will give a number of recommendations for auto-starting the BPQ32 system upon boot up.
With ARC 4.4.20, BPQ-OCX deselected, you should now select
AGWPE | BPQtoAGW in ARC’s I/O
panel. You will have to cancel and
restart ARC for this change to take effect.
You will be using the AGWtoBPQ interface,
which you must start by executing AGWtoBPQ.exe.
The running AGWtoBPQ has three
parameters:
In ARC select Cfg I/O Devices and confirm that you have enabled AGWPE|AGWtoBPQ. Click the button following that to open the Configure AGWPE|AGWtoBPQ via TCP window. In that window select AGWPE|AGWtoBPQ via TCPIP, check Enabled, for TCPIP Interface 1 set IP Address to 127.0.0.1 and Port to 8001. The enterprise version of ARC allows you to choose additional TCPIP interfaces 2 through 5, permitting you to serve multiple instances of AGWPE on other machines, locally or remotely. See 6.0 Known Issues for current restrictions. Click Apply, then click Exit, then click Exit on the prior window. You will receive a warning that changes you have made will not take place until ARC is closed and restarted. To get a clean start I recommend that you close both AGWtoBPQ (which closes all BPQ32 related windows) and ARC, then restart first AGWtoBPQ.exe, then ARC. After these have stabilized you will see on the ARC Connect tab a little green marker, following AGW Packet Engine, which includes the TCPIP interface port number. This indicates that ARC is getting a response back from AGWtoBPQ. Remote BPQ users now should be able to connect to ARC for DX spotting services.
On the ARC main window on the lower right hand side you will find two buttons, AGW and BPQ. If you right click on BPQ you will open a window wherein you provide a path to the BPQ Terminal Program. It’s likely to currently point to bpqterm.exe. While that program still runs, and the version in the beta package is a new version, it is depreciated and likely will be eliminated. Instead change that to the full path to bpqterminal.exe, the enhanced terminal program. That new program also includes the monitoring features of bpqmon32.exe. Bpqmon32.exe, although it still runs, is likely to be eliminated.
BPQ32 port numbers are defined by the user in bpqcfg.txt. The recommended practice is to begin with radio ports numbering from 1. The concluding port number should be for AX/IP/UDP if used. This is the practice followed in the supplied bpqcfg.txt configuration file.
3.02 UIView32
UiView32 may use BPQ32’s new AGWtoBPQ
interface, as an alternative to AGWPE. The
setup is exactly as with AGWPE with the exception that the port setting should
be for 8001 for AGWtoBPQ rather than the default 8000
used by AGWPE. In the supplied
bpqcfg.txt file, BPQ port 2 is used for APRS (144.39 MHz). You will need to set UIView32 to use the
appropriate radio port number for your site.
This is set in the Port Mask window,
3.03 UI-DX Bridge
3.04 BPQ32 Stand Alone Applications
BPQ32 may be run stand alone to provide AX.25 NET/ROM services via radio and AX/IP/UDP. A very useful application is described on my web page at Setting Up A Remote Access Site for AR-Cluster. That document has not yet been updated for the new version of BPQ32. The changes to it will be trivial however. It will be updated when the BPQ32 beta period is concluded.
3.05 AGWPE
BPQ32 implements an interface to AGWPE via AGWtoBPQ.dll. This allows BPQ32 to access all devices defined in AGWPE. See the file agwbits.txt as well as the supplied bpqcfg.txt for example port definitions. The main purpose of this interface is to allow BPQ32 access to sound card modems supported by AGWPE. However, it interfaces equally well with any device configured in AGWPE. Thus you can have AGWPE control all your devices and have BPQ32 access them via the AGWtoBPQ.dll interface.
4.0 New BPQ32 utility programs
BPQTerminal.exe replaces bpqterm.exe, although the later is still functional.
BPQTerminal adds a monitor window (replacing bpqmon32.exe) and adds scroll bars. It is envisioned that both bpqterm.exe and bpqmon32.exe will be removed from the BPQ32 suite after the beta period. Bpqterm.exe supplied with the beta is a new version.
BPQTelnetServer.exe allows remote access to the BPQ32 switch via a telnet connection from anywhere. The defaults are defined in BPQTelnetServer.ini:
TCPPORT=8010
LOGINPROMPT=user:
LOGINRESPONSE=ron
PASSWORDPROMPT=password:
PASSWORDRESPONSE=test
HOSTPROMPT=>
LOCALECHO=NO
Chose an appropriate name and password for security should you use this utility. After starting BPQTelnetServer.exe you can connect to it using telnet with a port number as defined in BPQTelnetServer.ini, i.e. port 8010. Using the simple built in Windows® telnet client the command would be ‘telnet my-ip-address 8010’. When connected you have the full range of BPQ32 commands, and you take on the call as defined by NODECALL= in bpqcfg.txt.
5.0 Automatically starting AGWtoBPQ
or BPQ32
If you will be using BPQ32 standalone, without AGWPE, then BPQ32.exe may be started by adding a shortcut to BPPQ32.exe in..\Start Menu\Programs\Startup\. A quick way to get to this folder is to right click on the Windows® Start button and select Explore. Windows® Explorer will begin at the Start Menu folder, and you can then drill your way down to two levels to the Startup folder, and there add a shortcut to BPQ32.exe.
If instead you are using the AGWtoBPQ interface, but without AGWPE, then do as above, but make the shortcut to AGWtoBPQ.exe.
When AGWPE is used is may be used to start other programs. Place a shortcut to AGWPE in the Windows® startup folder, then BPQ32.exe or AGWtoBPQ.exe as well as other user programs, such as AR-Cluster, UIView32 and UI-DX Bridge can be added to AGWPE’s startup list. This is convenient and assures that AGWPE is running and stable before it is accessed.
6.0 Known Issues and Limitations
Currently AGWtoBPQ provides little input buffering. While this is not an issue where the user programs access it on the same machine or even on a LAN to a nearby machine, when accessing it on a distant machine, for example via the Internet, a slow connection could cause it to run out of buffer space with fatal results. John, G8BPQ, intends to sort this out this autumn as time allows.
BPQtoAGW.dll, which interfaces BPQ32 to AGWPE, currently allows access to an instance of AGWPE only on the same machine, no ip address option is provided. This limitation is expected to be lifted when John finds the time.
AGWtoBPQ does not currently implement a monitor interface, thus if you attempt to use AGWTermTCP, which can perform multiple connects; the monitor window in AGWTermTCP remains blank. John may add the monitor interface as time allows.
7.0 Revisions
Revisions of this document as well as BPQ32 will be announced on the BPQ32 Yahoo Group.