CubeCell AB01: join issues and QA control

#1

Hi all,
I have some question about quality control on AB01 and proper hw reset.

I have a batch of ~20 AB01 that are sending a LoRaWAN msg on a specific timer value.
On top of this I do force a hwreset once per day (randomly).

All devices work fine for many weeks, but n.3 of them have issues.

after reset they try to join … and fail.
In my code when this happens I try to join again few times … if it still fails I do another hw reset.

What I see is that these n.3 devices keep joining for hours and hours … and then sometime success … they do connect.

===
I cannot explain why … beside poor quality control on AB01.

Do we have variability on some part of the unit that can cause these poor performance?

I’m using the proper hwreset command … but is there a better procedure to “fully reset” the unit, including the LoRaWAN onboard radio?

thanks

#2

I only bought one unit, and it does behave like you describe. It tries to join and join, and only sometimes it connects, after may intents. I guess you probably are right, maybe poor QA. What is worse, no support from Heltec, so you are left with a faulty device and no support. I’ll switch to another module (Currently trying Lora-E5 from Seeed and it worked out of the box for me).

#3

For suspected product quality problems, HelTec provides technical support. If your node can communicate normally occasionally, you can confirm whether your gateway frequency corresponds exactly to the node frequency. Factors such as server delay may cause communication failure. You can confirm whether the gateway normally receives and forwards the server’s downlink.

#4

My gateway receives correctly from other devices (PyCom with LoRa module and Seeed STM32/Lora SoC) but not reliably from the CubeCell, so I’d suspect the problem is with the CubeCell and not with the gateway. There are no external servers, the entire stack (chirpstack) is running on the gateway and I am checking the LoRa log directly on the gateway. Both gateway and end node are in the same room. The CubeCell sents multiple join requests and sometimes, after a few minutes, one of them is detected and accepted by the gateway. Also, with ABP, ony a few of the sent packets are seen.

#5

If the frequency points of the gateway and the node do not correspond, the gateway will only receive the node’s uplink, the gateway will not have the downlink, and the node will send multiple join requests. Can you show the frequency of your gateway and node?

#6

Config of packet forwarder in RAK gateway

   "radio_0": {
        "enable": true,
        "type": "SX1250",
        "freq": 867500000,
        "rssi_offset": -215.4,
        "rssi_tcomp": {"coeff_a": 0, "coeff_b": 0, "coeff_c": 20.41, "coeff_d": 2162.56, "coeff_e": 0},
        "tx_enable": true,
        "tx_freq_min": 863000000,
        "tx_freq_max": 870000000,
        "tx_gain_lut":[
            {"rf_power": 12, "pa_gain": 1, "pwr_idx": 4},
            {"rf_power": 13, "pa_gain": 1, "pwr_idx": 5},
            {"rf_power": 14, "pa_gain": 1, "pwr_idx": 6},
            {"rf_power": 15, "pa_gain": 1, "pwr_idx": 7},
            {"rf_power": 16, "pa_gain": 1, "pwr_idx": 8},
            {"rf_power": 17, "pa_gain": 1, "pwr_idx": 9},
            {"rf_power": 18, "pa_gain": 1, "pwr_idx": 10},
            {"rf_power": 19, "pa_gain": 1, "pwr_idx": 11},
            {"rf_power": 20, "pa_gain": 1, "pwr_idx": 12},
            {"rf_power": 21, "pa_gain": 1, "pwr_idx": 13},
            {"rf_power": 22, "pa_gain": 1, "pwr_idx": 14},
            {"rf_power": 23, "pa_gain": 1, "pwr_idx": 16},
            {"rf_power": 24, "pa_gain": 1, "pwr_idx": 17},
            {"rf_power": 25, "pa_gain": 1, "pwr_idx": 18},
            {"rf_power": 26, "pa_gain": 1, "pwr_idx": 19},
            {"rf_power": 27, "pa_gain": 1, "pwr_idx": 22}
        ]
    },
    "radio_1": {
        "enable": true,
        "type": "SX1250",
        "freq": 868500000,
        "rssi_offset": -215.4,
        "rssi_tcomp": {"coeff_a": 0, "coeff_b": 0, "coeff_c": 20.41, "coeff_d": 2162.56, "coeff_e": 0},
        "tx_enable": false
    },

