Maxuino problems with serial port

Mar 27, 2010 at 7:57pm

Maxuino problems with serial port

Hi can anyone help me with this problem please?
I’ve recently bought an Arduino board for use with Max, I fired it up with Max for the first time yesterday using maxunio. worked perfectly!
Today however I fired it up again and Max no longer recognises the serial port ‘serial: specified port not available’, nothing has changed though I really cant get my head around it, everything is exactly the same.

any help would be greatly appreciated

thanks

#49379
Mar 28, 2010 at 2:22am

you have the diecimila, or the mega, or the teeny [it think thats what they are]. i had a problem for a bit, the same issue.
i just reset and then loaded back on the firmata standard again, ran the program and was back up, no problems now.
although every now and again, it does not pair up with maxuino, so i close max, un-plug arduino and then plug back in and start the program again…

#177422
Apr 3, 2010 at 4:22pm

thanks yeh, I found that mine never works on the first attempt which is quite annoying, but thats sorted it thankyou.

#177423
Apr 4, 2010 at 4:47pm

there is also, arduino2max which is also good. it does only have 6 analog and 13 digital, but is really good…

#177424
Apr 6, 2010 at 10:20pm

it sounds like a problem with the USB to serial driver, not Max or Maxuino. If you could let me know your full setup I can make sure maxuino isnt causing the problem. Also, check out the new release….

#177425
Apr 27, 2010 at 2:48am

I’ve been running three maxuino objects with three USB boards to read from 38 sensors (two Megas and a Due) but have been having some pretty tough problems.

The main one is that when I’ve got all three boards returning data (using analogIns $1 1 for all numbers) it lags up really badly. One maxuino is fine, and two is okay, but three really ruins it.

The other is just a question about the patch: why do you use [qmetro 1] to bang the serial object? If I understand correctly (not entirely likely) qmetro runs on the lower-level queue, which only polls every 2 ms by default. I just deleted all the qmetro objects (saving it as maxuino-acs) and poll all three serial objects with a single qmetro set to 20 ms. This is good enough for my purposes, and I’m hoping it reduces the lag.

I’m also having a tough time getting it all to start up automatically without having to press extra buttons. This is just important because it’s going to be in a sound installation with no monitor, and I don’t want them to have to hook up a monitor and hit a few buttons every day. So, I guess a future feature request would be a bang out the right outlet when the serial object is finished connecting–that way I could send some messages automatically to maxuino.

Okay, lots of requests–sorry about that. Most of the time it’s working great though! Good work, and I look forward to future versions.

#177426
Apr 27, 2010 at 2:54am

I’ve been running three maxuino objects with three USB boards to read from 38 sensors (two Megas and a Due) but have been having some pretty tough problems.

The main one is that when I’ve got all three boards returning data (using analogIns $1 1 for all numbers) it lags up really badly. One maxuino is fine, and two is okay, but three really ruins it.

The other is just a question about the patch: why do you use [qmetro 1] to bang the serial object? If I understand correctly (not entirely likely) qmetro runs on the lower-level queue, which only polls every 2 ms by default. I just deleted all the qmetro objects (saving it as maxuino-acs) and poll all three serial objects with a single qmetro set to 20 ms. This is good enough for my purposes, and I’m hoping it reduces the lag.

I’m also having a tough time getting it all to start up automatically without having to press extra buttons. This is just important because it’s going to be in a sound installation with no monitor, and I don’t want them to have to hook up a monitor and hit a few buttons every day. So, I guess a future feature request would be a bang out the right outlet when the serial object is finished connecting–that way I could send some messages automatically to maxuino.

Okay, lots of requests–sorry about that. Most of the time it’s working great though! Good work, and I look forward to future versions.

#177427

You must be logged in to reply to this topic.