ABP with LMIC on Arduino does not work

Hello everybody,

currently I am setting up Chirpstack in Kubernetes.
For development purposes I use a Sparkfun 1CH Gateway that is equipped with the things4u Gateway OS. So far I have been able to connect the gateway with Chirpstack.

Now I tried to connect an Adafruit Feather M0 LoRa using the MCCI LoRaWAN LMIC Library with ABP but I have not been successful so far.
In the serial monitor I see that the device is queuing the packages:

22:26:09.519 -> 93306977: EV_TXSTART
22:26:09.679 -> Packet queued
22:26:11.645 -> 93437956: EV_TXCOMPLETE (includes waiting for RX windows)

The packages seem to never arrive in Chirpstack, the device I added has never been seen according to the device overview.

Is there a sample available on how to add the Device Adress, Network Session Key and Application Session Key in the ttn-abp-sample of the LMIC-library?
Could it be that I entered them in the wrong manner (all MSB)?

Example of how I currently added the constants in the ttn-abp-example:

// LoRaWAN NwkSKey, network session key
// This should be in big-endian (aka msb).
static const PROGMEM u1_t NWKSKEY[16] = { 0xF9, 0XE2, 0x5D, 0x09, 0x8F, 0x04, 0x21, 0x89, 0x77, 0x19, 0x79, 0xDF, 0XA3, 0x81, 0x3B, 0XB7 };

// LoRaWAN AppSKey, application session key
// This should also be in big-endian (aka msb).
static const u1_t PROGMEM APPSKEY[16] = { 0x15, 0xB7, 0xFD, 0xE7, 0xDC, 0x74, 0x53, 0x83, 0x04, 0xBB, 0xCB, 0x0B, 0xD4, 0xC7, 0xA1, 0xFD };

// LoRaWAN end-device address (DevAddr)
// See http://thethingsnetwork.org/wiki/AddressSpace
// The library converts the address to network byte order as needed, so this should be in big-endian (aka msb) too.
static const u4_t DEVADDR = 0x004F4824;

Any help is appreciated :slight_smile:

Best regards,

This is going to cause lots of compatibility problems often leading the the raw packets never being received (vs later problems decoding/interpreting them) and because it’s really not LoRaWAN and something that should be strongly discouraged and may lead to airtime violations means few will be willing to help you debug those.