CubeCell HTCCAB01 intermittent connection OTAA mode

rodbaca · June 16, 2023, 6:30pm

Hello, greetings, I need help with the CuveCell HTCC AB01 boards, I am trying to send data to TTN, through a Dragino DLOS8N Gateway, on the US915 frequency, OTAA mode network configuration, the nodes achieve connection with TTN and then they crash, they work fine for a few moments and then they disconnect, they work intermittently.

Can someone tell me, if these HTCC AB01 modules give problems with the OTAA configuration, because it seems that the board is stuck, trying the LoRa connection with the Gateway…
This is the information generated by the node log.

AT Rev 1.3
+AutoLPM=1
+LORAWAN=1
+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=30000
+ConfirmedNbTrials=4
+ChMask=00000000000000000000FF00
+DevEui=70B3D57ED005E4D9(For OTAA Mode)
+AppEui=120D516055E5BDA5(For OTAA Mode)
+AppKey=F9839C8DD2EE579650D1C1DD1A154989(For OTAA Mode)
+NwkSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+AppSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)
LoRaWAN US915 Class A start!
joining...TX on freq 904300000 Hz at DR 3 power 20 dBm
TX on freq 904300000 Hz at DR 3 power 20 dBm
Event : Tx Done
RX on freq 924500000 Hz at DR 13
Event : Rx Timeout
RX on freq 923300000 Hz at DR 8
Event : Rx Timeout
TX on freq 904100000 Hz at DR 0 power 20 dBm
TX on freq 904100000 Hz at DR 0 power 20 dBm
Event : Tx Done
RX on freq 923900000 Hz at DR 10
Event : Rx Timeout
RX on freq 923300000 Hz at DR 8
Event : Rx Timeout
TX on freq 903900000 Hz at DR 3 power 20 dBm
TX on freq 903900000 Hz at DR 3 power 20 dBm
Event : Tx Done
RX on freq 923300000 Hz at DR 13
Event : Rx Timeout
RX on freq 923300000 Hz at DR 8
Event : Rx Timeout
TX on freq 905100000 Hz at DR 0 power 20 dBm
TX on freq 905100000 Hz at DR 0 power 20 dBm
Event : Tx Done
RX on freq 926900000 Hz at DR 10
Event : Rx Timeout
RX on freq 923300000 Hz at DR 8
Event : Rx Timeout
TX on freq 905300000 Hz at DR 3 power 20 dBm
TX on freq 905300000 Hz at DR 3 power 20 dBm
Event : Tx Done
RX on freq 927500000 Hz at DR 13
Event : Rx Timeout
RX on freq 923300000 Hz at DR 8
Event : Rx Timeout
TX on freq 904700000 Hz at DR 0 power 20 dBm
TX on freq 904700000 Hz at DR 0 power 20 dBm
Event : Tx Done
RX on freq 925700000 Hz at DR 10
Event : Rx Timeout
RX on freq 923300000 Hz at DR 8
Event : Rx Timeout
TX on freq 904900000 Hz at DR 3 power 20 dBm
TX on freq 904900000 Hz at DR 3 power 20 dBm
Event : Tx Done

kersing · June 16, 2023, 7:11pm

You conclude this based on what evidence? Your log looks perfectly normal for a LoRaWAN device.
What do you expect that isn’t there?

Do you see data arriving in the TTN console?

descartes · June 16, 2023, 9:32pm

Formatted logs using </> tool

Confirmed uplinks every 30 seconds may well be killing the legal limit on the gateway and is very very very very definitely in breach of the TTN Fair Use Policy.

No timestamps make log interpretation much harder as well.

rodbaca · June 16, 2023, 11:35pm

Thanks kersing, the problem is that the messages arrive intermittently, very few arrive at TTN, they do not load the payload, I am trying to understand if the problem is the node, or the Gateway, sometimes the messages arrive fine, but after a while it disconnects from TTN and several hours pass, until another complete message is obtained, with the reading of the sensor.

Thank you so much

rodbaca · June 16, 2023, 11:36pm

A certain Descartes, he sets it to 30 seconds just to be monitoring it in front of the screen,… despair kills me, I already changed it, I set it every 5 minutes, I’m going to leave the two nodes running all night today, tomorrow I’ll share the log, from Gateway Dragino DLOS8N, and the log, from the console in TTN.

Thank you so much

Jeff-UK · June 17, 2023, 8:34am

