I'm trying to lash up two PS2 switchers 20-2497-1 and 20-2684-1 in that order. Every time I try to create the lash up, after naming it, it says check track before saving the lash up state. After the lash up is in the active screen, I can't do anything with it, not even start up. It says check track, engine not on track. The batteries in both engines are fully charged, there the one two engines on the track when creating the lash up and the signal strength is 10. Oh and the engines are right next to my TIU. I'm using the remote not the app. Any ideas? 

Attachments

Photos (1)
Last edited by Trainlover9943
Original Post

Try doing it again, only use a separate length of track not hooked up to layout or take all stuff off track that has a third rail roller, shouldn't have to do that. I have my layout divided into blocks and all my lash ups are built with nothing else in that one block, and all other blocks turned off.  two units should go easy. If that doesn't work you might be missing something.

First of all, do each run correctly on their own?

Did you try each in conventional mode?

Something is usually wrong when you're seeing those messages as you are. The remote isn't getting the proper response I believe. 

I went thru this recently and one of the batteries was failing. 

" on Sour mash and cheap wine " ??

Why go back to DCC when I have DCS!

Engineer-Joe posted:

First of all, do each run correctly on their own?

Did you try each in conventional mode?

Something is usually wrong when you're seeing those messages as you are. The remote isn't getting the proper response I believe. 

I went thru this recently and one of the batteries was failing. 

They both work fine individually in command and conventional. The batteries in both are fully charged. 

Something to try: (from Barry B. several years ago, I think) If you can get the MU on the active screen on the remote, "Inactivate" the MU on the remote, then go to "Inactive list" and reactivate the MU. Now try it. 

That's worked for me when (sometimes) MU's get "confused" between operating sessions.

Jeff

Jeff Horn posted:

Something to try: (from Barry B. several years ago, I think) If you can get the MU on the active screen on the remote, "Inactivate" the MU on the remote, then go to "Inactive list" and reactivate the MU. Now try it. 

That's worked for me when (sometimes) MU's get "confused" between operating sessions.

I tried that. After I reactivated the MU, and attempted to start up it gave me engine not on track but no check track. Again, still can't start it. 

I just looked up that first switcher and it's from 2004. Does it have the stock battery still inside?

There's something wrong that the remote is seeing with your engines and/or choices. At least one of them is not responding properly in the lash-up.

What version of DCS is this in the remote? TIU?

" on Sour mash and cheap wine " ??

Why go back to DCC when I have DCS!

Last edited by Engineer-Joe
Engineer-Joe posted:

I just looked up that first switcher and it's from 2004. Does it have the stock battery still inside?

There's something wrong that the remote is seeing with your engines and/or choices. At least one of them is not responding properly in the lash-up.

What version of DCS is this in the remote? TIU?

I'm not sure on the battery as I got it used. I'd imagine its replaced. TIU has 6.0. Remote has 5.0. FWIW, I tried a lash up with a different rear engine (20-20145-1)  with the PC S2 in the lead and got the same results. 

Last edited by Trainlover9943
Trainlover9943 posted:
Engineer-Joe posted:

I just looked up that first switcher and it's from 2004. Does it have the stock battery still inside?

There's something wrong that the remote is seeing with your engines and/or choices. At least one of them is not responding properly in the lash-up.

What version of DCS is this in the remote? TIU?

I'm not sure on the battery as I got it used. I'd imagine its replaced. TIU has 6.0. Remote has 5.0. FWIW, I tried a lash up with a different rear engine (20-20145-1)  with the PC S2 in the lead and got the same results. 

Whaaaaaaaaaa!!!!!!!!!!!!!!

You have to update your software. Both have to have the same software to talk correctly to each other. The remote is not getting the proper answer because it doesn't know the proper question!

5.0 had issues with this. 5.0 can't talk to 6.x as it doesn't have the codes.

" on Sour mash and cheap wine " ??

Why go back to DCC when I have DCS!

Last edited by Engineer-Joe
Engineer-Joe posted:
Trainlover9943 posted:
Engineer-Joe posted:

I just looked up that first switcher and it's from 2004. Does it have the stock battery still inside?

There's something wrong that the remote is seeing with your engines and/or choices. At least one of them is not responding properly in the lash-up.

What version of DCS is this in the remote? TIU?

I'm not sure on the battery as I got it used. I'd imagine its replaced. TIU has 6.0. Remote has 5.0. FWIW, I tried a lash up with a different rear engine (20-20145-1)  with the PC S2 in the lead and got the same results. 

Whaaaaaaaaaa!!!!!!!!!!!!!!

You have to update your software. Both have to have the same software to talk correctly to each other. The remote is not getting the proper answer because it doesn't know the proper question!

5.0 had issues with this. 5.0 can't talk to 6.x as it doesn't have the codes.

That would explain it. I'll update the software on the remote. 

Last edited by Trainlover9943

Add Reply

Post
The DCS Forum is sponsored by
OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
330-757-3020

www.ogaugerr.com
×
×
×
×
Link copied to your clipboard.
×
×