monome

i'm keen to see progress with this too..... any one doing anything yet? or are we just waiting on stability in serialosc first?

Hi,

I was in the IRC room this morning, I had mentioned that to the best of my knowledge serialosc currently does not support arduinomes under linux. visinin informed me that the latest release from github had added arduinome support. I plan on testing this when I get home.

Update...

Someone else in the IRC room said they were already running an arduinome under serialosc, sorry I can't recall their name right now.

artfwo is the one running an arduinome with serialosc.

I tested this last night, serialosc detected my arduinome.

ooh! must have a bash.

No luck on this side.

Plugging in my Arduinome (ArduinomeFirmware 3.2)

[73139.328024] usb 4-2: new full speed USB device using uhci_hcd and address 5
[73139.529834] cdc_acm 4-2:1.0: ttyACM0: USB ACM device

Running serialosc and plugging in Arduinome results in no output from serialosc

Any ideas?

@stelio:
linux?

@visinin yeah, and trying to run "sudo monomeserial -d /dev/ttyACM0" yields the response "failed to open /dev/ttyACM0"

the most likely cause is that you don't have the serial number of your device flashed to something that libmonome understands. it relies on that information to pick which protocol to use for your device.

if you can, try flashing it to "a40h-0001" or something of that form.

That makes sense, but i've built my Arduinome using the Arduino Uno which doesn't have the FTDI chip, this makes changing the serial number tricky (actually not sure how to do this?).

I've opted to detect any attached device as an arduinome, probably not a good idea but should work for testing purposes.

in src/private/devices.h, added:
{"%d", "40h", {8, 8}, "arduinome" , QUIRK_57600_BAUD},

Now "sudo monomeserial -d /dev/ttyACM0", yields the following:

initialized device 649383233313519032E1 at /dev/ttyACM0, which is 8x8
running with prefix /monome

and i can startup serialosc:

serialosc [649383233313519032E1]: connected, server running on port 16953

But none of the libmonome examples seem to work, most likely because they're using hard coded details? if( !(monome = monome_open("osc.udp://127.0.0.1:8080/life", "8000")) ) return EXIT_FAILURE;

or am i missing something else?

yeah you'll need to make sure your OSC server is running on port 8080 for those examples. you can do that in the serialosc config file for it (.config/serialosc/{serial}.conf).

those examples don't work with the monomeserial program anymore, unfortunately.

What does it all meeaaan?!

But really, what does it mean? I'm running XP SP3 with a StarFire 128 Arduinome. No idea on firmware versions or anything of the sort, but if needed I will look into it.

Even with the new Win update, I still am not totally sure if I have everything installed correctly. Does anyone have an adruino running on SOSC?

Hey guys,

We just updated our instructions on changing the serial numbers with the new arduinos (based on the info found here on monome), and also got it working with serialosc. See this post:

http://post.monome.org/comments.php?DiscussionID=10201&page=1#Item_36

Hope that helps

Just made some progress running arduinome (FW 3.2) with serialosc on windows vista.

0. - flashed my arduinome serial to a40h-0011
- ran serialosc
- ran monome_test 4.5 (serialosc version)
- result: arduinome NOT recognized

1. - repaired my bonjour service (which is zeroconf on windows) by clicking onto control panel > software > bonjour > modify > repair ( found an error in the event log stating that bonjour client and server versions mismatched )
- restarted serialosc
- ran monome_test 4.5
- result: arduinome NOT recognized
- BUT: hitting ctrl+m in max showed some erros: cannot resolve zeroconf objects ....

2. - found this http://post.monome.org/comments.php?DiscussionID=12026
- and found http://docs.monome.org/doku.php?id=app:serialosc > additional files > max5 for windows: zeroconf externals
- followed the link, downloaded, extracted, and moved the files from /dist/win32/zeroconf_20110226_win32 to C:\Program Files\Cycling '74\Max 5.0\Cycling '74\max-externals
- restarted serialosc
- ran monome_test 4.5
- no more errors in max window (zeroconf objects resolved)
- result: my arduinome SHOWS up in the serialosc connect dropdown!
- clicking on connect shows a connection to my arduinome!

- BUT: no leds light up, no button presses are recognized

Any hints?

which arduino do you have?

Its a Arduino Diecimilia.

by the way, I do have to correct myself.

With serialosc and monome_test 4.5 under windows vista, I can see some LED light up, but they seem to be pretty random or do have a pattern, I cannot recognize.

I cannot see any button reaction in monome_test, but I can see the data LED on the arduinome light up both on button press and button release, so there seems to be some kind of reaction.

running arduinomeserial the arduinome seems to be completely functional, all buttons and leds react in monome_test 4.4 as expected.

I'd be happy to help testing if needed (can test on vista, gentoo and snow leopard)

suit4, I have the exact same response when trying to run my arduinome under windows vista. Random lights and button presses not randomly registering. Last I heard, arduinomes still aren't supported under windows and there is a problem visinin knows about but hasn't had time to fix yet. My arduinome works just fine under OSX for the record. It's a starfire arduinome with the standard 168 chip on the logic boards (not the UNO).

Am I correct with this visinin or have I missed something?

Hi Ambassador Hobbes, good to hear that there is probably work in progress regarding that issue.

Do you have further information where those problems come from?
Is it serialosc itself or more likely from the arduinome firmware?

Pretty sure it's something in serialosc that needs to be changed, maybe visinin will chime in here. Since it works fine on OSX and in windows it can see the arduinome devices but not communicate correctly, I'd be surprised if anything is wrong with the firmware.

hmm, sounds quite logical ... and I already read somewhere here about a bug in serialosc and windows.

so, I'll practice patience while thinking about an enclosure 8)

oh yep, i remember now. on windows, serialosc doesn't set the correct baud rate for arduinome devices. i don't have a windows box around right now or i would have pushed out a fix already, sorry :(

if you know how to fix it, I would love to test it ...

I would happily help test too if you need it.

*moved*