Question about orientation vs direction about libbidib HOT 4 OPEN

Hi @timvanoostrom, good question. You are right, the BiDiB protocol for MSG_CS_DRIVE messages says that it should be direction with forward and reverse as the possible values.

When we were developing an automatic train driving algorithm, the notion of a train being "forward" or "reverse" seemed ambiguous because it depends on the polarity of the track rails and on the orientation of the train. For example, if the train is "forward", would the train drive forwards to the left or to the right? This was the rationale behind using left and right.

However, now that we've had more experience with our model railway (track plan), we can define forward as the anti-clockwise direction and reverse as the clockwise direction without ambiguity. I will probably revert the name change at some point in the future!

from libbidib.

Or to avoid ambiguity (a bit), THAT_WAY or THE_OTHER_WAY. Though humans controlling the trains will probably want to use terms like forward, back, reverse, left, right for comprehension and real-world orientation. I think that some loco decoders can broadcast their own direction as source of truth.

from libbidib.

Forward, backward, and reverse aren't always suitable when a train has gone through a reversing loop. In the image below, the train begins in the forward direction, but exits in the reverse direction which can be confusing because the train is physically going "forward". Note that the track polarity gets swapped as the train drives through the reversing loop:

Left and right aren't always suitable when people do not realise that a collection of tracks are on opposite sides of a loop:

I don't know whether there is a suitable solution to this problem 😄

from libbidib.

Indeed.

from libbidib.