@rodbaca In which case you will have killed your use of FUP in <1hr… you are allowed 10 downlinks (of all types) per day on TTN - and recommendation is that should be per week or even per month for good social use of GW capacity and spectrum resource… please use unconfirmed when ever possible

rodbaca · June 17, 2023, 6:02pm

Thank you very much Jeff-Uk, I’m going to change the settings…

rodbaca · June 17, 2023, 6:09pm

Hello, greetings to all, I need your help, I still have problems with the transmission of messages between the Cubecell HTCC-AB01 nodes and the Gateway DLS08N, I do not understand where the messages are lost, very few reach TTN, most do not load the payload, the messages arrive intermittently, the nodes manage to connect to TTN and then they fall, hours pass and they reconnect, I share the log, from the node reading the serial monitor, screenshot of the Gateway traffic log , and the log of the device in the TTN tray. Please help me correct the problem.

I would like to understand if the problem is in the node, or in the Gateway, or if it is a frequency problem here in the country, I am doing tests in US915.

17.06.23 17:00:31: 

17.06.23 17:00:31: AT Rev 1.3

17.06.23 17:00:31: +AutoLPM=1

17.06.23 17:00:31: 

17.06.23 17:00:31: +LORAWAN=1

17.06.23 17:00:31: 

17.06.23 17:00:31: +KeepNet=0

17.06.23 17:00:31: +OTAA=1

17.06.23 17:00:31: +Class=A

17.06.23 17:00:31: +ADR=1

17.06.23 17:00:31: +IsTxConfirmed=0

17.06.23 17:00:31: +AppPort=2

17.06.23 17:00:31: +DutyCycle=900000

17.06.23 17:00:31: +ConfirmedNbTrials=4

17.06.23 17:00:31: +ChMask=00000000000000000000FF00

17.06.23 17:00:31: +DevEui=70B3D57ED005CF5A(For OTAA Mode)

17.06.23 17:00:31: +AppEui=BA25D166745D8D4C(For OTAA Mode)

17.06.23 17:00:31: +AppKey=13AD0D812264242156DB8B61C71ED980(For OTAA Mode)

17.06.23 17:00:31: +NwkSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)

17.06.23 17:00:31: +AppSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)

17.06.23 17:00:31: +DevAddr=007E6AE1(For ABP Mode)

17.06.23 17:00:31: 

17.06.23 17:00:31: 

17.06.23 17:00:31: LoRaWAN US915 Class A start!

17.06.23 17:00:31: 

17.06.23 17:00:31: joining...TX on freq 904700000 Hz at DR 3 power 20 dBm

17.06.23 17:00:31: TX on freq 904700000 Hz at DR 3 power 20 dBm

17.06.23 17:00:31: Event : Tx Done

17.06.23 17:00:36: RX on freq 925700000 Hz at DR 13

17.06.23 17:00:36: Event : Rx Timeout

17.06.23 17:00:37: RX on freq 923300000 Hz at DR 8

17.06.23 17:00:37: Event : Rx Timeout

17.06.23 17:00:38: TX on freq 904500000 Hz at DR 0 power 20 dBm

17.06.23 17:00:38: TX on freq 904500000 Hz at DR 0 power 20 dBm

17.06.23 17:00:38: Event : Tx Done

17.06.23 17:00:43: RX on freq 925100000 Hz at DR 10

17.06.23 17:00:43: Event : Rx Timeout

17.06.23 17:00:44: RX on freq 923300000 Hz at DR 8

17.06.23 17:00:45: Event : Rx Timeout

17.06.23 17:00:45: TX on freq 903900000 Hz at DR 3 power 20 dBm

17.06.23 17:00:45: TX on freq 903900000 Hz at DR 3 power 20 dBm

17.06.23 17:00:45: Event : Tx Done

17.06.23 17:00:50: RX on freq 923300000 Hz at DR 13

17.06.23 17:00:50: Event : Rx Timeout

17.06.23 17:00:51: RX on freq 923300000 Hz at DR 8

17.06.23 17:00:51: Event : Rx Timeout

17.06.23 17:00:52: TX on freq 905300000 Hz at DR 0 power 20 dBm

17.06.23 17:00:52: TX on freq 905300000 Hz at DR 0 power 20 dBm

17.06.23 17:00:53: Event : Tx Done

17.06.23 17:00:58: RX on freq 927500000 Hz at DR 10

17.06.23 17:00:58: Event : Rx Timeout

17.06.23 17:00:59: RX on freq 923300000 Hz at DR 8

17.06.23 17:00:59: Event : Rx Timeout

