Software applications for robots

Every robot runs a piece of software (called “software application”), which is installed in the teach pendant and allows you to:

  • Create and maintain a database of models (create, edit, delete, copy)
  • Define the pick point, the target point and any other points along the robot path; as well as numerical, textual and binary (yes/no) information for every model
  • Each of the above data characterizes the model and remains associated to it, so as to minimize the set-up time of any previously created model.

 

This software application interacts with the robot software, filtering and reformulating the information that the operator receives, so that he can keep under control all and only the data necessary for the operation of the robotic system, without being familiar with all the information regarding the native OS of the robot. It is always possible to toggle between this application and the robot software by using a single key to access all the functions provided by the robot manufacturer.

In addition, the software application has a section for the various alarms and another for “scheduled maintenance”: for each type of service provided for in the user manual, you can read a short description and view the number of hours left until the next recommended inspection. By doing so, you can see at a glance whether the robot is in good working order and you will not risk forgetting routine maintenance.

This piece of software is capable of handling any item in the most common applications, in particular in cycles where the robot follows similar paths and only the initial position, the end position and a few other details change, e.g. direction of approach to and exit from the machine it tends to.

In such cases, we can use the robot without concerning ourselves with the robot programming. This is called “guided programming” and all the information is provided to the robot in a graphic and intuitive way. Other applications require the robot to follow more complex paths; for instance, a different path might be required for each model, making it preferable to use the native programming language of the robot; this way, we can exploit the full potential of the robot in terms of movement instructions and logic. This is called “free programming.

You can have both systems installed on the same robot, and then, for each model, decide whether to use the default structure of the “guided programming” or to avail yourself of the extra freedom afforded by the “free programming