Closed FrankUlbrich closed 5 years ago
The accept come back from the gateway
This is probably caused by recent changes in LMIC library, since the author of this library is working on the goal to reach certification.
You can set back to former stable LMIC version 2.3.2 by editing platformio.ini line58/59, i think this will solve the problem, until next point release of LMIC stack is out.
Meanwhile i tested the current code on a Heltec V2 board connecting to a MatchX gateway -> no join problems.
I sometimes see JOIN WAIT messages, probably a result of missing the join accept message; but i have this effect with a T-Beam, too. I'm fighting this problem since a while, missing serious debugging possibilities to check RX timings.
Strategy right now is to wait for the next main release of MCCI LMIC stack, awaited soon, since MCCI is close to pass LORAWAN compliance check. If the the join wait issue will persist after certification, i assume root cause is a timing issue with the multitasking paxcounter application, breaking timings of the LORAWAN stack (which runs in separate RTOS task on core 1, but must coexist with other tasks on core 1).
Thank you very much for your answer and spending time into my issue. I will try all your coming releases and combinations and report if I get success.
Does your Heltev V2 never join? Or does is join after a few minutes, while displaying JOIN WAIT?
I found a (temporary) solution: pinned down lmic stack to a preceding version which does not show this join issue. Please reload and rebuild from master branch.
I will open issue in mcci lmic repository to sort this out.
Current MCCI LMIC version is working again.
Hi cyberman, I got my problem back with my HELTEC LORA 32 v2 device and I got the feeling, that this hardware is not good for the paxcounter.
https://github.com/cyberman54/ESP32-Paxcounter/issues/411
The join of PAXCOUNTER does not working in my case. In the file of Loraserver the request is recorded and the positive reponse is sent. It looks like that this response is not recognized by the node.
I modified the setting but it does not solve the problem. The old 1.7 code does suddenly have problem, too.: // ATTN: VALUES > 7 WILL CAUSE RECEPTION AND JOIN PROBLEMS WITH HIGH SF RATES
define CLOCK_ERROR_PROCENTAGE 7
PAXCNT v1.8.02
OTAA won't work with my device. Demo code does not have a prblem. On the other hand. my "TTGO BEAM" works fine.
I would like to let you know, that I love your project.