as i understand from Automatic external settings Drives on depends on input 140 by default, no?
i am looking at input 140 (Drives ON) and it is not coming even when the I is green.
At the moment it is changing from green to red in AUT mode without a reason eben when the robot is not moving
is that the reason the I (io drives) to change its state from green to red?
after another braketest and the same message, i disabled the braketest in motiondrv.ini.
For now it is working ok, hopefully that was the issue.
One correction - the KSS is 5.6.12, not 5.6.10
yes, we did cold start.
The message after the breaktest you can see on my first post.
I will try to do it again now.
Hello, i need help with a robot, who is changing by itself the driver status - the I on the bottom left of the screen.
System is krc2 ed05, KSS
126.96.36.199.12 , Safe Robot with SafeOp 2.2.6. The robot is KR150 L110
The robot worked fine until yesterday - it asked for brake test. After it was done there was some errors - please see the attached screen.
The problem we have is after that the robot started to change the driver status the I sign is going from red to green and back by itself.
After we restart the robot, it is ok, can be moved by hand etc. When we execute a program in AUT mode it is starting and after a few movements stops with red I (IO status sign) and it is impossible to be moved even in T1.
To me it looks like a bad connection somewhere, but not sure where to look exactly. We exchanged the KCP panel but the problem i still there.
Anyone faced such situation?
Thank you in advance!
Yes, AUT mode.
Already swapped the KCP - nothing changed
$DRIVES_OFF and $MOVE_ENABLE are as by default - 1025
If you take a look at the PDFs you will notice that there are some more pins:
No messages at all it seems all is good... i recall may be i saw "safety circuit not ready" but it was cleared afterwards and didn't came up. Also i did some cold starts without any warnings etc...
I will check the AutoExternal signals and write here
The connections - checked triple with multimeter (and more):
I have nothing at 71, 108, 70, 54
Thanks for replying!
I did not connect 37-40 just used the one i am attaching here.
But something stops the robot to move in automatic mode.
I am trying to run a KR16-2 KSS 5.6.10 robot with KRC2ed05 PC
I did the X11 from the forum files - standard KRC2 type and the robot is moving fine in manual mode (T1 and T2) but cannot be moved in AUT - the I stays red
X11 doesn't have pins on numbers 37 and 40
The KSS is clean install, so all in Automatic external is at default settings.
I am attaching two pages with the description of the X11 of this particular robot as i suspect that there may be is something else need to be done on the X11
I swapped the PC and the KCP with no luck
Any advise appreciated!
Yes, exactly how i had it running - both plugs AND the lamp
Ok, confirmed - when the lamp is up there it is all ok
of course the two plugs also should be connected.
Seems like a useless thread if needed - delete it.
Hi guys, another problem to solve - i need to use a formerly cooperative robot KR16-2 with KSS5.6.10 as a standalone robot. There was two robots of the same type with a lamps on the A3 axis (removed now)
I reinstalled the KSS so it is a clean install now the problem is that they dont want to move - no errors on the pendant, but still i cannot enable the drives.
Any idea where to look?
there are two plugs - X270 and X271 which i am not sure how to use - may be the problem is there?
Or it is with the lamp for A3?
For me it looks like messed up procedure for end of the seam in config.dat
Check again all the signals where you define the end of a seam in Arc.Tech section in config. dat
Never used Kempi, so cannot help with the IO numbers
Hi again, coming back just to confirm - this was the reason for the PNIODriver to show that message - changing it to "false" solved the problem
Yes, thats was i also was thinking.
i found that line in PNIOdriver.xml to be "TRUE" (see attached photo)
I changed it to false and will try to upload to the controller - will report back if it helps
you could uninstall profinet
Thats what i did ... first in WV and afterward on the controller - de-installed the profinet as it was looking for connection to the PLC. Now that message still appears - may be i need to remove the profinet on some other place/file?
Hi again, i have another problem - it is not messing the work of the robot but i really would like to get rid of it.
On the same robot i have now message "Boot failed for module: PNIODriver"
I am not using Profinet, i use Ethercat for IO, so i removed the installed previously Profinet Nexxt driver as it was looking for a PLC or something
There are no other errors left, and the robot is working just fine.
Any idea how can i remove that message from coming up?
Hi, just to update - i added the wagon driver and now it is all working
Thanks panic mode, as always, i am keeping your beers on a safe place, i recommend you to accept more concentrated liquid, as the amount of the beer is really huge now