Skip to main content

Well this is one those "it worked last time I played and now it doesn't" scenarios.

 Everything starts at the Legacy base with a SER2.  I have a DZ data driver plugged into the SER2 to drive my DZ2500 switch motors.  The SER2 ties into the WiFi module and down the line I have 5 BPC2s 5 Sensor Tracks and 4 ACS2s daisy chained around my layout.  To this point I had been very happy with this system.  Customizing control panels on the iPad was easy and controlling the layout with iPad and engines with the CAB2 was a lot fun.

It has been at least 6 months since I added a module or made any changes to the LCS system.  But for some reason when I fired up the layout today the red light stayed lit on all the LCS devices.  The manual said it could be a problem with the base or the wiring.  I have a spare base on my work bench.  I swapped it but that did not work.  I had a spare DZ data driver.  I swapped it and that did not work.  I have been ballasting my yard, there is no way any water/glue mix got onto an LCS module.  Glue mix could have potentially gotten on a switch motor, although I did not see any visible signs (all the switch motors are under the layout).

Anyone experience the red light of death?  Any ideas how to fix it?  Really hoping Rudy @Railsounds will see this post and offer some insight!

thanks

 

Original Post

Replies sorted oldest to newest

Solid red light means the first LCS module in the chain cannot see the command base. It sounds like this is an SER 2 in your setup. It could be a bad cable (6-81499 LCS DB-9 Cable with Power Supply) connecting the command base to the first device. I'd check with customer service and ask them to send you a replacement.  The other thing I'd try if convenient would be to swap the position of the SER2 and the LCS WiFi module in your chain of device. Then, if the LCS WiFi does NOT have a solid red LED, you will know that the LCS DB9 cable is OK. And if everything starting with the SER2 is still red, then the problem could be in the SER2 itself.

Correction to my original post...the WiFi module was/is the first module in the daisy chain.  The SER2 was physically closer to the base, but I made the WiFi module first in the chain, there must have been a reason for that, but I can't recall.  The DB-9 cable does provide power and signal.  I learned this by removing the wifi from the chain and going straight to SER2.  The really odd thing that I figured out is that the WiFi module is bad and so too is the PDI cable that left that module and went to the second module in the chain (the SER2).  Seems strange that the cable and the module failed at exactly the same time.  I wonder if one failure caused the other.  So right now with the WiFi module removed from the chain and the SER2 with the DB9 plugged into it and a PDI cable going to the second module in the chain (ASC2) there are no red lights on!

@Railsounds does any of this make sense to you?

Thanks again for the advice!

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×
×