Stats

  • Locked Locked
  • Replies 1
  • Subscribers 163
  • Views 13262
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NCDPATH bug

archive

Hello All. In SPB15.7, I have a problem with NCDPATH: the environnement variable NCDPATH is set (since a long time) to dot (.) and another common path on the network where we store our default nc_param.txt file. on the . path (the physical board path), there is no nc_param.txt at the beginning. So the common file is read and then copier to . If you change it locally then "." file is read and not anymore the common file. Since SPB15.7, the default path is not read anymore. It creates a new one in . with wrong params (true in fact but not what we want). I tried to remove the first . (dot) path and the the common network path is used. So it seems that only one path of the NCDPATH is taken, the first one. Did somebody see a similar thing? Thanks.


Originally posted in cdnusers.org by willbi
  • archive

    Solved.

    In fact we use a script to generate the drill legend before running nctape command.
    This script was OK in 15.5.1 and before. But now when it runs, it creates a nc_param.txt wit two lines:
    DRILLING LAYER-PAIR
    BACKDRILL NO
    It seems these lines are informations needed to fill the legend (and it's new in 15.7)

    So I solved the problem by running the ncdrill param command at the beginning of the script.
    This makes that the default nc_params.txt file is copier to "." and like it already contains these two lines, it works.


    Originally posted in cdnusers.org by willbi
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.