#42

@alanza Always! :wink:

@tehn no dice… installed v2.4.2 (which I believe I have done before) from here https://www.ftdichip.com/Drivers/VCP.htm and no changes in response from the commands above.

I don’t think it work previously and eventually I ended up deleted it to get @neauoire’s rack/linn instruments working previously Pre-Mojave upgrade. Or maybe it was back during early days of norns and I was having trouble connecting to norns through serial before I made the switch to ssh/ftp.

#43

UPDATE: ignore everything I said. On a lark, restarted one last time I ran the command again and got:

> /dev/tty.usbserial-m1000539

… holy cow it works… on everything Rack, Linn, MarkEats, Max and VCV. :exploding_head:

Thank you VERY much for your continued 5 star support and nurturing. I’m thrilled to belong to this community. :heart:

4 Likes
#44

Don’t know if it warrants a bump in this thread, but in downloading the ftdi driver, my MacBook wouldn’t start again and I had to reboot from a time machine backup.

So, as of now, is it recommended to only use apple’s include ftdi driver with serialosc to get a monome working on 10.14?

#45

here’s the basic troubleshooting script I use for FTDI help requests:

  1. On your 10.14 device, open Activity Monitor and search ‘serialosc’ – you should see something like this:

    ?name=inline-772553309.png1600×296
    ​
    If not, then serialosc is not installed: https://monome.org/docs/setup/

  2. Once you confirm serialosc is installed, please connect the device and execute ls -lrt /dev/tty.usb* ​in terminal. You should see something like this:

    ?name=inline2077157953.png1092×146
    ​
    Please share the output you get from that command.

  3. Confirm what FTDI drivers are on your system by executing ls /System/Library/Extensions | grep FTDI ​in terminal.

  4. If you’ve gotten to this point and things are still not working, try this in terminal:
    launchctl unload /Library/LaunchAgents/org.monome.serialosc.plist ​
    and then: launchctl load /Library/LaunchAgents/org.monome.serialosc.plist
    This will kickstart serialosc. Open up [arc-test OR grid-test].maxpat, make sure the Max console is visible (shift+CMD+M) and plug in your device. You should see some messages in the Max console and you should be able to connect.

  5. If things are still wonky, please try installing the OEM FTDI driver. Here’s a link: https://www.ftdichip.com/Drivers/VCP/MacOSX/FTDIUSBSerialDriver_v2_4_2.dmg

if you get all the way to step 5 and no success, please email help@monome.org <333

3 Likes
#46

A post was merged into an existing topic: Apple/Mac issues: hardware, firmware, interfaces, etc

#47

Thank you so much for responding! Still no luck, up to step 5, and before I install the FTDI Driver here’s what I’ve done:

Here’s my setup:
OSX 10.14.5, Macbook Pro 2012, x1 USB 2.0, x1 USB 3.0, SerialOSC 1.4.1, Max 8, “series” 64 monome

I have serialosc 1.4.1 installed along with Apple’s FTDI drivers after the reboot, and the result from the terminal was this:

crw-rw-rw- 1 root wheel 18, 10 Oct 29 13:06 /dev/tty.usbserial-m64_0525

Serialosc seems to be updating when I plug and unplug the monome64.

Still nothing in the devices dropdown in either apps or Max patches, so onto downloading the FTDIUSBSerialDriver_v2_4_2.dmg.

#49

I got prompt help from the folks here and at Cycling 74’ .

My problem ended up being related to me changing my network settings in order to create an ad-hoc server for touchOSC (in lieu of a monome). After setting the network preferences (under wifi) back to default, serialosc began to work!

I’ve never gotten to use a monome before now so I’m jacked:)

1 Like
#50

so glad it worked out! thanks for closing the loop here :slight_smile: