Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Locked JMRI with multiple systems
|
Hi JMRI experts! I have so far been using JMRI to control a layout using DCC via a SPROG, using a dragonboard or, as an alternative, a Raspberry Pi 3. However, I am now thinking of adding train detection to my system, and the simplest way to do this I believe would be to use a Merg CBUS interface (via a second USB), either for the inputs alone, or also as an alternative to DCC for accessory (signalling and points) control. Looking at the JMRI documentation, I am not very clear on whether or not there are any restrictions on mixing and matching between multiple systems in this way? Do many JMRI users have mixed systems, particularly as I am proposing, DCC and CBUS? Are there any particular pitfalls that I should be aware of, or best ways to combine the two systems? How many simultaneous (USB connected) DCC systems will JMRI support? Regards, Ian Blair |
|
Hello Ian on the Cumberland West we can have up to 10 computers (all Windows 10) running JMRI. Normally we run 8 for B&O sessions, and 4 for WM sessions. Twice a year we run both railroads using all 10. Of the 10, 5 are dedicated B&O towers, 1 is a laptop for the WM (all connected to LCC only, all with touch screens), 2 for separate dispatchers (one for B&O the other for WM - LCC only), 2 for staging (one inbound and one outbound - these are the only ones that can also run trains, via NCE USB and Serial, plus LCC and Digitrax on USB, both B&O and WM). We also have a spare computer prepared (but turned off). 1 JMRI system also can run the WiThrottle Server for using cell phones for throttles. We also used to run the Web Server to use an Android tablet for one of the small towers, but due to being too slow (both communications and tablet) we now use a laptop with JMRI and LCC connection. One thing to point out is most computers do not share Logix (each tower has its own panel and Logix); only the 2 staging systems share staging Logix, though they operate only one end of staging (input or output).? NOTE: staging is one way only. I know this is no help for your specific hardware, but JMRI is very flexible with many computers. Cheers LeoP On Tue, Mar 19, 2019 at 5:15 AM Ian Blair via Groups.Io <blair.ian=[email protected]> wrote:
|
|
Ian,
On 19 Mar 2019, at 11:13 PM, Ian Blair via Groups.Io <blair.ian@...> wrote:There is no hard limit for the number of connections you can set up in a single instance of JMRI. Certainly no problem with two. Many users have two or even more. Dave in Australia |
|
Thank you all for your comments.? To clarify a little, I am more interested in how JMRI handles mixed model railway interfaces, rather than many of the same interface, but it certainly looks flexible, and if I get any issues then very clearly I can use separate computers for train control and for signalling/train detection. I think my next step will be to try some experiments. I have had no issues (other than a small change that was made previously for 64 bit ARM) with using JMRI on different computer systems (from Raspberry Pi & Dragonboard (with their linux versions) to Windows PC, to SPROG DCC. Even an original RPi will work, albeit probably more slowly than most users would like. BTW the Cumberland West system in particular sounds very impressive!? Ian Blair
On Tuesday, March 19, 2019, 10:27:32 PM GMT, Marc <forfoum@...> wrote:
and since this is CPU load, the computer may run out of wind under a high connection count. I've run simultaneous Loconet connections on a single computer without a hic and it was a 32 bit, 2GHZ system. Guess it depends on what traffic is being generated and needs to be processed. Marc? |
|
Ian,?
Very easy: Go to Edit -> Preferences in PanelPro, and you can add as many "Connections" you need. Each will have its own System identifying letter, and a number if you need more. You can have a MERG CBUS as 'M' on COM3, so your turnouts and sensors on the CBUS will start with MT and MS, your LocoNet connection on COM4 will use LT and LS, and if you add two NCE interfaces for two commend stations, you would have NT and N2T (or N1T and N2T). (all configurable, you could use 'A', 'B', 'C', and 'D' instead)? The main things to watch out for are, 1) when the computer reboot, is the LocoNet still on COM4, since you specify that when you create the Connection, and 2) which Connection controls the Trains, power and so forth. There are multiple layouts around here in the DFW area with more than one interface (running on only 1 PC or Raspberry Pi), so no problems with JMRI in that regard.?? Speed |
|
Thank you! That looks exactly like what I need to do/check out !
On Wednesday, March 20, 2019, 12:57:00 PM GMT, Speed <gertmul@...> wrote:
Ian,? Very easy: Go to Edit -> Preferences in PanelPro, and you can add as many "Connections" you need. Each will have its own System identifying letter, and a number if you need more. You can have a MERG CBUS as 'M' on COM3, so your turnouts and sensors on the CBUS will start with MT and MS, your LocoNet connection on COM4 will use LT and LS, and if you add two NCE interfaces for two commend stations, you would have NT and N2T (or N1T and N2T). (all configurable, you could use 'A', 'B', 'C', and 'D' instead)? The main things to watch out for are, 1) when the computer reboot, is the LocoNet still on COM4, since you specify that when you create the Connection, and 2) which Connection controls the Trains, power and so forth. There are multiple layouts around here in the DFW area with more than one interface (running on only 1 PC or Raspberry Pi), so no problems with JMRI in that regard.?? Speed |
|
Speed,
I have been searching for further information and clarification on just how JMRI handles multiple Command and Control systems and came across your reply to Ian Blair's similar query #158154, #158210 from last March. Your reply gave me some guidance on this issue because I am faced with a similar problem and have no clue as to where to start. My story follows developments in the DCC world. Several years ago now when I first looked at DCC, there was only the Hornby Zero One system from earlier days, so I decided to try the ZTC System. I have been using the ZTC system since as my 'Train Control System' without any problems. Developments within the DCC world continued and we got into 'Sound' and this meant more 'Function' Buttons than my system could easily provide. I then decided that I wanted to move on from manual control of the devices on the layout and discovered M.E.R.G. and its modules. At about the same time I was looking into ways to cut down on the wiring and static 'Control Positions' and have the freedom to set my train going and follow it all around the layout on its journey. This is where JMRI came into the picture. By this time my layout was growing from being a Branch Line to becoming a Branch Line within a Branch Line and therefore the need for 'Districts' arose and the need for a more sophisticated approach to Commend and Control. JMRI only ever talked about the 'Whole' layout which, at the time, to me, meant that I needed to develop to what my layout would eventually become - not that I had any fixed ideas about that at the time. I used the "Anyrail" package to develop several versions of what my 'Whole' layout might become and was able to get the output from "AnyRail" to convert into a format that JMRI could work with. I now had the problem of choosing how I was going to proceed with the DCC system when the whole digital world exploded with many innovations in may different fields! I looked at all of the current DCC Systems available to me but could not decide on which to choose. This limited me to using the 'Internal' Naming scheme within JMRI with no actual connections to the layout. To avoid the expense and time to fit and wire static Control Panels I decided that Touchscreen Tablets, running JMRI, was the way to go so no physical Control Panels! Now I had a 'Whole' layout file using the 'Internal' structure in JMRI but no system except perhaps, MERG for device control. Lenz then announced the introduction of their new Version 2 system. So, this is where I am today. I have decided to change to the new Lenz system from my existing ZTC System for 'Train Control' as well as some of its Devices (ABC System) but to continue to use the DIY MERG Modules for Layout Control. This means that I will have multiple Systems running within the JMRI Program which has overall control of nearly everything. The introduction of Apps such as 'WI Throttle' and 'Engine Driver' now gives me the choice of adding 'Train Control' to the Tablet that the user carries around with them if they choose to move around the whole layout and does this removes the need for several Lenz 'Cabs'? My question is:? "How do I put all of this together, in a logical sequence, that allows full Control of the layout and of the locos running on it?" Dave |
to navigate to use esc to dismiss