Sunday, August 16, 2009

Blog-Post -11-Packet Radio by AGW Packet Engine

Blog-Post -11-Packet Radio by AGW Packet Engine

Finding and installing SV2AGW’s Packet Engine Software, AGWTerminal, a very simple terminal program. All the software listed here is for Windows – there are other versions of the software for most other operating systems. Just go to the original links provided in the tutorial below. For the windows versions, just go to the WA-DIGITAL yahoo group and check in the files section:

http://groups.yahoo.com/group/wa-digital/files/

and look in the Packet Radio Folder Using AGW

Or go to the original site by SV2AGW

http://www.sv2agw.com/downloads/default.htm

Instructions below were originally from: http://www.kc2rlm.info/soundcardpacket/

A huge THANKS! To Ralph Milnes, KC2RLM for the following information:

Download and Install AGWPE

1. Download the AGWPE Program

  • The AGWPE web site is http://www.sv2agw.com/ham/agwpe.htm
  • You can download the AGWPE program from the AGW Programs page on this site. It has download links to get the file from SV2AGW's website or directly from this website.

    The AGWPE setup file comes in "zip" format. If you need an unzip program, visit the WinZip site for the latest copy of WinZip.

2. Install AGWPE

Note: To remove a prior version of AGWPE from your system, simply delete the files in the AGWPE folder or, even simper, delete the folder. You can not use the Windows' "Add or Remove Programs" routine in the Control Panel, since AGWPE is not "installed" in Windows like most other programs.

Another option is to rename the older version's folder rather than remove it.

  • 1. AGWPE does not us the typical Windows "Add or Remove Programs" install routine from the Control Panel (Start> Settings> Control Panel> Add or Remove Programs ).

    Instead, simply extract the zipped files into a new folder. I always create a new folder for each version of AGWPE that I download, since each version of the program uses the same file names and I don't want to mix files from different versions.

Language files: You do not need to unzip the alternate language files into the AGWPE folder if you plan to use the default language of English. (For more information on alternate language files see the Tips and Tricks page.)

  • 2. Note that the main AGWPE program is called AGW Packet Engine.exe
    You may want to create a Windows shortcut to this file on your desktop. You can also add a link to AGW Packet Engine.exe on your Windows Start Menu by dragging and dropping a copy of the AGWPE shortcut icon onto the Windows Start button on the Task Bar at the bottom of your screen.
Do I need to install special drivers for using the parallel port to control PTTl?

Not any more. Earlier versions of AGWPE did require special parallel drivers, but they are no longer necessary. For the most recent versions of AGWPE, e.g. since version 2001.38, it is not necessary to download or use the drivers.zip file from the AGWPE site despite what the AGWPE program Help file or the AGWPE web site may say.

Basic AGWPE Program Setup

One Radio to One Sound Card

Navigating in AGWPE
Configuring the Radio Port Properties
Configuring the Sound Card

AGWPE uses the concept of Radio Ports to define how it will interface with a radio. An AGWPE radio port is created for each TNC, radio modem or sound card channel that AGWPE will manage. This page will show you how to setup an AGWPE sound card radio port in just a few minutes. Note that to complete your configuration, you will need to decide which RS-232 port (COM or LPT) you plan to use for PTT control, in other words, where your PTT cable will connect to the computer. Usually this is an unused COM port. See PTT Cable for more information.

Before starting AGWPE, always close:

  • any programs that might be using the serial or parallel port you plan to use for PTT control
  • any programs that might be accessing the sound card

a. Navigating in AGWPE

When you start the AGW Packet Engine.exe program for the first time, you will be greeted with a Packet Engine banner all in gold and a Software License Agreement which you must accept. The banner will disappear in a few seconds or you can click on it once to speed things up. At this point, you will discover that AGWPE does not put an open Window on your desktop, nor will there be a button on the bottom Task Bar of your screen. Instead, all you will find is the AGWPE tower icon AGWPE Tower Iconon your Windows System Tray at the bottom right of your screen. This icon is your only access to AGWPE when it is running! To help you find it, a yellow pop-up 'balloon' message points to the icon when AGWPE starts.

To change any of AGWPE's configurations, left or right click on the AGWPE icon AGWPE Tower Iconto bring up AGWPE's pop-up menu:

Note: The Sound Card Tuning Aid option on the menu
will be grayed out until you create and configure a "radio port"
as described below.


b. Create and Configure an AGWPE Radio Port

The first step in working with AGWPE is to create and configure a radio port for a sound card channel and its associated radio. From the AGWPE menu, select Properties. A blank RadioPort Selection window will open. Press the New Port button on the right. A message window will appear: A New TncPort File Has Been Created. Click OK to close the message and move on.

