Contour with .00005 taper

[Leon82]

I have a square with radii in the 4 corners. Tool path tolerance it .00001.

On all 4 sides the posted code is moving.00005 along each length. The geometry is straight I even drew new geometry if I annalize with six place decimals it's a straight line..

 

The post is set for 6 place decimal. Will adjusting the system tolerance help this?

[Colin Gilchrist]

40 minutes ago, Leon82 said:

I have a square with radii in the 4 corners. Tool path tolerance it .00001.

On all 4 sides the posted code is moving.00005 along each length. The geometry is straight I even drew new geometry if I annalize with six place decimals it's a straight line..

 

The post is set for 6 place decimal. Will adjusting the system tolerance help this?

This is probably just an issue with rounding of the numbers in Windows.

Do a Google Search for 'round_opt$' on this site.

 

 

[Colin Gilchrist]

 

 

 

So, try the following (one at a time), to test the 'round_opt$' variable:

round_opt$ : 0

round_opt$ : 1

round_opt$ : 11

round_opt$ : 21

[Guest]

1 hour ago, Leon82 said:

I have a square with radii in the 4 corners. Tool path tolerance it .00001.

On all 4 sides the posted code is moving.00005 along each length. The geometry is straight I even drew new geometry if I annalize with six place decimals it's a straight line..

 

The post is set for 6 place decimal. Will adjusting the system tolerance help this?

Can you share a file?

[Guest]

Which version of Mastercam? You can use native vbscript tools to output the precise value in a message box of the selected lines endpoints.

It might not be in the right view, then you would combine views or something.

There is intellisense in code expert for the language

[Guest]

Dim success
success = StartDBSearch(MC_SELECTED,MC_LINETYPE)

If success Then
    Do 
	       Dim Line
		   
           Set Line = New mcLn

           If GetLineData(GetEntityEptr, Line) = True Then 
			
			  ShowString("Line end point1->" + "x" + Cstr(Line.X1)  + "y" + Cstr(Line.Y1) + "z"  + Cstr(Line.Z1) + " Line end point2->"+ "x" + Cstr(Line.X2)  + "y" + Cstr(Line.Y2) + "z"  + Cstr(Line.Z2))  
			 
           End If
    Loop While NextDBSearch   
End If  

 

[Leon82]

1 hour ago, Thee Byte™ said:

Which version of Mastercam? You can use native vbscript tools to output the precise value in a message box of the selected lines endpoints.

It might not be in the right view, then you would combine views or something.

There is intellisense in code expert for the language

2020.

1 hour ago, Colin Gilchrist said:

 

 

 

So, try the following (one at a time), to test the 'round_opt$' variable:

round_opt$ : 0

round_opt$ : 1

round_opt$ : 11

round_opt$ : 21

Thanks, I will give it a shot tomorrow

1 hour ago, Thee Byte™ said:

Can you share a file?

I will try. I need to strip it of customer data

[Leon82]

12 hours ago, Colin Gilchrist said:

 

 

 

So, try the following (one at a time), to test the 'round_opt$' variable:

round_opt$ : 0

round_opt$ : 1

round_opt$ : 11

round_opt$ : 21

That variable is not in the post

[Colin Gilchrist]

2 hours ago, Leon82 said:

That variable is not in the post

No, it isn't. 

This is something that you have to add to your Post, if you want to test it out. It is kind of a 'secret option'.

That MP variable instructs MP.DLL to utilize a different Windows Function for rounding a double value. (All numbers are stored as the Double Type in MP.)

Add the variable initialization, starting with the 'r' in the very 1st column of your editor.

Only add one line, and then change the 'initialization value', each time you run the test. (Be sure to sve the Post between the tests!)

round_opt$ : 11

There are 4 different values to try: 0, 1, 11, 21.

[Leon82]

11 worked.

 

Thanks again

[Colin Gilchrist]

44 minutes ago, Leon82 said:

11 worked.

 

Thanks again

Happy to help man. 

What good is all my knowledge; if I can't put it to use and pass it on?

[Leon82]

So it started doing it again after I changed the tool so I looked in the control def and changed the minimum nc step and math function tolerance to .00001 and it seems to have fixed it.