Replies to This Discussion

Permalink Reply by Adam H on July 24, 2012 at 9:29am

ArduIMU uses a custom FastSerial library. I thought that was causing the problem, but I've since removed all calls for FastSerial (which is basically everything having to do with the GPS) and I still cannot read any serial input on the ArduIMU. Any luck on your end with this problem? (I know I'm about a year too late.)

• ▶ Reply

Permalink Reply by yihualou92 on July 25, 2012 at 3:22pm

Sorry, I abandoned my efforts to try and communicate with the ArduIMU over serial. I'd crack it open again to see if I could get it working a year later, but it's still stuck at school along with the rest of my stuff.

• ▶ Reply

Permalink Reply by Adam H on July 25, 2012 at 5:35pm

I figured it out! The ArduIMU V3 already receives serial data from the GPS connection. For some reason, the GPS uses the TX line of the AVR, then another random pin that is used for the RX line. The Serial port that the code is referring to is the GPS RX pin. There's a setting in the code that changes a Serial_Mux pin to select between the normal hardware RX pin and another pin on the board. There are two options: 

1. Simply use the RX line on the GPS connection (labeled "IN' on the PCB).
2. What I did was to change a setting (#define GPS_CONNECTION 0 // 0 for GPS pins, 1 for programming pins).  I changed that back to the regular RX/TX programming port pins.  I plugged my other peripheral on the normal port pins and everything started working perfectly using if(Serial.available()>0)  {...} I assume serial.event should work as well.

• ▶ Reply