The following is rearranged a bit to make it more readable.
On Jul 26, 2017, at 9:45 PM, Gerald Michels gjmichels53@... [jmriusers] <jmriusers@...> wrote:
This is the sequence I get when using the potentiometers on the board to
force the detectors HI and then LOW.
e.g.
11:24:32.359: [B2 42 50 5F] Sensor LS133 () is Hi. (BDL16 #9, DS5;
DS54/64/SE8c #17, AuxC/A3/DS05)
So it seems to me that Decoder Pro is seeing the BLOC8D just fine.
Agreed.
I am curious about the text at the end of each line in parentheses
regarding such things as BDL #16, and so on). Is this text "comment"
supplied by Decoder Pro or LocoNet?
The only thing that the LocoNet provides it the part in []. e.g. [B2 42 50 5F] called the raw data. The rest is JMRI trying to make it readable for you. Digitrax has used lots of ways to write addresses, depending on which Digitrax board was in use, so the part in () is trying to show those. That message could have been issued by channel 5 on a BDL16* set to #9; etc.
I set the BLOC8D in this example with a beginning address of 200, so I was
assuming the output would read 200-207, and wonder why I am getting numbers
133-140.
What does the prefix LS mean?
LocoNet Sensor.
Finally, the main reason for this whole exercise is to deliver block
occupancy data to Loconet that can be read by other hardware and set
signals. Is this what the HEX numbers are at the beginning, right after
the time stamp indicate?
If you open the JMRI Sensor Table, you¡¯ll see entries for each of those under the LS numbers. They¡¯ll change as messages come in from the layout. You can use that in the various JMRI tools.
Bob
--
Bob Jacobsen
rgj1927@...
Bob Jacobsen