#7

it is almost certainly not dead. you’re experiencing the same Mac OS upgrade nightmare that many others have.

my quickest suggestion: try upgrading to 10.12 if you can, and read through these:

http://llllllll.co/search?q=AppleFTDI

#8

Now I have tried on IMac of my friend and the my little jewel 40h works very well on OS X 10.11.4 with serialosc 1.4.
While I have two MacBook Pro I7 OS X 10.11.6 and max7.
I don’t know, what it is happen, because on my setup Just 12 hours ago it seems broken while now on IMac it works very well.

#10

It’s not magically broken. You updated to the bleeding edge and are suffering the consequences so it seems.

#11

thank you, I understand, but so Apple has created us a big mess, and we can’t work with our monome. the apple is poisoned!

#12

not really. see tehn’s advise above to actually update to the “bleeding edge”.

yes osx+ftdi is sadly a bit wonky these days.

@dariocasillo there are some things to check/try in various threads, like this: SerialOSC not updating on monome connect/disconnect

1 Like
#13

i always wait a while after apple releases ANYTHING, i guess it goes back to my pro-tools fear days

#14

@dariocasillo is on 10.11 (me too), which was released one and a half year ago, so I don’t get your comment…

#15

I’m sorry i got confused with another thread, i was reading regarding someone on Sierra, my bad.

#16

i do recall having issues with Max7. I cleaned out the whole thing and installed via the package manager and it cleared things up.

#17

In this morning I deleted all those monome patches that I had installed in Max7. Then I update to Osx Sierra and there was an improvement: if I plug and unplug the monome is always intercepted, something that was previously not pissibile with El Capitan at that time I had to restart the computer. But despite this improvement the monome does not work, does not respond and does not send messages, and then the pads are always in the dark.

#18

what’s the output from the max window?
You uninstalled the serialosc manually?
if not try that. manually delete the serialosc file from max folder, /Users/Documents/Max7/…
and then install the monome package from the package manager in Max7

#19

MAX CONSOLE
binding to port 12006
binding to port 12288
binding to port 13288
udpreceiver: binding to port 12006
binding to port 12288
udpreceiver: binding to port 13289

monome is connected but the light is dark
it doesn’t control the patch

I have uninstalled manually the serialosc and after I have installed Monome file from Package manager
Now I have installed serialosc and the monome is connected but it doesn’t work .

#20

to ask again, can you confirm that you got this working (lights and keys) on another computer at some point?

#21

Also did you reboot after the uninstallation?
And what computer is it working on, didn’t you say it works on a friends laptop? or do you have/know someone with a mac that might let you try it on their computer? i think if it works on another person’s computer we can rule out if there is a defective unit/part

#22

Yes, Yesterday it worked on the imac of a friend but then I returned home I tried on my mac and monome continued to act as I described.
today I have tried on the imac of my friend and it did not work like yesterday.
no lights today

#23

can you take a photo of the unit and post it? i want to confirm the edition or if it’s a kit/etc.

#24

I do not think that this monome is a device kit.
While I’m sure the tilt sensor that is seen is a device upgrade kit.
The device is “m40h0205”.
It is second hand.
I bought it from Latvia users, some years ago.

IMG_20170301_075644_HDR.jpg3328×2496 1.89 MB
1488351788971..jpg3120×4160 1.37 MB

#25

Today
I have installed serialosc and monome home on another IMac 10.11.6.
I have installed serialosc and gridhowto on MacBook Pro 10.10 with Max7.
Well, dear colleagues I am a little sad, because after so many years of adventures my little jewel has decided to remain in the dark.
In all two cases the monome has been recognized by the GridhowTo or Monome Home MAXPatches but does not receive and when I plug in USB socket and when I hit the pads it does not turn on the lights. I have also tried with monomeserial and it has been successfully recognized but when I press the monomeserial “test mode” do not pad is light-on. Perhaps lack the firmware, the sketch, I do not know. How can you help me I can reload ATMega with my programmer to use with Arduino microcontrollers? Where can I get the sketch?

#26

do you get a startup animation pattern when you power the unit? what you wrote was unclear.

that’s certainly a real 40h, with the accel upgrade.

you need a programmer to reflash, and it’s hard to know that’s the actual problem.

do you still see tty.usbserial*** is your /dev/ folder?

#27

When I power the unit I don’t get animation pattern.
When I type in terminal ls -lrt /dev
I read this:
2 Mar 00:40 cu.usbserial-m40h0205
2 Mar 00:41 tty.usbserial-m40h0205

See this photo,
Also if the device has been detected and the TESTMODE is on the light of monome is in the dark.
What I can to resolve this problem?
can you help me?
Thanks