Pi = general purpose programming learning platform with side benefits (you can do your homework on it and interface with electronics).xcubicle wrote:im still very new to all of this. what are their target markets?
sleicreider wrote:what would be the best for my different projects i wanna try to make:
1) Turn Light(LEDs /LED strips) on/off via Smartphone or Computer(LAN/WLan)
2) Play music from Smartphone(with WLan) where the Signal Revceiver(Rasp Pi/ or µC) plays the music on my SoundSystem
3)Connected Camera on one the Boards(PI/µC) which sends mi video signals to my PC to see whats going on via LAN
which one can handle with these tasks?
For people like myself who already have development tools for working with Microchip PIC devices and are already familiar with programing PIC MCUs in C it would be nice to incorporate the Raspberry pie into existing and new PIC projects.sleicreider wrote:@danpeirce
i've seen in your picture that u use this ftdi & PIC for extra hardware access(I/O)? or ´what exactly are this 2 items?
i was thinking about getting a gertboard for more GPIO
MPLAB C and Hi-Tech C (there may be others) are both available at no cost, but with limited optimisation over the paid for versions. The differences are most apparent with floating point or complex functions (printf and scanf, for example), but for hobbyist/low volume stuff, a choosing a PIC with extra memory can compensate. Both support inline assembler, which is a useful catch-all if you can bear PIC assembly code.rurwin wrote: It's been ten years since I programmed a PIC, so I might be out of date, but at that time the only compilers you could get, you had to pay for, whereas the AVR uses the Gnu compilers.
This is the conundrum I'm having. I'm thinking of making a robot with the Raspberry Pi at its heart, but I'm trying to decide whether or not I need to put an Arduino (or rather an Atmel microcontroller) on my board. I only want to drive two motors so I only need 4 GPIOs. Even though it's not running an RTOS so isn't going to react quickly, if the RPi is making all of the decisions then I might as well connect its GPIOs directly to a motor controller (via protection and buffering as necessary) rather than talk to a microcontroller and get that to drive the motor controller. But that just seems too simple, I've got this nagging feeling that I'm missing something, it should be more complicated than that, and I will need the microcontroller after all.mikerr wrote:If its primarily hardware stuff you're doing - controlling a few servos, leds etc go arduino as it is setup for lots of IO
Best option is using both a Pi AND an arduino - you can get the Pi to talk to the arduino via serial or USB
Users browsing this forum: No registered users and 3 guests