Tech Note 1020 - Recording Diagnostic Logging 

Scout 85.2 and above

 

  • Description:

This feature is designed to enable the controller to capture logs 20 seconds prior to MMU flash activation. These logs can then be transferred to CUBIC Support for a diagnosis of the fault.

  • Implementation:

To enable this feature, go to MM-8-8-5. Toggle “DiagnosticLog” to “ON.”

A screen shot of a computer error

Description automatically generated with medium confidence

Once “DiagnosticLog” is enabled, the controller will maintain a current 20 second log triggered to write to memory upon MMU flash activation (Alarm 15).

NOTE: These logs will be overwritten every time the MMU flash is activated!

Alarm/Event #15 must be enabled via MM-1-6-1 and 1-6-4

A screenshot of a computer

Description automatically generated with medium confidenceA screenshot of a computer

Description automatically generated with medium confidence

 

 

With recorded log on controller, insert a USB and go to MM-8-8-8. Press enter and the logs will then be copied onto the USB.

A screen shot of a computer

Description automatically generated with medium confidence

 

Extract the file named “diag_log.dat” and send it to CUBIC Support for decoding.

  • TS1/Caltrans Implementation:

To enable this feature when an MMU is not present you must redirect alarm #15 to Input Function #206-Cab Flash. 

(Other Input functions could be used, just an Input that goes active when monitor latches a fault.)


NOTE: Input can be seen in MM-1-9-7-1.

A screen shot of a computer

Description automatically generated with low confidence

 

 

To do this go to MM-1-6-7-2 and set Alarm #15 to be equal to Input #206.

A screenshot of a computer

Description automatically generated with medium confidence


NOTE: This must be done for diagnostic logs to be capture on a TS1 or Caltrans cabinet.