Cubecell HTCC-AB02 Tx timeout issue

I am developing a LoRa based p2p remote controller on PlatformIO environment. I am not using any lorawan features or libraries but controlling the radio directly. Currently I have two HTCC-AB02 development modules, one that works perfectly with my sw and the other one that does not send anything, only Tx Timeout error occurs. Exactly the samy binary is uploaded to both modules.

I have defined callbacks like
RadioEvents.TxDone = OnTxDone;
RadioEvents.TxTimeout = OnTxTimeout;

Sending is done simply like
packetSent = false; // flag is set to true in OnTxDone() and OnTxTimeout()
Radio.Send(bufPayload, (uint8_t)LORA_PAYLOAD_LEN);
Radio.IrqProcess();
while(!packetSent) {
Radio.IrqProcess();
}

TxTimeout is defined to be 3000 ms. If have some debug prinouts in callback functions and one of the modules works as supposed to work but the other one prints only debug messages “Tx Timeout” meaning that tx timeout occurs every time Radio.Send() is called.

DO I have a faulty hw or what is going on? I am pretty sure that my sw is ok while the other module works without any problem. I hope this is not very common problem with ASR6502 while I have already ordered quite many HTCC-AM02 modules to be installed on my own pcb’s…

Did you care that the timeout is set to a value larger value than the physical time needed to send? so depends highly on your setup (spread, coding rate, preamble, crc and number of bytes). I would set the timeout to a very large value and see then what happens…

As I mentioned I have set the tx timeout value to 3000 ms (3 seconds). Using my LoRa configuration it normaly takes about 30 ms to send the packet of two bytes as my debug prints show when using the working module:
08:49:27.939 > >sendLoRaMsg(0) #0: [AA] [66]
08:49:27.970 > > TX done.> # 0
08:49:28.071 > >sendLoRaMsg(0) #1: [55] [66]
08:49:28.105 > > TX done.> # 1
08:49:28.202 > >sendLoRaMsg(0) #2: [CC] [66]
08:49:28.232 > > TX done.> # 2
08:49:28.334 > >sendLoRaMsg(0) #3: [33] [66]
08:49:28.365 > > TX done.> # 3
08:49:28.466 > >sendLoRaMsg(0) #4: [BB] [66]

The same print outs using the very same sw on non working module shows only 3 seconds timeouts:
08:51:14.350 > >sendLoRaMsg(0) #0: [AA] [66]
08:51:17.354 > > TX Timeout…>
08:51:17.456 > >sendLoRaMsg(0) #0: [55] [66]
08:51:20.461 > > TX Timeout…>
08:51:20.562 > >sendLoRaMsg(0) #0: [CC] [66]
08:51:23.567 > > TX Timeout…>
08:51:23.668 > >sendLoRaMsg(0) #0: [33] [66]
08:51:26.674 > > TX Timeout…>
08:51:26.774 > >sendLoRaMsg(0) #0: [BB] [66]
08:51:29.779 > > TX Timeout…>

It sounds like the same problem (hardware) I have.

No gateway, as I mentioned I do not use LoRaWan features, only point-to-point connection between two devices.

I meant the problem is the topic I shared in that in both cases the radio just returns TX Timeout for yet-to-be-understood reasons. My code works fine with all of my other boards.