¿ªÔÆÌåÓý

  1. Jmriusers
  2. Messages
Expanded Topics Messages Polls
Date
Locked Re: My Back and Forth layout won't reverse the loco and each end #dispatcher

 

On Thu, Apr 9, 2020 at 12:34 PM, Robert Schworm wrote:


For extra support with this automation, check the Jython folder in jmri.

There are some Python scripts that are called back and forth. Py. There are
two other versions, movement based on time delay movement based on sensors and
movement with a station in the middle of the Run. I think they are pretty much
set to go as they are. Check the sensor assignments in the script and be sure
they are in your sensor table. I think you can simulate the Run by opening the
sensor table to the sensors and changing their states manually and watching
the script run.

Bob s
Bob,

Since he is using dispatcher, I think that is a step backwards.

--
Peter Ulvestad

JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -

Locked Re: My Back and Forth layout won't reverse the loco and each end #dispatcher

Robert Schworm
 

For extra support with this automation, check the Jython folder in jmri.

There are some Python scripts that are called back and forth. Py. There are two other versions, movement based on time delay movement based on sensors and movement with a station in the middle of the Run. I think they are pretty much set to go as they are. Check the sensor assignments in the script and be sure they are in your sensor table. I think you can simulate the Run by opening the sensor table to the sensors and changing their states manually and watching the script run.

Bob s
Locked Re: My Back and Forth layout won't reverse the loco and each end #dispatcher

 

Steve

Thank you soooo much for such a quick response and for providing the answers.? It now works a treat, some different speeds in each section and some other fine tuning required.

Regads
Simon
Locked Re: Detection zones

 

¿ªÔÆÌåÓý

Dave sand...thanks for the reply, I am clad that you thinki am the right track..lol, what you can't see is that for the most part, most of the main lines(green, yellow, red) are at different elevations, the only place they are at the same elevation is were you see all the transfer points in the lower left, therefore there are two reversing lines(blue), they are only one way, because they use ramps to get connected,? makes for a very interesting routing to get from place to place in a particular? orientation. The user names in the tables I thought were for user documentation and not needed or used by jmri, not sure, since you mentioned it, I take it from what you said that to use virtual signals and SSL logic is ok, until one was to go whole hog and install physical signals sec108 digitrax boards. The switches that are shown but not hooked to another line(industries) are going to be set for jmri to ignore. I think that? by your comments that the amount of detection zones are adequate.
The reading did sort of indicated? that the turnouts should be included in the block adjacent to the throat for detection, but if I really should detect each turn out separately let me know and can throat to throat be done as one.? ?On personal note were are you located, I am in bridgewater nova Scotia

Cheers dave



Sent from Samsung tablet


-------- Original message --------
From: Dave Sand <ds@...>
Date: 2020-04-09 1:59 PM (GMT-04:00)
Subject: Re: [jmriusers] Detection zones

Dave,

That is a very interesting layout. ?It looks like 3 big circles with interconnections between the circles and a reverse loop on one.

The first recommendation is that you use "user names" for turnouts, sensors, etc. ?The prototype had names for everything. ?For example, the top siding on the green loop could be called "Alpha". ?The turnout on the left would then be T-Alpha-Left or T-Alpha-West. ?A linear layout would have a left-right direction such as East-West or North-South. ?Since you are dealing with circles, relative position might be better.

To continue the name concept, the main line block name would be B-Alpha-Main and the detection sensor would be S-Alpha-Main. ?I tend to prefix names with a one letter type or function identifier.

User names provide flexibility. ?For example, when you start the hardware phase, a turnout may end up with a different system name. ?The user name can be moved to the new system name and everything still works.

Signaling: ?Heads/SSL vs. Masts/SML

Signal heads with SSL (Simple Signal Logic) were the original signal concept support by JMRI. ?Signal masts with SML (Signal Mast Logic) came a bit later. ?I prefer signal mast/SML. ?It makes sense to me.

Signal heads are placed on anchor points, turnouts, level crossings, etc. ?The SSL defines block sensors, one turnout, and destination heads. ?The "one turnout" characteristic can require special handling. ?Since signal heads are placed on the turnout itself, including the turnout in same block as the throat end track segment is not an issue. ?Dispatcher requires that direction sensors be included in the SSL when running automatic trains. ?It will insert them if they are not there. ?Sometimes it inserts the wrong direction sensor.?

