Arm 3 Connection Error
- This topic is empty.
2015-02-17 at 20:45 #6081AnonymousInactive
I just assembled my Arm3 kit and I’m trying to connect to it run some sample code, however I’m unable to get the arm to move. Here is what I have done so far…
1. Installed Rumba firmware (prior to installing the rumba firmware the robot arm was moving back and forth, I assume for default code similar to the Makelangelo, however since uploading the firmware, the motors have stopped working).
2. Connected via the serial port, but the robot arm did not recognize any commands.
3. Tried connecting via the software (via the correct port), but it just froze anytime I tried to input any gcode commands. Also tried the r,f, etc. movements but no response.
4. I tried to upload the firmware_ams2 to board, but there was an error because FORWARD was not declared.
Here is an image of the wiring:
Received this error in arduino after triggering the limit switches:
java.io.IOException: Input/output error in writeArray
at gnu.io.RXTXPort.writeArray(Native Method)
I’m not sure what I should try next. Any feedback would be great!2015-02-17 at 21:23 #6951AnonymousInactive
I just noticed the limit switches were installed backwards, so I just flipped them but it is still not working…2015-02-17 at 21:38 #6952AnonymousInactive
Also, the motors are engaged when I power the robot arm, but I’m not able to activate them either through the serial port (the serial port does show Arm3 .3 at the top and the gcode options), or the software.2015-02-18 at 01:19 #6953AnonymousInactive
_AMS2 is for Adafruit Motor Shield v2, it won’t work on your board.
I turned on my Arm3 and immediately experienced the same problems you’re seeing.
It seems that in Arm3firmwarefirmware_rumbamotor.ino there are a few #define mistakes that are causing the board to reboot over and over again. in motor_setup() the following code should be…
#if NUM_AXIES > 3 // new, caused out of bounds problem.
#if NUM_AXIES > 4 // was >3
#if NUM_AXIES > 5 // was >4
So… my bad 🙁 Github GUI for windows is being dumb, so it’s going to be a moment before I can check this in.
I really really want to get OpenGL and swing components playing nicely together so that I can combine Arm3, Makelangelo, delta robot, and all future robots under one app roof.2015-02-18 at 02:36 #6954AnonymousInactive
I just uploaded the new code…but still no success. Can you offer any other suggestions?2015-02-18 at 04:53 #6955AnonymousInactive
Here is what the serial port is outputting…a series of >>>>>>? Is this typical?
M18; – disable motors
M100; – this help message
M114; – report position and feedrate
M1000; – set GUID
F, G00, G01, G04, G17, G18, G28, G54-G59, G90-G92, M06 as described by http://en.wikipedia.org/wiki/G-code
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>g28>>>>G28>>>>M100>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>2015-02-18 at 06:02 #6956AnonymousInactive
Yes. the board sends > to indicate it is ready for new commands. Some very rare occasions the > is never delivered. The easiest solution was to send > about once a second. It’s kind of like a ping/keepalive?2015-02-18 at 14:11 #6957AnonymousInactive
Thanks for your replies! I’m not sure what else to do…like I said before, when I initially turned on the arm, all the motors were working, until I uploaded the firmware. The motors are now enabled, but locked. Is it a wiring issue? Any additional advice would be helpful!2015-02-18 at 15:45 #6958AnonymousInactive
G28; will make the robot home.
The normal gcode commands will move the arm.
The Arm3 github project has an app has more good stuff.2015-02-18 at 15:50 #6959AnonymousInactive
Thanks for the reply. I’ve tried inputting the code (G28, etc.) via the serial port, but no response. The arm does not move. As I mentioned earlier, I tried the software as well (using the r,f,etc. keys), and the same result. I’m stuck, and desperate to get this guy running.2015-02-18 at 23:37 #6960AnonymousInactive
Please email me directly, I am on the road another 40 minutes and then I can do a gchat with video to try and help.
- You must be logged in to reply to this topic.