Closed pepefrog1234 closed 3 months ago
I'm not sure what the bug is here? That warning is normal, it's either receiving a real packet, so it cannot send yet, or it had a false preamble detection, which it discards after a short while. Then it will send as normal, like you said happened.
My test environment has three devices which are: 1. v3 mqtt network node 2. v3 portable device 3. CDEBYTE_EORA_S3 problematic device. The channel is idle, I send a message but the app application shows that the message cannot be sent and the message [Can not send yet, busyRx] appears in the log. I tried to send the same message with device #2 (v3) and it sent successfully.
I apologize for not being clear earlier, I've reworked my issue.
So from which device is the log output? That looks normal.
The logs are exported from CDEBYTE_EORA_S3.
But that logs shows it successfully sent the packets and even another node is rebroadcasting for you. Which app are you using that shows it cannot be sent?
android app. I have observed that if the message is only one or two characters long, it is more likely to be sent successfully, but if the characters are too long (more than 50 bytes), it will fail to be sent.
How far are the nodes from each other? If they're in the same room, they might get overloaded.
Can you show a log when the message fails? Preferably from both sending and receiving device.
I am having the same problem - I have 3 nodes - a PICO, and two Heltec V3s. the PICO and one Heltec are performing fine - the firmware was consistent on v2.3.15.deb7c27 between the two Heltec nodes but only one Heltec and the PICO were communicating. With direct messaging between the Heltecs, the working Heltec was saying the message sent successfully but it was never shown as received in the app (android) on the Heltec I am having issues with. I have just re-flashed the firmware on the problematic Heltec with the latest Alpha release 2.4.2.5b45303 and I am still getting swamped with the following logs as you can see from the timestamps. Even the beacons don't seem to be getting through as the node is not showing up on either the PICO (newly reflashed with flash_nuke) or updating the last seen on the working Heltec...
Any help greatly appreciated!
WARN | 17:12:37 34 [RadioIf] Can not send yet, busyRx WARN | 17:12:37 34 [RadioIf] Can not send yet, busyRx WARN | 17:12:37 34 [RadioIf] Can not send yet, busyRx WARN | 17:12:37 34 [RadioIf] Can not send yet, busyRx WARN | 17:12:38 34 [RadioIf] Can not send yet, busyRx WARN | 17:12:38 34 [RadioIf] Can not send yet, busyRx WARN | 17:12:38 34 [RadioIf] Can not send yet, busyRx WARN | 17:12:38 34 [RadioIf] Can not send yet, busyRx WARN | 17:12:38 34 [RadioIf] Can not send yet, busyRx WARN | 17:12:38 34 [RadioIf] Can not send yet, busyRx WARN | 17:12:38 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:38 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:38 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:38 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:38 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 35 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:39 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 36 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:40 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 37 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:41 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:42 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:42 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:42 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:42 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:42 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:42 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:42 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:42 38 [RadioIf] Can not send yet, busyRx WARN | 17:12:42 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:42 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 39 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:43 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 40 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 41 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 41 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 41 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 41 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 41 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 41 [RadioIf] Can not send yet, busyRx WARN | 17:12:44 41 [RadioIf] Can not send yet, busyRx WARN | 17:12:45 41 [RadioIf] Can not send yet, busyRx WARN | 17:12:45 41 [RadioIf] Can not send yet, busyRx WARN | 17:12:45 41 [RadioIf] Can not send yet, busyRx
Same issue here, started from 2.4.0 on two Heltec V3's as well 2 Heltec Wireless Stick Lite v3's.
Note; in non congested area!
Turn of mqtt and debug, those are normal errors if you are congested
The [RadioIf] Can not send yet, busyRx
logs are normal indeed, but should stop being printed after the maximum packet length, which is a couple of seconds or so on LongFast. If it's longer than that, then definitely something is wrong. I haven't encountered this on 2.4 myself.
So I wanted to drop an update on this from my perspective... After a reflash with " full erase and install" set on the problematic Heltec V3, this seemed to have corrected the issue so there must have been some corrupt configuration somewhere. Unfortunately I lost all my previous beacon info but at least I have it working again.
Category
Hardware Compatibility, Other
Hardware
CDEBYTE_EORA_S3
Firmware Version
2.3.10
Description
My test environment has three devices which are: 1. v3 mqtt network node 2. v3 portable device 3. CDEBYTE_EORA_S3 problematic device. The channel is idle, I send a message but the app application shows that the message cannot be sent and the message [Can not send yet, busyRx] appears in the log. I tried to send the same message with device #2 (v3) and it sent successfully.
Relevant log output