Signal masts are placed at block boundaries. ?When the SML is generated, it lists the blocks to the next signal mast(s) and the turnout positions. ?Complex turnout arrangements are not a problem. ?Since the masts are placed at block boundaries, if you want a signal mast at the throat end of the turnout, a block boundary is required which means the turnout has its own block. ?Dispatcher does not require direction sensors for automatic trains when using signal masts. ?They can be used if desired. ?They can be used to force opposing signals to display Stop when a transit section is allocated.

In either case, ignore Sections, Transits and Dispatcher until the layout design is working which includes all of the signals responding properly when blocks are occupied and turnout positions are changed.

Note: ?Signals are required for Dispatcher auto trains. ?They do not have to be real.


Dave Sand



----- Original message -----
From: mitchd <Mitchd@...>
Subject: Re: [jmriusers] Detection zones
Date: Thursday, April 09, 2020 6:26 AM

To Dave Sand.....this for your reply, I up loaded the file to that area a few days ago, of my jmri layout.
It would be great to hear what you have to say, I have all the blocks and sensers, have not created any sections yet, started to put some signal lights on, but stopped, did not run any logics, as I have not done the sections and transits,? also not sure if the signals should be listed as virtual? for now while i try to figure out if i am on the right path. I know there are many ways to do things, depending on goal, but it would be nice in ageneral way to find place in jmri that lists the general order of steps with rules of thumb so that one gets a general understanding of the process.

Cheers David Mitchell in self isolation with this to keep me occupied...have a great day



Sent from Samsung tablet


-------- Original message --------
From: Dave Sand <ds@...>
Date: 2020-04-09 3:05 AM (GMT-04:00)
Subject: Re: [jmriusers] Detection zones

Dave,

You are close.

Dispatcher uses Transits. ?It can function as a dispatching tool and it can run trains automatically.

A Transit consists of 2 or more Sections. ? A Section consists of 1 or more Blocks.

Blocks are assigned to track components (turnouts, track segments, etc) on a Layout Editor drawing of the track plan. ?Block boundaries occur when the block assignment changes. The block boundary is represented internally by a Path. ?

I recommend that you create the Layout Editor track plan and the block assignments. ?When ready, upload it to the group's ProblemsBeingWorkedOn folder and we can review it and provide feedback. ?Changes are a lot easier before construction.

Dave Sand



----- Original message -----
From: mitchd <Mitchd@...>
Subject: Re: [jmriusers] Detection zones
Date: Thursday, April 09, 2020 12:29 AM

Thanks for the reply
From what I have read, from jmri, is that paths are created using sections, and sections are created from? block(s). Where a section can have one or more blocks, yes and this allows direction to be resolved, also only one train unit can be in a section, and it is the section that needs to be large enough to hold the train length, ie if a section has 2 or three blocks, then the blocks are used to control the train so that it can slow and or stop in time if the next section or sections are not cleared for travel because of on coming traffic,? or following a train that is to close. That is the understanding that I have, from all the reading I have done, and it seems I need to get this pinned down as I am getting ready to lay track and wiring. P.s. I am new to this and js my first system, so would like to get it clear,? or at least err on the safe side.

Cheers Dave mitchell



Sent from Samsung tablet


-------- Original message --------
From: Don <donmcgil@...>
Date: 2020-04-08 10:30 PM (GMT-04:00)
Subject: Re: [jmriusers] Detection zones

My experience for running with autotrains is to use at least 2 blocks between turnouts in a crossing loop.

I try to have multiple trains running at once on my exhibition layout.? So I often have trains entering a crossing point from both directions.? With only a single detection section between turnouts JMRI would often report issues with determining train directions.? It would generally resolve this but JMRI would eventually freeze with memory management issues.

Having 2 detection blocks in each crossing loop vastly reduced the occurrence of the delay to determine direction and the memory issues.

As Roger points out a train needs to fit into a detection section to stop.
I found I could simulate this with some Logix.? When a train cleared the entry switch block and had entered the second block I clear the first block.? Autotrains will then think the train is totally within the second block and stop the train.? Warning, this does leave the rear end of the train unprotected.? One could re-enable the block via a delayed action once the train is stopped and may need to reset direction sensors also.

Don (socially distanced in Melb, Australia)
Locked Re: Detection zones

 

Dave,

That is a very interesting layout. ?It looks like 3 big circles with interconnections between the circles and a reverse loop on one.

The first recommendation is that you use "user names" for turnouts, sensors, etc. ?The prototype had names for everything. ?For example, the top siding on the green loop could be called "Alpha". ?The turnout on the left would then be T-Alpha-Left or T-Alpha-West. ?A linear layout would have a left-right direction such as East-West or North-South. ?Since you are dealing with circles, relative position might be better.

To continue the name concept, the main line block name would be B-Alpha-Main and the detection sensor would be S-Alpha-Main. ?I tend to prefix names with a one letter type or function identifier.

User names provide flexibility. ?For example, when you start the hardware phase, a turnout may end up with a different system name. ?The user name can be moved to the new system name and everything still works.

Signaling: ?Heads/SSL vs. Masts/SML

Signal heads with SSL (Simple Signal Logic) were the original signal concept support by JMRI. ?Signal masts with SML (Signal Mast Logic) came a bit later. ?I prefer signal mast/SML. ?It makes sense to me.

Signal heads are placed on anchor points, turnouts, level crossings, etc. ?The SSL defines block sensors, one turnout, and destination heads. ?The "one turnout" characteristic can require special handling. ?Since signal heads are placed on the turnout itself, including the turnout in same block as the throat end track segment is not an issue. ?Dispatcher requires that direction sensors be included in the SSL when running automatic trains. ?It will insert them if they are not there. ?Sometimes it inserts the wrong direction sensor.?

Signal masts are placed at block boundaries. ?When the SML is generated, it lists the blocks to the next signal mast(s) and the turnout positions. ?Complex turnout arrangements are not a problem. ?Since the masts are placed at block boundaries, if you want a signal mast at the throat end of the turnout, a block boundary is required which means the turnout has its own block. ?Dispatcher does not require direction sensors for automatic trains when using signal masts. ?They can be used if desired. ?They can be used to force opposing signals to display Stop when a transit section is allocated.

In either case, ignore Sections, Transits and Dispatcher until the layout design is working which includes all of the signals responding properly when blocks are occupied and turnout positions are changed.

Note: ?Signals are required for Dispatcher auto trains. ?They do not have to be real.


Dave Sand



----- Original message -----
From: mitchd <Mitchd@...>
Subject: Re: [jmriusers] Detection zones
Date: Thursday, April 09, 2020 6:26 AM

To Dave Sand.....this for your reply, I up loaded the file to that area a few days ago, of my jmri layout.
It would be great to hear what you have to say, I have all the blocks and sensers, have not created any sections yet, started to put some signal lights on, but stopped, did not run any logics, as I have not done the sections and transits,? also not sure if the signals should be listed as virtual? for now while i try to figure out if i am on the right path. I know there are many ways to do things, depending on goal, but it would be nice in ageneral way to find place in jmri that lists the general order of steps with rules of thumb so that one gets a general understanding of the process.

Cheers David Mitchell in self isolation with this to keep me occupied...have a great day



Sent from Samsung tablet


-------- Original message --------
From: Dave Sand <ds@...>
Date: 2020-04-09 3:05 AM (GMT-04:00)
Subject: Re: [jmriusers] Detection zones

Dave,

You are close.

Dispatcher uses Transits. ?It can function as a dispatching tool and it can run trains automatically.

A Transit consists of 2 or more Sections. ? A Section consists of 1 or more Blocks.

Blocks are assigned to track components (turnouts, track segments, etc) on a Layout Editor drawing of the track plan. ?Block boundaries occur when the block assignment changes. The block boundary is represented internally by a Path. ?

I recommend that you create the Layout Editor track plan and the block assignments. ?When ready, upload it to the group's ProblemsBeingWorkedOn folder and we can review it and provide feedback. ?Changes are a lot easier before construction.

Dave Sand



----- Original message -----
From: mitchd <Mitchd@...>
Subject: Re: [jmriusers] Detection zones
Date: Thursday, April 09, 2020 12:29 AM

Thanks for the reply
From what I have read, from jmri, is that paths are created using sections, and sections are created from? block(s). Where a section can have one or more blocks, yes and this allows direction to be resolved, also only one train unit can be in a section, and it is the section that needs to be large enough to hold the train length, ie if a section has 2 or three blocks, then the blocks are used to control the train so that it can slow and or stop in time if the next section or sections are not cleared for travel because of on coming traffic,? or following a train that is to close. That is the understanding that I have, from all the reading I have done, and it seems I need to get this pinned down as I am getting ready to lay track and wiring. P.s. I am new to this and js my first system, so would like to get it clear,? or at least err on the safe side.

