I am doing an Arduino based quadcopter for a school project and I am starting to debug the code to make sure it is reading the controller inputs, reading the gyro/accelerometer inputs, and computing everything correctly before I hook it up to the motors.
Right now, the Gyro/Acc (GY-521) uses I2C to communicate with the Arduino using the serial port pins. I went to use the Serial monitor to display each value, but it is coming up with nothing but Wingding Glyphs.
I'm guessing this problem exists because the I2C communication is taking control of the serial port while the Arduino board is trying to send information back to the serial monitor.
Is there any way I can still use the serial monitor to monitor the incoming values and calculations in my case, or is there another method of debugging without the serial port? Any information on the topic will help tremendously.
TOhlsen:
the Gyro/Acc (GY-521) uses I2C to communicate with the Arduino using the serial port pins
Why ?
Doesn't your Arduino do I2C through pins A4 and A5 ?
You forgot to tell us what Arduino you're using,or any detail whatsoever so i can't know for sure.
But you should never use the serial pins unless you absolutely need to, and you know what you're doing.
You can't use any pins for different functions at the same time.
If you'd need to do so you could monitor the traffic on those serial pins, but only if there's serial data on it of course and you need to match settings.
TOhlsen:
I went to use the Serial monitor to display each value, but it is coming up with nothing but Wingding Glyphs.
Wingding Glyphs?
Not sure what you mean. But if it is what I'm thinking it is, check your baud rate.
In your code, you set Serial.begin(9600); or some other baud rate. In the lower right of your serial monitor, select the same baud you have in your code.
I thought our "silly mistakes all the time" club was a bit too exclusive to invite a newbie to it
He needs to work through the "silly mistakes occasionally" stage first.
