Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rf230: missing option for determining received signal power via PHY_RSSI when using hardware ACKs #388

Open
miri-in opened this issue Dec 1, 2016 · 4 comments

Comments

@miri-in
Copy link
Contributor

miri-in commented Dec 1, 2016

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.

@cire831
Copy link
Member

cire831 commented Dec 2, 2016

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.

@miri-in
Copy link
Contributor Author

miri-in commented Dec 5, 2016

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?

Thank you for your time!

@cire831
Copy link
Member

cire831 commented Dec 5, 2016

sorry, no idea. its been too long since i looked at it. have you taken a look at the datasheets?

@miri-in
Copy link
Contributor Author

miri-in commented Dec 6, 2016

I haven't read them in-depth yet, but perhaps this would be the right next step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants