I have two issues going on that are really slowing down progress on my layout. First, I was wondering what's possible with computer automation using one of the free computer programs such as JMRI. Ideally, I'd like to set up my layout so if two trains are approaching the same block, the trains will halt before they collide. Another thing I'd like to setup is that if a train is approaching a turnout that is thrown when it needs to be closed, or closed when it needs to be opened, it will be automatically adjusted before a short-circuit occurs. I'm basically looking at wanting to setup a safety net, so while I would have full control of the trains, the computer will kick in and stop accidents and shorts from happening if I lose track of things. Is this kind of thing possible? Regarding blocks, I'm wondering how many or how few blocks I should be using to split up my layout with. It's complicated, so I drew up something to help explain what I'm asking: Do I want to isolate each turnout on all 3 ends, or would it be perfectly fine to only isolate the track leading to both the diverging and straight track? (looking at the first and second examples is the drawing). For several of the turnouts, the stretches of track leading into each turnout is very long, and may loop back on itself (specifically on the mainline). My second question here revolves around the collision avoidance I'd like to do, as mentioned above. If I can even do the collision avoidance setup, would I need small blocks after each turnout to detect trains in the immediate vicinity of turnouts, or is that overkill? (the third example from the drawing). The idea of having smaller blocks right before each turnout came up because if I have a train on a siding approaching a mainline turnout that already has a train on it, I'd want the train in question to fill the siding as much as possible before coming to a stop. If I only have 1 block on the entire siding, the train may stop several feet from the turnout. However, I don't know if using additional blocks makes it needlessly confusing, but it does for sure make it a lot more expensive, so I'm trying to consolidate blocks where possible. I've tried searching for information on these concepts off and on for months (including the JMRI wiki), but I haven't found anything useful that applies to what I'm going for, so if anyone personally knows this stuff or has any guides that covers exactly this kind of material, I'd greatly appreciate it. Also, I'm running Digitrax equipment (over Loconet, of course).
Don: I am currently using JMRI with Digitrax BDL168's for occupancy detection and DS64's for switch control. Using JMRI I am able to duplicate my track plan in PanelPro and display it on an over head LCD monitor. The panel displays occupied blocks and the status of all switches. In your examples for blocking I use the second option on the mainline(s). Most blocks on my layout are the length of my longest trains. I find this to be a great rule of thumb. You mentioned that you have some very long blocks. It may be necessary to break these up into two or more blocks for more realistic operations. I use the third option for hidden staging. With the aid of an over head LCD monitor and a PanelPro drawing of my track plan I am able to follow the status / progress of trains as they enter hidden staging. The short blocks let me know when the train has cleared the switch and when it arrives at the other end. This option works fantastic! Now for the more complicated aspect of your questions involving automation. JMRI provides you with the ability to write Scripts in order to obtain custom automation effects. You can also obtain the source code and write your own programing sub routines if you are so inclined. With this in mind anything is possible depending on how much expertise you have and how much time you are willing to spend. On a less automated level I also enjoy setting up Routes. Routes can be manually triggered by throwing a predefined switch on the throttle or automatically triggered for example by the occupancy of a specified block. By triggering predefined Routes for your trains you will be well on your way to collision avoidance and prevention of shorting out switches. Jerry
I've finally had some spare time to work on my layout this weekend, so I played around with JMRI, and success was non-existent. There's just so many different things to do with JMRI and so many places to start, I can't figure out the best place for me to start working on the basic automation.. I have already recreated my layout as a panel and associated each block to an appropriate BDL168 sensor, and associated 8 of the turnouts to the 2 DS64's that I have so far, however beyond that I'm stuck. Does anyone know of a detailed tutorial and JMRI demo file that might help me learn JMRI better and make progress on my layout's loconet/JMRI integration? I know about the 2010 clinic that's linked to from the JMRI documentation, but it skips a lot of information and shows other information in the wrong order. As for right now, I'm thinking about reducing the headache by taking apart pieces of my layout, creating a simple oval loop, with a single siding that connects at 2 turnouts, and working on my automation in a simpler environment, Then, as I figure things out, expand on it until I'm back to my proper layout.
Don, Sounds like a good approach but all you need is one turnout and 3 lengths of straight track for the experimenting. What are you using for powering and controlling the turnouts? I am planning on using Tortoise & Wabbit combinations and the Wabbit has options for creating detection 'blocks' that will align the turnout when approaching from the point ends. Paul
