Skip to content

Troubleshooting: confirm nanoCUL is transmitting OK

David Bonnes edited this page Jul 16, 2022 · 1 revision

To check that your nanoCUL is transmitting OK, look in the packet log for lines like these:

2021-02-05T23:17:45.242783 095 RQ --- 18:013393 01:145038 --:------ 000C 002 0208 
2021-02-05T23:17:45.260453 046 RP --- 01:145038 18:013393 --:------ 000C 006 02080010DAFB 

Note the RQ (request) from the 18:xxxxxx (nanoCUL or similar) to the 01:xxxxxx (controller), and the corresponding RP (same code, 000C).

If things are not working well, you'll see (I have added a blank line):

2021-02-05T23:17:46.892674 095 RQ --- 18:013393 01:145038 --:------ 000C 002 0604 
2021-02-05T23:17:47.121780 095 RQ --- 18:013393 01:145038 --:------ 000C 002 0604 
2021-02-05T23:17:47.555623 095 RQ --- 18:013393 01:145038 --:------ 000C 002 0604 
2021-02-05T23:17:48.387454 095 RQ --- 18:013393 01:145038 --:------ 000C 002 0604 

2021-02-05T23:17:48.509517 095 RQ --- 18:013393 01:145038 --:------ 0004 002 0600 ```

Note the four attempts to send an RQ before it gives up and codes to the next code (0004, zone name)

Now the question is: are all RQ being 'lost', or are some getting an RP:

2021-02-05T23:17:48.478006 048 RP --- 01:145038 18:013393 --:------ 000C 006 0604008A145D 

2021-02-05T23:17:48.478006 091 RP --- 01:145038 18:013393 --:------ 000C 006 0604008A145D 

Note the difference in RSSI between these two - the first is 048, suggesting good reception, the other is 095 suggesting poor reception.