Arduino uno and Mac

Thanks anyway Mike.

Mike, the Uno definitely has problems through a hub under 10.6.4. It also wants to add a new connection for every port you plug the thing into, which is sub-optimal. See my experiences here: http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1286033320/4

Thanks for the posts, guys. I updated the instructions to clarify about the network configuration options, and added a troubleshooting suggestion about not using a hub.

when I go into my network preferences it says "arduino uno is configured, but is not connected"

when I go into my network preferences it says "arduino uno is configured, but is not connected

OSX sees the UNO as a modem. Nothing in the network prefereces matter, except that it shows up as a device. "connected" in this sense refers to a modem bring connected to anther modem. NOT that the "Arduino is connected."

But then why isnt it uploading anything. my tx and rx flash but I get a avrude error

try using an external 9v power supply when uploading up till today i have been having the same type of problem. Let me know if it helps ya..

tired using a dc adapter while uploading and sitll got the same issue. Im really considering just sending it back

bubba5656: which version of the Arduino software are you using? What board do you have selected? What error do you get?

http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1287015838
here is my info. sounds like the op and I have close to the same problem

I have searched the internet for a week now and cant find the solution or even someone with the exact same problem as me and it is kind getting ridiculous is there anyone at arduino that can atleast tell me if it is my laptop or the arduino uno that is causing the issue

I have searched the internet for a week now and cant find the solution or even someone with the exact same problem as me and it is kind getting ridiculous is there anyone at arduino that can atleast tell me if it is my laptop or the arduino uno that is causing the issue

Keep in mind the new Uno board has only been out a couple of weeks and most of the more experianced users here probably haven't bought one yet. I'm sure it will all be resolved in time. I tend to never try and be an early adopter on anything technical, just been burned too many times.

Lefty

I am having the same problem. OS X 10.4.11. Macbook core2duo. Installed the new application and the USB driver. Bought four of these. Gonna try another one of them.

None of these four work.

FWIW, I have no problems with my uno on a 10.5.8 Mac Pro connected through the (powered) hub in my Dell Monitor. Nor through a generic unpowered hub connected to that hub.

None of these four work.

Then it is most likely to be something about your Mac rather than the boards. I was running V18 and got a UNO, upgraded to V20 and just plugged it in, no problem. I am running 10.6.4

Hello

First of all I'm sorry you're having there issues, we just wanted to let you know we're investigating this issue.

I believe there is a bug in the CDC driver shipped with certain versions of OSX Tiger that messes up the communication with Arduino.

CDC is a standard driver shipped with most modern operating systems that supports serial communication over USB. this is why the UNO doesn't require a driver.

we'll post more info when we're done investigating.

For what it's worth: I just received my Arduino Uno, and it's working fine with my MacBook Pro running 10.6.4. I'm willing to test stuff if that helps anyone.

I was able to get my Uno (x4) to work on Snow Leopard. No problems. Great improvement over the duemilanove. The Tiger laptop has been removed from the equation until there is an update or I change its OS.

Running OS X 10.4.11 and just got my new arduino ONU in the mail.

Sadly I got the same issue as Iofa and bubba5656. We all running osx 10.4.11
I tried fiddling around with the reset button an got a few sketches on the board, but I can't find the right moment to reset the board so it accepts the sketch. Maybe this had nothing to do with me pushing the reset button and I was lucky that everything went right.

I think we can narrow this problem down to osx 10.4.11 and maybe a wrong reset timing.