MacBook Pro, JMRI & SPROG II v3 - Obsolescence?

[richierich]

A bit of a simple question, after messing about and getting nowhere.

 

I have the following set up:-

 

• MacBook Pro (mid 2012) running Mac OS 10.15.7
• JMRI Decoder Pro 5.6
• SPROG II v3

 

Is this setup subject to obsolescence issues?

 

 

[Nigelcliffe]

All stuff gets obsolete eventually.    What's the specific issue ?  

 

This page says your MacOS version is fine for now.  

https://www.jmri.org/install/MacOSX.shtml

 

There is a bug in JMRI 5.6 which affects some MacOS versions with Sprog.   It is fixed in test release 5.7.1  

 

 

[Crosland]

If you ask on the SPROG specific group https://groups.io/g/sprog-dcc/topics someone with direct experience may be able to help. I don't, unfortunately, have access to Mac hardware.

 

As Nigel says, it's best to state the specific issue, if there is one.

 

Andrew Crosland

sprog-dcc.co.uk

 

[richierich]

On 24/03/2024 at 17:30, Nigelcliffe said:

All stuff gets obsolete eventually.    What's the specific issue ?  

 

This page says your MacOS version is fine for now.  

https://www.jmri.org/install/MacOSX.shtml

 

There is a bug in JMRI 5.6 which affects some MacOS versions with Sprog.   It is fixed in test release 5.7.1  

 

 

I cannot get JMRI to communicate with a DCC fitted loco on a programming track.

 

The MacBook Pro can see the Sprog on the USB bus. But JMRI doesn’t doesn’t send commands. 

 

The version of JMRI is 5.6 so maybe that is the issue ?
 

 

[Nigelcliffe]

56 minutes ago, richierich said:

I cannot get JMRI to communicate with a DCC fitted loco on a programming track.

 

The MacBook Pro can see the Sprog on the USB bus. But JMRI doesn’t doesn’t send commands. 

 

The version of JMRI is 5.6 so maybe that is the issue ?
 

 

Impossible for me to diagnose from the information provided.     However, you could try JMRI 5.7.x  (the "test releases") which would rule out the bug you report.  

 

There are other things to check:    
Look in "preferences/defaults" to see that buttons look correctly "ticked". 

That you are trying to "program" and not "edit" the decoder information ("edit" is editing the locally stored file, not doing anything to the decoder)

 

And probably other setup issues.     And then can move on to trying commands manually to see if hardware is working.   

[Crosland]

Did you set the JMRI connection preference to SPROG or SPROG Command Station? You need the former for programming on the programming track.

 

Use the firmware version tool in the SPROG menu of JMRI. Does it report the SPROG version? If so, that confirms the USB connection is good. If not, do you have the correct port selected ion the JMRI connection preferences?

 

What did you do to determine JMRI isn't sending any commands to the SPROG?

[Chris F]

This is exactly the setup I use and it all runs along just fine.  Check your connection preference and communication port as Crosland suggests; there's no shame in forgetting what goes where.;

[richierich]

I've installed test release 5.7.5 and the communication to the SPROG is fine.

 

The issue I have found is the direction control on the throttle doesn't work.