I just got my monome. i installed the port drivers (they installed fine
and i restarted). i'm running max 4.6. i'm using serialIO and Monome
serial...they both see the 40h.  i plug the monome in usb and i have a
set pattern of buttons lite on the left hand side (by the usb). they
will not go out and new buttons will not light. i ran the test patch but
it does nothing to the monome. Am i missing something?
the computer can see the monome as a usb device.  i ran mlr and balrog
neither function or affect the lighted pattern on the monome. Its the
same pattern each time i plug and unplug it...need some help.
thanks

i'm using a macbook intel
and OSX 10.4.9

try this on a clean boot:

run serialio

you should see "found m40h0300" or something

then run _40h_test.mxb from the base patches


pressing should now give you some results.


if this doesn't work, there could be some possibility that the wrong 
ftdi driver was installed? be sure to install the intel version.

i re-downloaded the intel driver and re-installed. on a fresh boot i ran 
serialIO.
serialIO did find the 40h and let me run the test patch. i could turn 
off the pattern with the toggle engaged. ran balron it also worked. quit 
serialIO, removed usb. then reattached usb, same pattern on left side. 
ran monome serial, it listed 40h by serial number as a device. ran test 
patch and no response, ran balron no response...every time i plug in the 
usb its the same pattern, is that normal?

Yeah... you should always see those lights when you plug in. If you 
don't then it's broken.


I think there needs to be some basic info for use related to the monome. 
A quick start and basic facts sheet would be a great help to new users.

so balron works with serialio, but not monome serial? is it just that 
the OSC prefix is wrong? (has balron been updated to work with /40h as a 
default, rather than /box?)

if so, try change the box in the monomeserial window that says /40h on 
startup to /box

if this is what's wrong, relax. it sounds like there's nothing wrong 
with your box. like nick said, if you've got the bootup light pattern, 
it's probably ok.

ok, i changed monomeserial from /40h to /box and balron works...so it 
definitely doesn't feel like a problem with the box. thanks.

also good to know about the bootup light pattern... so easy to get hung 
up on the little things.

i'll be playing around with it today, and hopefully can smooth out all 
the connections...

thanks again for the replies.

yes, seems like it's all working.

also apologies for the confusion.

presently we're in a state of flux with communication schemes, etc. 
serialio vs. monomeserial vs. (all of the xp methods) create some 
ambiguity. we're planning on having everything unified again.

alright,
  i'm still learning my way around here. i got balron to work, and 
64step and flip seems to be working. i'm still having trouble with mlr. 
i tried running serialIO and monome serial. for mlr  i'm using the Max 
patch and the new standAlone collective.

side note: does anyone know if its more stable to use Max runtime with a 
small app. or to use a full patch in Max/MSP itself?

i guess my question now is what is the ideal setup for mlr?

i prefer using monome serial, over serialIO

is monome serial in midi or osc mode? and is osc set for "/box" or 
"/40h"

i've tried as may combos as i can think up. the best result are with 
monome serial in osc set to /box.

i set mlr with some samples turn up the volume and hit buttons and 
nothing happens...
the only two buttons that light up and turn off are the fifth and sixth 
buttons from the left on the top row.
nothing happens in mlr, they just light on and off.
i'm not sure which osc objects need to be in Max? maybe that's it...

and once again it's an intel mac with 10.4.9

any help would be great...

forgive me if you've already tried this, but i think you need to click 
on the DAC button on the left to turn the audio engine on. (and turn up 
the main output volume on the slider right above that)

as for monomeserial, most of the early patches are written using the 
/box prefix, so using /40h as a prefix won't do anything (the patches 
won't be getting any messages. they're looking for /box prefix and 
nothing else, so when you press a button and it goes to the /40h prefix, 
they don't care).

setting monomeSerial to midi mode is probably good for using the 40h 
with software sound engines without having any other routing software 
open.

Hey thanks kevin.

It wasn't the DAC, well kinda..
I was hitting the DAC button in mlr, but for some reason it wasn't 
starting the DSP.
Once i started the DSP manually then mlr started working.

hopefully now i'm dialed in...
thanks again

sorry, this isnt related to this thread really, but:

brian, in monome serial and serialio it shows the serial number (build 
number) of the box?  how do you get that info from the box?  just 
curious....

in osx and linux, the serial number shows up included in the dev 
filename which lives in /dev:

usb.serial-m40h0000

or similar. so it's easy to extract from the file system.

i'm sure there's a way to do it in xp, i have no idea how.

what do you mean by the dev filename?  something thats on your 
harddrive, or in the ftdi files?  or, do you the filesystem via the 
serialport?  in windows, serial devices are accessed usually via 
streams, in the same manner as you analyze any binary file (stream of 
bytes).  is that what you meant?  im sorry, just really curious.

ok, i found it using Control Panel, now i gotta find it via my code!

in linux/unix, everything is a file. it's actually very nice.

yes, that makes a bit more sense.  one thing i hate about windows is the 
seperation between the registry, file system, control panel, etc.

hey, I have the exact same problem, the lights are permanently stuck in 
the monome pattern they dont flash, move or anything. I had it running 
on my macbook then it just got 'stuck'. I followed your 
directions.....reinstalled the intel driver.....
my computer reads the monome, but when i open _40h_test.mxb nothing 
happens. The patch also looks buggy as some of the buttons are not 
there. There is also a huge list of error:#M:no such object printed out. 
Also Mapd doesnt work either which is what I really need, and I 
understand your actually not supposed to use serialo or monome serial 
while using mapd. any ideas????

the startup pattern fades out when the monome gets its first received 
message, so your computer isn't sending it any messages.  try a 
different usb port, it could be that you always have to use it on the 
port you installed it on.  maybe try a complete uninstall and reinstall 
again.

I keep wondering what the startup pattern is patterned after, I can't 
make heads or tails of it.

binary count, 1-8

ok, makes sense, I just dont get what you mean by midi port, isnt the 40 
h communicate with OSC???

ooops, monday....  I meant USB.  I'll go fix that.

> binary count, 1-8
AAAHAAA!!!  thanks for that. :)

I tried both ports, and I just installed serialo, monome serial, mapd, 
and the ftdi driver on a new partition today.....Ill try again....

hmmm ANYTIME you plug in the 40h you should see some lights along one 
side light up in a seemingly random pattern, then they fade out after a 
few seconds.

OK, your problem has to be that you need more solder on the jumpers, 
maybe you have a chip in backwards, I believe it's something larger, 
more obvious.  find the pics of the kit, stare at them, stare at your 
board, check every inch, it's something easy to see.

good luck!!  it's all about calm, patience and persistence.

correction:

the 40h startup pattern fades after the device enumerates.

make sure your ftdi driver install is correct.

interesting, what does enumerate mean?  it gets registered by the OS as 
a device and gets a USB ID?

i dont think a chip is in backwards, i didnt build this myself, But I 
should open this up and check for soder??? how do I know if the ftdi 
installed correctly???

it's assembled fine probably since you're getting power and everything. 
i'm sure the driver is either not installed or the wrong version is 
installed.


enumerate, yeah you got it. the pattern turns off when the system 
acknowledges and activates the device. try plugging your 40h in while 
your CPU is getting hit hard, and the pattern will stay on a little 
longer...

is christian using a kit?  I'd be surprised if he had to 'open it up' to 
check for solder if he made a kit.  if that's the case DO NOT open it 
up, did you reboot your computer after install?