Stop due to locked drive A...?

don't recall seeing this... "lock" is something usually seen with safety like SBM or SHB

the message number is low suggesting something that existed since KRC1/KRC2 times though it was not documented there either. also message itself does not seem to appear in any of the newer KSS versions either - the last KSS that did have it may be the KSS8.2...

my next thought was maybe it is part of the option such as SafeOperation or SafeRangeMonitoring etc but messages from those tend to be in 15000 or so.

the other problem is that you are looking at the messages only in the message view. this is bad. it is only list of current messages. and since you cannot find much about this one, you need to broaden the search. check what happened just before these messages (close timestamp) even if those other messages are no longer displayed. maybe they appeared only momentarily so.... check the message log.

reading message logs on the smartPad is hard. i would collect archive and use offline copy of LogViewer on my computer. this gives you not just more screen space, but also additional search options, faster interactions etc.

another thing i would look at are safety signals from PLC.

perhaps because safety PLC locks the robot - intentionally or accidentally (scan glitch or logic problem). check things like SHS1, SHS2, SBH, SBH1..6, UER1..16 etc. or create temporary program that forces them on. also could be network issue, (configuration, missing packet etc.). so i would try isolating this to as small of a LAN as practical (just robot, PLC and your computer) until further info is found.

at any rate, i hope this gives you something to try...

If you check for help you will find this

yes... that is the message...

and its value is to serve as brilliant example of something perfectly useless. and the proof is that both presence and absence of the this message would make absolutely no difference whatsoever, regardless who is standing next to that robot and looking at the teach pendant.

all adults (and specially robot developers, technical writers) should be forced to spend 5min to watch something like this. it would make them so much better in their work. when problems happen, users expect instructions...

As panic mode mentioned:

You only show the message. Normally you need to check "what happend" before!

Using log Viewer could be helpful.

Checking the files in the log and log\system directories could be also very helpful

HI,

You said the robot have tested for a week. Do you mean it is testing with PLC ?

I think you can check the power cable and the resolution cable.

if the connector is fine? how about the pin inside? if the connection well?

From your message, the error is not only for A4, It really looks like the cables are not connected well.

what seem to be the problem? everything needed to troubleshoot is already stated...

open file in favourite text editor like Notepad++
verify time stamp order and note that in this case the newest messages appear at the top.
then search for your problem message, in this case 3154

once you find one or more of them, see what messages are just before them.

for example i see this:

#104: M_3154
16:50:02.165 26.08.2024
M_3154

Parameters: P_0
Module: CrossMeld
MsgNr: 3154

#105: M_26170
16:50:02.149 26.08.2024
M_26170

Parameters: KPP, 1, 0x00000200
Module: CrossMeld
MsgNr: 26170

message #105 appeared 16ms before message #104.
that happen to be message number 26170

then you lookup that message and see if that could be actual reason that you are seeing message 3154.

and that it is mains failure.

do you think that mains failure occurring 16ms before some axis is locked could be an issue? do you think that mains failure could affect any axis?

then you try to see how often that happens... and the log says message 26170 is mentioned hundreds of times. did you reboot controller so many times? or do those message appear also when you try to run robot?

that is obviously not a way to run production so you need find the problem, whatever is causing too large voltage drop... like too small transformer... or too small wire cross section or too long mains cable... or loose connection... but this could alco be due too large load... or too large acceleration. so for test lower the OV_PRO from 100 to 10 or 30% and trry again. do you still see the same issue?

one you find and fix this then you try it again and follow the process over and over until you weed out every issue...

It actuallly started before with error

then this message came up

With the explanation

parsing text file is not for everyone. which is why i suggested using LogViewer. go to robot D:\, under KSS installer there are some tools including LogViewer. install it on your computer add message files. then drag and drop archive or KrcDiag onto LogViewer window.

you can also get it from newer KSS as they are more polished. for example the newer ones allow you to have single LogViewer work with messages from different KSS versions.

then you have something much more user friendly than text editor

Did you resolve this issue? We're having the same issue with similar mains phase error codes.