MacBook Air and LocoBuffer Success

My friend was finally able to install the USB drivers for his LocoBuffer-USB interface on his Mac. He spent several days and it took working with Dick Bronson at RR-CirKits and 24 messages on the jmriusers group to sort out the solution. Fortunately it was a simple solution that apparently was not a conflict with the Macbook hardware, the High Sierra operating system, nor the LocoBuffer-USB drivers. Here is his final description of what did the trick.

I went back and downloaded FTDI 2.4.2 again (these are the drivers). This time after installing I shut down and rebooted. Then I immediately went to System Pref->Security/Privacy->General and there it was……..A prompt that said the extension was not allowed and did I want to allow it to be installed….I clicked on “Allow”.

So it really came down to having to tell the Mac to allow the drivers to be installed. If you are interested you can read the whole series of posts on the jmriusers group on YahooGroups.com. This solution of course has implications for installing any new drivers on a Mac be they for LocoBuffer-USB or any other device.

It also shows what a valuable resource the jmriusers and other DCC groups can be. There are always a bunch of experts on these groups willing to give a helping hand when a situation like this arises. So if you use JMRI, use Digitrax NCE, or any other DCC system or decoder, there probably is a group just waiting to give you a hand and all you have to do is join the group. Give it a try.

2 comments

  • Larry, Have you heard if anyone using a PC product other than Mac Book, such a mobile device using the Android operating system of having same or similiar problems as you have described?

    • This really boiled down to knowing where in the Mac OSX preferences to complete the driver installation process. Most manufacturers are pretty good about giving detailed installation instructions so I am not sure if this was a problem caused by a new sequence of steps for the High Sierra OSX in the Mackbook or something else. These kinds of issues always seem to pop up when a major new OS is released—think about all the issues with Windows 10. If I remember correctly High Sierra was a major release that mandated a move up from 32 to 64 bit which killed some old software so I am surprised we aren’t hearing about more problems.