I noticed some things about lash-ups with v1.2 that are different than before. When I designate an engine as the second engine in a lash-up and reverse it, that engine's default direction (when addressed later as an engine) also gets set to reverse. Previously, even when an engine was reversed in a lash-up it retained its default forward direction when run separately. Also, now I need to have that second engine already running in reverse before I address it with the first engine as a lash up or else it will not change to reverse and runs in the opposite direction than it should with its cab lights on. If I have the second engine already running in reverse, and address the lash-up at least then that second engine knows to turn off its lights and remain running in reverse. When I reverse the direction of the lash-up the second engine also knows to put on lights at its end. Previously, if I was runnging the two engines separately on the layout they both started off with cabs lit and forward as their default direction, and then by addressing their lash-up (e.g. TR5) the second engine would automatically put itself into reverse and outen its lights. For some reason now, v1.2 lash ups aren't as smart as the used to be.

Guys, On the railroad we have control points [CP's] with minor operating glitches that are not a safety issue. As a Manager of Signals I left these minor ticks in the program after spending a week service testing the interlocking because every time they opened the code to fix the bug found in testing something else got affected! Many of you might say I am being foolish but I still run DCS 3.01 and original Legacy ver 1 cause it works.

Bob,
My lash-up is Cab1 with Cab1 engines - - ENG40 a Cab1 diesel, and ENG80 a Cab1 diesel - - both converted to TMCC with Digital Dynamics Motor Mites. Their lash-up is TR5 a Cab1 lash-up with ENG80, the second engine, reversed. This is the same pair of engines in a lash-up that previously (then too as diesel, Cab1, no-sounds) behaved differently - - better. I'm glad to hear that for you Cab1 designation helped, but not for me.

Bob,
Just so I get this right - - with 2 otherwise Legacy capable engines programmed instead as Cab1 engines in a Cab1 lash-up with the second engine reversed - - you have no lingering Cab2 red LED problems, and the engine which is reversed in the lash-up defaults to forward when you run it separately - - correct? Thanks.

Maybe if I run my Cab1 engines and lash-up as Legacy.....nah. Not likely, but crazier things have been known to happen. Wish someone could explain what's going on here. Thanks for your posts.

Nothing like being a software beta tester.

Gerry

quote:

Originally posted by Sgaugian:
I noticed some things about lash-ups with v1.2 that are different than before. When I designate an engine as the second engine in a lash-up and reverse it, that engine's default direction (when addressed later as an engine) also gets set to reverse.

Sgaugian, the direction behavior you describe with the locomotive is controlled by the loco electronics, not the cab-2 (or cab-1) lash-up programming. While something may be happening here with regard to lash-ups on the cab-2, and I will keep investigating, please note the locomotive when reversed in a train build will always operate reversed as an engine. This has always been the case since TMCC was introduced.

The reason is that you can switch between train operation and a specific loco in a train (say a helper moving up to push on a grade), and not have a direction change. So you could cruise a loco up behind a train, couple, and switch to train operation and be in sync direction and speed wise.

The programming to flip the direction survives loco power cycles, and can only be reset by a train clear operation on the reversed loco.

Hope this helps.

All I can tell you this isn't the way a reversed engine in lash-ups used to work - - Cab1 or TMCC configured, I don't have, we (S-gaugers) don't have, any Legacy engines (yet). Previously when reversed in a lash-up, an engine would still have FWD as its default direction when addressed as a separate engine - - assuming that engine's original electronics, wiring, and programming are for it to run that way - - which mine all are. Then when it's train/lash-up got addressed, it would switch directions and outen it's light. Now unless I have it already in reverse and address its train/lash-up it stays in forward and keeps its cab light on. Only plays ball if already in reverse. I'm getting used to the new pattern, just I don't find it as smart or versatile/flexible as before.

Folks,

Thanks, let's keep this going until we sort out the concern. Let's try a few specific sequences to sync up. I have Legacy v1.2 and TMCC controllers; I switch by powering off the respective base.

I placed a single Legacy engine on the track. and using Legacy, I programmed this as TR 4, reversed. Throttled up, the loco started in reverse. I power cycled the loco, and turned the throttle - reverse run. Switched to engine, before and after power cycle - reverse run. Aux1 + 0, throttle up - reverse run.

The same behavior with the cab-1; reverse run was normal until I cleared the train setting.

--------

If the loco is not Legacy, then we need to know more, as the firmware changed on the R2LC over the years and perhaps something was overlooked on these locos. Sgaugian, can you give me a heads up on the loco you are using?

Jon, the engines are Lionel American Flyer SP Geeps - - a GP20 and a GP9. I converted them to TMCC awhile ago using Digital Dynamics Motor Mites. I've always programmed them the same whether before under TMCC or more recently with Legacy - - the GP20=ENG 40, the GP9=ENG80, and TR5=ENG40 as the lead, with ENG80 the second engine with its direction reversed (sometimes I run a dummy between them facing the same direction as the lead engine, but most often just as a the pair ENG40-ENG80). Previously even after programming ENG80 in as part of TR5 with its direction reversed it would maintain its default direction as FWD when run separately as an engine, now its default becomes reverse. Previously regardless of what direction ENG80 was headed in, when I pressed TR5 it would outen its lights and run backwards behind ENG40. Now if ENG80 is running in forward and I press TR5 nothing changes - - ENG 80's cab light stays on and it runs in fwd along with ENG40 in forward (pulling the lash-up apart, or trying to). If prior to pressing TR5 I put ENG80 into reverse, then it outens its lights and runs in reverse behind ENG40.

This is interesting to me and maybe I didn't notice it before, but is the following "normal?"

I have 4 Legacy diesels on my two loops of track.

I created a train by lashing up 2 of them. I assigned TR 5, and when I pressed the "set" button to save, ALL 4 engines started up simultaneously and blasted their horns.

The lashup works correctly: just the two engines I assigned. I just wasn't expecting all 4 currently on the track to start up.

Has anyone else noticed this? Not a big deal, just curious.

thanks
Don

Folks,

We have tried in vain to replicate this concern. I duplicated the engines and train numbers presented by Sgaugin. I did this with R2LC-c08 code; what is what the aftermarket folks are authorized to sell.

I have personally reviewed the command streams when building a train, and when running an ENG or TR on the Cab-2 in versions 1.0 and 1.2. The cab-2 commands sent out in each revision are identical.

Additionally, my earlier post on the direction setting and operation in TR and ENG is accurate. I am at a loss as to what is happening in the various scenarios described in this thread - however will monitor this thread in case more information presents itself and subsequently changes our understanding of the problem folks are experiencing.

Sorry, best I can contribute for now.