17.06.23 17:00:59: TX on freq 904300000 Hz at DR 3 power 20 dBm

17.06.23 17:00:59: TX on freq 904300000 Hz at DR 3 power 20 dBm

17.06.23 17:00:59: Event : Tx Done

17.06.23 17:01:04: RX on freq 924500000 Hz at DR 13

17.06.23 17:01:04: Event : Rx Timeout

17.06.23 17:01:05: RX on freq 923300000 Hz at DR 8

17.06.23 17:01:05: Event : Rx Timeout

17.06.23 17:01:06: TX on freq 904100000 Hz at DR 0 power 20 dBm

17.06.23 17:01:06: TX on freq 904100000 Hz at DR 0 power 20 dBm

17.06.23 17:01:07: Event : Tx Done

17.06.23 17:01:12: RX on freq 923900000 Hz at DR 10

17.06.23 17:01:12: Event : Rx Timeout

17.06.23 17:01:13: RX on freq 923300000 Hz at DR 8

17.06.23 17:01:13: Event : Rx Timeout

17.06.23 17:01:13: TX on freq 904900000 Hz at DR 3 power 20 dBm

17.06.23 17:01:13: TX on freq 904900000 Hz at DR 3 power 20 dBm

17.06.23 17:01:13: Event : Tx Done

17.06.23 17:01:18: RX on freq 926300000 Hz at DR 13

17.06.23 17:01:18: Event : Rx Timeout

17.06.23 17:01:19: RX on freq 923300000 Hz at DR 8

17.06.23 17:01:19: Event : Rx Timeout

17.06.23 17:01:20: TX on freq 905100000 Hz at DR 0 power 20 dBm

17.06.23 17:01:20: TX on freq 905100000 Hz at DR 0 power 20 dBm

17.06.23 17:01:21: Event : Tx Done

17.06.23 17:01:26: RX on freq 926900000 Hz at DR 10

17.06.23 17:01:26: Event : Rx Timeout

17.06.23 17:01:27: RX on freq 923300000 Hz at DR 8

17.06.23 17:01:27: Event : Rx Timeout

17.06.23 17:01:27: TX on freq 904700000 Hz at DR 3 power 20 dBm

17.06.23 17:01:27: TX on freq 904700000 Hz at DR 3 power 20 dBm

17.06.23 17:01:28: Event : Tx Done

17.06.23 17:01:33: RX on freq 925700000 Hz at DR 13

17.06.23 17:01:33: Event : Rx Done

17.06.23 17:01:33: joined

17.06.23 17:01:34: Light: 33.33 lx,BatteryVoltage:3998

17.06.23 17:01:39: unconfirmed uplink sending ...

…

Jeff-UK · June 17, 2023, 8:22pm

Please capture text and use formatting too (</>) vs pictures where possible. Clearly still using confirmed uplinks per your picture and I guess per

change that and folk might assist further…

descartes · June 17, 2023, 10:18pm

Detail is everything - please edit your post (so I don’t have to, again) and there is no point repeating the same information, particularly when showing us you haven’t turned off the confirmed uplink setting.

How many uplinks are being sent, how many are being lost. What does the TTN gateway web live data and the device live data layouts show for a successful uplink and for when your gateway shows that it has heard an uplink but nothing has arrived on the device - this is five screen shots, gateway+device from TTN when it has worked, gateway+device from TTN and the gateway log when it hasn’t happened.

Do you have a different make of device that you can run in parallel? Do you have a different make of gateway that you can run in parallel? How is the gateway connected to the internet?

rodbaca · June 17, 2023, 11:17pm

Thank you very much Descartes, I am going to correct the publication and I am going to verify the links

rodbaca · July 16, 2023, 2:40pm

Hello friends, good morning, I need your help, I continue trying to use the Heltec Cube Cell HTCC AB01 boards, I’m configuring it in OTAA mode to integrate them into TTN, I also tried other boards as recommended, two Hetelc SP32 V2 boards, after several days doing tests I can confirm that the Heltec SP32 V2 boards work well. And the Cube Cell boards can connect, but the message arrives incomplete, the payload does not load and then they do not connect again, only when restarted.

Apparently, on the cube cell board, when it is connected in OTAA mode, the code generates a loop that keeps trying to synchronize, as mentioned in the video (CubeCell review and how to connect it to TTN & Helium) by Biblioman09 at the minute 25:00.

I have two questions that I would really appreciate if you could help me clarify.

