On 1/25/2025 11:17 AM, Dave Sand wrote:
Jay,
I recommend that you look at the CTC tool within JMRI. ?The help page is at <>
That's JMRI's "new"er CTC solution, as opposed to several older JMRI pieces that can be used as part of a CTC solution with _lots_ of extra "work".
It can produce something "like" a CTC solution.
But be aware that if you want something "prototypical", you may need a different solution than that newer JMRI CTC tool can provide. That one does not seem to model a "code line", and falls short of handling things beyond OS and Signal and Switch indications and controls. In many ways, it is more like a "direct-wired" CTC solution, rather than a "time-coded" CTC solution.
If you have a typical CMRI "QB" code implementation a-la Chubb's documentation, then you may have features that the JMRI "new" CTC _cannot_ do , probably including a "time-coded" CTC solution.
This would not be a significant problem, except that _all of JMRI's CTC logic_ implemented in the "new" CTC solution is _hidden_ from the user. So when you want to get things to work differently, you can try to "tweak" the configuration information. Maybe you can get it to work the way you want. Maybe not. But you cannot change the "new" CTC code without JAVA experience, something that is awkward for most. And that typically means that you will spend time working with a JMRI developer to get new features added.
(Signaling is HARD. Anyone who tells you otherwise is full of wishful thinking, or doing something wrong, or doing something so simple that it is nothing like time-coded "CTC"!)
