Closed DomoArigatoMrGato closed 1 week ago
"Can not send yet, busyRx" due to false preamble detection is normal and happens every now and then. It's a known issue that the T1000-E cannot receive packets from the old SX127x radios, and this is being tracked in #4775.
Category
Hardware Compatibility
Hardware
Seeed Card Tracker T1000-E
Firmware Version
2.4.0 + 2.5.6
Description
I'm experiencing an issue with my T1000E, this was an issue with the default 2.4.0 firmware the device came with as well.
The device seems to always be busy with RX, there are only 2 reachable nodes in my area. I can send messages to my other T-Beam node from my T1000E on channel 0, and my T-Beam node sees my T1000E, but my T1000E does not see my T-Beam nor the messages sent by my T-Beam. Every message I send to channel 0 from my T1000E is only sent after preamble is ignored and it does not receive a message acknowledgment.
I have followed instructions on flashing the device firmware to 2.5.6, including loading the erase flash firmware, then loading the Meshtastic firmware.
Relevant log output