开云体育

As Jon says, it seems like something changed the status of all the entries.
Since I don't know of any command that would do that, I have to ask:



WHEN WAS THE COMMAND STATION BATTERY LAST CHANGED??



Sorry to use all caps, but when I see something that seems like a change
that makes no sense, I suspect the hardware. A failing battery could account
for anything being weird in the slots or settings.



Given the history of the JMRI throttle, I've known we put hooks for a few
other forms, but I've not found any code to do stuff with the Motorola form
other than identify the header if seen. Yes some of the command station have
something to do with it. But I can't find anything that JMRI could generate
to do the status edit. Maybe I missed it, but so far, I can't see how JMRI
would have any way to do what happened. At least on LocoNet, I don't see
code to do things with the format, only read it. Ecos, Marklin, and Zimo
have more code so might, but nothing obvious about being able to do anything
with it changing everything.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Folks,
I recently dove into my JMRI installation and all went well......for a while. I managed to list about thirty of my locos on the roster but when I opened the software yesterday and turned on my NCE DCC
system the software will not communicate with the DCC system. It just displays a notification (in red) that NCE is offline and nothing I have tried will reestablish communications between the two.
Has any one in this group ever experienced this situation and what did you do to resolve it? By the way the DCC system works fine in all other respects. Thanks in advance.
Bill Aulicino
Apex NC

Mike,
From what I can gather.
The laptop is a Dell XPS M1710. Model number on the back is PP05XB.
It has win7 ultimate.
200 Ghz processor
4 GB memory.
320 GB hard drive
GForce 7900 sound.
I can't get it to load my email keeps giving me stopped responding messages and script errors.
Thanks for advice in advance
Perry

On Jun 21, 2017, at 2:22 PM, Michael Piazza mpiazza2007@... [jmriusers] <jmriusers@...> wrote:

Can you be more specific as to it's specs and the Dell model? Not only
could we then tell you if it will run, if you want or need to upgrade it I
could point you at the parts that will work for you.

Mike Piazza

On Jun 21, 2017 9:34 AM, "texasperry@... [jmriusers]" <
jmriusers@...> wrote:

I read the system requirements on JMRI site. I did not see anything about
memory or processor speed. Are there any minimum requirements.
My current machine is an old old Dell gaming computer I was given. I could
not load Win 10 on it. I got a message it did not mee system requirements.
I was going take it to the local laptop shop and see if it could be
upgraded, or look at what they may have off lease.


Thanks
Perry

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

Jim S.,

There are two obvious things that can control a slot's "default" "operating mode" - that is, whether the slot defaults to "trinary" or "128 speed step" or "28 speed step" or "14 speed step" or "motorola" or one of the other possibilities...

First, you might want to take a look at DCS100 "OpSw"es 21, 22, and 23. These are supposed to provide the "global system default type" when acquiring a locomotive which is not already in the DCS100 slot table (and when the throttle does not override the command station).

Depending on which firmware version of DCS100 you have, and which version of the DCS100 manual you have, you can find conflicting information on these, and different lists of what values are supported. I've always used a "poke-and-hope" approach - try a set of OpSw 21/22/23, power-down then power-up, then acquire a loco that is not already in a slot, and see what mode it comes up in.

You need to use a DT*00x or DT402x throttle with a display to view the "status". For some throttle models, it is necessary to "status edit" the slot to view the "status" to find out what "status" or mode that the slot is using for the loco.

Second, if you use DT100x, DT300x, DT400x, DT402x, or DT500x throttles, each of these can provide a "default slot operating mode" which may override the DCS100 defaults.

With the DT100x throttles, the throttle's "Secondary Option" code "oS" influences the default slot operating mode value.

With the DT300x and DT400x throttles, throttle "OpSw2" influences the default slot operating mode value.

With the DT402x throttles and the DT500x throttles, when the "NewTypes" option is "on", then the "Nu Type=" value takes precedence over the command station's default slot operating mode; you want to make sure the "Nu Type=" value is reasonable (i.e. not "tr1"). Alternately, you may set "NewTypes" to "off" and rely on the command station's default value.

Regards,
Billybob

/On 6/22/2017 6:04 PM, jhswann@... [jmriusers] wrote://
/

/I can't find a location where to make 128 the default on the DCS100
but i'll keep looking/

There is a command station setting to make 128 default for NEW
decoders. But if somehow your current decoders were changed to a
different status then you either need to change them (status edit each
and every one) or delete and re-enter.

It seems as if a global command was sent to "status edit" all the
decoders on your layout to Motorola trinary.

--
Jon Miller
For me time stopped in 1941
Digitrax Chief/Zephyr systems,
SPROG, JMRI User
NMRA Life member #2623
Member SFRH&MS

Hi Fellows.

Thanks to all who tried to assist with this issue.


I have a solution:


Somehow the command station started to use something called stat tri for its communications with all my mobile decoders. When I changed all the engines (each individually!) back to 128 (digitrax preferred) the world returned to normal. This must be done from the wireless throttle near as I can tell. I can't find a location where to make 128 the default on the DCS100 but i'll keep looking. As of now the layout is operational. 2 days! WHEW!




Thanks again.




Jim Swann

Thanks for the info. That works.

Blair,

Thank you for your input and advice.

I had studied the message formatting earlier, however it was not obvious to me at first, was that the C/MRI protocol does not have any message formats which deal with only one output, or only one input. It only has formats which deal with "all inputs on the node" or "all outputs on the node" as clarified by Billybob in a previous post.

Regards
Geoff

Randall,



Thank you for the information. Be assured that I am pulling for your early success. In the meantime, I can get by using VNC Viewer remotely since it has a scalable window.



Brian



From: jmriusers@... [mailto:jmriusers@...]
Sent: June 22, 2017 17:08
To: jmriusers@...
Subject: Re: [jmriusers] JMRI with Java 9?





JMRI does not run with Java 9 on any OS. We hope to have that resolved soon.

Randall

On Jun 22, 2017, at 16:57, 'Brian Gilhuly' brianlgilhuly@... [jmriusers] <jmriusers@...> wrote:

Is there a way to make JMRI work with Java 9 on Windows? Running on Java 8
on my high-res display results in panels too miniscule to use. Setting the
font size to 30 makes the text in most windows semi-readable, with the
layout scrambled. But when I try with java 9, which does work well on my
display, the JMRI loader reports a "Java not found" error.

Apparently this is a known problem, but the last thread on the subject I
could find ended with someone asking in msg. #135627, "Has the problem with
JMRI failing to load under Java 9 been resolved now? (It was due to Java 9
defining different registry keys so the ones that JMRI checks to see if Java
is present were not found)". That was back on Feb. 7, and he never got an
answer.

What is the current status? If it is just a matter of registry keys, there
should be a simple manual work-around.

Thanks,

Brian Gilhuly

[Non-text portions of this message have been removed]

Steve,

Thanks for the suggestion. Yes there is an exclamation point on my WiFi icon, on both my phone and tablet.


On my Motorola Droid phone under WiFi Advanced, there is an option named "Avoid bad WiFi connections". Unfortunately, it was already off.This phone is running Android version 7.0


My knockoff tablet also has an option on the WiFi Advanced menu, this one is called "Avoid poor connections". It too was turned off. This tablet is running Android version 4.4.2


Bob

Jim,



The "key" is your "STAT TRI" message. The address (1201) has been "Status
Edited" (most likely inadvertently) so your command station is sending
"Motorola Trinary" format messages to address 1201. Your DCC decoder does
respond to these.



Check your manual for "Status Edit" on how to "Status Edit" the address back
to 128 speed step operation. Alternative -- use the JMRI Slot Monitor to
find address 1201 and clear that slot. Then when you select address 1201 it
will be a "new" address when you select it.



HTH



Ross Kudlick



From: jmriusers@... [mailto:jmriusers@...]
Sent: Thursday, June 22, 2017 4:50 PM
To: jmriusers@...
Subject: [jmriusers] Re: Trouble with JMRI throttle





Hi Walt.

Here is an update in the problem. It is an email I sent to Marc Fournier in
Quebec.
Hi Marc.
Thanks for the reply.
I have just trashed another day downstairs trying to sort this out.
Here is more data:
1. I use a digitrax command station DCS 150. I have a digitrax wireless
duplex throttle which I rarely use.....I usually run from the computer with
JMRI; however, I was using the wireless throttle on 1 engine (#1201) the
night prior to my problems as I was aligning a turntable track at the far
side of my layout. I tried Breezleys trick from the forum , and it was no
help. I do not use consists as yet.
2. Today I beamed up my program and confirmed that loconet system is
working. I can change all my switches and my script to "set all switches"
runs perfectly
3. I picked one engine (#1201) (the one I was using on my turntable test)
and it was not working on either the wireless or the computer throttle. I
was fiddling with the loco select knob on the wireless throttle and above
the 1201 number I got the message STAT TRI on the screen. I also noted that
I could move between the numbers "stat tri",14,28/128 - but I can't remember
how i was able to do that! . I hit 128 and the engine jumped to life and
roared around the track. I was quite surprised. I have no idea what I did. I
had to put the engine on the programming track and with much fussing about I
now have 1 engine running more or less the way it was with either the
throttle or the computer. All my other engines respond to some commands from
the computer throttle ( horns squeals etc.) but no engines work (i.e. run).
The wireless doesn't work them either.
4. I notice the buttons on the computer throttle don't seem to dim/un-dim
properly when they are clicked. Sometimes they stay grey, sometimes the are
clear. Sometime they don't clear until another button is pushed.


I am quite baffled by this mess.


Hope you have some ideas what to do next...




Cheers,




Jim

JMRI does not run with Java 9 on any OS. We hope to have that resolved soon.

Randall

/On 6/22/2017 1:49 PM, jhswann@... [jmriusers] wrote://
/

/I got the message STAT TRI on the screen/

You probably already know this and I have not followed this at all
but Is this not Motorola trinary?

--
Jon Miller
For me time stopped in 1941
Digitrax Chief/Zephyr systems,
SPROG, JMRI User
NMRA Life member #2623
Member SFRH&MS

Is there a way to make JMRI work with Java 9 on Windows? Running on Java 8
on my high-res display results in panels too miniscule to use. Setting the
font size to 30 makes the text in most windows semi-readable, with the
layout scrambled. But when I try with java 9, which does work well on my
display, the JMRI loader reports a "Java not found" error.



Apparently this is a known problem, but the last thread on the subject I
could find ended with someone asking in msg. #135627, "Has the problem with
JMRI failing to load under Java 9 been resolved now? (It was due to Java 9
defining different registry keys so the ones that JMRI checks to see if Java
is present were not found)". That was back on Feb. 7, and he never got an
answer.



What is the current status? If it is just a matter of registry keys, there
should be a simple manual work-around.



Thanks,

Brian Gilhuly

Dan,
Okay. ? I am departing on vacation as I write this. ?So after the 4th.
Thanks.?
Norman

Sent from Yahoo Mail on Android

On Thu, Jun 22, 2017 at 8:05 AM, daboudreau@... [jmriusers]<jmriusers@...> wrote: Norman,
Instead of sending the file to the printer, try the "Microsoft XPS Document Writer" and send the output to me to review. ?You might have a printer that doesn't quite work right with JMRI.
Dan

Hi Walt.

Here is an update in the problem. It is an email I sent to Marc Fournier in Quebec.
Hi Marc.
Thanks for the reply.
I have just trashed another day downstairs trying to sort this out.
Here is more data:
1. I use a digitrax command station DCS 150. I have a digitrax wireless duplex throttle which I rarely use.....I usually run from the computer with JMRI; however, I was using the wireless throttle on 1 engine (#1201) the night prior to my problems as I was aligning a turntable track at the far side of my layout. I tried Breezleys trick from the forum , and it was no help. I do not use consists as yet.
2. Today I beamed up my program and confirmed that loconet system is working. I can change all my switches and my script to "set all switches" runs perfectly
3. I picked one engine (#1201) (the one I was using on my turntable test) and it was not working on either the wireless or the computer throttle. I was fiddling with the loco select knob on the wireless throttle and above the 1201 number I got the message STAT TRI on the screen. I also noted that I could move between the numbers "stat tri",14,28/128 - but I can't remember how i was able to do that! . I hit 128 and the engine jumped to life and roared around the track. I was quite surprised. I have no idea what I did. I had to put the engine on the programming track and with much fussing about I now have 1 engine running more or less the way it was with either the throttle or the computer. All my other engines respond to some commands from the computer throttle ( horns squeals etc.) but no engines work (i.e. run). The wireless doesn't work them either.
4. I notice the buttons on the computer throttle don't seem to dim/un-dim properly when they are clicked. Sometimes they stay grey, sometimes the are clear. Sometime they don't clear until another button is pushed.


I am quite baffled by this mess.


Hope you have some ideas what to do next...




Cheers,




Jim

Thanks. It will take me a little while to dissect that. I see
several things going on, but I need to figure out where they are
coming from.

I can say that only the "Unsupported Command Sent to Command Station"
is caused by JMRI sending something to the Z21, and my guess is that
it is the JMRI XPressNet throttle implementation looking for some
piece of function status the Z21 must not support. This is something
I can stop, but it isn't something that will cause a loss of control
(we see this message because the command station responded to a
request we made).

Paul

On Thu, Jun 22, 2017 at 3:12 PM, tventonukgateway@...
[jmriusers] <jmriusers@...> wrote:

Thanks Paul, copy of system console follows.

Tim

2017-06-22 19:32:58,282 util.Log4JUtil INFO - * JMRI log ** [main]
2017-06-22 19:32:58,360 util.Log4JUtil INFO - This log is appended to file: C:&#92;Users&#92;Tim&#92;JMRI&#92;log&#92;messages.log [main]
2017-06-22 19:32:58,376 util.Log4JUtil INFO - This log is stored in file: C:&#92;Users&#92;Tim&#92;JMRI&#92;log&#92;session.log [main]
2017-06-22 19:32:58,423 apps.Apps INFO - PanelPro version 4.9.1ish+jenkins+20170620T0042Z+R91f70ab starts under Java 1.8.0_31 on Windows 7 x86 v6.1 at Thu Jun 22 19:32:58 BST 2017 [main]
2017-06-22 19:33:15,614 profile.ProfileManagerDialog INFO - Automatically starting with profile New_profile.3f0c6862 after timeout. [AWT-EventQueue-0]
2017-06-22 19:33:15,645 apps.Apps INFO - Starting with profile New_profile.3f0c6862 [main]
2017-06-22 19:33:16,815 node.NodeIdentity INFO - Using jmri-047D7B5B5239-3f0c6862 as the JMRI Node identity [main]
2017-06-22 19:33:20,309 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,341 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,341 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,341 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,356 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,356 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,372 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,372 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,387 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,387 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,387 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,387 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,403 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,403 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,419 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,419 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,419 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,434 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,434 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,434 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,434 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,450 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,450 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,450 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,465 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,465 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,465 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,465 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,481 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,481 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,481 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,497 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,497 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,497 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,497 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,512 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,512 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,512 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,621 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,621 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,621 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,621 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,637 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,637 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,653 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,653 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,653 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,653 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,668 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,668 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,668 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,668 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,684 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,684 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,684 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,684 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,699 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,699 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,699 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,699 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,715 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,715 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,715 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,715 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,731 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,731 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,731 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,731 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,731 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,746 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,746 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,746 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,746 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,762 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,762 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:20,762 roster.RosterEntry ERROR - IllegalArgumentException in RosterEntry.setDateModified - this may indicate a problem with the classpath, specifically multiple copies of the 'jackson` library. See release notes [main]
2017-06-22 19:33:22,587 util.FileUtilSupport INFO - File path program: is C:&#92;Program Files&#92;JMRI&#92; [main]
2017-06-22 19:33:22,587 util.FileUtilSupport INFO - File path preference: is C:&#92;Users&#92;Tim&#92;Dropbox&#92;JMRI&#92; [main]
2017-06-22 19:33:22,587 util.FileUtilSupport INFO - File path profile: is C:&#92;Users&#92;Tim&#92;JMRI&#92;New_profile&#92; [main]
2017-06-22 19:33:22,587 util.FileUtilSupport INFO - File path settings: is C:&#92;Users&#92;Tim&#92;JMRI&#92; [main]
2017-06-22 19:33:22,587 util.FileUtilSupport INFO - File path home: is C:&#92;Users&#92;Tim&#92; [main]
2017-06-22 19:33:22,587 util.FileUtilSupport INFO - File path scripts: is C:&#92;Program Files&#92;JMRI&#92;jython&#92; [main]
2017-06-22 19:33:43,709 throttle.ControlPanel WARN - Unhandled slider type: 0 [AWT-EventQueue-0]
2017-06-22 19:34:34,647 throttle.AddressPanel INFO - Asked for 837 got 837(L) [AWT-EventQueue-0]
2017-06-22 19:37:40,927 throttle.AddressPanel INFO - Asked for 2203 got 2203(L) [AWT-EventQueue-0]
2017-06-22 19:43:32,910 withrottle.UserInterface INFO - Creating new WiThrottle DeviceServer(socket) on port 1042, waiting for incoming connection... [WiThrottleGUIServer]
java.lang.ArrayIndexOutOfBoundsException: 18367hit not translated
java.lang.ArrayIndexOutOfBoundsException: 18156hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17788hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17788hit not translated
java.lang.ArrayIndexOutOfBoundsException: 31117hit not translated
java.lang.ArrayIndexOutOfBoundsException: 31117hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17788hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17902hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30425hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17938hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30345hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19400hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17562hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17938hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30345hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19400hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30741hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17562hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17756hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17756hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17938hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30345hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17562hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19400hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30345hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17938hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19400hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17562hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30696hit not translated
java.lang.ArrayIndexOutOfBoundsException: 18083hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17806hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19614hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19346hit not translated
java.lang.ArrayIndexOutOfBoundsException: 18592hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19648hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30705hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17282hit not translated
java.lang.ArrayIndexOutOfBoundsException: 18156hit not translated
java.lang.ArrayIndexOutOfBoundsException: 18367hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30423hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17398hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19665hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19665hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30423hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17398hit not translated
java.lang.ArrayIndexOutOfBoundsException: 18156hit not translated
java.lang.ArrayIndexOutOfBoundsException: 18367hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19356hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19565hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30437hit not translated
java.lang.ArrayIndexOutOfBoundsException: 18578hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19358hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30699hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30740hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30384hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17792hit not translated
java.lang.ArrayIndexOutOfBoundsException: 16827hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30476hit not translated
java.lang.ArrayIndexOutOfBoundsException: 18081hit not translated
java.lang.ArrayIndexOutOfBoundsException: 17037hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19226hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19395hit not translated
java.lang.ArrayIndexOutOfBoundsException: 19496hit not translated
java.lang.ArrayIndexOutOfBoundsException: 18458hit not translated
java.lang.ArrayIndexOutOfBoundsException: 18485hit not translated
java.lang.ArrayIndexOutOfBoundsException: 30442hit not translated
Failed to create URL from file:/C:/Program%20Files/JMRI/help/en/JmriHelp_en.hs|JMRI: Getting Started with Scripting
2017-06-22 19:47:04,868 withrottle.UserInterface INFO - Creating new WiThrottle DeviceServer(socket) on port 1042, waiting for incoming connection... [WiThrottleGUIServer]
2017-06-22 19:47:04,868 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:47:07,286 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:47:09,298 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:47:10,905 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:11,919 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:12,933 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:13,947 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:14,961 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:15,975 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:16,989 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:18,034 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:19,048 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:20,062 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:21,076 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:22,090 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:23,104 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:24,118 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:25,132 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:26,146 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:27,160 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:28,174 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:29,188 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:30,202 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:31,216 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:32,230 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:33,244 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:34,258 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:35,272 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:36,286 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:37,300 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:38,314 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:47:39,328 lenz.XNetThrottle ERROR - Unsupported Command Sent to command station [AWT-EventQueue-0]
2017-06-22 19:48:39,497 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:48:41,494 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:48:43,491 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:48:45,503 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:48:47,500 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:48:49,513 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:48:51,509 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:48:53,522 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:48:55,519 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:48:57,531 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:48:59,528 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:49:01,540 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:49:03,537 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:49:05,534 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:49:07,546 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:49:09,543 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]
2017-06-22 19:49:11,556 withrottle.DeviceServer INFO - Received Name: Engine Driver 1ec4 [WiThrottleUIDeviceServer]

[Non-text portions of this message have been removed]



------------------------------------
Posted by: tventonukgateway@...
------------------------------------


------------------------------------

Yahoo Groups Links

Two Corrections:

a) CVs>256* are affected.
b) The problem only affects Program Track write packets, not reads, or Program on Main.

* The technical reason is that there is no CV0 (only CVs 1-1024), so CV1 actually has an address of 0 in the NMRA programming packet, CV256 actually has an address of 255 and CV1024 actually has an address of 1023.
--
Dave in Australia

There is an option 4 without any extra hardware requirements:

4. Read the decoder in Program Track mode, save the Roster Entry and use that to make changes in Program on Main mode.

Clarification:
- The NCE Power Pro reads CVs>256 correctly in Program Track mode.
- The NCE Power Pro cannot write CVs>256 correctly in Program Track mode.*
- The NCE Power Pro writes CVs>256 correctly in Program on Main mode.

* When writing in Program Track mode, all CV addresses are truncated to 8 bit equivalents (1-256). So a write to CV275 instead goes to CV19. So current JMRI versions will not try to write CVs>256 in Program Track mode. If you try with the Pro Cab in Program Track mode, you will corrupt CVs.
--
Dave in Australia

Thanks for the explanation Paul.

Tim