Skip to main content

I am trying to run Legacy engines using DCS and cannot get the SER2 to communicate to the Legacy Command Base. The equipment is per pg 229 of the DCS WIFI Companion: Rev L TIU v6.1 > #50-1032 cable > SER2 module > 6-81499 LCS DB-9 cable > Legacy Command Base v1.60. Wifi is through DCS.  Individually, DCS and Legacy work perfectly on the layout. The problem exists even when using the DCS remote or an older iPod that does not have the recent updates. Basically, the SER2 module's green LED flickers when receiving commands but the Command Base shows no response (nor does the Legacy engine).  However, the remote is able to communicate to an engine if the SER2 is removed and the TIU is connected directly to the Command Base using the 50-1032 cable. I checked the continuity of the LCS DB9 cable per Dave Olson's diagram and believe it to be OK.

Any thoughts on how to check the SER2?

Original Post

Replies sorted oldest to newest

I remember being part of a troubleshooting conversation about a similar scenario with a SER2 and base recently in one of the forums. I then did some testing because I had on hand an older TMCC base, also a Base-1L, and of course my Legacy base.

What was clear to me plugging and unplugging the 9 pin serial cable from each base to the SER2- there is a handshake that attempts to happen from the SER2. It sends basically a challenge to the base firmware and expects a response. This is how it can tell if it is connected to a valid base- but also a side consequence of testing what firmware is on the Legacy base. If your base is not at the latest firmware, it won't have the firmware code to negotiate this handshake with the SER2 module, but yet would work as a serial port for other operations.

Just saying, might be worth checking the update on that base firmware.

Vernon, did you read this?

Yes I did, and just because I read that and it's STILL not working, it's one thing a person could check and make sure.

I'm trying to figure out why suggesting something like that is a bad thing? He's literally sitting there his weekend because he cannot use it and Lionel support is not available until next week. So, would attempting one simple verification or trying to update the base be one thing he could do while waiting on Lionel support?

Last edited by Vernon Barry

Another possible conflict would be something using the screw terminal connection like older TMCC modules on the SER2 ? Yes, the original post does not list any such usage or connection but again the SER2 manual discusses this can conflict with the 9 pin serial port.

https://www.lionelsupport.com/...50SER2UsersGuide.pdf

page 12

You may use either the three screw terminal connector or the DB9 connector
on one SER2. You may use both the DB9 and the comm/output screw terminals
simultaneously. However, if your configuration requires using the SER2's INPUT
screw terminal as well as the output, you cannot simultaneously use the DB9
connector. In this case, add an additional SER2 module to your layout.

Again, just trying to flush out other scenarios besides the SER2 being "bad".

I appreciate the follow-up gentlemen; the base was updated by Lionel a few years ago. The version number I listed is what the base displays during power up.

There are no other connections to the SER2 other than the MTH cable and the DB9 kit. In consideration of the cost of shipping and repair, I found a new SER2 for $36, so that is my next step.

The biggest time sink for me has been believing the SER2 was functioning properly because of the flickering green LED when sending commands. I will post an update once I know more.

Add Reply

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