The problem I met is zero value of rssi in some of promisc_callback user data.
the rssi field in userdata
To be detailed, when I set the module in promisc mode, and use AT command ATWM to capture the packet in the air. I find some of captured packet (rssi field in userdata of promisc_callback) returns zero, while most of cases, the value is valid in range of -128 ~ -1. So, I wonder why it returns zero, what does it mean?
BTW: The ambd_sdk version is master of github. The module is BW16 hardware.
Thank you @Jeffery . We are checking this issue. Any example from the SDK, you are running? So I can re-produce the issue.
I’m testing the
static void promisc_test(int duration, unsigned char len_used) in wifi_promisc.c. To figure out the captured package, I add some logging printf in this function. It will print the rssi value.
This function is called in fATWM, which could be triggered by AT command ATWM.
The code is master branch of github GitHub - ambiot/ambd_sdk: SDK for AmebaD
Hi @Jeffery, you can try to use the code in the release branch of Github: GitHub - ambiot/ambd_sdk at release