Lenz seems to have more or less given up on it, and only when ESU got involved, they did the RailComPlus thing. Since it's introduction, very little has happened. I do wonder if they're going to expand on RailCom though. If, on the other hand, you need 10 detection modules right away, the RailCom enabled ones would be quite a hefty extra investment at that time, although relatively speaking it'd be a small part of the cost of the rest of the digital system. If you're starting now, and you don't need a lot of detectors, or at least don't need to buy them all right away, there's definitely a reason to go for RailCom enabled detectors. For example, S88 doesn't support RailCom I believe, so if you have S88 occupancy detection, the entire detection system would need to be replaced. JRMI seems used a lot more for layouts that are for a large part also manually operated for simulating real operations etc.Īgain, I'm definitely not against RailCom (I have a Lenz digital system, as well as the ECoS, so plenty RailCom capable stuff), but the investment can be too big if you have (part of) an existing layout that doesn't use RailCom yet. Those are much more focused on a switchboard, and in most cases also routing and then just running trains. I think it's also a different way of thinking how JRMI compares to iTrain / Traincontroller / RocRail and the like. The same setup can be done in most programs without using RailCom and without any routing as well, but again, you won't get the the confirmation there.

In that case, yes, it can detect the direction. But you probably have it set up to enter in for example W, and then stop inside STN without ever triggering E. Form the other direct, it starts braking at E and then stops at W. So, train comes in, activates W and starts decelerating, then activates STN, and then stops at E. Ah, so you're not using the east and west sections as stop sections? Often in a multidirectional track, there's 3 sensors, where the 2 outer ones function as both entry and stop.

Rocrail s88