• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X PCB Editor
  3. why does export> NCroute> fail to export a rte file with...

Stats

  • State Suggested Answer
  • Replies 5
  • Answers 3
  • Subscribers 166
  • Views 1005
  • Members are here 0
More Content

why does export> NCroute> fail to export a rte file with the tool size defined?

RFinley
RFinley 1 month ago

I can't convince finance/operations to stop using ODMs that prefer fabricators who can't import ODB or IPC-2581

Thanks.

I  get "WARNING(SPMHMF-326): Cannot find NC Route bit tool file 'ncroutebits.txt'

 WARNING(SPMHMF-327): ... will auto-generate bit tool file 'ncroutebits_auto.txt'.
 Auto-generating tool file 'ncroutebits_auto.txt'
...every time.

log:

Processing NC Parameters file 'nc_param.txt' ...

 NC PARAMETERS
 -------------
 FORMAT   		2.5
 MACHINE-OFFSET		x:0.00000	y:0.00000   (mm)
 FEEDRATE		1
 COORDINATES		ABSOLUTE
 OUTPUT-UNITS		METRIC
 TOOL-ORDER		INCREASING
 REPEAT-CODES		YES
 SUPPRESS-LEAD-ZEROES	NO
 SUPPRESS-TRAIL-ZEROES	NO
 SUPPRESS-EQUAL		NO
 TOOL-SELECT		NO
 HEADER			none
 LEADER			12
 CODE			ASCII
 SEPARATE		NO
 SEPARATE-ROUTING	NO
 OPTIMIZE_DRILLING	NO
 ENHANCED_EXCELLON	NO
 SCALE			1.000000

 WARNING(SPMHMF-326): Cannot find NC Route bit tool file 'ncroutebits.txt'
 WARNING(SPMHMF-327): ... will auto-generate bit tool file 'ncroutebits_auto.txt'.
 Auto-generating tool file 'ncroutebits_auto.txt' ...
     0.6000  T01       
-------------------------------------------------------------
Pre_processing route path data ...
 WARNING(SPMHMF-296): No route path data was found for processing.

 Processing slot hole data ... TOP to BOTTOM 
 OVAL      slots routed: 14
 RECTANGLE slots routed: 0
 NC Route file 'Y.rou' created ...
 Program completed.
  • Cancel
  • Sign in to reply
  • RFinley
    0 RFinley 1 month ago

    By the year 2026, I would hope Excellon file generation wouldn't be producing random results.

    When it does work, this is the route file header I need.   CAM350 needs it to set the correct route toolsize and show artwork correctly:

    M48
    METRIC
    T01C.6

    I'll admit that going into  SETUP> User Preferences Editor> >Paths >Config >ncpath  and adding my pcbenv path solved a few problems. 

    But..


    WARNING(SPMHMF-326): Cannot find NC Route bit tool file 'ncroutebits.txt'
    WARNING(SPMHMF-327): ... will auto-generate bit tool file 'ncroutebits_auto.txt'.

    Auto-generating tool file 'ncroutebits_auto.txt' ...

    0.6000 T01

    After about 15 iterations, it always says it can't find then made a new routebits file.  But, it's stopped including those lines in the .rou.

    CAM350 guesses and sets it to 2.31mm, which is bad.  No idea where that's coming from.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • excellon1
    0 excellon1 1 month ago in reply to RFinley

    It works fine, but there is a bug in cam350.

    Your parameter file for the drills and routes need : the following checked.

    Automatically create drill ncroutebits_auto
    Leading Zero Suppression
    Enhanced Excellon Format  "Should be using this for everything" <<<<<<<<<<<

    The default file produced for the routing is a .rou file for nc-routes

    When creating the actual drill file check these.

    Auto Tool Select
    Separate files for plated non plated holes
    Optimize drill head travel

    Best regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • excellon1
    0 excellon1 1 month ago in reply to RFinley

    I responded to your question. Flagged as Spam LOL. Wow most sad. Trying again.

    Check The following in your NC Parameters Setup.

    Automatically create drill_ncroutebit_auto
    Auto create drill ncroutes
    Leading Zero Suppression
    Enhanced Excellon Format

    Wnen creating your drill file use.

    Auto Tool select
    Seperate Files for plated Non plated holes
    Optimize drill head travel

    When creating the Routes file Check.
    Seperate Files for plated non plated routing

    Best regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • RFinley
    0 RFinley 1 month ago in reply to excellon1

    ugh.  Needs work on documentation. 

    Arguably, the issue starts with:   why the toolsize isn't exported by default?

    Not useful without the toolsize.

    Thanks!  Need to work on this so my coworkers are successful.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • excellon1
    0 excellon1 1 month ago in reply to RFinley

    No, Your issue here on the NC routes is you are not using "Enhanced Excellon Format" in your parameters file !

    The NC Route file creates std g-code which is a profile of the routing to be performed, the width of your slot is typically the tool size, however at the board house for routing they may use one of their STD router bits instead. As long as the physical routing bit is smaller than your slot it can route out the board. The important thing here is the profile information.

    If you use Enhanced Excellon Format" The tool will be listed in the file. Here is an example at the start of the routing file using enhanced EX format.

    M48
    INCH,TZ
    T01C.056
    ;EXTENTS: -6.800  -7.000  21.200  10.000  
    ;LEADER: 12
    ;HEADER:
    ;CODE  : ASCII

    Here is an example of not using the enhanced excellon format. No tool shows up.

    ;EXTENTS: -6.800  -7.000  21.200  10.000  
    ;LEADER: 12
    ;HEADER:
    ;CODE  : ASCII

    Best Regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information