My hidden staging tracks are arranged as a double track reverse loop. It was originally wired for DC, but now has DCC. Initially, each of the two tracks was divided into three blocks, with eight optical detectors spaced evenly along each block's length. LEDs in the control panel showed train location and progress as a series of lighted LEDs. Now, with DCC, I've combined the three blocks in each route into a single longer block with 24 optical detectors.
While running DC, after much thought, I developed my own layout track description method, defining track "segments" as the track between two adjacent features. I described each of those original staging blocks as eight segments, from detector to detector, with one detector being at the boundary with the next block. Now, as wired for DCC, each staging track has one block with optical 24 detectors.
Is JMRI able to handle this? I have read in previous posts that many things need to be defined as being at block boundaries, things which aren't necessarily at signal or power block boundaries. It seems to me, in those instances, that "block" is being used as I used "segment". I sure hope JMRI wouldn't require me to define each 24 detector block as 24 blocks, or 25 blocks, with the block end requiring two definitions, one for the detector and another for the actual block power boundary.
If "block" isn't used for that contiguous track controlled by one switch or relay, then what is used in its place?
