• No labels

2 Comments

  1. At the end maintenance on 8/24, DSM 305 did not display any data. However, it was possible to ping DSM 305 from the ADS station. Prior to RF09 the CPU card (01331) and the A/D card was swapped out. Catherine made the necessary adjustments for us in the configuration regarding both cards. When the DSM was tested, it did not function...and we were not able to ping the DSM either.

    At the beginning of maintenance on 8/26, the newer CPU (02825) was removed and replaced with the original (01331) - thinking that if we could ping the original CPU, that would be the best place to begin our troubleshooting.

    This proved unsuccessful in the Nose, but we were able to ping the DSM when powering it up inside the plane with the Ethernet connection going directly to the back of the ADS station. However, the DSM did not boot entirely.

    We tested the Nose DSM Ethernet cable from the Radome to the ADS station. It tested Good.

    We took the DSM back to the Nose and tested it with power and Ethernet ONLY. Able to ping the DSM from the Nose for the first time today.

    Plugged in the Console connector so Catherine could communicate with the DSM from the cabin. Still able to ping.

    Plugged in the IRIG connector. No longer able to ping DSM.

    Swapped out Timing Card and tested DSM in cabin. CPU boots but Catherine finds that it is missing data in the /opt directory and the /boot file looks as if it may be corrupted. It is suspected that this may have been caused by the inadvertent aircraft power drop which occurred during maintenance on 8/24.

    Reinstalled CPU card (02825) from RF09 pre-flight. Tested in the cabin and everything looks good. Powered up in the Nose and everything operates as it should. Data reporting on all channels.

  2. Thank you for troubleshooting the nose DSM, it is the most critical one.

    Please take a look at the wing DSM on the next opportune maintenance day.