OS: Windows 10, x64
Model: AR2
Hardware: 3D Printed parts (Prusa MK3S; PLA+), AR2 & AR3 hardware kit from anninrobotics.com, stepper motor kit from steppermotorsonline.com
Software: AR2 Software 2.0
Problem: When I run the software, nothing happens. Nothing on the arm moves at all.
What I've Already Verified:
- Wall power (120V AC)
- 24V DC Motor driver power supply (120V AC going in, 24V DC coming out)
- Motor driver modules are all receiving the full 24V/5V DC (Green LED's on the modules are also lit)
- 5V DC Power supply (120V AC going in, 5V DC coming out)
- Arduino Mega (5V DC going in and the sketch has been uploaded into it correctly)
+ Baud rate: 115200
+ Com port 10 (Computer recognizes through the Device Manager that the Arduino is connected via USB)
- The entire arm is positioned (by hand) completely vertically with no limit switches actively engaged.
When I run the AR2 software, I set the com port to 10 and load the "LTEST" program. I then click the green "play" arrow. The program only gets 3 rows in when it comes to an "AXIS LIMIT" fault.
Any help would be greatly appreciated.
Good news @Chris Annin! As it turns out, I'm fully retarded. The robot is now 100% operational!!!
Regarding the com port issue:
As my wonderful, beautiful, smart and sexy girlfriend pointed out to me while helping me troubleshoot... The AR2 software was in fact communicating with the Arduino Mega the entire time after all... <sigh> ...fuck
What happened was that I had my Arduino plugged into a shield that made it lay face down so that I couldn't see the orange LED on the board (outta sight, outta mind type deal)
When I used the AR2 software and clicked the "Set Com" button with the appropriate channel, I would watch the python CMD window waiting to see something, letting me know that the communication was successful or something. The first click wouldn't produce any feedback in the CMD window, so I would click the "Set Com" button again thinking that something wasn't communicating properly (this is where the orange LED on the Arduino normally would have flashed, alerting me that it was in fact communicating with my PC - however, being face down I never saw it)
As it turns out, the com port permission error that I was getting previously was caused my the port already being in use from the first time that I clicked the "Set Com" button. I guess that was the software's way of saying "Hey dummy, I'm already in use".
So that was fun.
Anyways, after we figured that one out, we tested the AR2 software again. Still no movement however.
We then disassembled every wire on the robot and rewired it from the ground up.
As it turns out, I messed up the wiring for one wire. The -5V DC wire connected to the motor driver.
I had it wired into my 5V DC power supply's negative terminal (which disables the motor drivers, explaining why I couldn't get the robot to move)
So if anyone in the future has the same issue(s) as me, here's are your solution(s).
Oh and the AR2 software is in fact working on Windows 10, x64.
Chris, I am very sorry for wasting your time regarding this issue, sir.
However, I want to say THANK YOU VERY MUCH for trying to help me troubleshoot along the way!