Another Xbee Problem - Rubbish coming via hyperterminal

[alaska1717]

Hi,
I have made a program on the sending end:

//Reads data from 0 and 1 and relays back to reciver
//lmc

int light = 0;
int temp = 1;
int thirteen = 13;

int lightval;
int tempval;

void setup(){
Serial.begin(19200);
Serial.println('Bonjour =]');
pinMode(light, OUTPUT);
pinMode(temp, OUTPUT);
pinMode(thirteen, OUTPUT);
digitalWrite(thirteen, HIGH);
delay(1000);
digitalWrite(thirteen, LOW);
}

void loop(){

digitalWrite(thirteen, HIGH);
Serial.print(analogRead(light));
Serial.print(',');
Serial.println(analogRead(temp));
delay(500);
digitalWrite(thirteen, LOW);
delay(500);
}

The code reads the analog inputs and outputs it over the serial after putting a comma in between the two of them. I have connected the xbee module correctly as otherwise I would get nothing coming from the xbee module. I have tried reloading the firmware on (10CD is my latest) and all I get on the serial line is something like this:

[J:.[*:.*J.K*J:.[*J.*J:.K*J.[J:.[J:.*J:.I*J:.[*:.*J..[*:.[*J:.[*:.K*:.[J:.[J:.K*:.[J;.K+J;.

over and over again, every second, like it should send above.

Why on earth is it doing this?
I am using a 3.3v Arduino pro and the Arduino software is in lilypad mode
The receiving module is using my working ladyada xbee module board and a 5v ttl232 cable.
Thanks

[33Warlord]

Of the top of my head, the garbage looks a lot like a baud rate inconsistency.

I'm wondering if the baud rate is set the same on both the sender and receiver? If so, has been the baud rate configuration of both XBees been changed to 19200? Your code initializes the Serial port to 19200, but the XBee's themselves default to 9600 (unless you change in X-CTU or via command mode).

If the baud rate is the same, and has been changed on both XBee modules, then perhaps you can view the debug print directly on the sending node to verify that the correct data is going into the XBee.

If the data is correct before getting transmitted via XBee, yet it's incorrect on the receiving end, then i would start trying some basic XBee tests (like manual ASCII transmissions). This will tell you if its an XBee config issue (likely) or an esoteric oversight in the code that causing a variable type mismatch (for example a botched DEC to ASCII conversion).

[alaska1717]

*headesk* thanks very much. I knew that it was xbee related as plugging in the ftdi cable got the intended result. Thanks very much, part deux of my project is set for sail =] i am replying from phone as i am bored at a party so will check this later.