Mod

@freedomnx said in Problem with BananaPI M2U and RFM69HW:

!TSM:INIT:TSP FAIL

Indicates a communication problem with the radio. As you state your wiring is correct, it can be a faulty radio or indeed the bananapi. I can't help you on that...

Chipping in for @tekka

@encrypt said in A water pulse meter using interrupts and the ATMEGA328P "power save" mode:

On the gateway side, I can see that the node successfully registers and gets its ID. But for an unknown reason, after a few seconds, it keeps sending data as if time_elapsed never changed to false. And it never goes to sleep.

Please be aware that sleeping on interrupts is rather tricky to get right!
When going to sleep, pending interrupts will immediately wake the AVR again. See the MySensors code from https://github.com/mysensors/MySensors/blob/development/hal/architecture/AVR/MyHwAVR.cpp#L183 on.

In your case pending interrupts are very likely, as you use a mechanical button that hasn't been debounced.

Furthermore you are using MySensors internal functions that might work for now, but are not guaranteed to work in the future.
I would suggest to stick to the official API whenever possible.

MySensors development branch offers the ability to sleep for a fixed time and report remaining sleep time. Your node should just go back to sleep until 5 minutes have passed; see my post here: https://forum.mysensors.org/topic/9595/interrupted-sleep/11
Only drawback on AVR is the usage of the watchdog as a sleep timer, which makes it impossible to exactly get 5 minutes sleep interval.

Thanks you @alowhum, is the splitting systematic or done in settings/configured ?

@bean72 we do 't have conclusive data on that unfortunately.

In some cases, 4.7uF is good, sometimes 47uF is better. Some people use a combination of small and larger.

@freedomnx Did you follow the wiring scheme for RPi? https://www.mysensors.org/build/raspberry#wiring
What RFM breakout do you use? Post pictures of your setup.

@bean72 maybe the 3.3V regulator on the Micro is noisy? Nrf24 is very sensitive to noise.

You could try the Micro but use an external power supply for the nrf24.

exactly.
like mfalkvidd and nca78 said, i2c is a bus, not the case of the serial comm you use. and serial devices are usually not very low power.

again I agree, serial sw is maybe ok for a simple device, else it has very poor performance. bad idea for lcd fast refresh, or sampling sensors etc. I avoid it as much as I can (I think I don't have any projects using it though)

same as nca78 I have a few projects when I use all esp32 pins, and I use serial, i2c and spi a lot, even canbus, ..hopefully I have not used serial interface only!

better use the right tech for a project

@berkseo
I think it might be simple, and you might just have to add your digitalwrites to nrf5 driver, then you can PR on git if you want. team's busy for the moment, but if you don't PR, we'll do it, when more time.

@alowhum your are also missing the longer cables as uart is more resistant to interference.

The limits I see are:

1. when you need to use software serial with high baudrate, I don't think a poor uno will handle well multiple software serials at 115k ?
   If it has to process the data and store/send it, it might miss some data as software serial has no hardware input buffer.
   Of course if sensors don't need to run simultaneously then this will not be a problem.

2. pin usage. Each sensor using 2 pins can be a limit. Should not be in this case on a uno, but I have the problem on ESP32, I had to make a daughter board with an attiny to convert uart sensors to i2c, now I can have as many as I want.

@od1 i2c supports multiple devices on the same cable (if the devices can configure address).
Uart can support longer cables, but both can support 10m.

Both can be used with software (bit-banging) which means you are not limited to the hardware serial/i2c.