Code: Select all
#!/usr/bin/env python from time import sleep import os import RPi.GPIO as GPIO GPIO.setmode(GPIO.BCM) GPIO.setup(4, GPIO.OUT) GPIO.setup(24, GPIO.OUT) GPIO.output(4, GPIO.LOW) GPIO.output(24, GPIO.LOW) sleep(3) GPIO.output(4, GPIO.HIGH) GPIO.output(24, GPIO.HIGH)
Code: Select all
pi@raspberrypi ~ $ sudo lsmod Module Size Used by rfcomm 33663 0 bnep 10514 2 bluetooth 157711 10 bnep,rfcomm
Did you read http://www.raspberrypi.org/phpBB3/viewt ... 97#p252197 ? I told him that the gpio 4 I've used was to test that actually the code works, since the pin 4 is working and I was getting voltage on that, so I've cloned the code to test pin 24 and I don't get any voltage from that.RaTTuS wrote:did you read
http://www.raspberrypi.org/phpBB3/viewt ... 80#p252178
and what do you have to say about it
pluggy wrote:If you're already using Arduino, I'd stay with it. The arduino is a microcontroller, the Pi is a computer with microcontroller aspirations. I'd say 90% + of those with a Pi don't use (or even have a clue) what the GPIO pins are for. Everyone with an arduino uses the i/o pins, because there would be no point in having one otherwise. I have both and the arduino is vastly superior for control of external circuits, but the GPIO can be pressed into service if you don't have an arduino.....
Use the chalk when you need chalk and cheese when you want cheese.
The raspberry isn't sh*t but if your'e using it as a microcontroller, it maybe is in comparison to a dedicated microcontroller. (There, I said it).
No-one on here is responsible if your Pi is faulty, just as no-one on the arduino forum is responsible if your arduino is faulty. But since everyone on the arduino forum will know something about microcontroller I/O and most on here won't. It isn't a fair comparison.
as meaning you'd been there in the first place.I'll go back to arduino
Users browsing this forum: JustinL and 61 guests