APU-102 User Interface

This chapter discusses the APU application software and local and remote user access to the APU-102 via the System Menu and Supervisory Menu. Through these menus you may view train information received from the APU-102.

APU Application Software Overview

User Access

There are three types of user access available, local, remote, and network. Local access requires a computer equipped with a standard communications package and a null-modem cable from the local port of the APU-102 to the computer. Remote access requires a computer equipped with a Hayes compatible modem and a standard communications package. Telnet connection requires that the APU-102 has network capable hardware and software as well as a valid network path to the APU-102, via WAN remotely or LAN at the site.

The factory default communications settings are:

Type	Baud Rate	Word Length	Parity	Stop Bits
Local	2400	8	N	1
Remote	Modems will negotiate best speed	8	N	1
Network	Handled by TCP/IP protocol

Communications Settings

Main Menu Options

There are two APU-102 Menu options: the System Menu and the Supervisory Menu.

The System Menu (aka Main Menu) functions provide accessibility to a wide range of reports and other information that can be generated from the stored data.

The Supervisory Menu (aka Change Menu) provides functions to reconfigure the operational parameters of the APU-102 as well as clear the APU-102 of all trains and status information. The same data is available whether accessing the APU-102 from a remote site via the modem or on-site via the local communications port or via a telnet connection. For detailed information about these menus, see the System Menu and Supervisory Menu sections later in this chapter.

Software Programs

The APU-102 uses up to three different software programs. The first is the APU application software, which runs the APU-102’s normal functions. Comet Electronics incorporates its standard remote support into this application software. The second is a standalone “fail-safe” software program, used mainly for recovery and diagnostics. There are various versions of the fail-safe program depending on configuration of the APU-102. Mini Remote Support (MRS, Start-up ROM version 4.1) or ROMSHELL (Start-up ROM version 5.0+). When the SYS light (LED) is on steadily, the APU-102 is running the APU application software. When the SYS light (LED) is flashing, the APU-102 is running MRS/ROMSHELL.

With addition of network connections to the APU-102, NetMRS, a network capable version of ROMSHELL was created. It has all the functions/commands of ROMSHELL, with local and remote connectivity. Additionally, it has network connectivity using the AEI Application’s networking parameter set.

APU Application Software

The APU application software is the heart of the APU-102. It is stored on the solid state disk along with the train information. It logs the train axles, correlates the axles into cars, and puts the tags with the cars. It is a multitasking (or multi-threaded) program that allows the system to record a train, share live acquisition data to external devices, transmit consists and maintenance reports to multiple hosts, and allow remote diagnostic access.

When the APU application software is running, you connect to the APU-102 via the User Interface or “Front Door.” Connecting via the Front Door allows you to define the system parameters and individual session parameters, view train data, delete trains, and view the systems logs, etc. The Front Door is generally used unless there is a problem with the APU application software.

Mini Remote Support (MRS), ROMSHELL, and NetMRS

Mini Remote Support (MRS) Start-up ROM 4.1 and earlier

Mini Remote Support (MRS) is a version of the Video Masters (VMI) Remote Support software. When this program or the APU application software is running (version 4.x only), you can log into the APU site’s Back Door. Logging into the Back Door via the MRS program allows you to connect to the APU locally or via dial-up modem, transfer individual files, and download new code. However, these functions are not menu-driven. A special communication program, “Remote Support,” is required to connect to an APU-102 to use MRS’s features. Remote Support is a communications utility developed by VMI. It also requires legacy serial ports and modems and must be run under MS-DOS. It is not compatible with Windows operating system or most modern PC’s ports or modems.

MRS was programmed or burned into an EPROM before the unit was shipped to the customer. The use of the EPROM means the software cannot be erased. The APU-102 boots to the EPROM first, then looks to see if the APU application software is available. If there is any problem with the APU application software, the APU-102 loads the MRS program. Every fifth time the APU hard boots (power reset or watchdog timer reboot), the MRS program is loaded, stays in MRS mode for 20 minutes, then reboots. To boot the APU-102 directly into the MRS mode, press and hold the SYS button, then turn on the APU-102. A short time after power up, the Startup ROM checks the status of the SYS button and will flash rapidly (about 4 times per second) during this check. Release the SYS button anytime after the rapid flash stops. When the MRS application is ready, the SYS LED will flash slowly (about once per second).

The EPROM is located on the USSD card and can be identified by the name "Start-up ROM", version and USSD capacity. The capacity of the USSD is in a system file on the ROM and must match the configured SRAM memory on the USSD.

Note: The reboot command from the Front Door (soft boot) does not increment the MRSCOUNT counter.

ROMSHELL Start-up ROM version 5.0 or higher

ROMSHELL (Start-up ROM version 5.0+) replaces MRS. It has expanded functionality compared to MRS listed above and is accessible with any commercial communication software program. The ROMSHELL interface is detailed in ROMSHELL User Interface (Optional).

The EPROM is located on the USSD or PCM-SSD card in a Pentium class APU-102 and can be identified by the name "Startup ROM", version and USSD capacity. The capacity of the USSD is in a system file on the ROM and must match the configured memory on the USSD. The PCM-SSD does not use SRAM so capacity is irrelevant. Startup ROM is not used in the LX-800 equipped APU-102.

NetMRS

NetMRS is a network-capable version of ROMSHELL. It is not loaded from the Startup ROM, but is an application running from the XPe kernel on the system’s Flash memory. It has some additional capabilities compared to ROMSHELL. The NetMRS interface is detailed in NetMRS User Interface (Optional)

Multiple Sessions

The APU-102 supports numerous virtual APU's. (pre 5.2 supports four. 5.2+ supports up to ten) Each virtual APU, called a "session," can be configured individually according to the needs of the railroad it supports.

Current versions of the AEI application include a new feature, NetMenu. It allows multiple devices to be accessed via one external connection. You may be presented with a menu BEFORE getting the session menu of the APU-102. NetMenu is detailed later in this text.

When accessing the site, the first question the APU-102 software asks is which APU session you want to access. The Session Menu will only show 4 sessions unless more are configured. Each session has its own password protection, just like each physical APU would. (See Passwords.) Once you gain access to a session (other than Session 1), any parameters you change affect only that session.

Each session on the APU-102 is capable of reporting consist and maintenance reports to the host of your choice. Sessions can be configured for different purposes. For example, a customer may set up Session 1 for standard consist and maintenance reporting to its normal host system, then configure Session 2 to report different types of information (such as scale reports) to other facilities on the railroad. This often happens when the host system to which the AEI reports are sent cannot handle the type of data the other facility needs.

Each session uses the same train information but is completely independent when formatting and transmitting the information. The owner of the APU-102 is responsible the initial setup of each session, while the session owner has the ability to customize the individual session. After you select a session, password entry is required.

Passwords

Comet Electronics delivers the systems with default passwords set up in the APU-102. Both the System Menu and the Supervisory Menu are password protected. Also, a password is available for each session’s host interface. The System and Supervisory passwords are only visible under the Supervisory Menu display of the site parameters where separate password fields are maintained. Each session is independent of one another, so passwords for one session would not be available to other session users. The System Menu and the Supervisory Menu require different passwords from the host system. The following are the APU-102 default passwords:[DDC1] 

Default Passwords
System Menu	Supervisory Menu
SECRET	SUPER

Default Passwords

Tip Version 5 +

Entering the supervisory password at the initial login screen will login directly to the Supervisory Menu.

User-level security with complex password capability has been added with version 5.2. User-level security is detailed in User Access Account Management (USER) 5.2+, later in this article.

Inactivity Timeouts

There are numerous inactivity timeouts built into the APU-102. Their purpose is to remind the user that action has not been taken for a particular amount of time or to log the user off in case the user has forgotten to do so. At the Session Select menu, the APU-102 pauses for three minutes. The APU-102 then beeps and redisplays the Session Select menu. This represents one timeout period. The table below demonstrates how timeouts work:

Screen	Number of 3-minute Inactivity Timeouts Allowed	Result
Session Select Menu	3	APU-102 logs user off.
Password	2	Returns to Session Select Menu screen.
System Menu	1	APU-102 logs user off and returns to the Session Select Menu screen.
Supervisory Menu	1	Returns to System Menu screen.

Inactivity Timeouts

On-Line Help

Throughout the user command interface in the System Menu or Supervisory Menu, you may type a command followed by <?> to display available information about the command. If you do not remember the command, enter <?> at the command prompt and the software shows what commands you can currently use. Example: Typing <D><?> describes the Directory command and any options available with that command. Features that have been added since publication of this manual will be documented in the APU-102’s on-line help.

Command Formats

When entering commands in a string, always type a comma between them.

Example: To use the Check Tag Sequence (CT) command to verify that Reader0 and all antennas for a particular site are working correctly, enter CT,0,* for the command string.

Note: Applicable only when check tags are part of the hardware components.

Logging On To the APU-102

1)  After connecting to the APU-102 through either the local port, remote port (modem), or telnet, press <Enter> to activate the Session Select menu screen. If you get a “NetMenu Equipment Selection screen”, enter the option for the desired APU-102 to be connected to. Press <Enter> again if necessary to activate the Session Select menu screen and you will get the Session Select menu.

1. Comet Electronics 2. Inactive Session, Not Available for Selection 3. Inactive Session, Not Available for Selection 4. Inactive Session, Not Available for Selection X. Log Off Select the Appropriate Session # ( 1, 2, 3, 4 or 5) Session #: 1 Test  Wed 05/02/11  10:11:12 Password: ******

Figure 4.1: Session Select Menu Screen

Options 1 - 4 on this menu represent the four available sessions in the APU-102. Additional sessions only appear if configured. Option X logs you off the Session Select menu and, if accessed through the remote port, disconnects the modem.

2)  To log on to a session, enter the number corresponding to the desired session. The APU-102 requests the password for that session.

3)  Enter the correct system password. If no password is established for that session, type SECRET, the default password for the System Menu. (Passwords are not case-sensitive) The default security level System and Supervisory password fields are both a maximum of seven ASCII, printable characters. A higher level, user-based security is available and detailed in the “User” section later in this chapter.

Warning Version 4x

An issue was discovered in Version 4x where the password parameter would allow you to enter 7 characters. The password entry on login only allowed 6 characters, making the APU-102 inaccessible.  It has been corrected in Version 5x.

 

As the password is entered, an asterisk (*) displays where you type the character. After the correct system password is entered and accepted, the Logon menu displays and the cursor flashes at the APU102XP:  Main prompt with the current session number.

Comet Electronics Automatic Equipment Identification System APU Software Version 5.1.1.101 AMTECH Model AI1200 Ver 2.80 SN97514 Mon 05/02/11  10:11:12 Host Reporting:  On, All Last LOGON:  Thu 11/12/10   17:28:40 USID        COMET05150 Site Name:  Test APU102XP: Main 1>

Figure 4.2: Logon Menu Screen

If a train is being recorded or if an associated APU is recording a train (double-track sites), a “train recording” or “site activity” message will be displayed along with the prompt.

The APU-102 will not transmit critical system messages until the System Menu password is entered. This ensures that the information is available to authorized users only and that the remote terminal is ready to display data from the site.

If the password entered is invalid, the APU-102 displays the message “Invalid Password”. The password field re-displays to allow you a second chance. After 3 failed attempts, you are returned the user to the Session Select menu.

4)  Type <?> at the APU102XP:  Main prompt to display the System Menu.

5)  To enter the Supervisory Menu, type <C> (for Change) at the APU102XP:  Main prompt. The APU-102 requests the Supervisory Menu password for that session.

6)  Enter the correct system password. If no password is established for that session, type SUPER, the default password for the Supervisory Menu. The APU102XP:  Change prompt displays.

7)  Type <?> to display the Supervisory Menu.

The rest of this chapter explains the System and Supervisory menus in detail.

System Menu

Overview

To access the System Menu, type <?> at the APU102XP: Main prompt and press <Enter>. The System Menu displays. The left side of the System Menu shows the command options for displaying train information and the exit command. The right side of the System Menu shows the command options for displaying APU-102 system information and the help command.

 

APU102 SYSTEM MENU

D       Directory L       List Clean Consist S       Train Summary SHS     System Health Summary /       System Information & Status MST     Modem Self test (local only) SP      Toggle Sensor Power TR      Terminate Recording ST      Simulate Train SM      Stimulate Maintenance Report ODM     Outbound Data Manager DM     Inbound Data Manager MAP     Display Likely Matches X       Exit and Log Out

DD      Dump Raw Data DP      Display Parameters C       Change to Supervisory Menu I       Display I/O Information TL      Train Logger Reports PT      Pass-through to Port AMT     Pass-through to Reader CT      Check Tag Sequence IR      Initialize Reader RFON    Activate Reader RF RST     Reader Interface Self Test MA      Print Match List CMP     Compare two Trains ?       This Screen

For help on a command, enter the command followed by a '?'

Figure 4.3: System Menu

Menu and available commands may vary depending on AEI Application version. If not detailed in this text, refer to the on-board help.

System Menu Commands

Each System Menu command initiates a screen on which you may perform APU-102 transactions. The System Menu’s standard header fields are defined in the System Menu Headers section below. Individual screen functionality and data field definitions follow in the System Menu Screens section.

System Menu Headers

Tables 4-1 through 4-3 define the header information that appears on many of the screens. Table 4-1 shows the basic header that displays on all System Menu screens. Each screen description in this chapter refers you back to the appropriate header definition table where necessary.

Header Field	Description
MP:	Mile Post. Represents the mile post location of the site.
STATION:	Station Number. Represents the five-digit station number identifying the site.
READER:	Reader Number. Identifies the specific reader assigned to that station.

Table 4-1: Basic Header Information

Header Field	Description
Train Seq #	Sequence number of the train that is being listed.
DATE:	Date the train passed the site.
TIME:	Arrival time of the train at the site.
ENG:	Lead engine tag number if available. This will be replaced by a zero (0) if no tag is available.
DIR:	Train direction as it entered the site. Stopping and backing have no effect on this field. This is determined by the Transducer Orientation in the Operating Parameters and the Track Orientation in the Session Parameters.
MPH:	Average miles per hour of the train as it passed through the site.
AXLES:	Total number of axles correlated by the APU-102 during the train passage.
WDA	Number of wheel counts received on Wheel Detector A. Includes forward and backing counts.
WDB	Number of wheel counts received on Wheel Detector B. Includes forward and backing counts.
WDAB	Number of wheel transitions from Wheel Detector A to Wheel Detector B if the train was traveling across the sensor in the A to B direction. Otherwise this number will be 000.
WDBA	Number of wheel transitions from Wheel Detector B to Wheel Detector A if the train was traveling across the sensor in the B to A direction. Otherwise this number will be 000.
HOST REPORT	Describes the reporting that was provided to the Host System. The information that displays is: Host reporting status = ON/OFF Report status = (Y, N, P, E, X). See the Directory command for an explanation of these. An asterisk (*) displays when Host Reporting is off. Date of the host system transaction. Time of the log-on to the host system / Time of the end message from host system.

Table 4-2: Secondary Header Information

Header Field	Description
Loco Cnt:	Count of all locomotives recognized by the APU-102 - tagged and untagged.
Loco Tags:	Count of all locomotives recognized to have at least one AEI tag (EGC = 5).
Loco Xtags:	Untagged Locomotives. Count of locomotives recognized where the APU-102 did not read any AEI tags.
Car Cnt:	Count of all equipment recognized on the train to be a railcar - tagged and untagged. Multiple-platform articulated cars are counted as one (1) car. Cabooses are counted in this field. Lost axles groups are not counted in this field.
Car Tags:	Count of all the railcars recognized to have at least one AEI tag (EGC = 19). EOT tags are not counted in this field.
Car Xtags:	Untagged cars. Count of railcars recognized where the APU-102 did not read any AEI tags. Lost axle groups are not counted in this field.
Containers:	Number of tagged containers found on the train (EGC = 10).
Chassis:	Number of tagged chassis found on the train (EGC = 27).
Trailers:	Number of tagged trailers found on the train (EGC = 21).
Lost Axles:	Count of axles that could not be associated with a recognizable axle pattern. This does not indicate missed axles.
Lost Tags:	Count of tags not associated with a car, locomotive, caboose or EOT device. Test Tags are counted in this group when system testing is being done. This does not indicate missed tags.
Other Tags:	Count of tags other than EGC 5, 6, 10, 14, 19, 21, and 27.
END:	END Statement. After the last line of any train report, a blank line will be sent followed by the "END" Statement.

Table 4-3: Detailed Header Information

System Menu Screens

The following explains the purpose and use of System Menu commands and defines the data fields on the System Menu screens. Where applicable, the Header Fields section refers you to the appropriate header definition table above.

Directory (D)

The Directory (D) command displays the 15 most current trains. If there are less than 15 trains on the APU-102, the complete train list displays. If there are no current trains, the message “There are currently no trains available” displays.

APU102 Nicholson Ave         MP: 0000.0   Station 00001   Reader 1

SEQ	DATE	TIME	RPT	LEAD	ENG	DIR	RT	MPH	AXLES	CARS	TAGS	LEN(FT)
0002	05-02-11	09:02	Y	OICU	812	S	0	024	0024	0005	0001	003007
0001	05-02-11	06:31	Y	ENG	1	S	0	024	0024	0005	0001	003007

APU102XP: Main 1>

Figure 4.4: Directory Screen

1)  Type the D command in one of the following formats:

Command Format	Description
D	Required. Display the 15 most current trains.
D,*	Optional. See all trains (one page at a time if there are more than fifteen).

2)  Press <ESC> to exit or any other key to continue.

Header Fields

Refer to tables 4-1 through 4-3 for header field definitions.

Data Fields

The table below defines the data fields on the Directory screen.

Field	Description
SEQ:	Sequence number assigned by the APU-102 to identify the train file stored on the solid-state disk. This number continues to 9,999 before resetting to 0001. Can be reset to 0001 by using the Master Reset command. Before modifying this field, see the description of the Master Reset command in the Supervisory Menu later in this chapter.
DATE:	Date the train passed the site.
TIME:	Arrival time of the train at the site.
RPT:	Report Status. Indicates the status of the host report for that train. Y = Train reported OK. N = Train has not been reported, but will be reported when the APU-102 gets to its sequence number. P = Train is currently being reported or will be reported next when the telephone line becomes available. E = Train was reported but an error was found when the APU-102 correlated the axles and tags. This is NOT an error in host communication. X = Train was not reported due to an inhibit such as the age time-out. (The train was too old.) F = Train information was not reported due to an unknown condition. This would occur if none of the above conditions could be identified.
LEAD ENG:	Lead Engine Tag ID. Identifies the lead locomotives tag number for that train if it is tagged. If the lead locomotive is not tagged, the field will display the first locomotive tag that was read. If no locomotives are tagged, the field will be filled with 4 blanks and 6 zeros.
DIR:	The train direction as it entered the site. Stopping and backing have no effect on this field. This is determined by the Transducer Orientation in the Operating Parameters and the Track Orientation in the Session Parameters.
RT	Indicates the route the train is taking.
MPH:	Average miles per hour of the train as it passed through the site.
AXLES:	Total number of axles detected by the APU-102 during the train passage.
CARS:	Total number of railcars recognized by the APU-102. An engine is listed as a car here. An articulated car (3 or 5 pack) will be recognized as one car in this count. An untagged caboose will be recognized as a railcar. Unidentified cars are NOT reported in the car count.
TAGS:	Total of all read tagged units on the train. A tag count preceded by a minus sign (-) indicates that only a Train Summary remains for that train.
LEN (FT)	Total of all the calculated car lengths in the train. If the length is enclosed with brackets, [00486], one or more cars in the train had a length above 100 feet. This could indicate that the train had stopped, which would make the length of the car inaccurate. This length is approximate and should never be used for train movement operations. i.e., “will this train fit in a siding?”

