This forum has moved to forum.jeelabs.net - this read-only archive is for reference only!
Since I finally have more than one JeeNode ready to send data I tried to setup unique IDs for each of them. I'm using latest RF12Demo to do this. However it seems that after I upload my sketch the ID is always reset to "Q". I tried this on 3 differnt nodes with same results.
After seting node ID in RF12demo:
C i3 g212 @ 868 MHz
After uploading my room sketch:
Q i17 g212 @ 868 MHz
As you see the band and other settings stay intact. Is there anything that might erase eeprom ?
Do you see the Q still when re-powering the node with RF12demo still loaded? In that case EEPROM is ok.
Just tried your settings with the "rooms" sketch. Works for me.
Hm. EEPROM used by rf12config() is 0x020..0x03F. SImple one-byte damage wouldn't do what you describe - rf12config verifies a crc checkum to make sure it's reading a proper setup. Try printing the rf12config() return value - it should be 17.
After setting to "C" and re-powering with RF12demo I still see "C".
However in my sketch I see "Q". I checked the crc returned by rf12config() and it is 17 indeed. It seems suspicious that the Q is also equal to 17 as node ID. So maybe in some place in code you overwrite the node ID with the crc by incindent ?
Oh wait, I mixed things up. You should have seen 3 as rf12config's return value (the id extracted from eeprom).
Something is fishy. You're saving 3, you can see 3 after re-power, then you flash another sketch and it sees 17, right?
Make sure you have the latest RF12 (and Ports, just to be sure), and throw away all the applet/ subdirs in the sketch directories. Make sure you use Arduino 0017 (which places its libraries in a different spot!), and that it's really using the code you think it is using. Just to be sure you could also re-flash the boot loader (there's an erase EEPROM fuse bit, though I don't see how that would affect this in the way you describe).
I can't think of any other thing to do but re-tracing all your steps.