@snyfir said in Gateway with signing = low memory:
MY_RX_MESSAGE_BUFFER_FEATURE
It's hard to have it all with an Arduino Nano, but you could try with a smaller receive buffer, by defining
#define MY_RX_MESSAGE_BUFFER_SIZE (10)
Here it is changed to 10, default is 20, which is rather large.
Each buffer entry reserves 33 bytes, so you'll save 330 going back to 10 entries.
@blackchart maybe the radio died. That happened to me a few times.
@geforcegamer what do you use as interrupt source?
If you use e.g. a hardware button then bouncing of the switch contacts can cause the node to wake up unexpectedly.
Also, you wake on CHANGE, meaning both a low high and high low transition will wake up your node (e.g. Button press and button release).
Can you describe your hardware setup?
@grumpazoid what hardware are you running your gateways and sensors on? Please provide a thorough description.
@grubstake said in why no one uses latching relays ?:
This seems useful for any sort of battery powered node that is to trigger opening or closing a circuit
Be aware that the relay on the board is non latching. Keeping it in actuated state requires continuous power to the relay coil, which will quickly drain batteries.
@flyingdomotic I agree with @mfalkvidd. The delays follow the original nrf24 datasheet closely. If it works for you, it might break operation for many other users.
Your changes likely mask the real issue.
Did you try my suggestions?
@texnic the seller must have changed the items. I will look into it. Thanks for the hint!
@roland-wijnen This error is indeed common when the connection to the bootloader fails. Do you know if the ATMega contains a bootloader at all?
Try to contact @ceech for support.
@flyingdomotic I suspect it might have the same failure cause, when a node/gateway switches from receive to transmit (for the PONG response) too fast, preventing the hardware ACK from being transmitted to the sending node (the PING).
Especially this code looks suspicious: https://github.com/mysensors/MySensors/blob/development/core/MyTransport.cpp#L786
Try enabling that code on the fast node first.
You could also try adding a delay after reception of a message to assure there's time for the hardware ACK just before the return statement here: https://github.com/mysensors/MySensors/blob/development/hal/transport/RF24/MyTransportRF24.cpp#L148