Can't believe you've had this very common problem this long.
I'm disappointed but not surprised that someone from SolidCAM support didn't immediately jump in and help you with this.
A missing or wrong setting in your *.mac file is causing this problem.
Fire up your mac file in a text editor and find the Epsilon settings area.
The below command needs to be there, or if already there it needs to be changed from the default value of 3 decimal place output to 4 decimal place output.
You have already experienced the fact that it makes no difference that your values in the gpp file are set as they should be 5.4. This movement_precision value in the *.mac file needs to be set to allow the 5.4 values in your gpp file to work.
The below value in the *.mac file is either not there which results in it defaulting to 3 decimal place output or the value is there and it's set on 3.
if movement_precision is there it's probably set like one of the following:
movement precision = 3 ; this forces 3 decimal place output in inch or metric
or movement precision = 0.000, 0.000 ; 1st value is metric, 2nd value is inch.
It needs to be either of the following
movement_precision = 4 ;forces 4 decimal place output in inch or metric
or movement_precision = 0.001 , 0.0001 ; equivalent to = 4 above
I can assure you that this will force it to post out with 4 decimal place output.
Another little gotcha may be there.
When your X, Y, and Z values change to 4 decimal place output that does not mean that your R (if you use R's), I, J, and K will also. They are controlled elsewhere.
In the largest portion of the the SolidCAM posts there is not an explicit definition of R, I, J, K in your *.gpp as there is X, Y, and Z.
The following in you gpp file will take care of the decimal output of your R, I, J, and K values.
in your GPP variables
numeric_def_f = '5.3' needs to be changed to '5.4'
the numeric_def setting is kind of a catch all that takes care of address values that are not explicitly defined.
Good Luck  |