Congrats on the most excellent JeeNode, JC. Great size and useful docs. Wireless rocks!
I've got the demo blinkrecv and blinkxmit code working fine on two new JeeNodes, and now I'm doing the following as a test:
Unit A has an accelerometer. Unit B has 4 leds that respond to simple XY rotation positions on Unit A.
For unit A, I modified blinkxmit (took out the timers) and hooked up the accelerometer, and the code is working fine. (I added leds on the 4 ports on unit A, and they light up as planned.)
For unit B, so far I am just running your original blinkrecv. I am getting data from unit A (the leds do change when I rotate unit A), but the leds on unit B are not lighting up in the proper patterns.
Looking at blinkrecv, it seems you are hard coding the port writes based on flags in the "state" variable data received from the transmitter. The code logic in blinkrecv seems to match the logic in blinkxmit, minus the timers of course.
I am confused by that, because, in blinkxmit you are using Remote Port objects, which from reading the docs I expected would just directly (somehow, automagically, ha!) talk to the ports on the receiving unit.
So here are my hopefully-not-lame questions:
If I'm using RemoteNode and RemotePorts, how do I modify blinkrecv so that, for example a RemotePort digiWrite() from the transmitter can be properly interpreted in the receiver? Or is there a "generic" program a receiver can run which interprets the various possible reads and writes a transmitter can send with RemotePorts?
Or more generally, where can I find documentation about the RemoteNode::Data properties? I'm pretty sure if I knew the bit pattern assumptions I could work it out.
Cheers.
peterMac