¿ªÔÆÌåÓý

  1. Jmriusers
  2. Messages
Expanded Topics Messages Polls
Date
Locked Re: Trouble loading PanelPro panels

 

Now that the holidays are in the rear view mirror I can return to dealing with the issue our club is seeing when a configuration that loads panels crashes JMRI PanelPro and requires Java to be killed with the task manager. We are running 4.18.? I have the log files.? What is the best way to get the requested log to y'all.
Dan Kubarych
ARHS
Locked Re: Issue with Engine Driver and ESU Mobile Control 2 #enginedriver

 

Matt,?
It was shipped with Android 6.0.1?

I'm trying to find the older install package and have reached out to ESU directly to see if they could provide it.?

Thank you for the information!
Cody


On Fri, Jan 3, 2020, 3:28 AM Matthew Harris <matthew.john.harris@...> wrote:
Cody,

Was your Father's MCII originally shipped with Android 6.0.1 or was this, somehow, updated?

Only the MCII relies on some custom modules added to the Android core by ESU in order to work with the knob and extra buttons.

In EngineDriver we rely on these modules exposed via the ESU API in order to work with these controls.

For reference, when attempting to update the Android system on my MCII throttle, it will not go further than the 4.1.1 that's already there.

Best regards,

Matt H

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

 

George It's only the DCC controlled turntable that needs it I think.?
Locked Re: Webserver not showing all the tracks of panelpro editor #webserver

 

See PR #

It occurred to me after I submitted this PR that there also wasn't any code to draw the track in the turntable¡­
I'm looking into it as we speak¡­ (ok, type¡­ ;-)
Locked Re: NCE USB Issue with RPi4 #rpi #nce #powercab

 

Dick, I followed your advice about hook up procedure and it worked fine. I¡¯m in the very early stages of learning this stuff but I did get control of my points from the laptop so I know the interface will talk to the layout.
Kind regards
Roy

On 2 Jan 2020, at 16:45, Roy Whitgrove via Groups.Io <r.whitgrove285@...> wrote:

?Thank you. ?
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
Locked Re: Test version 4.19.1 of JMRI/DecoderPro is available for download

 

¿ªÔÆÌåÓý

Hi Ken,

It turns out that I had a bad installation, but no warnings. I re-installed Java where I wanted it, and JMRI found it just fine. Thanks.

Peace,

Mike G.


On 1/3/2020 7:46 AM, KenGreenwood wrote:

Mike,

You need to install Java first, that way the paths are setup for other programs (like JMRI) to use.? So I would simply uninstall JMRI, then try reinstalling it.??

Hope that helps,
Ken G.

On Thu, Jan 2, 2020, 12:42 PM emrldsky <azMikeG@...> wrote:
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.
Locked Re: JMRI 4.18: After updating from 4.14, problem with linking to NCE PowerCab #4-18 #nce #powercab

 

Rai,

Its ironic that you would post this you are our first tester.

  1. Disconnect the coiled cable to the NCE Interface.
  2. Start Decoder Pro and go into preference and make sure that the version setting is set to 7.x.x and your baud is 19200 I'm guessing you have a newer Power Cab
  3. Start Decoder Pro again....
  4. Connect the coil cable back to the NCE USB Interface? Watch the lower left text it should go green after a while.
Inobu
  1. ?
Locked JMRI 4.18: After updating from 4.14, problem with linking to NCE PowerCab #4-18 #nce #powercab

 

On starting DecoderPro, linking with PowerCab is made briefly and then goes offline, or simply stays offline.

Pertinent facts:
Last time used when on 4.14, no problems.
Tried with two different PowerCabs and different cables.
Linking with NCE Command Station via serial interface is OK.
Using latest windows10 software and Interface Silab software.
Locked Re: NCE USB Issue with RPi4 #rpi #nce #powercab

 

Marc,

I did not post the correct link.. Thanks for letting me know.



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

 

Locked Re: Files in location not link Help requested Clarification #operationspro

 


This is a clarification to my post from Thursday January 2

I ran a session and terminated all the trains.? I shut the system down and then called up the system back up to make a change in a location file in the yard. Only? one of the 6 tracks in the yard showed up in the location.The other 5 yard tracks can not be seen. ? However, the cars still show up on the 5 missing yard tracks (that cannot be seen in the location section)? in the car file with cars on those tracks.? How can I relink the locations of the cars in the car file to the tracks under location in the yard?? Any suggestions in resolving this issue would be greatly appreciated.


