Hot![RN2XX3] P2P communication - Issue

Author
DPerez
Junior Member
  • Total Posts : 81
  • Reward points : 0
  • Joined: 2014/01/15 00:26:02
  • Location: 0
  • Status: offline
2018/10/08 00:47:52 (permalink)
0

[RN2XX3] P2P communication - Issue

Hello there,

We are attempting a communication between two devices through radio P2P capability when suddenly, we find something rather weird.

The scenario has two devices, where one is sending a single packet every "X" minutes (working as it is expected... or we have noticed nothing bizarre yet), and the other one is in continuous reception mode with a watchdog set in order not to be always blocked (it is an exit way) -> for instance, a 20 seconds wdt and infinite rx mode.

When the watchdog timer expires, the module answers with "radio_err", and when a packet is received its answer is "radio_rx" with the payload, being by this available to receive new commands. This procedure is fine because it works at the beginning... but in the end, the receptor gets stuck without any reason, and its behaviour is stopping answering to any rx commands where its unique solution is removing its voltage, feeding it and restarting the whole process again.

It does not matter what parameters are set to the receiver device (wdt, crc, and so on), it always happens the same. We have the gut feeling that it looks like a watchdog timer issue but... who knows!

We are well aware that P2P communication is not supported by Microchip, but any help to understand what is going on would be great. Looking forward to your replies.

Best regards.
Daniel.
#1

1 Reply Related Threads

    DPerez
    Junior Member
    • Total Posts : 81
    • Reward points : 0
    • Joined: 2014/01/15 00:26:02
    • Location: 0
    • Status: offline
    Re: [RN2XX3] P2P communication - Issue 2018/10/10 23:41:16 (permalink)
    0
    Hello guys,
     
    We bring a clue about this issue. In the very first version, these were the commands that the receptor was executing in its initialization:
    1. mac pause
    2. radio set mod fsk
    3. radio set freq 915000000
    4. radio set pwr 20
    5. radio set sf sf12
    6. radio set crc on
    7. radio set iqi on
    8. radio set cr 4/5
    9. radio set sync 34
    10. radio set bw 250
    11. radio rx 0
    12. Point 11 is repeated always from here.
     
    But as we said, this did not work as it should be. After making many tests, one of them has been a success, because the device has been working for 1 day and a half (when the others, its maximum was 1 hour each one). It could be summarized in that we have erased 4 lines of code, which means 4 commands less, being by this the following final sequence:
    1. mac pause
    2. radio set mod fsk
    3. radio set freq 915000000
    4. radio set pwr 20
    5. radio set sf sf12
    6. radio set bw 250
    7. radio rx 0
    8. Point 7 is repeated always from here.
     
    So, we would like to know why are these commands useful for a P2P communication, and the most important thing, which one of them is the troubled (or there are more that just one).
     
    Thanks in advance! Looking forward to hearing from you.
     
    Best regards.
    Daniel.
     
    #2
    Jump to:
    © 2019 APG vNext Commercial Version 4.5