-
Notifications
You must be signed in to change notification settings - Fork 60
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
AS923 Support #225
Comments
OK, so we figured we need to implement the new region in the RegionManager using https://lora-alliance.org/sites/default/files/2018-04/lorawantm_regional_parameters_v1.1rb_-_final.pdf as reference, correct? |
Hello! Thank you for the interest, yes you are Correct. I tried here below to list the changes needed to implement a new region. In case you have questions or you need additional help, I'd be happy to help you out.
|
Hi @Mandur I've also sent you an invite to connect on Skype. Here are my responses to your last post:
Based on our initial testing, C2D messages are still not making it downstream. On the log, I see the following being inferred/resolved by the kit incorrectly:
Values used look incorrect - they should have been rx2dr = 2 and datr = SF10BW125. Per specs => The RX2 receive window uses a fixed frequency and data rate. The default parameters are 923.2 MHz / DR2 (SF10/125KHz). which is what we've coded for the region:
How does the kit resolve the region to use for a downstream message? Using the last upstream message from the device (our device sends some sort of status/heartbeat message every hour)? The log entry above seems to have come from the following lines of code in Region.cs:
RX2 value it's using seems incorrect. We've set the RX2DataRate property for the device twin to "2" - so it's in the desired properties but currently not in the reported properties. Our device is class C, ABP device. These are the log entries from last hourly upstream message from the device:
The last downstream message we sent C2D logged the following entries, but it doesn't look like it reached the device since we didn't see expected result:
|
Here's the device twin info:
|
@jsaez868 Would you still be interrested in merging the AS923 frequency plan with upstream? |
Is your feature request related to a problem? Please describe.
Support of AS923 frequency range
Describe the solution you'd like
LoRa starter kit should support AS 923 freq range
Describe alternatives you've considered
N/A
Additional context
Requested by community
The text was updated successfully, but these errors were encountered: