'Preferred' Programmatic Environment?

Greetings,

I started out programming my Arduino on OSX but ran into some 'workaround' issues with a separate Rainbowduino. The more and more disconnects I had, the more frustrated I got because I don't want to debug OSX, I want to work on my Arduino! I'm worried that the deeper into Arduinos (and their offshoots), the more problems like this I'll end up dealing with.

Can anyone tell me if there is a 'preferred' environment people have found that takes the hassle out of dealing with the OS and allows you to just get tinkering? Windows? Ubuntu? Debian? Should I be using FTDI as much as possible just to maintain some consistency across units? Am I over-optimizing this because I had one problem with one board?

I have a feeling the answer is going to be "Clone boards all react differently" and that OS really isn't a consideration...but I thought I would ask. I have an older laptop I could repurpose into a 'hackerstation' (or even a Raspberry Pi) but I wanted to consult with you all first.

Thanks in advance!

I don't understand the question.

Do you want to program Arduino or derivatives?

If the derivative board makes use of a utility only found on a particular operating system, I guess you are limited to that operating system for that board.

Not necessarily?

Most software starts out targeting a specific environment. Java clouds things up with its 'platform independence' but I was wondering if there is any sort of consensus one way or another as to what sort of set up tends to deliver the fewest headaches.

I know derivatives are going to be bring their own problems individually, but I figured I would ask if one setup seems to have less problems than another.

I know my question is vague at best. :frowning:

I've been using WinVista since summerish 2010, updating IDEs as they come out. Using 1.0.5 now. Wife has Win7, not sure which IDE. Little struggle getting UnoR3 driver installed, I had no such problem. Generally use FTDI interfaced boards, or offboard FTDI module connected to a header.
No Apple/Linux experience.
So based on that - I'd say go with Windows.

Just the answer that gives me that little push I needed. I'll mimic CrossRoads and go down the FTDI route to hopefully help iron out any little differences that might pop up communicatively-speaking.

Thanks!

The 8U2/16U2 route might be good for some projects -I haven't done anything where I needed another device to be programmed in front of a 328 or 1284 or 2560 tho.

I did inherit a Mega recently so time will tell. :slight_smile:

I use OS/X and have (virtually) no problems at all. This is with various Arduino boards. Sometimes I may have to disconnect and reconnect the USB cable, that is about all.

It isn't flaky, I've been posting stuff for a couple of years now as you can see from my post count. I don't regard the board(s) as flaky at all.

The Rainbowduino board is an Arduino compatible controller board with professional multiplexed LED driver.

I can't speak so much for so-called compatible boards. Nothing against them, but sometimes they employ USB drivers that are not as stable as the official ones.

BTW, I believe that a lot of the Arduino developers use Mac, but I'm not certain. I read it somewhere. :slight_smile:

I wouldn't throw your Mac out yet.

The Rainbowduino board is an Arduino compatible controller board with professional multiplexed LED driver.

I have a couple of these boards and as long as I select "Arduino Duemilanove w/ ATmega328" as my board type before uploading I have no problems in Windows. Are you saying Mac is also a bit flaky with arduino IDE.

Thanks for the continued feedback!

I believe the problem with the board I messed with (Rainbowduino 3.0) is that the FT232RL USB to UART chip is flaky and requires a bit of massaging based on all the threads I have seen across various websites. In this case, it required FTDI drivers and a lot of plugging things in over and over again until it sometimes worked.

I feel a little bit embarassed that I based my "issues" with OSX on one instance...I know better than that! :slight_smile:

JohnVilsack:
I feel a little bit embarassed that I based my "issues" with OSX on one instance...I know better than that! :slight_smile:

OSX and IOS are not perfect, I'm tracking IOS bugs across the last two major versions that have not been fixed.