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

LoraPhy should be in RX mode instead of STANDBY during reception windows #181

Open
Thomas-Durand opened this issue Oct 31, 2024 · 1 comment

Comments

@Thomas-Durand
Copy link

Hello,

I have a question/concern regarding the LoRa Phy model. In the NS3 code and documentation, the following requirement is listed:

  • The receiver must be idle (in STANDBY state) when the StartReceive function is called;

My concern is, that this does not represent a realistic model of the LoRa Phy. Should the device not be in receive (RX) mode to start the demodulation of a Packet? In the publication below, actual power consumption measurements were taken, and the device is in the RX mode (IDDR_L) irrespective of whether an acknowledge packet was received in the RX1 slot.
https://www.researchgate.net/publication/320435869_Modeling_the_energy_performance_of_LoRaWAN

Possibly the NS3 model could rather use a "reception" flag to indicate whether it is actively busy listening to a packet being received.

The advantage I see of being in RX mode rather than just IDLE would be that the power consumption model would be a bit more accurate.

@non-det-alle
Copy link
Collaborator

Hi, I also checked the SX1272 chip datasheet and it seems to be the case. I am adding this to the list of TODO tasks.

Regarding implementation, I also agree that a "busy" flag would be a good solution to avoid having a device PHY layer locking onto multiple transmissions.

@non-det-alle non-det-alle changed the title LoRa Phy StartReceive LoraPhy should be in RX mode instead of STANDBY during reception windows Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants