开云体育

Re: Block occupancy without resistive wheelsets


 

It can be done in Java. I? fact, I am doing something in Java on topmof JMRI that has train lengths (standard jmri doesn't have it for running trains, only for the relatively stand-alone "operations").

Using the information for positioning is not at all straightforward, though, because the positioning "brains" must at all times be aware of speed changes, too.

A further complication is, that this would be relatively easy for standard trains, but when adding and removing wagons the overhead of people having to add those changes to the "train" (a concept not present in java!) is considerable unless it can be automated with strategically placed RFID units. So a layout that uses unchanging passenger trains would be better served than one with lots of shunting of goods trains.

In short: it sounds much easier than it is.

Wouter


On Wed, 19 Mar 2025, 00:28 p.lavers via , <p.lavers=[email protected]> wrote:
To ensure the whole train is considered when assessing block occupancy by current sensors and not just the current drawing locomotive the standard solution is resistive wheelsets. However JMRI knows (with speed profiling) the speed of a train and can also record its length. Along with block length these values would allow a calculation of the block occupied by the end of the train. Would it therefore not be possible to show a block as occupied until the end of the train had left it? I can't find any information on this functionality within JMRI. Is this something that could be implemented on top of JMRI in (say) python or java? Anyone explored this? Any ideas?

Join [email protected] to automatically receive all group messages.