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
If one uses the rf230 with software ACKs,
then there are two possibilities in order to estimate
the received signal power, see RF230DriverLayerP.nc.
If F230_RSSI_ENERGY is not defined, then
PacketRSSI is set to the value of register PHY_RSSI (RSSI), see line 785;
otherwise, it is set to the value of register PHY_ED_LEVEL (Energy Detection), see line 746.
However, if one uses hardware ACKs, then there is no such choice and always Energy Detection, i.e., register PHY_ED_LEVEL, is used.
In contrast, for example both driver layers (software and hardware ACK) of atm128rfa1 support RSSI and Energy Detection.
The text was updated successfully, but these errors were encountered:
If one is using HW acks, I'm not sure if there is a way to get the RSSI out. There needs to be a mechanism to indicate that a packet has been received and here is the RSSI value. Not sure how that works when doing HW acks.
I'm not using the RF230, rather we are using the SiLabs si4468 radio.
As far as my limited understanding goes,
one can get an RSSI value any time in receive states,
like it is implemented in RFA1DriverHwAckP.nc line 701.
However, in extended operating mode (i.a. hardware ACKs) it is not recommended.
So, is there any deeper reason why the rf230 hardware ACK driver layer does not support
RSSI, whereas it is supported by the rfa1 hardware ACK driver layer?
If one uses the rf230 with software ACKs,
then there are two possibilities in order to estimate
the received signal power, see RF230DriverLayerP.nc.
PacketRSSI is set to the value of register PHY_RSSI (RSSI), see line 785;
otherwise, it is set to the value of register PHY_ED_LEVEL (Energy Detection), see line 746.
In contrast, for example both driver layers (software and hardware ACK) of atm128rfa1 support RSSI and Energy Detection.
The text was updated successfully, but these errors were encountered: