¿ªÔÆÌåÓý

Locked Decoder Pro returns 123 for all decoder settings


 

OK, using DP V4.2 and LocoBuffer-USB and WIN10.
Haven't used DP in several months. The last time I used it it was working properly. Today the problem is that when trying to read values from a decoder, DP returns the value of 123 for all fields/all pages. Have verified that LocoBuffer-USB is installed correctly. The decoders (multiple) operate properly on the MAIN, all functions. So I think I have eliminated the decoders and LocoBuffer-USB as the problem.

Any thought? Thanks. Bob


 

Bob,

Make sure that LocoNet is selected in Preferences >> Defaults.

Dave Sand

On Jul 19, 2018, at 2:30 PM, nebrzephyr via Groups.Io <nebrzephyr@...> wrote:

OK, using DP V4.2 and LocoBuffer-USB and WIN10.
Haven't used DP in several months. The last time I used it it was working properly. Today the problem is that when trying to read values from a decoder, DP returns the value of 123 for all fields/all pages. Have verified that LocoBuffer-USB is installed correctly. The decoders (multiple) operate properly on the MAIN, all functions. So I think I have eliminated the decoders and LocoBuffer-USB as the problem.

Any thought? Thanks. Bob


 

... and upgrade to 4.12 - what you're encountering is a typical 4.10 problem, and it will happen again (and again).

Wouter

On 19 July 2018 at 20:34, Dave Sand <ds@...> wrote:
Bob,

Make sure that LocoNet is selected in Preferences >> Defaults.

Dave Sand



> On Jul 19, 2018, at 2:30 PM, nebrzephyr via Groups.Io <nebrzephyr=yahoo.com@groups.io> wrote:
>
> OK, using DP V4.2 and LocoBuffer-USB and WIN10.
> Haven't used DP in several months. The last time I used it it was working properly. Today the problem is that when trying to read values from a decoder, DP returns the value of 123 for all fields/all pages. Have verified that LocoBuffer-USB is installed correctly. The decoders (multiple) operate properly on the MAIN, all functions. So I think I have eliminated the decoders and LocoBuffer-USB as the problem.
>
> Any thought? Thanks. Bob
>






 

OK, ,glad to hear it's a known issue. Will do the upgrade and report back. Thanks. Bob


 

One thing: the upgrade alone is not enough. Whether before or after upgrading, you will still need to go to the preferences and correctly set everything up. After that, 4.12 will leave things be, whereas 4.10 will mess up at every opportunity it sees...

Wouter

On 20 July 2018 at 15:04, nebrzephyr via Groups.Io <nebrzephyr@...> wrote:
OK, ,glad to hear it's a known issue. Will do the upgrade and report back. Thanks. Bob



 

OK, installed 4.12 and same problem. I have verified everything I can thing of. I ran the LocoBuffer-USB test noted on their website and it checks out. Could it be JAVA related? I have version 8.

What other things should I be checking. Thanks. Bob


 

Bob,

Did you verify that the "Preferences >> Defaults" entries are set to tLocoNet?

Dave Sand

On Jul 20, 2018, at 10:21 AM, nebrzephyr via Groups.Io <nebrzephyr@...> wrote:

OK, installed 4.12 and same problem. I have verified everything I can thing of. I ran the LocoBuffer-USB test noted on their website and it checks out. Could it be JAVA related? I have version 8.

What other things should I be checking. Thanks. Bob


 

Preferences > connections > defaults needs to be Loconet and not internal

Tom Wilson


On Fri, Jul 20, 2018, 9:42 AM Dave Sand <ds@...> wrote:
Bob,

Did you verify that the "Preferences >> Defaults" entries are set to tLocoNet?

Dave Sand


> On Jul 20, 2018, at 10:21 AM, nebrzephyr via Groups.Io <nebrzephyr=[email protected]> wrote:
>
> OK, installed 4.12 and same problem. I have verified everything I can thing of. I ran the LocoBuffer-USB test noted on their website and it checks out. Could it be JAVA related? I have version 8.
>
> What other things should I be checking. Thanks. Bob
>





 

Yep, preferences are set. Wondering about potential baud rate differences. Near as I can tell LocoBuffer-USB is 125,000? (according to the doc). Yet DP has that blanked out in in references, What's strange is I do not get an error even if I have no decoder attached to the programming track. DP just returns all 123 values.

Bob


 

The other possibility (which hardly ever happens by mistake, but you never know) is that you are using the simulator. That, too, makes all requests return 123.

Absolutely forget about baudrate. This is either something set to internal that shouldn't be, or a simulator connection. Nothing else fits the symptom.

Wouter

On 21 July 2018 at 17:18, nebrzephyr via Groups.Io <nebrzephyr@...> wrote:
Yep, preferences are set. Wondering about potential baud rate differences. Near as I can tell LocoBuffer-USB is 125,000? (according to the doc). Yet DP has that blanked out in in references, What's strange is I do not get an error even if I have no decoder attached to the programming track. DP just returns all 123 values.

Bob



 

Bob,
The LocoBuffer-USB runs at 57.6Kb. I'm not sure where you might have seen 125,000. However as long as you have 'LocoBuffer-USB' selected in JMRI, then the baud rate is locked to the correct value, so you don't need to worry about that. (be sure it is 'LocoBuffer-USB', not 'LocoBuffer').

This error is typical for incorrect defaults settings. Be sure that they are all set to 'LocoNet' and then saved. (then upgrade to 4.12)

Dick :)

On 07/21/2018 12:18 PM, nebrzephyr via Groups.Io wrote:
Yep, preferences are set. Wondering about potential baud rate differences. Near as I can tell LocoBuffer-USB is 125,000 (according to the doc). Yet DP has that blanked out in in references, What's strange is I do not get an error even if I have no decoder attached to the programming track. DP just returns all 123 values.

Bob


 

Problem solved. After a recent WIN10 maintenance (ugh!!!) it "lost" the LocoBuffer-USB, so I had to reinstall it. What I failed to notice at the time was that WIN had changed the port # from what was previously used. So when I checked DP preferences I mistaking assumed the previous used COM #. Today in looking in Device Manager I see the new COM #. Changed DP preferences and all is well.

I appreciate everyone help in this even though it was "User Error". :-))

Bob