Sound Card
Packet|
Introduction
|
HamScope and AGWPEHamScope is a digital communications interface that supports many modes including PSK31, RTTY, MFSK16 and packet (both HF and VHF). To run packet, HamScope 'connects' to an AGWPE 'port'. AGWPE does all the communication with the sound card or TNC for HamScope. HamScope is simply the terminal program that lets you "see" what is being received and transmitted. HamScope is different from most client applications in that it requires that the AGWPE files be located within the HamScope folder. They can't be in an AGWPE folder within the HamScope folder, and they can't be in a folder outside of the HamScope folder. The key AGWPE files -- AGW Packet Engine.exe, agwpe.sys, agwpe.ini, agwtcpip.sys, and all port*.ini files -- must reside with the other HamScope files in the HamScope folder. If you prefer, you could install AGWPE both in the HamScope folder (to work with HamScope) and in a second, separate folder (to work with other client programs.) To make it work: 1. Download and install HamScope: http://www.qsl.net/HamScope/ 2. Install the AGWPE files in the HamScope directory. Configure AGWPE and then test that it works with another program, such as AGWTerm. 3. In HamScope, from the Setup menu, select General Setup to bring up the General Setup screen. In the far right column enter the following:
You do not need to change any other values on this screen, such as PTT Control Setup or Sound Card selection. Those values are only used for other modes, such as PSK31. Since AGWPE controls those values for packet, changing them in HamScope will have no effect. 4. Back on the main HamScope screen, on the bottom half of the screen there is a Mode field. Use the drop down list to select Packet. HamScope should then start AGWPE. 5. If HamScope successfully hooks to AGWPE:
To see the commands to which AGWPE responds: at the "cmd: " prompt in HamScope , type in help and press enter. Note: HamScope version 1.55 (28 March 2005) fixed a problem with AGWPE on faster computers. In earlier versions, HamScope would tell AGWPE to load, but then HamScope couldn't detect that AGWPE was functioning.
|
||
| Return to top of page | |||
| Last Updated: 09/03/2010 |