Closed snh closed 2 years ago
Ran in to this again, but this time my fix didn't help. Closing this PR, as I'm not convinced it is actually the solution now.
Could there be something else sending serial output that messes up the detection process? Did you add any debug output to the firmware you are using?
Did you ever figure this out? I am going to release support for 2560-based homebrew devices in the official firmware and rnodeconf, and I'd love to have this ironed out. I currently don't have 2560-based hardware here to test on myself (on its way, but it is taking its time due to shipping issues), so I'm trying to prepare as much as I can without the actual hardware ;)
Hey @markqvist, apologies for the silence, I haven't had a chance to get back to this yet but will keep you updated when I do.
Thanks, no worries. Let me know if you figure something out!
Hi @snh I finally got my hands on some 2560-based boards, and I'm pretty sure I found the cause of your issue. I'll have an "official" 2560-compatible firmware available shortly :)
I added official support for homebrew RNodes based on ATmega2560 to both the RNode Firmware and the rnodconf utility. You can now autoinstall and provision homebrew RNodes based on 2560-boards with:
rnodeconf --autoinstall
I have not tested it heavily myself, since my access to 2560-based boards is limited at the moment, but I would very much appreciate any feedback you have on this if you decide to try it out.
@markqvist Thanks ❤️ I'll give it a try!
Cool, let me know if there is any issues!
OH, I totally forgot to mention this, I might have changed some pin assignments from how they were in your original PR. I actually can't remember now, but just wanted to give you a heads up on it. If your devices don't match my assignments, you will have to change them in the Config.h file again ;)
While setting up RNode on some Arduino Mega 2560s today, I was only managing about a 1 out of 10 success rate with having
rnodeconf
detect them. Increasing thesleep
here resolved the issue.