onSection() error only when tyring to post adaptive tool path

onSection() error only when tyring to post adaptive tool path

5X-machines
Enthusiast Enthusiast
723 Views
1 Reply
Message 1 of 2

onSection() error only when tyring to post adaptive tool path

5X-machines
Enthusiast
Enthusiast

Hey everyone,

 

I experienced something new today and not in a good way. When trying to post a new program today using Fusion standard DMG Mori NLX post processor, I get this error:

 

###############################################################################
Error: Toolpath exceeds the maximum ranges for operation "Adaptive".
Error at line: 1770
Error in operation: 'Adaptive'
Failed while processing onSection() for record 409.
###############################################################################

 

I did some forum searching and discovered it basically means there is an issue with the tool orientation. However if I post a 2D contour operation with the exact same tool orientation settings, it posts just fine. I did some more trial and error and discovered the following:

 

  • If I uncheck tool orientation for operation, it posts (but tool path isn't what I want obviously)
  • If I use a different post say generic fanuc, it posts without error
  • This only seems to affect 3D adaptive operations. 2D contour, ramp, drill all post fine with same tool orientation
  • Any adaptive operation that is not inline with the default WCS Z-axis posts with this error.

I'm at my wit's end trying to figure out how to fix this. Anyone have a suggestion? Thanks

 

here's the full error text if you would like to see it:

 

Information: Configuration: DMG Mori NLX Mill/Turn
Information: Vendor: DMG MORI
Information: Posting intermediate data to 'C:\Users\User\AppData\Local\Fusion 360 CAM\nc\1001.nc'
Information: Total number of warnings: 3
Error: Failed to post process. See below for details.
...
Code page changed to '1252 (ANSI - Latin I)'
Start time: Friday, September 13, 2019 4:53:13 PM
Warning: function getProgramNameAsInt does not always return a value
Warning: function getProgramNameAsInt does not always return a value
Warning: function getProgramNameAsString does not always return a value
Code page changed to '20127 (US-ASCII)'
Post processor engine: 4.3.0 45236
Configuration path: C:\Users\User\AppData\Roaming\Autodesk\Fusion 360 CAM\Posts\dmg mori nlx mill-turn.cps
Include paths: C:\Users\User\AppData\Roaming\Autodesk\Fusion 360 CAM\Posts
Configuration modification date: Wednesday, October 31, 2018 8:33:24 PM
Output path: C:\Users\User\AppData\Local\Fusion 360 CAM\nc\1001.nc
Checksum of intermediate NC data: edcefd93d013c730fd1a3a408936bf29
Checksum of configuration: b99046ee5eca6e879bf98bffbad36cb3
Vendor url: http://www.dmgmori.com
Legal: Copyright (C) 2012-2018 by Autodesk, Inc.
Generated by: Fusion 360 CAM 2.0.6263
...

###############################################################################
Error: Toolpath exceeds the maximum ranges for operation "Adaptive".
Error at line: 1770
Error in operation: 'Adaptive'
Failed while processing onSection() for record 407.
###############################################################################

Error: Failed to invoke function 'onSection'.
Error: Failed to invoke 'onSection' in the post configuration.
Error: Failed to execute configuration.
Stop time: Friday, September 13, 2019 4:53:13 PM
Post processing failed.

 

0 Likes
724 Views
1 Reply
Reply (1)
Message 2 of 2

bob.schultz
Alumni
Alumni

The error that you are getting simply states that the limits of the machine have been exceeded while performing a radial toolpath (tool axis is perpendicular to the Z-axis).  The default limits for this machine are defined as follows.

var yAxisMinimum = toPreciseUnit(gotYAxis ? -50.8 : 0, MM); // specifies the minimum range for the Y-axis
var yAxisMaximum = toPreciseUnit(gotYAxis ? 50.8 : 0, MM); // specifies the maximum range for the Y-axis
var xAxisMinimum = toPreciseUnit(0, MM); // specifies the maximum range for the X-axis (RADIUS MODE VALUE)

You can change these values in the post to match your machine and hopefully this will resolve your issue.



Bob Schultz
Sr. Post Processor Developer

0 Likes