¿ªÔÆÌåÓý

Losing occupancy when trying to record a warrant #warrants


 

When I try to record a warrant I get a message saying that the occupancy is lost when I cross into the next block and the recording stops.
I have a Digitrax? system with BXP88s detecting occupancy.
I believe the BXP88s are working correctly because when I observe the control panel the occupancy changes as it should between blocks.
I have the global debounce set at 4000 ms to inactive to try to conquer this problem but still no luck.
NX warrants work perfectly. Any ideas would be appreciated. Thank you, Bob


 

On Wed, May 14, 2025 at 09:28 PM, <dnbroraback@...> wrote:
NX warrants work perfectly. Any ideas would be appreciated.
So when you run this through the problem block it works fine?
--
H.O. Australia (Layout in Progress)
Digikeijs DR5000 LocoNet
JMRI v5.10 DecoderPro/Warrants/CPE/SML/LogixNG
Java: OpenLogic jre-17.0.12.7 ? Windows 10


 

All of the blocks work perfectly with an NX warrant


 

Bob, I'm not a techo but in the absence of anyone else I'll have a go...
?
So it shows as occupied on the JMRI Control Panel, does that include the train id?
--
H.O. Australia (Layout in Progress)
Digikeijs DR5000 LocoNet
JMRI v5.10 DecoderPro/Warrants/CPE/SML/LogixNG
Java: OpenLogic jre-17.0.12.7 ? Windows 10


 

Bob,
?
Also try recording a warrant that doesn't include this block.
Supposedly an NX Warrant doesn't need a block to have detection as it allows 'Dark' blocks. That would mean if the block had an issue then it mightn't register as a problem.
--
H.O. Australia (Layout in Progress)
Digikeijs DR5000 LocoNet
JMRI v5.10 DecoderPro/Warrants/CPE/SML/LogixNG
Java: OpenLogic jre-17.0.12.7 ? Windows 10