Why did many people switch from Arduino to Raspberry Pi?
Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Why did many people switch from Arduino to Raspberry Pi?
I mean for DIY electronic projects. Raspberry Pi has just 1 PWM, no ADC etc., and it has much less docs on interfaces like I2C and SPI than Arduino... Why do many bother writing code and interfaces on it and use it for projects that would work on a MCU like the ATMEGA328 then?
In addition, what is the equivalent of the Arduino IDE hobbyists use to write programs that use the GPIOs on the Pi?
I don't know that many persons switched. I think the Pi may have attracted interest from lots of persons who might never have tried an Arduino in the first place.
I'm not one of those Pi persons, at least not so far, so I can't hazard a guess on your second question.
I think the reason most people would switch is that the Rpi provides a system that is portable while Arduino is device that would be specific to configurations/interface beyond the Rpi without adding peripheral interfaces. Sure some designers will marry the two to get the means of providing expansions along with port-abilities of said units. You could use the Rpi to program/control the Arduino device while interfaced with it's shelds.
Not everyone would need to use Rpi's in order to use Arduino supported equipment/shields. Overhead cost for the Rpi would be one reason to just use Arduino to interface with the world.
That's a bit like saying people switch from motorcycles to a car.
They are very different animals.
They are both fabulous for very different reasons. Open souce hardware is the next big revolution I reckon.
Microsoft is becoming irrelevent as people have switched to phones and tablets, Sun and other big names have gone to the wall because of open source. Hardware is next, it should be very exciting.
It looks like the Pi has a lot more horsepower behind it. Quad core 900Mhz processor on the Pi vs a 16Mhz Arduino Pro. 1GB RAM on the Pi vs 2k on the Arduino. Basically the Pi is more capable for things like a homemade Roku. It can be used as a personal email server. It has 4 USB ports, Ethernet, HDMI out, and a discreet 3D graphics processor. It can be used as a computer, not just a controller chip.
It looks like the Pi has a lot more horsepower behind it. Quad core 900Mhz processor on the Pi vs a 16Mhz Arduino Pro. 1GB RAM on the Pi vs 2k on the Arduino. Basically the Pi is more capable for things like a homemade Roku. It can be used as a personal email server. It has 4 USB ports, Ethernet, HDMI out, and a discreet 3D graphics processor. It can be used as a computer, not just a controller chip.
That's probably why.
Ardunio is a lot different purpose than the Rpi. When controlling a interface for a shield one does not need the overhead of the Rpi with a standalone Arduino with interface as a shield. Apples & oranges! Or should I say apples & bananas??
Arduino can be a standalone interface subsystem at a minimal cost for little overhead.
It's not just device capabilities. The pi can be used for other things if a project doesn't pass the proof of concept stage. And there's a resale value for a pi. Where if you bought too many arduinos, you could be stuck with them for a very long time. In my opinion.
[snip]
In addition, what is the equivalent of the Arduino IDE hobbyists use to write programs that use the GPIOs on the Pi?
Thanks
I don't know about other people, but for my RPi GPIO I tend towards the python RPi.GPIO package... with vi as my "IDE"
I'm not a heavy user of the IO though, for that I have arudino (et al.)
@onebuck pretty much nailed your other question I think, it's apples and bananas. Each device has it's own place in the ecosystem.
Or apples vs raspberries
I agree they both fit different needs. The RaspberryPi's and BananaPi's, OrangePi's, Beagle Bone, etc are for when you need a higher level OS. For simpler projects the Arduino, PIC, etc are a better fit.
I don't know that many persons switched. I think the Pi may have attracted interest from lots of persons who might never have tried an Arduino in the first place.
I'm not one of those Pi persons, at least not so far, so I can't hazard a guess on your second question.
I think this is one of the biggest reasons.
I've never "switched" I've used Pi, Beagleboard, Hummingboard, and Gumstix; and have never used Arduino.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.