You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please allow the printing of RSSI values. (Weird negative strength values where the larger values ie closer to zero mean the radio signal is stronger. So RSSI -36 is a stronger signal than RSSI -90) It is really useful to be able to read the RSSI for signal strength at the device instead of relying on information from the LoRaWan network.
Typically the call would be something like
LoRaRadio.packetRssi()
Can we allow the MKRWAN library to show the RSSI values?
The text was updated successfully, but these errors were encountered:
Yes, it makes absolute sense if you want to know more about your network. The Server-side reports the signal strength of incoming data from your device. The device, yet, reports the signal strength of the incoming packet. RSSI is negative as it is the (relative) ratio of the transmitted signal vs. the received in decibel (logarithmic). Also, consider the SNR value as well. I used this formula for a user interface to simplify RSSI and SNR to a 0-100% value. >50% is considered good.
-136dBm is the sensitivity of the receiver, -20dB is the margin for signal/noise.
This call among many others is implemented in the not yet released v1.2.4 of my pull request. It includes the necessary modem firmware update in the MKRWAN standalone sketch.
Feature Request: Allow printing the RSSI values
Please allow the printing of RSSI values. (Weird negative strength values where the larger values ie closer to zero mean the radio signal is stronger. So RSSI -36 is a stronger signal than RSSI -90) It is really useful to be able to read the RSSI for signal strength at the device instead of relying on information from the LoRaWan network.
Typically the call would be something like
Can we allow the MKRWAN library to show the RSSI values?
The text was updated successfully, but these errors were encountered: