Re: NCE USB Issue with RPi4 #rpi #nce #powercab

[email protected]

To add to what Dick points out.

Current release of JMRI will throw an error message window at you (Error Inititializing DecoderPro)? and refuse to start? if the required USB device is not plugged in.
This is valid for NCE, Digitrax, any Command Station that uses USB/Serial as the interface.

If the USB device is plugged in to the computer, the Initialize error will not show but the Command Station will not respond if it is not powered up.?

So everything must be powered up; Computer, USB, Command Station before you start JMRI (PanelPro or DecoderPro).

Marc

Re: Test version 4.19.1 of JMRI/DecoderPro is available for download

#167639

A new computer running Windows 10. I installed JMRI, then installed Java in its default location. Tried to start DecoderPro.

Got the message "Java not found!". Where does JMRI "expect" to find Java, or, better yet, can I tell JMRI where to look for it?

Peace,

Mike G.

Re: Changing Car Type #operationspro

#167638

I believe you are missing my point. I am running a small terminal layout and as such will from time to time receive a specialty load for a specific industry..I am not interested in establishing a schedule. I was looking for a tool that would help make it easier to accomplish this action. I will keep searching the program
Jerry

Re: calling dispatched from script

#167637

开云体育

Got it, thanks.

Ken

On 1/1/2020 12:58 PM, Steve_G wrote:

Show quoted text

The one before last. "Y is the penultimate letter of the alphabet"

Re: NCE USB Issue with RPi4 #rpi #nce #powercab

#167636

Thank you. ?

Show quoted text

On 2 Jan 2020, at 14:10, dick bronson via Groups.Io <dick@...> wrote:

?Roy,

There is just one big rule, always have the USB unit running before you start JMRI. If you do not, then JMRI can not start due to a missing COM port. It is a Windows thing. Most folks just leave the USB adapter plugged into the computer all the time.

There is also a small rule. Start the command station before you start JMRI. If not then JMRI can not connect to it until you power it on.

Both of the above should be self evident, but only to those that understand that: a) an application can only find a com port during its start up processing, not after it is running; b) if an application is running with a COM port number, then Windows will choose a different COM port number for a device being connected. This is the reason that JMRI will stop working if the USB is unplugged and plugged in again. If you ever do that, then you need to completely start over to restore operation. (stop JMRI, unplug the USB, plug in the USB, start JMRI)

Dick :)

On 1/2/2020 8:02 AM, Roy Whitgrove wrote:
As an absolute beginner I have followed this thread with great interest and I did initially have a problem with downloading the drivers, however my son in law who is conversant with that sort of stuff finally got me connected ok.  What I would like to know is in your opinion which is the best way to hook up the usb interface. Do I power up the NCE Power Cab with the interface connected but the usb not connected to my laptop. Then start Panel Pro then Decoder Pro and finally connect the usb or which way is best? After all the controversy over this beating that sometimes there is a better procedure to follow. I sorry if this is over simplistic question but as I said I am very new and very old and just starting out with JMRI
Kind regards and all the best for the New Year.
Roy Whitgrove uk
On 1 Jan 2020, at 19:01, Dave Heap <dgheap@...> wrote:?Inobu,

I've taken a look at the whole thread and now see things that have been buried beneath your speculation about the way NCE USB communications work. Four things stand out to me:

1) A complete absence of JMRI system log transcripts from either you or Larry. We need to see those in both the working and non-working cases.

2) An "Unable to connect on ttyxxxx" message is not pointing to an NCE communications issue but an operating system level issue with the USB port, unrelated to the way NCE does communications.

3) The statements "You only have to do this on the initial install", "(Leave the Power Cab unconnected)" and "Start JMRI Panel Pro. (It will try to configure itself and you will have to change some settings.)". This could point towards some issue in what I understand to be an auto-configuration script in Steve's RPi distributions.

4) A total lack of reporting of the behaviour of two important NCE USB status indicators; the USB and CAB indicator LEDs. These provide vital troubleshooting information to both Ken and I, particularly when accompanied by system logs.

We need to put aside your speculation about how NCE communications work, your speculation that "This seems to be an inherent problem with the Power Cab as well", any suggestion that users should adopt your quite clumsy "workaround" as the solution and you, me, Ken and Steve work cooperatively to solve this problem properly.