1). That error could be a problem with the LoRaWan_APP.h library or it could be the code or the LoRaWan configuration, I have tried to make some changes, but it works the same, I have also tried with other CubeCell examples and they also work the same.

I would appreciate it if you could tell me if it is possible to integrate nodes in OTAA mode and other nodes in ABP mode into the TTN console, without generating conflicts.

I share the WASN log reading of the node, code that has two MT05S humidity sensors connected and capture of the node in the TTN console

Thank you very much Jeff-UK and Descartes, for all your collaboration, I apologize for the errors, I hope I have corrected them, regards

I couldn’t edit the previous message, sorry for that too, I have to make a new message.

Lectura Log WASN

16.07.23 07:32:07: Copyright @2019-2020 Heltec Automation.All rights reserved.
16.07.23 07:32:07: 
16.07.23 07:32:07: AT Rev 1.3
16.07.23 07:32:07: +AutoLPM=1
16.07.23 07:32:07: 
16.07.23 07:32:07: +LORAWAN=1
16.07.23 07:32:07: 
16.07.23 07:32:07: +KeepNet=0
16.07.23 07:32:07: +OTAA=1
16.07.23 07:32:07: +Class=A
16.07.23 07:32:07: +ADR=1
16.07.23 07:32:07: +IsTxConfirmed=0
16.07.23 07:32:07: +AppPort=2
16.07.23 07:32:07: +DutyCycle=900000
16.07.23 07:32:07: +ConfirmedNbTrials=4
16.07.23 07:32:07: +ChMask=00000000000000000000FF00
16.07.23 07:32:07: +DevEui=9A444B944F1D8C2B(For OTAA Mode)
16.07.23 07:32:07: +AppEui=13A714E72B450000(For OTAA Mode)
16.07.23 07:32:07: +AppKey=20B2C2BDF38A7D456E18B2B779D8AEF6(For OTAA Mode)
16.07.23 07:32:07: +NwkSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
16.07.23 07:32:07: +AppSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
16.07.23 07:32:07: +DevAddr=007E6AE1(For ABP Mode)
16.07.23 07:32:07: 
16.07.23 07:32:07: 
16.07.23 07:32:07: LoRaWAN US915 Class A start!
16.07.23 07:32:07: 
16.07.23 07:32:07: joining...TX on freq 905100000 Hz at DR 3 power 20 dBm
16.07.23 07:32:07: TX on freq 905100000 Hz at DR 3 power 20 dBm
16.07.23 07:32:07: Event : Tx Done
16.07.23 07:32:12: RX on freq 926900000 Hz at DR 13
16.07.23 07:32:12: Event : Rx Timeout
16.07.23 07:32:13: RX on freq 923300000 Hz at DR 8
16.07.23 07:32:13: Event : Rx Timeout
16.07.23 07:32:14: TX on freq 904900000 Hz at DR 0 power 20 dBm
16.07.23 07:32:14: TX on freq 904900000 Hz at DR 0 power 20 dBm
16.07.23 07:32:15: Event : Tx Done
16.07.23 07:32:20: RX on freq 926300000 Hz at DR 10
16.07.23 07:32:20: Event : Rx Timeout
16.07.23 07:32:21: RX on freq 923300000 Hz at DR 8
16.07.23 07:32:21: Event : Rx Timeout
16.07.23 07:32:21: TX on freq 904500000 Hz at DR 3 power 20 dBm
16.07.23 07:32:21: TX on freq 904500000 Hz at DR 3 power 20 dBm
16.07.23 07:32:21: Event : Tx Done
16.07.23 07:32:26: RX on freq 925100000 Hz at DR 13
16.07.23 07:32:26: Event : Rx Timeout
16.07.23 07:32:27: RX on freq 923300000 Hz at DR 8
16.07.23 07:32:27: Event : Rx Timeout
16.07.23 07:32:28: TX on freq 905300000 Hz at DR 0 power 20 dBm
16.07.23 07:32:28: TX on freq 905300000 Hz at DR 0 power 20 dBm
16.07.23 07:32:29: Event : Tx Done
16.07.23 07:32:34: RX on freq 927500000 Hz at DR 10
16.07.23 07:32:34: Event : Rx Timeout
16.07.23 07:32:35: RX on freq 923300000 Hz at DR 8
16.07.23 07:32:35: Event : Rx Timeout
16.07.23 07:32:35: TX on freq 904100000 Hz at DR 3 power 20 dBm
16.07.23 07:32:35: TX on freq 904100000 Hz at DR 3 power 20 dBm
16.07.23 07:32:35: Event : Tx Done
16.07.23 07:32:40: RX on freq 923900000 Hz at DR 13
16.07.23 07:32:40: Event : Rx Timeout
16.07.23 07:32:41: RX on freq 923300000 Hz at DR 8
16.07.23 07:32:41: Event : Rx Timeout
16.07.23 07:32:42: TX on freq 903900000 Hz at DR 0 power 20 dBm
16.07.23 07:32:42: TX on freq 903900000 Hz at DR 0 power 20 dBm
16.07.23 07:32:43: Event : Tx Done
16.07.23 07:32:48: RX on freq 923300000 Hz at DR 10
16.07.23 07:32:48: Event : Rx Timeout
16.07.23 07:32:49: RX on freq 923300000 Hz at DR 8
16.07.23 07:32:49: Event : Rx Timeout
16.07.23 07:32:49: TX on freq 904700000 Hz at DR 3 power 20 dBm
16.07.23 07:32:49: TX on freq 904700000 Hz at DR 3 power 20 dBm
16.07.23 07:32:50: Event : Tx Done
16.07.23 07:32:55: RX on freq 925700000 Hz at DR 13
16.07.23 07:32:55: Event : Rx Timeout
16.07.23 07:32:56: RX on freq 923300000 Hz at DR 8
16.07.23 07:32:56: Event : Rx Timeout
16.07.23 07:32:56: TX on freq 904300000 Hz at DR 0 power 20 dBm
16.07.23 07:32:57: TX on freq 904300000 Hz at DR 0 power 20 dBm
16.07.23 07:32:57: Event : Tx Done
16.07.23 07:33:02: RX on freq 924500000 Hz at DR 10
16.07.23 07:33:02: Event : Rx Timeout
16.07.23 07:33:03: RX on freq 923300000 Hz at DR 8
16.07.23 07:33:03: Event : Rx Timeout
16.07.23 07:33:04: TX on freq 905100000 Hz at DR 3 power 20 dBm
16.07.23 07:33:04: TX on freq 905100000 Hz at DR 3 power 20 dBm
16.07.23 07:33:04: Event : Tx Done
16.07.23 07:33:09: RX on freq 926900000 Hz at DR 13
16.07.23 07:33:09: Event : Rx Timeout
16.07.23 07:33:10: RX on freq 923300000 Hz at DR 8
16.07.23 07:33:10: Event : Rx Timeout
16.07.23 07:33:11: TX on freq 903900000 Hz at DR 0 power 20 dBm
16.07.23 07:33:11: TX on freq 903900000 Hz at DR 0 power 20 dBm
16.07.23 07:33:11: Event : Tx Done
16.07.23 07:33:16: RX on freq 923300000 Hz at DR 10
16.07.23 07:33:16: Event : Rx Timeout
16.07.23 07:33:17: RX on freq 923300000 Hz at DR 8
16.07.23 07:33:17: Event : Rx Timeout
16.07.23 07:33:18: TX on freq 904300000 Hz at DR 3 power 20 dBm
16.07.23 07:33:18: TX on freq 904300000 Hz at DR 3 power 20 dBm
16.07.23 07:33:18: Event : Tx Done
16.07.23 07:33:23: RX on freq 924500000 Hz at DR 13
16.07.23 07:33:23: Event : Rx Timeout
16.07.23 07:33:24: RX on freq 923300000 Hz at DR 8
16.07.23 07:33:24: Event : Rx Timeout
16.07.23 07:33:25: TX on freq 904100000 Hz at DR 0 power 20 dBm
16.07.23 07:33:25: TX on freq 904100000 Hz at DR 0 power 20 dBm
16.07.23 07:33:25: Event : Tx Done
16.07.23 07:33:30: RX on freq 923900000 Hz at DR 10
16.07.23 07:33:30: Event : Rx Timeout
16.07.23 07:33:31: RX on freq 923300000 Hz at DR 8
16.07.23 07:33:31: Event : Rx Timeout
16.07.23 07:33:32: TX on freq 904700000 Hz at DR 3 power 20 dBm
16.07.23 07:33:32: TX on freq 904700000 Hz at DR 3 power 20 dBm
16.07.23 07:33:32: Event : Tx Done
16.07.23 07:33:37: RX on freq 925700000 Hz at DR 13
16.07.23 07:33:37: Event : Rx Timeout
16.07.23 07:33:38: RX on freq 923300000 Hz at DR 8
16.07.23 07:33:38: Event : Rx Timeout
16.07.23 07:33:39: TX on freq 904900000 Hz at DR 0 power 20 dBm
16.07.23 07:33:39: TX on freq 904900000 Hz at DR 0 power 20 dBm
16.07.23 07:33:39: Event : Tx Done
16.07.23 07:33:44: RX on freq 926300000 Hz at DR 10
16.07.23 07:33:44: Event : Rx Timeout
16.07.23 07:33:45: RX on freq 923300000 Hz at DR 8
16.07.23 07:33:45: Event : Rx Timeout
16.07.23 07:33:46: TX on freq 905300000 Hz at DR 3 power 20 dBm
16.07.23 07:33:46: TX on freq 905300000 Hz at DR 3 power 20 dBm
16.07.23 07:33:46: Event : Tx Done
16.07.23 07:33:51: RX on freq 927500000 Hz at DR 13
16.07.23 07:33:51: Event : Rx Done
16.07.23 07:33:52: joined
16.07.23 07:33:52: //-------------------------
16.07.23 07:33:52: // Start Testing MT05S     
16.07.23 07:33:52: //-------------------------
16.07.23 07:33:52: Test Function Command- Convert T [0x44]  & Read Scratchpad [0xBE]: 
16.07.23 07:33:52: Convert T [0x44]: .....Conversion Done
16.07.23 07:33:52: Read Scratchpad [0xBE]: 9 EC 3 66 0 0 8 0 71  CrcCalculated=71
16.07.23 07:33:52: TEMP(C) = 25.40  HUMIDITY(%) = 8.70  CONDUCTIVITY(ms/cm) = 0.00  CONFIG0 = 8  CONFIG1 = 0  CRC8 = 71
16.07.23 07:33:52: 
16.07.23 07:33:53: //-------------------------