which corresponds to global_conf.eu_863_870.json, i.e. Europe 868 MHz. The AT session looks like

+OK
+LORAWAN=1
+OK
+ChMask=0000000000000000000000FF
+OK
+AppPort=2
+ConfirmedNbTrials=4
+OK
+DutyCycle=15000
+OK
+ADR=1
+OK
+OTAA=1

LoRaWAN EU868 Class A start!

joining...TX on freq 868300000 Hz at DR 5
TX on freq 868300000 Hz at DR 5
Event : Tx Done
RX on freq 868300000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868300000 Hz at DR 5
TX on freq 868300000 Hz at DR 5
Event : Tx Done
RX on freq 868300000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868500000 Hz at DR 5
TX on freq 868500000 Hz at DR 5
Event : Tx Done
RX on freq 868500000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868100000 Hz at DR 5
TX on freq 868100000 Hz at DR 5
Event : Tx Done
RX on freq 868100000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868100000 Hz at DR 5
TX on freq 868100000 Hz at DR 5
Event : Tx Done
RX on freq 868100000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868500000 Hz at DR 5
TX on freq 868500000 Hz at DR 5
Event : Tx Done
RX on freq 868500000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868300000 Hz at DR 5
TX on freq 868300000 Hz at DR 5
Event : Tx Done
RX on freq 868300000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868100000 Hz at DR 4
TX on freq 868100000 Hz at DR 4
Event : Tx Done
RX on freq 868100000 Hz at DR 4
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868500000 Hz at DR 5
TX on freq 868500000 Hz at DR 5
Event : Tx Done
RX on freq 868500000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868100000 Hz at DR 5
TX on freq 868100000 Hz at DR 5
Event : Tx Done
RX on freq 868100000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868100000 Hz at DR 5
TX on freq 868100000 Hz at DR 5
Event : Tx Done
RX on freq 868100000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868300000 Hz at DR 5
TX on freq 868300000 Hz at DR 5
Event : Tx Done
RX on freq 868300000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868500000 Hz at DR 5
TX on freq 868500000 Hz at DR 5
Event : Tx Done
RX on freq 868500000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout
TX on freq 868500000 Hz at DR 5
TX on freq 868500000 Hz at DR 5
Event : Tx Done
RX on freq 868500000 Hz at DR 5
Event : Rx Done
joined

Sending data (not received by gateway)

+Send Hex Data:AA
unconfirmed uplink sending ...
TX on freq 868300000 Hz at DR 5
TX on freq 868300000 Hz at DR 5
Event : Tx Done
RX on freq 868300000 Hz at DR 5
Event : Rx Timeout
RX on freq 869525000 Hz at DR 0
Event : Rx Timeout

And, as I already said, other devices configured for 868 MHz work fine with the gateway.

I have checked the radio signal emitted from the CubeCell with a SDR (LoRa 868 MHz SF12 “00” data), looks ok to me:

lora868
lora868.png568×736 118 KB

#7

Can you provide a screenshot of the gateway log from node “joining…” to “joined”?

#8

