An issue we resolved yesterday. Ironically, I was just about to update this post, too...Originally Posted by N8YX
Short story: Few months back, a near lightning hit caused some issues in one of the airport's wiring closets (there are people who don't believe in proper grounding, but that's another story). Closet holds the Device Server that controls a section of the Daktronics LED boards in Ticketing. We originally thought the DS itself was affected... it wasn't. Then we thought we had a network issue... we did, but it turned out to be minor and actually unrelated. Then we thought we had a problem with the LED boards themselves. We did.
Boards are daisy-chained together into segments of about a dozen or so boards via RS422 cabling, and each segment then goes (also via RS422) to the device server; so each of the 4 COM ports on the DS runs a segment of LEDs.
So... we figured out which segment had an issue. Started at the end of the daisy chain (LED 58) disconnected the cabling until we found the one causing issues (response time on a PING to the DS was 60 - 3000 ms instead of 1 - 2 ms). Powered down the culprit (LED 49). Looked at what modules on the board we could change. First up was the RS422 input/output board. Changed it to a 'new' one from stock, powered the board back up, no more issues. (Yay!)
Would still like to talk with an 'expert' on these things. We have 3 boards that don't respond to commands from the control server, would love to get them fixed. We know more now that we did, but we still don't know enough. And it didn't help that the previous administrator of these boards didn't leave us any documentation or notes... he took it pretty personally when his company lost the contract renewal to my company.
Reply With Quote