开云体育

  1. Jmriusers
  2. Topics

Just Upgraded to Decoder Pro 5.10 and Java 17, now NCE Power Pro and JMRI won't talk #nce

 

?Hi,? ?I'm new here, mostly because my Decoder Pro and NCE system(s) have gotten along well for years through various computers and upgrades...now I've hit a wall, so any insights appreciated.?
?
? Here's the hardware basics.?
?
? ?NCE Power Pro 9 pin serial port command stations. Have two, tried two and same result.?
?
? ? NCE latest Chip installed in both command stations, "March 22, 2021"?
?
? ? Computer: Lenovo Pentium Silver N6000? 4.0 GB ram.? Windows 11.? ?Using Com Port 3.??
?
? ? Here's the situation, shifting Java and JMRI versions? mentioned? as follows.?
?
? ? For about two years, I've been using this set up with JMRI 5.2 and Java 11.? Aside from occasional hiccups, a pretty solid arrangement.?
?
? ? Now I just received two locomotives with Soundtraxx Blunami decoders.? Went to create a new locomotive file in Decoder Pro? it wouldn't download the data.? Figured, newest decoders...time for an upgrade to the latest version from JMRI.?
?
? ? ?Went to upgrade to version 5.10.? Says while it would work better with Java 17, would also be expected to work with Java 11.? Decided to play it safe and stick with Java 11 for now.?
? ? ? ? ?When bringing up Decoder Pro I received the dreaded red words.? "Service Mode Programmer NCE Is Offline"? - " Operations Mode Programmer NCE is Offline"? Despite everything? which follows, this has not changed.? ?
?
? ? ? ?Next step, ok let's try Java 17--installed Java 17.? No change.??
?
? ? ? ?Then I took a risk, and installed JMRI 5.11.4, which is still under evaluation.? Again. No Change.? The NCE and JMRI are still not on speaking terms.?
?
? ? ? ?Now, before anyone asks, the USB to Serial port cable came to me directly from NCE several years ago and had just been working.? When I plug and unplug, it makes that booping sound, which means it's seeing something, but no communications.? And besides, again, it was just working fine.??
?
? ? ? ? Here's one area I suspect may be a problem, which is the Com Port 3 driver, which had not been an issue under JMRI 5.2 and Java 11 on my Windows 11 laptop.??
?
? ? ? ?This is what shows up under driver files for "USB to Serial Cable (COM3): ? C:\WINDOWS\System32\serenup.sys (along with) C:\WINDOWS\System32\DRIVERS\SVK9PL64? ?And of course, Device Manager says everything is working properly.?
?
? ? ? ? In poring over the NCE, as well as JMRI trouble shooting pages and doing other on? line searching, it appears there are more drivers that don't show up on my machine.? But those posts go back many years to much earlier versions of both JMRI and JAVA.? I honestly cannot say there was anything more on my machine prior to this,? because it all worked.
?
? ? ? ?If there is a new driver I need which would work with the newest setup, let me know...along with a few hints on how to install it.??
?
? ? ? ?Anyway, thanks in advance.? I hope this isn't one of those obvious things that I've missed...but I'm about 6 or 7 hours into this already and going crazy.? I've tried to keep this note to the essentials, but have more data available, but all the boxes I can open appear to be checked correctly within Decoder Pro, such as port, baud rate etc.? But I can pull it back up if anyone thinks that would help.? ?
?
Glenn?
?
? ? ? ??
?
? ? ?
?
 

开云体育

Glenn,

?

Have you checked over on the NCE-DCC user group on 开云体育?? You are a member there under this e-mail address.

?

The crew over there has provided great support over the years for NCE – JMRI connectivity issues.

?

Best regards,

?

Steve

?

Steve Haas

Snoqualmie, WA

?
 

Different versions of JMRI don't require different device drivers. That's strictly an issue between your interface device and the OS you're plugging it into. For example, my interface device uses a Microsoft-supplied driver that hasn't changed since Win200 or so. Many different versions of Java and JMRI between then and now have lived happily with that device/driver combination.
?
But the interface device itself could fail in such a manner that it still makes the beep/boop, but doesn't communicate. If you're sure you're using the correct COM port, the next thing I'd try is a new USB-Serial adapter.
?
HTH,
Steve
"Breezlys"
 

Check JMRI Prefs and connection tab see if the com port has changed ?

Jim K


On Monday, March 17, 2025 at 12:54:06 PM EDT, Breezlys via groups.io <livinthelife@...> wrote:


Different versions of JMRI don't require different device drivers. That's strictly an issue between your interface device and the OS you're plugging it into. For example, my interface device uses a Microsoft-supplied driver that hasn't changed since Win200 or so. Many different versions of Java and JMRI between then and now have lived happily with that device/driver combination.
?
But the interface device itself could fail in such a manner that it still makes the beep/boop, but doesn't communicate. If you're sure you're using the correct COM port, the next thing I'd try is a new USB-Serial adapter.
?
HTH,
Steve
"Breezlys"
 

开云体育

Steve, ?

? ?Yes. That’s the next step. It got pretty late last night by the time I posted, so of course, woke up in the middle of the night going why not post this to the NCE group! ?
? ?Your note is a good reminder.?

Thanks

Glenn?



On Mar 17, 2025, at 9:54?AM, Breezlys via groups.io <livinthelife@...> wrote:

?
Different versions of JMRI don't require different device drivers. That's strictly an issue between your interface device and the OS you're plugging it into. For example, my interface device uses a Microsoft-supplied driver that hasn't changed since Win200 or so. Many different versions of Java and JMRI between then and now have lived happily with that device/driver combination.
?
But the interface device itself could fail in such a manner that it still makes the beep/boop, but doesn't communicate. If you're sure you're using the correct COM port, the next thing I'd try is a new USB-Serial adapter.
?
HTH,
Steve
"Breezlys"

1 - 5 of 5