@jvdk I agree with the point made by @evb , why would you want to wire connect the ultrasonic node rather than the usual radio connection ? You are adding levels of complexity and power demands for what reason ?
My ultrasonic water tank node (pro-mini+rfm69) is now 2 years on the same 2xAA batteries sending in levels every hour (RTC), the only problem encountered - condensation forming a drip on the face of the ultrasonic head during very low temperatures.
@fot said:
Hi!
I ask my gateway about it's version (0;0;3;0;2;). It will responde with the library version number (1.4.1 in my case).
It tells me that the gateway software is up and running. But it will not give me any clue about if the (NRF)network is working.
That's a problem, right.
I only ask the gateway if no other packages are received in $timeout seconds.
/Magnus
Of course ! Thank you for pushing my nose on it. Sometimes you don't see the most obvious
Since my gateway is relatively close to the controller (Domoticz on a Raspi), I can do a hard reset of the gateway (via Raspi GPIO), which should resolve the issue.
Cheers
Josh
@nrf24_is_hard When I sent data between an Aduino and the RPi I discovered that I have to make the the receiving and the sending structs the same size AND the variables be on 4 byte boundaries. Change your char name[15] to char name[16]
Another challenge is that the number of bytes of type int are different. If I remember correctly, Arduino Uno is 2 bytes and RPi is 4 bytes.
To make matters worse, some compilers make the least significant byte the first byte of a word and others make it the last byte of a word. eg, sending the value 1 would be received as 16777216 (0x00000001 vs 0x01000000)
There are a lot more gotcha's
OSD