An asterisk (*) indicates the other track was active on a double-track site.

List Clean Consist (L)

The List Clean Consist (L) command lists the most recent train in a generic format.

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0002   Date: 05-02-11   Time: 09:02:35   ENG: OICU 812     Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON  : * :05-02-11  09:04:52/09:05:01   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:     000    Chassis:     000     Trailer:  000   Lost Axles:      000    Lost Tags:     000     Other Tags: 00     D001  OICU   812   N    0/ 14   @ D002      000000   C          (6)   @ R003      000000   C          (4)   @ R004      000000   C          (4)   @ R005      000000   C          (4)   End List 0002      END APU102XP: Main 1>

Figure 4.5: List Clean Consist Screen

1)  Type the L command in one of the following formats:

Command Format	Description
By information:
L	Required. Lists the most current train in generic format.
L,*	Optional. Lists all trains.
L, Sequence #	Optional. Displays information for the specified sequence number.
By format:	Many formats no longer used
LC	Optional. COMPASS format. No Longer used.
LT	Optional. TCS format. No Longer used.
LT94	Optional. T94 format.
LF	Optional. Full consist format.

Each time you enter the L command, the APU-102 prompts you to select a C (Continuous) or P (Paused) screen display. Selecting the Continuous display scrolls through all of the requested information without stopping. Selecting (P)aused scrolls through the data one screen at a time.

2)  Enter C or P.

If you selected Paused and there are more screens to display, the APU-102 prompts you to press <'C>' to change to Continuous display, press <ESC> to exit the list, or press any other key to continue the Paused display. This process continues until all the requested data has been displayed or a different selection is made.

If there are no additional screens, the APU102XP:  Main prompt displays.

Header Fields

Refer to tables 2, 3, and 4 for header field definitions.

Optional Formats

The LC, LT, LF, and LT94 commands list train information in specific formats. Below are the optional formats and their command code.

List Clean Consist - Compass Format (LC)

The List Clean Consist - Compass Format command generates and displays a train consist listing in the COMPASS format. For information on Compass Record format processing, refer to Header and Tag Formats in 2.0 AEI Site Operation. For Compass Record header and tag formats, refer to Appendix B.

 

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0002   Date: 05-02-11   Time: 09:02:35   ENG: OICU 812     Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON  : * :05-02-11  09:04:52/09:05:01   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:     000    Chassis:     000     Trailer:   000   Lost Axles:       000    Lost Tags:    000     Other Tags:  00 4O2 1 00001S1996013116020001000003000000000000  05 OICU  812C0X  19    000000C0X  19    000000C0X  19    000000C0X  AVI   End List 0002

Figure 4.6: List Clean Consist - Compass Format Screen

List Clean Consist - TCS Format (LT)

The List Clean Consist - TSC Format (LT) generates and displays a train consist listing in the TCS format. For information on the TCS format processing, refer to Header and Tag Formats. For TSC header and tag formats, refer to Appendix B: Host Reporting Formats.

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0002   Date: 05-02-11   Time: 09:02:35   ENG: OICU 812     Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON  : * :05-02-11  09:04:52/09:05:01   Loco Cnt:    02    Loco Tags:   01     Loco Xtags:  01   Car Cnt:    003    Car Tags:   000     Car Xtags:  003   Container:     000    Chassis:   000     Trailer:   000   Lost Axles:      000    Lost Tags:     000     Other Tags:  00 =#@001000000test      199601311602002000003000000000000S    0000000G000216020030 7024 001D OICU    812     00000024 002D    000000     00000024   End List 0002      END

Figure 4.7: List Clean Consist - TCS Format Screen

List Clean Consist - Full Consist Format (LF)

The List Clean Consist - Full Consist Format (LF) command generates and displays a train consist listing in the Full Consist format. For information on the Full Consist format processing, refer to Header and Tag Formats in 2.0 AEI Site Operation. For Full Consist header and tag formats, refer to Appendix B: Host Reporting Formats.

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0002   Date: 05-02-11   Time: 09:02:35   ENG: OICU 812     Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON  : * :05-02-11  09:04:52/09:05:01   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:     000    Chassis:     000     Trailer:   000   Lost Axles:       000    Lost Tags:    000     Other Tags:  00 Full Consist Listing Car EGC   Car ID    Ts Or Ax  LenFT MPH   Tr PC Pp A0  A1  Fuel(L) Spare --- --- ----------- -- -- --- ----- ----  -- -- -- --- --- ------- ------- 1   5   OICU000812  L  A  6   61    24.7  -  -  -  -   14  ------- ------- 2   5   ----------  U  -  6   61    24.7  -  -  -  -   -   ------- ------- 3   19  ----------  U  -  4   62    24.7  -  -  -  -   -   ------- ------- End List 0002      END APU102XP: Main 1>

Figure 4.8: List Clean Consist - Full Consist Format Screen

List Clean Consist - T94 Format (LT94, AAR standard S918A)

The List Clean Consist - T94 Format (LT94) generates and displays a train consist listing in the T94 format. T94 is the most common host reporting format. For information on T94 format processing, refer to Header and Tag Formats in 2.0 AEI Site Operation. For T94 header and tag formats, refer to Appendix B: Host Reporting Formats.

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0002   Date: 05-02-11   Time: 09:02:35   ENG: OICU 812     Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON  : * :05-02-11  09:04:52/09:05:01   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:     000    Chassis:   000     Trailer:   000   Lost Axles:      000    Lost Tags:     000     Other Tags:  00 AEM     COMET00515011050206021602060N4110002GGS0E024024024??FN00307G02000030000024 RRE001D    OICU000812A GLK00014240601 THI001OICU0000000812?????0000?00000000??????0?0014???? RTD2A453C29502020243252452058585858204E415300 RRE002D    0000000000U GNK00000240601 RRE003R    0000000000U GNK00000240401 RRE004R    0000000000U GNK00000240401 RRE005R    0000000000U GNK00000240401 EOC0000000378   End List 0002      END APU102XP: Main 1>

Figure 4.9: List Clean Consist - T94 Format Screen

Train Summary (S)

The Train Summary (S) command provides the train header and the equipment and tag summary without the consist information. A recap of the equipment that moved across the site is provided. This includes the number and types of equipment that went through the site as well as the number of tags read for some groups.

'Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0002   Date: 05-02-11   Time: 09:02:35   ENG: OICU 812     Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON  : * :05-02-11  09:04:52/09:05:01   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:     000    Chassis:   000     Trailer:   000   Lost Axles:      000    Lost Tags:     000     Other Tags:  00 End List 0002      END APU102XP: Main 1>

Figure 4.10: Train Summary Screen

Type the S command in one of the following formats:

Command Format	Description
S	Required. Summary of most recent train.
S, Sequence #	Optional. Summary for the specified sequence number
S,*	Optional. Summary for all available trains.

Header Fields

Refer to tables 4-1 through 4-3 for header field definitions.

Data Fields

As a summary screen, only header fields displays.

System Health Summary (SHS)

The System Health Summary (SHS) command displays any trains that the APU-102 flags as having potential problems, performs a Reader Interface Self Test (RST) and, if not dialed in with the modem, performs a Modem Self Test (MST). The APU-102 monitors items such as antenna handshakes, wheel detector pulses, modem retries, etc. If a train shows up on the System Health Summary, it should be determined if a problem can be prevented before it happens.

APU102 SYSTEM HEALTH SUMMARY Condition                                                                       Status Train #0070   Axle conversion error                           WARNING Train #0076   Axle conversion error                           WARNING 0 Failure(s), 2 Warning(s). End of report. APU102XP: Main 1>

Figure 4.11: System Health Summary Screen

Type the SHS command and press <Enter>.

Header Fields

There are no header fields on this screen.

Data Fields

The table below defines the data fields on the System Health Summary screen.

Field	Description
Condition	Condition of the train. Lists the train sequence number and the diagnosed problem.
Status	Issues a “Warning” or “Failure” status indicating if the problem may be corrected or if system failure has occurred.
# Failure(s)	Lists number of APU-102 system failures.
# Warning(s)	Lists number of APU-102 system warnings.

System Information and Status (/) [Forward Slash]

The System Information and Status (/) command displays the software version, date, and file size. It also displays the available memory and disk space. The status of the Inter-track Communications (ITC), HBD, Scale, REDI, XTrack are displayed, if installed. The status indicator reports the presence of periodic heartbeat messages received from the other connected device.
This report may be updated as improvements are made to the AEI application.

'

Version Date/Time: "AP423.EXE" V4.23 9/2/1998 4:23:0  (180272bytes) Free Mem: 194160, Free Disk: 431104, Next Handle: 2, Free Handles: 15 ITC Status....... Not Installed Scale Status..... Not Installed REDI 1 Status.... Not Installed REDI 2 Status.... Not Installed REDI 3 Status.... Not Installed REDI 4 Status.... Not Installed

Figure 4.12: System Information and Status Screen Version < 5.1.1

Version Date/Time: "APU102.EXE" V5.1.1.102 4/11/2011 11:37:32 (bytes) Free Mem: 331,169,792, Free Disk: 85,196 KB ITC Status......... Not Installed. Scale Status....... Not Installed. MicroHBD Status.... Not Installed.

Figure 4.13: System Information and Status Screen Version 5.2+

Type the </> command (Forward Slash) and press <Enter>.

Header Fields

Refer to table 4-1 for header field definitions.

Data Fields

The table below defines the data fields on the System Information and Status screen.

Field	Description
Version Date/Time:	Software version, date, and file size.
Free Mem:	Available memory.
Free Disk:	Available disk space.
Next Handle	Next available file handle.
Free Handles	Number of handles available to open files.
ITC Status	Status of the Inter-track Communications (ITC).
Scale Status	Status of the scale.
REDI (1-4) Status	Status of the REDI port(s), if installed.
MicroHBD Status	Status of the MicroHBD, if installed.
XTrack Status	Status of all configured Tracks

Extended System Information and Status (//) [Double Forward Slash] ]

The Extended System Information and Status (//) command (Double Slash) displays debug and self diagnostic information in addition to the standard System Information. It varies from version to version and will not be detailed here.

Display Message Metrics (MM) Version 5.2+

The Display Message Metrics (MM) command displays the count for each system status message. Messages are from APUERROR.DAT file and correspond to messages in SYS report and reports sent to maintenance host. Remove the file "messmet.dat" to reset the Message Metrics count file.

===== Message Metrics ===== Unit Startup                                - User Abort                                  -        ************ Presence Startup                       8 Presence Clear                          8 Process Startup                          -        ************ Pres Circuit Warnin        1 Aborted File Create         -

Figure 4.14: Display Message Metrics Screen (partial) Version 5. 2+

Modem Self Test - Local Only (MST)

The Modem Self Test (MST) command checks the modem setup and operational ability. It does NOT test telephone line connectivity. It can only be run from the local port or telnet and will return the test results in the same format as the Reader Interface Self Test.

Modem Test                  Status -----------------------------------------------------------  ----- Modem Communications.........................    OK Modem Carrier.........................................    OK All Tests Passed.......................................   NORMAL

Figure 4.15: Modem Self Test - Local Only Screen

Type the MST command and press <Enter>.

Data Fields

Field	Description
Modem Test:	Lists the type of modem test being run: Modem Communications and Modem Carrier.
Status	Displays the results of the modem tests.

Toggle Sensor Power (SP)

The Toggle Sensor Power (SP) command allows you to turn the power to the external sensor devices off and on (if the site is equipped with a sensor power relay or LVD-2000).

1)  To turn external sensor power off, type the SP command and press <Enter>. The following message displays:

--------------------------------------- !! External sensor power is now OFF  !! Press any key to turn power back on... ---------------------------------------

Figure 4.16: Toggle Sensor Power Message

2)  Press any key to turn external sensor power back on. The following message will display.

“External sensor power is now ON”

Note: This usually causes spurious inputs the APU-102 perceives as site activity. The APU-102 may go into acquisition mode. It will timeout.

Terminate Recording (TR)

The Terminate Recording (TR) command terminates the APU-102’s recording of the current train.

1)  Type the TR command and press <Enter>. The following message displays:

"This function will terminate recording of current train. Continue (Y/N)?"

2)  Select Y(es) or N(o). The APU102XP:  Main prompt redisplays.

Simulate Train (ST)

The Simulate Train (ST) command initiates a train test sequence for testing the reporting functions. The simulation cannot exercise the acquisition processes, but can perform post-processing functions and consist reporting. It is assigned a sequence number and will appear in the train directory just like an actual train. If it is undesirable to report simulated trains, a host reporting parameter can be modified to enable/disable reporting for each active session.

1)  Type the ST command and press <Enter>. The APU-102 Main prompt re-displays.

2)  Type D (or any of the available D command formats) to access the Directory command. The Directory screen displays the simulated train.

Simulate Maintenance Report (SM)

The Simulate Maintenance Report (SM) command causes the maintenance reporter process to initiate a maintenance transaction with the host by issuing a "No Activity" message to the system logger for the session you are logged into. If maintenance is enabled, it goes through its normal reporting processes. This function has no effect if the maintenance reporter is not activated.

No Activity" message has been logged. Maintenance report is now pending... APU102XP: Change 1>

Figure 4.17: Simulate Maintenance Report Screen

Type the SM command and press <Enter>.

Outbound Data Manager (ODM)

Outbound Data Manager is used in Distributed Processing Systems. AEI information from this APU-102 is transmitted to other “readerless” wayside systems, upstream on the same corridor, to match to axle data on those systems. This allows those systems to send tagged consists with defect data added to their respective hosts.

Refer to the APU103 Installation & Operation Manual' for additional information.

Inbound Data Manager (IDM) ]

Inbound Data Manager is used in Distributed Processing Systems. If this APU-102 was configured as a readerless APU (APU-103) it would be connected to wayside defect detector equipment. Axle data from the Defect Detector would be matched to AEI data received from downstream APU-102s. Its primary use is to show what trains from what remote sites are on the system, specifics about each train, and whether or not it has been matched to a local train.

Refer to the APU103 Installation & Operation Manual' for additional information.

Display Likely Matches (MAP)

MAP used in Distributed Processing Systems. If this APU-102 was configured as a readerless APU (APU-103) it would be connected to wayside defect detector equipment. The MAP command displays potential matches between trains received from downstream readers to local trains acquired by this APU-103.

Refer to the APU103 Installation & Operation Manual' for additional information.

Exit and Log Out (X)

The Exit and Log Out (X) command allows you to exit the current session and return to the Session Select menu.

1)  Type the X command (or “5” if displayed as a choice) at the Session # prompt and press <Enter>. X works regardless of the version.

2)  The system displays site name, the date and time, then logs out.

=== Dump Raw Data (DD) ===

The Dump Raw Data (DD) command dumps the raw data to the requesting terminal.

1)  Type the DD command in one of the following formats.

Note: This command must be entered with one of the valid extensions.

Command Format	Description
DD(Extension)	Required. Raw data for the most recent train. Valid extensions: S          Processing Summary F          Full Composite Listing T          Raw Tag Data C          Axle-Car Conversion Data L          Event Log W         Wheel Event Log
DD(Extension), Sequence #	Optional. Raw data for the specified sequence number.
DD(Extension), *	Optional. Raw data for all trains.

Example: Type DDS,0002 to receive Processing Summary information for sequence number 0002.

If all screen information has displayed, the APU102XP:  Main prompt displays. If more information is available, you are prompted to select Continuous (C) or Paused (P). The Continuous display screen scrolls all information about the requested train without stopping. The Paused display scrolls through the data one screen at a time.

2)  Type C or P.

If you selected (P)aused and there are more screens to display, the APU-102 prompts you with an option to press <C> to change to Continuous display, press <ESC> to exit the list, or press any other key to continue the Paused display. This process continues until all the train data has been displayed or a different selection is made.

Optional Formats

The functionality of each Dump Raw Data command extension is described below.

Dump Data Processing Summary (DDS)

The Dump Data Processing Summary (DDS) command takes the raw data and sorts it into categories that you can easily identify and use. The information is divided into six groups excluding the train header and equipment and tag summary. The groups include the Train Summary Recap, the Axle Summary, the Speed summary, the Conversion Summary, the Tagged Equipment Summary, and the Reader Summary.

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0002   Date: 05-02-11   Time: 09:02:35   ENG: OICU 812     Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON  : * :05-02-11  09:04:52/09:05:01   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:     000    Chassis:   000     Trailer:   000   Lost Axles:      000    Lost Tags:     000     Other Tags:  00   Site : test                 Lead Engine : ENG0000001    Locomotives : 2   Time : 16:02:01 01/31/96     Sequence # : 0001             Railcars : 3    Dir : LtoR (S)                 File ID : 00000001          Unknown : 0       Axle Summary       Speed Summary   Conversion Summary        --------            -----------------     ---------------------    WDA : 24    WDAB : 0        Average : 24          Status  : GOOD    WDB : 24    WDBA : 24       Maximum : 24         Lost Axles : 0       C On : 0     C Off: 48        Minimum : 24          Lost Tags  : 0        Total : 24        Tagged Equipment Summary   ----------------------------------     Locomotive : 0         Tractor : 0      Railcar : 0       Truck : 0      Container : 0        Dolly : 0       Trailer : 0       Non.Rev : 0      Chassis : 0         EOT : 0       Other : 0                               Reader Summary   ---------------------------------------------------------------------------     Tier      Tags Read    Avg Handshakes  Pred Handshakes  Performance Index    -------   --0--  --1--   --0--  --1--    --0--  --1--     --0--  --1--   Tier  0 :   1  0    0    0     14    0      0     -   Tier  1 :   0  0    0    0     0    0      -      -   Tier  2 :   0    0    0    0     0    0      -      -   Tier  3 :   0  0    0    0     0    0      -      -   End List 0001      END APU102XP: Main 1>

Figure 4.18: Dump Data Processing Summary Screen

Type the DDS command in one of the following formats:

