FILE-008 when running Karel file

    Hello!

    I have encountered FILE-008 error, and I'm having a really rough time debugging it... As I understand from the error manual, it comes from an "Illegal Device Name", and that the device name might contain illegal characters. Great. No more info there, really.

    The interesting thing is that the same code is executed without a problem on two different CRX robots, with a slightly older SW (updated within the last year), while the one that encounters this issue is running a more recent SW version (V9.40P/63).

    There is also an older version of this code, however, FILE names used for socket communication in the code have not changed between the two versions. The older version runs fine on all of the robots.

    I've also asked for a Full Backup (without image backup) of the problematic robot, and when I ran the code in Roboguide replicated cell, I did not encounter the same FILE-008 Warning, but I also did not establish a socket connection as I do not have that setup in my Roboguide (not sure if that's even possible, as I've tried it once and did not get anywhere), in case that would give anybody a clue.

    I'm not sure if it would make sense that the robot SW version difference would be causing this issue. But how can I debug this? Seems like because of this warning, socket communication fails and cannot be established, even though the karel programs that have been started are running (checked under STATUS -> Program).

    Any advice on how to move forward with this would be greatly appreciated!

    As always on Karel programs you are digging blindfolded for a needle in a haystack.

    You must insert some debug messages or setting variables, you can observe on TP into the Karel program to debug it.

    Edit: you can compare source of old and new code to see the difference, as you said the older one runs on all robots.

    Quote from hermann

    As always on Karel programs you are digging blindfolded for a needle in a haystack.

    You must insert some debug messages or setting variables, you can observe on TP into the Karel program to debug it.

    Edit: you can compare source of old and new code to see the difference, as you said the older one runs on all robots.

    Inserting messages is the way to go to debug when you can't see the code being executed... also, keep in mind that even while karel is compiled + encrypted and you can't see what is being executed, the line number from the .pc file matches the one of the .kl file.

    So if the robot reports an error on line 8 of the karel routine and you have the karel source code, check the line 8 on the source code as it will be the same.

Advertising from our partners