Re-commissioning or running system?
Looks like you eventually miss some files...
Re-commissioning or running system?
Looks like you eventually miss some files...
You can try to simulate the axes, but I ran into a problem that the axis still need to be connected or not faulty...
$PRO_NAME1[] e.g. "CELL"
$PRO_NAME0[] e.g. "SPS"
but they only show you the name of the selected program, not the subprograms
$PRO_IP gives you a lot more information, e.g.
$PRO_IP.SI01[] Name and Line number of selected program
$PRO_IP.SI02[] if present, Name and Line number of 1st sub-program
$PRO_IP.SI03[] if present, Name and Line number of 2nd sub-program
$PRO_IP.SI04[] if present, Name and Line number of 3rd sub-program
... etc.
would be a good idea to save $PRO_IP before a Cold start of the robot system. Question is, can you declare and write to a Variable of the type PRO_IP and what is the maximum nesting depth?
$PRO_IP0 shows the submit interpreter, which is an easier way to troubleshoot a stopped submit instead of changing the interpreter.
I mean, the programmer copied this parameters from .dat file and get into config.dat. This is one way. This point is not in this .dat file, only in config.dat. Are you sure, that local variable is over the global one? Doesnt robot write error message....duplicate variable or any one?
It won't show an error...
and if any variable e.g. <DECL FDAT FZP=...> is left in the local dat-file it may use that one. If you want to use global positions, you have to declare them before using them.....
Leave the system with local data-files, unless you know enough about data manipulation!
I can not find LTC submenu in Diagnosis in my KSS 5.2
Does selecting that launch an external executable?
If so, is there a way to launch it? (Don't know if useful: i found LTCserver.exe in C:\KRC\BIN but it does nothing)
Thank you
I don't have time to check it now, but yes that should do it!!!
Here is the line out of MenueKeyKuka.ini, KSS5.6.9
mDiagnose =mpTrace, mpLogBook, mpCross, miStackLog, miInterrupt, miEscDiagnosis, miWebDiag, miSafeRobotDiagnosis
and
miWebDiag = LTC, 5000, HMI, BROWSER;http://Localhost/ltc/default.aspx;1
KR C4 you can also change C:\KRC\Roboter\LOG\MaintenanceLog.xml as long as you are familiar with xml's
E.g.
<?xml version="1.0"?>
<XmlLog xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<MaintenanceGroups>
<MaintenanceGroup Name="BasicInspection">
<MaintenanceLogs>
<MaintenanceLog IntervalInYears="1" Maintenance="BasicInspection">
<CurrentDate>2031-12-31T00:00:00-04:00</CurrentDate>
<UserName>Amazing guy</UserName>
<RunTimeInHours>11115</RunTimeInHours>
<OrderNumber>0815</OrderNumber>
<Comment>SIB safety relais checked, local and external E-Stop checked, fan on back of cabinet wiped clean, pressure in counterbalancer checked (within 5 bar tolerance), greased counterbalancer (both grease nipples)</Comment>
</MaintenanceLog>
....
....
etc.
Reset Maintenance KR C2:
- Log on as Expert if needed
- Select Menu Monitor / Diagnosis / LTC
- You see the LTC (Life Time Counter) Login screen
- Enter User name > kuka and for the password type in the red displayed Session ID in reverse order. E.g. Session ID is 0986 type in the password as 6890
- navigate using Enter, Esc and Tab button
- navigate to Maintenance Log, press Enter
- in the List field e.g. Two-year maintenance, select up/down to the maintenance you did
- navigate with Tab to New maintenance, press enter
- your new entry will show in the list
- navigate to main menu button press enter
- navigate to Log out press enter
- last but not least press ESC
KUKA Hotline should know this!
Check the cable From the A3 board labelled X258 this goes to the RDC i have had at least 5 robots where this cable has a very bad bend radius causing the connection to drop . Power off the robot Remove the cable from the board Cut the tie wrap pull a bit slack through and clip it back in
Thank you very much "leg"
But I guess you're talking about a different controller. I have a standard KRC4 NA with transformer. So there is no A3, unless I'm blind.
My connection to the RDC goes from CCU (A1) X34 Controller bus to X21 at the connection plate of the cabinet. And 24V buffered goes from CCU (A1) X21 to X21 at the connection plate.
I changed this cable on one robot and I've have been ok for the last 36 hours. Another robot still got the issue.
Strange is that KUKA saved some money and put a cable tie on the shield instead of a shield clamp. And the shield of the network cable is not connected to X21. And even though the RDC cable has a ground pin, there is no connection to ground on the other side.
Not to my knowledge, you just have to map them correctly
those should offer some insight though this is weird. maybe i am forgetting something, it's been a while since i saw KRC2. the only safety input that i can think of that considers AUT mode is operator safety but that should result in a message. $DRIVES_OFF does not show message but if it is set to 1025, this cannot be a problem...
$Drives_off is one thing, but the X11 signals Enabling, External E-stop as well as External Drives off and the Qualifying Input are necessary to run the robot. Plus You need to have internal or external 24V and the Safeguard.
Maybe you're missing something simple like the Qualifying Input...
Does your robot system run in T1 & T2, or any limitations there?
Please post screenshots of the ESC Safety Diagnosis for all nodes available, something like this:
Thanks for your help!
I looked up V1.x that didn't support it at all. Believing in documentation V2.x should work, but like said I even can't get online. The Balluff and SMC devices are able to support Quick Connect at least according to their manual. But they want the explicit messaging to set 1 or 2 attributes. Another Turck device I have allows Quick Connect in WV. The Web interface on Balluff, SMC doesn't have an option to enable it....
I guess the only way to get it working, is to activate the attributes with Rockwell software, hoping that ownership is no problem!
you don't mention what part of the procedure#2 does not work for you... but i am guessing it is because your target device is not an EIP scanner (master), it is adapter (slave).
Very interesting panic mode. My documentation "Issued: 11.03.2013 Version: KR C4 EtherNet/IP 2.0 V2 en (PDF)" does not show that it is limited to the EIP Scanner. Please provide info which Version of documentation you used.
What doesn't work for me is even after changing the EthernetIP Settings, to match my configuration, the Context-menu button <<Connect>> doesn't establish Online mode EthernetIP.
Crossposting is not a good idea:
Sorry Hermann. Looked like nobody paid attention to the other post. Can I delete this Thread somehow?
20 robots, using 20 different types/brands of I/O? was this some charity donation?
No. I have these robots in different Production lines. The tools are unique based on the requirements of the individual tool. E.g. One EOAT uses a Balluff IO Link with a Schmalz Vacuum pump, versus the other one use SMC to actuate clamps.
so you already have two solutions.... what is the problem?
I need solution 1 to work
can you be more specific? who and what exactly did you ask? if you tell that you have multiple solutions, why would they spend more time on you when others need help too? and if you ask for assistance coupling of for 20 brands, nobody has time for that. be specific, ask about one thing. if you asked for an example for explicit message, over EIP did they share it or not? according to KUKA user documentation and training manual on EIP there is no mention of explicit message. I know that it is possible +(and i have seen an example few years ago) but it is not advertised.
I guess I need to re-phrase, Solution 1, is according to the manual the solution, but I can't get it to work. I asked the Focus Center to help me to get online with EthernetIP, but so far nothing worked.
Procedure Point #2 is not working!
Screenshot is out of the manual:
Use QuickConnect on KUKA KR C4 V8.3.x with EthernetIP V2.0.3
I searched in the Forum, but didn't found what I look for.
Problem:
To improve cycle time, I need to make sure that I can use QuickConnect EthernetIP devices on Tool changers. I have around 20 robots, that I try to improve.
Solution:
Looking trough manuals of KUKA, Turck, Balluff, SMC, I need to either enable QuickConnect under Device, Exclusive Owner, Configuration settings or I need to use Explicit messaging.
Like the Turck Device, you just activate it and you're done.
But other devices like SMC don't show this tab and according to their manual, you have to enable it using explicit messaging.
I need a solution that works:
Following all the required steps, I end up that I am not able to go online with EthernetIP. Even though I connect my Laptop to the KLI, ping all necessary addresses successful and change the settings for EthernetIP, I just get
Also turned my Firewall off and disabled all other Network adapters.
KUKA has been no help so far.
Anybody ever got Online with EthernetIP in WorkVisual?
I used WV V4. and V6.
Use QuickConnect on KUKA KR C4 V8.3.x with EthernetIP V2.0.3
I searched in the Forum, but didn't found what I look for.
Problem:
To improve cycle time, I need to make sure that I can use QuickConnect EthernetIP devices on Tool changers. I have around 20 robots, that I try to improve.
Solution:
Looking trough manuals of KUKA, Turck, Balluff, SMC, I need to either enable QuickConnect under Device, Exclusive Owner, Configuration settings or I need to use Explicit messaging.
Like the Turck Device, you just activate it and you're done.
But other devices like SMC don't show this tab and according to their manual, you have to enable it using explicit messaging.
I need a solution that works:
Following all the required steps, I end up that I am not able to go online with EthernetIP. Even though I connect my Laptop to the KLI, ping all necessary addresses successful and change the settings for EthernetIP, I just get
KUKA has been no help so far.
Anybody ever got Online with EthernetIP in WorkVisual?
I used WV V4. and V6.
I only see it on 2 robots and the KCB issue happens sometimes once a week, sometimes 8 times a day. There is no way to reproduce it, KSS is 8.3.29.
If it happens, I always have the LED plus errors on KPP1, e.g.
It looks a little bit different every time, so not related to a particular axis.