Heltec CubeCell HTCC-AB02S with 'failed, code -5' using LoRa

[javrolijk]

Hi all,

I'm trying to make the Heltec Cubecell HTCC-AB02S send random sensor data with LoRa to an MQTT gateway. While I can see the data being received in MQTT, it gives a 'failed, code -5' error after a while and stops sending data. Here's the latest Serial Monitor run. Any clues as to what is going on here? Could it be a faulty board? Below I've also included the 'fdrs_node_config.h' as a reference.

21:15:42.490 -> FDRS User Node initializing...
21:15:42.490 -> Reading ID 2
21:15:42.490 -> Gateway: 1
21:15:42.614 -> RadioLib initialization successful!
21:15:42.614 -> LoRa Initialized. Frequency: 915.00 Bandwidth: 125.00 SF: 10 CR: 5 SyncWord: 18 Tx Power: 17dBm
21:15:42.646 -> LoRa node address is 7839 (hex).
21:15:42.646 -> Id: 2 - Type: 3 - Data loaded: 74.00
21:15:42.646 -> Id: 2 - Type: 1 - Data loaded: 21.00
21:15:42.646 -> Sending FDRS Packet!
21:15:42.691 -> Transmitting LoRa message of size 20 bytes with CRC 0xb147 to gateway 0xee01. Retries remaining: 2
21:15:43.417 -> Incoming LoRa. Size: 11 Bytes, RSSI: -23.00dBm, SNR: 7.75dB, PacketCRC: 0xdfde, Total LoRa received: 0
21:15:43.417 -> ACK Received - CRC Match
21:15:43.417 -> Deep sleeping.
21:15:43.417 -> Delaying.
21:16:13.883 -> Id: 2 - Type: 3 - Data loaded: 80.00
21:16:13.883 -> Id: 2 - Type: 1 - Data loaded: 21.00
21:16:13.883 -> Sending FDRS Packet!
21:16:13.883 -> Transmitting LoRa message of size 20 bytes with CRC 0x3ef6 to gateway 0xee01. Retries remaining: 2, Ack Ok 100.00%
21:16:14.268 -> failed, code -5

The 'fdrs_node_config.h' content:
`// FARM DATA RELAY SYSTEM
//
// Sensor Configuration

#include <fdrs_globals.h>

#define READING_ID 2 //Unique ID for this sensor
#define GTWY_MAC 0x01 //Address of the nearest gateway

//#define USE_ESPNOW
#define USE_LORA
#define DEEP_SLEEP
//#define POWER_CTRL 14
#define FDRS_DEBUG

// LoRa Configuration
#define RADIOLIB_MODULE SX1262
#define LORA_SS RADIO_NSS
#define LORA_RST RADIO_RESET
#define LORA_DIO RADIO_DIO_1
#define LORA_BUSY RADIO_BUSY
#define USE_SX126X

#define LORA_TXPWR 17 // LoRa TX power in dBm (: +2dBm - +17dBm (for SX1276-7) +20dBm (for SX1278))
#define LORA_ACK // Request LoRa acknowledgment.

//#define CUSTOM_SPI
//#define LORA_SPI_SCK 5
//#define LORA_SPI_MISO 19
//#define LORA_SPI_MOSI 27`

[timmbogner]

Hi Jairo,
First try disabling DEEP_SLEEP. The deep-sleeping routines are specific to ESP32 and 8266. If you need lower power consumption, we could look into adding chip-specific code for doing that on CubeCell.
@sbobowski

[javrolijk]

@timmbogner
I tested the example provided. I've uploaded the transmit on a TTGO Lora ESP32 and the receive code snippet in the Cubecell. The screenshot below shows that the Cubecell receives the packet as it should.

[timmbogner]

@javrolijk What about the opposite, does anything fail when sending from the CubeCell?

Also, I just updated the code for those testing examples. It was a fix I made months ago but forgot to commit, so let me know if it broke anything.

[javrolijk]

@timmbogner The Cubecell sends data through Lora Ok. Tested the code for my application and all works. Only when enabling '#define LORA_ACK' it will give the -5 fault code after 3-4 cycles. Uploading the transmit example code on the Cubecell and the receive example code on the TTGO ESP32 work flawlessly, with no error code.

[timmbogner]

I think my best guess is that there is some glitch within the timing of everything. I have a general idea of where something could be going wrong, but I don't have the time or hardware to sort it out. I don't know how it all works, but is there an interrupt handler for the GPS NMEA data that might interrupt FDRS? Can you somehow fully disable the GPS and try it?

I would check out what boards LilyGo has with integrated GPS and LoRa. Unlike Heltec, LilyGo has been happy to send me samples of their products in order to help me develop for them 😏. I don't have anything from the T-Beam line, but that is what I would look at.

[javrolijk]

@timmbogner sounds like a plan.
If you want and have the time. My code package is in a zip file, and you can take a look. Perhaps you can find something that I may not be explaining correctly.