General

Releases

Version 5.2.0.17

media:File:V5.2.0.17Full.zip

Special Release only:

New: Support for TDM and DCL segments

New: Support for tag data format 7

NOTE: Train processor is not included in this update.

1. Fixed: If configured for DHCP, unit can enter reboot loop if

addresses isn't assigned by the time ETHOBS starts.

2. Fixed: Reporting via the dial-up modem not working

3. Fixed: Upload/download problems when using Teraterm

4. Fixed: MPRX initialization files deleted under certain circumstances.

5. New: Update to communications software to allow reporting with

encrypted transmission protocols including ftps, sftp, scp, https.

Version 5.2.0.16

1. Fixed: ZPUT/ZGET commands not working: work-around for this issue is

that port number must be specified (typically 23) (issue #28).

2. Fixed: scale issues (weight now collected from scales without an end

of line specified); intermittent missed weights from certain scales.

(issue #125)

3. New: DDSC command to display contents of scale data file.

4. Fixed: Telnet protocol issues that caused problems with certain terminal

software.

5. Fixed: corrupted train directory file (STATE.FSB) caused a crash and would

result in unit going into NETMRS mode.

6. New: support Transcore MPRX report. (Issue #173)

7. Fixed: Corrupted STATE.FSB file could cause application to hang.

(Issue #157)

8. Fixed: Long filenames could cause issue with remove command.

Version 5.2.0.15

1. Fixed: MR with reboot loses user-entered starting sequence number (issue 123)

2. New: "[BEGIN]" statement in scale configuration file specifies scale message

that indicates start of weights for current train (to handle cases where scale

emits a weight from a previous train) (issue 124).

3. New: Support for future Secure SHell (SSH) update.

4. New: ?? command shows all available commands in alphabetical order.

5. New: PASSWD command (SSH passwords) available only on session-1.

6. Fixed: Value for DigitizerMaxFileSizeKBytes is inspected at startup and

limited to 10000 KB (10 MB).

7. Fixed: it was possible to lose the last weight from a scale (scale sends it

but it is not included in train consist). (issue 125)

8. Fixed: ethernet observer was failing to clear an error counter when certain

network faults cleared resulting in unneeded reboots after several

occurrences even if the occurrences are days apart. The reboot should

occur only after the fault persists for several minutes. (issue 132)

9. EW command could cause part of a train to be lost. (issue #133)

10. '/' command now displays "release candidate" version info (e.g. "RC3").

Version 5.2.0.14

1. Fixed: train sequence number assigned to "conversion note" log entries

when no train is present on local track was "65535". (issue 120)

2. Fixed: Help for ABDD? command added; help text for AB* commands corrected.

3. Fixed: LF *, DDF *, DDT * commands caused reboot. (issue 121)

Version 5.2.0.13

- Not released.

Version 5.2.0.12

1. Fixed: DTRACK-IN stuck "active" pin could prevent train acquisition even

if unit is configured for single-track operation (issue 91)

2. Fixed: Watchdog could reset the unit when Ethernet observer detects a

connectivity problem even if a train is passing; observer now waits

(maximum of twenty minutes) until the train clears. (issue 88)

3. Fixed: Double-track sites aren't issuing the same event log messages

(presence clear and conversion note) issued by 5.1 software when train

passes on adjacent track. (issue 95)

4. Fixed: CPU3 harvester was disabled (issue 96)

5. Fixed: If CPU3 harvester is not enabled, files sent by FTP to the APU can

accumulate in the CPU3FTP directory until unit runs out of disk space; this

version keeps this directory clean. (issue 96)

6. Fixed: empty tag reader configuration file could cause crash.

7. Fixed: TDA204 command now available when train is present (will cause

train acquisition to be aborted).

8. New: DDTI command allows viewing of tag reads received from adjacent track.

9. New: ABORTDIR command shows extra info: date/time as well as data

available for download.

10. Fixed: Site issues resulting in numerous aborted trains could result in

too many files in the ABORTED directory that could result in low disk

space conditions.

11. Fixed: SYS LED should go dark when AEI application exits. (Issue 105)

12. Fixed: DDF command sometimes has extraneous text in column headings.

(Issue 102)

13. Fixed: Watchdog reboots system if TDA204 command is left running too

long. (Issue 107)

14. Fixed: changes to master input (multi-presence input function) from

parameter editor not being saved to configuration. (Issue 99)

15: Fixed: MRR command not deleting ACQ0???? files.

16. New: commands added to allow convenient viewing of aborted train

data (ADBBW, ABDDDT, ABDDC, ABDDTI)

17. Fixed: at yard sites, certain moves resulted in a log message that

resulted in a crash. (Issue 115)

18. Fixed: sporadic crashes when attempting to deliver train consists via

FTP. (Issue 116)

19. Fixed: missing HBI and SIM segments at sites with defect detector.

(Issue 119)

20. Fixed: report attempts after 32,000 consecutive failures could cause crash.

Version 5.2.0.11

1. Fixed: ACQ wasn't deleting "orphan" files (issue 83)

2. Fixed: Toggling presence input could cause exhaust disk space (issue 84)

3. Fixed: resource leak found while working on issue 83 (silent - no reports of

problems in the field.)

4. Fixed: intermittent issue where false wheel pulse at startup would cause

tag reader activation. (issue 79)

5. Fixed: last tag counts not retrieved if tag reader is running E4 firmware.

(issue 66)

Version 5.2.0.10

1. ACQ Process now saves pre and post train files after aborted train

2. Presence of ITCALTTO.SEM file will cause ITC to timeout quicker

Version 5.2.0.9

1. Fixed: SHS command would cause a reboot at sites running without

a tag reader.

2. Fixed: low speeds were reported at sites with a TDA204 if pre-trigger

digitizing was enabled and clock rate was changed from high to normal.

3. Fixed: if ACQQUEUE.DAT file became corrupted, system would hang until

watchdog triggered.

4. Fixed: an issue preventing clock mode changes (TDAA204) wasn't working.

5. Change: Transducer balance check now occurs only after a train passes.

6. Fixed: on-board WD LEDS (TDA204) weren't working if imbalance detection

was on.

7. Fixed: TR (terminate record) may not work at high speeds.

8. New: The '/' now displays TDA204 info (if equipped).

9. New: Log message added to note digitizer overflow (error 153: digitizer

overflow).

10. Fixed: a corrupted session log could cause reboot.

11: New: (TDA204) added gain/threshold settings for individual wheel detector

inputs.

12: New: (TDA204) added event reporting for blown fuses (messages 151: fuse

alarm, 152: fuse OK)

13: New: (TDA204) pre-trigger digitizing can be disabled in parameter editor.

14: Change: TDA204 command now restricted to "supervisor" mode.

15: Change: Set default imbalance detection threshold at 1 volt.

Version 5.2.0.8

1. Support for long trains (250+ cars) and high axle count cars

2. Support for TDA204 card

3. Support for shared tag reader

4. Fixes for various CPU3FTP issues

5. Wheel detector panel LEDs now mirrored on AUX1 block (in "calib mode")

to support trackside adjustment at sites without TDA105

6. Improved support for PuTTY and Teraterm clients.

7. New TDA204 command to provide visibility of TDA104 and TDA204 operation

for tuning and troubleshooting.

8. Automatic check for wheel detector imbalance after train exit (TDA204 only);

includes new error codes. Default is "off".

9. Various fixes.

Version 5.2.0.7

1. CPU3FTP process has been added

2. Corrected data transfer delay caused by ITC that can happen when a train

passes on one track and the other track is clear

3. ST command can now accept a direction (N,S,E,W,L,R,<,>) as an argument to

force the simulated train to be recorded in the specified direction

4. DNS cache obeys time-to-live value received from name server

5. Added ability to disable DNS caching altogether

6. APU can have a user defined acknowledgement character

7. IP of connected user logged when front door is accessed

Version 5.2.0.5

1. Added S918B RAT segment.

2. Modified SYS command to allow specifcation of process ID and pause/continue (/P /C)

options at the command line.

3. Improved reliability of FTP transfers to hosts with slow connections

5. Support for two step train processing that improves function with other

trackside equipment that depend on AEI, requires at least Proc0326

Version 5.2.0.4

1. Distributed AEI now working on LX800

2. Removed unnecessary log messages during readerless operation

3. Added support for STUCKOFF.DAT features via parameters

4. Added support for HBD harvesting via ethernet

5. Maintenance via FTP support custom file names

6. Alternate user prompt supported

7. Idle timeout can be adjusted between 1 and 20 minutes

8. Unexpected return values from the train processor are logged

9. DEM segment support added

10. Added the ability to make the alternate telnet port the only telnet

port for front door access

11. Improved support for shell command when multiple users are connected

12. ETHERNET channels are unconditionally forced to be connection based.

13. Improved Ethernet Observer's handling of communication issues

14. Improved reliability of NTP process

15. Increased number of telnet front door threads, by default we listen

on ports 23 and 1023

16. Supports front door listening on a user defined alternate telnet port

17. Improved opening of the reader port during startup

18. Corrected issue with time zone reported by DetectorSupportThread

19. Improved handling of reporting via unreliable modem connections

20. Recovery method implemented for unsuccessful IP assignment

21. All files are now retained after an aborted train

Version 5.2.0.3

1. Added IO command. It allows viewing of the IO changes in a list form.

2. Added the ability to specify which IO signals are logged (Acquisition.Operating.DifferentialInputMask and

Acquisition.Operating.Differential.OutputMask). These should be set to 0 unless instructed otherwise

by Comet Engineering).

3. Now supports presence detect mode 4 (Acquisition.Operating.PresenceDetectMode). This mode instructs the

software to ignore external presence signal until wheel activity is first seen. Useful when non-contacting

presence devices are in use (radar, acoustic, etc).

4. Added the ability for the software to automatically recover and reprocess trains that were unable to be

processed initially due to resource limitations.

5. For GEMicroHBD processing, AEIPRELIMPROC.BAT is no longer used. It has

been replaced by FASTPROC.BAT.

6, Complex movement types (includng "NoMove","Through","ReverseOut","Jockey","Pickup","Setout") are identified.

and displayed in the system log.

7. Supports improved timebase logging for differential io. Can now handle trains that park on sites for more

than 24 hours.

Version 5.2.0.2

1. Added commands:

DA - display every train aquisition

DDAI - display raw aquisition file data

R,T - The APU will reboot after a train passes that meets the

(optional) minimum axles and speed requirements.

R,T [min axles] [min speed]

2. Custom file name for FTP reporting supported

Version 5.2.0.1

1. Added commands:

ASYS - display archived system logs

EW - ?

FTP - tests connection to supplied FTP server

HELP - displays all available commands

HR,NOW - force any pending session report without waiting for timeout

IBACKUP - backup current image

IPCONFIG- identical to Windows IPCONFIG command

IRESTORE- restore previously backed up image

MM - display system log message counts

NOTE - site specific note management

NTP - forces NTP time sync

PING - identical to Windows PING command

R,C - Changes to write protected partition are saved to disk

and the APU is rebooted (LX800 only)

R,T [min axles] [min speed]

STARTNET- force restablishment of IP address

USER - used to manage user accounts with strong password support

2. User names and strong passwords supported

3. 10 sessions (reporting and maintanence) supported

4. 10 simultaneous telnet connections into the APU supported

5. Ability to specify alternate telnet port for APU access supported

6. XTrack added

7. Logging of cubic acoustic presence detection supported

8. ReportingOrder supported, if enabled lower numbered sessions take priority

9. KLD "GO" passenger cars supported

10. CPU Type is identified on login

11. Modemless operation supported, if running modemless that is noted at login

12. Primary AND secondary NTP server now supported

13. Distributed AEI now supports network transfers

14. Master Reset command (MR) allows user to specify starting train id

15. Increased size of system logs and added log archive which creates the

16. ability to recall much older log messages

17. Improved support for ZPUT and ZGET commands

WDI Driver updated?

IO event recording?

Added ACQProcess for saving/reporting of raw aquistion files?

Defensive mismatch?

Support for additional rail cars and yard processing?

Changes to DST?

Version 5.1.1.106

1. Corrected issue with front door not terminating when carrier was dropped

Version 5.1.1.105

1. Fixed watchdog timeouts with unresponsive FTP servers

Version 5.1.1.104

1. Now trims whitespaces from reader responses to support E4 reader.

2. Added "special command" capability to the reader INI files to modify the

readers handling (to support E4 and MPR nuances).

3. Corrected issue that affected session 2-4 "report transmit" times.

4. Corrected issue that caused multiple simultaneous transfers to contain report errors.

5. Corrected issue that caused thermal harvesting to quit working over time (requiring a reboot).

Version: 5.1.1.103

1. Parameter editor now supports dumping to and loading from a file. After issueing

the EP or DP command to access the parameter editor, use the DF command to dump

to a file (instead of D) and the LF command to load from a file (instead of L).

2. "Console" port is now supported.

3. Fixed issue that caused 7-E-1 reporting to not work properly.

4. Fixed issue that caused NetModem server threads to periodically not work.

5. Added logging of reboot cause anytime the app intentionally reboots or restarts itself.

6. Added support for ""UseAlternateRemoteFilename" in FTP INI file. If "yes", the consist

is sent to the FTP server with the filename format:

"AEM<USIDOwnerID:5><USIDUnitNum:7><TrainStartDate in YYMMDD> <TrainStartTime in HHMMSS><TRAINSEQ:4>.TXT"

7. Removed unused DST Parameters from "DaylightSavings" section.

8. Added "DaylightSavings.CustomDSTRulesFilename" that allows specification of a Comet supplied DST rule file.

If blank, it assumes US rules. MEX_DST.DAT is supplied to support the Mexican rules.

Version: 5.1.1.101

1. Added support for longer host names in FTP INI files

2. Added NTP service

3. Any host reporting method dependant on cURL will not function unless the directory

C:\Program Files\AEI is present on the system

Version: 5.1.1.100

1. Added the ability to send commands to FTP hosts.

2. Added support for reporting using a batch file

Version: 5.1.1.99

1. Fixed issue with harvester reporting multiple alarms on car

Version: 5.1.1.98

1. Modified NTP process to bring it inline with the HCP103X

Version: 5.1.1.95

1. Added support for Codeline External Temperature Probe with new commands: XTP,

XTPDEBUG, XTPNOW, and XTPHISTORY.

Version: 5.1.1.92

1. Eliminates shutter issue caused by <ESC>C breakback sequence on GE MicroHBD units.

<ESC> C guard time has also been eliminated when connected to detectors passthrough

connections.

2. Support for more Detector Support Threads added.

3. Single partition and dual partition flash cards are now both supported.

Version: 5.1.1.89

1. Support for DED segment (dragging Equipment) when harvesting from the Servo 9000

2. Support for SIM segment reporting data anomalies with the Servo 9000 (example:

MISS and OPEN in the temperature field, no ambient temperature available)

3. Support for harvesting car side alarms from the Servo 9000

Version: 5.1.1.87

1. Added ZPUT, ZPUTR, ZGET, ZGETR, and CLEAN

Version: 5.1.1.47

1. NetMenu now supports 8 different connections and all setup is done on one system.

2. Support for 2.1, 2.0, 2.06 con6, and 2.06 con7 Cyberscan 2000 detectors.

3. Support for 02/09/98 CR9941I and 11/03/98 CR9980L Servo 9000 detectors.

4. Support for 6.6A MicroHBD detectors.

5. Standard Microsoft versioning rules are adhered to (ex X.X.X.X).

6. Train directory command (D) now reveals whether HBD harvesting has taken place for each

train. An H will appear next to the entry if harvesting took place. An M will appear

next to the train if that data was successfully applied to it.

Version: 5.10 Build 2 September 14, 2007

1. Added "HR NOW" command to cause immediate reporting.

2. Added "SET TELNET ON/OFF" command. When connected to site via dialup or local serial

connection AND a network passthough (PT) connection is made to another box, specify

"SET TELNET OFF" if ZMODEM transfers are not working correctly.

Version: 5.10 Build 2 September 12, 2007

1. Added support for NETMODEM.

2. ZMODEM over IP (Telnet) now works properly.

3. Added support for Code Activated Switch (link device type = 5).

Version: 5.10 Build 1 August 1, 2007

1. Added support for "SysDiags.PresenceLoop.ExcessivePresencePeriodWarningTimeout". Specifying

a value (in minutes) causes the system to issue message 122 ("Pres Stuck Warning"). The

additional text will indicate the # minutes the site has detected a presence signal with no

wheel activity. To disable this feature, set the parameter to 0 (a reboot is required).

Stuck OFF

2. Improved "stuck off" logic.

3. When presence circuit stuck off condition is detected (message 143 "Pres Circuit Failure"

"Stuck Off"), the additional text field now includes the following information:

# axles in train, last speed & duration (in seconds).

4. Condition that caused the clock to periodocally shift by one hour when a spontaneous

reboot occurs has been corrected.

5. Added support for huge trains during ITC exchange

6. To allow more flexible presence failure detection parameter tuning, the ranges on the

following parameters have been increased.

MinAxles

LowSpeedThresh

HighSpeedThresh

PresTimeOutAboveSpeed

PresenceTimeoutSeconds

SecondsBetweenTrains

7. Default host response size allowble increased from 64 tp 1024 bytes. This may explain the

rare spontaneous reboot on maintenance transactions.

8. If the software detects a slow ITC com issue (known as "push failure"), message 91 ("Extern

Com Warning") is logged with the additional text "ITC Com Slow (Overflow)". This is an

indication of a probable COM4 hardware issue.

9. Release package now includes the B0 SP1 changes.

Changed Files:

PARM.HLP

APUERROR.DAT

APU102.EXE

Version: 5.10 Build 0 February 2, 2007

1. Added support for new 2007 DST rules.

2. Corrected host sync "push back" when site prematurely enters new DST state.

3. Added support for "ReferenceTimeZone" parameter (supports 2 zones west of reference zone).

Changed Files:

* APU102.EXE

* APU.BAT - corrected support for "RunOnce.bat"

* BACKUP.BAT - Added .HDR and .SEM to the backup list.

Version: 5.09 Build 9 May 16, 2006

1. Support for "$USEPLUSPLUSPLUS" (item 3 in Build 8 notes) causes problems

in the field. A revised MCM2496.INI file was sent to all build 8 sites and

is included here to update older files. The problem will be fixed in a

later build and the original MCM2496.INI will be restored.

2. Power alarms not reported in T94 report header (Trac 2)

3. Code changes to address WD timeout after record complete message (Trac 6)

4. No longer possible to ZSEND (or XSEND) data files for a train that is

being recorded (allowing this can cause data loss). (Trac 7)

5. WDI code now uses software timestamps for tag pulse timestamps at start

of acquisition until hardware timer is stable. (Trac 20)

6. Fixed: sometimes, report lines were lost if "pause" option was selected

by user. (Trac 24)

7. Corrupted session logs now deleted by event logger at startup. (Trac 28)

8. Changes to address rare but annoying WD timeouts in event logger. (Trac 29)

9. Program crashes should now create FAULT.LOG for post-mortem debugging. (Trac 39)

10. WDM command added to see "low water mark" for thread watchdogs. This will be

used to see if any threads need longer timeout values. (Trac 41)

11. Slight performance improvement to code that scans host responses for trigger

phrases specified in ACC files. (Trac 21)

12. Fixed: occasional WD timeouts in report code when reporting to CPRR. (Trac 26)

Version: 5.09 Build 8 Feb 06, 2006)

1. Corrected error in outbound REDI code

2. This build uses a new event logger which reduces the chances of a

corrupted log file (session log reset) messages. The new logger is

compatible with files used by the previous event logging code so

version rollbacks can be done without loss of event data. The new

logger runs as its own process (process ID is 23).

3. Added support for "$USEPLUSPLUSPLUS" modem directive to address rare

occasions where the 2496 modem fails to go onhook.

4. Additional debug code was added to capture info when occasional ITC

COM failures are logged (these are cases where the ITC channel fails

for a couple of minutes). So far, no definite cause has been

determined. The alarm timeout for ITC was increased from two to four

minutes to reduce the number of nuisance alarms. This is not a fix.

5. Fixed bug in SYS command that resulted in incorrect output if a

a specific PID was entered (e.g. to view only event messages for REPORT1).

6. Fixed a potential "infinite loop" bug that may be causing occasional

WD resets during train post-processing.

7. Fixed: Tag data from single-track sites was indicating ITC failure

which affects confidence logic.

8. Fixed: invalid movement and train termination status was, sometimes,

being sent in T94 header when train reports were delayed.

9. Fixed: watchdog was attempting "fast restarts" when a reader problem

was detected. Fast restarts are reserved for reporting hang-ups only.

10. Fixed: invalid memory access in T94 report generator was causing

occasional watchdog restarts if the last car in a train was untagged.

11. Includes support for new 56K modem card.

Version: 5.09 Build 7 Sep 08, 2005)

1. REDI interface code is enabled

2. Fixed: RFID tag records indicated an ITC failure when unit is configured

for single-track operation. This resulted in using the wrong confidence

level which results in more untagged cars.

3. Train processing no longer deletes an existing 034 (train summary) file.

Note: FIX060.EXE is included in this package for compatibility with earlier

AEIPROC.BAT files (5.09B6). The AEIPROC.BAT file in this package never

calls this program.

Version: 5.09 Build 6 (July 25, 2005)

1. ITC was not locking it's communications channel. It was still working

but it should lock the channel to be on the safe side.

2. Added new performance counters to modem handling code. Added *NEW* MDMS

command. Counters are enabled if "MDMSTATS.DAT" file is present.

3. Modem reset always sends ATS0=1 to modem (to ensure that auto-answer is on)

regardless of what's in the installed modem INI file.

4. Added new reboot modes ('R' command):

R FULLBOOT - full restart (OS restart - same as before)

R,F FASTBOOT - application restart; no OS restart (fast)

R,M FORCEMRS - force into MRS

5. PT command no longer allows pass-thru to channel the command is issued

from.

6. Changes made to code that updates the system parameter file that reduce

the chances that the file can be corrupted.

7. Express "supervisor" login. Entering the supervisor password at the initial

login will take the user directly to the supervisor mode (no need to use the

'c' command).

8. Added method to recover a unit where the password is unknown.

9. File writes are no longer cached by the operating system; file writes occur

immediately. (Previously, the OS cached writes for performance reasons. This

provided a small window of time in which data could be lost in the event of a

restart. It was determined that it was safer to update the files on disk; the

performance penalty is negligible in this application).

10. SHS command: internal testing found that when WDA/B counts differ, output of SHS

command was backwards (would say WDA is low when WDB is low and vice-versa).

11. Internal testing revealed a potential "divide by zero" error; this was corrected.

12. Added *NEW* BP command that allows the user to create a backup copy of the

system parameter files.

13. Additional validation checks have been added to code that loads the parameter

files. If the files are corrupted, the backup files (created with the BP command)

are used, if available.

14. This distribution contains a non-standard DT336.INI file. This file contains

the modem strings that set 2400 baud line speed.

Version: 5.09 Build 5 (March 03, 2005)

1. Added debouncing of modem carrier signal (Issue 37).

Version: 5.09 Build 4 (February 28, 2005)

Changes since 5.09B3

1. Fixed: occasional watchdog timeouts during T94 report generation

2. Fixed: modem power down now working

3. Fixed: application was occasionally generating numerous bogus .LOG

files during shutdown

4. The extra space at the end of an AMH record has been removed

5. A corrupted session log file (FFFFFFFx.LOG) would prevent transmission

of maintenance reports. The application now deletes corrupted logs and

logs an event message to indicate this occurrence.

6. Event log message generated if wheel event file can't be created.

7. Additional logic added to reduce chances of tag pair being reported on

two trains when ITC presence wire is disconnected.

8. APUEQUIP properly identifies later versions of startup ROM.

Version: 5.09 Build 3 (February 07, 2005)

Changes since Version 5.08

1. Scales that send A and B weights now supported

2. Extraneous space after version string was removed (appeared in T94

maintenance report header which caused processing errors at certain hosts)

3. Additional debug code was added to capture data in the event of an "Issue 9:

occasional watchdog restart during T94 report generation" event

4. All transmitted reports (consist and maintenance) are limited to 64K bytes

regardless of transmission format

5. Event logger is now disabled during shutdown to prevent occasional generation

of numerous bogus log files

6. Sites equipped with LVD should no longer see a spurious, one-axle train at

startup that was created when the LVD applied power to the wheel detector

7. Corrected bugs in internal file tracking code that was causing spurious "file

closed by another thread" messages in the event log and was causing closed

files to be displayed in the open file list (these issues affect internal

debug functions; no effect on customer functions)

8. Error #146 is now assigned as "log full". This message is issued after a

maintenance log gets deleted because it's too large to transmit in a report

less than 64K is size (see #4)

9. Process names for SCALE and WDOG corrected; Errors #138 and #139 changed

from "Extern Alarm" to "DC Power"

10. Maintenance reports no longer delayed after a watchdog restart

11. Find reader code (IR command) now defaults to 4800 baud rate only if port file

baud rate isn't supported by the reader

12. Disk manager no longer deletes three most recent trains (it was improperly

deleting these trains if there were three or fewer trains stored)

13. Watchdog can now call external batch file when an Issue 9 restart occurs (see #3).

REPCRASH.BAT file shipped with this build is called to copy train and debug files

to C:\AEI\REPORT for later analysis.

14. Pending reader commands are terminated before flushing tags; tag flushing should

be faster.

Installation:

There is no incremental installation for this build since the WDIDVR.RTS file has

changed since 5.09 Build 2.

Distribution Files:

V509B3.EXE Self-extracting archive

F.BAT Run-once file to install files

ZIP.PSP Flag file (required for F.BAT to run)