System test procedure
Verify Train Recording Operation
1) Log onto the APU-102, System Menu. Start a file capture on your portable computer. This logs all the data you are displaying to a file on the portable. It is recommended to create a file referencing the site name so you can look at it later and compare results.
2) Run the Dump Data Summary Report (DDS,*) and Dump Data Full Report (DDF,*) for all trains stored on the APU-102. These reports display all the trains recorded on the APU-102 in summary and full composite formats. Press <ESC> to stop the report at any time.
3) Close the capture file, browse to it if necessary and open the capture file you just created to check the following information in the train files:
Axle Summary
In the DDS portion of the report, make sure that the WDA counts match the WDB counts and the WDAB/WDBA counts match the total number of axles listed in the Axle Summary column. If there are missing axles or the WDA and WDB counts are not the same and the train did not stop, check the wheel detector operation and parameters again. You can tell if the train did not stop by checking the value in the Minimum field in the Speed Summary column.
Reader Summary for AVG
In the DDS portion of the report, make sure the average handshakes on both antennas for the highest speed train is still 3-4 handshakes at the minimum. Check the Tags Read field for each tier to make sure they are approximately the same. If your average handshakes are high (above 4) on both channels and there are a few missing tags on a channel, it is safe to say that those tags are really missing or damaged.