You are not logged in.
Pages: 1
Note:
I am using v5.4.5. Our production license server is not ready for V6.0. So please take this into consideration for any thoughts you might have.
The Vericut on-line training session #55 shows me how to configure a control to check for conflicts between the T and H values. This is good for me most of the time. I made it work as outlined in the lesson in my pre-5.4.5 Fanuc15m control in V5.4.5. I even modified it so that the error became a warning (MessageMacro, 2), allowing me to review before proceeding (sometimes I need an H code not equal to T code, esp. with slotted cutters).
Then, of course, I decided to upgrade my control file to Fanuc15m V5.4.5 when the g-code checker told me that I had (gasp) obsolete macros. I changed controls and added my customizations (e.g. T vs H, etc). At that point, Vericut was unable to handle this tweak anymore. I found that the new control file placed the word value G43 before the word value H. This is the opposite of the old control file. When I moved G43 after H, then the tweak started working again.
My question is, does anyone know if I am causing a bigger problem for myself than the problem I am solving?
Thank You,
Robert Davie
Offline
Hi Robert,
The State group represents all the G-Codes that are modal in the program. There was no real functional reason for us to move this word there other than a logical classification.
I do not see any problems moving this word to the G_Prep as before.
Offline
Pages: 1