A robotic workcell is defined as the complete environment around a robot. This environment may include tools, machines and/or other robots.
In this activity you will use a robot and a microcontroller system to recreate a workcell. Your workcell will incorporate all of the devices that you have learned about in previous activities including: ● Inputs & outputs ● Sensors ● Conveyor belt ● Machines ● Robots You and your team will design, organize, create, program and test a full work cell.
Often robotic arms need to communicate with other devices or controllers in a work cell, or factory. This is called HANDSHAKING and can be done between different machines, devices and robots. It is a very simple form of communication and is done with simple ones and zeros; or “ons” and “offs”.
In this activity you will use all of the knowledge learned in previous activities to make a Dobot Magician Robot communicate with a VEX cortex.
Often the process of handshaking goes beyond a robot’s need to communicate with another robot. In industry the process of have Programmable Logic Controllers (PLCs) communicate with each other, or Robotic arms can be just as simple as having two robots communicate.
It is a very simple form of communication and is done with simple ones and zeros; or “ons” and “offs”. In this activity we will reuse the theory of communicating with simple ones and zeros; or “ons” and “offs” from the previous activity. We will replace the robots with two microcontrollers. For this activity, we will focus on the wiring and syntax programming for two VEX microcontrollers.
I used the Dobots last year to do activity 4 Using Digital Inputs (Here) and it worked great! The kids are having a blast! But no matter what I do this year, I cannot get it to work on any of my robots. How do I fix this?
Well….. My bad…. I’ve been telling y’all (for you Texans out there) to be sure your wiring it correctly, and be sure it’s plugged in the correct port…. but that doesn’t seem to be the problem. The problem is a bug in the latest version of the 1.7.1 software. I am told that the bug will be addressed in the next release of the software, but no one knows when that will be released. So the safest answer right now… I know it is hard for some schools to do, but to revert to version 1.5.1 of the software. I will let you know as soon as I hear that the new version is out!This only seems to be a problem if you are using Teaching and Playback…. It works fine in Blockly…
To do this, follow the steps below:
3. In the resulting window choose version _Magician Studio v1.5.1
4. Delete the new version from your computer and reinstall this older version… until the new version with the bug fix comes out. Sorry for the hassle! In my classroom I am lucky enough to have the older version installed so I did not have this issue.
5. I strongly suggest that you do NOT install updates mid year!
Do you have any ideas for ways to teach students about parts feeders in industry?
Imagine a project that incorporates VEX pneumatics, 3D printing, CAD design, and Robotics all in one! That’s exactly what we did here. I taxed one of my students with this “Going Beyond” activity: Design a pneumatic parts feeder using what you have learned in CIM class so far, and here is what he came up with!