You removed the FTDI driver that came with OS X. Did you install the one from FTDI?

I did not! I take it I should do that?

Yes! Monome grids have a FTDI chip that facilitates communication, so a driver is needed.

Great! Thank you! My computer crashed and I freaked out mid first installation, tried it again and now it’s working great! Now just to figure out what I’m doing with this thing!

1 Like

Please don’t install the FTDI OEM driver on 10.13, it is known to cause problems with recent serialosc. The documentation explicitly mentions that:

https://monome.org/docs/setup/

Oh, my bad. Sorry for the confusion

to clarify, Apple has it’s own built-in FTDI driver. in various MacOS versions they have broken their own driver, hence sometime the OEM FTDI helped.

the wording of the Max 7 “if you haven’y installed serialosc, please do” is misleading. it does not check an installation. it’s simply reminding you to install it if you haven’t. run test_grid or similar to see if it’s working.

2 Likes

Hey! Did you sort it out? Yesterday I bring my first monome home and couldn’t get it to be recognized by my macbook pro.

@OliverMiller did you install serialosc? what patch are you running that’s not recognizing it? can you see serialosc in your activity monitor? are you running 10.13 macos? i need details in order to diagnose.

Nah, I have still yet to get this working after replug, all my other usb devices are fine, tried on two different aged MacBooks now, sure its something to do with the software

hi @tehn! thanks! Yes. I installed serialosc several times. I tried with every instance of MAX 7 package and also with Max4Live. Im running an apple macbook pro 2017 with 10.13.3 and a monome 128 walnut grid

Me too Im still looking for a solution

all seems to be good and clear. seems to connect consistently.
many thanks for your time and guidance.
bleep bloop whoop whoop

So I’m having issues with macOS 10.13.3 / varibright 128 / on an early 2015 macbook pro. My issue isn’t quite the same as everyone else posting here though - my issue is around monome patches crashing Max 7.3.4. Whenever I open one (ie: grid-test.maxpat, or meadowphysics, etc) it just beachballs out and I have to force quit. This only seems to occur while the grid is connected. All that said, I did manage to get grid-test to load once while the grid was connected, and it was visible in the dropdown, however no lights lit up when testing, so maybe there’s a communication issue as well.

Full disclaimer, it didn’t work before High Sierra either on this computer, so that may be something of a red herring. Apologies if I should have started a new thread.

Any guidance appreciated! I sold off my euro, but would like to hold on to the grid if I can get it working.

edit: I’ve tried with the stock driver and the ftdi one as suggested above.

Hey Guys, Still can’t get my GS64 working after replugging, sounds daft, but it really makes working with my grid unusable, I unplug my laptop a lot to take it to another room or work etc, so everytime i want to use my grid i need to reboot my mac.
Has anyone got the working, either with the new serials installer by other methods,
Id love to get some kind of workaround here.
Thanks

Alistair

Are you still updating your OS on your Mac?

No joy for me with High Sierra on a 2015 retina MacBook Pro and a 128 kit Grid. I did initially try updating the FTDI driver when I saw Monome Sum urned to Dingbats but then followed the steps in the doc setup to remove it and install serial osc. My grid isn’t recognised by Max 7 patches. Any help would be much appreciated.

with the FTDI removed, do you see the device appear in system prefs and/or by running ls -l /dev/tty.usb* in a terminal?

In a terminal I see:
crw-rw-rw- 1 root wheel 21, 2 4 May 06:55 /dev/tty.usbserial-A4039N7X

In the system profile under USB I see:

FT245R USB FIFO:
Product ID: 0x6001
Vendor ID: 0x0403 (Future Technology Devices International Limited)
Version: 6.00
Serial Number: A4039N7X
Speed: Up to 12 Mb/sec
Manufacturer: FTDI
Location ID: 0x14100000 / 2
Current Available (mA): 500
Current Required (mA): 90
Extra Operating Current (mA): 0

This serial number doesn’t match any of the monomes’ series, that’s why serialosc doesn’t detect it. Use software like FT_Prog to change the serial number in the FTDI EEPROM to something like “mk00000000”. It should work then.