Posts by Mariangelo Franzini
-
-
-
To interrupt robot execution, you are either:
- Telling it to stop.....WAIT, HOLD, PAUSE, ABORT, SAFETY etc.
- Robot error is occurring causing it to stop.
Allow me to provide a clearer explanation of my situation. The challenge I face is that glitches often occur in my absence, leaving me uncertain about the events. The issue stems from operators restarting the machine, and the explanations provided are consistently imprecise.
I harbor suspicions that the root cause may be an alarm signal sent by the PLC overseeing the work area, causing a halt in the robot's operations.
In which case all you really have are error logs and operational logs:
SAVE/ELOG
SAVE/OPLOG
You're absolutely correct about what you just mentioned. I've tried other commands like SAVE/ALLLOG and SAVE/FULL, and KRterm consistently returns 'illegal qualifier.'
Unfortunately, attempting SAVE/OPLOG hasn't proven successful either. While the file is saved, it lacks the inclusion of program steps. I've tested this on both the virtual robot in K-Roset and the physical one, and the results were consistent.
Attached are the logs from the physical robot for your reference
Now, this didn't occur when I used a more recent model. I'm attaching the txt file containing the logs for that robot, in which, in fact, the program steps are included.
I've noticed that in one, it says
while in the other, it says
Am I doing something wrong, or is it simply because I'm using an old model?
No controller connecting to an F Series arm has USB capabilities in either hardware or software AFAIK.
You are correct once again; I confused some features with those of a newer model.
Or directly download logs by clicking right mouse button on log menu in the project tree
What you just mentioned works perfectly with newer models, but unfortunately, it doesn't work with FS030L. In fact, when you do that, you are executing the SAVE/FULL command at the terminal.
I want to thank you for your patience and kindness. I've recently started delving into Kawasaki systems. The company I work for wants me to become proficient in programming them to expand the use of Kawasaki robots in the automotive department. I'm putting in a lot of effort to achieve this goal.
-
To be more precise, a real error does not occur, but the robot stops because something happens that causes it to stop. Some bugs in the program.
The robot model is FS030L-A001.
So with the SAVE commands I am able to see the robot's logs, in particular what steps the program took?
In the manual I see "SAVE OPLOG file name". Where is the file saved and how do I access it? If I connect to the robot via ethernet using KRterm, can I save it to the desktop, for example?
Same questions for USB_SAVE_OPLOG. How do I select my usb driver?
Could it be possible to show some examples?
-
Good morning,
for some time I have been looking for an effective way to understand the cause of bugs in my programs when they occur. Unfortunately until now my only tool has been to rely on the word of the operators who were working on the machine where the bug occurred. Unfortunately, however, the reconstruction of what really happened is always approximate and difficult to interpret.
I recently became aware of the "program execution log" functionality in K-IDE. Unfortunately, when I download the program from the robot, I see this section completely empty. Am I doing something wrong? Is this the best way to monitor your code in Kawasaki robots?
Best regards,
Mariangelo
-
The solution was using a newer version of K-IDE, I used version 1.1.3.0 and the bug was no longer present
-
-
Unfortunately I am unable to provide you with a real time video of what I did at work. But this short video sums up my actions.
The KIDE version in the video is 1.1.3.0 but at work I got 1.1.1.0. Could it be that my problem is caused by the fact that I am using an old version of the program? Also, could the fact that the controller is switched on bother the upload?
External Content www.youtube.comContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy. -
When I try to load the interface panel onto the robot from my project opened in K-IDE an error occurs. It's a robot from the company I work for and it works fine, model FS030L-A001. I was wondering if it could be a problem due to the fact that the interface panel is running on the display so it doesn't allow me to change it. I thought about this since the same problem occurs when you modify a running program or an autostart program and they need to be aborted and killed.
What I did was just editing a pilot lamp signal and then I clicked "send interface panel to robot". Is there something wrong or missing from what I did?
Best regards,
Mariangelo