Cheers Dave mitchell



Sent from Samsung tablet


-------- Original message --------
From: Don <donmcgil@...>
Date: 2020-04-08 10:30 PM (GMT-04:00)
Subject: Re: [jmriusers] Detection zones

My experience for running with autotrains is to use at least 2 blocks between turnouts in a crossing loop.

I try to have multiple trains running at once on my exhibition layout.? So I often have trains entering a crossing point from both directions.? With only a single detection section between turnouts JMRI would often report issues with determining train directions.? It would generally resolve this but JMRI would eventually freeze with memory management issues.

Having 2 detection blocks in each crossing loop vastly reduced the occurrence of the delay to determine direction and the memory issues.

As Roger points out a train needs to fit into a detection section to stop.
I found I could simulate this with some Logix.? When a train cleared the entry switch block and had entered the second block I clear the first block.? Autotrains will then think the train is totally within the second block and stop the train.? Warning, this does leave the rear end of the train unprotected.? One could re-enable the block via a delayed action once the train is stopped and may need to reset direction sensors also.

Don (socially distanced in Melb, Australia)
Locked "Replacing" a program function #scripting

 

Hi,
there is a jython script how to replace the MQTT parser (SetMqttParser.py) and also to set a general MQTT topic for MQTT turnouts (SetMqttPrefix.py).
How do I do if I want to change a function?
I want to change what is subscribed to the MQTT broker.

This is the original function in MqttTurnout.java.

? ? MqttTurnout(MqttAdapter ma, String systemName, String topic) {
? ? ? ? super(systemName);
? ? ? ? this.topic = topic;
? ? ? ? mqttAdapter = ma;
? ? ? ? mqttAdapter.subscribe(this.topic, this);
? ? }

I also want to subscribe to other topics and handle them in SetMqttParser.py.

ex.
I want to know if a signal ahead is showing stop or go or changing in between stop/go to set my own exit signal to correct aspect.
The signal ahead is not part of the station (JMRI) having the exit signal.
The signal ahead is a block signal publishing it's own signal states thru MQTT and listning on next signal ahead of it.

I also want to replace this function so I can use the 'username' instead of 'systemname' if set.

? ? public Turnout createNewTurnout(@Nonnull String systemName, String userName) {
? ? ? ? MqttTurnout t;
? ? ? ? String suffix = systemName.substring(systemPrefix.length() + 1);
? ? ? ? String topic = topicPrefix+suffix;
?
? ? ? ? t = new MqttTurnout(mqttAdapter, systemName, topic);
? ? ? ? t.setUserName(userName);
?
? ? ? ? if (parser != null) t.setParser(parser);
?
? ? ? ? return t;
? ? }

Is that possible to do with jython scrip?

/BR
Benny
Locked Re: Controlling Servos directly connected to Arduino with DCC++ Base Station #arduino #dccpp

 

Hi Thomas,

How will your idea react at obstructions?
Is the mechanism for mesure the current always active?
If there get's some dirt, a piece of ballast for example, in between the rail and point-rail?

--
with regards,
Willie
Locked Re: Consisting questions #nce

 

I was doing a speed matching clinic at a train show, and one of the guests has a story:
"I ran an ABBA set of F7s for years with no issues.
Then one day one of the B units derailed. Looking at the wheels, they were flat.?
The other three Loks were dragging that unit around for some time, until the wheels came off."
Consisting Loks that are not speed matched can lead to derailments, motor failures, etc. Any track imperfections will be magnified by these bad consists.
If your fleet is generally matched, regardless of decoder type, you can freely mix and match. But, remember that sound decoders may not play nice together without special setup. (You can disable waiting for sounds to complete before moving, but that looks odd when the Lok starts moving, then the sound changes)
I generally set my consists up in JMRI, then always run those sets together. I.E., CNW GP15 for Operations, RS-1/2/3 for road trains, GMD-1 for grain trains, etc.

Thomas
DeSoto, TX
Locked Re: Confusion resulting from trains in adjacent blocks #automation

 

Interesting reads!? How they did it in real life was impressive, trying to model that via programing would be an enjoyable and daunting task for someone who loves to code.