16.07.23 07:33:53: // Start Testing MT05S     
16.07.23 07:33:53: //-------------------------

16.07.23 07:33:53: Test Function Command- Convert T [0x44]  & Read Scratchpad [0xBE]: 
16.07.23 07:33:53: Convert T [0x44]: .....Conversion Done
16.07.23 07:33:53: Read Scratchpad [0xBE]: 9 EC 5 8C FF FF 8 0 9D  CrcCalculated=9D
16.07.23 07:33:53: TEMP22(C) = 25.40  HUMIDITY22(%) = 14.20  CONFIG0 = 8  CONFIG1 = 0  CRC8 = 9D
16.07.23 07:33:53: 
16.07.23 07:33:58: unconfirmed uplink sending ...
16.07.23 07:33:58: TX on freq 904500000 Hz at DR 3 power 20 dBm
16.07.23 07:33:58: TX on freq 904500000 Hz at DR 3 power 20 dBm
16.07.23 07:33:58: Event : Tx Done

Consala TTN

…

descartes · July 16, 2023, 8:22pm

Is there some reason to persist with the Heltec boards?

I just rechecked, the LoRaWAN code base provided is 6 years old and can only manage v1.0.2 - whilst most are on v1.0.3 moving towards v1.0.4 and planning for v1.1

