Serial gateway and NRF24 and repeater mode



  • I have a serial gateway with one nodeid=20 running for some time with no problems.
    Getting comms problems with a second nodeid=22 when added to the same gateway.

    Below is the debug log from nodeid=22 with the communication problems.
    On the 4th line is a READ from nodeid=20. I don't have REPEATER MODE defined!
    There is also a broadcast message MSG:BC

    What could be wrong here?

    124187 !TSF:SND:TNR
    124194 MCO:SLP:MS=6000,SMS=0,I1=255,M1=255,I2=255,M2=255
    124199 !MCO:SLP:TNR
    124436 TSF:MSG:READ,20-20-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
    124441 TSF:MSG:BC
    124585 TSF:MSG:READ,0-0-22,s=255,c=3,t=8,pt=1,l=1,sg=0:0
    124591 TSF:MSG:FPAR OK,ID=0,D=1
    126053 TSM:FPAR:OK
    126054 TSM:ID
    126056 TSM:ID:OK
    126057 TSM:UPL
    126095 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
    126220 TSF:MSG:READ,0-0-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
    126225 TSF:MSG:BC
    126537 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=21,pt=1,l=1,sg=0,ft=1,st=NACK:0
    126647 TSF:MSG:READ,0-0-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
    126652 TSF:MSG:BC
    127391 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=21,pt=1,l=1,sg=0,ft=2,st=NACK:0
    128102 TSM:UPL
    128139 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=3,st=NACK:1
    128690 TSF:MSG:READ,0-0-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
    128695 TSF:MSG:BC
    129430 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=21,pt=1,l=1,sg=0,ft=4,st=NACK:0
    130147 TSM:UPL
    130184 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=5,st=NACK:1```

  • Mod

    @peerv the log parser can be useful.

    Node 20 sends a broadcast message. Broadcast messages are received by all nodes, including node 22. Since node 22 is not a repeater, node 22 does not send a reply to node 20. That's just normal operation.

    However, when node 22 sends a reply to the gateway's I_DISCOVER_REQUEST, the reply is not acknowledged (st=NACK). See https://forum.mysensors.org/topic/666/debug-faq-and-how-ask-for-help for a troubleshooting flowchart with the most common causes. Power is top 1, 2 and 3 on that list.

    How is your node powered?
    The debug logs from the gateway will probably be very useful for troubleshooting.



  • @mfalkvidd Thanks for confirming about the BC message being normal protocol.
    I have used the log parser (great!) and the trouble shooting flowchart (great!).
    I am currently powering thru USB but as the comms problem is intermittend I need some further investigation.


 

423
Online

7.9k
Users

8.8k
Topics

94.3k
Posts