You are not logged in.
I normally use UG to generate code. But I also need to write G-Code manually. I almost always manage to make typos with zeroes and O's, i.e. "GO" instead of "G0". This causes me considerable angst, especially when my typo is in a sub-routine, since Vericut stops scanning the sub-routine as soon as it finds my error. Both times this has happened I went into a tailspin for a day or so until the error was seen.
My suggestion is either:
a) Provide an option to put a dot in the middle of a Zero
or
b) Allow the user to specify a different font in the listing window. For example, the "Arial monospaced for SAP" available on our network does put a dot in the middle of a Zero.
You know, in the old days, before Microsoft, computer terminals always put a dot in the middle of a Zero. How about it?
Offline
Hello Robert,
What you really need is a quick way to find this 0/O mistake (option C?).
In the control file, you add a message macro that will output a warning each time you use a O in the code. So you can see it in the logger at the bottom of the screen of in the log file.
Offline
Option C, it is!
Thank You Very Much!
Offline