-
Notifications
You must be signed in to change notification settings - Fork 212
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
Add AU915 plan & setting #341
Conversation
AVR fails CI. We also need documentation to explain why this is needed, etc. Updates to README.md. Aslso see comments on commit it looks like some things have regressed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks very much for the contribution. Please see my comments. We also need to update the documentation.
@@ -421,6 +468,7 @@ enum { | |||
HDR_FTYPE_DADN = 0x60, // data (unconfirmed) dn | |||
HDR_FTYPE_DCUP = 0x80, // data confirmed up | |||
HDR_FTYPE_DCDN = 0xA0, // data confirmed dn | |||
HDR_FTYPE_REJOIN = 0xC0, // rejoin for roaming |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a regression, as it's not part of the LoRaWAN 1.0.3 spec. Please remove.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry this might have been an oversight on making the device work.
@@ -64,6 +64,7 @@ Revision history: | |||
// constants for comparison | |||
#define LMIC_REGION_eu868 1 | |||
#define LMIC_REGION_us915 2 | |||
#define LMIC_REGION_au915 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be a unique value. By convention, these match the subsections in the LoRaWAN regional spec.I've not had a chance to review the updates that enable AU915. Because the regulatory regime is different, even if this is identical to US915, we need to think about keeping it separate here. (There's no necessary connection, it's just an interesting fact.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its the same band per se, the US ISM actually starts lower.
so we are not able to use the first sub band,
One other difference is the use of EIRP here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Scobber What document defines AU915 (as opposed to "AU915-928", which is defined by section 2.6 of the LoRaWAN regional parameters document)?
This is important because we (architecturally) must use a new value for LMIC_REGION_au915
-- we can't use 2
because it's already in use. I just checked the latest regional specs, and this doesn't seem to be published. Is this something the LoRa Alliance defined, or something someone else defined? Thanks!
@@ -1,6 +1,7 @@ | |||
// project-specific definitions | |||
//#define CFG_eu868 1 | |||
#define CFG_us915 1 | |||
#define CFG_au915 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we shouldn't change this in lmic_project_config.h, I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah i agree, i committed what i use here. i probably should have sent //#define CGG_au915 instead
Add band plan and defines that enable AU915