I am using Windows 10 and used JRMI version 4.17.3? and then upgraded to 4.18 to see if that would solve the problem.? Any suggestions on how to relink the files would be appreciated.? The computer was also checked for viruses and malware and that is not an issue.

Thank you
Bob in Houston.
_._,_._,_
Locked Re: Test version 4.19.1 of JMRI/DecoderPro is available for download

 

Mike,

You need to install Java first, that way the paths are setup for other programs (like JMRI) to use.? So I would simply uninstall JMRI, then try reinstalling it.??

Hope that helps,
Ken G.

On Thu, Jan 2, 2020, 12:42 PM emrldsky <azMikeG@...> wrote:
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.
Locked Re: NCE USB Issue with RPi4 #rpi #nce #powercab

[email protected]
 

Link not working for me on two different Computers.

Marc
Locked Re: JMRI 4.18: Problem with adding Action to Section within Transit?

 

Bart
I cannot recreate this problem. After you do the "?Create New Action" and nothing seems to appear do alt+tab to get a list of the open windows and see if its listed (Add Action). If you are accessing the pi via vnc you will have to be in full screen mode for the Alt+tab to work.
Steve G.
Locked Re: Decoder Pro/Hornby Elite communication problem #hornby

 

No problem reading/writing decoder CV ( the supplied example came via Railmaster, I've done this for all my locos, one of which has a DCC23 the rest have the Bachman 36-558 decoders) thanks - Richard
Locked Re: Webserver not showing all the tracks of panelpro editor #webserver

 

Thanks Steve.
Locked Re: Issue with Engine Driver and ESU Mobile Control 2 #enginedriver

 

Cody,

Was your Father's MCII originally shipped with Android 6.0.1 or was this, somehow, updated?

Only the MCII relies on some custom modules added to the Android core by ESU in order to work with the knob and extra buttons.

In EngineDriver we rely on these modules exposed via the ESU API in order to work with these controls.

For reference, when attempting to update the Android system on my MCII throttle, it will not go further than the 4.1.1 that's already there.

Best regards,

Matt H
Locked Re: NCE USB Issue with RPi4 #rpi #nce #powercab

 

No words to describe it......

NCE Interface cycling with RPi-4 no a Laptop but a RPi-4.?



Inobu
Locked Re: How to download one decoder definition? #definitions

 

Bob,

On 3 Jan 2020, at 4:23 PM, Bob P <comm4rgp@...> wrote:

Can read and write most pages, but on new Tsunami 2 and Econami programming, the Function Map page appears stuck on writing the first change, of which all appear to be indexed CVs. Doesn't matter which function is changed, it appears unresponsive. A new topic which I'll search for guidance.
This almost certainly indicates you have an NCE Power Pro system.

Power Pro CV Limitations
==================

Due to a firmware issue, the NCE Power Pro is:
- Capable of reading values correctly from any CV in the range 1-1024** inclusive in Program Track mode.
- Incapable of writing values correctly to any CV>256 in Program Track mode. The wrong CV is written. For example, a write attempt to CV275 will instead reprogram CV19!
- Capable of writing values correctly from any CV in the range 1-1024** inclusive in Program on Main mode.

** If using the Pro Cab, you can only program CVs in the range 1-999 inclusive. You need software like JMRI DecoderPro to access the full 1-1024 range.

Notes:
1) This is unrelated to the concept of indexed CVs. Your NCE system is unaware of this concept, everything is just a CV. The indexed concept only exists in the decoder (and JMRI DecoderPro if you use it).

2) JMRI DecoderPro will not attempt to write to any CV>256 in Program Track mode. It protects your decoder from CV corruption.

3) JMRI DecoderPro is able to program CVs>256 in Program Track mode for ESU decoders only. This is because ESU has provided an in-decoder workaround to deal with DCC systems having this problem and JMRI automatically uses this workaround when needed.

