![]() ![]() Can a sensors that is used for oocupany also be used as the stop sensor for the section that the block belongs to? I have a RailCom enabled block detector that I will use. ![]() JMRI does this when using Automatic running of trains. 2) Automatic stop of trains at red signals, preferably close to the signal On Fri, at 07:28 AM, wrote: 1) Automatic control of signals based on block occupancy and turnout position The larger the number of block occupancy sensors you have (especially in those areas where train speeds are known to change dramatically on account of grade change or tight curves) the better the chance the software will have at making its guess. ) can _make a guess_ about the position of a train, but it cannot _know_, without help from hardware. Only you can determine the answer to that question! So one key question is "how much precision is needed". Doesn't matter which software you use - they all will face the same challenges. With all of those variables, and likely a host of additional ones, it is difficult to predict where a train will be at any given time. How many feeders have unknowingly detached from the track, resulting in poor power distribution to your locomotives? How many cars "uncoupled" unintentionally and unknowingly from the train? How much has the performance of the loco(s) changed since they were first characterized X years ago? Do any two or more locos on a multi-loco train "fight each other" at certain "speed-steps"? Do any two or more locos on a multi-loco train "fight each other"? Is this other downgrade so steep that the train cannot even stop from the current speed? How much of the train is on this side of the peak or low-point of the grade? How much does the train speed up on this other grade? How much does the train slow down on this grade? How fast can the loco(s) run with _this_ train? In long, exactly how fast a loco moves depends on many things, including: Magnus wrote "* Can JMRI calculate the train position based on speed and time to stop the train at a signal using just one occupancy sensor (like RocRail and iTrain does) " Can a sensors that is used for oocupany also be used as the stop sensor for the section that the block belongs to? Should each turnout be placed in a block of its own? What is preferred when installing sensors: * Sections with a with at least two blocks, one short block at the signal, the block sensor is used as stop sensor? * Add optical sensors at desired stopping points and use them as stop sensor? * Can JMRI calculate the train position based on speed and time to stop the train at a signal using just one occupancy sensor (like RocRail and iTrain does) Best regards Magnus Now I want to add sensors with 3 goals in order of priority : 1) Automatic control of signals based on block occupancy and turnout position 2) Automatic stop of trains at red signals, preferably close to the signal 3) Automatic running of trains I have a RailCom enabled block detector that I will use. Hi, We are building a new layout and have it hooked up to JMRI for running trains and operating turnouts and signals. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |