ASatLogger Virtual Access Server: Remote users can remotely access a TNC/D7/D700/D710 attached to an ASatLogger equipped SatGate with an Internet connection. All remote users can monitor all serial traffic but only users supplying the correct password will have write access to the serial port and the VAS Command Interpreter. This capability can be used for full remote control of D7/D700/D710's and TNC2 or KISS TNC's. This includes commands to change frequency etc of attached D7/D700/D710's to account for doppler shift. This capability can be used to access ASatLogger SatGates around the world, provided the Virtual Access Server is enabled, the SatGate has a public IP address and a firewall/router is configured to allow remote access. This would permit centralized monitoring and control of individual satellites, 24 hours a day if a sufficient number of ASatLogger SatGates participated. At the present time, there is no way to control an AZ/EL array, but a separate application could be developed to handle this task. Remote Clients: The remote user can use a full duplex telnet like Internet connection, such as Hyperterminal or AChat to connect to ASatLoggers Virtual Access Server. AChat 3.0 is available at http://www.billdiaz.dynip.com . Many standard APRS client applications can take advantage of this capability thru the use of a Virtual Serial Port (VSP) available from http://www.hw-group.com/products/hw_vsp/index_en.html. The VSP can be configured as a regular ComPort on your machine. Your APRS client application can then open this comport to communicate directly with the the serial device connected to ASatLogger or the VAS Command Interpreter. Note that serial hardware handshaking and flow control are NOT supported at the present time. ASatLogger VAS setup: The ASatLogger session must have a LAN or Internet connection, except when using a client application on the same machine and no Internet connection is desired or available. Remote users (including users on a LAN) must have access to the IP address and Port of the session. If a router and Firewall is used, you must configure them to allow remote TCP access to that IP address and port. This can be an issue when operating over a network not under your control. It may be possible to use TCP port 23 as the ASatLogger VAC port as a workaround in some cases. Your mileage may vary. The IP address of the ASatLogger session is displayed at the bottom right of ASatLogger when connected to the Internet or LAN. Very often, this is a local IP address or non-routable IP address and is not available to remote users. If the address is 192.168.x.x, 10.0.x.x, 169.x.x.x, it is a non-routable IP address. Every machine also responds to 127.0.0.1 or localhost for local applications running on the same machine. Localhost can be used when your client application resides on the same machine as ASatLogger. If Internet based remote access is desired and you do not have a public IP address on your home machine, you can subscribe to various services to obtain an actual or virtual public IP address. I use a commercial service, Dynip, but No-IP.org and others may provide similar services for free. Not recommended when you are using someone elses network for Internet access and you cannot administer the firewall/router. The ASatLogger "APRS-IS Server" tab "Client Port" box is used to set the TCP port to be used as the Virtual Access Server port. The default port is 14439. If necessary, configure your router/firewall to allow TCP access to your local IP address and this port number. If you change the port number, make sure you make corresponding changes in your router/firewall. If you are operating ASatLogger and a client application on the same machine, no changes to the firewall/router are usually required, provided remote access is not needed or wanted. The "Virtual Access Server" button, "Start", enables remote access. "Stop" disables remote access. "Close All" disconnects all connected clients. If the "Auto Start" check box is checked, remote access will automatically be enabled after a short delay. The "Connected Clients" combo box displays the IP address and Name/Callsign (if known) of all connected users. The Name/Callsign will only be present if the client has supplied the proper logon text. Properly logged on clients will have full access to the serial port and attached TNC/Radio. The "Relay to APRS-IS" checkbox will relay any valid APRS packets received from the APRS-IS that pass the logging filter set on the "Log Incoming Packets" tab if "Log all packets containing" is checked and there are 1 or more entries in "Text in Packet" combo box. The "Auto Start" check box will cause the VAC to automatically start listening for client connections after a short delay upon startup of ASatLogger, or after closing the VAC port. The "Help" button displays this file. ASatLogger VAC Password: Only clients who provide a recognized logon will be allowed to send data to serial port. All connected clients will see all data from serial port. The default logon is LOGON: (case sensitive). The default logon can be changed by editing the ASatLogger.INI file. The [USER] WORD field contains the logon string. This string must be at least 6 characters and end with a colon. Text following the colon will be treated as a user name or callsign. For example, using the default LOGON:, a remote Hyperterminal TELNET, AChat or compatible APRS client would send: LOGON:KC9XG-15 KC9XG-15 would be the user name displayed in ASatLogger and connected clients. It is STRONGLY recommended to change the default LOGON: to something unique and not likely to be found in an APRS Packet! For example, in the ASatLogger.INI file, change WORD=LOGON to: WORD=LogMeOn.144*39a: The logon is case sensitive! A client supplying a valid logon is considered an authorized user and has remote access to most ASatLogger features via the VAS Command Interpeter. See RemoteCommands.Txt for details, via the TNC form or the "Serial Port" tab. ASatLogger VAC Operation: All users connecting to an active ASatLogger VAC IP address and Port, will see all serial port activity. In addition, all logged packets set on the "Log incoming packets" tab will be provided. Status information from the VAC server to clients will be transmitted as an APRS test packet. The FromCall will be the Logon call from the "My Station" tab. The ToCall will be APGnnn, with nnn giving the ASatLogger version number. Status information can include Serial port status (open, closed), Baud rate, TNC mode (CMD, CONVERSE, KISS), D7/D700.D710 Radio Mode (Control, APRS, Packet) and status results of other commands. See RemoteCommand.Txt for details, via the TNC form or the "Serial Port" tab. ASATLogger VAC Remote Serial port commands: Most data received on the VAC client port (defaut 14439) by logged on user will be passed to the serial port, with several exceptions noted below. If the data received starts with: CONV or CONVERSE (when in Command Mode), forces TNC to Converse mode. ^C^C^C or Chr(3) forces TNC to Command Mode. Continues in selected mode til changed. When TNC is in Command Mode, all TNC commands are available, provided the TNC is accessible. TNC commands will not be accessible when a D7/D700/D710 is in Radio Control or APRS mode. VAS Remote Contol commands are available to authorized remote users at any time. The Remote Control commands are lines that begin with the letter "&" and contain a valid remote control command. See the ASatLogger TNC Help file and Remote commands help file (accessible via the main menu "TNC" command for details on configuring TNC's and D7/D700/D710 with ASatLogger) and the help file available on the "APRS-IS Server" tab. The ASatLogger Remote Commands help file is also accessible on the "Serial Port" tab. NOTICES: ASatLogger (c) copyright 2007 William Diaz KC9XG William.diaz@comcast.net http://www.billdiaz.dynip.com 815-838-1194