esib_iot_challenge
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
esib_iot_challenge [2017/05/17 17:32] – [3. Devices] samer | esib_iot_challenge [2017/05/17 17:43] – [1. Platform] samer | ||
---|---|---|---|
Line 14: | Line 14: | ||
[{{ : | [{{ : | ||
- | <WRAP left help 100%> | + | <WRAP left help 75%> |
* Where is the LoRa modulation implemented on the platform? | * Where is the LoRa modulation implemented on the platform? | ||
* What are the advantages of the LoRa modulation? | * What are the advantages of the LoRa modulation? | ||
Line 54: | Line 54: | ||
</ | </ | ||
+ | Download the example sketch and open it with Arduino IDE. Now you should configure your device with the same identifiers as in the backend. | ||
+ | |||
+ | <WRAP center round tip 100%> | ||
+ | Note that the device and application identifiers should be in little endian format. The application key is in big endian format. For example, '' | ||
+ | </ | ||
+ | |||
+ | |||
+ | <code c++> | ||
+ | static const u1_t PROGMEM APPEUI[8]= { }; | ||
+ | void os_getArtEui (u1_t* buf) { memcpy_P(buf, | ||
+ | |||
+ | // This should also be in little endian format, see above. | ||
+ | static const u1_t PROGMEM DEVEUI[8]= { }; | ||
+ | void os_getDevEui (u1_t* buf) { memcpy_P(buf, | ||
- | Download the example sketch, open it with Arduino IDE and compile it. | + | static const u1_t PROGMEM APPKEY[16] = { }; |
+ | void os_getDevKey (u1_t* buf) { memcpy_P(buf, APPKEY, 16);} | ||
+ | </ | ||
You can download the following sketch {{ : | You can download the following sketch {{ : |
esib_iot_challenge.txt · Last modified: 2021/08/28 09:53 by samer