Introduction
    AGWPE Overview
    More about AGWPE
1. Interface
    Getting Started
    Kits and Pre-assembled
    Receive Audio Cable
    Transmit Audio Cable
    PTT (TX Control) Cable
    2 Radio Modification
2. AGWPE Set Up
    Download and Install
    Basic AGWPE Setup
    2 Radio Setup
    2 Card Setup
3. Sound Card Setup
    Basic Settings
    Additional Settings
    Tuning Aid
4. Windows™ Setup
    TCP/IP Settings
    Update Windows
5. Problems?
    Program Behavior
    Receiving
    Transmitting
    Connections
6. Using AGWPE
    AGWPE on a Network
    Baud Rates & Modes
    Remote Control
    TCP/IP Over Radio
    Tips and Tricks
    Traffic Parameters
7. Compatible Programs:
    Setup Help
    UI-View
    WinAPRS
    Winpack
    Others
  
   

Tips and Tricks

Use Selective Packet Routing
Launch AGWPE-Dependent Applications Automatically
Use Alternate Languages
Use GMT Time
Use Alternate AGWPE Configurations
Override AGWPE's Traffic Parameters
Decipher Packet Headers
Use a Loopback Port
Build a Watchdog Timer

• Selective Packet Routing: For some of the AGWsoft client programs, such as AGWTerm or AGWDXCluster, the callsign and SSID you use in the program will be noted by AGWPE. If you use different SSIDs in each program, then AGWPE can route packets to the proper program.
  
  As an example, let's say that you are running both a BBS program with a callsign of SV2AGW-1 and a DX Cluster program with a callsign of SV2AGW-12. AGWPE will know that packets to SV2AGW-1 must be directed to the BBS program and packets to SV2AGW-12 must be directed to the DX Cluster program. Neither program gets packets intended for the other.
   
• Launch AGWPE-Dependent Applications Automatically: Use AGWPE's auto start feature to automatically load application programs or utilities as soon as AGWPE is finished loading. For example, if you mostly use UI-View with AGWPE, you could add UI-View as an auto start client. Then when you start AGWPE, UI-View will launch immediately, too.  The auto start feature is found on the AGWPE menu under Startup Programs. Configure the StartUp Programs window to start the applications you want.
  
   

  Some users find that they need to include more of a delay when starting programs. Jim KB9MMC uses this solution: "I use a program called Autostart Delayer. It's a free program, and it works well. I have it set so that the AGWPE starts first, then Autostart Delayer waits about 5 seconds to start up my other programs that run off of AGWPE (Telpac, Sally UI-View). You can find the program at:  http://www.r2.com.au/software.php?page=2&cat=5&catname=Network

   

• Use Alternate Languages: AGWPE has language support for many languages other than English (the default). The alternate language files were created by other AGWPE users and they are included within the main AGWPE zip file, e.g. french.zip. (If you want to create an alternate language file for your language, see the instructions in AGWPE's Help file ( Help > Index> Multilingual Support.)
  
  Note: Not all words in the AGWPE menus and dialog boxes will translate.
  
  To use an alternate language file:
   
  • 1. Unzip the language file of your choice, e.g. French.zip, into the AGWPE folder. The three unzipped files of importance that will appear are files ending in " .lng", ".hlp" and " .cnt".  So if you unzip the French.zip file you should see these new files: 1036.lng, agwpe_f.hlp, and agwpe_f.cnt (the .lng file has menu and dialog translations, the .hlp file is the translation of the AGWPE 'Help" file, and the .cnt file is the table of contents for the help file).
     
  • 2. Open the agwpe.ini file in the AGWPE folder. You should see a line with Windows' language code number, e.g.
    
        LANGUAGE=1036
    
    This is the code for the language you selected when you installed Windows (1032=Greek, 1033=English, 1036=French, 1044=Norwegian, etc.) You you can not edit this number in AGWPE.ini since AGWPE is programmed to get it from Windows.
     
  • 3. When AGWPE starts, it looks to see if there is a .lng  file that matches this language code. If the Windows language code is 1036 (French) and AGWPE finds a 1036.lng file (French) in the AGWPE folder, it will load the French language files. Otherwise, AGWPE will use the default language of English.
     
  • 4. If you want to use a language in AGWPE that is different from the default Windows language, you will need to rename the AGWPE language files to match the default Windows language code. Let us assume 1033 (English) is the Windows language code and 1036 (French) is our desired language in AGWPE:

  • First, rename the desired "  .lng" file, e.g. 1036.lng (French) to match the Windows' language code specified in the agwpe.ini file, i.e. 1033 (English). So, to install the French files on an English machine -- we would rename 1036.lng to be 1033.lng.
  • Then rename the "  .hlp" file you unzipped, e.g. agwpe_f.hlp, to be agwpe.hlp
  • Finally, rename the "  .cnt" file you unzipped, e.g. agwpe_f.cnt, to be agwpe.cnt

  • 5. When you restart AGWPE, it will use the replacement language files.
    
     
• Use GMT time: AGWPE can use either Local (Computer) time or GMT (Greenwich Mean Time or UTC ) in reporting packets received. To change the time zone, you will need to edit the AGWPE.ini file: under the [TNC] section, add either GMT=1 for the GMT time stamp or GMT=0 (the default) for a local time stamp. If there is no entry, then it uses local time. Example of GMT time setting:

[TNC]
GMT=1

• Use Alternate AGWPE Configurations: There may be times when you want to start AGWPE in a specific configuration, say for  different TNCs or to auto start different programs. The easiest way to do this is to create duplicate AGWPE folders. Each folder will have the full program but different AGWPE configuration ".ini" files. Then use shortcuts that point to the AGWPE programs in the different folders. Use shortcut names that describe the configuration files, for example, "AGWPE PacLink" or "AGWPE ICOM 706" or "AGWPE Loopback".
   
• Override AGWPE's Traffic Parameters: Note that AGWPE automatically monitors frequency traffic and can adjust TNC timing parameters to match that traffic level. You can override this feature  (see TNC parameters screen) but generally it would be to your advantage to use this feature, since it relieves you of the chore of determining and implementing the best timing parameters.
   
• Decipher Packet Headers: If you really want to understand what is happening when you make a connection to another station, you need to be able to interpret the header information in the packets being exchanged. AGWTerm and AGWMonitor and other programs let you see them. The Deciphering Packet Header page on this website will help you interpret and understand them.
   
• Use a Loop Back Port: For off-air testing of two programs, create a loop back port. For instance, you could run both  AGWTerminal and WinPack and use the loop back port to "connect" WinPack to AGWTerm.
  
  To create a loop back port: from the AGWPE menu, select Properties, then New Port. In the new port's Properties for Portx screen, select a TNC Type of LoopBack Port.  Now connect both of your applications to that same AGWPE radio port and they can communicate with each other without going on the air.
  
  Example: Say your loop back port is on AGWPE radio port #3. Start AGWTerm and WinPack, but make sure they are using different callsigns, e.g. KC2RLM-6 and KC2RLM-7. Then, on WinPack's command line enter this connection request: "C  3 XXXX" ,  where "3" is the loop back port and  XXXX is the callsign you are using in the AGWTerm program. The two programs should now be connected to each other via the loop back port.
   
• Build a Watchdog Timer: Most TNCs have a timer that prevents continuous transmission in the event of some TNC or software failure. Typically such a watchdog timer stops transmission that last more than 2 or 3 minutes. With AGWPE's sound card, you don't have such a timer, so here is a page describing how to build a watchdog timer circuit for your PTT cable.