Command Format	Description
DDS	Required. Summary of the most recent train.
DDS, Sequence #	Optional. Summary for the specified sequence number.
DDS,*	Optional. Summaries for all available trains.

Header Fields

Refer to tables 4-1 through 4-3 for header descriptions on this screen.

Data Fields

The tables below define the data fields in the different sections on the Dump Data Processing Summary screen.

Train Summary Recap

Recaps information that identifies the train.

Field	Description
Site	Site name.
Time	Time and date the train entered the site.
Dir	Direction the train was moving.
Lead Engine	Lead engine’s tag number, if read.
Sequence #	Sequence number of the train.
File ID	Permanent file identification number that the APU-102 assigns the train.
Locomotives	Number of locomotives detected.
Railcars	Number of railcars detected.
Unknown	Number of units detected that did not fit into any recognizable pattern.

Axle Summary

Summarizes the axle count for the train.

Field	Description
WDA	Number of wheel counts received on Wheel Detector A. Includes forward and backing counts.
WDB	Number of wheel counts received on Wheel Detector B. Includes forward and backing counts.
C On	Number of “C - On” pulses received over the maximum required for the axle count. Should be 0.
Total	Total number of axles on the train.
WDAB	Number of wheel transitions from Wheel Detector A to Wheel Detector B.
WDBA	Number of wheel transitions from Wheel Detector B to Wheel Detector A.
C Off	Number of “C-Off” pulses received over the maximum required for the axle count. Zero-Speed transducers should = 0; Passive transducers should = total number of A and B pulses (because C-pulse not used).

Speed Summary

Summarizes the train’s speed as it passed the site.

Field	Description
Average	Average speed of the train as it passed the site.
Maximum	Fastest speed of the train as it passed the site.
Minimum	Slowest speed of the train as it passed the site.

Conversion Summary

Summarizes the train conversion.

Field	Description
Status	Status of the way the train correlation ended up. Good = All axles and tags correlated correctly. ERR1 = An error was found in the correlation of the car section of the train. ERR2 = An error was found in the correlation of the locomotive section of the train.
Lost Axles:	Count of axles that could not be associated with a recognizable axle pattern. It does not mean the system missed any axles.
Lost Tags:	Count of tags not associated with a car, locomotive, caboose or EOT device. Test Tags are counted in this group when system testing is being done. It does not mean the system missed any tags.

Tag Equipment Summary

Totals all tags that were read for the train grouped into the following categories:

Locomotive	Chassis	Non-Revenue
Railcar	Tractor	EOT
Container	Truck	Other
Trailer	Dolly

Reader Summary

Summarizes what AEI the readers saw while recording the train.

Field	Description
Tier	Tier on which the tag was read. 0 = railcar                   1 = lower container 2 = upper container    3 = interference reader.
Tags Read	Number of tags read on each antenna where 0 = the near antenna and 1 = the far antenna.
Avg Handshakes	Average number of times the reader read each tag on each antenna where 0 = the near antenna and 1 = the far antenna.
Pred Handshakes	Predicted Handshakes. Number of handshakes the software predicts should be received based on the speed of the train and the width of the lobe.
Performance Index	Determines read performance based on the average handshakes and the predicted handshakes. Average handshakes X 100/predicted handshakes. Maximum = 999.

Dump Data Full Composite Listing (DDF)

The Dump Data Full Composite Listing (DDF) command begins with the standard train header information and continues with the “Composite AEI Listing.” This section is divided into tag-specific and non-tag-specific information for each car on the train. The DDF is a “first run” at processing the train. Further processing may occur before the final consist report is generated for transmission to the host.

Composite AEI Listing                                                      +------------------ First Tag --------------++----------------- Second Tag -------------- Rec# Car EGC   Car ID    Ts Or Pc Ax LenFT MPH  Di Tc Ti   Hnd Pre  Disqual    P# EGC LenFT Ax Pc  Ti   Hnd Pre  Disqual    P# EGC LenFT Ax Pc ---- --- --- ----------- -- -- -- -- ----- ---- -- -- ---- --- --- ----------- -- --- ----- -- -- ----- --- --- ----------- -- --- ----- -- -- 1    1   5   COMT000123  G  A  1  6  69    3.8  1  2  R0F- 43  40   ----------- -  5   71    6  -   L1R- 31  26   ----------- -  5   71    6  -   2    2   5   KCS000659   G  B  1  6  66    3.5  1  2  L0F- 39  40   ----------- -  5   68    6  -   R1R- 16  26   ----------- -  5   68    6  -   3    3   19  KCS125649   G  A  1  4  64    2.7  1  2  R0F- 64  40   ----------- -  19  67    4  -   L1R- 46  40   ----------- -  19  67    4  -   4    4   19  TTZX855310  G  A  1  4  73    1.8  1  2  R0F- 90  60   ----------- -  19  79    4  -   L1R- 11  80   ----------- -  19  79    4  -   5    5   19  KCS711108   G  B  1  4  [100] 1.1  1  2  L0F- 129 120  --L-------- -  19  79    4  -   R1R- 36  255  --L-------- -  19  79    4  -   6    6   19  UTLX025459  G  A  1  4  42    1.5  1  2  R0F- 93  120  ----------- -  19  43    4  -   L1R- 59  80   ----------- -  19  43    4  -   7    7   19  MSRC004330  G  B  1  4  62    1.8  1  2  L0F- 95  120  ----------- -  19  67    4  -   R1R- 6   40   ----------- -  19  67    4  -   8    8   19  GMSR040435  G  A  1  4  64    2.5  1  2  R0F- 87  60   ----------- -  19  67    4  -   L1R- 29  40   ----------- -  19  67    4  -   9    9   19  KCS125602   G  A  1  4  66    3.1  1  2  R0F- 59  40   ----------- -  19  67    4  -   L1R- 35  26   ----------- -  19  67    4  -   10   10  19  KCS129103   G  A  1  4  64    3.2  1  2  R0F- 48  30   ----------- -  19  67    4  -   L1R- 27  26   ----------- -  19  67    4  -   11   11  19  KCS129279   G  A  1  4  65    3.4  1  2  R0F- 59  40   ----------- -  19  67    4  -   L1R- 38  40   ----------- -  19  67    4  -   12   11  6   KCS925804   G  -  -  -  -     3.4  1  1  -0-- 28  34   ----------- -  6     -   -  -     End List 1349      END

Figure 4.19: Dump Data Full Composite Listing Screen

Type the DDF command in one of the following formats:

Command Format	Description
DDF	Required. Composite information for the most recent train.
DDF, Sequence #	Optional. Composite information for the specified sequence number.
DDF,*	Optional. Composite information for all available trains.

Header Fields

Refer to tables 4-1 through 4-3 for header descriptions on this screen.

Data Fields

The table below defines the data fields on the Dump Data Full Composite Listing screen.

Note: Some communication programs do not support 142 character display width and will word wrap or truncate at 80 (or 136) characters. DDF is best viewed by capturing or logging the display and viewing the file offline at 142 characters width.

Full Composite Listing

Field	Description
Rec#	Record number assigned by the APU-102.
Car	Location of the equipment in the train with zero (0) being the first car.
EGC	The EGC type of the equipment based on the axle pattern or tag. AAR Value Description 1 Railcar Cover 4 Train Number Tag 5/37* Locomotive  *5 is static tag, 37 is dynamic tag 6 End-of Train Device 8 Generator Set 10 Intermodal Container 14 Reserved (Formerly Non-Revenue Rail) 17 Tractor (Power) 18 Straight Truck 19 Railcar (Includes non-revenue railcars) 20 Dolly 21 Trailer 24 Rail Compatible Multi-Modal Equipment 27 Chassis 28 Passive Alarm Tag 31 Experimental User/Other
Car ID	Owners code (initials) and equipment number.
Ts	Tag status for that piece of equipment. G =Both sides tagged correctly. R =Right side tag was not read or missing. L = Left side tag was not read or missing. M =The car ID of the tags did not match. U = Untagged. E = Extra tag.
Or	Orientation of the equipment with A or B as the leading end.
Pc	Platform count for that piece of equipment based on the axles. This pertains only to multi-platform articulated and fixed draw-bar cars such as cars that carry cargo containers.
Ax	Axle count for that piece of equipment.
LenFT	Length of the car in feet based on the axles. Stopping does affect this field. Any undetermined lengths over 99 feet will be shown as [100].
MPH	Speed the car was traveling through the site. This is the average speed of all the axles.
Di	Direction recorded for that piece of equipment.
Tc	Number of tags that were read.

Tag Details

Information listed for the first and second tags read for each car. Information based on tag information and how the APU-102 interpreted it. 

Field	Description
Ti	Tag information. First digit represents the tag that was read. (L=Left; R=Right) Second digit represents the antenna that read the tag. (0 or 1) Third digit represents the orientation of the car.-(F=Front; R=Rear) Fourth digit is the tier of the intermodal tag. (T = Top; B = Bottom)
Hnd	Number of handshakes for that tag. The number of times the reader read the tag.
Disqual	List of any reasons that the tag and the car information did not match or a reason that the tag is invalid.
	I   - Track Interference O - Invalid Tag Orientation P  - Illegal Position M - Multiple Antenna L  - Length Mismatch D - Platform Code Mismatch	A -  Axle Mismatch C - Inter track Canceled E - ECG Mismatch T - Inter track Comm Failed F - Invalid Format
P#	Platform code of a multi-platform car determined by the software based on Orientation. This pertains to multi-platform articulated and fixed draw-bar cars such as cars that carry cargo containers. A single platform car does not have a platform code.
EGC	The EGC type of the equipment based on the tag programming.
	05 = Locomotive 06 = End of Train device 10 = Intermodal Container 14 = Non-Revenue Railcar 17 = Tractor	19 = Railcar 20 = Dolly 21 = Trailer 27 = Chassis 05 = Dynamic Locomotive
	Note: For a complete list of all possible EGC codes, see the EGC field definition in the Full Composite Listing section or the AAR, S918A specification.
LenFT	Length of the car in feet based on the tag programming.  (Stopping does not affect this field as it is read from the tag)
Ax	Axle count for that piece of equipment based on the tag programming.
Pc	Platform code for that piece of equipment based on the tag programming. This pertains to multi-platform articulated and fixed draw-bar cars such as cars that carry cargo containers. A single platform car does not have a platform code, but are sometimes programmed erroneously.

Dump Data Raw Tag Data (DDT)

The Dump Data Raw Tag Data (DDT) command displays raw tag data, which is the uncoded information as read by the APU-102. After the normal heading, there are five groups of information in this listing.

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0002   Date: 01-31-96   Time: 16:02:35   ENG: ENG   1      Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON  : * :05-02-11  09:04:52/09:05:01   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:  000    Chassis:    000     Trailer:   000   Lost Axles: 000    Lost Tags:  000     Other Tags: 00                                 Raw AVI Listing  #     MS   EGC    ID                         RAW TAG --- ------- --- --------- ---------------------------------------------------- 001 00000063 D ENG 000001 #*E<)P  $2RE XXXX NAS&13:58:01.41 09/04/92%00-0-FF-F   End List 0002      END APU102XP: Main 1>

Figure 4.20: Dump Data Raw Tag Data

Type the DDT command in one of the following formats:

Command Format	Description
DDT	Required. Tags for the most recent train.
DDT, Sequence #	Optional. Tags for the specified sequence number.
DDT,*	Optional. Tags for all available trains.

Header Fields

Refer to tables 4-1 through 4-3 for header definitions on this screen.

Data Fields

The table below defines the data fields on the Dump Data Raw Tag Data screen.

Field	Description
#	Sequence number. Order in which the tags were read by the APU-102.
MS	Time in milliseconds that the event occurred in relation to the start of the train.
EGC	EGC code. Equipment group code letter from the tag.
ID	Equipment ID. Decoded owner code (initials) and equipment number.
RAW TAG	Raw, undecoded tag data as read from the AEI reader. Also includes any appended reader data such as time and date, antenna number, and handshakes.

Dump Data Axle-Car Conversion Data (DDC)

The Dump Data Axle-Car Conversion Data (DDC) command lists the standard header and then breaks down each car by axle information only.

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0002   Date: 01-31-96   Time: 16:02:35   ENG: ENG   1      Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON  : * :05-02-11  09:04:52/09:05:01   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:     000    Chassis:   000     Trailer:   000   Lost Axles:      000    Lost Tags:     000     Other Tags:  00                                 Car-Axle Listing Rec#  Car#  Plat#  Start Ax.  End Ax.   Axle Count  Start Time   End Time  Type -----       -----      ------    ----------       --------            ------------     -----------            ----------        ----   1    0    -    0      5        6        0     1303  5   2    1    -    6     11       6    1715      3019  5   3    2    -     12    15       4    3430      4848  19   4    3    -     16    19       4    5145      6563  19   5    4    -     20      23       4    6861      8278  19   End List 0002      END APU102XP: Main 1>

Figure 4.21: Dump Data Axle-Car Conversion Data

Type the DDC command in one of the following formats:

Command Format	Description
DDC	Required. Cars for the most recent train.
DDC, Sequence #	Optional. Cars for the specified sequence number.
DDC,*	Optional. Cars for all available trains.

Header Fields

Refer to tables 4-1 through 4-3 for header definitions on this screen.

Data Fields

The table below defines the data fields on the Dump Data Axle-Car Conversion Data screen.

Field	Description
Rec#	Record number assigned by the APU-102.
Car#	Location of the equipment in the train with zero (0) being the first car.
Plat#	Number of the platform within the car. Articulated cars are divided into platforms that are grouped into one (1) car.
Start Ax.	Axle number in the train that the APU-102 used to begin the car with. The first axle of a train is always zero (0).
End Ax.	Axle number in the train that the APU-102 used to end the car with.
Axle Count	Total axles in the car.
Start Time	Time in the train that the APU-102 identified the first axle of the car. The start time of the first axle is always zero (0).
End Time	Time in the train that the APU-102 identified the last axle of the car.
Type	EGC code of the car as identified by the axles only.

Dump Data Wheel Event Log (DDW)

The Dump Data Wheel Event Log (DDW) command lists transducer activity for the most recent train, all available trains, or a specific train.

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0001   Date: 01-31-96   Time: 16:02:01   ENG: ENG   1      Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON  : * :05-02-11  09:04:52/09:05:01   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:     000    Chassis:     000     Trailer:   000   Lost Axles:       000    Lost Tags:    000     Other Tags:  00 Rec#   Tick Count  Disp   Type  Dir  +C   Pres? ----        ------------       -------- ----  ---  ---  ----- 1        0        0   B    0    0      Y 2         22        22   A    0    0      Y 3       137        115      B    0    0      Y 4       160        23   A    0    0      Y 5       274        114   B    0    0      Y 6       297        23   A    0    0      Y 7        1029        732   B    0    0      Y 8        1051        22   A    0    0      Y © for continuous display, (ESC) to exit or any other key to continue

Figure 4.22: Dump Data Wheel Event Log Screen

Type the DDW command in one of the following formats:

Command Format	Description
DDW	Required. Transducer activity for the most recent train.
DDW, Sequence #	Optional. Transducer activity by specific sequence number.
DDW,*	Optional. Transducer activity for all available trains.

Header Fields

Refer to tables 4-1 through 4-3 for header definitions on this screen.

Data Fields

The table below defines the data fields on the Dump Data Wheel Event Log screen.

Field	Description
Rec#	Number assigned to each wheel event.
Tick Count	Incremental time elapsed from the beginning of wheel event recording to the current specified event.
Disp	Time elapsed between one wheel event and the next.
Type	Identifies “A” or “B” segment wheel event.
Dir	Direction of train movement.
+C	Identifies presence of “C” pulse.
Pres?	Identifies state of presence circuit during that axle event

Display Parameters (DP)

The Display Parameters (DP) command displays a sub-menu of all the APU-102 parameter settings. This function is identical to the Display Parameters function in the Supervisory Menu, except passwords are not displayed. Logging into Session 1 gives access to all parameters including the other session parameters. Acquisition and hardware configuration of the equipment is also accessible to Session 1. Logging into other sessions gains access only to that session’s parameters. The Dump parameters (D) option displays at the bottom of all screens within the Display Parameters menu. The parameter dump can be captured to an ASCII file and later restored to the system using the Edit Parameters (EP) function in the Supervisory Menu.

Note: Version 5.1.1B103 has added capability of dumping parameters to an on-board file. 

Display Parameters -     1. Session1     2. Session2     3. Session3     4. Session4     5. LocalSupport     6. RemoteSupport     7. Acquisition     8. Ports     9. DiskManager    10. TimeZoneControl    11. DaylightSavings    12. SysDiags    13. DebugFlags    14. NetMenu    15. SupportThreads    16. MoreSessions [D]ump parameters, e[X]it >

Figure 4.23: Display Parameters Menu Screen

All options may not be available depending on software version

1)  Type the DP command and press <Enter>.

2)  Enter one of the parameter options (1-16) at the screen prompt. Enter any sub-menu options to view the desired parameters.

3)  To initiate a parameter dump, type D and press <Enter>. The APU-102 will prompt you to press <Enter> to start the dump. This gives you an opportunity to start your capture file before starting the dump. The dump can be run from any level where the “[D]ump parameters” prompt shows on the bottom of the screen.

If 5.1.1B103 or later you can capture your parameter dump to a file on-board the APU-102. This file can be downloaded after completion using a more reliable transfer protocol (such as ZMODEM) Type DF and press <Enter>. (The DF option might not be displayed on the prompt) You will be prompted to supply an on-board file name.

Progress of either dump mode will be displayed.

4)  Type X and press <Enter> to go up one level, but only when the “e[X]it” prompt shows on the bottom of the screen.

Press <ESC> to go up one level at any time.

Change to Supervisory Menu (C)

The Supervisory Menu (C) is submenu of the System Menu and can only be accessed with the proper authority and password. The password assigned for access to the Supervisory Menu may or may not be the same as the System Menu password. It is recommended that the password for the two menus be different in order to limit the number of people that can make changes to the parameters or reset the system. Main Menu commands are accessible from the Supervisor menu.

1)  Type the C command at the APU102XP:  Main prompt. The date, time, and password field display.

2)  Type the designated Supervisory Menu password and press <Enter>. Asterisks (*) display as you type the characters.

3)  Type your name and press <Enter> at the Enter Your Name prompt. If the password was entered correctly, the “Welcome to” message displays and the cursor appears at the APU102XP:  Change prompt.

4)  Type <?> and press <Enter>. The Supervisory Menu displays.

Tip	Entering the supervisory password at the initial log on screen will log directly to the Supervisory Menu (version 5.10+).

For a screen example and information on moving around the Supervisory Menu, refer to the Supervisory Menu section later in this article.

Display I/O Information (I)

The Display I/O Information (I) command displays the state of the Input/Output (I/O) in a real time mode.

