Skip to content
  • 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
  • Getting Started
  • Controller
  • Build
  • Hardware
  • Download/API
  • Forum
  • Store

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.
  • 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
        • mfalkviddM 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
          
          
          
          miljumeM Offline
          miljumeM Offline
          miljume
          wrote on last edited by
          #44

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

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

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

            1 Reply Last reply
            0
            • alowhumA Offline
              alowhumA Offline
              alowhum
              Plugin Developer
              wrote on last edited by alowhum
              #46

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

              Changing to the development version fixed it.

              1 Reply Last reply
              0
              • alowhumA Offline
                alowhumA Offline
                alowhum
                Plugin Developer
                wrote on last edited by
                #47

                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?

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

                  Compile as ethernet GW, much less problems :D

                  1 Reply Last reply
                  0
                  • alowhumA Offline
                    alowhumA Offline
                    alowhum
                    Plugin Developer
                    wrote on last edited by alowhum
                    #49

                    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'

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


                    12

                    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
                    • OpenHardware.io
                    • Categories
                    • Recent
                    • Tags
                    • Popular