Optical pick and place robot arm with ArUco markers: part 2
Вставка
- Опубліковано 2 кві 2022
- I extended the functionality of my Python controlled robot arm. With the use of ArUco markers, I was able to eliminate entering the coordinates of the position of the object. The pick and place robot arm now works based on optical feedback from my phone camera.
Check out the first video on how I controlled the robot arm with Python.
• Python controlled robo...
Code:
github.com/NNaert/Python-cont...
Tinkerkit Braccio robot arm:
store-usa.arduino.cc/products...
Very well done. Excellent work.
Very nice!!!
🌈 Very well done. Great job. I say too❗
Good video!. I have a similar robot arm, but I don't know how to start with inverse kinematics
🔥🔥
Can i use regular 6 dof robotic arm...??
I found an aruco cube 4x each side Is it worth anything?
Hi, I’m working in a project with April tags for a robot, I’m in a FRC team and I’m interested if we can get some of your help, because the use of Aruco markers and Apriltags is a very new topic for us.
how did you do the inverse kinematic to the arm?
Is there a way i can get in touch with you??
how do you deal with the height of the object? Or did you just set a Z coordinate to make sure to get the piece?
I want to learn programming
"prev_teta.txt" file are missing i can't complete the project without this file.. please can you provide the file
There are some important mistakes, that I saw you on your first video and still present several months later. Going further than using an arduino to send gcode to move servos or testing opencv, probably people here expect some work on the arm itself. The first section of the arm has to move in the opposite direction of the object to keep the center of mass near the base. The maximun distance is not what you get with all arms in line unless you add some counter weight, this is so wrong for that poor toy. You are making the arm even worse than the construction of the toy is itself. Second the movement need to have a PID control of the speed to avoid that shaking at the end of the move. The backslash can be correct if the last move of the 3 sections are possitive in direction of the object (not the joint to the arm), and not just moving all at the same time and don't calculate the finish time. Also when lifting an object, you cannot rotate just the base and lift it. You have to split the movements at least in 2 joins to lift and use more in the joins closer to the object than the base or better to spread the movement in the 3 joins with some weight calculation to avoid the shake even more. No excuses it's just foam. Also you are not lifting the object, just rotating it, and the object should lift straight and land straight witch is really easy to program. Instead of playing with opencv with cards that we are boring to see, use it to calculate if the finish move of the arm before dropping the object is correct. This is also done in the industry a lot, to have cameras to center with precision. After that adjust, check again and drop the object. This is the kind of things you probably need to figure out instead of running code fast and record a video to youtube. The