APU102 I/O Status Display -------------------------
Block	#	Label	I/O	State >	Block	#	Label	I/O	State
-----	--	---------	---	------	+	-----	--	---------	---	------
Main	7	PresIn	I	Clear >	Main	9	PresOut	O	Clear
Main	15	DTrkPres	I	Clear >	Main	16	DTrkPres	O	Clear
----	--	WDA	I	0 >	Aux1	7	ClkSync	O	1
----	--	WDB	I	0 >	Aux!	9	WatchDog	O	1
Aux1	5	WDC	I	0 >	Aux2	9	SensorPwr	O	On
Aux2	1	WDD	I	0 >	Aux2	11	SpareOut	O	1
----	--	VTP R0,A0	I	Off >	----	--	RFOn R0,A0	O	Off
----	--	VTP R0,A1	I	Off >	----	--	RFOn R0,A1	O	Off
----	--	VTP R1,A0	I	On >	----	--	RFOn R1,A0	O	Off
----	--	VTP R1,A1	I	On >	----	--	RFOn R1,A1	O	Off
Aux2	7	VTP R2,A0	I	Off >	Aux2	15	RFOn R2,A0	O	On
Aux2	5	VTP R2,A1	I	Off >	Aux2	13	RFOn R2,A1	O	On
Main	11	24VAC	I	Fail >	----	--	Sys LED	O	On
Aux1	3	Progrmble	I	Clear >	----	--	Sys Button	I	Out
----	--	RsrfcSens	I	1 >	----	--	SW3 Button	I	Out
Aux2	3	24VDC	I	Ok >	----	--	SW2 Button	I	Out
----	--	Phone Sel	O	Line 1 >	----	--	SW1 Button	I	Out

Figure 4.24: APU102 I/0 Status Display Screen

Type the I command in one of the following formats and press <Enter> at the APU102XP:  Main prompt.

Command Format	Description
I	Required. Displays the standard I/O.
I,C	Optional. Displays configurable inputs and counters, if present.

There are no special inputs configured. There are no special counters configured. There are no alarms configured. APU102XP: Main 1>_

Figure 4.25: I,C Command Display (No Inputs, Counters, or Alarms Configured)

Header Fields

This screen has no standard header fields.

Data Fields

The following table defines the data fields on the APU102 I/0 Status Display screen.

Field	Description
Block	Connection block for DC power, wheel detectors, and AC monitoring or input/output channels. (Green connector blocks on bottom of APU-102)
#	Block pin number.
Label	Name for input or output signal.
I/O	Indicates whether the signal is an input or an output. (I or O)
State	The condition of the signal.

Train Logger Reports (TL)

Using the Train Logger Reports (TL) command with a valid extension displays a log of train related events, consist host transaction events, and maintenance host transaction events for a specific train or all trains. The displayed information defaults to the most recent train. Type the TL command in one of the following formats:

Command Format	Description
TL(Extension)	Required. Command code followed by the selected extension. Valid extensions: T = Train related events. C = Consist host transaction events. M = Maintenance host transaction events.
TL(Extension), Sequence #	Optional. Transaction events for a specific sequence number.
TL(Extension),*	Optional. Transaction events for all trains.

Optional Formats

Below are the optional formats and their command code.

Train Log - Train Events (TLT)

The Train Log - Train Events (TLT) command lists the standard train header followed by an event log listing events associated with the train selected. Use this command to determine if anything occurred to affect the consist and to dump an event log associated with the train. Except for specific messages that are always logged in the train log, this information is only available if enabled with the DiskManager.TrainLogEnable parameter. (See below for list of these messages that are always on.) The format of the listing is similar to that viewed with the SYS command in the Supervisory Menu.

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1 Train Seq #0005   Date: 02-22-96   Time: 16:46:06   ENG: ENG   1      Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON   : * :00-00-00  00:00:00/00:00:00   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:     000    Chassis:     000     Trailer:   000   Lost Axles:       000    Lost Tags:    000     Other Tags:  00 96-02-22 16:45:54 REMOTE  0005 ST Function          name 96-02-22 16:45:56 RECORD  0005 Record Complete      0000 0276 96-02-22 16:46:07 RECORD  0005 Simulated Event        0000 0000 96-02-22 16:46:10 RECORD  0005 Presence Clear       0018 0005   End List 0005      END APU102XP: Main 1>

Figure 4.26: Train Log - Train Events Screen

The following messages are always logged in the system log, regardless of the parameter setting.

• Pres Circuit Failure
• Pres Circuit Warning
• Wheel Det Failure
• Wheel Det Warning
• Antenna Failure
• Antenna Fail Warning
• Extern Com Failure
• Extern Com Warning
• AEI Reader Failure
• AEI Reader Restored

Train Log - Consist Host Transaction Events (TLC)

Lists the communications events that occurred as the APU-102 reported the specified train(s) to the host. Log is maintained relative to the train sequence when communications occur (time period from the last train to completion of this train). If no log is present, host transaction logging is probably turned off or consist communications did not occur during the logging period. This information is available only if the AEIReportOpts.TransactionLogger parameter is enabled for the specific session. Set this parameter to 0 to turn host report logging off.

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0005   Date: 02-22-96   Time: 16:46:06   ENG: ENG   1      Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON   : * :00-00-00  00:00:00/00:00:00   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:     000    Chassis:     000     Trailer:   000   Lost Axles:      000    Lost Tags:     000     Other Tags:  00 Event log file not found.   End List 0005      END APU102XP: Main 1>

Figure 4.27: Train Log - Consist Host Transaction Events Screen

(Usually disabled so log file doesn’t exist)

Train Log - Maintenance Host Transaction Events (TLM)

Lists the communications events that occurred as the APU-102 reported maintenance information around the time of the current train to the maintenance host. Log is maintained relative to the train sequence when communications occur (time period from the last train to completion of this train). If no log is present, host report logging is probably turned off or maintenance host communications did not occur during the logging period. Set this parameter to 0 to turn maintenance report logging off. This information is available only if the MaintReportOpts.TransactionLogger parameter is enabled for the specific session.

Nicholson Ave        MP: 0000.0 Station 00001  Reader 1  Train Seq #0005   Date: 02-22-96   Time: 16:46:06   ENG: ENG   1      Dir: S   MPH: 024    Axles: 0024   WDA = 024   WDB = 024   WDAB = 000   WDBA = 024      HOST REPORT:  ON   : * :00-00-00  00:00:00/00:00:00   Loco Cnt:    02    Loco Tags:   01     Loco Xtags: 01   Car Cnt:    003    Car Tags:   000     Car Xtags: 003   Container:  000    Chassis:    000     Trailer:   000   Lost Axles: 000    Lost Tags:  000     Other Tags: 00 Event log file not found.   End List 0005      END APU102XP: Main 1>

Figure 4.28: Train Log - Maintenance Host Transaction Events

(Usually disabled so log file doesn’t exist)

Pass-through to Port (PT)

This function allows the operator to establish a connection directly to the port specified in the port parameter file if it is not in use by another process.

1)  Type the PT command in the following format:

Command Format	Description
PT	Required. Command code.
Port parameter filename	Required. The parameter filename of the port.

The following message displays:

Remote passthru session established. Press <ESC C> to terminate session.

2) Press <Esc> then uppercase <C> to terminate. If idle, the session automatically terminates after five minutes. The following message displays:

Remote passthru session terminated. APU102XP: Main 1>

Command Examples:

PT,$REMPORT.DAT - Connect to the modem port.

PT,$LOCPORT.DAT - Connect to the external LOCAL port.

PT,AVI1PORT.DAT - Connect to the reader 0 port.

PT,AVI2PORT.DAT - Connect to the reader 1 port.

PT,AUX1PORT.DAT - Connect to the external AUX DATA-1 port.

PT,AUX2PORT.DAT - Connect to the external AUX DATA-2 port.

PT,NETMODEM,IP  - Connect to the another port on the network.

PT,ETHERNET,IP  - Connect to the another port on the network.

Pass-through to Reader (AMT)

The Pass-through to Reader (AMT) command allows you connect directly to the reader card and, if necessary, make changes to the reader card programming. This command should not be used without knowledge of the APU-102 software and the AI1200 reader card command set. All reader related commands will not operate if the reader is currently servicing a train.

1)  Type the AMT command in the following format:

Command Format	Description
AMT	Required. Command code.
0-2	Required. The 1-digit reader number.

The following message displays:

Remote passthru session established. Press <ESC C> to terminate session.

2)  Press <Esc> then uppercase <C> to terminate the session. If idle, the session automatically terminates after five minutes. The following message displays:

Remote passthru session terminated. APU102XP: Main 1>

Check Tag Sequence (CT)

The Check Tag Sequence (CT) command provides a way of verifying that the antennas, RF unit, and reader card are working correctly. When using the CT command locally and the Sonalert is on, you hear a beep when each check-tag is read and visually, the appropriate reader’s LOCK LED will light.

Check Tag [Reader: 0] [Antenna: 0] [Status : OK] Check Tag Data:  0000000000000   00&12:54:09.17 05/31/95 Check Tag [Reader: 0] [Antenna: 1] [Status : OK] Check Tag Data:  1111111111111   00&12:54:10.47 05/31/95 Reader #1 is not in current configuration. Reader #2 is not in current configuration.

Figure 4.29: Check Tag Sequence Screen

Type the CT command in one of the following formats and press <Enter>:

Command Format	Description
CT	Required. Command code.
0 - 2, or *	Required. Selected reader number. The asterisk (*) specifies all readers.
0, 1, or *	Required. Selected antenna number. The asterisk (*) specifies all antennas.

Example: Type CT,0,* to activate the Check Tag Sequence for the first reader, both antennas.

NOTE	A check tag must be installed inside at least one antenna per track covered. It may not indicate a failure if a failure message is returned from the antenna not containing the check tag.

Initialize Reader (IR)

The Initialize Reader (IR) command initializes the Amtech reader hardware. It resets all the reader commands to the required APU-102 settings. Even if the communication parameters have been changed, the APU-102 searches all the available communication parameters to connect to the reader. Using the IR command is very helpful if the user cannot connect to the reader or there appears to be a problem with the reader card. With one command you may choose to initialize one reader or all readers.

Type the IR command in the following format:

Command Format	Description
IR	Required. Command code.
0-2, *	Required. 1-digit reader number (0-2) or asterisk (*) for all readers.

Example: Type IR, 0 to initialize reader number 0.

The following message displays the selected reader (or readers):

 

Reader #0 initialization complete. APU102XP: Main 1>

Figure 4.30: Initialize Reader Screen

Activate Reader RF (RFON)

The Activate Reader RF (RFON) command is a diagnostic tool that allows you to activate the RF of a reader or antenna. Either antenna may be turned on individually or together. Only one reader can be activated at a time.

1)  Type the RFON command in the following format:

Command Format	Description
RFON	Required. Command code.
0-2	Required. 1-digit Amtech reader number.
0-1 or *	Required. 1-digit antenna number or asterisk (*) for all antennas.

Example: Type RFON, 0, * to activate the RF for reader 0 and all antennas.

The APU-102 displays the following message stating what has been turned on and that it is waiting for the antenna to read a tag.

APU102XP: Main 1>rfon,0,* --------------------------------------- RF Is ON [Reader: 0] [Antenna: 0 & 1]. Press any key to turn RF off... --------------------------------------- #*C2??$@:U2H-(4&< NAS&16:52:39.91 12/28/98%00-1-06-F #*C2?0$K8X2G.1=”$ NAS&16:52:59.73 12/28/98%00-0-00-F #FC$L $&<HAD      NAS&16:53:13.74 12/28/98%00-1-05-F Waiting for tag... Flushing Tags...                      RF Is OFF.                   APU102XP: Main 1>

After a tag is read, the raw (un-decoded) tag information displays.

2)  Press any key to remove the tag data from the system and turn off the RF. The following message displays:

Flushing tags..... RF Is OFF.

=== Reader Interface Self Test (RST) ===

Use the Reader Interface Self Test (RST) command to determine if the APU-102 can communicate with any of the readers installed in the system. This screen displays the type of tests and the test results. This can be extremely valuable when troubleshooting a site that is not reading tags. It does NOT activate the RFID subsystem.

AI1200 Reader Test                                         Status --------------------------------------------------------------------------- Reader 0: Communications............................. OK Reader 0, Antenna 0: Rf Control Line.................OK Reader 0, Antenna 1: Rf Control Line.................OK Reader 0, Antenna 0: Antenna Handshake Line..........OK Reader 0, Antenna 1: Antenna Handshake Line..........OK All Tests Passed........     ........................      NORMAL

Figure 4.31: Reader Interface Self Test Screen

Type the RST command in one of the following formats and press <Enter>:

Command Format	Description
RST	Required. Command code.
0-2, *	Required. Selected reader number or asterisk (*) to indicate all readers.

Example: Type RST, 2 to test the communication between the APU-102 and reader number 2.

Data Fields

Field	Description
AI1200 Reader Test	Displays the reader number (0-3) and the type of test being reported.
Status	Displays the results of the test.

Print Match List (MA)

Print Match List (MA) is used in Distributed Processing Systems. Any time a new local train is recorded, the software must scan all trains it received from other sites that are within a defined “time window” looking for matches.

Refer to the APU103 Installation & Operation Manual' for additional information.

Compare Two Trains (CMP)

Compare Two Trains (CMP) is a diagnostic tool used in Distributed Processing Systems. It does a car-by-car comparison of 2 trains to help determine why a match was not found.

Refer to the APU103 Installation & Operation Manual' for additional information.

Main Help Screen (?)

Type ? to re-display the current menu screen.

Confidence Logic Parameters (CNF)

This function displays how the Confidence Logic Parameters are configured for the current session. Changes are made in the appropriate session’s AEI Report Option parameters.

 

AEI CONFIDENCE LOGIC PARAMETERS    The following parameters are used to filter AEI data from outgoing consists based on software comparisons between AEI tag information and axle generated car information.                             Current Settings             ------------------------------------------------                          Default Confidence Level :  3       Double Track Active Confidence Level :  2                     ITC Failure Confidence Level :  1         Conditional Options                       Confidence Level Options -----------------------------------                     ------------------------------------- D - Default. Used when no abnormal      0 - Tags are not reported.     conditions exist.                                  1 - Tag is reported only if both left T - Double Track Active. Used when          and right tags were read.     train is active on adjacent track.          2 - Single tags are reported only if F - Intertrack Communications Failure.      no discrepancies exist between     Used when APU cannot access data        car and tag information.     on adjacent track's APU.                       3 - All tags are reported.

Supervisory Menu

Overview

The Supervisory Menu allows you to change parameters, run diagnostic tests, and reset the APU-102. It is password-protected and should only be used by persons authorized to make parameter changes that are vital to the APU-102. Note: Main Menu commands (and help) are accessible from the Supervisory Menu.

APU102 SUPERVISORY MENU
HR              Host Reporting Options	*MR           Master System Reset
*EMS          Edit Message Status	*SR            System Status Reset
*VM            Version Maintenance	RMS           Reset Maintenance Sequence
SYS            System Status Info	*R               Reboot Unit
DIR             Directory Listing	*WT            Watchdog Test
TYPE          Type a File	ZSEND       Zmodem Send File(s)
ZREC          Zmodem Receive File(s)	ZSENDMA  Zmodem Train and Matched Files
ZRECR        Zmodem Receive Restart	XSEND       Xmodem Send File
XREC          Xmodem Receive File	XSEND1k   Xmodem1k Send File
ZPUT           Local ethernet file xfer	ZGET          Local ethernet file xfer
IPCONFIG   Check Network Settings	PING           Packet Internet Groper
*T                 Set Date/Time	RA               Reassociate all Trains
X                  Exit to Main Menu	SHELL        DOS Command
*RHS           Run Hardware Setup	MAIN?        Main Menu Help
EP               Edit Parameters	?                 This Screen
CLEAN        System cleanup
For help on a command, enter the command followed by a '?' All main menu commands are available as well, type MAIN? for help * - Available to Session #1 Only

Figure 4.32: Supervisory Menu

Menu may vary depending on AEI Application version. If not detailed in this text, refer to the on-board help.

1)  Type the C command at the APU102XP:  Main prompt from the System Menu screen. The APU-102 requests password entry.

2)  Type the Supervisory Menu password and press <Enter>. If you enter an invalid password, the “Invalid Password” message displays.

3)  Type your name and press <Enter>. A “Welcome To” message displays, followed by the APU102XP:  Change prompt.

4)  Type <?> and press <Enter> to display the Supervisory Menu.

The Supervisory Menu is the same for all sessions except the items with the asterisk (*). These items are only accessible from if logged into Session 1. The information displays in the format selected for that particular session.

Supervisory Menu Screens

Host Reporting Options (HR)

The Host Reporting Options (HR) command displays or changes host reporting with several different options. All are specific to the session you are logged into.

1)  To view or change Host Reporting options, select one of the following command format options and press <Enter>.

Command Format	Description
HR	Required. Displays current host reporting status, either “Activated” or “Deactivated”. This command does not change the status of the host reporting option.
HR,OFF	Optional. Turns off host reporting. This command suspends reporting of any train information to host system. New train entries will be stored with a report status in the train directory of “N”, for NO report sent.
HR,INI	Optional. Initialize or change the host password for COMPASS reports.
HR,ON,N	Optional. Activate host reporting; report only new trains.
HR,ON,A	Optional. Activate host reporting; report all trains.
HR,ON,#	Optional. Activate host reporting with Age Threshold. # = Age Threshold in hours (0-9).
HR,####	Optional. Requests re-transmission of a particular train. #### = Sequence number of the requested train. By entering a sequence number after the HR command, the requested train sequence number is placed in the queue for reporting. This feature will not operate unless host reporting is enabled and the train falls within reporting options.
HR,NOW	Suppresses reporting wait times from consist and maintenance processes and causes immediate transmissions of pending reports. (Version 5.10B2 or later)

A screen message displays the action taken on the Host Reporting Option. The following example shows a screen display if HR is entered.

APU102XP: Change 1>hr *********** Host Reporting Activated *********** APU102XP: Change 1>

Edit Message Status (*EMS)

The Edit Message Status (EMS) command allows you to remotely change (enable or disable) the reporting status of messages in maintenance reports. Some critical messages are always logged and cannot be disabled with this function. This function has no effect on the messages appearing in the system status log.

MSG #000: Unit Startup ENABLED <E>nable or <D>isable or <ENTER> for current status: MSG #001: User Abort ENABLED <E>nable or <D>isable or <ENTER> for current status: MSG #002: APUERROR.DAT #2 ENABLED <E>nable or <D>isable or <ENTER> for current status: MSG #003: APUERROR.DAT #3 ENABLED <E>nable or <D>isable or <ENTER> for current status: MSG #004: Presence Startup ENABLED <E>nable or <D>isable or <ENTER> for current status: MSG #005: Presence Clear ENABLED <E>nable or <D>isable or <ENTER> for current status: msg #006: Process Startup ENABLED <E>nable or <D>isable or <ENTER> for current status: MSG #007: APUERROR.DAT #7 ENABLED <E>nable or <D>isable or <ENTER> for current status: MSG #008: Dos Error ENABLED <E>nable or <D>isable or <ENTER> for current status:

Figure 4.33: Edit Message Status

1)  Type the EMS command and press <Enter>. The first message displays and requests you to select <E> to enable, <D> to disable, or <Enter> to bypass.

MSG #000: Unit Startup ENABLED <E>nable or <D>isable or <ENTER> for current status: MSG #001: User Abort ENABLED <E>nable or <D>isable or <ENTER> for current status: MSG #002: APUERROR.DAT #2 DISABLED <E>nable or <D>isable or <ENTER> for current status: E Status change to ENABLED

Figure 4.34: Example: MSG #002 Changed to ENABLED

2)  Select <E>, <D> or press <Enter>. The next message and its associated number display.

3)  Continue enable/disable selections for each message that displays.

4)  Press <ESC> to exit the EMS command.

Version Maintenance (*VM) (not implemented for version 5.0+)

Use the Version Maintenance (VM) command to change the software version running on the APU-102. If for some reason the software needs to be changed, the VM command displays the software versions that are available.

Version Maintenance (VM) Menu #  Cur  Version    Run File                Description -  ---    -------        ------------      ---------------------------------- 1        4.20     APUV4_20     T94 4.12 + Zmodem reporting 2   *    4.23     AP423        APU102 V4.23 (Base), T94 V4.12 Options ------------------------------ V - Change current version C - Clear changes D - Delete version X - Return to previous menu Enter option:

Figure 4.35: Version Maintenance Screen

1)  Type the VM command and press <Enter>. The Version Maintenance menu displays.

2)  Enter a number that corresponds to the desired version. Within the VM command, all sub-commands are hot-keyed (no need to follow with <Enter>).  Valid values are:

V - Change current version.

C - Clear changes.

D - Delete version.

X - Return to previous menu.

3)  You will be presented with choices depending on command selected. Answer as appropriate.

System Status Info (SYS)

The System Status Info (SYS) command displays the system status log. This log provides a list of all APU-102 activities. The size of the System Status Info file is limited and can fill quickly if the site is very busy or has a problem. If the site is not very active and everything is working well, the log may contain information for several days. The size of the log file can be specified by the SR command.

1)  Type the SYS command to bring up the Process Identification Menu (PID).

PID   Process            PID   Process ------------------------------------------- 0      ALL                 |  11    REPORT1 1      MAIN              |  12    REPORT2 2      RECORD       |  13    REPORT3 3      FSB                |  14    REPORT4 4      CLOCK           |  15    MAINT1 5      REMOTE        |  16    MAINT2 6      LOCAL           |  17    MAINT3 7      AVI1               |  18    MAINT4 8      AVI2                |  19    AXLE 9      AVI3                |  20    DISKMGR 10     AVI4               | Enter the appropriate PID Number:

Figure 4.36: Process Identification Menu

PID menu may vary depending on AEI Application version. Example is version 4.25

2)  Select the type of status log, or PID, to review. Software is under constant development and options may be added or reassigned.

3)  The APU-102 prompts you to select (C)ontinuous or (P)aused display. Type C or P. The selected status log displays the available records.

In the following screen example, the Main process (PID #1) in Paused (P) display was selected:

Comet Electronics Automatic Equipment Identification System APU Software Version 4.23 AMTECH Model AI1200 Ver 2.80 SN97514 Wed 06/30/04  16:43:26 Host Reporting: On, All Last LOGON: Wed 06/30/04  16:37:45 05-16-04 10:29:41 MAIN    0000 Clock Resync           ASCII Data Time before sync Sun May 16 10:29:39 2004 05-16-04 10:29:41 MAIN    0001 Unit Startup           ASCII Data  Halli                 APUV4_20 03-03-1998 04:20:00 05-16-04 10:36:27 MAIN    0001 Unit Startup           ASCII Data Halli:AP43 09-02-1998 04:23:00   End of System Status     END APU102XP: Change 1>

Figure 4.37: System Status Info Screen

It is possible that the status log will not have any records for the selection made. The APU-102 then displays the header information and the END statement.

Archived System Status Info (ASYS) Version 5.2+

Still under development to SQLite database and command structure is likely to change.

The Archived System Status Info (ASYS) command is like the standard SYS log, but for archived files. You will be prompted for PID and starting/ending date and times. This report provides a list of all APU-102 activities for the specified PID and date/time range.

PID  Process  PID  Process    PID Process   PID Process -------------------------------------------------------  0   ALL     | 24  ERROR    | 81  XTRKSERV |  1   MAIN    | 25  GEHBD    | 82  XTRKMON  |  2   RECORD  | 26  ETHOBS   |              |  3   FSB     | 27  ODM      |              |  4   CLOCK   | 28  IDM      |              |  5   REMOTE  | 29  TALKER   |              |  6   LOCAL   | 30  NTP      | 101 REPORT1  | 111 MAINT1  7   AVI1    | 31-36 TELNET | 102 REPORT2  | 112 MAINT2  8   AVI2    | 41-50 DETECT | 103 REPORT3  | 113 MAINT3  9   AVI3    | 51-60 XTRACK | 104 REPORT4  | 114 MAINT4  10  AVI4    | 61-70 NETMDM | 105 REPORT5  | 115 MAINT5  19  AXLE    | 71  XTPMON   | 106 REPORT6  | 116 MAINT6  20  DISKMGR | 72  XTP      | 107 REPORT7  | 117 MAINT7  21  SCALE   | 73-76 COMBOM | 108 REPORT8  | 118 MAINT8  22  WDOG    | 77  CAH      | 109 REPORT9  | 111 MAINT9  23  ITC     | 78  ACQPROC  | 110 REPORT10 | 120 MAINT10 Enter the appropriate PID Number: 2 Display entire archive contents? (if Y, bypasses Date/Time entries) Beginning date and time of archive: Enter New Date mm/dd/yyyy >01/01/2012 Enter New Time hh:mm:ss   >00:00 Ending date and time of archive: Enter New Date mm/dd/yyyy >01/02/2012 Enter New Time hh:mm:ss   >23:59 (C)ontinuous or (P)aused display? :

Figure 4.38: Process Identification Menu PID menu may vary depending on AEI Application version. Example is version 5.2+

Directory Listing (DIR)

The Directory Listing (DIR) command displays the file directory on the APU-102 with wildcard support.

Type the DIR command in the following format:

Command Format	Description
DIR	Required. Command code will display the entire file directory for all files.
DIR filespec	Optional. Command code and the desired file specification. Displays the file directory specified by filespec.
DIR filespec /p	Optional. Displays the directory specified by filespec in paused mode. Press any key to continue through the listing.

The directory listing displays:

<DIR>      96-01-17  12:33               <DIR>      96-01-17  12:33 DM144S  INI        441   95-06-26  11:39 SPT94    CFG        741  95-04-19  16:33 APUV4_14 EXE     157440  95-11-03   8:40 TERMINAL ACC        125  95-05-10  13:14 TERMSTAT ACC        125  95-05-10   8:55 SPHOST   ACC        167  94-03-22  13:19 CRMAINT  ACC        162  94-08-08  10:45 CPMAINT  ACC        361  95-08-07  15:19 ATSRPRT  CFG        742  95-04-19  16:35 UP       TLR          2  95-04-21   8:28 UPT94    CFG        740  95-06-30   7:53 CRT94    CFG        741  95-04-19  16:33 BNMAINT  ACC        223  95-05-10   8:56 MAINTERM ACC        125  95-05-10   8:55 KCSFEP   ACC        243  94-08-08  10:43 MCM2400  INI        584  93-11-01  13:22        132 file(s)  261750 bytes  725504 bytes free

Figure 4.39: Directory Listing Screen (excerpt)

The filespec may contain asterisk <*> or question mark <?> wildcard characters. Press <ESC> twice to quit the directory listing. Typing </p> after the command displays the directory listing in paused mode. The size and timestamp of each file are displayed. At the end of each directory listing is a summary including the number of files in the listing, the total number of bytes in the files listed and the bytes available on the disk.

Type a File (TYPE)

The Type a File (TYPE) command displays the contents of specific files on the APU-102. Large files may scroll off the screen.

APU102XP: Change 1>type modem.ini ATZS0=0 ATE0 ATV0 AT&C1 AT&D2 AT\N3 ATS7=60 ATX1 ATS0=1

Figure 4.40: Type a File Screen

1)  Enter the TYPE command in the following format:

Command Format	Description
TYPE	Required. Command code.
Filename for contents display	Required. The name of the APU-102 file for which you want to display contents.

2)  For more convenient viewing of larger files, you may capture the output to a log file or download with ZSEND.

Zmodem Receive File(s) (ZREC)

The Zmodem Receive File(s) (ZREC) command places the APU-102 in Zmodem receive mode. Zmodem can receive multiple files.

1)  Type the ZREC command in the following format:

Command Format	Description
ZREC	Required. Command code.
Path	Optional. The file path must be specified if directory location of the file to be received is not in the default directory.

Note: The path option is not available on application versions prior to 5.0. Files are received into the default path only.

The message “Ready to receive” displays.

2)  Once the APU-102 is in the receive mode, use the Zmodem protocol on your communications program to initiate a file transfer or a file upload. Use wildcards (* or ?) to upload multiple files. Refer to your communications software package for instructions on sending the file.

After file is received, the message “N file(s) received successfully” displays. (N representing the number of files.)

If there are errors in the modem’s transmission, one or all of the following messages may display (where N represents the number of files).

N port overrun errors	Serial port has at least one overrun.
N byte framing errors	Serial port has at least one framing error.
N parity errors	Serial port has at least one parity error.

These errors are normal and the Zmodem protocol is designed to correct for them. If they become excessive, you may need to repair either the serial port or the modem.

Zmodem Receive Resume (ZRECR)

The Zmodem Receive Resume (ZRECR) command places the APU-102 in Zmodem receive restart mode to resume a failed file transfer. Zmodem can receive multiple files. If a file already exists on the unit, Zmodem resumes transfer of the existing file at the point where the previous transfer was interrupted. With ZRECR, previously interrupted transmissions can continue, which saves time.

Note: The resume is done blindly, with no checks to ensure that the existing file has the same contents (up to the point of interruption) as the sent file. This means that if the file is a different version, the new file may be corrupted. Only use ZRECR on file transfers that you know were previously interrupted.

1)  Type the ZRECR command in the following format:

Command Format	Description
ZRECR	Required. Command code.
Path	Optional. The fill path must be specified if directory location of the file to be received is not in the default directory.

Note: The path option is not available on application versions prior to 5.0. Files are received into the default path only.

The message “Ready to receive” displays.

2)  Once the APU-102 is in the receive mode, use the Zmodem protocol on your communications program to initiate a file transfer or a file upload. Use wildcards (* or ?) to upload multiple files. Refer to your communications software package for instructions on sending the file.

After file is received, the message “N file(s) received successfully” displays. (N representing the number of files.)

If there are errors in the modem’s transmission, one or all of the following messages may display (where N represents the number of files).

N port overrun errors	Serial port has at least one overrun.
N byte framing errors	Serial port has at least one framing error.
N parity errors	Serial port has at least one parity error.

These errors are normal and the Zmodem protocol is designed to correct for them. If they become excessive, you may need to repair either the serial port or the modem.

Xmodem Receive File (XREC)

The Xmodem Receive File (XREC) command allows files to be transferred to the APU-102 using the Xmodem protocol.

1)  Type the XREC command in the following format:

Command Format	Description
XREC	Required. Command code. Places the APU-102 in Xmodem receive mode.
Path	Optional The file path must be specified if directory location of the file to be received is not in the default directory.
Filename	Required. The filename that the transferred file assumes.

The message “Ready to receive” displays.

2)  Once the APU-102 is in the receive mode, use the Xmodem protocol to initiate a file transfer or a file upload.

3)  Refer to your communications software package for instructions on sending the file.

Local Ethernet File Transmit (ZPUT)  

This command is used to transfer a single file between units residing on the same network. This similar to the ZSend function, except that it is only available to perform network transfers. This command ALWAYS send the entire file from the beginning (ZPutR can be used to resume transfers that were interrupted).

Type the ZPUT command in the following format:

ZPUT	Required. Command code.
Filename for transfer	Required. The file specification of the APU-102 file send to another unit on the local network. Wildcards are not permitted.  Use caution with this command as it will overwrite an existing destination file.
IPAddressOrURL	Required. Network address of destination computer.
IPPort	Optional. IP Port on the destination computer. Defaults to 23 on the APU.

Local Ethernet File Transmit Resume (ZPUTR)  

This command can be used to resume a ZPUT file transfer that was interrupted.

Note: The resume is done blindly, with no checks to ensure that the existing file has the same contents (up to the point of interruption) as the partial file. This means that if the file is a different version, the new file may be corrupted. Only use ZPUTR on file transfers that you know were previously interrupted.

Type the ZPUTR command in the following format:

Command Format	Description
ZPUTR	Required. Command code.
Filename for transfer	Required. The file specification of the APU-102 file send to another unit on the local network. Wildcards are not permitted.  Use caution with this command as it may overwrite or corrupt an existing destination file. (see note above).
IPAddressOrURL	Required. Network address of destination computer.
IPPort	Optional. IP Port on the destination computer. Defaults to 23 on the APU.

Check Network Settings (IPCONFIG)

Identical to the simple Windows command line IPCONFIG (no options).

Type the IPCONFIG command and press <Enter>.

ipconfig < y.dat 1> dosshell.txt 2> dosshll2.txt Windows IP Configuration Ethernet adapter Local Area Connection: Connection-specific DNS Suffix  . : IP Address. . . . . . . . . . . . : 192.168.1.102 Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : 192.168.1.1

Figure 4.41: Sample IPCONFIG Response Screen

For advanced options and switches, run IPCONFIG under the SHELL command.

Set Date/Time (*T)

The Set Date/Time (T) command displays and sets the APU-102 date and time.

Current time Sun Jun 01  13:30:18 2004 Enter New Date mm/dd/yyyy >06/01/2004 Enter New Time hh:mm:ss   >13:30:18 New time Sun Jun 01 13:45:00

Figure 4.42: Set Date/Time Screen

1)  Type the T command and press <Enter>.

2)  Type the date in the format indicated and press <Enter>.

3)  Enter the time in military time format (24-hour clock, hh:mm:ss) and press <Enter>. The new date and time you established displays at the bottom of the screen.

Note: The time zone is set using the Edit Parameters (EP) command and selecting TimeZoneControl.

Exit to Main Menu (X)

Type the X command to exit the Supervisory Menu and return to the System Menu.

Run Hardware Setup (RHS) LPMTX with 5.0+ only

The Run Hardware Setup (RHS) utility is used whenever the hardware in the APU changes. The Windows XPe Operating System needs to identify hardware changes independent of the AEI application parameters. Select this function to set the APU-102 to run the Hardware Setup routine at next power up. The Startup ROM must be disabled to run the routine.

1)  Type the RHS command and press <Enter>. The following warning message displays and offers a chance to abort the command.

WARNING: THIS WILL SET THE UNIT TO RUN HARDWARE SETUP. Continue (Y/N)?

2)  Press <N> to cancel and return to the APU102XP:  Change prompt or press <Y> to continue. If <Y> is selected, the following message displays:

THE APU HAS BEEN SET TO RUN HARDWARE SETUP PLEASE POWER OFF UNIT AND FOLLOW HARDWARE SETUP PROCEDURE. TYPE "RHS?" FOR MORE INFORMATION.

Hardware Setup Procedure (following RHS command):

1)  Power off the APU.

2)  Remove the LPM-TX Pentium card.

3)  Remove the Startup ROM at U1 on the PCM-SSD card (daughter-card on Pentium card). Refer to Appendix F for ROM location

4)  Reinstall the LPM-TX Pentium card.

5)  Power on the APU. The hardware setup program runs automatically. The APU will reboot itself during the process and when completed, will indicate with a 3-blink, pause, and repeat pattern on the SYS LED. If Watchdog timer reboots the APU, it will return to this state.

6)  Power off the APU.

7)   Reinstall the Startup ROM at U1 on the PCM-SSD card removed earlier.

8)  Reinstall the LPM-TX Pentium card.

9)  Power on the APU to restore normal operation.

Edit Parameters (EP)

The Edit Parameters screen is a sub-menu of the Supervisory Menu that may be used to view and edit the parameters. The Edit Parameters command provides access to all the configuration parameters of the APU-102 if logged in under Session 1. Logging into other sessions allows access the parameters that affect their session only. (For parameter definitions and default values, refer to Appendix A: System Parameters.)

Groups of parameters can be dumped all at once by using the Dump Parameters (D) option. This allows you to capture the information to a log file providing a record of the site's configuration should it need to be reconfigured or the information is lost. The parameter information can also be loaded back to the site using the Load Parameters (L) option.

Note: Version 5.1.1B103 has added capability of dumping or loading parameters to/from an on-board file.  Refer to the 4.5 Edit Parameters (EP) Menu for more information.

Edit Parameters - 1. Session1   2. Session2   3. Session3   4. Session4   5. LocalSupport   6. RemoteSupport   7. Acquisition   8. Ports   9. DiskManager  10. TimeZoneControl  11. DaylightSavings  12. SysDiags  13. DebugFlags  14. NetMenu  15. SupportThreads  16. MoreSessions [D]ump or [L]oad parameters, e[X]it >

Figure 4.43: Edit Parameters Menu

All options may not be available depending on software version

1)  Type the EP command and press <Enter>. The parameters display in logical groups that can be accessed via the EP menu system.

2)  Type the number corresponding to the parameter group you want to edit. Either a list of the parameters within that group or an additional, second-level parameter group displays.

If the option you select on the Edit Parameters menu displays an additional, second-level parameter group, select the desired group to access to the desired parameter list.

3)  To keep the current parameter value, press <Enter> to move to the next displayed value.

To change a displayed value, enter the new value opposite the current value prompt and press <'Enter>'. If the new value entered is out of range or invalid, either an error message displays or the system redisplays the previous value when you reboot.

4)  To dump groups of parameters and allow you to capture the information to the log file, select the D(ump). To load parameter information back to the site, select the L(oad) option.

Press the <ESC> key to exit the current level at any time. The <X> key will also exit the current level. Use the <X> key with caution and ONLY when the "X" option is displayed.

5)  Reboot the APU-102 when finished to ensure that the new parameters have taken effect.

For on-screen help, position your cursor at the parameter value and press <Ctrl><U>. To move backward, press <Ctrl><B>.

Note: The PARM.HLP file must be maintained in your system files; otherwise the parameter help will not be available.

For more information about the parameter editor interface, refer to the 4.5 Edit Parameters (EP) Menu.

