Thanks. I am using USB A to USB B cable into NCE USB adapter.

?

I will verify Java version.

?

SB5 Wouter.

?

I’m going to try some of the other device types to see if that makes a difference.

?

Well I just tried use Power Cab (like it says) even though I have an SB5 and the message didn’t appear again so I am going to try and read a locomotive.

?

Very strange as under Windows 10 it did work as SB5.

?

Bill S,

?

This message happens with the ID from the connection, like 6.2.1, doesn’t agree with your settings. Please post the console log from your startup (before making any changes) so I can confirm that code made the right decision. What I am looking for is the line that looks like this:

?

17:53:35,155 jmri.jmrix.nce.NceConnectionStatus??? INFO? - NCE: NCE EPROM revision = 6.2.1 [AWT-EventQueue-0]

The value after the equals is the trigger. Knowing what you had set in the preferences and matching to that code will figure this out.

?

I’ll also need to know which jumpers you set on the NCE USB to confirm it worked correctly or not.

?

-Ken Cameron, Member JMRI Dev Team

?

?

Bill S,

?

I confirmed by looking at the code that I need to see the system log of that startup to give you a correct explanation. But the general statement is the code is seeing a version number coming back from the interface that doesn’t match with the settings in the connection. But I’m thinking the message in the popup window may be misleading as currently worded.

?

-Ken Cameron, Member JMRI Dev Team

?

Bill S,

?

Looking deeper into the code, I see I need to know more things. I’ll recap:

1. System console so I can see:
1. Version of JMRI
2. Version returned by the NCE USB
3. The logged error message
2. NCE command station firmware version id
1. That’s either 1.28something or 1.65something.

?

But so far it is looking like you may not have the right jumper settings in the NCE USB and the version ID it is giving doesn’t match what it should be for the SB5 system. But depending on which jumper settings, the baud rate may also need to change to match what it expects.

?

But with the details above, I can guide the right answers.

?

-Ken Cameron, Member JMRI Dev Team

?

?

?

Ken,

?

I am currently using 5.11.3, but this problem existed on the prior released version as well.

?

I have a “new” session log attached here for your review. My message log goes back to 2020 so it is much bigger.

?

Thanks,

Bill

?

Bill,

?

This log looks normal. I don’t see it showing any issue with opening the port, getting the id from the NCE USB. But what did you have set in the connection window at this time?

?

I’m presuming you have both a PowerCab and a SB5 from what you said. The recommended setup for that combination would be using two profiles. One for the PowerCab as the command station so you have a programming track. The second is with the SB5 as the command station so you can move around with the PowerCab as a normal throttle.

?

But to do that, I suggest you make a change to the NCE USB. I would use it with all jumpers in place. This is the ‘all systems’ setting. That in turn would mean both profiles are set for 19,200 baud. This way you don’t have to change the jumpers between the two systems.

?

But there is a table of the id’s used by the NCE USB and the code cross checks that value with the command station selection. The message you posted would say the selection you had in the connection settings didn’t match the id value returned by the NCE USB.

?

I take it that this last run didn’t give you any popup?

?

-Ken Cameron, Member JMRI Dev Team

?

?

Bill,

?

That log didn’t have the other run. The session.log gets reset every time you open JMRI. The messages.log is the last ### runs up a meg of file space.

?

I think what would be best is a post of the messages.log so I see the history and a snap of the connection profile showing all the settings.

?

-Ken Cameron, Member JMRI Dev Team

?

?

Here you go Ken, everything from today.

?

I will re-install the jumpers and tweak the Advanced settings to 19,200 vs 9,600 baud.

?

Bill

?

Bill,

?

I see three startups in the file. The first and third seem to be fine, but the second one has the problem. What was the settings in the connection for each of the three? To me, it looks like the 1^st and 3^rd was using a profile set for the PowerCab but the 2^nd was set for using the SB5. But the log says these were all the same profile. That’s why I was asking about the connection settings for each startup of JMRI to match what was different.

?

-Ken Cameron, Member JMRI Dev Team

?

?

Yes, first and third were PowerCab and middle was SB5. All same profile, just changed the preferences.

?

I put the jumpers back on the board, set it to 19,200 and it appears to be happier now.

?

Bill,

?

You should be seeing the id 7.3.7 in the logs. That says ‘all systems’ so JMRI lets that match any of the command stations.

?

-Ken Cameron, Member JMRI Dev Team

?

?

This is in the log:

?

2025-03-09T08:34:45,387 nce.NceConnectionStatus?????????????? INFO? - NCE: NCE EPROM revision = 7.3.0 [AWT-EventQueue-0]

2025-03-09T08:34:45,389 nce.NceConnectionStatus?????????????? ERROR - NCE: System Connection is incorrect, detected USB connected to a PowerCab [AWT-EventQueue-0]

?

Bill

Bill S,

?

The 7.3.0 in the log says you have no jumpers on the NCE USB. That code tells JMRI that the system is a PowerCab and it has the old 1.28 firmware.. The error message says that’s not what you are telling the system connection.

?

If you have two profiles, one for a PowerCab so you can use it to have a programming track, another profile for an SB5, and both have the 1.65 firmware, you would do best to set all jumpers on the NCE USB. Then use 19,200 baud for the connection. You should see it report as 7.3.7 in the log which means all systems and both profiles would work correctly with their respective settings.

?

With a SB5 system it is important to set the right command station so JMRI know that only ops mode programming will work.

?

-Ken Cameron, Member JMRI Dev Team

?

?