I've been trying to figure out this signaling/dispatching/automation for parts of my layout. The others who work on the layout see some of the things I do on JMRI and run out the room.? They do like that they can use their phone to control a train and walk around. They wouldn't be interested in even hearing about what will be going on inside JMRI.to make the trains move and stop. I guess I do the same thing regarding scenery.? "Does it make the trains go?" I ask. "No, not for me!" But this conversation on how real trains did it and modeling is educational!

Thanks all for the responses!?

On Wed, Apr 8, 2020 at 8:04 AM matt peeler via <mtler1930=[email protected]> wrote:
Reading Ken's historical response made me wonder wouldn't a real dispatcher have made a time table calculation that no two trains would hit opposing (on the single track) "at the same time"?? Even miles apart, it would be a given that if both trains got to their control point and "cleared" to enter the single track that inevitably there would be a collision since both trains were allowed on the track with probably the authority to travel at best possible speed.? Wouldn't they have staggered the "arrival time" to be at that point at a different time so this wouldn't happen?

For train modeling, couldn't that be done as well or some concept like that in JMRI??

More of a point to ponder and not something JMRI would have to program but rather a way to avoid this.? If the train doesn't get to its assigned control point at the proper time, it has to wait if early, or assume another train is in the block unless cleared by special communications from a dispatcher??? Might be showing my ignorance on dispatching as well but it would seem that not only automated dispatching as well as time tables would be needed for "real trains" that might not be as readily available for modeling?

On Tue, Apr 7, 2020 at 5:59 PM Ken Cameron <kcameron@...> wrote:
Don W,

Those race conditions are why something other than the signals had to
control who was supposed to move first. Some signal systems got in to
interesting ideas like biasing the two directions or something I recall
called 'double approach' but I don't recall the details well enough to say.
They were part of APB which tried to improve the safety over long single
tracks. APB uses a waterfall from one end to the other of the single track
so the distant signal would show stop to the opposing direction. There are
still races possible as I understand it, but I'm not sure how they handled
it. These were more popular in the US west which had many miles between
passing points and the dispatcher usually had a couple trains going one way
before opposing traffic would try coming the other way.

It all comes back to why the railroads used signals only for safety of not
running into another train. Only in CTC, where they were controlled to not
show the clear, until the dispatcher had decided who was supposed to move
first. Everyone else waited at the control point until the dispatcher
decided otherwise.

Can you automate some of the dispatching, yes but it isn't the simplest way
to do things. But for models, I've found way too many people 'fear being the
dispatcher'. I even did a clinic in 2014 with that as the subtitle.

-Ken Cameron, Member JMRI Dev Team
Locked Re: Change locomotive address #arduino #dccpp

 

Hi, i have arduino mega in down, in the middle the ethernet and on top motorshield. In arduino mega I instaled the last version of the dcc++ base station (1.2.1) with option ethernet. Check that all cables are connected correcly. You have check if the four leds are on when you, in decoderpro, click on buttom to "ON". The motorshield is powered by a 16V and 3.75A laptop charger, the Arduino Mega is powered by a 5V and 1A USB phone charger.
Locked Re: Passenger Operations #operationspro

allenzeesman
 

Thanks Dan. The train services the passenger car but the passenger depot does not. Worked perfectly. And at the end of the route it tucked the baggage and passenger cars nicely into the coach yard! Then it worked perfectly for the return trip. Its a fabulous program and I am enjoying it thoroughly. I am learning it to use in conjunction with Trainz. I really appreciate having access to this gem, All the best,
Allen Zeesman


On Wed, Apr 8, 2020 at 8:57 PM Dan Boudreau <daboudreau@...> wrote:
Allen,

If you don't want a change in the number of passenger cars at a location, just disable that car type for that location. Now the program will not add or drop off a passenger car.

Dan

Locked Re: Detection zones

 

¿ªÔÆÌåÓý

To Dave Sand.....this for your reply, I up loaded the file to that area a few days ago, of my jmri layout.
It would be great to hear what you have to say, I have all the blocks and sensers, have not created any sections yet, started to put some signal lights on, but stopped, did not run any logics, as I have not done the sections and transits,? also not sure if the signals should be listed as virtual? for now while i try to figure out if i am on the right path. I know there are many ways to do things, depending on goal, but it would be nice in ageneral way to find place in jmri that lists the general order of steps with rules of thumb so that one gets a general understanding of the process.

