开云体育

Steve, I've had problems myself so very interested if you make progress
with this. I'm just wondering how the transit was defined, as I am confused
by this. If you make one that goes around and at the end includes the block
you started from, which is what I imagined was possible on a circular
layout, it seems to allocate all blocks (well, you do want those all free
to run, yes??!,) but your train is now occupying the last block, so of
course you will get no clearance to go as there is traffic there.
That's how I read it anyway, but would love to hear a more enlightened
view!
My feeling is that it was never designed for complete to circuits.... more
back-and-forth.

John

Hi John,

My transits do include all the sections to make a circuit, and the first and last sections are the same. Trains loop around the layout very nicely.
Dispatcher allocates 3 sections ahead. You can see this as the yellow blocks in my youtube video.
So your loop must be more than 4 sections or I would expect the issue you describe. How many sections are in your transit?


SteveT

Hi Hubert/Steve,
I've been following this thread with interest as I'm just about to get in to automation & whilst I don't want to hijack this thread, I do have a couple of questions.I really don't mind if you want to leave the answers until you get the issue sorted to save any confusion, but I thought the questions might help others that are new to or thinking about using automation ..
Q1: What is the difference between using signal heads & signal masts??(I've seen these referred to in several threads so it obviously makes a difference between the types?).
Q2: What direction sensors are you using - or are aware of??(I was under the impression that JMRI would work out the direction of travel itself via two consecutive detectors (IR or other)).
Stu...
Sent from my Samsung Note3

Hi Stu,

Others could explain the _benefits_ of SignalHeads vs. SignalMasts better than I, but inside the Dispatcher code, there are some unavoidable differences in the logic. I use SignalMasts, so I can test/debug issues with those more easily than SignalHeads. The goal should be for these differences to be transparent to the regular user, but we're not there yet.


As for direction sensors, I only use internal sensors. Dispatcher SETS these when allocating a section. If I've included these sensors in my SignalMast logic, this prevents two trains from trying to allocate the same block, as only one will have a clear aspect.
Note: I only include the direction sensors in SM logic for blocks that may be used by opposing trains.


I've no experience with hardware direction sensors.


HTH,
SteveT