What's new
What's new

Need to add trailing zero to Code on VF-5

Mohawk72

Aluminum
Joined
Jan 17, 2008
Location
Syracuse, NY
I now have a new HAAS VF-5 Mill and the control drops all trailing zeros from my programs.

Most of the programs are 10 pages or so long so I need to have FeatureCAM drop the trailing zeros from my posted code or the Machine control to add the zeros to the Code.

Otherwise comparing programs will make ya blind as every line is different.

HAAS tells me there is no parameter in the control that will fix this, They say it's for saving space.
They should then have deleted the leading zeros too, But they didn't.

Let me know if any of you have see a switch or parameter that will correct this for me.

Or how to make FeatureCAM drop the trailing zero from my code.
Now you need to try this in the edited post before you tell me what to do.
As I have tried every switch in the post editor.
I am running version 14.2.0.63 now.

Thanks

Mohawk72
 
What do you mean by "comparing programs"? You are comparing printed output from FeatureCam to the Haas control? Why?

Haas didn't delete leading zeros because typing a leading zero before a decimal point is good practice. It's easy to miss a tiny decimal point on that screen. DAMHIK. :(
 
Mohawk

The Haas uses a 32 bit word for each coordinate value, so adding or removing leading/trailing zeros would not in any way affect program size. A 32 bit value is a 32 bit value.
They do however use a fixed format of no trailing zeros and a leading 0.
Similarly for commands, a G1 gets translated to G01, G0 to G00, M0 to M00 etc.
Nice thing is though that it is fixed and consistant, unlike Fanyuck, which almost looks like stores each digit separately. Makes for the ugliest looking code received back from the control. No spaces, some 0-s, some no 0-s.... Yuck!

As for FC, you should be able to edit your post's definition to have no trailing zeros.
Mine doesn't have them by default, so not sure why does your's.
 
Morning,

I have 73 different CNC machines runnign 3 shifts, And I have the operators punch the program back to the DNC when they make any changes to the code.

I then compare the programs to see the differences to make a determination weather the change is fit and finish or just a tool is not taught right.

I have tried every setting in FeatureCAM to do away with the trailing zeros on X and Y. For some reason there is no trailing zero's on Z. Go figure.

And that is interesting about not saving space. Two HAAS techs both told me that was the reason that the control doesn't display trailing zero's.

Thanks for the replies guys,

I am still looking for a way to accomplish this.

Mohawk
 
Go into xbuild and click "words" then goto page 6, there you will see x-coord and down a few more you will see y-coord. notice there is spots labled LD_ZR and TR_ZR. Now since your z is not using trailing "0's" look down a few more spots and see wich of the boxes are checked the simply do the same for x-coord and y-coord. if your using an a axis you can do the same there as with rapids on page 7. when you finnish editing the post remember to save as a different rev. such as "Haas VF-5 rev-2" and i always put a new message in the post box telling the changes just as a reminder.

If you have anymore questions just ask, i dont know it all about FC but ive been using it since the early 90's and if you cant get a post right i have about 20 differant ones for Haas.
 
Another thing you should do in your post is while in Featurecam open the post dialog, there you will see a box that has "min-max arc". by default max arc is set to 1000". you may not ever need more than 1000" but to be safe set this to 10'000". if this is set to small it breaks your radius up into linear segments that are much smaller than the programed radius. I found this out the hardway when i scrapped a piece of t-100 armour plate that was about $20,000 bucks.
 
Thanks for the tip, I will take care of that too.

I have poked all through the FeatureCAM setup and It is close but the Haas still strips out more than the Cam can do. Plus the Haas removes the blank line I like between processes for ease of reading on screen.

SO the work around I am using now is when I call the program into the control using my DNC. I then immediately punch the code back to my hold directory as the Haas has already stripped the trailing zero's and removed my blank lines.

I then use this punched back code as my MASTER for compare purposes.

This works great and simplifies my job.

C Ya

Mohawk
 
Mohawk

I still don't get it.
Here is a snippet from my output from FC:

( OP:ROUGH1 SIDE - OUTSIDE )
( TOOL02 = 0.5 DIA 1/2CA-3FL-ROUGH )
T02 M6
G00 G43 H02 D02
G00 X-3.7727 Y-4.2391 Z1.05
S3000 M03
M08
G01 Z0.1 F200.
G01 X-3.7727 Y-4.2391 Z-0.4233 F120.0
M97 P9901
G01 X-3.7727 Y-4.2391
G01 X-3.7727 Y-4.2391 Z-0.8467 F120.0
M97 P9901
G01 X-3.7727 Y-4.2391
G01 X-3.7727 Y-4.2391 Z-1.27 F120.0

Notice the 4 precision Z values when needed, and the lack of trailing zeros when not.

As for the dropped blank lines, blanks are not read and stripped by Haas, but empty lines with nothing but an EOB (;) character are fine and will not be touched.
You can add those to help in aiding the visual separation.
The above example with the blanks:

( OP:ROUGH1 SIDE - OUTSIDE )
( TOOL02 = 0.5 DIA 1/2CA-3FL-ROUGH )
;
T02 M6
G00 G43 H02 D02
;
G00 X-3.7727 Y-4.2391 Z1.05
S3000 M03
M08
G01 Z0.1 F200.
G01 X-3.7727 Y-4.2391 Z-0.4233 F120.0
;
M97 P9901
;
G01 X-3.7727 Y-4.2391
G01 X-3.7727 Y-4.2391 Z-0.8467 F120.0
;
M97 P9901
;
G01 X-3.7727 Y-4.2391
G01 X-3.7727 Y-4.2391 Z-1.27 F120.0
 








 
Back
Top