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. Troubleshooting
  3. Still not going well for me.

Still not going well for me.

Scheduled Pinned Locked Moved Troubleshooting
24 Posts 7 Posters 6.5k Views 7 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.
  • CoffeesnobC Offline
    CoffeesnobC Offline
    Coffeesnob
    wrote on last edited by
    #21

    Ok, so the new hardware has finally arrived and I have been pulling my hair out trying to get it working. It appears like there is something wrong in the way the node and the gateway are setting up. I didn't have this problem a couple of weeks ago but since I have upgraded to v2.1.1 the problem has manifested. I have seen that there are a number of posts that appear to have similar issues but not exactly the same. Perhaps somebody can shed some light.

    The setup is still exactly the same as I have described earlier in this post. I have a Mega and a Nano both with NRF24L01, I have a 10uf Cap across the power supplies of both radios, and I am 100% sure that the radios and the Arduinos are all working because I have built a NON Mysensor test sketch to prove this is all fine. Aside from that you can also see from the log transcript below that the units are actually talking. They just don’t seem to be able to complete the negotiation.

    So here is what I am seeing. in the log transcript below you can see that the two devices are talking to each other. the Bold text are the messages being sent from the gateway and the normal text is the messages being sent from the Node.

    0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
    0;255;3;0;9;TSM:INIT
    0;255;3;0;9;TSF:WUR:MS=0
    0;255;3;0;9;TSM:INIT:TSP OK
    0;255;3;0;9;TSM:INIT:GW MODE
    0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
    0;255;3;0;9;MCO:REG:NOT NEEDED
    0;255;3;0;14;Gateway startup complete.
    0;255;0;0;18;2.1.1
    0;255;3;0;9;MCO:BGN:STP
    0;255;3;0;9;MCO:BGN:INIT OK,TSP=1

    0 MCO:BGN:INIT REPEATER,CP=RNNRA--,VER=2.1.1
    3 MCO:BGN:BFR
    5 TSM:INIT
    6 TSF:WUR:MS=0
    12 TSM:INIT:TSP OK
    14 TSM:FPAR
    16 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:

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

    89 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0
    94 TSF:MSG:FPAR OK,ID=0,D=1
    2023 TSM:FPAR:OK
    2024 TSM:ID
    2025 TSM:ID:REQ
    2027 TSF:MSG:SEND,255-255-0-0,s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:

    0;255;3;0;9;TSF:MSG:READ,255-255-0,s=255,c=3,t=3,pt=0,l=0,sg=0:
    255;255;3;0;3;

    4035 TSM:ID
    4036 TSM:ID:REQ
    4038 TSF:MSG:SEND,255-255-0-0,s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:

    0;255;3;0;9;TSF:MSG:READ,255-255-0,s=255,c=3,t=3,pt=0,l=0,sg=0:
    255;255;3;0;3;

    4035 TSM:ID
    4036 TSM:ID:REQ
    4038 TSF:MSG:SEND,255-255-0-0,s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:

    0;255;3;0;9;TSF:MSG:READ,255-255-0,s=255,c=3,t=3,pt=0,l=0,sg=0:
    255;255;3;0;3;

    4035 TSM:ID
    4036 TSM:ID:REQ
    4038 TSF:MSG:SEND,255-255-0-0,s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:

    0;255;3;0;9;TSF:MSG:READ,255-255-0,s=255,c=3,t=3,pt=0,l=0,sg=0:
    255;255;3;0;3;

    10066 !TSM:ID:FAIL
    10067 TSM:FAIL:CNT=1
    10070 TSM:FAIL:PDT

    What you can clearly see here is that the initial node setup takes place, the request from the node to the gateway is received by the gateway and it reply’s. the node receives the reply and then it sends its reply, the Gateway receives the reply and then try to send an acknowledgment, but the node never gets the message. I suspect this is because the message being sent from the gateway is incomplete for some reason.

    For example the Node sends

    4038 TSF:MSG:SEND,255-255-0-0,s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:

    The gateway responds with
    0;255;3;0;9;TSF:MSG:READ,255-255-0,s=255,c=3,t=3,pt=0,l=0,sg=0:

    Which in and of its self doesn’t look exactly right to me, but as I am not the expert in this I am probably wrong.

    The gateway then prints 255;255;3;0;3; with nothing else in the line, this looks to me like its trying to send something but the message is empty.

    What are your thoughts? @mfalkvidd and @petewill I am hoping you guys can shed some light here.

    Thanks in advance.

    1 Reply Last reply
    0
    • hekH Offline
      hekH Offline
      hek
      Admin
      wrote on last edited by
      #22

      Which controller do you have setup with your gateway to answer the id requests from the node?

      1 Reply Last reply
      0
      • petewillP Offline
        petewillP Offline
        petewill
        Admin
        wrote on last edited by
        #23

        @Coffeesnob I didn't look at your logs in too much detail (I still don't have the codes memorized) but like @hek is noticing you may not be getting a node id back. You could also try assigning a static node ID like this:

        #define MY_NODE_ID 1
        

        Also, try adding a 40uF or 100uF capacitor to the radio. The new 2.1.1 library is much more efficient and can use more power in shorter periods (because it can transmit faster).

        My "How To" home automation video channel: https://www.youtube.com/channel/UCq_Evyh5PQALx4m4CQuxqkA

        1 Reply Last reply
        0
        • CoffeesnobC Offline
          CoffeesnobC Offline
          Coffeesnob
          wrote on last edited by
          #24

          Thanks heaps @Hek and @petewill I didn't realise that without the controller running I will not get a node id. I thought incorrectly the node id came from the gateway. I booted up MYSController and it now works as expected. thanks for pointing me in the right direction..

          cheers until next time.

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


          20

          Online

          11.7k

          Users

          11.2k

          Topics

          113.1k

          Posts


          Copyright 2025 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