-
Notifications
You must be signed in to change notification settings - Fork 958
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not send yet, busyTx #860
Comments
@tomasbrincil Hi, have you connected the busy pin also ? possibly need same connection as Type 2 here ? -https://github.com/NanoVHF/Meshtastic-DIY/blob/main/Schematics/Mesh_NiceRF.pdf. |
Hi, thank for your time. Yes busy pin is connected to original pin 32. I rewired 1:1 all pads to G-Nice RF module. |
No change. I am trying differents GPIO pins and nothing helps. @geeksville can you hint me pls? Is it software thing? |
There is no Tx pin issue, "busyTx" in this message means you are still sending a message or forget to handle it: to clear the message after sending it. |
Hi there, I am using T-Beam v 1.1 sx1262, I am trying to desolder original chip a and wire G-NiceRF sx1262 module with integrated power amplifier (I am licenced ham I should know what I am doing :))
Considering same wiring for G-NiceRF module as original module there is some issue when trying to transmit.
BUSY pin on module is 0V. I tried watch scope and no difference between modules.
Yellow is clock, green is data from master, blue is BUSY.
Any idea? In your private TODO.md (sorry!) I found "swbug! stuck busy tx occurred!" on eink. Can´t be same problem?
The text was updated successfully, but these errors were encountered: