My DSAB worked flawlessly for about 8 years. About 6 month ago, it started to occasionally give me a configuration error where the D10A and DMS did not detect each other. After some period of time, they would eventually detect each other and everything would work fine.
In the last month, the problem has continued to get worse and now the units never configure at all. I have tried re-seating the cables. I have Ohmed out the DSAB connections and grounds multiple times. After performing this testing the first time, the unit worked for about a week before failing again making me think it is a wiring integrity problem. Multiple retests of and inspections of the wires has failed to show any problems, however. The units now fail to detect each other all of the time. The wires all test out as dead shorts where there should be shorts, and opens where there should be opens. I have never had the system fail in flight. If the bus configures, it works. It will continue working until the next flight when it attempts to configure again.
What should my next course of action be? My thinking is that I should get an oscilloscope and and take a look at the signals on the cable. To do that, I would like to know what I should expect to see for levels, frequency, etc. Also, what termination should I use? What other tests should I run to isolate where this problem is?
Steve
In the last month, the problem has continued to get worse and now the units never configure at all. I have tried re-seating the cables. I have Ohmed out the DSAB connections and grounds multiple times. After performing this testing the first time, the unit worked for about a week before failing again making me think it is a wiring integrity problem. Multiple retests of and inspections of the wires has failed to show any problems, however. The units now fail to detect each other all of the time. The wires all test out as dead shorts where there should be shorts, and opens where there should be opens. I have never had the system fail in flight. If the bus configures, it works. It will continue working until the next flight when it attempts to configure again.
What should my next course of action be? My thinking is that I should get an oscilloscope and and take a look at the signals on the cable. To do that, I would like to know what I should expect to see for levels, frequency, etc. Also, what termination should I use? What other tests should I run to isolate where this problem is?
Steve
