Profile working in simulation but not in real operations

[Vittorio]

Hello everyone,
I'm experimenting a different behaviour among simulation and real operations.
My installation includes WDP 2015 PE and ESU Ecos II.

The goal is to activate (or deactivate) a function when the loco is coming out from hidden track, i.e. activate Headlights and deactivate the Mute function.

I created a LokID 0 Profile based on Busy condition.
It works fine in simulation, not in real operations.
In simulation functions are correctly switched as soon as the loco reaches the given FB.
In real operations functions are switched only if the loco stops on the given FB, not until moving (so, not if the loco travels on the given FB without stopping).

If I only change the condition form Busy to Free (referred to the preceding FB), functions are activated as soon as the last conductive axle lives the FB. In this manner I would exclude errors in function choosing.

I tried with Fleischmann sound original decoder and ESU LokPilot V4 decoder (only basic functions like headlight or shunting mode).

I didn't find similar issue in this english forum, so I have a doubt: I'm wrong in something obvious...  ?

In attachment you can find screenshots of profile definition, profile test in real operation and simulation.

Thanks
Vittorio

[Markus Herzog]

Hi Vittorio,

this functionality is expected when I take a look at the programming.

Many users claimed, that they want to (de)activate the special functions at the destination contact not before the train has stopped (e.g. turn the steam off not before the train has stopped).
Thus all special function profile events etc. at the destination contact will be delayed until the train has stopped.

This was a design decission.

For your case I would suggest to the move the switching of the special function to a second start contact row delayed by the cm difference between start and destination.

Regards
Markus

[Vittorio]

Hi Markus,
thank you for your clarification.

I'm not sure about the hint: what do you mean by "move the switching of the special function to a second start contact row"?
What kind of row must I add? do I have to add a row on contact 66, condition Busy, with delay in cm?

Thanks
Vittorio

[Markus Herzog]

Hi Vittorio,

What kind of row must I add? do I have to add a row on contact 66, condition Busy, with delay in cm?

Yes

Regards
Markus

[Vittorio]

YES Markus, great hint.
I was trying just now what I correctly undersood and it works.

This solution rises however another issue
I set a delay in cm, but the delay starts from the beginning of the contact if the loco keeps moving, starts from the point of a new start if the loco stops on the contact (i.e. because the following route is busy).
In other words: the delay starts form the beginning of the contact and is reset if the loco stops.
So I have no certainty about the point of functions activations.

It' better than basing the profile on the previous contact Free (the point of activation will depend on the last conductive axle), and I can mediate between start of contact and point of loco stop, but anyway has the drawback said above.

Do you have additional hints  ?

Thanks again
Vittorio

[Markus Herzog]

Hi Vittorio,

no additional hints/idea at the moment.

Regards
Markus

[Vittorio]

Hi Markus,
let me came back on your answer.
I can't understand

Many users claimed, that they want to (de)activate the special functions at the destination contact not before the train has stopped (e.g. turn the steam off not before the train has stopped).
Thus all special function profile events etc. at the destination contact will be delayed until the train has stopped.

People already have a better and elegant method to achieve the goal you exemplify: add a row in profile after the Stop. In this manner they can de(activate) functions not only at the stop, but also with a delay and, in case of on/off function, possibly set the duration too.
I use this method to activate compressor seconds after the Stop, and deactivate it after a while. It works fine.

So the design introduced a different behavior between contact before stop and stop contact, taking out the possibility to (de)activate functions on last contact and introducing the issue I said, if using your hint.

And, above all (the topic object), the simulation is not predictive of reality: in simulation the profile with function activation works without stopping.
So a user is bound to try real operations, with the test setup complication.

I hope a future release will correct this diversity, and I suppose the best way would be real operation to act as simulation (since users have the method said above to activate function at stop, whereas there is no method to activate function before stop in a precise manner).

Kind regards
Vittorio

[Markus Herzog]

Hi Vittorio,

I hope a future release will correct this diversity, and I suppose the best way would be real operation to act as simulation (since users have the method said above to activate function at stop, whereas there is no method to activate function before stop in a precise manner).

At the moment there is no plan to change this. But when we change something the normal is adapting the simulation to the reality and not vice versa.

Regards
Markus

[Vittorio]

Hi Markus,
having the simulation correctly predicting real operation was my main claim, since this saves a lot of time and allows to try several different solutions giving confidence on what will happen.

I withdraw the "hope" of function activation without stopping on last contact of route, since I realized this will not a definitive solution if the loco stops before that point (see my other post about function activation point).

Thank you, kind regards
Vittorio