-
Notifications
You must be signed in to change notification settings - Fork 27
Arduino Nano Every requires workaround #40
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
Comments
And in case anyone wonders why the "Every" instead of the normal Nano it's because I'm an idiot. I designed the PCBs with the Nano in mind without realizing that the Tx/Rx pins are needed for serial coms. The Every has a second Serial connection independent of those pins. Separately, I also didn't realize that Pin 13 can't really be used as an input because it's tied to the on-board LED, but I managed to work around that by scratching off the LED/resistor. 😁 I may redesign the PCBs to work with the base nano and add a socket for a Max487 to use it with RS485, but that's way down on the priority list. Thanks, |
If this is still an issue, I curious if you are already using, or have tried using |
Sorry I missed your comment. I am able to use the Everys just fine, and I was already using
As for switching to plain Nanos, I'd love to but some poor planning on my part makes it complicated. I designed PCBs for a few of my panels with the Nano in mind, but didn't understand at the time that I couldn't use pins 0 and 1 because they are for the serial connection. The Every has a separate USB serial connection so pins 0 and 1 work fine. Thanks, |
I have a couple of PCBs that I designed for my Warthog pit (CMSP, CMSC, and ARC-210) that require an Arduino Nano Every with the ATMega4809 microcontroller.
The boards don't work using RS485, but they do work when directly connected via USB. However, I have found that I have to first open and close a serial monitor on each board via the Arduino IDE before it will communicate with DCS. The ports are recognized by socat, but they won't talk to DCS until after the serial monitor trick.
Any idea what might be causing this? Any suggested alternative approach to make these boards work without the extra step?
Thanks,
Eric
The text was updated successfully, but these errors were encountered: