¿ªÔÆÌåÓý

Locked JMRI serial failure macOS Sonoma #mac-os


 

Not sure of the actual time frame but I believe this problem may have shown up with a recent update to macOS Sonoma 14.7. ?My FTDI serial to USB interface is no longer working for the serial connection to an NCE Power Pro system.
It is available to be selected in the Panel Pro>Preferences>Connections window and is selected but the connection fails after I save the preferences and restart JMRI. ?
?
?I tried updating macOS to 14.7.1, no fix. ?
Updated JMRI from 5.6 to 5.8, no fix
Updated Java to v11.0.15, no fix.
Updated JMRI to v5.95+, no fix?
Reset NCE Command station to factory defaults and changed backup battery
?
?
iMac 2020
3.3 GHz 6-Core Intel Core i5
AMD Radeon Pro 5300 4 GB
8 GB 2667 MHz DDR4
?
NCE PH PRO 5A
Using NCE Serial connection @ 9600 baud. ?
Command station EPROM Mar 1 2007C
?
Tested FTDI interface on Win8 laptop and it works fine. ?
?
Any thoughts?

?

?
--
Dave in Hamilton, ON.


 

Dave,

Go through the steps at?

What version of the FTDI driver are you using?

Dave Sand


----- Original message -----
From: Dave Burroughs <ve3ljw@...>
Subject: [jmriusers] JMRI serial failure macOS Sonoma #mac-os
Date: Tuesday, November 05, 2024 11:12 AM

Not sure of the actual time frame but I believe this problem may have shown up with a recent update to macOS Sonoma 14.7. ?My FTDI serial to USB interface is no longer working for the serial connection to an NCE Power Pro system.
It is available to be selected in the Panel Pro>Preferences>Connections window and is selected but the connection fails after I save the preferences and restart JMRI. ?
?
?I tried updating macOS to 14.7.1, no fix. ?
Updated JMRI from 5.6 to 5.8, no fix
Updated Java to v11.0.15, no fix.
Updated JMRI to v5.95+, no fix?
Reset NCE Command station to factory defaults and changed backup battery
?
?
iMac 2020
3.3 GHz 6-Core Intel Core i5
AMD Radeon Pro 5300 4 GB
8 GB 2667 MHz DDR4
?
NCE PH PRO 5A
Using NCE Serial connection @ 9600 baud. ?
Command station EPROM Mar 1 2007C
?
Tested FTDI interface on Win8 laptop and it works fine. ?
?
Any thoughts?

?

?
--
Dave in Hamilton, ON.


 

Dave,?
?
It says FTDI-FT232RL on the interface. ?
?
FT232R USB UART:
? Product ID: ? ?0x6001
? Vendor ID: ? ?0x0403 ?(Future Technology Devices International Limited)
? Version: ? ?6.00
? Serial Number: ? ?A10LKLC6
? Speed: ? ?Up to 12 Mb/s
? Manufacturer: ? ?FTDI
? Location ID: ? ?0x14110000 / 11
? Current Available (mA): ? ?500
? Current Required (mA): ? ?90
? Extra Operating Current (mA): ? ?0
--
Dave in Hamilton, ON.


 

Dave,

I am running Sequoia but I have a dim memory of a USB issue.

In Mac System Settings go to "Privacy & Security". ?Find "Allow accessories to connect". ?I use "Automatically When Unlocked". ?The "Ask..." options did not always work.

I assume that you are using the FTDI 1.5.0 driver extension instead of the old 2.4.4 kernel extension.

Dave Sand


----- Original message -----
From: Dave Burroughs <ve3ljw@...>
Subject: Re: [jmriusers] JMRI serial failure macOS Sonoma #mac-os
Date: Tuesday, November 05, 2024 11:54 AM

Dave,?
?
It says FTDI-FT232RL on the interface. ?
?
FT232R USB UART:
? Product ID: ? ?0x6001
? Vendor ID: ? ?0x0403 ?(Future Technology Devices International Limited)
? Version: ? ?6.00
? Serial Number: ? ?A10LKLC6
? Speed: ? ?Up to 12 Mb/s
? Manufacturer: ? ?FTDI
? Location ID: ? ?0x14110000 / 11
? Current Available (mA): ? ?500
? Current Required (mA): ? ?90
? Extra Operating Current (mA): ? ?0
--
Dave in Hamilton, ON.


 

