What other people asked us about drag&bot
Yes, this is possible as long as the program does not use functions that support either only the iiwa or just the UR. Conversely, if the integrated, model-specific force function of the KUKA iiwa is used, these function blocks must be replaced accordingly with another robot.
Since the 3D model is a visualization and not a simulation, possible collisions are neither checked nor displayed. drag&bot was developed for direct “online” programming on robots. There are already many software solutions that allow offline programming. However, these are designed for robot experts.
Yes, that is possible. On the one hand, you can create new function blocks “graphically” by combining existing function blocks. On the other hand, you can implement your own function blocks in the programming language Python.
No. Since there is no automatic path planning, there is also no automatic cycle time optimizer. However, there are many simple ways to manually optimize the cycle time: adjust points, adjust motion parameters, execute function blocks in parallel, …
3D geometry data in STL and Collada format can be uploaded into the visualization. It remains a visualization, wich means the points of the CAD model can not be used as a reference for programming points and trajectories of the robot. Applying points and trajectories from a CAD model is a feature that is on our development roadmap, but is currently not available.
The installation of drag&bot works on an IPC with preinstalled Linux with a mouse click via an installation script. This requires no special knowledge of Linux. For KUKA and Fanuc robots it is also necessary to configure a program on the robot controller. For this purpose, commissioning on site by drag&bot employees is currently necessary.
If you do not want to take care of the installation of drag&bot on an IPC yourself or have never installed Linux before, we are happy to provide you with a prepared IPC that you can use to start directly.
Robots: KUKA, Fanuc, Denso, Universal Robot, ABB. Gripper: All grippers based on I / Os or IO-Link. Cameras: Sick PIM60, various USB cameras. The current list can be found here:
We were able to show in a study with an automotive supplier with subjects of different expertise that production staff with no robot skills was able to use the robot independently with drag&bot, whereas this was not possible with the standard programming interface provided by the robot manufacturers. Experts (i.e., people who regularly work with robots) became 5x faster in application programming compared to the standard programming interface.
Do you have an use-case you want to try with drag&bot? Let’s discuss more details together.