Led flickering

I loaded the blink code and it’s fine. It blinks on/off

23:52:12.969 -> LED OFF....
23:52:12.969 -> LED ON....
23:52:12.969 -> LED OFF....
23:52:12.969 -> LED ON....

However I do get the following error very frequently and I have to push the reset button. It takes sometimes 2~3 attempts to load the code.

Sketch uses 11676 bytes (4%) of program storage space. Maximum is 262144 bytes.
Forcing reset using 1200bps open/close on port /dev/cu.usbmodem14201

Regarding the loraWan join, I am using an already defined DEVEUI which is already added to the Network Server (I am using loraserver.io). I know the code works, because the second Ultra Pro loaded with the same code is working perfectly.

Here is a partial log

23:57:56.957 -> HUB-001 STARTING...
23:57:56.957 -> LMIC: Initializing...
23:57:56.991 -> LMIC: Reseting...
23:57:56.991 -> LMIC: Starting OTAA...
23:57:56.991 -> [do_send] Get sensor data...
23:57:56.991 -> ============================
23:57:56.991 -> T = -15 *C
23:57:56.991 -> H = 45 %
23:57:56.991 -> P = 1012 hPa
23:57:56.991 -> M = 75 %
23:57:56.991 -> G = -17 *C
23:57:56.991 -> L = 55245 lux
23:57:56.991 -> ============================
23:57:56.991 -> [do_send] Packet queued
23:57:56.991 -> EV_JOINING
23:57:56.991 -> EV_TXSTART

Don’t pay attention to the data, they are bogus for now 🙂
And what seems to be happening is the Join request isn’t being received by the gateway at all.

• This reply was modified 5 years, 2 months ago by Amir Nathoo.

Is the DIO1 jumper at the back of the board shorted?

I haven’t shortened the jumper. The odd thing is again the second board working as expected and it’s not altered either.
I tested the boards with the same antenna and with only 1 device connected at a time. The gateway is about 12 meters away and separated by a ceiling.
As far as I can tell the join request isn’t being received by the gateway and the board is basically stuck waiting for a response. I’ll enable LMIC debug tomorrow (it’s late here) and report my findings.

The code I am using is proven to work as expected and I already adapted it based on the tutorial. It’s working perfectly on one of the board.

But I added DEBUG to LMIC (also had to redefine Serial to SerialUSB in the config and it is throwing an Assert because the Radio went to sleep after sending the join request.

09:33:42.503 -> EV_JOINING
09:33:42.503 -> EV_TXSTART
09:33:42.538 -> FAILURE 
09:33:42.538 -> /Users/anathoo/Documents/Arduino/libraries/MCCI_LoRaWAN_LMIC_library/src/lmic/radio.c:746

static void startrx (u1_t rxmode) {
    ASSERT( (readReg(RegOpMode) & OPMODE_MASK) == OPMODE_SLEEP );
    if(getSf(LMIC.rps) == FSK) { // FSK modem
        rxfsk(rxmode);
    } else { // LoRa modem
        rxlora(rxmode);
    }
    // the radio will go back to STANDBY mode as soon as the RX is finished
    // or timed out, and the corresponding IRQ will inform us about completion.
}

It’s failing here: ASSERT( (readReg(RegOpMode) & OPMODE_MASK) == OPMODE_SLEEP );
This seems to confirm what you were saying about shorting the DIO1 jumper, correct?
But why this would only affect this one particular board and not the other?

• This reply was modified 5 years, 2 months ago by Amir Nathoo.