Inobu, the ball is in your court to provide logs of both the non-working and working cases, along with accompanying information about the NCE Status LEDs' behaviour. You have the hardware and knowledge to perform these tests so please help us solve this cooperatively.

Larry, if you can provide any logs as well, they'd be much appreciated.

Dave in Australia

Re: Decoder Pro/Hornby Elite communication problem #hornby

#167635

PPS -? I must be getting old, I missed the other query above. When I unplug the USB lead, COM2 disappears from device manager then re-appears when I plug it back in.

Re: Layout Editor: issue connecting two turnouts #layouteditor

#167634

If I decide to "try" it I'll make it 100% "opt-in" (meaning unless you opt-in you'll never know it's there).
I've been working with the developer of RailModeller Pro on his JMRI export and one of the "features" it has is "real" (inches, feet, mm or kilometer) units…
(FYI: his layout editor uses a library of commercial tracks parts with the exact dimensions to match. So WYSIWYG. In theory exporting to JMRI would give you an exact scale representation of your layout.)
Just wondered if it ("real" units) would be of interest to anyone using JMRI.
Thanks for the feedback.

DB-HV-1969 Changes in xml files

#167633

Just updated to 4.18. Modeling German modern day in N. Have been setting up Signal Masts with the DB-HV-1969. Discovered that I could no longer set a "dark" signal aspect from ?the Signal Mast table. Started up 4.16 and "dark" was back. Compared the xml files for DB-HV-1969 in 4.18 vs 4.16 and found that indeed "dark" was missing in 4.18. Any particular reason "dark" has gone dark?

I have set up some Logix that set signals aspects including "dark" and this change affects present operations and future plans. I replaced the DB-HV-1969 xml files in 4.18 with those from 4.16 and things seem to be fine.?

Any enlightening concerning this change would be appreciated.

Gary

When responding to help, address needs

#167632

Just a thought to maybe focus messages better for people needing help.
When someone says "I bought this and tried to install but...", I think people who want to help should answer his/her concerns rather than suggesting they buy something else.? Not to say that that might be the best route to Joy, but it doesn't seem to be helpful to the original poster.
Also, anecdotal evidence is often misleading ("My thing works this way, so I recommend it."). Often too many variables differ to be a usable comparison without in depth review.
I've been at the end of my rope sometimes and asked for help. Being lectured that I should have bought NCE instead of Digitrax is not helpful.
Happy New Year everyone.??
Phil in awesome Santa Rosa Beach (vacation)

Re: Webserver not showing all the tracks of panelpro editor #webserver

#167631

On Thu, Jan 2, 2020 at 01:24 AM, SwissChris wrote:

display not matching panelpro especially in the areas of turntables.

SwissChris,
Please post your panel file (and any custom items needed for it) and I'll create an issue. Or you can create an issue here:?and include the same items directly in the issue.
My guess is that the client-side panel code needs to be enhanced to handle your turntables.
--SteveT

Re: Engine Driver panel turnout operation problem #enginedriver

#167630

Graeme,?
How did you "upgrade" JMRI? And what operating system are you running JMRI on?
Also, this problem is coming from the JMRI webserver, not EngineDriver, so please browse to it using a browser on your JMRI computer and see if you get the same error(s).
--SteveT

Re: NCE USB Issue with RPi4 #rpi #nce #powercab

#167629

Roy,

There is just one big rule, always have the USB unit running before you start JMRI. If you do not, then JMRI can not start due to a missing COM port. It is a Windows thing. Most folks just leave the USB adapter plugged into the computer all the time.

There is also a small rule. Start the command station before you start JMRI. If not then JMRI can not connect to it until you power it on.

Both of the above should be self evident, but only to those that understand that: a) an application can only find a com port during its start up processing, not after it is running; b) if an application is running with a COM port number, then Windows will choose a different COM port number for a device being connected. This is the reason that JMRI will stop working if the USB is unplugged and plugged in again. If you ever do that, then you need to completely start over to restore operation. (stop JMRI, unplug the USB, plug in the USB, start JMRI)

Dick :)

Show quoted text

On 1/2/2020 8:02 AM, Roy Whitgrove wrote:
As an absolute beginner I have followed this thread with great interest and I did initially have a problem with downloading the drivers, however my son in law who is conversant with that sort of stuff finally got me connected ok.  What I would like to know is in your opinion which is the best way to hook up the usb interface. Do I power up the NCE Power Cab with the interface connected but the usb not connected to my laptop. Then start Panel Pro then Decoder Pro and finally connect the usb or which way is best? After all the controversy over this beating that sometimes there is a better procedure to follow. I sorry if this is over simplistic question but as I said I am very new and very old and just starting out with JMRI
Kind regards and all the best for the New Year.
Roy Whitgrove uk
On 1 Jan 2020, at 19:01, Dave Heap <dgheap@...> wrote:

?Inobu,

I've taken a look at the whole thread and now see things that have been buried beneath your speculation about the way NCE USB communications work. Four things stand out to me:

1) A complete absence of JMRI system log transcripts from either you or Larry. We need to see those in both the working and non-working cases.

2) An "Unable to connect on ttyxxxx" message is not pointing to an NCE communications issue but an operating system level issue with the USB port, unrelated to the way NCE does communications.

3) The statements "You only have to do this on the initial install", "(Leave the Power Cab unconnected)" and "Start JMRI Panel Pro. (It will try to configure itself and you will have to change some settings.)". This could point towards some issue in what I understand to be an auto-configuration script in Steve's RPi distributions.

4) A total lack of reporting of the behaviour of two important NCE USB status indicators; the USB and CAB indicator LEDs. These provide vital troubleshooting information to both Ken and I, particularly when accompanied by system logs.

We need to put aside your speculation about how NCE communications work, your speculation that "This seems to be an inherent problem with the Power Cab as well", any suggestion that users should adopt your quite clumsy "workaround" as the solution and you, me, Ken and Steve work cooperatively to solve this problem properly.

Inobu, the ball is in your court to provide logs of both the non-working and working cases, along with accompanying information about the NCE Status LEDs' behaviour. You have the hardware and knowledge to perform these tests so please help us solve this cooperatively.

Larry, if you can provide any logs as well, they'd be much appreciated.

Dave in Australia

Re: WiThrottle - control panels #paneleditor #withrottle

#167628

On Thu, Jan 2, 2020 at 03:40 AM, Brian Jackson wrote:

Do you know if the?"slipturnouticon" issue in the webserver is being worked on for a future release or should I raise it as an issue?

Please create an issue for it here:?
Include the panel file, your icon folder, and your screenshots. I'd also include a link back to this thread as a reference for the problem.

Thanks!
? --SteveT

Re: Ops - Using the Alternate Track #operationspro

#167627

One of the issues Jeff ran into when using the alternate track feature, was using the planned pickups for the spur that also needed an alternate track.? The combination of the alternate track feature and planned pickups caused the program to not move cars from the alternate to the spur once cars on the spur were pulled.? The latest test release now warns that the two feature should not be used together.

Dan

Engine Driver panel turnout operation problem #enginedriver

#167626

Rpi 3
DCC++
JMRI 4.18 from 4.16

Previously running JMRI 4.16
Engine Driver v2.24.93 on Samsung Galaxy S2
Panel startup with Webserver and WiThrottle Server

Engine Driver loads, panel loads and turnouts operate correctly when selected via the panel

2020-01-02 22:46:24,740 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Creating new WiThrottle DeviceServer(socket) on port 12090, waiting for incoming connection... [WiThrottleServer]

2020-01-02 22:46:24,744 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:46:25,371 consisttool.ConsistFile? ? ? ? ? ? ? ?INFO? - Consist file does not exist.? One will be created if necessary. [WebServer-43]

2020-01-02 22:46:30,816 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:46:36,776 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:46:42,786 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:46:48,784 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:46:54,790 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:47:00,794 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:47:03,887 json.JsonNamedBeanSocketService? ? ? ?WARN? - get request for turnout made with user name "Turnout #1"; should use system name [WebServer-45]

2020-01-02 22:47:03,895 json.JsonNamedBeanSocketService? ? ? ?WARN? - get request for turnout made with user name "Turnout #2"; should use system name [WebServer-45]

2020-01-02 22:47:03,919 json.JsonNamedBeanSocketService? ? ? ?WARN? - get request for turnout made with user name "Turnout #3"; should use system name [WebServer-45]

