¿ªÔÆÌåÓý

Locked Re: Inconsistent behaviour with the dispatcher


 

Steve,

Thanks for the feedback. I suspected that it was protecting against unknown trains. Not that they would respect signal indications. :)

Dave Sand

On Aug 1, 2018, at 5:07 PM, Steve_G <RailRodder@...> wrote:

Ah Dave
Belt and Braces.
If an unscheduled train is in the section it will still show a stop. Think a young or old manual engineer looking at the mast. "No dad/daughter/over served friend, you havent been scheduled yet." Its not fool proof, but helps moving the blame off the dispatchers shoulders.!!
Steve G.

Steve G.


On August 1, 2018 5:39:27 PM EDT, Dave Sand <ds@...> wrote:
Steve,

I noticed that you included the direction sensor for the section prior
to the mast in SML along with the normal direction sensor for the
section protected by the mast.

I am curious about its function.

Dave Sand



On Aug 1, 2018, at 4:32 PM, Steve_G <RailRodder@...> wrote:

Hi James
Firstly I made all sections consistant in direction, so the transit
would show all Fwd, it makes setting the fwd and rev sensors consistant
and therefore which sensors should be checked easier. I rebuilt the
transits, hence the actions were destroyed, sorry.
Then I manually edited the masts to check for correct directional
sensors.
The icons I added so when running I could check which sensors were
active or inactive as the train proceeded round, and also take my time
by using a non existing loco, emulating its passage by clicking the
occupancy sensors. I think I set the occupancy icon closest to the
track and fwd/rev sensors going clockwise. This is by memory as I am
not near anything bigger tah a smart phone. Hopefully by manual
intervention you meant using the manual throttle in the auto trains
window, if you used a real throttle that could lead to the slot in use
message.
Steve G.




On August 1, 2018 5:00:06 PM EDT, "jamespetts via Groups.Io"
<jamespetts@...> wrote:
Thank you for working on this: that is most kind. Firstly, in
response
to Dave, here is a screenshot of my train settings:

/g/jmriusers/photo/65718/0?p=Name,,,20,1,0,0

As you will see, I did not have the "reset when done" option
selected -
this would obviously cause (and be intended to cause) continuous
running, as the dialogue states. Thank you for clarifying as to the
significance of the block tracking issues.

I am aware that the best signal will be caution in a two train setup
on
this layout; but this is not a problem in itself. The problem is the
inconsistent behaviour as described.

Steve - thank you for uploading a modified panel. May I ask: other
than
adding the sensor icons (may I ask what the function of these is in
this context?), what other changes are there?

Testing this, I am afraid that the inconsistency is no better
(albeit
it is now different).

Initially, when I tried to run two trains ("Haymarket" from the
front
and "The London STANDARD" from the rear), the latter refused to
accelerate for some reason, so I terminated both trains, manually
drove
"Haymarket" back to its starting location and opened a manual
throttle
for "The London STANDARD" to which the train responded correctly.

I then tried to create the automatically driven Active Trains again,
and this time, it worked correctly as it had done the last time that
I
tried two trains on this layout (as described in the original post),
save that the action to turn the lights on at the beginning of the
run
did not seem to work and the lights remained off.

I ran this a second time using the "restart" option in the Auto
Active
Trains dialogue, and the behaviour was identical to the first time.

I then removed "Haymarket" and tried to run "THe London STANDARD"
again. This time, the train moved forward into the right curve and
stopped. The signal for entering the lower straight was at danger
for
some reason. The only thing that would clear this was touching
"Haymarket"'s wheels on the track on that section so that the sensor
registered it as occupied then removing it again. Once it did that,
the
train then ran at a moderate speed, but kept going and never stopped
until I terminated it manually. Testing this again (using "restart"
with the Auto Active Trains dialogue), exactly the same behaviour
was
repeated.

Again, this does not seem consistent with what the documentation
describes should happen in this situation. Have I misunderstood the
documentation in some way, or should I be filing a bug report?

Thank you again for all your help - it is much appreciated.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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