4) The original Tsunami decoders are unaffected by this problem. For Tsunami2 and Econami, any attempt to write CVs in Program Track Mode on the Function Map, Sound, Alt Sound Levels, and DDE panes will be blocked by JMRI, but you will need to restart JMRI to continue (I'd like to fix that but it's not easy and I don't have the time).

5) The JMRI workaround with affected decoders is to read and save the roster entry in Program Track, close and reopen in Program on Main mode when changing affected panes.

6) This problem has nothing to do with PTB-100 or any programming track booster. That is related to programming track hardware limitations and not related to the CV>256 firmware issue. It is an unrelated separate question.
Locked Re: NCE USB Issue with RPi4 #rpi #nce #powercab

 

¿ªÔÆÌåÓý

Inubo and Marcus,

On 3 Jan 2020, at 2:09 PM, Inobu One via Groups.Io <one2beros@...> wrote:

This is what the log doesn't reveal. The NCE USB Interface has a 20 second lock up cycle. During that time the NCE USB Interface seems to be inaccessible.?
Any connection although good will fail. I think this is where I interjected the power cycle to start the NCE USB Interface again. I noticed that Decoder Pro
aligned itself verses Panel Pro did not.

Thanks for the logs.

I've performed some timing tests using both Mac and Ubuntu to test the power-up delay of the NCE USB and Power Cab.

1) The NCE USB power up cycle.

I made sure I had the following JMRI windows opening automatically and non-overlapping:
- NCE Command Monitor with Show Raw Data and Show Timestamps enabled.
- Send NCE Command, with Binary Enabled and AA entered into the Command Field.
- Single CV Programmer, with mode set to Direct.

After starting JMRI successfully, I turned off the 240V power switch supplying the PCP and waited for all NCE components to be thoroughly shut down.

While watching the seconds on the computer clock, I simultaneously flicked the 240V power on with one hand and with the other I clicked on the Send button in the Send NCE Command window.

The NCE Command Monitor log showed the AA command being sent within the same second I had used on the clock and the 07 03 07 response being returned in less than 10 milliseconds.

This was fully repeatable, even with the Power Cab being unplugged from the PCP.
So there is very little power-up delay within the NCE USB itself, less than 1 second.

2) The combined NCE USB and Power Cab power up cycle.

Before performing the following tests I navigated to the Setup Command Station menu item on the Power Cab throttle, and went through to the "PROCAB POWER UP SECONDS(1-30):" item (available on V1.65 firmware and above) and made sure it was set to "01" (for obvious reasons).

While watching the seconds on the computer clock, I flicked the 240V power on with one hand, waited a few seconds and with the other I clicked on the Read CV button in the Simple Programmer window.

I found I had to wait about 5 seconds between "flick" and "click" in order to get a reliable read of CV 1 in the attached decoder.

3) The time between JMRI startup and Version Report in the Log.

In all cases (with Profile Selector Delay disabled), the interval between " JMRI log " and "NCE EPROM revision = 7.3.7" was less than 5 seconds.

I would expect that interval to be considerably greater with an RPi.

My Conclusions and Speculations

There is no evidence to support the assertion that "The NCE USB Interface has a 20 second lock up cycle."

Some other factor(s) must be in play with Larry and Inubo's RPi situations.

In most cases (but maybe not with the RPi setup) the user would normally power up the NCE hardware well before starting JMRI. If there is simultaneous power-up it would be well worth a user checking the?"PROCAB POWER UP SECONDS(1-30):" setting. (I have no idea how long an RPi takes to boot up, but I'd assume at least 5 seconds).
?
My speculations about possible factors in the situation include:
- The RPi USB behaviour after the JMRI code sets up a connection and tells the driver to ?reset the Baud Rate of the CP2102 chip on the NCE USB. (We've not observed any problem of this sort with Windows/Mac/Ubuntu.)
- The slower processing speed of the RPi.
- The reported difference in behaviour between PanelPro and DecoderPro could be related to Startup Items (or slightly different code paths in JMRI).
- One factor that was mentioned was that the "workaround" is a one-off rather than every time. If that's the case, something happening in JMRI code at first start with the premade image (possibly coupled to processor speed) or to the Auto Configuration used by Steve (although I thought this still occurred with?Auto Configuration disabled. But a lot of this information has been buried in interpretation and speculation rather than simple clear reporting of test conditions and results.


Dave in Australia
73141 - 73160 of 240199