开云体育

Train tracking, dealing with gaps #traintracking


 

I created a nice panel for the museum layout and created train tracking markers on it. It works well except for one show stopping thing. At one spot in the loop there is a detection gap between blocks that kills the tracking. The gap is only 1 or 2 seconds.?
?
Is there a workaround for this? Increasing train length is not an option. Installing a new detector is not likely either.
?
George


 

George,

If you can use a test release, JMRI 5.11.2 introduced a concept called a ghost block. ?The allows Dispatcher to simulate a train going through the ghost block.

If you are just looking at train tracking, you can create a virtual block and use Logix or LogixNG to simulate occupancy. ?

Another approach is to pretend the gap does not exist. ?Don't tell JMRI about the gap. ?Of course, that will not work if the gap is a turnout.

Dave Sand


----- Original message -----
From: "George Hofmann via groups.io" <george.hofmann=[email protected]>
Subject: [jmriusers] Train tracking, dealing with gaps #traintracking
Date: Thursday, April 03, 2025 1:06 PM

I created a nice panel for the museum layout and created train tracking markers on it. It works well except for one show stopping thing. At one spot in the loop there is a detection gap between blocks that kills the tracking. The gap is only 1 or 2 seconds.?
?
Is there a workaround for this? Increasing train length is not an option. Installing a new detector is not likely either.
?
George


 

Dave
I think LogixNG would work here. I tried putting a dummy block in between that was constantly occupied but that did not work unsurprisingly.
?
But I'm confused about your third option. I'm already not telling JMRI that a gap exists. As far as it knows the two monitored blocks are abutting even though physically they are not. It's just that block A goes dark before block B lights up.?
?
Thanks for the help.
George
?


 

George,

Maybe you could put a long going "inactive delay" on block A. ?Or both if bi-directional.

Dave Sand



----- Original message -----
From: "George Hofmann via groups.io" <george.hofmann=[email protected]>
Subject: Re: [jmriusers] Train tracking, dealing with gaps #traintracking
Date: Thursday, April 03, 2025 1:54 PM

Dave
I think LogixNG would work here. I tried putting a dummy block in between that was constantly occupied but that did not work unsurprisingly.
?
But I'm confused about your third option. I'm already not telling JMRI that a gap exists. As far as it knows the two monitored blocks are abutting even though physically they are not. It's just that block A goes dark before block B lights up.?
?
Thanks for the help.
George
?


 

Well yeah! Delay to inactive should do the trick. I was not aware of that little tool.
I'll give it a try.
?
Tnx again
George


 

Expanding on Dave Sand's idea, assign a virtual sensor to the block.
The sensor is set occupied by Logix or LogixNG when both blocks on either side are occupied, otherwise unoccupied.
This is the way I have been indicating occupied turnouts, without hardware detection, for years (before the creation of the "ghost" block).
--
Ken
NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959)
Loconet * JMRI 5.11.4 * OSX,Win10,Ubuntu
Blog: ?
Youtube:


 

The 'delay to inactive' technique worked. I'm glad that I was made aware of these 'debouncing delays'. I think they might be useful to clean up some flaky sensor data that we have been dealing with.
?
George