Pular para o conteúdo principal

Let's talk about program standardization ...

 Hello guys! Let's go to the third blog post!


Something indispensable for maintenance in the industry is the easy and quick interpretation of the programming, for which it is essential to standardize the programming. If the maintainer visualizes the programming and in a few moments can understand the logic described, the maintenance of the equipment becomes faster! As my area of ​​understanding is KUKA robotics, I will raise some points of KRL programming.


Points that I think are important for a standardization of programming:


-> If possible, use a main program with global subprograms. In the main program have the macro logical structure of the station and global subprograms with the specific logics for each process in which the robot does, some examples of subprograms: deposit machine 1, withdraw machine 1, deposit machine 2 and withdraw machine 2. So if example the maintainer visually verifies a problem in the deposit of machine 1, he already knows where in the program he will work;


-> Request organization and several comments on the schedule;


-> Standardize the I / O's declaration, a suggestion would be in the declaration to inform what itself  does;


-> Standardize specific inputs for important bits of the robot, example: External automatic, errors, physical inputs / outputs, network inputs / outputs, among others;


-> Use the I / O's declared in the logical structures;


-> Use the same I / O's declaration on the input and output verification screen (descriptive text in the case of KUKA robots, my friend Márcio Massula made an interesting post on his blog regarding this);


-> Create comments for the robot's movement points, informing which displacement the robot will make;


-> Make relevant robot information available on internal HMIs (teach maintenance how to access them);


But the most interesting thing besides these points is to go to the factory and check with the maintenance the relevant items, creating relationships between the engineering and the technicians of the factory.

Comentários

Postagens mais visitadas deste blog

Are you taking care about your new KUKA Robot? Or are you forgetting this?

Are you taking care about your new KUKA Robot? Or are you forgetting this?   When passing through companies here in Brazil, I came across the following problem, most of the integrated KUKA robots are without load determination! When integrating into robotic cells, the load determination is something that should not be missed, as it is with it that you will make last longer the reducers, servants, pulleys, among other important parts of the manipulator. Without the load determination, the kuka robot comes from the factory with the disregarded determination (your robot will work ignoring the tool's mass) or at the robot's maximum payload (your robot will be forcing itself to lift a feather). Both conditions will make the robot wear out faster. With the correct load determination, the robot optimizes the movements for the correct mass informed, increasing the useful life and decreasing the cycle time of the process.   How to make the correct load determination? There are 2 ways fo

Help maintenance work faster with the company's robots.

 Is the company's maintenance taking too long to save points in the schedule? But are you able to save it more easily? To save the points it is essential to create a TCP plus coordinate system, especially if the machines are not in level with the robot. See the example below: While the robot is manipulating, the deposit and handle position of this machine is angularly different from the robot's coordinate system, for example, when i have to move only the tool forward, due to the problem reported above i have to move the robot in X and Y making a "step ladder", this type of movement is very difficult when fine adjustments are needed. Remembering that the robot works on the right hand rule. After the creation of a TCP plus coordinate system for the tool, the adjustments became easier, since the robot's movement will be in relation to this created system. To move the robot forward in the new case, it would use only the Cartesian X axis. There are several items that m