I have been looking at the log while trying to join. There are no messages while the end node is transmitting. Just the stats which are printed every minute that look like this

Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [up] PUSH_ACK received in 1 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [down] PULL_ACK received in 0 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [down] PULL_ACK received in 0 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [down] PULL_ACK received in 0 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ##### 2021-08-11 08:28:27 GMT #####
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [UPSTREAM] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # RF packets received by concentrator: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # RF packets forwarded: 0 (0 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PUSH_DATA datagrams sent: 1 (124 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PUSH_DATA acknowledged: 100.00%
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [DOWNSTREAM] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PULL_DATA sent: 3 (100.00% acknowledged)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # RF packets sent to concentrator: 0 (0 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX errors: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (collision packet): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (collision beacon): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (too late): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (too early): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### SX1302 Status ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # SX1302 counter (INST): 1731871454
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # SX1302 counter (PPS):  2355991725
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # BEACON queued: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # BEACON sent so far: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # BEACON rejected: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [JIT] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: #--------
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [GPS] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # Valid time reference (age: 0 sec)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # no valid GPS coordinates available yet
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ##### END #####
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: JSON up: {"stat":{"time":"2021-08-11 08:28:27 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"temp":0.0}}
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [up] PUSH_ACK received in 0 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [down] PULL_ACK received in 0 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [down] PULL_ACK received in 0 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [down] PULL_ACK received in 0 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ##### 2021-08-11 08:28:57 GMT #####
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [UPSTREAM] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # RF packets received by concentrator: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # RF packets forwarded: 0 (0 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PUSH_DATA datagrams sent: 1 (124 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PUSH_DATA acknowledged: 100.00%
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [DOWNSTREAM] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PULL_DATA sent: 3 (100.00% acknowledged)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # RF packets sent to concentrator: 0 (0 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX errors: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (collision packet): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (collision beacon): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (too late): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (too early): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### SX1302 Status ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # SX1302 counter (INST): 1761872807
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # SX1302 counter (PPS):  2355991725
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # BEACON queued: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # BEACON sent so far: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # BEACON rejected: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [JIT] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: #--------
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [GPS] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # Valid time reference (age: 0 sec)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # no valid GPS coordinates available yet
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ##### END #####
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: JSON up: {"stat":{"time":"2021-08-11 08:28:57 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"temp":0.0}}
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [up] PUSH_ACK received in 1 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [down] PULL_ACK received in 0 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [down] PULL_ACK received in 0 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [down] PULL_ACK received in 0 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ##### 2021-08-11 08:29:27 GMT #####
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [UPSTREAM] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # RF packets received by concentrator: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # RF packets forwarded: 0 (0 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PUSH_DATA datagrams sent: 1 (124 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PUSH_DATA acknowledged: 100.00%
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [DOWNSTREAM] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PULL_DATA sent: 3 (100.00% acknowledged)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # RF packets sent to concentrator: 0 (0 bytes)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX errors: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (collision packet): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (collision beacon): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (too late): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # TX rejected (too early): 0.00% (req:71, rej:0)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### SX1302 Status ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # SX1302 counter (INST): 1791874162
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # SX1302 counter (PPS):  2355991725
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # BEACON queued: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # BEACON sent so far: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # BEACON rejected: 0
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [JIT] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: #--------
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ### [GPS] ###
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # Valid time reference (age: 0 sec)
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: # no valid GPS coordinates available yet
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: ##### END #####
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: JSON up: {"stat":{"time":"2021-08-11 08:29:27 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"temp":0.0}}
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [up] PUSH_ACK received in 1 ms
Aug 11 09:29:42 rak-gateway ttn-gateway[6936]: INFO: [down] PULL_ACK received in 0 ms

When the end node after many intents finally prints “joined” the packet is detected by the packet forwarder and forwarded to the rest of the stack (I have edited some id’s)

Aug 11 09:31:13 rak-gateway ttn-gateway[6936]: INFO: Received pkt from mote: 00000000 (fcnt=0)
Aug 11 09:31:13 rak-gateway chirpstack-network-server[7059]: time="2021-08-11T09:31:13+01:00" level=info msg="uplink: frame(s) collected" ctx_id=ppppppppp-9ee7-43c5-92fc-9e0d1b88a109 mtype=JoinRequest uplink_ids="[kkkkkkkkk-6e0f-40d0-ad40-1a5dd8094f64]"
Aug 11 09:31:13 rak-gateway chirpstack-application-server[561]: time="2021-08-11T09:31:13+01:00" level=info msg="backend/joinserver: request received" message_type=JoinReq receiver_id=0000000000000000 sender_id=000000 transaction_id=2315205115
Aug 11 09:31:13 rak-gateway chirpstack-application-server[561]: time="2021-08-11T09:31:13+01:00" level=info msg="device-keys updated" ctx_id="<nil>" dev_eui=my_device_eui
Aug 11 09:31:13 rak-gateway chirpstack-application-server[561]: time="2021-08-11T09:31:13+01:00" level=info msg="backend/joinserver: sending response" dev_eui=my_device_eui message_type=JoinAns receiver_id=000000 result_code=Success sender_id=0000000000000000 transaction_id=2315205115
Aug 11 09:31:13 rak-gateway chirpstack-network-server[7059]: time="2021-08-11T09:31:13+01:00" level=info msg="lorawan/backend: finished backend api call" message_type=JoinReq protocol_version=1.0 receiver_id=0000000000000000 result_code=Success sender_id=000000 transaction_id=2315205115
Aug 11 09:31:13 rak-gateway chirpstack-network-server[7059]: time="2021-08-11T09:31:13+01:00" level=info msg="sent uplink meta-data to network-controller" ctx_id=kkkkkkkkk-43c5-92fc-9e0d1b88a109 dev_eui=my_device_eui
Aug 11 09:31:13 rak-gateway chirpstack-network-server[7059]: time="2021-08-11T09:31:13+01:00" level=info msg="device-queue flushed" ctx_id=kkkkkkkkkkk-43c5-92fc-9e0d1b88a109 dev_eui=my_device_eui
Aug 11 09:31:13 rak-gateway chirpstack-network-server[7059]: time="2021-08-11T09:31:13+01:00" level=info msg="device-session saved" ctx_id=kkkkkk-43c5-92fc-9e0d1b88a109 dev_addr=001c5af1 dev_eui=my_device_eui
Aug 11 09:31:13 rak-gateway chirpstack-network-server[7059]: time="2021-08-11T09:31:13+01:00" level=info msg="device-activation created" ctx_id=kkkkkkkkkk-43c5-92fc-9e0d1b88a109 dev_eui=my_device_eui id=45
Aug 11 09:31:13 rak-gateway chirpstack-network-server[7059]: time="2021-08-11T09:31:13+01:00" level=info msg="device updated" ctx_id=kkkkkkkkkkk-43c5-92fc-9e0d1b88a109 dev_eui=my_device_eui
Aug 11 09:31:13 rak-gateway chirpstack-network-server[7059]: time="2021-08-11T09:31:13+01:00" level=info msg="gateway/mqtt: publishing gateway command" command=down downlink_id=hhhhhhhhhh-43c5-92fc-9e0d1b88a109 gateway_id=another_id qos=0 topic=gateway/some_id/command/down
....

I should add that sometimes the join works almost instantly but most of the time it just spins forever. My area is rural, I have checked with the SDR that there are no interferences in the band.

#9

When the node is “joined”, what is the rssi of the node in the server, like this:

test
test.png935×486 20.3 KB

#10

Thank you very much for answering! I get rssi: -60, snr: 11

#11

Are you using the default LoRaWAN code? Did you modify the code?

#12

I have tried both, LoRaWan and simple AT commands. The tests above are all with AT commands, as you can see from the output.

#13

Dear @shaffer, any updates on this? Is this a faulty device? I have reported everything you asked me (which by the way has taken quite some time), but there are no solutions from Heltec.

#14

Sorry, I am not sure if there is a problem with the hardware, the node has output, and the rssi of the successful communication is within the normal range, but you cannot use it normally, if it is really not available, you can contact the seller for a replacement or refund.

#15

OK @shaffer, thank you anyhow. I’d guess some frequency stability or timing problem, my other devices all connect on the first join intent. I’ll contact amazon.