While working with the DX200 for the first time, I have discovered an unpleasant "innovation": unlike the predecessors, the display does not indicate the line number, where an error is detected at loading a job from a memory card.
The error code is shown, but not the job line number.
The error message appears truncated on the right, and it is not clear whether there is no such information at all, or it is off-screen.
But since it is impossible to display the entire message, we have to assume that it is missing.
Loading a job into DX200- Unpleasant surprise
-
Sergei Troizky -
February 21, 2016 at 8:49 PM -
Thread is Resolved
-
-
I remember that sometimes the line numbers were not shown even on DX100, only the error code. It may depends on the error code.
-
I remember that sometimes the line numbers were not shown even on DX100, only the error code. It may depends on the error code.He's right. I've had a DX100 that gave me a line number which didn't even exist in a job because I typed "IF" rather then "IFTHEN" or forgot an "ENDIF." Also, no specification of line number for not declaring local variables which were used in the instructions... it might not be a DX200 thing.
-
Yes, but in DX100 this happened sometimes.
The DX200 never indicates the line number. -
If your error is in the header of the job (number of steps not matching, external axis not matching...) you will not get a line number. Not to sure on DX200 and syntax errors is the body of the job.
If you buy Job editor software it can check your job for errors and show you where they are.
-
Greetings,
By job editor are you alluding to Yaskawa's motosim software?
Or are there other editors out there (please mention some)?My group is writing an autocad to inform translator and would greatly benefit from debugging with a job editor, as compared to various iterations of testing via USB stick.
Thanks.
Sent from my iPad using Tapatalk
-
You can use MotoSim, however, Yaskawa does have job editor software for each controller. It's just like the CIO editors, but for jobs. This way the syntax and structure can be checked before you try to load it in a controller. I'm old school and still use Notepad to do my edits, but run it through an editor to check for errors (oh's and zero's get me every time).