Sound Card Packet































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
8. Packet Reference
   
Overview
    Exchange Modes
    Frame Headers
    TNCs and AGWPE
    What to do with Packet
    Common Frequencies
    Sound Card Mechanics
    Further Reading     
  
   

 

 

Remote Control of AGWPE with Your Web Browser

George SV2AGW has started to develop a web browser interface for AGWPE which lets you access AGWPE over a LAN or the internet. Using your browser (Internet Explorer, Opera, or Netscape), you can:

  • change some AGWPE settings
  • see radio channel activity

Here's how you do it:

  • 1. First, make sure that you have an http folder (with files) in your main AGWPE folder. This should have been created when you installed AGWPE.


     
  • 2. Second, start AGWPE. Then call up the AGWPE menu and select Setup Interfaces. This brings up the Winsock and HTTP Interface Setup window.
    • Make sure the Enable Winsock TCP/IP Application Interface is checked.
    • Then click on the HTTP Interface tab (see picture below).
    • Checkmark Enable the HTTP Interface.
    • Note the port number. The default of 80 should be fine. You would only need to change it if some other server or program in your computer was using port 80 and that would be unusual (for example, port 80 is normally the default TCP port for web browsers).
    • Optional: Under Password, either leave the LOGIN and PASSWORD name defaults or enter new words of your choice. Use of a LOGIN name and PASSWORD are suggested in order to prevent others from changing your AGWPE settings.
    • Press the OK button to save the changes.

    picture of HTTP interface window

     

  • 3. Call up the AGWPE pop-up window again and this time select Launch IBrowser;  or with AGWPE running, launch your Internet browser.
    • If you are working from a remote computer, in the browser's address bar enter the IP address of the computer running AGWPE
    • If you are working from the same computer where AGWPE is running, enter http://127.0.0.1:80 or http://localhost:80).

      Possible Problem:  127.0.0.1 is an IP address that refers to your own machine. But if you are on a network/connected to a router and your computer has been assigned a different IP address, you may need to enter that address, e.g. 192.168.0.xxx via the address window in your browser.

       
  • If everything is working correctly, you should now get a green textured "AGWPE web page" with login slots.

AGWPE Brower Login page

If you kept the defaults on the HTTP Interface page, you do not need to enter a LOGIN or PASSWORD providing you are accessing the AGWPE from the same computer, i.e. not accessing the AGWPE machine over a network.

  • Your browser will then display a AGW Packet Engine Main Menu page.

Picture of browser main menu page  <-- Click for larger picture

If you click on the MONITOR option, you should soon see incoming lines of packet data scrolling across your browser!

You can also call up a MHEARD LIST and even edit you AGWPE ports... but not all the menu choices are working (as of version 2003.308).

Trouble Shooting:

If you can't get your browser to display the AGWPE green web page:

  • Check your AGWPE folder. You need to have a "HTTP" folder in it and it should have some files in it -- those files come with the original AGWPE zip file for all major releases, such as 2003.308. They usually are not included with beta release zip files.
     
  • Make sure you have the HTTP Interface activated on port 80 -- see #2 above.
     
  • Your firewall program (ZoneAlarm, etc.) may be blocking access to port 80. Temporarily turn off the program to test this. If everything then works, you will have to configure the program so it allows access to AGWPE's port 80.
     
  Last Updated: 09/03/2010   Return to top of page