![]() ![]() For blocks with two physical sensor only.Ī combination of enter and pre2in. The events are generated sequentially shortin is simulated. For blocks with one physical sensor only.Ī combination of enter and shortin. The events are generated sequentially in is simulated. This kind of event is not suited for trains but solely for Car systems.Ī combination of enter and in. It is not connected to a physical sensor, but is generated after an in event from the previous block. The use of this event is discouraged: Use BBT instead. To use the exit event after the in event, the exit event must be set to the general route "all enter +/-" because after the in event the "from block" is set to the current block. When this happens the train is stopped immediately and put back in manual mode. This event is used for extra safety and detects if a train does not stop with in the distance between in and exit. Use this event type only if the sensor has no further functionality. (Lissy, BarJut, RailCom, …) This information is compared in auto mode to the identity-code set in the Loco properties, in manual mode this identity-code is shown in the block symbol. Some sensor systems provide more information like the address of the passing locomotive. The status will be evaluated if a reserve request is put by a train to make sure the whole block is electrically free. ![]() No action is taken as long as it is not unexpected. Hence, before the definition of sensors in the block properties all routes must have been set up before. For all possible routes sensors have to be defined. The definition of the sensors occurs in the route properties of a block and depends on from which block the train comes. When required additional sensors like pre2in, shortin etc. These sensors are called as enter and in. Rocrail needs two sensor events for every block which define when a train is entering the block and when it has (almost) 1) reached the end of the block. > Note: To the avoidance of misunderstandings it should be noted that with the word "Sensor" physical (real, hardware-) sensors, as well as the corresponding software objects and events are called. The page Objects: Sensors and its sub pages inform about the setup of sensors. In Rocrail sensors are defined as objects. An overview of the hardware and an introduction to the use of sensors is provided on the page Sensors. Sensors can either provide an impulse (e.g., switch rails, Reed contacts, hall sensors) or a permanent signal (e.g., contact rails, other occupancy detectors like current detectors etc.). By the sensors the positions of the trains on the layout are announced to the software. I'm pretty confident I can get to the same point in RocRail in a few hours also.Sensors are a core component of every computer controlled model railway. 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. 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. 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. 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 is open source model railroad software similar to JMRI or Model Railroad Automation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |