Hello
When making sections be consistent in all things. Keep the fwd & rev direction consistent. If you have 3 blocks a,b,c and 3 sections 1,2,3 then section 1 has block a, with entry from block b rev. Section 2 has block b, with entry from block a fwd and block c rev. Section 3 has block c with entry from block b fwd. When making the transit the directions will be consistent. You can reuse the same sections for both ways, one transit will be all fwd, the other all rev.
It understands true reversing sections. Half the transit will be fwd, the other half rev.
Give each section a unique fwd and unique rev sensor.
When adding SSL signals, have it gen the logic, it normally works everything out ok.
The command station fwd, rev has nothing to do with sections and transits fwd and rev. The Auto engineer dispatcher is logically separate from the physical technology being used.
Steve G.
toggle quoted message
Show quoted text
On January 14, 2019 5:09:40 PM EST, Nathan Tableman <nathan@...> wrote:
Ok so I have followed a couple how-tos to get the automation working right and I cannot for the life of me make it work and it is really frustrating me.
This is my test system for the tech I want to put into my larger system before I start building it. I deeply desire this kind of automation because I need JMRI to do some of the smarts…my ML model can only do so much.
I dont know if images come through on this list, but here I go….
I am just missing something…because when I try to dispatch the train it gives me errors about the transit or the train doesn’t move, or it then just runs and doesn’t stop.
Here is my setup:
- Simple big oval with a passing siding.
- geoLine track
- ECoS w/ block detection (this is where I found the bug in the ECoS code, so hard to fix that first, have it working, but it is less than ideal)
- I have 4 blocks
- Transit (through section)
- Siding (opposite to the through section)
- The big oval is in two blocks, just to know generally where it is
- Blocks are also signaled with my IR MQTT and ML model (the idea is to make sure I have multiple systems to help me manage the system)
- Layout panel with my oval
- sensors and reporters all working
- Signals set at turnouts and block boundaries
- I made three sections
- I tried to make transit, but the direction (forward vs reverse) dont make sense to me, but I managed to get them to save without errors.
- I set SSL and F/R sensors in logic (because the ECoS has direction, but it doesn’t seem to be used by JMRI)
- Transit…this is where I get lost. Ideally I want to make one where the train starts on the siding, then does loops across the transit and then I bring it back to the siding.
- Ultimately I want to have 2 trains
- One sits on the siding while the other passes in the transit
- As the trans moves from transit to main, the siding train moves out
- And I can alternate them to mimic arrivals and departures at a station
- There are other issues I have that I’d like to fix in JMRI, but those can wait
- Sending out train info on a block via MQTT (being faked in node red, seems if I get the ECoS Railcom working right I can add two reporters one with the ID and one with the name...)
- Binging sensors together (being done in node red like iTrain does)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
