KRC5 micro, CinfigurationErrorException

  • My guess someone messed up SmartHmi.User.config. Could be willingly or unwillingly. Get a KRCDiag and look into the SmartHmi.User.config. Should be an ASCII file. In the past I had similar issues after people opened files with an (shitty) editor and then accidentally saved the file with a wrong encoding. So the first characters of some lines contained strange characters and Smart-HMI-Config parsers where no longer able to read the files.


    If thats the case just restore the SmartHmi-User.Config from their latest hopefully quite new backup. Reinstalling KSS and then restoring latest archive should also work.


    Fubini

  • My guess someone messed up SmartHmi.User.config. Could be willingly or unwillingly. Get a KRCDiag and look into the SmartHmi.User.config. Should be an ASCII file. In the past I had similar issues after people opened files with an (shitty) editor and then accidentally saved the file with a wrong encoding. So the first characters of some lines contained strange characters and Smart-HMI-Config parsers where no longer able to read the files.


    If thats the case just restore the SmartHmi-User.Config from their latest hopefully quite new backup. Reinstalling KSS and then restoring latest archive should also work.


    Fubini

    Thank you

  • had similar case recently. user chose to generate KRC Diag. it happened that robot was in auto (EXT mode i think). not sure if this is normal or just a coincidence but logs confirmed that PMB killed all power so KPC did not power down gracefully. upon reboot menu file was corrupt. replacing corrupted file with healthy copy from an earlier KRCDiag fixed the problem.


    KRCDiag is (among other things) collecting hardware logs from KPP/KSP/RDC/CIB/PMB etc. so i can see that additional messages and data transfer may not go too well while system is running. but.. not sure why file like this would get corrupt. Cannot think of anything what would need a write access to file like that.

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

Advertising from our partners