2020-01-02 22:47:03,932 json.JsonNamedBeanSocketService? ? ? ?WARN? - get request for turnout made with user name "Turnout #4"; should use system name [WebServer-45]

2020-01-02 22:47:03,947 json.JsonNamedBeanSocketService? ? ? ?WARN? - get request for turnout made with user name "Turnout #6"; should use system name [WebServer-45]

2020-01-02 22:47:03,961 json.JsonNamedBeanSocketService? ? ? ?WARN? - get request for turnout made with user name "Turnout #7"; should use system name [WebServer-45]

2020-01-02 22:47:03,973 json.JsonNamedBeanSocketService? ? ? ?WARN? - get request for turnout made with user name "Turnout #5"; should use system name [WebServer-45]

2020-01-02 22:47:06,798 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:47:13,252 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:47:18,807 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:47:24,813 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:47:30,819 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:47:36,823 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:47:42,827 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

2020-01-02 22:47:43,325 json.JsonNamedBeanSocketService? ? ? ?WARN? - post request for turnout made with user name "Turnout #1"; should use system name [WebServer-46]

2020-01-02 22:47:48,835 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-1]

Upgrade to JMRI v18?
Engine Driver loads and Panel loads but turnouts do not operate correctly when selected via the panel (reloading the Engine Driver panel fixes it until the next turnout selection)?

2020-01-02 22:40:08,861 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-2]

2020-01-02 22:40:14,862 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-2]

2020-01-02 22:41:19,728 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Creating new WiThrottle DeviceServer(socket) on port 12090, waiting for incoming connection... [WiThrottleServer]

2020-01-02 22:41:19,732 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver tablet [DeviceServer-3]

2020-01-02 22:41:21,104 jmri.InstanceManager? ? ? ? ? ? ? ? ? ERROR - Exception creating auto-default object for jmri.server.json.schema.JsonSchemaServiceCache [WebServer-44]

java.lang.reflect.InvocationTargetException

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:422)

at jmri.InstanceManager.getInstance(InstanceManager.java:289)

at jmri.InstanceManager.getNullableDefault(InstanceManager.java:233)

at jmri.InstanceManager.getDefault(InstanceManager.java:204)

at jmri.server.json.JsonConnection.<init>(JsonConnection.java:22)

at jmri.server.json.JsonWebSocket.onOpen(JsonWebSocket.java:35)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at org.eclipse.jetty.websocket.common.events.annotated.CallableMethod.call(CallableMethod.java:71)

at org.eclipse.jetty.websocket.common.events.JettyAnnotatedEventDriver.onConnect(JettyAnnotatedEventDriver.java:148)

at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.openSession(AbstractEventDriver.java:233)

at org.eclipse.jetty.websocket.common.WebSocketSession.open(WebSocketSession.java:504)

at org.eclipse.jetty.websocket.common.WebSocketSession.onOpened(WebSocketSession.java:433)

at org.eclipse.jetty.io.AbstractConnection.onOpen(AbstractConnection.java:200)

at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onOpen(AbstractWebSocketConnection.java:566)

at org.eclipse.jetty.io.AbstractEndPoint.upgrade(AbstractEndPoint.java:432)

at org.eclipse.jetty.server.HttpConnection.onCompleted(HttpConnection.java:376)

at org.eclipse.jetty.server.HttpChannel.onCompleted(HttpChannel.java:651)

at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:459)

at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)

at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279)

at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:104)

at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124)

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:247)

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produce(EatWhatYouKill.java:140)

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)

at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:243)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:679)

at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:597)

at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.NoSuchMethodError: com.networknt.schema.SchemaValidatorsConfig.setUriMappings(Ljava/util/Map;)V

at jmri.server.json.schema.JsonSchemaServiceCache.<init>(JsonSchemaServiceCache.java:50)

... 35 more

2020-01-02 22:41:21,122 json.JsonWebSocket? ? ? ? ? ? ? ? ? ? ERROR - Unanticipated error Required nonnull default for jmri.server.json.schema.JsonSchemaServiceCache does not exist. [WebServer-44]

java.lang.NullPointerException: Required nonnull default for jmri.server.json.schema.JsonSchemaServiceCache does not exist.

at jmri.InstanceManager.getDefault(InstanceManager.java:206)