RF14 was scheduled for this morning. The flight was initially delayed due to fog, then ultimately cancelled for an aircraft issue found right after door close.
All cards, cables, and both end panels were swapped out of DSM 305. The only items that remained from the old DSM were the card cage and the enclosure.
Testing DSM 305 -
The new card stack does not boot with the Console connected to the DSM in the Nose. We tried booting it with the Serial to USB Adapter, but were unsuccessful.
Once the Console connector was removed from the DSM in the Nose, the DSM booted successfully each time.
*This is inconsistent with what was experienced with the previous card stack in that the previous DSM stack would only boot when the Console was connected at the Nose AND the Serial to USB Adapter was installed behind the ADS rack.
At this point we have a fully functional DSM. More testing will be done on our next Maintenance Day to ensure we did not miss any underlying operational problems. If no further issues are found, we will plan to fly the remainder of the project with the current DSM configuration. The Console connector is not a requirement and will be coiled and stowed.
The prior card stack defiantly had problems booting and for some reason needed the console port with an adapter. This card stack is behaving as I would expect if there is an issue with the console port wire or connector that was tied to the other DSM. Here the DSM you just installed worked fine either with the console connected or without. At this point I suspect there is something wrong with the wire or connector on the plane that is being plugged into the console port. I would guess that if you had another serial cable you could plug it into the DSM and it would not effect the booting of the DSM.
Great work. Hope it continues to work well for you. I would not go back to the other DSM unless there is something really wrong with this one.
4 Comments
David Allbee
RF14 was scheduled for this morning. The flight was initially delayed due to fog, then ultimately cancelled for an aircraft issue found right after door close.
All cards, cables, and both end panels were swapped out of DSM 305. The only items that remained from the old DSM were the card cage and the enclosure.
Testing DSM 305 -
The new card stack does not boot with the Console connected to the DSM in the Nose. We tried booting it with the Serial to USB Adapter, but were unsuccessful.
Once the Console connector was removed from the DSM in the Nose, the DSM booted successfully each time.
*This is inconsistent with what was experienced with the previous card stack in that the previous DSM stack would only boot when the Console was connected at the Nose AND the Serial to USB Adapter was installed behind the ADS rack.
At this point we have a fully functional DSM. More testing will be done on our next Maintenance Day to ensure we did not miss any underlying operational problems. If no further issues are found, we will plan to fly the remainder of the project with the current DSM configuration. The Console connector is not a requirement and will be coiled and stowed.
John Cowan
The prior card stack defiantly had problems booting and for some reason needed the console port with an adapter. This card stack is behaving as I would expect if there is an issue with the console port wire or connector that was tied to the other DSM. Here the DSM you just installed worked fine either with the console connected or without. At this point I suspect there is something wrong with the wire or connector on the plane that is being plugged into the console port. I would guess that if you had another serial cable you could plug it into the DSM and it would not effect the booting of the DSM.
Great work. Hope it continues to work well for you. I would not go back to the other DSM unless there is something really wrong with this one.
Kurt Zrubek
Dave,
That's unfortunate, and unexpected obviously! I like your plan let me know how things go and if you need anything. We'll talk it over here...
Kurt Zrubek
I agree it point to a cable/connector issue.