For standard signals the commands red, green, yellow and white are available. Afterwards the command that should be executed for the signal when the train departs (for instance "green") has to be selected. Now, from the drop-down field ID the wanted signal is selected by it's ID. If the route contains switches, some switch commands should be in the list already. On tab Commands the commands executed on activating the route are listed. This is done by opening Tables → Routes… and selecting the relevant route from the Index tab. If a signal is to be switched by a route command, the signal has to be added to the list of commands of that route. signals with more than four aspects) it is mandatory. In some cases it is favourable to link signals with routes instead of blocks. The aspect number for aspects not used can be left at 0 (zero).Īddressing and aspect numbers as shown in the examples 5). If yellow is aspect number 2 then white has aspect number 3 and vice versa. Yellow is either 2 or 3 depending on the decoder configuration. Usually aspect 0 is red and aspect 1 is green. Multi aspect signals have a fixed correlation between aspects and gates.Īspect numbers are between 0 and 3 where 0 is the first aspect and 3 is the fourth. Standard signals with up to four aspects use the aspect number to assign aspects to gates. In this way up to 32 aspects can be controlled using up to 16 consecutive addresses. The more aspects are used, the more addresses will automatically be employed. Signals with three and four aspects are controlled by two addresses, the second one is base address + 1. For signals with two aspects only this address is used.
I'm pretty confident I can get to the same point in RocRail in a few hours also.The linear control type is the easiest way to control signals. I spent about eight hours learning JMRI and producing a panel, after that it only took about 5 hours to do the same thing with Model Railroad Automation. If you haven't tried any of these programs out yourself, I encourage you to. Once I get some time to really sit down and figure this out I'll try to write a review.
#Rocrail with. how to
I haven't spent much time trying to figure out my block sensors yet, and that scares me a little, because I have no idea how to begin. The addressing terminology seems a bit odd to me.
#Rocrail with. trial
The English documentation is thin, so it's a little trial and error. I also like that the mobile client (iRoc) is able to display and control panels.
The panels are layed out on a grid and it is easier to move objects around after you've placed them. Object properties are settable via property dialog boxes. I've only scratched the surface of RocRail, but so far I like it better than JMRI because it is packaged into one development environment. Now when I open iRoc on my iPad, it is connected to RocRail.
#Rocrail with. for android
Hooking up the iPad was a simple as installing iRoc (by the way there is also an andRoc client for Android OS), providing my computer IP address and RocRail Port (62842). <- If all of this client/server talk sounds scary (it does to me), don't worry it's just terminology of what's going on in the background, in reality, RocRail sets it up mostly, I only needed to supply my computer IP address and the COM Port settings for my Digitrax PR3. I'm running one client on the PC and one on the iPad. RocRail runs as a server and multiple clients (I think 10) can hook up to that service. I'm using RocRail on a PC with Windows XP. It is available in many languages and can run on PC, Mac and Linux.
#Rocrail with. software
RocRail is open source model railroad software similar to JMRI or Model Railroad Automation.
0 kommentar(er)