Whilst in theory this shouldn’t matter as long as you are registered your devices as v1.0.2 with RP v1.0.2rB, in practise it’s not cool that a vendor continues to sell hardware with such out of date firmware.

As to mixing and matching OTAA or ABP on an application, there’s no reason why not, I’ve plenty of apps with an OTAA & an ABP registration for device testing.

Where is this video you mention? That user id doesn’t appear to be on this forum so the content may be an unknown quantity.

rodbaca · July 18, 2023, 4:18pm

Thank you very much Descartes, indeed the boards are obsolete, the HTCC AB 01 are discontinued and the HTCC AB 01 V2 are substitutes, however it maintains version v1.0.2 so I am going to change to another brand.

I am looking for a board that is cheap, compatible with Arduino IDE and known libraries.
Thank you very much for all your advice

descartes · July 19, 2023, 10:25am

Cheap is not a number so bit hard to advise - but the reason the Heltec price can be ~$15 is because it uses a non-mainstream chipset / manufacturer, so a sort of unknown quantity with no ongoing firmware updates - sadly Dragino jumped on this bandwagon as well with their ASR offerings so that suffers from older firmware too.

If you make a bunch of them, an ATmega4808 + RFM95 can run the current LMIC nicely sub $10. Pre-made boards available from https://www.rocketscream.com/blog/product/mini-ultra-lora/ which I’ve used & recommend.

Otherwise you may want to look at the supported boards list for LMIC-node and do some web research on prices.