Join Fails Immediately

Hi. One of the units I recently purchased for prototyping immediately fails when I try to do an OTAA join. The same code works okay on other units.

I am thinking there is a hardware fault or maybe I got sent a 433MHz unit rather than a 915MHz one by mistake? Is there any way to check? Thanks again.

AT Rev 1.1
+AutoLPM=1

+LORAWAN=1

+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=15000
+ConfirmedNbTrials=4
+ChMask=00000000000000000000FF00
+DevEui=2232330000888802(For OTAA Mode)
+AppEui=0000000000000000(For OTAA Mode)
+AppKey=88888888888888888888888888886601(For OTAA Mode)
+NwkSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+AppSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)


LoRaWAN AU915 Class A start!

joining...join failed, join again at 30s later

could you show the join faild’s serial print log?

I’m not sure if I understand the question. The serial output is already above?
Here’s the full log when I enable debugging. I’m not sure if the ‘TX Timeout’ event is part of the standard debugging or something I added. But the failure only takes a few seconds. This is your LoraWAN_watchdog example, but I have the same problem on any AU915 LoRa application with this node.

AT Rev 1.1
+AutoLPM=1

+LORAWAN=1

+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=15000
+ConfirmedNbTrials=4
+ChMask=00000000000000000000FF00
+DevEui=2232330000888802(For OTAA Mode)
+AppEui=0000000000000000(For OTAA Mode)
+AppKey=88888888888888888888888888886601(For OTAA Mode)
+NwkSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+AppSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)

LoRaWAN AU915 Class A start!

joining…TX on freq 918000000 Hz at DR 5
Event : Tx Timeout
join failed, join again at 30s later

Is there a Gateway?

E_T

hi,

my module have no problem. can you show your tools menu?

%E5%9B%BE%E7%89%87

Yes the gateway is <100m away. But it doesn’t even try to join, it just returns that error within a few seconds. The LEDs don’t even blink.

All of my modules work fine as well - except this one (and the other one I reported with broken battery voltage monitoring). It’s not a configuration or software issue.

The case says it is 868-915 but either it is the wrong module or else I guess there is a hardware fault. Would you like me to post the module back so you can test what the fault is?

1 Like

I think I got a board with the same Issue. I have several identical PCBs with CubeCell Module Plus on them. However, this one just won’t work.

This seems to be a common failure mode - I have had several of these.

Probably something that Heltec should be taking seriously and looking in to - but we always seem to get the same run around when reporting issues like this.

1 Like

I now have a reliable way of making this happen / fixing it.

When I use v1.2.0 of the board in boards manager, this issue goes away, and v1.3.0 and v1.4.0 both do this to every board I have.

Hopefully Heltec can find a fix?