The Properties for Port`1 window should now appear. Remember that AGWPE also can manage TNCs and radio modems, so some of the fields on this screen will not pertain to sound cards. The field outlined in red will be the key fields for a sound card radio port. Follow the step below in filling out the fields:

1. Make the following selections first on this screen (i.e. TNC Setup tab):

Select Port

enter the port where you will attach your PTT cable, e.g. COM1 or LPT1; see notes below *

TNC Radioport:
Port Description

you can overwrite the current description for Port 1 and enter a description of your own choice, e.g. Icom 1200 Packet

* Notes about Port selections (COM & LPT):

  • To select a parallel port scroll to the bottom of the port list
  • If you are setting up a receive-only installation or using a SignaLink interface or other audio-controlled PTT interface and don't want to tie up a real port for a PTT line you won't be using, the AGW software will accept non-existent parallel port assignments, but not non-existent serial ports.

2. You can leave all other selections at their defaults, including Serial Port/ Modem Baud Rate, which is not used for sound cards.

3. Now go to the TNC Type field in the top middle of the screen and use the pull down list to select "Sound Card".

c. Settings on the Sound Card Setup screen:

When you select "Sound Card" for your TNC Type (or if press the Options button in the middle of the TNC setup window, underneath TNC subtype), the program will bring up the SoundCard Modem/TNC Setup window which looks like this:

1. Baud Rates: Note that your sound card is capable of supporting two radio ports using its left and right audio channels. If you are only using one radio, it will be Port 1 on the left channel. Set the left channel baud rate for the rate you plan to use, i.e. 300 baud for HF SSB work; or 1200, 2400, 4800, or 9600 for VHF/UHF work.

Assuming that you will not be using the right channel for a second radio connection, set the right channel rate for a baud rate different from the one you have chose for the left channel. This may prevent the possibility of future problems. (If you will be connecting to 2 radios, see Configuring AGWPE for 2 Radios. )

2. Sound Card Selection: Use the pull down menu to select the sound card device you will be using with AGWPE. You may see other choices, such as a telephone modem (don't use) or another another card if you have two.

3. For now leave the other fields at their defaults:

  • Full Duplex Driver: The Full Duplex Driver box should be checked. Most recent sound cards are full-duplex capable. If you later encounter transmitting problems, you may need to un-check the Full Duplex Driver box. This is likely to apply only to older sound cards; see Problems with Connections for more about this.
  • Sound Card Clock: This setting is used if you have problems receiving distant stations; see the Problems with Receiving page for more information, but for now leave the setting at 4, the default.

Now press the OK button to return to the Properties for Port1 window but do not close it yet.

4. Note that, by default, AGWPE has created two sound card radio ports. To avoid future operating problems, change the setting from Dual Port to SinglePort in the TNC Control Commands section of the Properties for Port1 window. (Doesn't apply if you really will be connecting to 2 Radio).

For a simple, first time installation, all other selections can remain "as is" (use the default selections), including those in the Tnc Commands tab window in the Properties for Port1 window and any other selections on the AGWPE menu.

5. Now press the OK button at the bottom of the Properties for Port1 window. You should get a popup message telling you to restart the program, so click on the Packet Engine icon AGWPE Tower Icononce again and select 'Exit'. Now restart AGWPE. The Packet Engine icon AGWPE Tower Iconshould once again appear, but in addition you should now see a TNC icon AGWPE Modem Iconnext to it. This new icon represents your new sound card Radio Port.

d. Editing a Port's Properties

If you want to change a setting in the Radio Port's configuration, click on the AGWPE icon to call up the menu, select Properties, and then click on the radio port you want to change. Then click OK and edit the fields in the Properties for Portx window.


e. Problems?

  • Any time you have trouble starting or configuring AGWPE, it is often best to close AGWPE and delete all port*.ini files and the agwpe.ini file in your AGWPE directory/folder. Then restart and re-configure AGWPE from the very beginning.
  • If you don't see this TNC icon AGWPE Modem Icon, you probably have a conflict with another program or device:
    • Make sure that the COM or LPT port you have select in AGWPE is not already dedicated to another device, for example, an internal modem or printer) or has been "captured" by another program (for example, your Palm Pilot's "Hot Sync Manager". You'll have to resolve any conflicts by either closing the other program, disabling the device, or selecting another port for AGWPE's PTT control.
    • Make sure that no other program is running and using the the sound card.

For further help in resolving port conflicts, go to the Problems with Program Behavior page on this site.

BEGIN SPECIAL SIGNALINK SETUP SECTION +++++++++++++++++++++++++++++++++

AGWPE and the SignaLink USB

The Tigertronics SignaLink USB interface (http://www.tigertronics.com/slusbmain.htm) has many interesting features of value to AGWPE users:

* Includes a built-in "sound card" chip so AGWPE doesn't need to use your computer's sound card

* Uses the TX audio (VOX) to trigger your radio's PTT circuit -- doesn't need a serial or parallel port on your computer for PTT control

* Only a single USB cable to the computer -- no audio cables to sound card jacks

* Powered by the USB connection

1. Configuring the SignaLink USB for AGWPE

Be sure to read the SignaLink USB (SLU) documentation, especially the part about configuring the jumper wires inside the SLU to match your radio's pin-outs .

To create an AGWPE radio port for the SLU, first plug in the SLU's USB cable to your computer. Your computer should recognize a new USB device. (In my XP computer, Windows "connection" tones can be heard when this happens.)

Then follow the basic AGWPE setup to create an AGWPE radio port but with these exceptions:

1. In the Properties for Port1 window, for the Select Port field, select a non-existent LPT (parallel) port. Since the SLU does not require either a COM or LPT port for PTT control, there is no need for AGWPE to tie up a COM or LPT port on your computer.

2. At the bottom of the SoundCard Modem/TNC Setup window (found by pressing the Options button in the middle of the Properties for Port1 window), you will find the SoundCard Selection field. If necessary, use the scroll arrow to reveal and select the SLU's sound card, which is called USB Audio CODEC (on some computers it may be called USB Audio Device.

<-- click on this image for a larger image of the SoundCard Modem/TNC Setup window.

Then press OK to close all the AGWPE windows and restart AGWPE. The SignaLink USB should now be set to work with AGWPE.

2. Troubleshooting AGWPE - SignaLink USB (SLU) Problems

The SignaLink USB Installation and Operation Guide contains detailed information about recommended SLU settings and troubleshooting. There is also a website which has troubleshooting information http://www.tigertronics.com/slusbts.htm

Here are just a few key things to check if you have difficulties:

a. Received Audio - The RX audio dial on the front of the SLU is the only way to increase or decrease the RX audio levels (unless you are getting the RX audio from the speaker of your radio, in which case your radio volume control dial will also have an effect on the RX audio level). I've had good success with the SLU's RX audio dial set to the 9 o'clock position.

[You may have experience with other sound cards which use the Windows Volume Control Recording sliders to adjust RX volume levels. There is no such control with the SLU; likewise the RX control sliders on AGWPE's Sound Card Tuning Aid screen have no effect on the SLU's RX Audio levels.]

Also, set the DLY (Delay) dial on the front of the SLU to the 7 o'clock position (fully counterclockwise). This minimizes the time the SLU keeps your radio in transmit mode. If you increase the delay, the packet station which you are communicating with may begin to transmit before the SLU and your radio return to "receive" mode and you will not receive the first packet from the distant station.

b. TX Audio -

* Use the Windows Volume Control program to control the SLU's TX audio levels. Follow the instructions on the Sound Card settings page of this web site, but set the Speaker slider for the USB Audio CODEC to maximum (up) and set the Wave slider to 50%.

* Set the TX audio dial on the face of the SLU to the 9 o'clock position.

c. PTT Transmit fails:

* If the SignaLink USB's PTT LED does NOT turn ON: Verify that the SignaLink USB’s PWR LED is ON. If it is not, then make sure that the SignaLink USB's PWR switch is pressed in and the USB cable is securely connected to the computer and the SignaLink.

Make sure AGWPE is configured to use the SignaLink USB’s built-in sound card. The program should have “USB Audio CODEC” selected.

Try increasing the Wave slider in the Windows Volume Control program for the USB Audio Codec. (There is also a special jumper setting inside the SLU to further increase TX audio levels; see the SLU Installation and Operation Guide.)

If the SignaLink is plugged into a USB hub, verify that the hub is a powered hub. Non-powered hubs may not supply enough power for the SignaLink to operate properly (Receive will work, but Transmit may not).

* If the SignaLink USB's PTT LED turns ON but the radio doesn't switch to transmit, then you have most likely incorrectly installed the PTT jumper wires inside the SLU. Double check the wiring there and also make sure that the cable to your radio is going to the correct PTT pin (in some radios, the PTT pin for FM packet is different from the one used for SSB modes such as PSK-31, RTTY and SSTV; if this is the case, you will need a different cable for packet).

END SPECIAL SIGNAL LINK INFO +++++++++++++++++++++++++++++++++++

Basic Sound Card Settings for AGWPE

For AGWPE to work, you need to set four basic sound card settings correctly:

  • The receive audio source
  • The receive audio volume level
  • The transmit audio source
  • The transmit audio volume level

You can adjust these sound card settings in two ways:

Other information on this page includes:

There are some advanced sound card settings that may also affect you. These include "Speaker Type", "Hardware Acceleration", and "Sample Rate". These are discussed on the Additional Settings page of this web site.

1. Using AGWPE to Adjust Basic Sound Card Settings

To set the volume controls from within AGWPE, right click the AGWPE tower icon to bring up the AGWPE menu and then click on Sound Card Tuning Aid. The Tuning Aid is a great way to adjust your RX (receive) volume. Note that the Tuning Aid screen window will remain on top of all other windows. You can drag it with the blue Title Bar if it gets in the way, but it's handy to keep it displayed throughout the volume adjusting process:

Then in the AGWPE Sound Card Tuning Aid window, click on the Set Volume button to get to this window:

See the sections a. and b. below for more information about these controls:

Bug Report: There are still some problems with this AGWPE feature as of 2003.308:

  • By default, this window assumes the LINE IN is the RX Input Line. If you are using LINE IN, then you will have no problems and can use the volume sliders to adjust your RX audio level.

    The bug is that the window will not let you change the RX Input Line (audio source) as the pull down menu suggests. For example, if the sound card is now set to use the "LINE IN" jack as the audio source, then selecting "MIC" as the RX Input Line in this window will have no affect. The sound card (and AGWPE) will continue to use "LINE IN". You will be able to control the volume sliders for the source you select, e.g. MIC, but your input source will not change to MIC.
  • If you have two sound cards in your system, AGWPE only controls the volume settings on the first sound card. If you are using a second sound card for AGWPE, then this window will have no affect on the settings for that second card.

If either of these problems affect you, then you need to use the Windows' Volume Control Program (see #2 below) to adjust the input source and/or the sound card being used. See #2 below.

a. Receive Audio Settings (via AGWPE)

  • Receive Audio Volume: The left Rx slider controls the receive volume (recording volume) of the left channel or port 1 of the sound card. The right column sliders control the right channel or port 2. (If you are using only one radio port in AGWPE, it will be the left slider).

    I've had good success with the sliders set 1/3 up from the bottom. Be sure not to set them too low since it may stop all input (they don't have to be to the very bottom for audio input to be stopped). Use the sound card tuning aid's Sine Wave scope to see the results of your settings. The sine waves should fill about half the scope as in the Tuning Aid screen shot above. Use the volume slider to adjust the wave size. If you get the output from the radio's speaker jack, you can also adjust the radio volume. AGWPE is pretty tolerant of RX volume levels, but conceivably it is possible for the volume to be too loud or too soft.

    If you don't see any waves, then your audio source setting is probably incorrect (see next paragraph) or, if you are using the radio's mike or speakers for RX audio, your radio's squelch in on; turn it off so you can hear the channel noise.

Visit the Sound Card Tuning Aid page for more information, including screen shots of signal problems.

·

  • Receive Audio Source: See Bug Report above. The Rx Input Line (audio source) does not work as advertised in version 2003.3008. You need to use the Windows' Volume Control Program (see #2 below) to adjust your settings.

    [When the bug is corrected, you will be able to select the source of your receive audio, either Line (meaning LINE IN) or Microphone, depending where your RX audio cable is plugged. As the screen says, other sources will be muted and that's good.]

    (If you opt to use the Microphone instead of the Line In for RX in, be sure that you do not use the Microphone Boost option of your sound card. See Windows' Volume Control Programbelow for instructions on how to configure boost.)

  • Set/Restore Options: If you use your sound card for programs other than AGWPE, the Set These Levels on Start and Restore Levels on Exit will be helpful. They allow you to set the volume especially for AGWPE and then return them to their previous settings when you exit AGWPE.

b. Transmit Audio Settings (via AGWPE)

  • Transmit Audio Volume: The Tx Master sliders and two Tx Wave volume sliders work together: Wave means Program, in this case AGWPE and the packet tones it generates. The Tx Master sliders are a master control that will further adjust the Wave volume.

    As with the RX sliders, the left column sliders (for both Master and Wave) control the left channel or port 1 of the sound card. The right column sliders control the right channel or port 2.

    I've had good success with the sliders set 1/3 up from the bottom. Your setting will depend largely on how well the attenuation circuit in your TX audio cable matches the optimal microphone input level for your radio. See How Much TX Volume? below for some further advice.

    It is essential that none of these two sliders be at the absolute bottom or near the bottom, as that may stop all output.

How Much TX Volume?

You can get a rough idea of your TX volume by temporarily plugging your computer speakers into the LINE IN jack. But that will not tell you how what your TX audio sounds like on the air. It would be better to listen to your transmitted audio with a second radio.

But the best way to check your transmit volume is with a deviation meter. The correct deviation is 3.75 kHz of deviation (+/- .25). But since most of us don't have a deviation meter, Jim K6CCC offered this alternate suggestion:

My standard advice for people who do not have access to a deviation meter is to set your path to digipeat through a single local digipeater (e.g. TEST VIA WIDE ), then go into converse mode (UI mode) and transmit a single carriage return. Watch to see if your single packet gets digipeated by that one local digipeater. If it doesn't get digipeated on your first attempt, try several more times because it may not have gotten through because of a collision. If it does not get through after a few attempts, turn up the volume just to that point where it gets through reliably.

Conversely, if the packet does get digipeated, turn down the transmit audio level a little and try again. Keep doing this (turning down the volume) until your packet does not get digipeated reliably. Then turn it back up just a little bit and verify you can get the packet reliably digipeated.

It's FAR better to have your volume too low than too high!

When you are done, press OK to save your settings and then close the Tuning Aid window.

2. Using Windows' Volume Control Program to Adjust Sound Card Settings

It's also possible to set the volume control settings with the Windows' Volume Control program, but the AGWPE method above in #1 is much easier. However, there may be some settings, such as Microphone Boost, that can only be controlled by Windows' Volume Control program and not AGPWE. The The sections below discuss how to configure Windows' Volume Control for :

To start, you should see the volume control icon Windows Speaker Iconin the system tray on the lower right of your screen. If you don't, follow the directions on the sound settings page to display it.

a. Transmit Audio Settings (via Windows)

To set the source and volume level of your outgoing packet tones:

  • Left click twice very quickly on the Volume Control icon Windows Speaker Icon(or go to the Control Panel and Sounds: Audio). The Volume Control window should open . It initially displays settings for just the Playback or TX audio ( sound card-to-radio). Here is what that window looks like in my system; it may be somewhat different in your system because of the sound card type:


  • The settings of importance on this window are:
    • The left most Volume Control volume slider and the Wave volume slider work together. Consider Wave to mean Program, in this case AGWPE, which is creating the outgoing packet tones. The Volume Control slider is a master control that will further adjust the Wave volume.

      I've had good success with both sliders set 1/3 up from the bottom. Your setting will depend largely on how well the attenuation circuit in your TX audio cable matches the optimal microphone input of your radio. See How Much TX Volume? below for some further advice.

      It's essential that neither of these two sliders be at the absolute bottom or near the bottom, and it's essential that the Mute boxes are not checked.
    • Leave all Balance sliders in the middle. They are for stereo channel control and setting the slider to the wrong side could mute outgoing sounds to one of the two possible sound card channels/radioports.
    • I mute all other audio output sources ( Mic, Line In and CD) so that only AGWPE (wave) outputs sound to the radio and not other sources.

b. Receive Audio Settings (via Windows)

To set the source and volume level of your receive or RX audio is a bit more difficult to find. These settings are found in a different Volume Control sub-window, the Recording Control window, whereas the outgoing sounds (see A. above) are set in the Playback window. This is very important. Many people do not realize this Recording window exists. Failure to get the recording settings correct results in problems receiving packets. To get to the Recording Window:

  • From the Playback Volume Control window shown above, select the Options menu choice, then Properties.
  • Click on the Recording radio button to bring up the list of volume controls. Make sure that there's a check mark next to the jack where you plugged in your radio RX audio cable -- either Line In (preferably) or Microphone. Here's what this window looks like on my system.

· When you're done, click on the OK button.

· You should now see the Recording Control window (or the Wave In window as it is called in my system). Since I use the Line In jack for Radio RX audio, here's what my settings look like. Notice the Select check mark under Line In:


· Click the Select box for the jack where you will plug in your radio RX audio cable, either the Line In (preferably) or Microphone.

· Set the volume slider about 1/3 up (soft). This should work for you, but note that AGWPE can probably handle any setting other than "off/quiet". See How Much RX Volume? below for some further advice.

· Leave the balance slider in the middle.

· After you've made your choices, click the 'X' in the top right corner of the window to close the window and the Volume Control program. Your settings will be saved automatically.

Microphone Boost: If you opt to use the Microphone instead of the Line In for RX in, do not use the Microphone Boost option if it is offered by your system. I found this option by clicking on the Advanced button found under the Microphone slider in the Recording Control window. The "boost" feature typically adds a 20 dB increase in audio volume and is designed to amplify the weak signal from a computer electret microphone. The audio from your radio is normally already too high for input into the MIC jack (that is why you are advised to add an attenuation circuit to the RX cable). So using the boost feature can make the problem worse.



3. Configuring the Volume Control program for a Second (or more) Sound Card

If you have two or more sound cards installed, you will need to set the playback and record settings for the additional cards (those used by AGWPE). Here's how to do it:

  • Left click twice very quickly on the Volume Control icon Windows Speaker Iconin the System Tray. The Volume Control window should open.
  • Select the Options menu choice, then Properties to bring up the Properties Window.
  • At the top of the Properties window, you'll see a Mixer Device field. Click on the down arrow ▼to the right of the field to call up a list of mixer devices.

ç Click to enlarge

  • Click on the second sound card to select it. Then after making sure the Playback button below it is selected, press the OK button. This will return you to the Volume Control playback sliders for the second card (the sound card's name will be in the lower left of the window). Make your settings as you did above in Transmit Audio Settings.
  • When your done with the playback settings for the second card, select the Options menu choice again and then Properties to bring up the Properties Window again.
  • Once again click on the down arrow ▼to the right of the Mixer Device field to call up a list of mixer devices.
  • Click on the second sound card again to select it. This time make sure the Recording button is selected and press the OK button. This will bring you to the Volume Control recording sliders for the second sound card . Make your settings as you did above in Receive Audio Settings.

4. Preserving your volume control settings

When most systems reboot, the volume control settings will remain as they were when you shut down. This is more likely if you use the Set and Restore Options in AGWPE's SoundCard Volume Settings screen, see Receive Audio Settings above.

However in some sound cards/systems, when Windows reboots, your Volume Control settings may automatically be reset to a default that is something other than you want. This happened to me with one sound card. Even though I would chose Line In as my desired 'audio in' recording source, as soon as I rebooted, Microphone became the recording audio source! I'm not sure why this was happening -- perhaps it was the sound card mixer program.

Or your ideal AGWPE settings may be changed by another program that subsequently uses the sound card.

You have two main options if this is happening to you:

1. Each time you run AGWPE after a Windows boot/reboot, re-configure the Volume Control Recording Control properties as above.

2. Use a utility program that, on startup, automatically sets the Volume Control settings the way you want them. I used a small (260 kb) freeware utility called QuickMix to do this. You can download the program from the Quick Mix web site.

Using QuickMix

1. Install QuickMix by running the QuickMixIn.exe program that you downloaded.

2. Set the Windows Volume Controls the way you want.

3. Run the QuickMix program and 'save' the Volume Control settings to a AGWPE.QMX file in the directory of your choice.

4. Then you can run QuickMix (or just click on the .QMX file) to restore your AGWPE settings.

If you want to have this .QMX file automatically load at boot-up, put a shortcut to this .QMX file in your Windows startup folder. For me, that would be:

C:\WINDOWS\Start Menu\Programs\StartUp


In Windows Explorer, go to this directory and, from the Menu bar, select File, then New, then Shortcut, and then Browse to the AGWPE.QMX file you want. (Make sure you set the Browse directory window to show All Files, not Programs.)

5. Now whenever you start Windows, it will automatically read the AGWPE.QMX file, load and run QuickMix, reset the Volume Controls, and then close QuickMix.

Additional Sound Card Settings for AGWPE

Related Multimedia Properties
Displaying the Volume Control Icon
Turning Off Window's Sounds

This page has additional sound card/multi-media properties that may be help in operating AGWPE successfully. (See the Sound Card Settings page on this site for basic sound card settings.)

1. Related Multimedia Properties

Three additional Windows multi-media properties can affect AGWPE performance:

  • Speaker Type - affects TX audio; generally, Desktop Stereo Speakers should be selected
  • Hardware Acceleration - can affect both TX and RX audio; generally, the highest rate the computer can handle should be selected but if AGWPE is having packet decoding or connection problems, set it to a lower speed.
  • Sample Rate Conversion Quality -- affects both TX and RX audio; generally, the highest rate the computer can handle should be selected

These settings are usually made from the same general area in version of windows.

· Windows 95: There is little to set in the Multimedia Properties window. I'm not sure if the Recording Preferred quality or CD Quality setting makes a difference. Click on the Apply button (if not gray-ed out) and then the OK button to close the window.

· Windows 98/ME: Go to Start: Settings: Control Panel and select Multimedia (98) or Sounds and Multimedia (ME). With the default Audio tab showing:

o Click first on the Advanced Properties button under the Playback: Preferred Device . On the resulting Speaker tab, select Desktop Stereo Speakers (or lap top mono, maybe). According to George SV2AGW, anything else will distort the TX sound.

o Then click on the Performance tab next to the Speakers tab. Hardware Acceleration should be set to Full, at least at first to see if your computer can handle it. If AGWPE is having packet decoding or connection problems, you can try setting it to a lower speed.


o Below the Hardware acceleration settings is the Sample Rate Conversion Quality setting. Set this to Best. Then click OK to close the Playback Advanced Properties.

o Back on the Audio tab, click on the Advanced Properties button under Recording: Preferred Device. On the Performance tab, once again set the Hardware Acceleration one stop before Full, at least at first to see if your computer can handle it. If AGWPE is having packet decoding or connection problems, set it to a lower speed. And set Sample Rate Conversion Quality to Best. Then click OK to close the Sound Recording Advanced Properties.

o Back on the Multimedia Properties window, click on the Apply button (if not gray-ed out) and then the OK button.

o On the Audio tab, click on the Advanced button for (Sound) Playback

o Click OK to save the settings and leave the Sounds settings.

· Windows XP: Most of the default settings should be as described below but you should check them. Go to Start: Settings: Control Panel and select Sound and Audio Devices. On the Audio tab, press the Advanced button under Sound Playback

o On the resulting Speaker tab, select Desktop Stereo Speakers, even if this is a lap top.

o Then click on the Performance tab next to the Speakers tab.

o Hardware Acceleration should be set to Full, at least at first to see if your computer can handle it. If AGWPE is having packet decoding or connection problems, you can try setting it to a lower speed.

o Sample Rate Conversion Quality must be set to Best.

o Then click OK to close the Playback Advanced Properties and return to the Sound and Audio Devices: Audio tab.click on the Apply button (if not gray-ed out) and then the OK button.

· Windows 2000: the default hardware acceleration and sample rate conversion sliders are in the middle position. Follow the general instruction for XP above and move these to the right for best performance.

2. Displaying the Volume Control Icon Windows Speaker Icon

If this icon is not currently in your Windows System Tray (bottom far right of your screen), you may want to add it. It lets you quickly access the Windows volume and audio source settings of the sound card, including some that can not be controlled by AGWPE's SoundCard Volume Settings screen.

  • In Windows 98 it's , Start: Settings: Control Panel: Multimedia: Audio tab and check Show volume control on the taskbar.
  • In Windows ME it's: Start: Settings: Control Panel: Sounds and Multimedia: Sounds tab; Sound Volume box and check Show volume control on the taskbar.
  • In XP, it's Start: Control Panel: Sounds and Audio Devices: Volume tab and check Place volume icon in the taskbar.
  • I'm not sure how it's done in Windows 95, but it's probably very similar to Win 98.

3. Turning Off Window's Sounds

On some computers you may have conflicts between a program and Windows itself over the use of the sound card. (A typical crash message is "an application caused an invalid page fault in module WINMM.DLL"). To avoid this, try turning off Windows' sounds.

  • In Windows 98 it's: Start: Settings: Control Panel: Sounds: Schemes field = No Sounds
  • In Windows ME it's: Start: Settings: Control Panel: Sounds: Sound Events: Scheme = No Sounds.
  • In XP, it's Start: Control Panel: Sounds and Audio Devices: Sounds tab: Sound Scheme field = No Sounds.
  • I'm not sure how it's done in Windows 95, but it's probably very similar to Win 98.

Sound Card Tuning Aid

The Sound Card Tuning Aid screen is accessible from the AGWPE menu and can be used to "see" the quality of received signals and, for HF packet particularly, help in tuning the radio to the correct frequency. At least one oscilloscope will appear on the left side of the screen. A second scope below the first only appears if you have selected Dual Port use of the sound card on the Properties screen.

This page gives describes the Tuning Aid and gives some examples of good and bad signals as seen on the tuning aid's oscilloscope.

The first screen shot below shows the Tuning Aid page with the sine wave view selected. Only one oscilloscope is visible since the sound card is running in Single Port mode. In Dual Port mode, another scope would appear beneath the first. Note the sine wave in the scope. This is what a quiet 1200 baud packet channel looks like. The only undulation in the wave is due to noise. It verifies the audio connection to the sound card and radio is working.

<-- Click for larger image

In contrast, if the sine wave was perfectly flat (or nearly so), as below, then you know you have no audio input from the sound card, either because of a problem with the audio feed from the radio or incorrect sound card volume settings (source or volume):

<-- Click for larger image

Oscilloscope Styles

There are four (4) display styles available for the Oscilloscope. The first two are generally the most useful.

1. Sine Wave - shows strength of the signal (audio volume) and the quality of the signal. A signal with good strength will have waves that fill about 1/2 of the screen (relative distance between the peaks and valleys of the wave). You can use the Volume Control settings for RX audio to adjust them.

Signal samples for 1200 baud:

Sample of a good signal;
packet decoded.


Too weak or distant;
packet was not decoded


Collision of packets;
packet was not decoded

This is from a Yaesu FT209 transceiver with bass boost activated. The boost creates incorrect pre-emphasis: the low tone is emphasized, not the high tone. These packets can only be decoded about 80% of the time. The sending station must turn off the radio's bass boost option to correct this.



Below, a 9600 baud signal sample:


This is a generally good signal that was decoded, but you can see small sparks caused by some "bug" at either the transmitting station or receiving radio or sound card.



2. Waterfall -
This is a frequency spectrum display that shows activity in the audio pass band over the last few seconds. Received signals create color streaks which will 'fall' down the display as time progresses. Relative signal strength is indicated by the colors, which are -- weakest to strongest -- blue, green, yellow, red. Black indicates no signal.

The waterfall should be centered between the two vertical white lines. For AFSK (UHF/VHF), it should center automatically. For HF operations (FSK), adjust the radio's receive frequency to center the waterfall. Centering is critical for accurate decoding of HF packets. The strongest signal (yellow/red color streak) must lie between those two lines, as this next screen shot illustrates:


The screen shot below shows an HF radio that needs tuning. The yellow area showing packet activity is below the tuned frequency marked by the two vertical lines:

This sample below is a waterfall display showing two 1200 baud packets. The packets have black areas to their left and right of the two vertical white lines.

The upper packet has fair modulation and was decoded. Also, note in the black area above the packet that there are small green vertical lines. This is the result of TXDelay, i.e. a short interval of carrier with no modulation.

The bottom packet has very low modulation (little color; similar to a carrier with no modulation), but the packet was still decoded.


3. Eye
- is really a scatter diagram. The closer together the scattered points, the better the signal.


4. Frequency -
a real-time display of where signals are being heard along a frequency scale. The TWO white vertical lines are centered around the dialed frequency, and the majority of signal peaks and valleys should fall between the left line (lower tone) and the right line (upper tone). If they don't, you'll need to change the radio's dialed frequency to center the signal between the white lines.



Set Volume Button

Pressing this button takes you to the sound card Volume Settings window where you can adjust TX audio levels, RX audio levels, and the RX input source jack.

Problems with Program Behavior

1..Problems with the AGWPE Program
2. Linking to Client Applications

3. Extra packets seen

Note: Please make sure you are using the latest version of AGWPE before troubleshooting problems. Your problem may have been fixed by the most recent version of AGWPE!

As you troubleshoot receive problems, remember that AGWPE provides you with a some visual aids:

  • If AGWPE loads successfully, you will see the AGWPE tower icon at the bottom right of your screen in the Windows System Tray.
  • If a "radioport" has been successfully configured, you should see the AGWPE modem icon next to the tower icon. There will be one modem icon for each working radioport. A green pixel in the modem icon will flash once if AGWPE successfully decodes a packet. A red pixel in the modem icon will flash once if AGWPE has sent a packet to the soundcard and radio for transmission.

1. General Program Problems

General Troubleshooting Hint: Any time you have trouble with a configuration setting in AGWPE, it may be best to just start fresh: close AGWPE and delete any port*.ini files and the agwpe.ini in your AGWPE directory/folder. Then restart and re-configure AGWPE from the very beginning. It doesn't take much time.

  • When I try to start AGWPE, I get an error message that says "Can not find WS2_32.dll"

Sounds like you're running Windows 95. You need the Winsock 2 Update from Microsoft. See the Windows update page on this site for the full solution.

  • I'm running Windows 98 SE. After I configure AGWPE for my sound card and restart AGWPE, I get Windows' blue crash screen saying "A fatal exception 0E has occurred at (some address) in VXD KMIXER. The current application will be terminated."

    You have a problem with your sound card driver and the KMIXER.SYS, Windows' audio mixer kernel. Windows 98 used VXD drivers in its original version but then switched to WDM drivers in SE (Second Edition). I suspect there's a problem with Windows calling the incorrect driver file. You might try totally uninstalling the card and drivers from Windows and then, when it restarts, point it to the new WDM drivers. On the other hand, some users have found success, with the opposite, counter-intuitive strategy -- uninstall the newer WDM drivers and install the VXD drivers.

    Warren sent me his solution that is, essentially, to install the latest drivers for his sound card:

"Here is my solution to the Win98SE problem with the VXD and WDM issue with AGWPE. My problem was the VXD KMIXER(06) fatal error

My environment: Win98SE All Windows updates done Pentium 533MHz 512MB Ram Chipset Via Pro133 82C693A and 82C686A (Southbridge). Sound is integrated on the mother board and is AC'97 v2.1 CODEC in the 82C686A Southbridge chip.

When first checked, the drivers being used for the sound chip were:
VIAaudio.sys 4.10.3104 MMDevldr 4.10.1998

A visit to the VIA site gave a later driver package. The file downloaded was Vinyl_AudioCodec_V570a.zip

(This also produces another volume controls interface, called Vinyl Deck, that gives an easier volume interface than the Windows one. )

Even though I read the suggestion about forcing Win98SE to take the VXD driver, I decided to just let the new driver package run and install WDM as it should. This proved successful and AGWPE does not now produce the VXD error.

The drivers are now: Vinyl AC'97 Codec Combo Driver (WDM) 10.10.2004

So it looks like a fix by using the latest sound drivers and these more modern drivers seem to take care of the use of VXD / WDM in different Win98/98SE editions."

  • The AGWPE banner comes up, but then I get an error message that says:
    "
    Your SoundCard Driver cannot Support the Wave Format".

    One of two things maybe wrong:
    • Most likely AGWPE is configured to use a device other than a sound card, most commonly, a telephone modem. To fix this, go to the Sound Card Modem /TNC Setup window, and select a sound card in the Sound Card Selection field.
    • Your sound card driver really can not support the wave format. Make sure you have the most recent version of the driver for your version of Windows.

  • AGWPE tries to start but then a "Copyright Violation" box appears. I click "OK", but the program then closes.

    The AGWPE.SYS file is missing from your AGWPE folder. You can reinstall the entire program from the zip file or just the AGWPE.SYS file. (The AGWPE.SYS file has the date of the program, so don't use the AGWPE.SYS file from another version. It will display the wrong version date when you start the program.)

  • AGWPE starts and runs but first I get a message that says:
    "
    AGWTCPIP.SYS Not Found! TCPIP Over Radio will be IDLE!"

    You have turned on AGWPE's special "TCP/IP Over Radio" (TOR) feature but have not installed the special TOR software adapter. If you really meant to use this feature, see the TOR pages on this web site for information about installing the adapter. Most people do not need or use this feature. It is NOT needed for normal packet functions or to interface with your applications (applications use the TCP/IP Application Interface to connect to AGWPE, not TCP/IP Over Radio).

    To turn TOR off and stop the message, go to the AGWPE menu (click on the AGWPE tower icon) and select TCP/IP Over Radio Setup. In the resulting window select "Thank's NO TCP/IP".
  • I can run AGWPE and my packet program on my laptop for about 30 (or 15 or 60) minutes and then it just crashes.

    Turn off the computer's energy saving mode.
  • When I drag my mouse over AGWPE's modems icon in the system tray, a message pops up telling me how the port is configured and how many frames (packets) I have received and sent. But even when I haven't sent any frames, as time goes on, AGWPE says that I have been sending more and more frames. Is that normal?

    It is normal. In its default mode, AGWPE calculates the "best" traffic parameters (slot/persist, resptime, etc.), every 2 minutes and these recalculated values get reported as sent frames even though nothing is actually transmitted by the radio. Don't worry. AGWPE is not keying up your radio and transmitting on its own.
  • AGWPE loads but then my system just freezes. I need to power off to reboot.

    One user said that new sound card drivers fixed the problem.

  • AGWPE starts but then gives a message that "Packet Engine Pro Shuts Down Abnormaly, It Is Strong Recommended to restart your Computer".
    or
    AGWPE is behaving very strangely, particularly my radioport configuration.
    or
    AGWPE won't start and locks my system.

    In the AGWPE folder, delete the AGWPE.ini file and all port?.ini (port0.ini, port1.ini, etc.) files and then restart and reconfigure AGWPE.

    The problem may have developed when you configured a radioport to use a COM or LPT port that was already claimed by another program or device; or the TNC was not plugged into the COM or LPT port; or you may have tried to delete and add a port without restarting the program after deleting one port and trying to add another.
  • I'm running Windows 95 and when I start AGWPE, the AGWPE tower icon appears in the Task Bar *not* the System Tray. If I right click on the icon, I get the usual AGWPE menu, but "Setup Interfaces" does nothing; the popup menu just closes. I can't seem to make AGWPE do anything.
    or
    I fill in the new port information, close the program and restart it, but the port shows "IDLE" and I can't open the
    Properties window for that port by clicking on OK.

    You need to update the Windows "common controls" file, COMCTL32.DLL file. See the Windows update page on this site for the full solution.
  • AGWPE closed and the Packet Engine icon disappeared, but the modem icon remained on the System Tray!

    This may happen if AGWPE is closed down unexpectedly. Usually restarting AGWPE will correct it, although a reboot may be necessary. If AGWPE fails to start (you may get a "Fatal Exception Error" message), go to the AGWPE folder/directory and delete all files ending in .ini; then restart and reconfigure AGWPE.
  • Modem Icon Never Appears: The modem icon won' t appear until you configure an AGWPE port and then closed and restarted AGWPE. If the modem icon doesn't appear then:
    • Double check the properties for the AGWPE port to make sure you have done it correctly. Use the Port Settings information on this site for guidance.
    • Look for possible port conflicts with the PTT port you have selected. See next section:

Port Conflicts

It's possible that some other device is affecting the COM/LPT port you have chosen for PTT control. For example, one user forgot that he had an unused phycial adapter "installed" in Windows that was conflicting with the PTT port. Another user reported a conflict with the Palm HotSync Manager, which loads on startup and puts the COM RTS pin high; Windows didn't report that the COM port was being used by the Palm device driver, but it was. Another user had both the COM port and an infrared port assigned to the same IRQ. Another user suggested that, if your XP machine is running an NVIDIA graphics adapter, some of its drivers are reported to tie up COM1 for no reason -- so disable Nview 2.0.

It may be difficult to identify port conflicts, since AGWPE may start and run despite the conflict, i.e. no error message. Conflicts may arise either from a device, such as a printer, or from a program that uses the same port.

Try this first: temporarily force AGWPE to a port where there CAN'T be a conflict with another program. Reset the Serial or LPT Port in AGWPE's properties window to a non-existent parallel port, perhaps LPT 3 (scroll down past all the COM options to the LPT options).

If AGWPE now receives packets and your other program now works, then you know you did indeed have a port conflict. Fix the conflict (see below) and then change the AGWPE PTT port settings back to a real port, i.e. not the non-existent one.

To search for a device that might be causing the problem, first go to the Start menu and then Settings: Control Panel: System. On the "Device Manager tab, select "View devices by Connection" and double click on "Computer". This should tell you which devices are using each IRQ. Look for a conflict with your chosen AGWPE PTT physical port (COMx, LPTx) and some other device.

If there is a device conflict, you'll need to either reset the port used by the conflicting device (could be hard) or tell AGWPE to use a different PTT port (might be easer). To change the port AGWPE uses, move the PTT cable to a different physical COM or LPT port. Then make the corresponding change in the Port Properties in AGWPE.

If only one device is assigned to each COMx and LPTx port "serial port IRQ", then there is no conflicting device, so there is probably a conflicting program which is using the port. Either:

  • reconfigure the conflicting program to use another port
  • just close the offending program before working with AGWPE
  • change the PTT port in AGWPE (see paragraph above).


2. Linking to Client Applications

  • I am having trouble configuring my client application to link to AGWPE.

    There may be instructions in the Help section of your client application; or you can try the Application Setup page on this website.

    If you're having trouble getting a particular application to work with AGWPE, first make sure AGWPE works with AGW Terminal Program. If AGWTerm won't work with AGWPE, then you have a problem with AGWPE that needs to be resolved first.

  • I see the little green pixel flashing on the TNC icon so it appears AGWPE is receiving packets, but the packets don't seem to be getting from AGWPE to my packet program; my program isn't showing any packet activity.
    or
    When I try to run a client application, I get an error message from the client indicating the IP connection was refused.

    Check for these problems:
    • Make sure AGWPE's TCP/IP Application Interface is active: from the AGWPE menu select Setup Interfaces . On the Winsock & HTTP Interface Setup screen; Winsock Interface tab, enable the Winsock TCP/IP Application Interface with a checkmark. Also make sure the TCP field is set 8000.
    • Any application linking to AGWPE with the TCP/IP Application Interface should have a corresponding field to specify AGWPE's TCP port number (8000, by default); see the Application Setup page for advice about selected programs. The application should also have a field to specify the IP Address of the computer where AGWPE is running. That address will be "127.0.0.1" or "localhost" if AGWPE is on the same computer as the application. Read the application's Help section or see AGWPE on a Network for advice when AGWPE is on a different computer.
    • Make sure the application is listening to the correct AGWPE radio ports. The application may be linked to AGWPE but not linked to all of AGWPE's radio ports. For example, some programs, such as UI-View, allow you to block access to specific AGWPE radio ports (UI-View calls it "masking" ). Read the application's Help section or see the Application Setup page for advice about selected programs.
    • Make sure the TCP/IP Protocol is installed on your computer. If you use the internet successfully, then it is. If you don't have either the Window's Dialup adapter or a network card installed on your computer, then the protocol may not be installed. To correct this, just create a Dialup connection (see Windows' Help for advice; you can use a dummy telephone number for the connection).

      If you still have a problem, make sure the "Internet Protocol (TCP/IP)" is installed for the Dialup connection or the network adapter. Normally it is installed by default and active, but it may have been deleted somehow (see the Windows: Enabling the TCP/IP Protocol page for advice).
    • If you have a firewall program and/or router running, turn off the firewall temporarily to see if this fixes the problem. If it does, configure the firewall and/or router so that AGWPE can communicate with other programs via AGWPE's TCP/IP Application Interface port (default is 8000).
    • Try changing the default TCP Port from 8000 to some other number, say 8100. Make the change in both AGWPE and in your client program.
  • My packet program suddenly closed and I got this error message from Windows:

    (The Application) caused an invalid page fault in module WINMM.DLL

You probably have a Windows sound scheme in effect and there was a conflict over use of the sound card. To prevent this from happening, set the Windows' Sound scheme to No Sounds. See the Window Sound Settings page on this site for further advice.

  • I seem to have the AGWPE program working fine. My problem is when I run certain packet programs, such as RXClust or AGWTerm, a box opens saying:

Object Windows Exception

Failure in common control DLL

OK to resume? YES / NO

This is a Windows 95, 98, and ME problem. Do an online search for comctl32.dll to find a download patch for your version of windows.

  • I have two applications sharing an AGWPE sound card radio port. But Application A is not seeing packets sent by Application B and vice versa.

It is a feature of AGWPE that the received frames it sends to an application do not include frames transmitted by other applications using the same instance of AGWPE. So if you have this:

App A --------|
|
AGWPE -------- radio(s) etc.
|
App B --------|

Then, using KISS frames, App A will not see the original frames transmitted by App B.

If you do want App A to see App B's transmission, then a work-round is to configure a loop-back port in AGWPE. Then transmit the beacons from your application(s) to the RF radioport and to the loop-back port, and configure your application(s) to "listen" on both the RF radioport and the loop-back port so they can hear what the other program asked AGWPE to send.

3. Extra Packets Seen

  • If your packet application displays duplicates of every received packet, reasons can be:
    • the second sound card radioport is active in AGWPE even though it is not being used. To correct this, select Single Port (not Dual Port) on the Properties screen
    • you are using a mono plug instead of a stereo plug for the LINE IN jack
  • If your packet application displays packets that are from another frequency:
    • you are probably running two radio ports from the sound card (left and right channels) and audio from one radio port is being heard on the other port. The reason for this is not clear. The best known solution is to reduce the RX audio input on each radioport to the minimum needed to decode packets using the volume control settings.

If your problem is not resolved by the problem solving pages on this website, join the AGWPE Yahoo Group to ask a question or search the archives for previous postings that may relate to your problem

Problems with Receiving

As you troubleshoot receive problems, remember that AGWPE provides you with a some visual aids:

  • The Sound Card Tuning Aid screen is accessible from the AGWPE menu. It can be used to "see" the quality of received signals and, for HF packet particularly, help in tuning the radio to the correct frequency. Go to the Tuning Aid page to see examples of how good and packet signals should look.
  • If AGWPE successfully decodes a packet on a radioport, then the green light on that radioport's modem icon will flash once .

Note: Please make sure you are using the latest version of AGWPE before troubleshooting problems. Your problem may have been fixed in the most recent version of AGWPE!

1. No Sine Wave in Oscilloscope
2. Oscilloscope Activity But No Decoding


1. No Sine Wave in Oscilloscope

Tune to a busy packet channel and select the Sine Wave oscilloscope mode in the Sound Card Tuning Aid. If you do not see sine wave activity, look for a reason at one of five places along the RX audio path:

a. Radio/antenna

First confirm that audio signals -- preferably packets! -- are are being received at the radio. Disconnect the sound card interface temporarily and see if you can hear packets from the radio's speaker and/or see the radio's 'S' bars or the 'Busy" indicator light up.

  • If you don't see or hear packet activity:
    • is the squelch too high? Since AGWPE prefers no squelch for transmitting, it's best to leave the squelch off (even though AGWPE will still receive with the squelch on, providing the squelch is not set too high).
    • is tone squelch (CTCSS and DTSS) turned off?
    • if dual VFOs, is the correct VFO/band selected?
    • is the antenna connected?
    • is the radio tuned to the right frequency?
    • is the mode set for FM and not accidentally in CW, SSB or another mode?
    • can you hear packets by using a different antenna (more gain)? or by moving the antenna to another location (higher, away from possible EMI interference)?
    • can you hear packets using a different radio with a different antenna? with a different radio but the same antenna?
  • If you can't hear packets from the radio's speaker (internal or external):
    • Is the speaker volume knob set too low? Low speaker volume would only affect sound card receiving if your interface's RX cable connects to the radio's external speaker or microphone jack, not a data jack.
    • If your interface's RX audio connects to the radio's external speaker jack, is that radio jack known to work with speakers? Plug in a different speaker or use a meter to test the jack.

b. Radioport settings

Check the following in the Properties settings for the sound card:

  • Make sure you have selected the correct sound card device
  • Make sure you have selected the correct packet baud rate for the radioport channel

c. Volume Control settings

Use the Volume Control screen to check your sound card settings:

· If you happen to have more than one sound card (i.e. mixer device), make sure you are working with Recording settings for the correct sound card. (Program Bug: if you have more than one sound card, AGWPE's Volume Control Screen can be used to set the first card but not a second card. To control the second card, you will need to use the Windows Volume Control Program.)

· Make sure you are working with the Volume Control Recording settings, not the Playback settings.

· Make sure you have selected the correct input jack -- LINE IN or MIC -- where your RX interface cable is attached.

· Make sure the vertical volume sliders for the selected input jack is not at or near the bottom (about 1/3 up is fine). If you see Balance sliders, make sure they are centered.

· If there are still no signals, try selecting the other input source -- Microphone or Line In. You may have the plug in the wrong jack. If this was the problem, move the plug back to the correct jack and reset the input source.

d. RX audio cable

See the RX audio cable page for wiring schematics and other hints.

  • Is the RX cable plugged in completely at the sound card jack? Make sure you haven't used the wrong sound card jack or haven't confused the RX cable with the TX or PTT cable. (Hint: put labels on the ends of all cables.)
    If you are using two sound cards, is the RX cable plugged into the right one?
  • Are you using a stereo jack at the sound card plug? You should use a stereo plug for most sound cards.
  • You can not interface two radios to the sound card using the microphone jack. The Microphone jack on sound cards is not stereo capable, so you will probably only receive audio from the port 1 (left channel) radio. Use the LINE IN jack instead (see Rx audio page).
  • Test the cable:
    • Unplug it from the sound card jack and plugging it into a speaker (if the speaker has a plug and not a jack, use clips leads or an in-line coupler to join the two plugs). If you hear RX audio in the speaker, the RX cable is OK, or
    • Use a multi-meter:
      • test for continuity and short circuits. Check your solder connections if you find a problem.
      • Is the RX audio line wired to the tip of the stereo plug? The ring of the stereo plug should be unwired, unless you are interfacing to two radios. The sleeve should be wired to the sound card ground.
    • Is the RX line securely soldered to the correct pin in the radio plug?
    • If the RX cable has an in-line isolation transformer, make sure it is a 1:1 transformer, unless you are using the radio's external speaker for RX audio. If you are using the external speaker, then you should be using a 1000:8 transformer and the 1000 Ohm primary coil of the transformer should be wired to the sound card side, not the radio side.
  • Try using another cable without a transformer.

e. Sound card or driver

  • Does the sound card work with other Windows' sound generating programs? If not, in the Windows Control Panel under Sounds/Multimedia, make sure the sound card is installed and there are no conflicts with other devices.
  • Sound card suddenly stops working after a few minutes and always about the same number of minutes: This probably a power management issue; your computer or laptop is going into power saving mode and is turning off the sound card.
  • Driver: Make sure you have the latest driver for your version of Windows. You can the latest version from the sound card/chipset manufacturer's website (better source than the computer manufacturer).
  • Card: Some cards may not work with AGWPE even with the correct driver. (Read the section on Compatible Sound Cards on the More About AGWPE page on this site.)

    If the problem appears to be your sound card, consider replacing the card or adding another. New cards are fairly inexpensive or you may find a "used" sound card at a hamfest/computer show or in a discarded computer. PCMCIA and USB sound cards are also available. A second sound card dedicated only to ham programs may actually be very useful. Your first card then be used for Windows and other programs.

Note: If receiving works for a while but then stops, your computer's power management settings may be turning off the sound card.

SignaLink USB Interface user? See the AGWPE-Signalink USB page on this web site for troubleshooting suggestions.


2. Oscilloscope Activity But No Decoding

If AGWPE is receiving signals but is not decoding them, look at these possibilities:

f. "Recording" Volume Settings

AGWPE is very tolerant of RX audio volume levels, but your volume settings may still be too loud or too soft.

· Too soft/muted: try raising the receive volume sliders until you see more deflection (peaks and valleys) in the Tuning Aid's Sine Wave. If the sliders don't change the wave significantly, try turning up the volume at the radio.
If the RX audio from the radio is still too low:

o make sure you are pulling audio from the correct radio pin/plug. Some radios have different RX audio pins/plugs for different modes or packet baud rates. Make sure you are using the one for your packet baud rate. (Example: the Yaesu FT-847 has a Data In/Out stereo plug jack for HF modes and a 6 pin mini-DIN jack for packet. Audio from the HF jack will be too weak for packet. If you buy a sound card interface, you may get only the Data In/Out plug and not the 6-pin mini-DIN plug.)

o remove any attenuation circuit you may have in the RX line

o try plugging the RX audio line into the MIC jack instead of the LINE IN

o install an audio pre-amplifier in the RX line.

· Too loud: If the sine pattern has very thick and tall waves (nearly fill the scope top to bottom), try lowering the volume settings. (If the sliders don't change the wave, try turning down the volume at the radio.)

· MIC input: If you are using Microphone input, note that most sound cards expect a maximum input voltage on the microphone line of about 200 mV, which is much less than most radio's maximum output, e.g. 500 mV. For this reason, you should probably use a voltage attenuation circuit in a microphone RX cable. The ideal attenuation will depend on the sound card's input and radio's output specifications. You can try to use the volume sliders to find an ideal spot, but the setting is likely to be very delicate without the attenuation circuit.

In addition, check that your are not using the Microphone Boost or the 20dB option on our sound card, if available. This option is not found in the AGWPE Volume settings, but it may be found as a button in the Windows' Recording Volume Setting window under the Microphone slider (you may need to use the Option: Advanced menu option to have it display). This option will increase the MIC input by 100 times, which could distort your packet even more.

g. AGWPE Settings

  • Baud Rate: Make sure you have selected the correct packet baud rate in the Sound Card Setup screen
  • Ports: If you are only using one port, set AGWPE for Single Port (not Dual Port) on the Properties screen

h. Poor Signal quality:

  • 1200 baud packet: To successfully decode a packet, you need about an S3 signal at minimum.
  • 9600 baud packet: To successfully decode a packet, you need nearly an S9 signal. (see 9600 Packet Operations on the Baud Rates and Modes page. for additional advice about 9600 baud packet operations.)
  • 300 baud packet (HF SSB): Use the Sound Card Tuning Aid's Waterfall Scope to accurately tune the signal. (see HF Packet Operations on the Baud Rates and Modes page. for additional advice about HF packet operations.
  • Are you tuned to the correct frequency exactly?
  • Is the mode set for FM and not accidentally in CW, SSB or another mode?
  • Do you have tone squelch on? Do you have manual squelch on? Is the radio's squelch set too high and blocking many signals. (The squelch should not be operating when using AGWPE. When it transmits, AGWPE needs to hear the frequency at all times.)
  • Packet collisions -- two or more transmitting stations send packets at the same time, making both unintelligible. This is a common problem on busy frequencies, e.g. APRS. No real solution is available although network members could experiment with traffic reduction and collision avoidance schemes and settings, such as slotting.
  • The other station's packets are too distant, faint, or noisy:
    • Increase your radio knob's volume control if the radio knob controls RX audio volume; or increase your RX Volume Setting for LINE IN (or MIC, if you are using that).
    • Poor radio signal path: You may be experiencing multi-path refraction/ reflection problems (signal waves arriving out of phase) or a Fresnel null (part of the signal wave is blocked) because of the antenna's poor position. Try moving your antenna.
    • Use a better antenna (more height, more gain, more separation from noise or interference sources).
    • Ask the other station to increase power.
    • Ask the other station to try a different antenna or a different antenna location.
    • Consider an antenna feed-line problem at your station if there is any other evidence of weakened signals, e.g. moving the antenna doesn't help and you experience low audio and static on your RX signal compared to the signal someone nearby is receiving.
  • The packets the other station is sending are are poorly formed:
    • The sending station sent the packet without sufficient TX delay. Its radio didn't have sufficient time to power up or switch from receive to transmit. As a result, the beginning of the packet was lost. Ask the sending station to increase TX delay in his station's TNC or sound card.
    • The sending station's TNC or sound card was over-driving the radio (sending packet tones that were too loud) and his radio had to "clip" the signal (reduce the deviation). This results in a poorly formed packets at the receiving end (low tone is louder than high tone). Ask the sending station to reduce his station's TNC drive level.
    • Some radios offer a bass boost function that will distort a packet signal. Make sure the sending station is not using this feature.
  • Are you using the MIC jack on the sound card instead of the LINE In jack? Then you probably should have an attenuation circuit in the RX cable. See the RX audio cable Help page for such a circuit.
  • Note that distorted packet signals simply cannot be decoded. For example, if you have mountains (or tall buildings) near you, then signals may be reflected by the mountains (or buildings) and result in multipath (or phase) errors. You can try using a small beam antenna to overcome the problem. Align the antenna with the boom parallel to the mountains.

i. Interference

Signal interference from EMI, RFI, and ground loops can distort received packet signals so much that they can not be decoded. Radios such as the Yaesu FT-290 are known for being susceptible to computer noise interference. And computer (laptop) noise can get into radios (particularly HTs) and antenna if they are too close to the computer.

  • Power noise: Especially on laptops, noise can enter the sound card from the power supply. Try disconnecting the power supply and run on battery only. If your radio is connected to a poor quality power supply or if it's connected to a battery charged by a poor quality power supply, you may also have problems. See http://www.buxhamparts.com/humsolving.html
  • EMI, electro-magnetic interference, can come from any nearby AC-powered source, such as your monitor. Turn off the monitor temporarily and then turn it on to see if your packet program recorded any signal when it was off. You may be able to reduce EMI if you:
    • change the monitor scan rates or screen size or combinations of both in:
      Windows Desktop > Right Click > Setting Tab > Monitor ----- etc....
    • replace outdated or incorrect monitor driver software
    • place a ferrite snap-on core on the monitor cable, close to the computer and another close to the monitor
    • re-locate either the device or your interface cables
    • use shielded interface cables
    • use ferrite cores (split or toroids) on the interface cables.
    • use shielding on the radiating device
    • move mag-mount or HT antennas away from the computer

  • RFI, radio frequency interference, can be reduced if you:
    • limit the length of your interface cable
    • use interface cables with shielding
    • use ferrite cores (split or toroids) on cables.
  • Ground loops can result when DC current flows between your computer and your radio. Normally, DC current should not flow between the devices, but it will if there is a voltage potential difference between the devices. Unfortunately, a sound card interface can become that link.

    If you have your computer and radio plugged in to a different branch of the AC wiring in your house, you may have problems. Plug your computer in to the same AC outlet strip as your radio, so they share the same electrical ground.

To break the ground loop, you should use isolation transformers on your RX and TX audio cables, plus a phototransistor, or optocoupler, in the PTT line (a simple transistor in the PTT line does not does provide isolation). You must isolate all three connecting cables.

Note that some manufactured interfaces may not provide isolation on all three cables (For example, the West Mountain NOMIC does not provide isolation for a RX cable). You can verify if the interface does by visual inspection: look for a small transformer in audio line circuit; or ask the manufacturer.

I see that Buxcomm now offers a simple add-on audio isolation cable if you don't want to build your own. You simply plug in the Buxcomm isolation cable between your sound card jacks and your audio in and your audio out lines. The item is called a ISOL8R and you can order it for $9.97 ($17.97 for 2) at http://www.buxhamparts.com/humsolving.html

Below are screen shots from the Tuning Aid's Sine Wave scope showing a ground loop:


EMI or RFI on Your Receive Audio Cable?

You can use the Sound Card Tuning Aid to "see" if you have interference or some other problem affecting your RX audio cable. Here is a way to hear it:

  • Temporarily plug your computer speakers into LINE OUT jack of the soundcard.
  • Open AGWPE's Soundcard Volume Settings screen
  • If you can't hear the radio's RX audio in your computer speakers, increase the RX volume sliders'
  • When you do hear RX radio audio, tune to a quiet frequency and lower the RX volume slider to its minimum (you may need to also turn down the radio' speaker volume dial if you get RX audio from the radio's mic or speaker jack. )
  • Now increase the TX Playback volume (WAVE & TX Master) to maximum.
  • You should hear no radio signals or radio noise. If you hear any Hummmmmm or Hissssssss it should be very, very slight. If it very distinct, you probably have a RFI, EMI or ground loop problem with your RX audio cable. Just to be sure, compare the sounds from your computer speakers with the sounds from your radio's speaker to see if the sounds are the same as the radio's (no problem) or unique.

j. Sound Card or Driver

  • You can try adjusting the sound card clock from the Sound Card Modem Setup screen. Sound cards have a reference "clock" that oscillates at approximately 11025 Hz. The exact speed usually varies for each person's sound card. The clock setting in AGWPE can be used to better match AGWPE to the actual sound card clock speed.

All TNCs try to adjust their receiving clock (a software component) to match the bit rate they receive and thus follow the clock changes of the receiving signal. The AGWPE soundcard modem does the same using the soundcard clock. In certain cards, that clock may be very wrong (fast or slow). The clock setting value you can change in AGWPE tries to adjust the sound card clock using software inside AGWPE's modem code. It doesn't change anything in the sound card.

· AGWPE's default clock setting is "4", which is no adjustment. Using trial-and-error, you can try to find a setting that is better. (I do not know in absolute terms how much change in Hz there is for each setting; or even if "2" is slower or or faster than "4".)

· For your experimentation:

    • after you select a new clock setting, you must restart AGWPE. Clock setting changes are NOT immediate.
    • it's best to test reception of a weak station (less than S8)

Interestingly, you may find the perfect setting for some stations may change with the seasons, if the hardware in those stations are outdoors and exposed to heat fluctuations.

  • If AGWPE appears to be receiving good quality packet signals that are not being decoded, then you may have an incompatible sound card. (This seems to be more prevalent with integrated, "on board" sound "cards".)
    See "e." above.

k. Radio Settings

  • If your radio has signal processing settings, turn them off. For example, some Yaesus have a "bass boost" function. Others radios such as the ICOM IC-706MKIIG, have a "DSP" setting. These settings should be turned off/disabled.
  • Make sure you are using the correct RX data output source on the radio. For example, on a Yaesu FT-8500, AGWPE can not decode 1200 bps through the data port , only through the speaker-out jack. The "problem" with the data port is that it has no de-emphasis circuitry and so the packet tones are skewed by at least 6 dB. (To fix that, "You would need to add the right value capacitor." Sorry I can't help much beyond that.)
  • Hand-held radio often have a "battery saver' or "power saver" setting that turns off the radio's receiver circuit for a few seconds or parts of a second. It that setting is on, you may be missing the first part of packets.

If your problem is not resolved by the problem solving pages on this website, join the AGWPE Yahoo Group to ask a question or search the archives for previous postings that may relate to your problem

Problems with Transmitting

As you troubleshoot transmit problems, remember that AGWPE provides you this visual aid:

  • If AGWPE receives a packet transmission request from a client application and then successfully passes that packet to the sound card and radio for transmission, the red light in the transmitting radioport's modem icon will flash once and your radio should transmit.

To Force a Transmission through AGWPE, use the AGWTerminal (TCPIP version) program to send a QRA packet: From AGWTerm tool bar, press the "Tower & Question mark" button, and then select the radioport you want to test.

Note: Please make sure you are using the latest version of AGWPE before troubleshooting problems. Your problem may have been fixed in the most recent version of AGWPE!

1. Radio Doesn't transmit
2. Radio Locks in Transmit mode
3. Intermittent Transmissions
4. No audio or poor audio on transmit

1. Radio Doesn't Transmit

  • A. No Red Light Seen: My application program sent a packet, but I do not see the red light in the AGWPE modem icon indicating it has transmitted the packet to the radio.
    • Make sure the radio's is ON and the squelch is fully open at all times. AGWPE needs to hear the frequency noise level at all times -- no squelching! -- otherwise it may not transmit.
    • Make sure you application program is correctly linked to AGWPE. See the Program Behavior page about Linking to Client Programs.
    • Make sure the application program really is requesting a packet transmission. For example, a terminal program will not send anything if it is linked to AGWPE in COMMAND mode (unless you use the CONNECT or DISCONNECT commands). Try a CONNECT command if you are not yet connected or go to CONVERSE mode (K) if you are connected.


  • B. Red Light is Seen: I saw the red light blink in the AGWPE modem icon, but the radio isn't transmitting.
    • Double check that the PTT cable is connected tightly to the appropriate COM (or LPT) port. Make sure you do not have a loose connection.
    • It may be that the physical COM or LPT port where your PTT cable is connected isn't really the port you think it is: e.g. you think it's COM1, but your mouse or internal modem is on COM1, so your PTT is really plugged into COM2 . Try changing the port for PTT Control in the Port Properties or move the PTT cable to another COM or LPT port.
    • Is there a problem with your PTT cable and circuit? You can test it by using a 9 volt battery to apply voltage to the cable's RTS/DTR pin (in the DB9 or DB25 connector) and then using a voltmeter to test for voltage on the radio end of the cable or, if the cable is connected to the radio, look to see if the radio is transmitting.
    • Your application program may be configured for the wrong AGWPE radioport. If you need instructions for changing the radioport, look in the Help section of the client application; or you can try the Application Setup page.
    • Are you using the parallel port (LPT) for PTT control and running Windows XP or 2000? This can't be done with AGWPE and those versions of Windows. For those versions, your only choice is to purchase Packet Engine Pro. (Windows XP and 2000 use a port addressing scheme that is different than the scheme used in Win 95, 98, and ME, which do let AGWPE use the LPT port for PTT control.) Alternatively, you can use the following PTT signaling methods instead of the LPT if you have Windows XP/2000:
      • use a serial (COM) port
      • use a USB port by obtaining a USB-to-Serial Port (COM) adapter
      • use a TX audio tone keyer that uses detected audio to trip the PTT circuit

These are all described on the PTT cable page.

    • Are you using the parallel port (LPT) with Windows 98SE/ ME? It should work but, if it doesn't, some users have success configuring the LPT1 port to a "legacy" I/O address, i.e. IRQ 7 and address 0378-037F. To do this, go into Settings, Control Panel, System, Device Manager, Ports, Printer Port and select the Resources tab. Configure manually to the above settings and reboot. Check that there are no conflicts with other devices.
    • Is your PTT cable wired to the correct pin at the computer's RS-232 port (COM or LPT)? AGWPE sends the PTT signal to the RTS pin only if you have chosen Single Port in the Port Properties window. It does not also send it to the DTR pin, as some other sound card programs do or as earlier versions of AGWPE did. If AGWPE is set for Dual Port then the radioport 1 radio (left channel ) will use the RTS pin, while radioport 2 (right channel) will use the DTR. See the PTT Cable page for wiring schematics. Possibly so some manufactured interfaces may have wired the PTT cable to the DTR pin only and not the RTS.
    • SignaLink USB Interface user? See the AGWPE-Signalink USB page on this web site for troubleshooting suggestions.
    • Occasionally there is a problem with the physical port. You can use a voltmeter to test the COM/LPT port pin. There should be DC voltage on the pin when the red pixel in the AGWPE modem icon lights.

      Note: When Windows boots, it tests all COM and LPT ports by momentarily putting a signal on the port pins (Windows XP does it 5 times). If you have your PTT cable connected and your radio "on" when Windows boots, then the radio PTT will activate for a few short bursts during the boot sequence. This is a good indication that your PTT cable is working correctly.

COM Port Problem?

Although I haven't heard of this happening with sound card interfaces or AGWPE, I have heard that TNCs and GPS units attached to a COM port can pose problems for Windows and your ability to use that COM port for packet programs.

During the boot up process, Windows will automatically try to determine what device is attached to every COM port if finds. For example, if it finds a TNC or GPS on COM1, it may incorrectly identify that device as a "Ballpoint" track ball mouse, reserve it for that (non-existent) mouse and prevent other programs, such as packet programs, from using COM1.

Booting up without the sound card interface/ TNC / GPS attached to the COM port may be one way to avoid this problem. (Another, more radical but still temporary fix is to use Windows' Device Manager to delete the COM port, turn off the computer, and disconnect the device from the COM port. When you restart the computer, Windows will re-discover the empty COM port and not reserve it for a particular use. You can then re-attach your device to the COM port and use it for your packet programs.)

But a better, more permanent solution to this problem is to run Microsoft's free COMdisable utility. Contrary to it's name, this Microsoft utility does not disable COM ports or even disable the boot-up detection of COM ports. Rather, it prevents Windows' from trying to identify what devices are connected to COM ports and reserving ports unnecessarily. You need run COMdisable only once; Windows will remember your preferences. After you run COMdisable, you then will be able to leave your TNC/GPS/sound card interface attached to your preferred COM port when you boot up.

You can get COMdisable at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;819036

Thanks to Stephen WA8LMF for this tip. He also keeps a copy of COMdisable on his site: http://wa8lmf.net/aprs/GPS_Mouse.htm

o

    • Many new transceivers, e.g. Yaesu 8100, won't transmit if the TX audio level is too high. Use the Volume Settings screen to lower the TX Master and/or TX Wave volume. Or adjust the potentiometer on the line, if thre is one.
    • Some radios may use different TX audio pins for HF and VHF/UHF. The ICOM 706 is one. Consult your radio's user manual for pin out instructions. This can be the solution if your interface works correctly for HF digital modes such as PSK31, but won't work for VHF/UHF packet, or vice versa.
    • If AGWPE seems to run fine for a set time (15, 30 minutes) and then stops transmitting, your computer's power management scheme may be turning off the COM/LPT port that controls PTT.
    • I'm using a commercial sound card interface (in this case a RASCAL GLX). I can transmit once, but I can't transmit again unless I reboot. I'm running Win2k Pro, SP4 (but may be a problem with other Windows versions).

      Many commercial interfaces are wired to allow PTT control by either the RTS or DTR line of the COM port. It may be that a small amount of negative voltage (-V) on the DRT line was canceling the positive voltage +V on RTS line.

To fix this, you will need to disconnect the wire in the interface that connects the DTR line to the PTT circuit. Use just the RTS line for AGWPE in single port mode.

2. Radio Locks in Transmit mode

  • First try closing and restarting the packet application and AGWPE; or try rebooting.
  • If you are using a hand held radio:
    • Remember that, in addition to the usual PTT circuit components, you will still need all the PTT components recommended by the radio manufacturer for MIC and Speaker jack data use. Many handhelds need a capacitor on the TX audio line between the radio and the PTT gate circuit (as well as a resistor on the PTT line). Without that capacitor, the PTT circuit may be active at all times.
    • If the manufacturer says to use a stereo plug for the radio's MIC jack, don't use a mono plug!
  • You may have a wiring problem in the PTT cable. Double check the wiring, components, and circuit routing:
    • the PTT line from the radio must not touch the shield or ground before it gets to the transistor or optocoupler.
    • the PTT line must be wired to the correct pin on the transistor or optocoupler. See PTT Cable for a schematic. If the PTT closes when AGWPE transmits, then you most likely have the transistor or optocoupler wiring inverted. (You can test your cable and circuit by using a 9 volt battery to simulate the computer RTS line: plug the PTT cable into the radio and on the computer end of the cable, apply the positive side of the battery to the #7 pin (RTS ) pin and the negative side to the #5 pin (Ground). This should close the transistor/optocoupler gate and the radio should transmit.)
  • Windows can start up leaving the COM port handshaking lines "high" (with voltage) instead of "low" as it should. This seems to be limited to ound card interfaces that are wired to use the DTR line to key the transmitter (many commercial interfaces are wired to use either the RTS or DTR line for PTT keying). This has been reported happening with Windows ME and XP; also in other versions of Windows when using a USB-to-Serial Port Adapter.

    For Windows ME: Look first on the Microsoft web site for a Windows fix; see http://support.microsoft.com/default.aspx?scid=kb;en-us;285894 ).

Or Roger Barker, G4IDE/SK, wrote a free 20 kb utility, HSOFF, that can be used to reset the handshaking lines of a COM port if they are left "high". HSOFF come in a zip file that includes a .TXT file of instructions. (Note that the program needs the Microsoft runtime libraries MSVBVM60.DLL and MSCOMM32.OCX to run. These libraries are installed if you install UI-View32; and they are also available at some web sites -- do a web search to find them.)

For Windows XP: Although I couldn't find verification of this problem on the Microsoft web site, it have been said that when Windows XP boots up, it too may leave the DTR (Data Terminal Ready) line of the serial port in a HIGH state. The supposed fix for this is problem is to go to the Device Manager within Windows XP and remove all of the Communication Ports, or COM ports, as listed under "Ports (COM & LPT)". After doing that, re-boot Windows XP and it will re-install all of the drivers for these ports.

  • It's possible that some other device is affecting the COM/LPT port you have chosen for PTT control. For example, one user forgot that he had an unused adapter "installed" in Windows that was conflicting with the PTT port. Another user reported a conflict with the Palm HotSync Manager, which loads on startup and puts the COM RTS pin high; Windows didn't report that the COM port was being used by the Palm device driver, but it was. Still another user had both the COM port and an infrared port assigned to the same IRQ. Another user suggested that, if your XP machine is running an NVIDIA graphics adapter, some of its drivers are reported to tie up COM1 for no reason -- so disable Nview 2.0.
  • Try disabling the Full Duplex mode of the card. On the Sound Card Setup screen, un- check Full Duplex.
  • On older/slower computers, the default sound card sampling rate may be too high for the computer to process. You can try using the Windows Control Panel to adjust the soundcard hardware acceleration and sample rate quality until you find an optimum setting (For example, in Windows XP, you get there by clicking on Sound and Audio Devices, then click on the Audio tab. Under Sound Playback, click on the Advanced button then click on the Performance tab.)

3. Intermittent Transmissions

  • Sometimes AGWPE will not transmit immediately if AGWPE's automatic timing features are in effect. AGWPE monitors the frequency and uses "slotting" to send your packet when the frequency is not likely to be busy. So, AGWPE is holding the packet for a few seconds before transmitting it.

    If this delay really bothers you, you can override this feature by setting the timing parameters yourself. Call up the Properties screen for the radioport, click on the the Tnc Commands tab, select Let me Control Parameters. , and then change the Persist and Slot parameters. But remember that AGWPE usually does a very good job of adjusting the timing to match traffic conditions on the frequency. You may make matters worse by controlling them yourself. For example, you may not be as prompt to change parameters when frequency traffic changes.

    Another reason for a transmit delay is if the sound card is busy processing other sounds from Windows or your application programs. For example, UI-View has an option to announce received callsigns and this slows everything down. Usually there is an option to turn these sounds off in the application, as there is for Windows' sound schemes.
  • Problem: I can send and receive a few packets, but pretty soon transmitting stops, especially if I try to send packets too rapidly. This clears up if I close and restart AGWPE and the packet application, but it just happens again.
    *
    Solution: This seems to happen mostly on computers with older processors. It's possible your computer isn't keeping up with the quick switching that is taking place between the sound card and AGWPE. The computer may have missed a "hand shaking" data segment from AGWPE, so it's waiting for a signal from AGWPE that will never come again. This may mean you need a faster processor or perhaps a sound card driver upgrade to run AGWPE, although you can try to cut the processor load by shutting down other programs and background tasks. Also, see the paragraph above about interruptions of the packet stream.
  • Note: If transmitting works for a while but then stops, your computer's power management settings may be turning off the sound card and/or the serial ports.

4. No audio or poor audio on Transmit

How does my transmit audio sound?

The surest test of your transmitted audio is to use a second radio to listen to the audio transmitted by your first radio. A hand held radio is great for this. Or ask a nearby friend to listen. You should be hearing packets signals from your station that sound similar to the packets you hear from other stations (although perhaps a bit louder and with less noise).

Remember that your audio signal must pass through four ( 4 ) devices that could modify it:

  • the sound card's mixer,
  • the interface cable,
  • the radio and
  • your transmission system, i.e. antenna and feed line.

For example, you can test the audio coming from the sound card mixer by temporarily putting your computer speakers back into the LINE OUT jack. This will give you a fairly good indication of whether you have good volume level settings, but it isn't how your final audio will sound.

Your interface's TX cable has an attenuation circuit or potentiometer that could reduce the audio significantly -- or maybe not enough. As a result, your radio may be receiving audio that is too weak or too loud.

Even your radio may have audio modification circuits in it. Some VHF radios have a "bass boost" option (should be off), and HF radios have speech compression settings (should be off), drive settings (should be turned all the way up) and microphone gain settings (should be left at normal).

And of course your transmission system -- feed line and antenna -- could attenuate your signals.

So the best way to test your audio is to listen to how it sounds on another radio.

If you might have a problem with your TX audio:

  • Re-check AGWPE's volume settings for Playback (TX audio). Make sure the TX Master and TX Wave settings are not muted and that none of the four sliders is too close to the bottom of the scale (remember that sliders 1 and 3 control the transmit audio for radioport 1, while sliders 2 and 4 control audio for radioport 2).
  • The attenuation circuit in your TX cable may be over/under attenuating your TX audio. If you have a variable resistor (pot) in the attenuation circuit, try adjusting it.

Adjusting Your Transmit Audio Level

With TNCs and sound cards you want a transmit audio level that is decodable but not too high. One of the biggest reasons for poor packet performance is too much audio. If you do not have access to a deviation meter to set the level (you want about 3 KHz of deviation), use a local digipeater and "trial-and-error" to get the lowest audio level that works reliably.

Use a program that can send unconnected packets or a beacon (AGWTerm can send a beacon; UISS can send unconnected packets). Set the beacon PATH to relay through the digipeater (e.g. TEST VIA LOCALDIGI), then go into converse mode and transmit a single carriage return. Watch to see if your single packet gets digipeated by that one local digipeater. If it doesn't get through, try several more times because it may not have gotten through because of a collision.

If it does get through, turn down the transmit audio level a little and try again. Keep turning down the audio until your packet reliable DOES NOT get digipeated ... and then turn it back up just a little bit until it does once again.

Remember, in packet, soft is better than loud.

  • Are the TX Audio cables connected tightly to the LINEOUT jack on the sound card of a desktop computer (or the headphones jack on a laptop?)
  • Make sure you are using a stereo plug (has 2 bands below the tip) for the LINE OUT (TX audio) jack. If you use a mono cable (has 1 band below the tip) you may get only half the audio volume on transmit or you may even short out one channel of the sound card.
  • Re-check the soldering and component placement in the TX cable.
  • EMI or RFI: The strong magnetic fields in your monitor may be distorting the signal, or there may be electro-magnetic interference (EMI) from your computer or other nearby devices, or there may be radio frequency interference (FRFI):
    • Use a shielded audio cable. Connect the shield to either the sound card ground or the radio's ground but not both.
    • Try using ferrite chokes on the audio cable
    • If you antenna is near your computer, move it further away
  • If you have unusual sounds in your transmitted audio or experience delays before AGWPE transmits a packet, it may be that your sound card is getting input from sources other than AGWPE:
    • Turn off any sound schemes for Windows.
    • Turn off any sounds that might be generated by your packet applications, for example voice announcements in UI-View.
  • Some radios offer a bass boost function that will distort a packet signal. Make sure you are not using this feature.
  • HF: Speech compression should probably be off for digital modes and the Drive adjustment should be turned all the way up (use the Volume settings to control transmit power output). Microphone Gain should be set to normal.
  • If you hear interruptions, or stuttering, of the packet stream, it may be because:
    • your sound card is not fully capable of full duplex operations (sending and receiving). This is mostly a factor on older 16-bit sound cards. To turn off Full Duplex, go to the AGWPE Port properties' Sound Card Setup screen and uncheck the Full Duplex box.
    • your computer/or driver is not fast enough. In that case, set the Port Properties for Single Port use and use only the left channel. Also, set your VGA card accelerator a click below full level and adjust the soundcard hardware acceleration and sample rate quality until you find an optimum setting (these sound card settings are made through the Window Control Panel. For example, in Windows XP, you get there by clicking on Sound and Audio Devices, then click on the Audio tab. Under Sound Playback, click on the Advanced button then click on the Performance tab.)

Listen! ---> Sample Wav files: one with no stuttering in packet and one with stuttering.

  • If you hear other noises mixed in with your packets, our sound card is getting input from sources other than AGWPE, such as you CD player or another application:

If your problem is not resolved by the problem solving pages on this website, join the AGWPE Yahoo Group to ask a question or search the archives for previous postings that may relate to your problem

Problems with Packet Connections

A. Connections not made
B. Connections not maintained
C. Slow Exchanges

D. Diagnosing Exchange Problems by Packet Type

A. Connections not made

First, make sure you don't have an underlying problem receiving or transmitting.

  • I can see on my radio that the PTT has been opened and the radio is transmitting, but I can't connect with another station.
  • It looks like the other station heard my connections request and is responding since the radio is receiving packets, but AGWPE is not decoding the packets.
  • I'm having difficulty connecting at 9600 baud.

    Read the 9600 baud section of the Baud Rates and Modes page for a discussion of the difficulties or operating 9600 baud packet. Problems could be: your radio is not 9600 capable without modification; incorrect radio settings; using audio transformers in the audio cables; and poor signal quality.
  • I having difficulty connecting on HF at 300 baud.

    Use the Sound Card Tuning Aid to help tune your radio to the correct frequency. Also read the 300 baud section of the Baud Rates and Modes page for a discussion of the difficulties or operating 300 baud packet.

B. Connections not maintained

  • When I connect, the other station (a BBS) immediately disconnects me.

    You probably have Dual Port selected in the port properties screen and probably have the same baud selected for both ports. Try changing the second port's baud rate to something other than the first. Better yet, if you are not using the second port, select Single Port, close AGWPE, delete the port1.ini file from the AGWPE folder (retain port0.ini, do not delete it) and restart AGWPE.

    If you are using the second port (to run two different radios from the same sound card) and want to use the same baud rate on both channels, the only know solution is to reduce the receive (RX) audio volume in both channels to the minimum needed to decode packets reliably (find this setting through trial-and-error.) You can do this with the volume control recording sliders, but it may help to reduce the volume using a voltage attenuator circuit in the RX audio line; or if you are pulling the audio from the radio's speaker jack, turn down the radio's volume control.

    What seems to be happening is that there is not adequate audio channel separation, i.e. cross-talk, in the sound card, so AGWPE hears both radio ports. In the scenario above, port 1 asks for a connection and the BBS sends a connect confirmation. Because of cross-talk, AGWPE hears this on both port 1 and 2. Realizing this is problem, AGWPE sends a disconnect request, which the BBS accepts and that is the message you see.
  • I can send and receive a few packets, but pretty soon transmitting stops, especially if I try to send packets too rapidly. This clears up if I close and restart AGWPE and my packet application, but then it just happens again.

    It may be that your computer isn't keeping up with the quick switching that is taking place between the sound card and AGWPE. The computer may have missed a "hand shaking" data segment from AGWPE, so it's waiting for a signal from AGWPE that will never come again. This may mean you need a faster processor (or perhaps a sound card driver upgrade) to run AGWPE, although you can try to cut the processor load by shutting down other programs and background tasks.
    (George, SV2AGW, talks about this problem on his web site.)

C. Slow Exchanges

  • The other station doesn't seem to hear all my transmission, so my station is sending many repeats.

    Try disabling the Full Duplex mode of the card. On the Sound Card Setup screen, un-check Full Duplex. Some sound cards (usually older ones) have only one 16-bit and one 8-bit channel, so they can not handle both receive and transmit (i.e. full duplex) at 16-bit rates. They compensate by moving one function -- usually transmit -- to the 8-bit channel where the audio signal is not as good. By un-checking Full Duplex, you force the card to alternate between receive and transmit, but it will always use the 16-bit channel.

Is Your Sound Card Full Duplex Capable?

Can your sound card send and receive simultaneously? In Windows, you can test for full-duplex capability by launching two copies of Sound Recorder.

You'll find Sound Recorder from the Start button: Programs > Accessories > Entertainment > Sound recorder

Repeat the process in the above sentence to launch two copies of the Sound Recorder. You can test for full duplex by playing a file on one Windows Sound Recorder and, while that file is playing, making a recording with the Sound Recorder.

Another way to test is with an AGWPE debugging log. AGWPE asks soundcard drivers if they have Full Duplex capabilities. To see the results of this query:

  • Open the agwpe.ini file in Notepad and edit the file to add these lines:
    [DEBUG]
    TRACE=3
  • When AGWPE restarts it will create an agwpe.log file. If you open that file with noted pad, you should find a SOUND CARD: FULLDUPLEX line that says either YES or NO, which is the result of AGWPE's query of the card.

D. Diagnosing Exchange Problems by Packet Type

The following suggestions are based on observations which can be made by running AGWTerm: (download from the AGW Programs page on this site).

When you use AGWTerm to make a connection with another station, you can monitor ALL packets in the exchange by selecting Window: Unproto Channel from the AGWTerm menu. This will let you see supervisory packets not normally seen in AGWTerm's "receive" window. The type of packet -- SABM, UA, I, RR, REJ -- is identified immediately after the target or VIA station's callsign in the packet, for example here is an RR packet: 1:Fm KC2RLM To SV2AGW <RR P/F R1 >

Remember to leave the Unproto channel window and switch back to the the Channel 1 window to resume your exchange with the other station. You can not send from the Unproto channel window.

  • I'm receiving many REJ packets.

    Increase your TXDelay parameter on the TNC commands tab of the Properties for Portx screen.
  • I'm sending many REJ packets.

    Ask the other station to increase his TXDelay.
  • I'm seeing a RR packet from the other station, then a RR packet from my station, and then this repeats again and again.

    The other station is not hearing your acknowledgement of a packet it just sent you. Increase you transmitted audio (Wave "playback" in the sound card volume control) or improve you transmitted signal (higher power, better antenna).
  • I'm receiving many RR packets in the same transmission.

    Increase your FRACK parameter on the TNC commands tab of the Properties for Portx screen. Consider letting AGWPE resume controlling the parameter.

  • I'm sending many RR packets (R1, R2, R3, etc.) in the same transmission.

    Increase your RESPTIME parameter on the TNC commands tab of the Properties for Portx screen . Consider letting AGWPE resume controlling the parameter.

  • After receiving a burst of data, AGWPE usually responds, for example, with "RR R3", "RR R4", "RR R5", all in ONE burst. But with this one BBS, AGWPE frequently responds with a short break between "RR R3" and "RR R4". During the break, AGWPE releases the PTT and that results in the BBS sending more data. This new data causes a collision with AGWPE's transmission of "RR R4", and the whole packet exchange slows down dramatically. Why does AGWPE insert that break?

This problem usually results when the sender -- the BBS in this case -- isn't using the AX.25 ver. 2 protocol and has a PACLEN of less than 255 characters. This creates a timing problem in the acknowledgement of packets.

Since you are seeing multiple "RR"s, this means you are probably setting the timing parameters yourself and not letting AGWPE control the timing (AGWPE would probably only send one "RR"). Increase the value of the RespTime until the problem goes away. Or select let the AGWPE "program adjust parameters"


If your problem is not resolved by the problem solving pages on this website, join the AGWPE Yahoo Group to ask a question or search the archives for previous postings that may relate to your problem


OK, you ask, "Now that I can get some packet racket into my computer and decode it, what's next?"

Check out some local Bulletin Boards (BBS’s)
145.010 for SEA -- just Connect SEA or C SEA and type H for a list of commands such as BBS or NODES or MH for a list of monitored calls from this machine
Do some DX Cluster monitoring for distant stations to work:
145.73 for K7PKT, or via SEA to one of the K7EK clusters
Connect to the EOC and drop off an emergency message:
W7acs-3 w7acs-10 or any of the WINLINK stations below (for our region, roughly north to south):
Edmonds, WA7AUX-10, 145.050 1200baud
Woodinville, KD6GKD-4, 145.670, 1200baud
Duval, K7DV-10, freq?
Bellevue, W7EFR-4, 144.950, 1200baud
Sammamish, W7SRG-5, 144.950, 1200baud
Seattle ACS, not currently on map...?
Vashon, W7VMI-11, 445.075, 9600baud
Federal Way, WA7FW-10, 144.930 1200baud
Maple Valley, NS7C-10, 145.030, 1200baud
Maple BValley, KC7KEY-10, 145.030, 1200baud
Tacoma, W7DK-4, 144.910, 1200baud
Puyallup, AA7ZV-10, 145.630, 1200baud

This system is subject to relentless improvement, please check out
http://www.winlink.org/RMSPacketPositions
for current resource availability


Check out all the things you can do with the Automatic Position Reporting System - "APE-Errs" or A.P.R.S...
http://aprs.fi/?call=wr5j&mt=m&z=11&timerange=3600
http://www.nwaprs.info/
http://www.aprs.net/


Setup your own bulletin board, gateway or node


Try out HF Packet

Connect to the International Space Station or the Shuttle:
Check out http://spaceflight.nasa.gov/station/reference/radio/
and
http://www.issfanclub.com/taxonomy/term/43
and maybe some tracking software like Jtrack or Satscape
http://science.nasa.gov/RealTime/jtrack/
http://www.satscape.co.uk/main/satscape.php


Try sending TCP/IP data encapsulated in AX.25 packets:
http://www.wetnet.net/node/759
http://www.microhams.com/binfile/talks/200011.ppt
add: Bob at Boeing 9.6 and Vashon group link...

Next week - more of the same with APRS and Airmail

vy 73 de WR5J - Curt
black@nwfirst.com

No comments: