Amazing project, Jeorg! I'll be studying/dissecting it for months. Thank you for all of your efforts in assisting bees and beekeepers!
I'm in REGION_US915 and connecting with TTN using the required 2nd sub-band. I am in a LoRa wasteland with no gateway within 50 miles. For development/learning I am using a CubeCell node with a Heltec HT-M00, indoor 2-channel gateway.
In the Heltec CubeCell example sketches I specify frequencies 1 and 2 in the second sub-band as follows:
_uint16t userChannelsMask[6] = { 0x0300, 0x0000, 0x0000, 0x0000, 0x0000, 0x0000 };
Can you recommend a strategy to restrict join/transmit in a similar way? I am seeing numerous, conflicting instruction for editing lmic.h with "...NO NO NO if you do that..." warnings (not to mention stern admonishments from LoraWan Paladins regarding non-compliant gateways).
Anyway, thank you for such an awesome app. If you cannot offer a suggestion I will begin hacking at lmic.h :)
Amazing project, Jeorg! I'll be studying/dissecting it for months. Thank you for all of your efforts in assisting bees and beekeepers!
I'm in REGION_US915 and connecting with TTN using the required 2nd sub-band. I am in a LoRa wasteland with no gateway within 50 miles. For development/learning I am using a CubeCell node with a Heltec HT-M00, indoor 2-channel gateway.
In the Heltec CubeCell example sketches I specify frequencies 1 and 2 in the second sub-band as follows: _uint16t userChannelsMask[6] = { 0x0300, 0x0000, 0x0000, 0x0000, 0x0000, 0x0000 };
Can you recommend a strategy to restrict join/transmit in a similar way? I am seeing numerous, conflicting instruction for editing lmic.h with "...NO NO NO if you do that..." warnings (not to mention stern admonishments from LoraWan Paladins regarding non-compliant gateways).
Anyway, thank you for such an awesome app. If you cannot offer a suggestion I will begin hacking at lmic.h :)