NRF24L01+ problems in 2.1.1 and 2.2.0 Beta

[Jokgi]

@miljume Are you using modules with the genuine Nordic Devices mounted on them? How do you have it connected? Are you successful with any other "compatible" modules?

[mfalkvidd]

@Jokgi to my knowledge, there is no way to know if devices are genuine, besides sending them to Nordic to have them checked. I have not done that, so I don't know whether they are genuine.

The radio module is connected using a 2x4 pin jumper wire connector on the nrf24 end and a 2x5 jumper wire connector on the raspberry pi end. Wiring for the nrf end is according to https://www.mysensors.org/build/connect_radio and https://www.mysensors.org/build/raspberry for the raspberry pi end.

I don't understand your third question. Could you clarify/rephrase?

[gohan]

I think he is asking if you tried other modules from different manufacturer

[mfalkvidd]

Thanks @gohan
In that case, the answer is that I don't know. I have ordered through Aliexpress 3-4 times. I don't know which modules came from which order, or if the orders were sourced from different manufacturers.

[mfalkvidd]

I have now tracked down the commit that makes the default raspberry pi gateway work: https://github.com/mysensors/MySensors/commit/4c31e22d6ff45c3a4f8aa70f915c5f10fe345f64

When using the commit before this (26c237adadda9f79b07d862708d8471285a96905 ) the radio init fails.

So now we at least know why development works and 2.1.1 does not.

git checkout 26c237adadda9f79b07d862708d8471285a96905
...
./configure --extra-cxxflags="-DMY_DEBUG -DMY_DEBUG_VERBOSE_RF24" && make && sudo bin/mysgw -d
...
mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0-beta
mysgw: MCO:BGN:INIT GW,CP=RNNG----,VER=2.2.0-beta
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: RF24:INIT
mysgw: RF24:INIT:PIN,CE=9,CS=24
mysgw: RF24:WBR:REG=0,VAL=14
mysgw: RF24:WBR:REG=3,VAL=3
mysgw: RF24:WBR:REG=4,VAL=95
mysgw: RF24:WBR:REG=5,VAL=76
mysgw: RF24:WBR:REG=6,VAL=37
mysgw: RF24:WBR:REG=16,VAL=115
mysgw: RF24:WBR:REG=29,VAL=6
mysgw: RF24:RBR:REG=6,VAL=0
mysgw: RF24:RBR:REG=5,VAL=0
mysgw: !RF24:INIT:SANCHK FAIL
mysgw: !TSM:INIT:TSP FAIL

git checkout 4c31e22d6ff45c3a4f8aa70f915c5f10fe345f64 #68
...
./configure --extra-cxxflags="-DMY_DEBUG -DMY_DEBUG_VERBOSE_RF24" && make && sudo bin/mysgw -d
...
mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0-beta
mysgw: MCO:BGN:INIT GW,CP=RNNG----,VER=2.2.0-beta
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: RF24:INIT
mysgw: RF24:INIT:PIN,CE=22,CS=24
mysgw: RF24:WBR:REG=0,VAL=14
mysgw: RF24:WBR:REG=3,VAL=3
mysgw: RF24:WBR:REG=4,VAL=95
mysgw: RF24:WBR:REG=5,VAL=76
mysgw: RF24:WBR:REG=6,VAL=37
mysgw: RF24:WBR:REG=16,VAL=115
mysgw: RF24:WBR:REG=29,VAL=6
mysgw: RF24:RBR:REG=6,VAL=37
mysgw: RF24:RBR:REG=5,VAL=76
mysgw: RF24:WBR:REG=2,VAL=2
mysgw: RF24:WBR:REG=1,VAL=0
mysgw: RF24:WBR:REG=28,VAL=3
mysgw: RF24:FRX
mysgw: RF24:FTX
mysgw: RF24:WBR:REG=7,VAL=112
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: RF24:WBR:REG=2,VAL=3
mysgw: RF24:WBR:REG=1,VAL=1
mysgw: RF24:STL
mysgw: RF24:WBR:REG=0,VAL=15
mysgw: RF24:WBR:REG=10,VAL=0
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: RF24:RBR:REG=23,VAL=17
mysgw: Listening for connections on 0.0.0.0:5003

[GrantsPi]

I am glad I'm not the only one having this issue (but hope it will be resolved soon).
I had a RPi3 with the MQTT gateway working well for the past year, until I decided to upgrade to the latest version of Raspbian (and MySensors). I've now tried with a fresh install on both the RPi3 and a RPi2; with the same NRF24 as before (working well in the previous build); I also tried with a different radio using a socket and capacitor.
Looking forward to your progress!

mysgw: Starting gateway...
mysgw: Protocol version - 2.1.1
mysgw: MCO:BGN:INIT GW,CP=RNNG---,VER=2.1.1
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: !TSM:INIT:TSP FAIL
mysgw: TSM:FAIL:CNT=1
mysgw: TSM:FAIL:PDT
mysgw: TSM:FAIL:RE-INIT
mysgw: TSM:INIT
mysgw: !TSM:INIT:TSP FAIL
mysgw: TSM:FAIL:CNT=2
mysgw: TSM:FAIL:PDT

[miljume]

@Jokgi Mots probably they are not genuine (bought from Aliexpress) but these devices themselves have not caused me any issues before. It started when I upgraded to 2.1.1. Although, after a clean install with 2.2.0 Beta it started working again so I am 100% sure that it's not the modules

[miljume]

@mfalkvidd Good! I have now succeded in getting 2.2.0 Beta up and running with Ethernet GW

[wergeld]

@mfalkvidd said in NRF24L01+ problems in 2.1.1 and 2.2.0 Beta:

git checkout 4c31e22d6ff45c3a4f8aa70f915c5f10fe345f64

Okay, this works for me now as well. However, Domoticz still doesn't report any updated data beyond the first seen measurement for the temp portion of the sensors....I am about to see how far these slim nodes can fly...

[alowhum]

I had the same problem with 2.1.1 on a Raspberry Pi Zero W.

Changing to the development version fixed it.

[alowhum]

I'm trying to connect Domoticz to a virtual serial.

./configure --my-transport=nrf24 --my-rf24-irq-pin=15 --my-rf24-pa-level=RF24_PA_LOW --my-gateway=serial --my-serial-is-pty --my-serial-pty=/dev/serial2

But while Domoticz sees the serial port, it does not seem to connect. I also see the "end of file" error in the Domoticz logs.

What baudrate should be set in Domoticz?

[gohan]

Compile as ethernet GW, much less problems :D

[alowhum]

Tried that, still having problems.

Syslog says a lot of: "mysgw: Client 0: 0:0:3:0:18:PING
with an occasional "rsyslogd-2007: action 'action 17' suspended, which is probanly about the log being spammed by MySensors.

• It uses a 3.3v stabiliser board.
• Tried different power levels in settings (usually use low power because it works better for the cheap Chinese knock-offs)
• Tried external 5v power supply.

My nodes are saying 'FPAR: NO REPLY'