![]() So when I had a moment, I removed them from the project and re-deployed, thinking this would get rid of the nagging error. There was no I/O mapped to these modules, which made their presence in the hardware tree harmless. I found that the WV project for this robot included several ECat I/O modules on the KEB, that didn't exist in hardware (I suspect the project was copy&pasted from an earlier, similar, system). Now, the robot runs fine in Teach and Auto, but there's a constant warning message that just won't go away: KSS 13012 Error during ECat Stack Initialization (No network response). The integrator has only basic knowledge of KUKAbots, and their resident KUKA "expert" is unavailable, hence me dropping in for a few days. The robot had already been programmed and integrated successfully, I'm just on site to touch up a few points and be available if anything unexpected happens. ![]() So, I got contracted to do a quick bit of support for an integrator that just installed a KR10R1000 on a KRC4 Compact (KSS 8.3.33). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |