- Thu Jan 04, 2007 3:38 pm
#24519
I've been using the arduino proto board with the bluesmirf on a robot build. One of the first things I realized when I put it together is that the bluesmirf's rx and tx are connected to pins 2 and 3. Was there a reason for this?
The arduino's rx and tx pins are hardwired to 1 and 0. With my smirf, that's where I'd prefer its pins to point, as I'd like to use the Serial object in my code.
The only other way to talk to serial on pins other than 1 and 0 is to use the software serial functions, that run at limited baud rates (er.. 1 baud rate.. 9600.. because the smirf won't talk slower than that) and have limited functionality (no Serial.available())
Additionally, discussion on this thread:
http://www.arduino.cc/cgi-bin/yabb2/YaB ... 1167803201
seems to indicate that by taking up 2 and 3, you lose external interrupt capabilities, as those are hardwired to those pins.
Could we get a version of the protoshield where the smirf's serial pins go to a header so we can choose where they point? or failing that, one that just points to 0 and 1? I'm thinking about cutting the traces on mine.
The arduino's rx and tx pins are hardwired to 1 and 0. With my smirf, that's where I'd prefer its pins to point, as I'd like to use the Serial object in my code.
The only other way to talk to serial on pins other than 1 and 0 is to use the software serial functions, that run at limited baud rates (er.. 1 baud rate.. 9600.. because the smirf won't talk slower than that) and have limited functionality (no Serial.available())
Additionally, discussion on this thread:
http://www.arduino.cc/cgi-bin/yabb2/YaB ... 1167803201
seems to indicate that by taking up 2 and 3, you lose external interrupt capabilities, as those are hardwired to those pins.
Could we get a version of the protoshield where the smirf's serial pins go to a header so we can choose where they point? or failing that, one that just points to 0 and 1? I'm thinking about cutting the traces on mine.