Sounds like the servofloat option.
Posts by Mike01TJ
-
-
You can set up cubic interference zones and monitor the output. Basically a 3D cube in space that triggers an output when the TCP is inside it, or outside it. Check manual 178642-1CD (section 8.6 - Interference Area)
-
I believe a software mismatch connects but gives you an error.
Change Ethernet ports on the Doosan.
Try a different Ethernet cable.
-
A DX100 pendant cable is compatible with the DX200 and FS100 but not the YRC1000. The YRC1000 cable is unique to the YRC1000 controller/standard pendant.
-
How do I enable the angle option for a position variable. I have two robots, one shows it in the position variable screen, the other doesn't and I can't figure it out.
YRC1000 GP88
Options - Speed Control, Endless Rotation
Thanks,
Mike
-
WattUp's answer is the way.
-
The FSU uses the tool data for multiple safety features and changes can create a hazard if not properly accounted for. Like anything safety related, redundancy is king.
Readback->Write->Confirm -> ✅
-
Depending on where you are, you can ship the robot to Motoman for calibration. It costs less than the software but you have to ship the robot. They can also come to you, but that may be cost prohibitive depending on you location.
-
I'll hop in with my 2 cents. Welding robots(besides the AR700 and AR900) usually use an upper arm assembly that include a through hole in the T axis to accommodate the torch lines and allow T to turn without swinging all the cables and hoses around. The 35L is not designed this way so potential collisions could be an issue for programming due to the wire/gas/electrical lines hanging out over the edge. Also, the robot was probably initialized as a General Purpose robot, so it lacks ARCON/ARCOF and their associated files. Without re-initializing the controller as a welding robot, you would have to figure out some other way of creating that functionality. How has it not done well with its original application?
-
It's really easy if you have access to a smart pendant?
Other good commands include Switch/Case, Gete, Sete, Relative Shift(paid option)... You can also math out the positions using using preset programs or using input from a PLC. The I/F Panel(paid option*) to choose which SKU to palletize.
-
If you will be modifying the ladder with any frequency, or make a large amount of changes, it is worth it. The ability to quickly make modifications, upload them and then watch the ladder in action while still using the pendant can save a ton of time
-
That's not bad number for just programming them out. You can program the first layer or two, if they interlock, and run a shift for the remaining layers. If singularity becomes an issue, use relative job shift(option) to create individual programs for each layer and touch up points that act weird. You can also create the background math to pump out the placement position variables. Otherwise, if you have access to a smart pendant, the Pallet Builder program(it's free) on Ver3 is pretty good. It provides ease of programming without the complexity and cost of PalletSolver. You can also switch back to a standard pendant once your done.
-
Q3 PalletSolver is great if you have a bunch of SKUs that you will be palletizing. How many different parts will you be running?
-
-
Reach out to Motoman support with your warranty ID (on the front of the controller) and request them.
-
This could be accomplished in the ladder program. Search for "ladder" on the Motoman website to get the proper manual for your controller.
-
What sort of errors?
Can you elaborate on your issues with precision?
-
robotruler and alex1793 haven't logged on to this site since 2021, so I am not sure you will get an answer out of them. You may want to start a new post and provide the details of what is happening. Look through the previous posts on this thread to get an idea of the relevant information.
-
Any chance you want to link the CMOS?
-
The gripper will function with either pendant, they just wrote their instructions with the assumption you have a smart pendant. Looks like the grip/ungrip is actually a job call with arguments determining the action.
The EtherNet/IP function will need to be enabled and set up to communicate with the Robotiq controller. Here is the manual for EtherNet/IP on the YRC1000 controller.
You can always search the Motoman website for any of their documentation.