Cheers David Mitchell in self isolation with this to keep me occupied...have a great day



Sent from Samsung tablet


-------- Original message --------
From: Dave Sand <ds@...>
Date: 2020-04-09 3:05 AM (GMT-04:00)
Subject: Re: [jmriusers] Detection zones

Dave,

You are close.

Dispatcher uses Transits. ?It can function as a dispatching tool and it can run trains automatically.

A Transit consists of 2 or more Sections. ? A Section consists of 1 or more Blocks.

Blocks are assigned to track components (turnouts, track segments, etc) on a Layout Editor drawing of the track plan. ?Block boundaries occur when the block assignment changes. The block boundary is represented internally by a Path. ?

I recommend that you create the Layout Editor track plan and the block assignments. ?When ready, upload it to the group's ProblemsBeingWorkedOn folder and we can review it and provide feedback. ?Changes are a lot easier before construction.

Dave Sand



----- Original message -----
From: mitchd <Mitchd@...>
Subject: Re: [jmriusers] Detection zones
Date: Thursday, April 09, 2020 12:29 AM

Thanks for the reply
From what I have read, from jmri, is that paths are created using sections, and sections are created from? block(s). Where a section can have one or more blocks, yes and this allows direction to be resolved, also only one train unit can be in a section, and it is the section that needs to be large enough to hold the train length, ie if a section has 2 or three blocks, then the blocks are used to control the train so that it can slow and or stop in time if the next section or sections are not cleared for travel because of on coming traffic,? or following a train that is to close. That is the understanding that I have, from all the reading I have done, and it seems I need to get this pinned down as I am getting ready to lay track and wiring. P.s. I am new to this and js my first system, so would like to get it clear,? or at least err on the safe side.

Cheers Dave mitchell



Sent from Samsung tablet


-------- Original message --------
From: Don <donmcgil@...>
Date: 2020-04-08 10:30 PM (GMT-04:00)
Subject: Re: [jmriusers] Detection zones

My experience for running with autotrains is to use at least 2 blocks between turnouts in a crossing loop.

I try to have multiple trains running at once on my exhibition layout.? So I often have trains entering a crossing point from both directions.? With only a single detection section between turnouts JMRI would often report issues with determining train directions.? It would generally resolve this but JMRI would eventually freeze with memory management issues.

Having 2 detection blocks in each crossing loop vastly reduced the occurrence of the delay to determine direction and the memory issues.

As Roger points out a train needs to fit into a detection section to stop.
I found I could simulate this with some Logix.? When a train cleared the entry switch block and had entered the second block I clear the first block.? Autotrains will then think the train is totally within the second block and stop the train.? Warning, this does leave the rear end of the train unprotected.? One could re-enable the block via a delayed action once the train is stopped and may need to reset direction sensors also.

Don (socially distanced in Melb, Australia)
Locked Re: Consisting questions #nce

 

Paul,

On 9 Apr 2020, at 12:11 PM, Paul Champlin <paul.champlin@...> wrote:

I have a wide assortment of decoders and an NCE based DCC system and, of course, I use the absolutely fantastic, JMRI.
Please read this:
<>


I have about 30 locomotives on my layout and am finding that I have sorted them in various consists and have used the NCE system to set up and manage the consists. Heretofore, I¡¯ve always left the Consist tab in JMRI untouched. But it dawned on me today as I was setting up a new loco (like I need another one...), that maybe it is easier to set them up, manage the starting and stopping momentum, lights, etc in JMRI.
Setting up CVs 21 & 22 (and 109 & 110 in the latest LokSound 5 firmware) is best done with the Consist tab in JMRI.

For example, I¡¯d like the lead loco light to go on when in forward movement and the rear loco light to come on when in reverse. Or, does the momentum work better for a consist in JMRI vs in NCE?
NCE momentum simple reprograms CVs 3 & 4 on the fly. JMRI isn't linked to this.

Again, this has to be taken in consideration that I have many different brands of decoders and don¡¯t want to organize locos by decoder/loco mftr brand.
Speed matching for consists is best done by JMRI. Please read this:
<>

Dave in Australia
Locked Re: Detection zones

 

Dave,

You are close.

Dispatcher uses Transits. ?It can function as a dispatching tool and it can run trains automatically.

A Transit consists of 2 or more Sections. ? A Section consists of 1 or more Blocks.

Blocks are assigned to track components (turnouts, track segments, etc) on a Layout Editor drawing of the track plan. ?Block boundaries occur when the block assignment changes. The block boundary is represented internally by a Path. ?

I recommend that you create the Layout Editor track plan and the block assignments. ?When ready, upload it to the group's ProblemsBeingWorkedOn folder and we can review it and provide feedback. ?Changes are a lot easier before construction.

Dave Sand



----- Original message -----
From: mitchd <Mitchd@...>
Subject: Re: [jmriusers] Detection zones
Date: Thursday, April 09, 2020 12:29 AM

Thanks for the reply
From what I have read, from jmri, is that paths are created using sections, and sections are created from? block(s). Where a section can have one or more blocks, yes and this allows direction to be resolved, also only one train unit can be in a section, and it is the section that needs to be large enough to hold the train length, ie if a section has 2 or three blocks, then the blocks are used to control the train so that it can slow and or stop in time if the next section or sections are not cleared for travel because of on coming traffic,? or following a train that is to close. That is the understanding that I have, from all the reading I have done, and it seems I need to get this pinned down as I am getting ready to lay track and wiring. P.s. I am new to this and js my first system, so would like to get it clear,? or at least err on the safe side.

Cheers Dave mitchell



Sent from Samsung tablet


-------- Original message --------
From: Don <donmcgil@...>
Date: 2020-04-08 10:30 PM (GMT-04:00)
Subject: Re: [jmriusers] Detection zones

My experience for running with autotrains is to use at least 2 blocks between turnouts in a crossing loop.

I try to have multiple trains running at once on my exhibition layout.? So I often have trains entering a crossing point from both directions.? With only a single detection section between turnouts JMRI would often report issues with determining train directions.? It would generally resolve this but JMRI would eventually freeze with memory management issues.

Having 2 detection blocks in each crossing loop vastly reduced the occurrence of the delay to determine direction and the memory issues.

As Roger points out a train needs to fit into a detection section to stop.
I found I could simulate this with some Logix.? When a train cleared the entry switch block and had entered the second block I clear the first block.? Autotrains will then think the train is totally within the second block and stop the train.? Warning, this does leave the rear end of the train unprotected.? One could re-enable the block via a delayed action once the train is stopped and may need to reset direction sensors also.

Don (socially distanced in Melb, Australia)
Locked Re: Detection zones

 

¿ªÔÆÌåÓý

Thanks for the reply
From what I have read, from jmri, is that paths are created using sections, and sections are created from? block(s). Where a section can have one or more blocks, yes and this allows direction to be resolved, also only one train unit can be in a section, and it is the section that needs to be large enough to hold the train length, ie if a section has 2 or three blocks, then the blocks are used to control the train so that it can slow and or stop in time if the next section or sections are not cleared for travel because of on coming traffic,? or following a train that is to close. That is the understanding that I have, from all the reading I have done, and it seems I need to get this pinned down as I am getting ready to lay track and wiring. P.s. I am new to this and js my first system, so would like to get it clear,? or at least err on the safe side.

Cheers Dave mitchell



Sent from Samsung tablet


-------- Original message --------
From: Don <donmcgil@...>
Date: 2020-04-08 10:30 PM (GMT-04:00)
Subject: Re: [jmriusers] Detection zones

My experience for running with autotrains is to use at least 2 blocks between turnouts in a crossing loop.

I try to have multiple trains running at once on my exhibition layout.? So I often have trains entering a crossing point from both directions.? With only a single detection section between turnouts JMRI would often report issues with determining train directions.? It would generally resolve this but JMRI would eventually freeze with memory management issues.

Having 2 detection blocks in each crossing loop vastly reduced the occurrence of the delay to determine direction and the memory issues.

As Roger points out a train needs to fit into a detection section to stop.
I found I could simulate this with some Logix.? When a train cleared the entry switch block and had entered the second block I clear the first block.? Autotrains will then think the train is totally within the second block and stop the train.? Warning, this does leave the rear end of the train unprotected.? One could re-enable the block via a delayed action once the train is stopped and may need to reset direction sensors also.

Don (socially distanced in Melb, Australia)
Locked Consisting questions #nce

 

I have a wide assortment of decoders and an NCE based DCC system and, of course, I use the absolutely fantastic, JMRI.

I have about 30 locomotives on my layout and am finding that I have sorted them in various consists and have used the NCE system to set up and manage the consists. Heretofore, I¡¯ve always left the Consist tab in JMRI untouched. But it dawned on me today as I was setting up a new loco (like I need another one...), that maybe it is easier to set them up, manage the starting and stopping momentum, lights, etc in JMRI.

For example, I¡¯d like the lead loco light to go on when in forward movement and the rear loco light to come on when in reverse. Or, does the momentum work better for a consist in JMRI vs in NCE? Again, this has to be taken in consideration that I have many different brands of decoders and don¡¯t want to organize locos by decoder/loco mftr brand.

What are some of your thoughts that have been down this path already?
Thanks
Paul
Locked Re: Passenger Operations #operationspro

 

Allen,

If you don't want a change in the number of passenger cars at a location, just disable that car type for that location. Now the program will not add or drop off a passenger car.

Dan
Locked Re: Detection zones

 

My experience for running with autotrains is to use at least 2 blocks between turnouts in a crossing loop.

I try to have multiple trains running at once on my exhibition layout. So I often have trains entering a crossing point from both directions. With only a single detection section between turnouts JMRI would often report issues with determining train directions. It would generally resolve this but JMRI would eventually freeze with memory management issues.

Having 2 detection blocks in each crossing loop vastly reduced the occurrence of the delay to determine direction and the memory issues.

As Roger points out a train needs to fit into a detection section to stop.
I found I could simulate this with some Logix. When a train cleared the entry switch block and had entered the second block I clear the first block. Autotrains will then think the train is totally within the second block and stop the train. Warning, this does leave the rear end of the train unprotected. One could re-enable the block via a delayed action once the train is stopped and may need to reset direction sensors also.

Don (socially distanced in Melb, Australia)
Locked Re: Controlling Servos directly connected to Arduino with DCC++ Base Station #arduino #dccpp

Thomas Chalabi
 

Hi John,

I've implemented a different approach to solve the servo position problem.? ?I started w/ trying to store the Thrown / Closed values for each servo.? I've got about 300 turnouts and 15 Arduino's on my layout, so keeping track of the trimming values in the Arduino code become a nightmare.? Adding additional hardware and memory card was going to be too expensive.? Calibrating each servo is a pain too.

So,? first rule of problem solving -- eliminate the problem.? ?Don't bother saving the values, let the software calculate the correct Thrown / Closed position on-the fly.

As a servo moves, it typically draws about 25mA of current (SG90).? ?When the servo moves too far (and hits the rail), the current draw will spike, as the servo is fighting to get to it's final position.? ?Hence, the optimal position is just before the servo current spikes.? ?If you can find the location where the current spikes and back off 1 or 2 ticks, you are golden.

Solution:??
I'm using a PCA9685 16 channel servo driver in an I2C bus connected to my Arduino Uno.? This is powered by a 5 volt power supply and uses JMRI CMRI signals to activate each of the 16 servos.

I've placed an INA219 current sensing module In between the 5V supply and the PCA9685,? ?This allows me to sense how much current is being consumed by a servo.? ??https://www.amazon.com/gp/product/B01ICN5OAM/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

The INA219 is also an I2C device and the current value can be easily read by the Arduino.

I wrote some code to record the current value as the servo moves.? ?When the current spikes (ie 60mA or greater), then I move the servo back a tick.

It also makes installation a breeze, as there's no need to calibrate each servo.


Thoughts?
Locked Auto Set Turnouts - not! #dispatcher

 

I use JMRI V4.17.5 with Java V1.8.0 on a laptop with Windows 10 and use NCE Power Pro with V2007a.? Layout Editor was used to create a dispatcher panel for the layout track.? There are no block occupancy detectors.? I am working with Dispatcher with its associated concepts of Active Trains, Transits, Sections, and Blocks.

?

The turnouts on the panel have System Names of ITxxx to represent manual turnouts on the layout or have System Names of NTxxx to represent powered turnouts on the layout with NCE Switch-Its.

?

In Dispatcher Options, I have not checked the box ¡°Automatically set turnouts when a Section is allocated¡± and have selected Save Options.? I find that when I run an Active Train, some of the turnouts are set and some of the turnouts are not set.? This occurs for both manual and powered turnouts.? I see no error messages on the System Console.

?

What should I look for or change so that none of the turnouts are set automatically for the allocated route?

?

Thanks for your help.

?

Ted of Iowa City
69881 - 69900 of 240782