Bob Milhaupt

I'd say this information is "a nice start". But it is lacking the level of specific detail that is needed to truely interpret the LocoNet messages and to make JMRI's...

I have concerns about the `loconet.LnReporter.lissyReport()` method as it exists, as well as the proposed change. - The proposed code specifically looks for bit 6 of LocoNet message byte 3...

@bobjacobsen, > To me, it looks like this code is progress, even if not known to completely and perfectly address Lissy messages. So I think it would be reasonable to...

@arthkl, It was not my intent to offend, or to limit your contributions to JMRI in any way. It was only my intent to ensure that you, as a new...

If you cannot read a loco CV via Digitrax software and the PR4, then it is almost impossible that JMRI will be able to read it. I suggest that you...

I'd recommend that you ask on the Digitrax-Users list about "neutral mode" and its effect on non-Digitrax mobile decoders.

@dsand47, "'Splain me Lucy!", please! I haven't opened "Preferences". I haven't loaded any panel/table XML. I haven't knowingly created _any_ Beans. _Something else_ has created some beans, without my explicit...

The attached XML was saved by PanelPro 5.1.1 (released version), C/MRI simulator connection, no XML loaded, no scripts run, only start-up action is "Open JMRI System Console", running on Win10...

@dsand47, I am using a C/MRI simulator connection. The connection has two defined C/MRI nodes. I have _not_ created any turnouts, or sensors, or memory variable, or panels. For the...

5.1.4 does not exhibit the problem, so far as I can tell from my minimal testing, so I consider the issue "resolved" and I am closing this issue.