Replies: 2 comments 1 reply
-
Pins 51 52 and 53 have special meaning on a mega. You need to avoid them. These Pins depend on your hardware setup snd configuration... see MotorDrivers.h for a discussion on this. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Turns out this is all linked to ISCLOCKRUNNING.
Regards,
Ian
Sent from my iPhone
+44 7768 215798
… On 10 Jun 2022, at 20:09, Asbelos ***@***.***> wrote:
Pins 51 52 and 53 have special meaning on a mega. You need to avoid them.
Pins 3 and 13 are normally used to communicate between the mega and the motor shield so will go berserk if you try and sens or output to them.
These Pins depend on your hardware setup snd configuration... see MotorDrivers.h for a discussion on this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Apologies for being a noob. I have success with DCC++ EX and JMRI and have added Sensors using Arduino Mega pins (for testing). I have tried on and off for two weeks now to setup Test outputs on pins 3 and 13.
In the DCC commands it acknowledges the Pin 3 and Pin 13 assignment as Outputs as it does for Sensor Inputs on Pins 52 and 53.
I sense that problem lies in the "Hardware Address" for Pins 3 and 13. I have assumed these are just 3 and 13 but the DCC message sent is referring to a decoder address.
Any help appreciated as I am about to buy a gun and shoot myself.
New Text Document (2).txt
Beta Was this translation helpful? Give feedback.
All reactions