AMPEstreams2.2 Help rev1 The AMPEstreams was constructed to tie the Airmail packet server module to the AGW packet engine. AMPEstreams is a ten stream version of AMPE1.6. So AMPEstreams functions with either the Airmail packet server or the Airmail packet client modules. Version 2.2 adds the capability to select from the Airmail packet module which packet engine radio port to use. Like AMPE1.6, AMPEstreams starts a TCP server listening on a TCP port for the Airmail packet module, emulates a Kantronics tnc to the Airmail, translates and presents a client to the AGW packet engine on the packet engine TCP port. This version uses the TCP socket in the Airmail packet modules. Unlike AMPE1.6, streams uses a default TCP port number on its Airmail side of 8200. The default TCP port that AMPE1.6 opens for Airmail is 8100. This program will be obsolete when the Airmail supports the packet engine directly. ----- To configure only the Airmail packet client module to work with the AMPEstreams: In Airmail tools/options/modules/vhf packet client setup: Select the KAM+ for the tnc. The default Airmail TCP port in AMPE1.6 is 8100. The default Airmail TCP port opened by AMPEstreams is 8200. If Airmail and AMPEstreams are running on the same computer, in the Com window enter T8200. If you have changed the default TCP port number in AMPEstreams you will need to enter the same port number in Airmail here. Other entries for the Com window can be: T8200 localhost:8200 localhost:T8200 127.0.0.1:8200 127.0.0.1:T8200 For AMPE1.6 the default Airmail TCP port is 8100. ------ To configure only the Airmail packet server module to work with the AMPEstreams: In Airmail tools/options/modules/vhf packet server setup: Select the first choice in the drop down menu for the tnc. The default Airmail TCP port opened by AMPEstreams is 8200. If Airmail and AMPEstreams are running on the same computer, in the Com window enter T8200. If you have changed the default TCP port number in AMPEstreams you will need to enter the same port number in Airmail here. Other entries for the Com window can be: T8200 localhost:8200 localhost:T8200 127.0.0.1:8200 127.0.0.1:T8200 Save the changes and close Airmail. In your Airmail folder find the Airmail.ini file and open it for editing. Notepad works fine. In the packet server section find the DecoderType line and make the DecoderType=KAM+ Save the edited Airmail.ini file. If you later apply/save changes in the Airmail packet server setup window. Airmail may alter the Packet Server DecoderType line. ----- You can run both Airmail packet server and packet client modules concurrently if you like. You will need to run two instances of AMPEstreams with unique callsign-ssid and unique TCP ports for the Airmail packet modules. Use the command line input option to change the Airmail TCP port in at least one of the AMPEstreams. You can enter the unique callsign-ssid as a command line input if you like as well. ----- COMMAND LINE ARGUMENTS: AMPE1.6 and AMPEstreams accept command line arguments to change their default settings. Arguments are separated by commas. Use a batch file, a windows shortcut, or the AGW packet engine program start up option to start AMPEstreams with command line arguments. You can start AMPEstreams without arguments and it will use the default value. Arguments must be made in order but the trailing arguments can be missing and those default values will be used. ie: AMPEstreams22.exe arg1,arg2,arg3,arg4,arg5 arg1 = Initial mycall. This is like the mycall saved in a physical tnc. Enter a callsign -ssid you want registered with the AGW packet engine when AMPEstreams starts. Airmail packet modules do not send the KAM tnc your mycall until a connect to: command is issued. Putting a callsign in arg1 allows you to start the packet engine, AMPEstreams, Airmail, its packet module and be ready to accept AX25 packet connect requests without first issuing a connect to: command to register a callsign. The mycall callsign registered by AMPEstreams will change if/when Airmail sends a mycall command for your station and if all the streams are in a disconnected state. Default mycall is empty. AMPEstreams converts any lower case call signs to upper case for AX25 packet compatability. arg2 = Default AGW packet engine radio port number to use if none is specified in the Airmail packet module connect to: text box. Default is number 1. arg3 = Allow incoming connect from any AGW packet engine radio port. TRUE/FALSE. Default is TRUE. FALSE will only process connect requests from the AGW packet engine radio port in arg2. arg4 = AGW packet engine TCP port where the AGW packet engine listens. Must be the same as the packet engine is set to. Packet engine version later than 2001. The packet engine uses TCP port 8000 as default. AMPEstreams uses TCP port 8000 as default. arg5 = AMPE TCP server port to listen for Airmail. Make this the same as you set in the Airmail packet module setup. AMPEstreams default is 8200. Command line argument example: AMPEstreams22.exe AA9AA-1,1,TRUE,8000,8200 ----- It is highly recommended that you use the AGW packet engine startup program menu to start AMPEstreams and define any command line arguments. Your callsign at least. You can also have the packet engine start Airmail for you. ----- Starting AMPEstreams AGW packet engine must be running and ready. Start AMPEstreams. If AMPEstreams successfully logs on to the packet engine. In the AMPstreams window you will see: EVENT: PE is ready The packet engine version Now start the Airmail packet module. If the Airmail packet module successfully connects to the AMPEstreams. In the Airmail packet module window you may see: Packet initialized OK In the AMPEstreams window you will see: accept winsock connection from client Congratulations your Airmail is now connected to the AGWpacket engine. You may minimize the AMPEstreams window. ----- Packet Engine Radio Port selection from Airmail: In the Airmail packet module connect to: text box. After your connect to call/via call list string. Append # Packet Engine Radio Port number. Connect to: text box Example: AB1CD-1 KW1VIA-7 KW2VIA #2 (This selects packet engine radio port 2) If the packet engine radio port number is omitted. AMPEstreams processes the connect to request using the default packet engine radio port. The default radio port can be changed at startup with command line arguments. ----- Pitfalls: Mind your [connect as] call sign in the Airmail packet server window tabs. Each tab is a different stream or channel. You can change your [connect as] call sign in every tab. This has no effect unless you start a connection from an affected tab. Airmail then sends the mycallsign command to the tnc. AMPEstreams mimics the KAMs response. If all streams are disconnected, then AMPEstreams changes its registered callsign per Airmails command. If any stream is in use then AMPEstreams mimics the KAM, scolds the host program and processes the connection request using the currently registered AMPE streams callsign. Incoming connect requests to the current AMPEstreams call sign are answered on the first open stream. Mind the computer handshaking selection on each tab. If you leave this in keyboard mode, then any packet connections to that tab will not enable automatic mail transfer or the Airmail BBS prompt. The transmit gauge in Airmail records the sending of bytes by Airmail to AGWPE program buffer. If sending a large file the transmit gauge can finish long before the radio transfer is complete. Trust the Airmail receive gauge and the AGW link status window to show the actual radio port exchange progress. License: Consider it the same as Airmail and AGWPE. Free for amateur radio use. Not liable for any damages. Use at your own risk. Credits: Jim Corenman KE6RK and the Airmail team for the Airmail program. George Rossopulos SV2AGW for his packet engine. Pedro Colla LU7DID for his active x control that made this linker possible. Brian Smith KG9OG