Dave,?
?
I cannot find the option to "Allow accessories to connect" on my Intel Mac. ?It appears that option is used with Apple Silicon processors.?
?
I have installed FTDI 1.5.0 driver and restarted. ?
I tried to uninstall the kernel extension and it will not allow me to dp that. ?
?
Interesting though, I have an amateur radio program called SKCClogger and the FTDI adapter works fine on it but I am not getting it to work on JMRI Panel Pro or Decoder Pro. ?I can select it in the configuration panel, save and restart JMRI but it still will not work. ?
?
The fact that the FTDI adapter works with my amateur radio program suggests the software drivers are installed and working. ?
Just for giggles, I installed JMRI on my old 2011 MacBook Pro and the FTDI adapter works fine with High Sierra. ?
?
Doing the elimination process, it appears that JMRI is ?not playing nicely with my FTDI adapter. ?
?
--
Dave in Hamilton, ON.


 

Dave,?
?
This is somewhat embarrassing. ?I just started my iMac in safe mode, shut down and restarted.?
The FTDI interface appears to be working properly now with JMRI. ?
?
Thanks for your assistance. ?I will keep an eye on it and make sure it keeps working. ?
--
Dave in Hamilton, ON.


 

Dave,

I keep forgetting about Safe mode. ?Apparently there was some old data in a cache that needed to be removed.

Dave Sand



----- Original message -----
From: Dave Burroughs <ve3ljw@...>
Subject: Re: [jmriusers] JMRI serial failure macOS Sonoma #mac-os
Date: Tuesday, November 05, 2024 2:50 PM

Dave,?
?
This is somewhat embarrassing. ?I just started my iMac in safe mode, shut down and restarted.?
The FTDI interface appears to be working properly now with JMRI. ?
?
Thanks for your assistance. ?I will keep an eye on it and make sure it keeps working. ?
--
Dave in Hamilton, ON.


 

Well, that didn't last very long. ?Just opened up JMRI and once again, back to the problem of JMRI not able to use the FTDI USB to serial adapter. ?I tried to boot into safe twice and it is still failing. ?
--
Dave in Hamilton, ON.


 

Dave,

What was the macOS version before 14.7?

After starting and getting the connection error go to "Help -> System Console". ?Use the "Copy to clipboard" button and paste in a reply.

Dave Sand


----- Original message -----
From: Dave Burroughs <ve3ljw@...>
Subject: Re: [jmriusers] JMRI serial failure macOS Sonoma #mac-os
Date: Tuesday, November 05, 2024 9:45 PM

Well, that didn't last very long. ?Just opened up JMRI and once again, back to the problem of JMRI not able to use the FTDI USB to serial adapter. ?I tried to boot into safe twice and it is still failing. ?
--
Dave in Hamilton, ON.


 

I had an issue with a USB to serial adapter dongle on my Mac with C/MRI devices.? It would send data to the SMINI's, and the SMINI would respond, both as indicated by LED activity, but JMRI complained something about an "invalid command" received (don't recall exact wording).? This was with an adapter that worked on a Windows 10 machine to interface to Ham radios via CHIRP and radio manufacturer's software.? The solution for me was to purchase an adapter that is KNOWN to have a legitimate FTDI chip in it.? In case you aren't aware, the FTDI chip is WIDELY counterfeited.? On Amazon, search on "GearMo Windows 7. 8 and 10 Compatible USB Seri8al Adapter FTDI Chip RS232 DB-9 920k with TX/RX LED".
My Mac is a Macbook Pro, Intel Core 9 running Mac OSX Sonoma.
?
Good hunting!
?
--John.


 

Thanks John and Dave,?
?
The light finally came on here. ?I have JMRI and several amateur radio programs that use a serial interface. ?When I used one of the amateur radio programs and went back to use JMRI after I was finished, at times, I had a connection problem. ?It was intermittent but I am not sure which radio program was causing the issue due to the length of time between using JMRI. ?Sometimes, it is weeks or longer depending on how often I operate my model railroad.?
?
I purchased another FTDI USB to serial interface which is now used exclusively with JMRI and connectivity to my layout on an NCE Power Pro system. ?Since I did that, I have not had any further interaction connection issues. ? ?
--
Dave in Hamilton, ON.


 

Hi Dave: ?Glad you found a solution. The following is tangentially JMRI related so any further discussion we can take offline. I know your issue is with the Mac, but I also had some weirdness with the Baofeng radio interface on Windows. Windows would ¡°help me out by updating the driver, rendering the Baofeng interface cable inoperable. The solution is to locate an older driver and force install the older driver. I also have a Yaesu radio and switching between interface cables brings out the problem with Windows updating the driver. Perhaps Mac has a similar issue.
?
¡ª´³´Ç³ó²Ô.