Hello,
I am using a JeeNode micro running the sender example and an adafruit Atmega32u4 breakout board with a RFM12B attached (running the receiver example). They are communicating but after the third loop iteration only payload garbage appears on the screen (see attached scrennshot of the serial terminal data). CRCcheck seems to pass. Any ideas where to look at?
Thanks!
Nils
I suspect the problem is actually with the serial terminal program you are using to capture the data. I see this a lot with TerraTerm. When the serial terminal receives an data byte which is not a printable character, it gets into a very funky mode. The only way out is to reset the terminal or disconnect and reconnect the serial connection to the serial terminal program.
The hint for me that its a serial terminal display problem only is that :
1. It works for awhile and then quits.
2. Even when getting garbage, the CRC checks out. If real garbage was received, then the CRC should fail.
Well, I also tried a different terminal (Arduino IDE). Same results. I think if it is a terminal issue the "ack send" would also be weird. I suspect that something on the sender side goes wrong (Oszillator frequency?). I will check that on the weekend...
I had the same problem when I got my Moteinos and then I realized my Serial terminal was refreshing at a slower rate (9600 vs 115200), I was busting my head on the wall until I saw this. Super simple and easy to overlook. I dont know why having the serial at a different baud rate creates this kind of problem (I thought you just didn't see anything). Maybe someone with more experience can explain.
Hope this helps!
In UARTS there is no clock reference. It is just an assumption that both ends run at the same baud rate. Then what the sender transmits at Xbaud is interpreted at Xbaud on the receiver. Otherwise garbage will result.