System Cleanup (CLEAN)

The System Cleanup command (CLEAN) is used to eliminate unnecessary files from the APU-102. This command does NOT eliminate train files.

1)  Type the CLEAN command and press <Enter>. The following warning message displays and offers a chance to abort the reboot.

CLEAN - System Cleanup Command. ------------------------------- This function will remove unnecessary data and log files from the system. This function does NOT remove any trains! Continue? (Y/N)?

2)  Press <N> to cancel and return to the APU102XP:  Change prompt or press <Y> to continue.

Backup Parameters (BP) (5.09+)

This function is used to create an on-board backup copy of your system data files. These backup parameters will be automatically reloaded by the software when corrupt parameters files are detected. An initial backup parameter set is created the first time 5.09+ is booted. It is important to create a current backup set when parameters are changed. Verify the parameters are correct and the APU-102 is operational before executing the BP command.

1)  Type the BP command and press <ENTER>.

The APU-102 replies with a warning and confirmation to execute.

2)  Press <N> to cancel and return to the APU102 Change prompt or press <Y> to Continue.

Master System Reset (*MR)

The Master System Reset (MR) command removes all previously recorded trains from the APU-102. This process also uses the parameter DiskManager.MaxTrains to determine how many trains will now be maintained by the APU-102, assuming sufficient disk space. The APU-102 responds to the MR command with a warning statement and a chance for the user to abort the reset. The Continue? (Y/N)  response provides additional options to perform when the train files are deleted. Using this command is recommended when an APU-102 is put into service or after a problem has been solved. It is also useful to free up disk space or to remove old trains from drives that are swapped between units.

1)  Type the MR command and press <Enter>. The Master System Reset warning screen displays.

************Warning!!! Master Reset Initiated********** **********All Train Information will be flushed******** Continue? (Y/N)

2)  Type <N> to cancel or <Y> to continue and delete all trains on the unit.
The display will move to the following prompt.

“Reset train sequence number to 1? (Y/N)”

3)  Type <N> to maintain current train sequence numbering or type <Y> to reset the train sequence to 1. The display will move to the following prompt. (depending on software version)

Starting sequence number <1-9999>:

4)  Type the sequence number you’d like to start with if not 1 and press <ENTER>. The display will move to the following prompt.

Reboot after trains are removed? (Y/N)

5)  Type <N> to delete trains only or type <Y> to reboot after the trains are removed. The APU will display the following message.  

**********    Master Reset In Progress    **************

The APU will display the following message if reboot requested.

REMOTE REBOOT IN PROGRESS…

Pressing <ESC> before the reboot prompt will abort the MR command.

Master Reset and Restart (*MRR) 5.2+

Similar to MR, except it also deletes all known log files, reset train sequence number to 1 and restarts the AEI application.

1)  Type the MRR command and press <Enter>. The Master Reset and Restart warning screen displays.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!                      WARNING                        !!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! This function will remove ALL unnecessary files from the unit and will automatically restart the app. All trains will be deleted and the train sequence number will be reset to 1. Also, all log files will be removed. Continue? (Y/N)

2)  Type <N> to cancel or <Y> to continue.

System Status Reset (*SR)

Use the System Status Reset (*SR) command to delete the system status information from the APU-102.

1)  Type the SR command in one of the following formats:

Command Format	Description
SR	Required. Command code.
SR, 2 -15	Optional. Specifies the new size of the system status log file in Kbytes. Default size = 5 Kbytes.

 

APU102XP: Change 1>sr 10 *******Warning!!!! System Status Reset Initiated******* ********All Status Information will be flushed********* Continue? (Y/N)

 Figure 4.44: System Status Reset Warning Screen

In the above example, a reset to a 10-kilobyte system status file has been selected. Resetting the system status log is recommended when an APU-102 is put into service or after a problem has been solved. This removes old information that might be confusing.

2)  Type <Y> to continue with the reset or <N> to cancel and return to the APU102XP:  Change prompt.

Reset Maintenance Sequence (RMS)

The Reset Maintenance Sequence (RMS) command resets the maintenance report sequence number back to one for the current session. Resetting the maintenance report sequence number is recommended when an APU-102 is put into service. This removes old information that might be confusing.

1)  Type RMS and press <Enter>. The following message displays:

APU102XP: Change 1>rms Reset maintenance report sequence number to 1?  (Y.N)

2)  Select Y(es) or N(or). The APU102XP:  Change> prompt redisplays.

Reboot Unit (*R)

The Reboot Unit (R) command is tied to the reset line of the APU-102. When executed, the computer in the APU-102 restarts and the boot process begins. (Version 5.0+ closes files and shuts down Windows XP before resetting the computer.) All the external hardware and software is reinitialized. This is very helpful in the case of an inadvertent lock up of the reader board or I/O card, however the R command can be a very detrimental command, especially on 486 class APUs. Once the reboot is initiated, all acquisition, all communications with the APU-102, local or remote, will be lost. To prevent losing train data, avoid the reboot command while a train is passing the site. While a train is recording, a message is displayed with the command prompt.

**********Train Recording (24 axles)**********

A train must completely finish recording and appear in the train directory in order to be saved. Since the APU-102 cannot acquire data until the startup sequence is complete, it is impossible to generate an accurate consist from a train entering the site during that time.

1)  Type the R command and press <Enter>. The following warning message displays and offers a chance to abort the reboot.

WARNING: This function will cause the remote unit to reboot. Continue (Y.N)?

2)  Press <N> to cancel and return to the APU102XP:  Change prompt or press <Y> to continue and reboot the APU-102.

NOTE

Version 5.09+ has additional reboot options. R,M reboots the APU directly to ROMSHELL mode (or NetMRS if applicable). R,F performs a “fast” reboot. It shuts down and restarts the AEI application only. This option only takes a few seconds and is helpful when parameters have been changed that require a reboot. The computer P.O.S.T is not performed, nor are many “housekeeping” functions, such as code loading. R,T (5.2+) will execute a full reboot after the next train clears. R,C (5.2+, LX-800 processor only) The LX-800 processor uses a protected partition for the embedded operating system. Some parameter changes made are kept on the protected partition. The R,C command was added to update these changes to the protected partition. You will be prompted when the R,C reboot is necessary.

Watchdog Test (*WT)

The Watchdog Test (WT) command tests the operation of the unit's watchdog timer circuit. The watchdog thread is placed in a "HALT" state (simulating a failure). If the watchdog circuit is operating properly, the unit restarts in less than four minutes (before “Seconds to failure” reaches .0).

--------------------------------------- !! Watchdog Circuit Test in Progress !!      Press any key to stop test... --------------------------------------- Test is successful if the APU reboots before "Seconds to failure" reaches 0. The counter will stop when rebooting. Seconds to failure : 078....

Figure 4.45: Watchdog Test Screen

1)  To begin the test, type the WT command and press <Enter>.

2)  To stop the test before it is completed, press any key. The message “Test aborted by user” displays.

Zmodem Send File(s) (ZSEND)

The Zmodem Send File(s) (ZSEND) command places the APU-102 in Zmodem send mode. Zmodem can send multiple files.

1)  Type the ZSEND command in the following format:

Command Format	Description
ZSEND	Required. Command code.
Path	Optional. The file path must be specified if directory location of the file to be transferred is not in the default directory.
Filename for transfer	Required. The file specification of the APU-102 file (or files) you want to send using Zmodem. Use wildcards (* or ?) to upload multiple files.

Note: The path option is not available on application versions prior to 5.0. Files are sent from the default path only.

2)  Refer to your communications software package for instructions on receiving the file. Most programs will auto-receive, but have differing options when receiving a duplicate file. Insure your program does not blindly “resume” when receiving a duplicate file. After file has been sent, the message “N file(s) sent successfully” displays (where N = number of files).

Xmodem Send File (XSEND)

The Xmodem Send File (XSEND) command transfers files from the APU-102 using the Xmodem protocol. When the APU-102 is in send mode, you can initiate a file transfer or a file download using the Xmodem protocol.

File length: 125 Ready to send

Figure 4.46: Xmodem Send File Screen

1)  Type the XSEND command in the following format:

Command Format	Description
XSEND	Required. Command code.
Path	Optional. The file path must be specified if directory location of the file to be transferred is not in the default directory.
Filename for transfer	Required. The name of the APU-102 file you want to transfer in Xmodem send mode.

2)  The message “Ready to send” displays. Refer to your communications software package for instructions on receiving the file.

If no action is taken to send the file, an XSEND error message “Local timeout” displays and you are returned to the APU102XP:  Change prompt.

Xmodem1K Send File (XSEND1K)

The Xmodem1K Send File command allows files to be transferred from the APU-102 using the Xmodem1K protocol. When the APU-102 is in send mode, you can initiate a file transfer or a file download using the Xmodem1K protocol.

File length: 741 Ready to send

Figure 4.47: Xmodem1K Send File Screen

1)  Type the XSEND1K command in the following format:

Command Format	Description
XSEND1K	Required. Command code.
Path	Optional. The file path must be specified if directory location of the file to be transferred is not in the default directory.
Filename for transfer	Required. The name of the APU-102 file you want to transfer in Xmodem1K send mode.

2)  Refer to your communications software package for instructions on receiving the file.

If no action is taken to send the file, an XSEND error message “Local timeout” displays and you are returned to the APU102XP:  Change prompt.

Local Ethernet File Receive (ZGET)

This command is used to transfer a single file between units residing on the same network. This similar to the ZRec function, except that it is only available to perform network transfers. This command ALWAYS gets the entire file from the beginning (ZGetR can be used to resume transfers that were interrupted).

Type the ZGET command in the following format:

Command Format	Description
ZGET	Required. Command code.
Filename for transfer	Required. The file specification of the APU-102 file get from another unit on the local network. Wildcards are not permitted. Use caution with this command as it will overwrite an existing destination file.
IPAddressOrURL	Required. Network address of source computer.
IPPort	Optional. IP Port on the destination computer. Defaults to 23 on the APU.

Local Ethernet File Receive Resume (ZGETR)

This command can be used to resume a ZGET file transfer that was interrupted.

Note: The resume is done blindly, with no checks to ensure that the existing file has the same contents (up to the point of interruption) as the partial file. This means that if the file is a different version, the new file may be corrupted. Only use ZGETR on file transfers that you know were previously interrupted.

Type the ZGETR command in the following format:

Command Format	Description
ZGETR	Required. Command code.
Filename for transfer	Required. The file specification of the APU-102 file get from another unit on the local network. Wildcards are not permitted. Use caution with this command as it may overwrite or corrupt an existing destination file. (see note above).
IPAddressOrURL	Required. Network address of source computer.
IPPort	Optional. IP Port on the destination computer. Defaults to 23 on the APU.

Packet Internet Groper ('PING)'

This command works just like the basic Windows command line PING command.

Command Format	Description
PING	Required. Command code.
IPAddressOrURL	Required. Network address of destination computer. (192.168.0.12 in example below)

 

ping  192.168.0.12 < y.dat 1> dosshell.txt 2> dosshll2.txt Pinging 192.168.0.12 with 32 bytes of data: Reply from 192.168.0.12: bytes=32 time=1ms TTL=128 Reply from 192.168.0.12: bytes=32 time<1ms TTL=128 Reply from 192.168.0.12: bytes=32 time<1ms TTL=128 Reply from 192.168.0.12: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.0.12:     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 0ms, Maximum = 1ms, Average = 0ms

Figure 4.48: Sample Ping Response Screen

For advanced options and switches, run PING under the SHELL command.

Network Time Protocol (NTP)  

This command initiates a time sync request with a Network Time Protocol server (if configured in system parameters).

Reassociate Trains (RA)

Reassociate Trains is used in Distributed Processing Systems. The RA command reassociates all local trains to remote trains.

Refer to the APU103 Installation & Operation Manual' for additional information.

Command Shell (SHELL)

SHELL command argument switches

Any commands entered after the SHELL command will be sent to DOS command shell and treated as a DOS command. Batch files and DOS programs resident on the APU-102 can be executed as well as commands embedded in the DOS command interpreter, such as COPY, ECHO, REN, DIR (with switches), etc.

Caution

Use extreme caution with the SHELL command. Any command issued must NOT require any user intervention to complete the command or the APU-102 will be inaccessible via the current port until it is rebooted (for example, “Overwrite file Y/N?”). Some commands could even hang the AEI application in a manner that prevents a watchdog recovery. Shell commands should only be used by experienced users. In version 5.2, a timeout function was added to exit a hung Shell command.

Example:

SHELL COPY SPECIAL.BAT SPECIAL.BAK /y

Main Menu Help (MAIN?)

Main Menu commands (and help) are accessible from the Supervisor menu.

This command displays the Main Menu (or System Menu). All Main Menu functions can be executed from the Supervisory level.

Supervisory Help Screen (?)

Type ? to re-display the current menu screen.

Additional commands

Caution

For skilled administrators only. Improper use of these commands can make APU-102 inoperable.

Delete File(s) (REMOVE)  

Used to manually delete files. Works similar to DOS DEL command. You will be prompted for confirmation to execute the file deletion. After command execution, a summary of deleted files displays.

Command Format	Description
REMOVE	Required. Command.
FILENAME.EXT	Required. File(s) to delete. Must specify both basefile name and extension. Wildcards ? and * allowed

External Temperature Probe Commands

Used when external Rail Temperature Probe is properly installed and configured.

Force TempProbe Reading (XTPNOW)

Display Last TempProbe Reading' ('XTPDEBUG)

Acquisition Process Info' ('ACQ) 

ACQ Report is not running Next ACQ sequence will be 1013

Cubic Acoustic History' ('CAHHISTORY)

Modem Stats' ('MDMS)

Display modem statistics including reset, initialization, connection, and disconnection stats.

Reset Modem Stats (MDMS,R)

Resets the Modem Statistic file.

Site Notepad (NOTE) 5.2+

Used to manage banner messages that appear during the login process.

Usage: NOTE Option Argument

Option [Argument]:
A [message]	Add a message
D [message number]	Delete message number
C	Clear all messages
P	Print all messages
L	Toggle whether to display notes at user login

COMET ELECTRONICS Automatic Equipment Identification System APU Software Version: 5.2.0.4 CPU Type: LPMTX AMTECH Model AI1200 Ver 2.90 SN41656 Reader #1 is not in current configuration Thu 02/11/2015   08:59:03 Host Reporting: On, All Last LOGON: Wed 02/10/15   15:06:30 ================== Site Notes =================== 1)  Updated to 5.2.0.4 12/11/2014 @ 11:22 ================================================= USID:       COMET00001 Site Name:  TEST UNIT Display help command - "?" APU102XP:Main 1>

Sample login screen with Note shown.

Set debug flags (SET)

Communications Logging

  SET LOGCOM 1 Turns com logging on

  SET LOGCOM 0 Turns com logging off

All communications are logged to text files, outbound communications are logged to [port file].TX, inbound communications are logged to [port file].RX

WARNING:  These log files are not managed by the Disk Manager and will continue to grow in size indefinitely!!! DO NOT leave logging active for an extended period of time!!!

Manually delete the *.TX and *.RX files when done.

Telnet Escape Characters enable/disable

  SET TELNET 1 Turns on escape characters

  SET TELNET 0 Turns off escape characters

User Access Account Management (USER) 5.2+

User level access control. Higher security than standard 2 level APU security.

Usage: User [option] [parameters]

Options [Parameters]

add    [username] [password]

remove   [username]

show

Note: To change the password of an existing user, simply add the user again, but with the new password.

 

View Channel Info' ('VCI)

Lists all currently used ports and displays diagnostic data.

--- Locked --- -Depacket- #     Name      PID   Dev  Port  Baud Ctrl Stat #S   By     Sec    Run? State -- ----------- ----- ----- ----- ---- ---- ---- --- ----- -------- ---- ----- 0  $REMPORT      0   COMN      1 6    0002 0020   3                 Y    4 1  $LOCPORT      0   COMN      2 3    0003 0005   2   05     0000   Y    4 2  ETHERNET01   30   TCPIP    23 0    0002 0000   1   30     0000   Y    4 3  ETHERNET02   31   TCPIP    23 0    0002 0001   1   31     0742   Y    4 12 AVI1PORT      1   COMN      4 4    0003 0001   1                 Y    4

Sample VCI

XTrack Log' ('XTL) – Currently not available (Comet Engineering use only).

Watchdog Monitor Stats' ('WDM)

Displays stats for the software watchdog.

PID  Timeout   Low Mark ===  ========  ========  23     60000     45000   2     30000     25000 100    300000    295000 114    300000    295000 113    300000    121000 112    300000    121000 111    300000    295000 110    300000    295000 104    300000    112000 103    300000    112000 102    300000    112000 101    300000    112000   1    300000    295000

Sample WDM

Test FTP Connection' '(FTP)

Attempts to open a socket on port 22 at the specified IP address or host name and reports back success or failure.

Usage: FTP [IP Address or Host Name]

Restart Network (STARTNET) (5.2+)

Restarts network to apply network related parameter changes without rebooting the APU-102

Switch Session

Switches to the next session without logging out to session selection screen and choosing a different session. Must be initially logged into Session1, Supervisory level to use. At last Session, command will return to Session 1.

Switch session <CTRL>-G, followed by <ENTER>

Edit Parameters (EP) Menu

The Edit Parameters Menu allows those with Supervisory Menu access to view and update current APU-102 parameters. As explained in the Supervisory Menu Commands section, type the EP command at the APU102XP:  Change prompt on the Supervisory Menu to access the Edit Parameters menu.

Parameter Editing Methods

Interactive Method

This method allows you to select a parameter group and view and/or edit its parameters using a simple menu style interface.

Example: Follow the steps below to give the site a new session name using the interactive method:

1)  Enter the EP command at the APU102XP:  Change prompt. The Edit Parameters menu displays. See screen sample in Edit Parameters (EP).

2)  Type 1 for Session1 because you know that the "Session1" parameter group contains the site name. The Edit Parameters – Session 1 screen displays:

Edit Parameters -   1. Session1   2. Session2   3. Session3   4. Session4   5. LocalSupport   6. RemoteSupport   7. Acquisition   8. Ports   9. DiskManager  10. TimeZoneControl  11. DaylightSavings  12. SysDiags  13. DebugFlags  14. NetMenu  15. SupportThreads  16. MoreSessions [D]ump or [L]oad parameters, e[X]it >

3)  Select 1. SiteInformation. The following screen displays, showing that the current setting of this parameter is “Misc Railroad”:

Edit Parameters - Session1    1. SiteInformation    2. AEIReportOpts    3. AEIReportConnect    4. MaintReportOpts    5. MaintReportConnect    6. Security    7. T94    8. CP    9. CR160   10. EarlyWarning  [D]ump or [L]oad parameters, e[X]it >1  Editing Session1.SiteInformation  Ctrl-B MOVES BACKWARDS  SalutationMessage = My Railroad >

4)  Press <Enter> to advance to the next parameter of the group without changing the current setting.

- or -

Type the new session name and press <Enter> to change the setting. The SalutationMessage field displays the new entry and you automatically advance to the next parameter of the group, if any.

Note:  No need to burrow to the end of a group if you do not want to make any more changes, press <ESC> to return to go up to the group menu.

If you want to modify a parameter in the group that you have already bypassed, press <'Ctrl><'B> until you return to the desired parameter.

Command Line Method

Each parameter group has a name, as does each individual parameter in a group. In the above example, we interactively changed the "SalutationMessage" parameter. We set “Session1.SalutationMessage” to “My Railroad," with the EP function guiding us. The parameter could have also been changed at the EP command line by typing “Session1.SalutationMessage=My Railroad” and pressing <Enter>. Parameters are represented as statements rather than menu selections, which allow the entire parameter set to be “batched.”

Batch Operations

Batching allows parameters to be uploaded or downloaded in groups, as opposed to one-by-one using the interactive method. In our applications, batching allows you to gather and store all parameters for the site in one file. Because the file is human readable and editable using any text editor, viewing and/or modifying the system parameters from a remote site is a simple process. It also allows a site to be duplicated easily in the event of a complete system failure. While reloading code to a site may be a simple operation, reconfiguring the site exactly as it was (i.e. parameters) is not.

Example: Replacing Sites; The solid state disk needs to be replaced due to an upgrade. Fortunately, you logged an EP dump of the site parameters just after the site went into operation. After the local technician put the unconfigured spare unit in place at the site, connect and upload the EP dump back to the site. Reboot the APU-102 when finished to ensure that the new parameters have taken effect. When appropriate (depending on AEI application version), log back in and do parameter backup (BP) and update the system mirror image for accurate system recovery. .

Example: Cloning Sites Batch operations are useful for duplicating sites. For example, if another unit is added at another location, everything at the new site is identical, except for the name, number, etc. Simply edit the captured dump file to make appropriate changes and upload to the new site with the modified version.

Editing Parameter Groups

Each parameter group on the Edit Parameters menu contains a list of individual parameters that may be edited. For parameter descriptions, valid values, and default values, refer to Appendix A: System Parameters.

Downloading Parameters

To download (or dump) all parameter statements for the system:

1)  Enter the EP command at the APU102XP:  Change prompt. The Edit Parameters menu displays. See screen sample in Edit Parameters (EP).

2)  Type <D> for Dump at the Edit Parameters menu command prompt. The “Press enter to start…” prompt allows you to start a capture file on the communications package you are using to store the parameters.

3)  The EP command then downloads the parameter statements to you. When the last parameter displays, you can press <ESC> to return to the previous parameter listing menu or wait for the inactivity timeout to do the same.

The following is an example of a parameter dump from a sample APU-102 application:

TimeZoneControl.ReferenceTimeZone=6 TimeZoneControl.TimeSyncWithHost=1 SysDiags.PresenceLoop.MinAxles=3 SysDiags.PresenceLoop.LowSpeedThresh=4 SysDiags.PresenceLoop.HighSpeedThresh=15 SysDiags.PresenceLoop.PresTimeOutAboveSpeed=15 SysDiags.PresenceLoopPresenceTimeoutSeconds=30 SysDiags.PresenceLoop.SecondsBetweenTrains=20 SysDiags.Antenna.ConsecutiveTrains=1 SysDiags.Antenna.MinTrainLength=10 SysDiags.Antenna.FatalTagPercent=1 SysDiags.Antenna.WarningTagPercent=50 SysDiags.WheelDet.ConsecutiveTrains=1 SysDiags.WheelDet.MinValidTagPairs=3 SysDiags.WheelDet.TrainsToReview=0 SysDiags.WheelDet.AxlesToReview=0 SysDiags.WheelDet.Mismatch=0 SysDiags.WheelDet.LowtoleranceMismatch=0 SysDiags.WheelDet.LowToleranceSpeed=0

Figure 4.49: Parameter Dump Example (partial)

Uploading Parameters

Before you can do a parameter upload, you will need a file containing the parameters. The easiest way to obtain a parameter file is to create one using the download procedure described above.

To upload a parameter file, enter <L> for Load at the EP prompt and send the file to the unit using your communications package’s “RAW ASCII TRANSMIT” or “TEXT” command. EP echoes back to you the parameter statements it receives as well as a message indicating how well it digested each message. If the EP command does not like a parameter or setting, it will let you know. (It’s a good idea to log the message stream). When the last parameter displays, you can press <ESC> to return to the previous parameter listing menu or wait for the inactivity timeout to do the same.

Caution

Pay attention to the responses. As the number of parameters grow with the application development, it is possible to over-run the buffer on the APU-102, especially if using the Local Port, resulting in parameters not getting updated as desired.

Some communications programs will allow you to “paste” text to the screen and can be a handy method of loading partial parameter files.

Reboot the APU-102 when finished to ensure that the new parameters have taken effect. When appropriate (depending on AEI application version), log back in and do parameter backup (BP) and update the system mirror image for accurate system recovery.

  Dumping Parameters to on-board file (5.1.1B103 or later)

To download (or dump) all parameter statements for the system:

1)  Enter the EP command at the APU102XP:  Change prompt. The Edit Parameters menu displays. See screen sample in Edit Parameters (EP).

2)  Type <DF> for Dump File at the Edit Parameters menu command prompt. You will be prompted for a file to capture the parameters to. This file will be on the APU and it can be downloaded to your PC via any available file transfer methods on the APU102, i.e., Zmodem, Xmodem, FTP, etc.

3)  The EP command then dumps the parameter statements to that file. The parameter listing will be refreshed when the process is done. If the file already exists, you will be prompted to overwrite it.

 Loading Parameters from on-board file (5.1.1B103 or later)

Before you can do a parameter upload, you will need a file containing the parameters. The easiest way to obtain a parameter file is to create one using the download procedure described above.

To load parameters from a file, it must be resident on the APU-102. The file can be uploaded from your PC via any available file transfer methods on the APU-102, i.e., Zmodem, Xmodem, FTP, ZPUT, ZGET, etc.

1)   Enter the EP command at the APU102XP:  Change prompt. The Edit Parameters menu displays. See screen sample in Edit Parameters (EP).

2)  Type <LF> for Load File at the Edit Parameters menu command prompt. You will be prompted for the file to load the parameters from. 

3)  The EP command then loads the parameter statements from that file. Progress will look like the standard “L” load or may show progress bar on later versions of software.

Note: A log file (PED.LOG) will be created of the complete parameter load noting errors. It is a text file that can be downloaded or viewed on-line with the TYPE command.

4)  Reboot the APU-102 when finished to ensure that the new parameters have taken effect. When appropriate (depending on AEI application version), log back in and do parameter backup (BP) and update the system mirror image for accurate system recovery.

ROMSHELL User Interface (Optional)

 Overview

ROMSHELL is an alternate operating mode of the APU-102 that is hard coded into the Startup ROM (drive A of the USSD/PSSD). Not applicable for L-Series APU-102 (LX-800 equipped). It has diagnostic functionality superior to Mini-Remote Support (MRS). Benefits of the ROMSHELL user interface include:

Loading Code via Zmodem

Versions of the AEI code prior to 4.20 do not support Zmodem file transfers. Xmodem will pad the file to an even 128 bytes, and that padding may make some files unstable or unusable. Formerly, Remote Support and a “Back Door” connection had to be used to load these files. With ROMSHELL, they can be loaded via Zmodem.

Restoring site operation when USSD is blank

The USSD may be blank due to onboard battery failure coupled with power loss to APU-102. It may also be cleared intentionally by removing battery jumpers or issuing a remote format command. This is usually done if a corrupt file structure is suspected or field upgrade of a card is desired. With ROMSHELL, the site can be restored to operation.

Additional Benefits:

• Zmodem file transfer protocol. Does not require a special communication software package, as with MRS.
• ROMSHELL identifies the modem and initializes it with the highest possible connection rate. (independent of the AEI application)
• Local port initialization at 2400 or 9600 baud depending on version (detailed below in Local Port Connection and Logon). (independent of the AEI application)
• Password protection. (independent of the AEI application)
• ROMSHELL activity is logged to a text file on the APU-102’s “disk”.
• Contains many DOS-like commands.
• MS-DOS commands, including COMMAND.COM embedded commands can be performed through the shell.
• PORTATTACH utility that does not require port-specific portfile or initialization files.
• Watchdog timer reboots the APU-102 after 20 minutes.
• Real-time verification of file transfers.
• Automatic compact flash recovery if corruption is detected.

  (Version 5.4 for LPMTX only! Requires CF imaged with mirror partition. Refer to document 385-0010-00, APU102 Auto-Recovery Quick Start Guide for LPM-TX for detailed operation)

  Why is ROMSHELL Running?

  The APU-102 boots to ROMSHELL every fifth time the APU-102 is hard booted by power reset or watchdog timer reboot. The APU-102 can be forced to boot to ROMSHELL for diagnostics. The APU-102 also boots to ROMSHELL under the following additional circumstances:

  The application boot-up sequence fails. This can be caused by corrupt or missing files, incorrect parameter setup, or loss of all files from the static RAM of the USSD (C: drive).

  The following files are required to boot to the DOS version AEI consist application:

• SPECIAL.BAT (Executes commands preparing the APU-102 to run the application.)
• APUEXEC.BAT or other batch file to load the application. (Its contents must contain the file name of the Application Executable.)
• SYSPARMS.DAT
• $REMPORT.DAT
• $REMPARM.DAT
• $LOCPORT.DAT
• $LOCPARM.DAT
• SAAEI.EXE
• Modem INI file identified in $REMPORT.DAT
• Application Executable file (e.g. AP423.EXE)

  Note: File requirements vary for other DOS APU-102 applications, such as Tracker and ACQ.

  XP version APU-102 have file requirements that are too complex to detail here.

  The application fails to initialize some of the hardware, particularly Modem and Local Ports. A possible cause could be an error in following parameter files:

• $REMPORT.DAT (Particularly Modem INI file specified correctly, and the file must be on the disk)
• $REMPARM.DAT (Tells the APU-102 which port file to use for remote access. Usually modem port is $REMPORT.DAT.)
• $LOCPORT.DAT
• $LOCPARM.DAT (Tells the APU-102 which port file to use for local access. Usually local port is $LOCPORT.DAT.)

  Other potential file problems include:

• F.BAT (run once BAT file) has invalid commands that prevent it from fully executing such as those requiring user input.
• SPECIAL.BAT does not fully execute.
• APUEXEC.BAT (or other batch file to load the application) does not contain the file name of the Application Executable.

ROMSHELL Operation

Local Port Connection and Logon

1)  Attach a PC or data terminal to the “LOCAL” communications port of the APU-102 unit. The APU-102 is configured as a DTE with a female 25-pin “D” RS-232 connector. Communications parameters for Startup ROM version 5.3+ are controlled by a flag file (96.DAT) in the APU’s AEI directory. If the file is present, the local port is initialized at 9600 baud. If the file is absent, the port initializes at 2400. Version 5.1 is fixed at 2400 baud. Other prior versions are fixed at 9600 baud. All utilize 8 data bits, no parity, and one stop bit. These parameters are independent of the AEI application and may be different. Setup your communications program to match.

2)  Press <Enter> and the ROMSHELL responds with the Password prompt.

3)  Type your password and press <Enter>. The default password is “SECRET” but can be changed. (Refer to Password command) You will see a prompt similar to the following example. From here you can enter any of the ROMSHELL commands.

-RS- A:\>

Note: The prompt will reflect the current working directory; in this case, the root of “A.”

Dial-up Connection

1)  Dial the site with any commercial communication package, and the modems will negotiate the best connection.

2)  Once connected, press <Enter> and the ROMSHELL responds with the Password prompt.

3)  Type your password and press <Enter>. The default password is “SECRET” but can be changed as. (Refer to Password command) You will see a prompt similar to the following example. From here you can enter any of the ROMSHELL commands.

-RS- A:\>

Note: The prompt will reflect the current working directory, in this case, the root of “A.”

ROMSHELL System Commands

Type <?> and press <Enter> to display a list of available ROMSHELL commands. A list of the commands displays.

Command Listing

? HELP EXIT CLS DIR TYPE DEL / REBOOT SHELL PORTVIEW ZSEND ZREC ZRECR TIME DATE CD ATTACH PORTATTACH VER L FORMATUSSD PASSWORD TTL HDTOOL

Command Definitions

The following defines and explains how to use each ROMSHELL command. Type <?> and press <Enter> (or HELP and <Enter>)  to display a list of available commands.

?

Displays the ROMSHELL command listing.

/

Displays information on available system memory.

Free Mem : 445856, Free Disk : 1121792       Stack Usage Information    Name    Id    Base     Size   Free ---------- --  ---------  -----  ---- Main       00  25DE:0BF6  29240  17133  $locport   04  25DE:7296  3000   1667   $remport   05  25DE:66D4  3000   1891   conport    06  25DE:5B12  3000   2055   DOG        07  25DE:4F50  3000   2351          Memory Fragment Information #    Address    Len --  ---------  ----- 01  3325:0000  445856 02  2EA6:0000  80   03  2FF0:0000  48   Total free: 445984 (bytes) Example: / Command

ATTACH Portfile

Attaches to defined ports ($REMPORT.DAT and $LOCPORT.DAT). For example, if logged into the local port, you could attach to the modem port ($REMPORT.DAT) and execute Hayes commands to the modem. Control-Z exits the attach utility.

Note:  Legacy ports only-not compatible with ports 3-6 on network capable APU-102s.

CD path

Works like a DOS CD command. It changes to the specified directory and displays the -RS- (path)> prompt, reflecting the now current working directory.

Note: You can also change to a different drive as you would in DOS. Example: Type C: and press <Enter> to change to the “C” drive.

CLS

Clears the screen and displays the -RS- (path)> prompt.

DATE

Displays the following prompt with the current ROMSHELL site system date. To change the date, enter the new date using the format displayed in parentheses. To accept the current date, press <Enter>.

Current date is 06/01/2004

Enter new date (mm-dd-yyyy):

Note: Changing the date or time on the E-Series APU restarts the 20-minute watchdog. The P-Series APU handles time differently and may cause a reboot (time has expired). It is recommended that the system date and time be set with the AEI application. If date/time is set in ROMSHELL and then booted to the application, the time may be off due to time zones or daylight savings time settings. These settings are applied AFTER time is read from the CPU.

DEL  filename

Deletes the specified filename from the system.

DIR (optional parameters)

Use the DIR command alone to display a directory of all files in the current path. To display specific files, add the optional path and filename arguments using standard DOS conventions including wildcard arguments (* or ?). This is not a true DOS DIR command though, therefore do not apply any “/” switches to your command line. If a true DOS DIR is desired, refer to the SHELL command below.

Volume in drive A is Ac  Volume Serial Number is 0616-1200  Directory of A:\ $LOCPORT DAT        76 03-09-00   1:29p $REMPORT DAT        78 03-09-00   1:30p ANSI     SYS      9029 04-27-95   8:10p AUTOEXEC BAT      1145 03-16-00   4:34p CHECKSYS COM       192 04-27-95   8:12p CHKDSK   EXE     16200 04-27-95   8:10p COMMAND  COM     47845 11-11-91   5:00a CONFIG   SYS       152 03-09-00   2:01p CONPORT  DAT        78 11-17-95   5:42p DOG      INI        82 03-21-00  10:59a DT336    INI       564 03-21-00  10:31a EMM386   EXE     91742 04-27-95   8:10p HIMEM    SYS     11616 04-27-95   8:10p MCM2496M INI      1342 12-17-99  10:05a MDM144S  INI      1124 03-21-00   8:19a MODEM    INI        65 04-27-95   8:10p MRS      BAT        52 03-16-00   4:34p PASSWORD TXT         8 03-16-00  10:19a ROMSHELL EXE     54745 03-21-00  10:50a ROM_VER  TXT        50 03-20-00   2:53p SHARE    EXE     10912 04-27-95   8:10p USSD     SYS      9282 04-27-95   8:10p        22 file(s)     256379 bytes                      1121792 bytes free

Example: DIR Command of ROMSHELL ROM

EXIT

Exits the ROMSHELL program. The following message displays:

Terminating Console.  Bye…..

To return to the ROMSHELL application, press any key to display the Password field, then reenter your password.

FORMATUSSD

This command formats the USSD and reboots the APU-102. A warning and confirmation message is displayed. After the reboot, you will need to reestablish the connection to proceed.

Note: This command does not function on Pentium Flash disk.

HDTOOL (Romshell 5.4+)

Hard drive toolkit. This is a utility used by the system for Compact Flash recovery. Do not use without instruction by Comet Electronics Support personnel who will guide you through command entry.

HELP

Displays the ROMSHELL command listing. Identical to the <?> command.

L

Displays the last command. Press <Enter> to repeat the command or edit as necessary.

PASSWORD newpassword

Changes the ROMSHELL logon password. The system will ask for confirmation of the new password. This command has no effect on the applications password. The password is in the encrypted file “PASSWORD.TXT” on the root of the “C” drive. If the ROMSHELL password is forgotten, it can be reset with a special boot sequence detailed at the end of this section. (Startup ROM version 5.1 and higher)

PORTATTACH PORT BAUD B P S

Attaches to undefined ports. Example: PORTATTACH COM4 4800 8 n 1 connects to Comm port 4, 4800 baud, 8 data bits, no parity, 1 stop bit. (Default for first reader.) Control-Z exits the PORTATTACH utility and displays the -RS- (path)> prompt.

Note:  Legacy ports only-not compatible with ports 3-6 on network capable APU-102s.

PORTVIEW port number N (or port number N port number N)

This is the port-specific version of the IO screen. Displays one or more selected ports to view.

PORT   D7 D6 D5 D4 D3 D2 D1 D0   HEX -----  -- -- -- -- -- -- -- --   ---- 0x310   1  1  1  1  0  0  1  1   0xF3 Example: PORTVIEW Command

Example: PORTVIEW Command

REBOOT

Performs a software reboot. You will be prompted for confirmation. After the reboot, you will need to re-establish the connection to proceed.

SHELL command argument switches

Any commands entered after the SHELL command will be sent to DOS and treated as a DOS command. Batch files and DOS programs can be executed as well as commands embedded in the DOS command interpreter, such as COPY, ECHO, REN, DIR (with switches), etc.

Caution

Use extreme caution with the SHELL command. Any command issued must NOT require any user intervention to complete the command or the APU will be inaccessible via the current port until it is rebooted. It should only be used by experienced users.

Example:

SHELL COPY SPECIAL.BAT SPECIAL.BAK

TIME

Displays the following prompt with the current ROMSHELL site system time. To change the time, enter the new time using the format displayed in parentheses.

To accept the current time, press <Enter>.

Current time is 17:45:45 Enter new time (hh:mm:ss):

