I have a customer whose KRC4 (KSS 8.3.4) OfficeLite has developed an issue we haven't been able to resolve. Unfortunately, my OL experience is all in 5.6, so...
The issue arose when the customer tried to build a new project in WorkVisual (with a different robot model) and send it to the OL controller. Everything seemed to work fine, but whenever the new project is activated, it generates an error message about the "Nexxt Driver" (I didn't get a chance to grab the error code or full message, darn it, but it says it's an I/O driver). I've never heard of this one.
The worst news is, even the WV projects that worked previously, now show the same error when activated.
I messed with it for a while, attempting to activate the original Base Project, making a completely new project from scratch, and even making copies of the most recent "good" project and making semi-random changes (I/O tree, robot model, external axes, etc) just trying to get some change. No luck -- I could generate lots of additional errors (MADA mismatches, power module failures, etc), but I could fix those. But this "Nexxt Driver" error seems to be intractable.
Part of the problem is, I'm not sure if this is a project-level issue (for example, something special that needs to be done for an OL machine, as opposed to a "real" robot), or if this might be some kind of "damage" to the OL that might require re-creating the entire Virtual Machine, or something along those lines.
(and no, there are no image backups, KSR, VM, or otherwise )