Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Bug Reports
  3. NRF24L01+ problems in 2.1.1 and 2.2.0 Beta

NRF24L01+ problems in 2.1.1 and 2.2.0 Beta

Scheduled Pinned Locked Moved Bug Reports
49 Posts 9 Posters 10.1k Views 12 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    arraWX
    wrote on last edited by arraWX
    #24

    With 2.1.1 I have the exact same problems.

    However, everything seems to be fine with 2.2.0 Beta:

    git clone https://github.com/mysensors/MySensors.git --branch development
cd MySensors
./configure --my-transport=nrf24 --my-gateway=ethernet --my-port=5003 --my-rf24-pa-level=RF24_PA_MAX
make

    In domoticz:
    0_1508010294046_Udklip.PNG

    The result:

    pi@raspberrypi:~/MySensors $ sudo ./bin/mysgw -d
mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0-beta
mysgw: MCO:BGN:INIT GW,CP=RNNGL---,VER=2.2.0-beta
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: Listening for connections on 0.0.0.0:5003
mysgw: MCO:BGN:STP
mysgw: MCO:BGN:INIT OK,TSP=1
mysgw: TSF:MSG:READ,2-2-0,s=1,c=1,t=0,pt=7,l=5,sg=0:24.0
mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=1,pt=2,l=2,sg=0:58

    After success with 2.2.0 Beta I tried to go back to 2.1.1. However, it still does not work.

    I am on rpi3 and use a socket adapter board for the radio.

    1 Reply Last reply
    2
    • W Offline
      W Offline
      wergeld
      wrote on last edited by
      #25

      So, I did a lot of re-configuring and using 2.2.0 beta when a node sends a value payload (in my case a temp/humidity/battery value I get this while running my RPi ethernet gateway in debug:

      mysgw: TSF:MSG:READ,3-3-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=3
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OK
mysgw: !TSF:MSG:SEND,0-0-3-3,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
mysgw: TSF:MSG:READ,3-3-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=3
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OK

      This continues until I kill the process. In the middle of all of these error messages though, it also reports client PING events:

      mysgw: Client 0: 0;0;3;0;18;PING

      Other interesting items of note:
      Domoticz says the values for temp have not been updated for 3+ hours for that node.
      Domoticz says that node only has a temp sensor.
      MYSController reports it having 2 sensors (temp and humidity) and it reports the values when i would expect them to be sent (ie, not 3+ hours old but updated continuously when temp changes).

      I am at my wits end here.

      1 Reply Last reply
      0
      • gohanG Offline
        gohanG Offline
        gohan
        Mod
        wrote on last edited by
        #26

        NACK on the gateway usually means that the radio module is not powered correctly or there is a range issue (or you didn't set max tx power on the gateway)

        W 1 Reply Last reply
        0
        • W Offline
          W Offline
          wergeld
          wrote on last edited by
          #27

          This is getting odder and odder.
          I am running 2.2.1 beta on my RPi2B. It is running on channel 76, with power max, and using ethernet gateway config.
          I have MYSController running on separate laptop and it is seeing updates to temp/hum and/or battery level. However, neither Domoticz or OpenHab2 have seen a change since last night at 9pm.

          In Domoticz - Setup - Hardware - Mysensors 2.2.0 Gateway it shows 2 nodes. First node is the gateway, of course, and the second is the sensor node. The data and the last seen times are correct! But, the Domoticz - Setup - Device list only shows the Temp sesnor and a last seen date of last night at 9pm. There are not other mysensors devices available.
          So, what is different between MYSControler and Domoticz and OpenHab?

          1 Reply Last reply
          0
          • gohanG gohan

            NACK on the gateway usually means that the radio module is not powered correctly or there is a range issue (or you didn't set max tx power on the gateway)

            W Offline
            W Offline
            wergeld
            wrote on last edited by
            #28

            @gohan This doesnt really make sense to me. This happens after I get data from a sensor and the gateway gets stuck in a loop of those messages. MYSControler shows the correct value that triggered these messages while OpenHab and Domoticz do not.

            1 Reply Last reply
            0
            • gohanG Offline
              gohanG Offline
              gohan
              Mod
              wrote on last edited by
              #29

              Do you have capacitors on the radio modules? If you move the node closer to the gateway (3/4 meters apart) , does it work better?

              W 1 Reply Last reply
              0
              • gohanG gohan

                Do you have capacitors on the radio modules? If you move the node closer to the gateway (3/4 meters apart) , does it work better?

                W Offline
                W Offline
                wergeld
                wrote on last edited by
                #30

                @gohan Yes, capacitors on both the node(s) and the gateway radios. Moving the nodes closer to gateway has no affect. The gateway is sending out udpates (per MYSControler at least) but Domoticz sees no new devices and OpenHab has not seen an update either. So frustrating.

                1 Reply Last reply
                0
                • gohanG Offline
                  gohanG Offline
                  gohan
                  Mod
                  wrote on last edited by
                  #31

                  Try to stop the gateway and run it with debug from console and c'è if you see any NACK occurring, also on the node if you can, because probably the controller is not accepting messages with NACK. If you can, try to make another arduino based gateway and see if you still get same errors. Keep in mind that if radio modules are not genuine you have to consider they are the cause of your problems.

                  W 1 Reply Last reply
                  0
                  • gohanG gohan

                    Try to stop the gateway and run it with debug from console and c'è if you see any NACK occurring, also on the node if you can, because probably the controller is not accepting messages with NACK. If you can, try to make another arduino based gateway and see if you still get same errors. Keep in mind that if radio modules are not genuine you have to consider they are the cause of your problems.

                    W Offline
                    W Offline
                    wergeld
                    wrote on last edited by
                    #32

                    @gohan unable to run my node in debug with radio attached at the moment (no 3.3v FTDI or mosfets available right now).
                    But, that being said - the MYSControler does get the updated values. Just not Domoticz or OpenHab. So, why does one client connecting to the gateway get data while the other two do not?

                    1 Reply Last reply
                    0
                    • gohanG Offline
                      gohanG Offline
                      gohan
                      Mod
                      wrote on last edited by
                      #33

                      Myscontroller doesn't see all debug messages. Get a ftdi adapter quickly 😁

                      W 1 Reply Last reply
                      0
                      • gohanG gohan

                        Myscontroller doesn't see all debug messages. Get a ftdi adapter quickly 😁

                        W Offline
                        W Offline
                        wergeld
                        wrote on last edited by
                        #34

                        @gohan Yea, I have one on order taking the slow boat from China. But, it bothers me that MYSControler "gets" the sensor node values and the other controlers do not. Same IP config. And the weird NACK errors. Something just seems screwy as this hardware was working up until about 3 months ago - no changes made.

                        1 Reply Last reply
                        0
                        • mfalkviddM Offline
                          mfalkviddM Offline
                          mfalkvidd
                          Mod
                          wrote on last edited by mfalkvidd
                          #35

                          I have now purchased an extra Raspberry Pi to test the raspberry pi gw.

                          2.1.1 fails with the most basic configure (without any parameters) while the same wiring and configure command works for development (I used commit 901258f16598)

                          git checkout 2.1.1
./configure
...
make
...
sudo ./bin/mysgw -d
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

git checkout development
./configure
...
make
...
mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0-beta
mysgw: MCO:BGN:INIT GW,CP=RNNGL---,VER=2.2.0-beta
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: Listening for connections on 0.0.0.0:5003
mysgw: MCO:BGN:STP
mysgw: MCO:BGN:INIT OK,TSP=1

                          I'm not sure how to proceed though. Is there anything you want me to try?

                          1 Reply Last reply
                          2
                          • mfalkviddM Offline
                            mfalkviddM Offline
                            mfalkvidd
                            Mod
                            wrote on last edited by
                            #36

                            This is the verbose rf24 output. Not sure if it helps.
                            2.1.1:

                            ./configure --extra-cxxflags="-DMY_DEBUG -DMY_DEBUG_VERBOSE_RF24" && make && sudo bin/mysgw -d
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: RF24:write register, reg=0, value=14
mysgw: RF24:write register, reg=3, value=3
mysgw: RF24:write register, reg=4, value=95
mysgw: RF24:write register, reg=5, value=76
mysgw: RF24:write register, reg=6, value=39
mysgw: RF24:write register, reg=16, value=115
mysgw: RF24:write register, reg=29, value=6
mysgw: RF24:read register, reg=6, value=0
mysgw: RF24:read register, reg=5, value=0
mysgw: !RF24:INIT:SANCHK FAIL
mysgw: !TSM:INIT:TSP FAIL

                            development:

                            ./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=RNNGL---,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=4
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
                            1 Reply Last reply
                            0
                            • miljumeM miljume

                              Hello,

                              I would like to submit a bug report for these libraries in the use of NRF24L01+ radio

                              I have problems with NRF24L01+ on both 2.1.1 and 2.2.0 Beta

                              I have installed a fresh RPI with all new libraries and trying to make a RPI Serial GW

                              In 2.1.1 it doesn't start at all but in 2.2.0 it starts but in the log I constantly receive the following in the Domoticz log where I have added the GW

                              I2017-10-09 19:25:12.306 MySensors: Gateway Version: 2.2.0-beta
2017-10-09 19:25:12.306 Error: Serial Port closed!... Error: End of file
2017-10-09 19:25:13.306 MySensors: retrying in 30 seconds...

                              After a while I get the following in the console

                              mysgw: TSF:MSG:READ,0-0-0,s=0,c=3,t=2,pt=0,l=11,sg=0:Get Version
mysgw: !TSF:MSG:LEN,0!=18

                              The above points at something wrong with the radio connection

                              I have tried 3 different radios but still no luck so I guess it has something to do with the libraries

                              JokgiJ Offline
                              JokgiJ Offline
                              Jokgi
                              wrote on last edited by
                              #37

                              @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?

                              mfalkviddM miljumeM 2 Replies Last reply
                              0
                              • JokgiJ 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?

                                mfalkviddM Offline
                                mfalkviddM Offline
                                mfalkvidd
                                Mod
                                wrote on last edited by
                                #38

                                @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?

                                1 Reply Last reply
                                0
                                • gohanG Offline
                                  gohanG Offline
                                  gohan
                                  Mod
                                  wrote on last edited by
                                  #39

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

                                  mfalkviddM 1 Reply Last reply
                                  0
                                  • gohanG gohan

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

                                    mfalkviddM Offline
                                    mfalkviddM Offline
                                    mfalkvidd
                                    Mod
                                    wrote on last edited by mfalkvidd
                                    #40

                                    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.

                                    1 Reply Last reply
                                    0
                                    • mfalkviddM Offline
                                      mfalkviddM Offline
                                      mfalkvidd
                                      Mod
                                      wrote on last edited by
                                      #41

                                      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
                                      miljumeM 1 Reply Last reply
                                      3
                                      • G Offline
                                        G Offline
                                        GrantsPi
                                        wrote on last edited by
                                        #42

                                        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
                                        1 Reply Last reply
                                        0
                                        • JokgiJ 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?

                                          miljumeM Offline
                                          miljumeM Offline
                                          miljume
                                          wrote on last edited by miljume
                                          #43

                                          @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

                                          1 Reply Last reply
                                          1
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes

                                          19

                                          Online

                                          11.7k

                                          Users

                                          11.2k

                                          Topics

                                          113.0k

                                          Posts


                                          Copyright 2019 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
                                          • Login
                                          • Don't have an account? Register
                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • MySensors
                                          • OpenHardware.io
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular