Awesome, Yes he is very attentive to the LIB, I wish more were like that
Nice, narrowing it down. Iâm confident youâll get to the root, and Heck with all the experience and work. Youâll know the solution already.
Meanwhile , canât hurt.
RadioLib relies on:
DIO1 interrupt â sets flag â main loop processes it
If:
ISR fires
BUT semaphore / flag handling fails (you mentioned this!)
Then the CPU:
never blocks
spins in a loop
never returns to low-power wait That alone can explain mA-level current
Iâm feeling like maybe SX1262 not fully transitioned to sleep/standby
BUSY line might still be active
Or radio maybe left in RX/TX standby instead of sleep
RadioLib usually handles this but I recall a post where it was in standby not sleep because of timing, it was an edge case.
also only does it on Battery Right, not when USB is plugged in?
What happens if you Force-clear the interrupt explicitly
After TX complete:
radio.clearIrqStatus();
Even if RadioLib should do it â do it anyway.
or just slam it into a known state for sure before hand.
radio.sleep();
delay(2); // give it time
Also maybe, Check BUSY pin before sleeping MCU as a gate.
while(digitalRead(BUSY_PIN) == HIGH);
if BUSY never drops â bingo, thatâs your smoking gun.
When sleeping, DIO1 goes low and BUSY goes high, which matches what I read on the pins. I have tried everything.
I have tried pulling the +3.3V supply to the SX1262 when I measure high current consumption, and this has no effect. Performing reset() has no effect, nor does finishTransmit().
I suspect that I have several faulty boards. The problem is that there arenât any alternatives to the kit at such a good price. Heltec and RAKWireless are several times the cost.
Here, Here⌠You have done everything IMO. Good on you for the effort.
I agree there are no Cheaper alternatives, the RAK is good but too expensive IMO.
Iâm with you though , In thinking you may have some marginal boards.
You got a picture of them? or the setup?
Pulling the power, more less seals it for me⌠that should Drop everything, sleep or NOT. so puzzling to say the least.!
Maybe we can get them to setup the same test , with your code and see if it shakes out
I have excalated this to the Seeeders Only area⌠hopefully someone will come to work this week.. before Friday in China⌠what da?
If this is a hardware problem⌠and I am assuming it is based on all the work that is going on⌠it must be something on the chip, so seeed will probably not be able to âFIX ITâ other than moving on to the newest chip. I know it does not solve the question⌠but moving on to live with the current available or a software solution. I am not an expert⌠but i cant think of a hardware fault that would cause this absent a bad transistor that will not switch fullyâŚ
one last thought is internal pullups?
If you can manually in the code activate and deactivate the individual pins/gpio