Note: Changing the date or time on the E-Series APU restarts the 20-minute watchdog. The P-Series APU handles time differently and may cause a reboot (time has expired). It is recommended that the system date and time be set with the AEI application. If date/time is set in ROMSHELL and then booted to the application, the time may be off due to time zones or daylight savings time settings. These settings are applied AFTER time is read from the CPU.

TTL (Romshell 5.4+)

Display or change the current “Time-To-Live” (TTL) before the watchdog timer reboots the APU-102.

1)  To view or change TTL options, select one of the following command format options and press <Enter>.

Command Format	Description
TTL	Required. "Time-To-Live" before the watchdog timer reboots the APU-102. This command does not change the current TTL.
TTL,#	Optional. Changes “Time-To-Live” (in Seconds) before the watchdog timer reboots the APU-102.

The following example shows a screen display if TTL is entered.

-RS- A:\>TTL Current Time-To-Live = 1076 (seconds). -RS- A:\>

TYPE filename

Displays the contents of the filename entered after the command.

@ECHO OFF @ECHO ---------------------------- type rom_ver.txt @ECHO      ATS Systems @ECHO ---------------------------- path a:\;c:\;c:\aei PROMPT $P$G

Example: TYPE Command with autoexec.bat filename (part of file displayed).

VER

Displays the ROMSHELL version.

ZREC

The Zmodem Receive File(s) (ZREC) command places the APU-102 in Zmodem receive mode. The files will be received into the current working directory. Zmodem can receive multiple files.

1)  Type the ZREC command and press <Enter>. The message, “Ready to receive,” displays.

2)  Once the APU-102 is in the receive mode, use the Zmodem protocol on your communications program to initiate a file transfer or a file upload. Use wildcards (* or ?) to upload multiple files. Refer to your communications software package for instructions on sending the file.

After file is received, the message “N file(s) received successfully” displays (N representing the number of files.) and the -RS- (path)> prompt re-displays.

If there are errors in the modem’s transmission, one or all of the following messages may display (where N represents the number of files).

N port overrun errors	Serial port has at least one overrun.
N byte framing errors	Serial port has at least one framing error.
N parity errors	Serial port has at least one parity error.

These errors are normal and the Zmodem protocol is designed to correct for them. If they become excessive, you may need to repair either the serial port or the modem.

ZRECR

The Zmodem Receive Resume (ZRECR) command places the APU-102 in Zmodem receive restart mode. The files will be received into the current working directory. Zmodem can receive multiple files. If a file already exists on the unit, Zmodem will resume transfer of the existing file at the point where the previous transfer was interrupted. With ZRECR, previously interrupted transmissions can continue, which saves time.

Note: The resume is done blindly, with no checks to ensure that the existing file has the same contents (up to the point of interruption) as the sent file. This means that if the file is a different version, the new file may be corrupted. Only use ZRECR on file transfers that you know were previously interrupted.

1)  Type the ZRECR command and press <Enter>. The message, “Ready to receive,” displays.

2)  Once the APU-102 is in the receive mode, use the Zmodem protocol on your communications program to initiate a file transfer or a file upload. Use wildcards (* or ?) to upload multiple files. Refer to your communications software package for instructions on sending the file.

After file is received, the message “N file(s) received successfully” displays (N representing the number of files.) and the -RS- (path)> prompt re-displays.

If there are errors in the modem’s transmission, one or all of the following messages may display (where N represents the number of files).

N port overrun errors	Serial port has at least one overrun.
N byte framing errors	Serial port has at least one framing error.
N parity errors	Serial port has at least one parity error.

These errors are normal and the Zmodem protocol is designed to correct for them. If they become excessive, you may need to repair either the serial port or the modem.

ZSEND filename

The Zmodem Send File(s) (ZSEND) command places the APU-102 in Zmodem send mode. Zmodem can send multiple files.

The message, “Ready to send,” displays. Use wild cards (* and ?) to send multiple files. Refer to your communications software package for instructions on receiving the file. Most programs will auto-receive, but have differing options when receiving a duplicate file. Insure your program does not blindly “resume” when receiving a duplicate file. After file has been sent, the message “N file(s) sent successfully” displays (where N = number of files) and the -RS- (path)> prompt redisplays.

Note: Refer to your communications software package for instructions on receiving the file.

Additional Commands (Not in HELP file)

You can change to a different drive as you would in DOS. Example: Type C: and press <Enter> to change to the “C” drive.

Forcing the APU-102 to boot to ROMSHELL

1)  Power the APU off.

2)  Power the APU on.

3)  Immediately press and hold the SYS button on the front panel.

4)  About 30 seconds after power up, the SYS LED will blink rapidly. Continue holding the SYS button until the rapid blink stops.

5)  Release the SYS button. ROMSHELL will load in about 30 more seconds, indicated by a slow blinking SYS LED.

Resetting ROMSHELL Password (Startup ROM version 5.1 and higher)

Note: Does not reset application password.

1)  Power the APU off.

2)  Power the APU on.

3)  Immediately press and hold the SYS button on the front panel.
About 30 seconds after power up, the SYS LED will blink rapidly.

4)  Release the SYS button and immediately press and hold for second blink sequence (about 5 sec).

5)  Continue holding the SYS button until the second rapid blink sequence stops.

6)  Release the SYS button. ROMSHELL will load in about 30 seconds, indicated by a slow blinking SYS LED. The password will be reset to the default (SECRET)

NetMRS User Interface (Optional)

Overview

NetMRS is an alternate operating mode of the APU-102 that runs under XPe and is preloaded to the compact flash. It has diagnostic functionality similar to ROMSHELL, but has added network connectivity. The L-Series APU (LX-800 equipped) only has[RCT4] [DDC5]  NetMRS.  Benefits of the NetMRS user interface include:

Additional Benefits:

• Does not require a special communication software package, as with MRS.
• Modem port initialization is the same as specified in the AEI application’s parameters.
• Local port initialization [DDC6]independent of the AEI application and may be different. The baud rate is controlled by a flag file in the APU’s AEI directory. Refer to Local Port Connection and Logon in the next section
• Network port initialization is the same as specified in the AEI application’s Ethernet parameters for telnet connectivity.

  Why is NetMRS Running?

  NetMRS follows most of the same rules as ROMSHELL. It has different file requirements as well as the capability of checking the integrity of key files. On P-Series APU-102 (LPMTX processor[RCT7] [DDC8] ), there is currently no method to force NetMRS operation other than a R,M command from the AEI application.

  Beginning with 5.1.1 Build 117, an L-Series APU-102 can be booted to NetMRS by holding the SYS button on power up in the same manner as LPMTX (P-series) and 486 (E-Series) APUs are forced to ROMSHELL.

NetMRS Operation

Local Port Connection and Logon

1)  Attach a PC or data terminal to the “LOCAL” communications port of the APU-102 unit. The APU-102 is configured as a DTE with a female 25-pin “D” RS-232 connector. It will use 8 data bits, no parity, and one stop bit. The baud rate is controlled by a flag file (96.DAT) in the APU’s AEI directory. If the file is present, the local port is initialized at 9600 baud. If the file is absent, the port initializes at 2400. Setup your communications program to match[RCT9] [DDC10] .

2)  Press <Enter> and the NetMRS responds with following login:

APU102XP NetMRS 1.2

Password:

3)  Type your password and press <Enter>. The default password is “SECRET[RCT11] [DDC12] ” but can be changed. (Refer to Password command) You will see a prompt similar to the following example. From here you can enter any of the NetMRS commands.

-NetMRS- C:\AEI>

Note: The prompt will reflect the current working directory; in this case, the AEI directory on the “C” drive. The LX-800 CF is configured differently and the default AEI Application directory on it will be D:\AEI.

Dial-up Connection

1)  Dial the site with any commercial communication package, and the modems will negotiate the best connection.

2)  Press <Enter> and the NetMRS responds with following login:

APU102XP NetMRS 1.2

Password:

3)  Type your password and press <Enter>. The default password is “SECRET” but can be changed. (Refer to Password command) You will see a prompt similar to the following example. From here you can enter any of the NetMRS commands.

-NetMRS- C:\AEI>

Note: The prompt will reflect the current working directory; in this case, the AEI directory on the “C” drive. The LX-800 CF is configured differently and the default AEI Application directory on it will be D:\AEI.

Telnet Connection

1)  Connect to the site with any [RCT13] commercial communication package that supports telnet. You must have a valid connection path to the APU-102 to connect. You will need to specify the IP address and optionally, the port number. The APU-102 uses the default telnet port 23 unless specified differently in the AEI Application’s Ethernet port parameters.

2)  Press <Enter> and the NetMRS responds with following login:

APU102XP NetMRS 1.2

Password:

3)  Type your password and press <Enter>. The default password is “SECRET” but can be changed. (Refer to Password command) You will see a prompt similar to the following example. From here you can enter any of the NetMRS commands.

-NetMRS- C:\AEI>

Note: The prompt will reflect the current working directory; in this case, the AEI directory on the “C” drive. The LX-800 CF is configured differently and the default AEI Application directory on it will be D:\AEI.

NetMRS System Commands

Type <?> and press <Enter> (or HELP and <Enter>) to display a list of available NetMRS commands. A list of the commands displays.

Command Listing

? HELP EXIT CLS DIR TYPE DEL / REBOOT SHELL ZSEND ZREC ZRECR T CD VER L PASSWORD PT IPCONFIG PING

Command Definitions

The following defines and explains how to use each NetMRS command. The associated parameters appear in italics after the command, where applicable.

?

Displays the NetMRS command listing.

/

Displays APUINFO.DAT file and system metrics if available.

APU-102 Equipment Identifier V1.02 PROCESSOR:              Pentium BIOS CHKSUM:            0xA7BA CONVENTIONAL MEMORY:    640 KBytes EXTENDED MEMORY:        N/A KBytes COM1 FOUND:             PORT = 0x03F8 IRQ = 4 COM2 FOUND:             PORT = 0x02F8 IRQ = 3 COM3 FOUND:             PORT = 0x0380 IRQ = 10 COM4 FOUND:             PORT = 0x0388 IRQ = 10 COM5 FOUND:             PORT = 0x0288 IRQ = 10 COM6 FOUND:             PORT = 0x0230 IRQ = 10 COM CARD:               COM4 Card MODEM TYPE:             56000 SSD TYPE:               PCM-SSD READER VERSION:         2.80 APU SOFTWARE VERSION:   5.11 B101 STARTUP ROM VERSION:    5.4 DOS VERSION:            5.00 Free Mem: 27,140,096, Free Disk: 53,743,616 KB Metric                         Value ------------------------------ ---------- Startup....................... 285 SpontaneousBoot............... 279 SoftBoot...................... 0 Trains........................ 0 FileReadbackSizeMismatch...... 0 FileReadbackDataMismatch...... 0 SystemParameterRestores....... 1 SystemParameterNoRecover...... 0

CD path

Works like a DOS CD command. It changes to the specified directory and displays the -NetMRS- (path)> prompt, reflecting the now current working directory.

CLS

Clears the screen and displays the -NetMRS- (path)> prompt.

DIR (optional parameters)

Use the DIR command alone to display a directory of all files in the current path. To display specific files, add the optional path and filename arguments using standard DOS conventions including wildcard arguments (* or ?). This is not a true DOS DIR command though, therefore do not apply any “/” switches to your command line. If a true DOS DIR is desired, refer to the SHELL command below.

-NetMRS- C:\AEI>dir m*.ini M144-12  INI        890  10-25-11  12:54  M144-144 INI        724  10-25-11  12:54  M144-24  INI        815  10-25-11  12:54  M144-3   INI        886  10-25-11  12:54  M144-48  INI        814  10-25-11  12:54  M144-96  INI        814  10-25-11  12:54  MCM1414V INI      1,187  10-25-11  12:54  MCM2400  INI        649  10-25-11  12:54  MCM2496M INI      1,381  10-25-11  12:54  MDM144   INI        684  10-25-11  12:54  MDM144BN INI        801  10-25-11  12:54  MDM144S  INI      1,125  10-25-11  12:54  MODEM    INI         65  10-25-11  12:54         13 file(s)  10,835 bytes  98,451,456 bytes free

DEL  filename

Deletes the specified filename from the system. Wildcards (*) and (?) are permitted to delete multiple files.

EXIT

Exits the NetMRS program. Disconnects without displaying any messages.

HELP

Displays the NetMRS command listing. Identical to the <?> command.

IPCONFIG

This command works just like the basic DOS IPCONFIG command. For advanced options and switches, run IPCONFIG under the SHELL command

ipconfig < y.dat > dosshell.txt Windows IP Configuration Ethernet adapter Local Area Connection:         Connection-specific DNS Suffix  . :          IP Address. . . . . . . . . . . . : 192.168.0.2         Subnet Mask . . . . . . . . . . . : 255.255.255.0         Default Gateway . . . . . . . . . : 192.168.0.12

L

Displays the last command. Press <Enter> to execute the command or edit as necessary.

PASSWORD newpassword

Changes the NetMRS logon password. The system will ask for confirmation of the new password. This command has no effect on the applications password. The password is in the encrypted file “PASSWORD.TXT” on the root of the AEI Application drive.

PING

This command works just like the basic DOS PING command. For advanced options and switches, run PING under the SHELL command.

ping 192.168.0.12 < y.dat > dosshell.txt Pinging 192.168.0.12 with 32 bytes of data: Reply from 192.168.0.12: bytes=32 time=1ms TTL=128 Reply from 192.168.0.12: bytes=32 time<1ms TTL=128 Reply from 192.168.0.12: bytes=32 time<1ms TTL=128 Reply from 192.168.0.12: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.0.12:     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 0ms, Maximum = 1ms, Average = 0ms

PT Portfile

Attaches to defined ports. For example, if logged into the local port, you could attach to the modem port ($REMPORT.DAT) and execute AT commands to the modem. <ESC>-C exits the PT attach utility.

Note:  Legacy ports only-not compatible with ports 3-6 on network capable APU-102s.

REBOOT

Performs a software reboot. You will be prompted for confirmation. After the reboot, you will need to re-establish the connection to proceed.

SHELL command argument switches

Any commands entered after the SHELL command will be sent to DOS command shell and treated as a DOS command. Batch files and DOS programs can be executed as well as commands embedded in the DOS command interpreter, such as COPY, ECHO, REN, DIR (with switches), etc.

Caution

Use extreme caution with the SHELL command. Any command issued must NOT require any user intervention to complete the command or the APU will be inaccessible via the current port until it is rebooted. Some commands could even hang the NetMRS application. Shell commands should only be used by experienced users. Additionally, NetMRS emulates Windows XP version of DOS and has different options than ROMSHELL which is DOS 5.0. Without the “/y” switch to force an over-write in the following example, Windows DOS would prompt the user to confirm the over-write an existing file, and would hang the port.

Example:

SHELL COPY SPECIAL.BAT SPECIAL.BAK /y

T

The Set Date/Time (T) command displays and sets the APU-102 date and time.

Current time Sun Jun 01  13:30:18 2004 Enter New Date mm/dd/yyyy >06/01/2004 Enter New Time hh:mm:ss   >13:30:18 New time Sun Jun 01 13:45:00

1)  Type the T command and press <Enter>.

2)  Type the date in the format indicated and press <Enter>.

3)  Enter the time in military time format (24-hour clock, hh:mm:ss) and press <Enter>. The new date and time you established displays at the bottom of the screen.

TYPE filename

Displays the contents of the filename entered after the command.

-NetMRS- C:\AEI>dir m*.ini ATZS0=0 ATE0 ATV0 AT&C1 AT&D2 AT\N3 ATS7=60 ATX1 ATS0=1

Example: TYPE Command with MODEM.INI filename

VER

Displays the NetMRS version.

ZREC

The Zmodem Receive File(s) (ZREC) command places the APU-102 in Zmodem receive mode. The files will be received into the current working directory. Zmodem can receive multiple files.

1)  Type the ZREC command and press <Enter>. The message, “Ready to receive,” displays.

2)  Once the APU-102 is in the receive mode, use the Zmodem protocol on your communications program to initiate a file transfer or a file upload. Use wildcards (* or ?) to upload multiple files. Refer to your communications software package for instructions on sending the file.

After file is received, the message “N file(s) received successfully” displays (N representing the number of files.) and the -NetMRS- (path)> prompt re-displays.

If there are errors in the modem’s transmission, one or all of the following messages may display (where N represents the number of files).

N port overrun errors	Serial port has at least one overrun.
N byte framing errors	Serial port has at least one framing error.
N parity errors	Serial port has at least one parity error.

These errors are normal and the Zmodem protocol is designed to correct for them. If they become excessive, you may need to repair either the serial port or the modem.

ZRECR

The Zmodem Receive Resume (ZRECR) command places the APU-102 in Zmodem receive restart mode. The files will be received into the current working directory. Zmodem can receive multiple files. If a file already exists on the unit, Zmodem will resume transfer of the existing file at the point where the previous transfer was interrupted. With ZRECR, previously interrupted transmissions can continue, which saves time.

Note: The resume is done blindly, with no checks to ensure that the existing file has the same contents (up to the point of interruption) as the sent file. This means that if the file is a different version, the new file may be corrupted. Only use ZRECR on file transfers that you know were previously interrupted.

1)  Type the ZRECR command and press <Enter>. The message, “Ready to receive,” displays.

2)  Once the APU-102 is in the receive mode, use the Zmodem protocol on your communications program to initiate a file transfer or a file upload. Use wildcards (* or ?) to upload multiple files. Refer to your communications software package for instructions on sending the file.

After file is received, the message “N file(s) received successfully” displays (N representing the number of files.) and the -NetMRS- (path)> prompt re-displays.

If there are errors in the modem’s transmission, one or all of the following messages may display (where N represents the number of files).

N port overrun errors	Serial port has at least one overrun.
N byte framing errors	Serial port has at least one framing error.
N parity errors	Serial port has at least one parity error.

These errors are normal and the Zmodem protocol is designed to correct for them. If they become excessive, you may need to repair either the serial port or the modem.

ZSEND filename

The Zmodem Send File(s) (ZSEND) command places the APU-102 in Zmodem send mode. Zmodem can send multiple files.

The message, “Ready to send,” displays. Use wild cards (* and ?) to send multiple files. Refer to your communications software package for instructions on receiving the file. Most programs will auto-receive, but have differing options when receiving a duplicate file. Insure your program does not blindly “resume” when receiving a duplicate file. After file has been sent, the message “N file(s) sent successfully” displays (where N = number of files) and the -NetMRS- (path)> prompt redisplays.

Note: Refer to your communications software package for instructions on receiving the file.

Additional Commands (Not in HELP file)

You can change to a different drive as you would in DOS. Example: Type D: and press <Enter> to change to the “D” drive.

Note	On the L-Series APU-102, the AEI application files are on the D drive. The Operating System files are on the protected C drive.