Ping Pong with ESP8266 results in !TSM:FPAR:NO REPLY [solved]



  • Hello,

    I have 2 identical ESP8266 Node MCU's. Each has the Ping Pong example sketch installed to it.

    Now I'm getting a lot of Find Parent errors:

    TSM:INIT
    TSM:INIT:TSP OK
    TSM:INIT:STATID=201
    TSF:SID:OK,ID=201
    TSM:FPAR
    TSF:MSG:SEND,201-201-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    !TSM:FPAR:NO REPLY
    TSM:FPAR
    TSF:MSG:SEND,201-201-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    !TSM:FPAR:NO REPLY
    TSM:FPAR
    TSF:MSG:SEND,201-201-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    !TSM:FPAR:NO REPLY
    TSM:FPAR
    TSF:MSG:SEND,201-201-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    !TSM:FPAR:FAIL
    TSM:FAIL:CNT=7
    

    Why does a ping pong sketch between 2 nodes ask for a parent?

    What is needed to find the parent?

    Thanks!

    edit: updating the controller to the latest version has fixed the issue.


  • Mod

    I think one needs to have ID 0 and the other ID 1 if I remember well... but I never used it. Did you check already https://www.mysensors.org/build/debug ?



  • Yes, I checked the debug page.

    I followed all the documented steps:

     *  To use this sketch, assemble MySensors nodes - they need nothing more than a radio
     *  1.  Flash each node with the same sketch, open the console and type either 0 or 1 to the respective nodes to set thei ID
     *  2.  You only need to set the node id once, and restart the nodes
     *  3.  To being a ping-pong test, simply type T in the console for one of the nodes.
    

    Some documentation is missing:

    • You need to set the MY_NODE_ID to 201 or 200 when using it with ESP8266
    • You also need a Gateway, even when testing Node to Node ping pong

    It's not clear what the expected result is, I'd expect something like Ping from node 200, then Pong! from node 201. But it would seem that it gives "Ying node", then "Yang node".


  • Mod

    Besides the ping pong sketch, did you have trouble running normal gateway sketch and adding the other esp8266 as node?



  • @gohan not sure if I understand your question since I don't know what can be expected from the Gateway?

    Here's the gateway log:

    0;255;3;0;9;MCO:BGN:INIT GW,CP=RRNGE--,VER=2.1.1
    0;255;3;0;9;TSF:LRT:OK
    0;255;3;0;9;TSM:INIT
    0;255;3;0;9;TSF:WUR:MS=0
    scandone
    state: 0 -> 2 (b0)
    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
    state: 2 -> 3 (0)
    state: 3 -> 5 (10)
    add 0
    aid 6
    cnt 
    chg_B1:-40
    f r-40, 
    connected with Airport, channel 6
    dhcp client start...
    scandone
    .chg_B1:-80
    ............ip:192.168.0.164,mask:255.255.255.0,gw:192.168.0.1
    .IP: 192.168.0.164
    0;255;3;0;9;MCO:BGN:STP
    0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
    IP: 192.168.0.164
    0;255;3;0;9;Attempting MQTT connection...
    0;255;3;0;9;MQTT connected
    0;255;3;0;9;Sending message on topic: mygateway1-out/0/255/0/0/18
    pm open,type:2 0
    

    I see the following in the mqtt log:

    mygateway1-out/0/255/0/0/18 2.1.1
    

  • Mod

    I forgot to ask: are you using any nrf24 or rfm69 radio or are you trying to make the esp8266 talk to each other over wifi?



  • @gohan i'm using rfm69. Somehow I got it to work with one ESP gateway and 2 ESP nodes. All three have an rfm69 chip. I don't understand why you need a gateway to do ping pong?


  • Mod

    The mysensors protocol relies on the gateway, you can't do without it unless you are using other ping pong code that are not relying on mysensors.



  • @gohan then shouldn't there be a note in the documentation of the ping pong sketch about this?


  • Mod

    I'll take a look



  • @gohan thanks!


  • Mod

    Actually it is explained in this page how the mysensors network works, but I'll see how to add a line in the example sketch



  • @gohan thanks for the feedback. According to that page it seems you not only need a gateway but also a controller. This explains why my nodes don't get a node id automatically.


  • Mod

    The controller is needed for auto ID, but it can also be used myscontroller. It is also written in different places that manual id should be set also in case of problems.



  • @gohan indeed you're right. What did you mean with "myscontroller"?

    Setting the node id manually for the ping pong sketch makes them communicate to the Gateway:

    #define MY_NODE_ID 201
    

    Would auto ID work with the ESP MQTT Gateway and OpenHab controller?

    I have an MQTT server up and running and OpenHab is installed with the following configuration in /etc/openhab2/services/mqtt.cfg:

    broker.url=tcp://127.0.0.1:1883
    broker.clientId=OpenHab
    broker.retain=true
    broker.async=false
    

    Yet I still get !TSM:FPAR:NO REPLY


  • Mod

    https://forum.mysensors.org/topic/838/windows-gui-controller-for-mysensors

    I'd start from the ethernet gateway and work it out from there, myscontroller works with ethernet gateway. In openhab I don't know how to enable auto id, but there must be something in documentation. To be honest assigning manually ID has to be done only once because it is saved in eeprom and read at every boot, so I don't see it so mandatory to have the controller handling it.



  • @gohan, do you mean http://www.mycontroller.org? I can't find any project page with downloads on the link you provided. There is a download link to a zip file somewhere in the comments but impossible to say if that is still up to date as it dates from 2015.


  • Mod

    yes, it's the zip file. It is a windows app. Mycontroller it is actually a controller like Domoticz or Openhab. I know it is a little old, but it works.



  • @gohan, I switched over to mycontroller (from OpenHab) and I'm using Arduino's nodes and I'm still getting errors not finding the parent.

    I'm using the Mock sketch and tested with setting the ID manually but no luck.

    0 MCO:BGN:INIT NODE,CP=RRNNA--,VER=2.1.1
    4 TSM:INIT
    4 TSF:WUR:MS=0
    108 TSM:INIT:TSP OK
    110 TSM:INIT:STATID=99
    112 TSF:SID:OK,ID=99
    114 TSM:FPAR
    3241 TSF:MSG:SEND,99-99-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    5249 !TSM:FPAR:NO REPLY
    5251 TSM:FPAR
    8378 TSF:MSG:SEND,99-99-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    10385 !TSM:FPAR:NO REPLY
    10387 TSM:FPAR
    13514 TSF:MSG:SEND,99-99-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    15521 !TSM:FPAR:NO REPLY
    15523 TSM:FPAR
    

    Edit: adding a 4.7 capacitor didn't change this. Neither did downgrading to 2.0.

    Starting sensor (RRNNA-, 2.0.0)
    TSM:INIT
    TSM:RADIO:OK
    TSP:ASSIGNID:OK (ID=254)
    TSM:FPAR
    TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
    TSM:FPAR
    TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
    TSM:FPAR
    TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
    TSM:FPAR
    TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
    !TSM:FPAR:FAIL
    !TSM:FAILURE
    TSM:PDT
    TSM:INIT
    TSM:RADIO:OK
    TSP:ASSIGNID:OK (ID=254)
    TSM:FPAR
    TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
    TSM:FPAR
    TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
    TSM:FPAR
    TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
    TSM:FPAR
    TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
    !TSM:FPAR:FAIL
    !TSM:FAILURE
    TSM:PDT
    TSM:INIT
    TSM:RADIO:OK
    TSP:ASSIGNID:OK (ID=254)
    TSM:FPAR
    TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
    TSM:FPAR
    TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
    TSM:FPAR
    TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
    

    Any idea?


  • Mod

    On the gateway do you see any message received? Can you post the gateway log when nodes are registering?



  • @gohan, when using the WemosD1 (without capacitor!) and a static ID, I get the following:

    0;255;3;0;9;TSF:MSG:READ,253-253-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=253
    0;255;3;0;9;TSF:PNG:SEND,TO=0
    0;255;3;0;9;TSF:CKU:OK
    0;255;3;0;9;TSF:MSG:GWL OK
    0;255;3;0;9;TSF:MSG:SEND,0-0-253-253,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
    0;255;3;0;9;TSF:MSG:READ,253-253-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
    0;255;3;0;9;TSF:MSG:PINGED,ID=253,HP=1
    0;255;3;0;9;TSF:MSG:SEND,0-0-253-253,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
    0;255;3;0;9;TSF:MSG:READ,253-253-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
    0;255;3;0;9;TSF:MSG:SEND,0-0-253-253,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
    0;255;3;0;9;TSF:MSG:READ,253-253-0,s=255,c=0,t=17,pt=0,l=5,sg=0:2.1.1
    0;255;3;0;9;Sending message on topic: mpp-mygateway1-out/253/255/0/0/17
    

    When I do the same for the Pro Mini, there is nothing to see. When I flash a Moteino test sketch it works properly.


  • Mod

    @mpp the gateway is getting the message and it replies so you could either have a power issue on gateway or range problem. How far are the gw and node?



  • @gohan tested with less than a meter up to 10 meters. In fact the Wemos Node now is working as it shows up in mycontroller but the Pro Mini doesn't receive a response from the GW.


  • Mod

    Do you have other radio modules to try? If not, if you swap the radios do you see any changes? Are the radio rfm69 right?



  • @gohan I have several RFM69 radio's and they're all working (with the Moteino sketch) on a Pro Mini.

    Here's my config:

    #define MY_RADIO_RFM69
    #define MY_RFM69_FREQUENCY RF69_433MHZ
    #define MY_IS_RFM69HW
    #define MY_RF69_IRQ_PIN 4
    #define MY_RF69_IRQ_NUM MY_RF69_IRQ_PIN
    #define MY_RF69_SPI_CS 15
    #define MY_RFM69_NETWORKID 99
    #define MY_NODE_ID 123
    


  • Removing some of the config lines seems to have an effect:

    0 MCO:BGN:INIT NODE,CP=RRNNA--,VER=2.1.1
    4 TSM:INIT
    4 TSF:WUR:MS=0
    8 TSM:INIT:TSP OK
    10 TSF:SID:OK,ID=254
    12 TSM:FPAR
    143 TSF:MSG:SEND,254-254-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    1232 TSF:MSG:READ,0-0-254,s=255,c=3,t=8,pt=1,l=1,sg=0:0
    1239 TSF:MSG:FPAR OK,ID=0,D=1
    2150 TSM:FPAR:OK
    2150 TSM:ID
    2152 TSM:ID:OK
    2154 TSM:UPL
    2285 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
    2314 TSF:MSG:READ,0-0-254,s=255,c=3,t=8,pt=1,l=1,sg=0:0
    2320 !TSF:MSG:LEN,0!=8
    2435 TSF:MSG:READ,0-0-254,s=255,c=3,t=25,pt=1,l=1,sg=0:1
    2441 TSF:MSG:PONG RECV,HP=1
    2443 TSM:UPL:OK
    2445 TSM:READY:ID=254,PAR=0,DIS=1
    2580 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=NACK:0100
    2717 TSF:MSG:READ,0-0-254,s=255,c=3,t=0,pt=1,l=1,sg=0:1
    2723 !TSF:MSG:LEN,0!=8
    2795 TSF:MSG:READ,0-0-254,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
    2936 !TSF:MSG:SEND,254-254-0-0,s=255,c=0,t=17,pt=0,l=5,sg=0,ft=1,st=NACK:2.1.1
    3076 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=6,pt=1,l=1,sg=0,ft=2,st=NACK:0
    3110 TSF:MSG:READ,0-0-254,s=255,c=3,t=0,pt=6,l=2,sg=0:0100
    3117 !TSF:MSG:LEN,0!=9
    Send Sketch Info: 5197 TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=11,pt=0,l=14,sg=0,ft=3,st=OK:MockMySensors 
    5341 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=12,pt=0,l=4,sg=0,ft=0,st=NACK:v0.5
    MockMySensors v0.5
    5480 TSF:MSG:READ,0-0-254,s=255,c=3,t=0,pt=6,l=2,sg=0:0100
    5486 !TSF:MSG:LEN,0!=9
    Get Config: Metric
    Presenting Nodes
    ________________
      S_DOOR
    6375 TSF:MSG:SEND,254-254-0-0,s=1,c=0,t=0,pt=0,l=12,sg=0,ft=1,st=OK:Outside Door
    ________________
    6434 MCO:REG:REQ
    6567 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=NACK:2
    6664 TSF:MSG:READ,0-0-254,s=255,c=3,t=0,pt=6,l=2,sg=0:0100
    6670 !TSF:MSG:LEN,0!=9
    6744 TSF:MSG:READ,0-0-254,s=255,c=3,t=27,pt=1,l=1,sg=0:1
    6750 MCO:PIM:NODE REG=1
    6752 MCO:BGN:STP
    GW Started
    7254 MCO:BGN:INIT OK,TSP=1
    
    
    
    #########################
    RandomNumber:36
    Send Battery Level
    7290 TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=0,pt=1,l=1,sg=0,ft=1,st=OK:36
    Request Time
    7929 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=1,pt=0,l=0,sg=0,ft=0,st=NACK:
    Door is: Open
    8509 TSF:MSG:SEND,254-254-0-0,s=1,c=1,t=16,pt=2,l=2,sg=0,ft=1,st=OK:1
    System is: Armed
    8646 !TSF:MSG:SEND,254-254-0-0,s=1,c=1,t=15,pt=1,l=1,sg=0,ft=0,st=NACK:1
    8783 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=0,pt=1,l=1,sg=0,ft=1,st=NACK:36
    8792 TSF:MSG:READ,0-0-254,s=255,c=3,t=27,pt=1,l=1,sg=0:1
    8798 !TSF:MSG:LEN,0!=8
    #########################
    

    So now the node is sending data but there's no ack/Invalid message length.


  • Mod

    Are they RFM69HW? What antenna are you using on them?



  • @gohan they're all HW, yes. I tested with single wire and coil antenna's. Atm I'm testing with authentic Moteino's with single wire. They all result in !TSM:FPAR:FAIL.



  • @mpp said in Ping Pong with ESP8266 results in !TSM:FPAR:NO REPLY [solved]:

    So now the node is sending data but there's no ack/Invalid message length..

    @gohan they're all HW, yes. I tested with single wire and coil antenna's. Atm I'm testing with authentic Moteino's with single wire. They all result in !TSM:FPAR:FAIL.

    Any progress on this front? I got the exact same things as the log you posted; loads of NACK's.
    Checked/replaced radios, antennes and caps ..


 

384
Online

8.0k
Users

8.8k
Topics

94.4k
Posts