Use robots for different tasks with drag&bot
Enable your existing employees to control robots like any other machine
Get a robotics quick check for your company
In order to be able to respond individually to your wishes, please write us in the form on the right why you are interested in drag&bot and in which application you can imagine to use the software.
We will show you how to benefit from drag&bot in a 30 minute web-session!
Frequently asked questions
3D geometry data in STL and Collada format can be loaded into the visualization. However, this is a visualization, i.e. the points of the CAD model cannot be used as a reference for programming points and trajectories of the robot. The import of points and trajectories from a CAD model is a feature that is on our development roadmap, but currently not available.
Yes, it’s possible. Prerequisite is the purchase of a developer license including training. Function blocks are programmed in Python.
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.
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.
An Internet connection is no longer required.
Basically every IPC can be used on which Linux (Xubuntu) can be installed. Besides drag&bot other Linux programs can be executed on the IPC. However, it is recommended to buy drag&bot pre-installed together with an IPC, because then you do not have to take care of the installation yourself and we guarantee that drag&bot works well together with the IPC.
Standard components provided by us, e.g. robot drivers, cannot normally be changed. You can change, extend and adapt components you have created at any time.
No, this is not possible. drag&bot programs can only be changed and executed in drag&bot. Reason : drag&bot does not create programs that are executed on the robot controller, but contains itself an execution environment for drag&bot programs, the so-called drag&bot runtime. drag&bot programs can only be executed when this execution environment is running, i.e. when the IPC is connected to the robot controller and the drag&bot runtime is running on the IPC.
Yes, they are. This is either possible via a function block (for sphere) or CAD export (GCode).
It’s our proprietary cloud. In principle, the drag&bot server can also be installed in local or company-owned clouds. However, this means a considerable additional expenditure. For the first installations it is recommended to use the drag&bot cloud. If you have any questions, please contact us.
The required operating system is Xubuntu 16.04. When installing drag&bot, ROS Kinetic is also installed.
A computer with Intel i5 processor, 8 GB RAM, 64 GB hard disk and at least 2 network interfaces is recommended.
The license has an unlimited duration. You can create new programs and adapt programs as long as you have the support package. If you decide not to extend the support package, you can only run existing programs, but you cannot create new programs or modify existing programs.
Vacuum monitoring: If your gripper offers this feature, you can use it either via the robot’s input I/Os or via evaluation by a PLC.
Controlled joining: With drag&bot usually with the help of a force-torque sensor and the additional package FORCE. Motor current monitoring is not available for all robot brands and models and is usually less accurate, so we do not currently support it. Against additional expenditure it would be possible to integrate this function if necessary.
Yes, there is an error handling for every single function block. “n.o.k. sequences” can also be implemented using “if-else” structures.
Yeah, that’s exactly how it’s done. You can choose between Cartesian, Joint and Tool coordinate systems. Movements can be executed as PTP or LIN movements. In the end you have all the parameters that are also available in the motion functions in the classic robot programming languages.
You can grind intermediate points as much as you like to save hardware and time. An automatic optimization is currently not planned or available.
We are currently supporting Siemens S7 and are working on supporting the Beckhoff controller. Interaction (start program X) or constant communication is possible. Technically, this information transfer is implemented in Siemens TIA via a Modbus server.
Yes. Most quick-change systems can be controlled via I/Os. These can be controlled via the robot controller or a PLC.
This depends on the communication interface of the tool. As a rule, complex grippers are equipped with PLC systems, where communication via I/O or Modbus interfaces is easily possible. Alternatively, the interfaces to grippers are often implemented via the “IO-Links” protocol. Finally, you can develop function blocks in drag&bot yourself in Python, where you can also implement RESTful calls or other interfaces independently.
No, but it is very fast to create them with drag&bot.
Low, the integration takes between 0.5 hours (UR, Denso) and 2 hours (Fanuc, KUKA, ABB). For Fanuc, KUKA and ABB, packages must be installed in the controller. Typically, we support the customer in setting up these models on site.
This is not necessary. drag&bot only uses interfaces approved and documented by the manufacturer for communication with the robot controller.
Yes, this is possible as long as the program does not use functions that support either only the iiwa or just the ABB Robot. Conversely, if the integrated, model-specific force function of the KUKA iiwa is used, these function blocks must be replaced accordingly with another robot.
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, …
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.