Re: Odd Serial Monitor Readings..

Forum 2005-2010 (read only) Software Syntax & Programs
1

Edit: Double post :frowning:

2

Is the Serial.begin(9600) different than the one in the serial monitor?

3

Nope, both are set to 9600.

Thanks for the response :slight_smile:

Edit:

Even a simple

Serial.print("TEST");

comes out as an illegible string like above.

4

It definitely looks like a baud rate error.

Are you sure your oscillator frequency is 16 MHz?

--
Check out our new shield: http://www.ruggedcircuits.com/html/gadget_shield.html

5

No, I'm not really sure. :-?

I did play with the 9600 baud selection though, and found something.

If I change it to 4800 ( On the serial port window ) I get legible results.

Even though the code is listed at 9600. It seems to work in factors of two, if I change the code to 4800, I get legible results @ 2400 baud.

6

Then either you are using an 8 MHz oscillator or you have not programmed your fuses on the ATmega328 to make it use an external oscillator (16 MHz I'm assuming).

--
Check out our new shield: http://www.ruggedcircuits.com/html/gadget_shield.html

7

Well 16Mhz isn't perfect at 9600 anyway

http://www.wormfood.net/avrbaudcalc.php

Doesn't explain your issue though.

Then either you are using an 8 MHz oscillator or you have not programmed your fuses on the ATmega328 to make it use an external oscillator (16 MHz I'm assuming).

Presumably he got it pre-programmed and tested as an arduino pro mini but it might be that which is the issue.

Mowcius

8

Yes, I didn't do the programming myself. Though I am taking over the project, so I'm self teaching this stuff to myself

I think I found the issue, in the arduino setting I didn't have the correct board set... Once I correctly set the board to a Pro Mini, it works on 9600 baud.

Everything is working as intended at the moment, now I actually get to start coding it to do what we need :slight_smile:

9

Ahh, glad the issue is sorted :slight_smile: