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
Postar um comentário