• 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 APD
  3. In OrCAD Capture 17.4 net changes name when a Test Point...

Stats

  • State Not Answered
  • Replies 8
  • Subscribers 68
  • Views 16222
  • Members are here 0
More Content

In OrCAD Capture 17.4 net changes name when a Test Point is added

Agilulfo
Agilulfo over 3 years ago
  1. Hello

I am facing a simple but odd question in using OrCAD Capture 17.4.

I have inserted into the schematics some test points in order to identify them when I will have the PCB.

It happens that the nets where the TP are inserted change their name with respect to the alias I imposed.

As an example, net labeled with alias CMD_L2 becomes CMD_L2_17233165. The alias anyway does NOT change!

I tried to change net name in properties or to delete the alias and place it again into the same position, without success.

I have found no property in the test point part which I can relate to such a behaviour.

Usually, posts that I found on TPs are about PCB layout, not about the schematics.

Could anyone be so kind to give me a piece of advice about how to solve this issue?

  • Sign in to reply
  • Cancel
  • oldmouldy
    0 oldmouldy over 3 years ago

    The issue may be related to what you are using as a testpoint. Capture is considering the addition of the testpoint as a connectivity change that makes this CMD_L2 Net different from other CMD_L2 Net(s) in the design and appends an ID to the flattened netlist to enforce this. You would need to attach an archive of the DSN file, or a DSN file that contains a representative example of the issue, to get this investigated in more detail. Also, which exact version of OrCAD Capture 17.4 are you using? (Check from Help>About in Capture)

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Agilulfo
    0 Agilulfo over 3 years ago in reply to oldmouldy

    Dear Oldmouldy

    Thank you for your answer. The exact Orcad version is 17.4-2019 P001, if this answers to your question.

    Unfortunatly my Cadence licence Onlus for Schematics tool, so I can not see DSN file...

    Would you have an idea about how to solve this issue? Can any setting of TPs as a part that could be  changed in order to stop this behaviour?

    Thank you in advance 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • oldmouldy
    0 oldmouldy over 3 years ago in reply to Agilulfo

    The DSN file contains the binary data that Capture uses to store the schematic data, you must have one if you have a Capture schematic. The version of Capture that you have is a Base Release from October 2019, which may explain a lot, the current 17.4 version is 17.4-2019.s027 from February 2022.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Agilulfo
    0 Agilulfo over 3 years ago in reply to oldmouldy

    Dear Oldmouldy

    Thank you again; I see that I should have had to be morr precise. I have a .DSN file, but I can not open it as it is opened with OrCAD PCB. When I tre to see the DSN, an error is given me about lack of license. I can not give you an extract of the file.

    As the design is proprietary, I can not upload it entirely as it is.

    How could a part change the name of an aliased net? I thought that aliases were as written in stone on a design!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Agilulfo
    0 Agilulfo over 3 years ago in reply to Agilulfo

    I have also found an interesting point: if I do a search only for net called CMD_L2 it finds both CMD_L2 and CMD_L2_17233165.

    It is not a matter of matching the first part of the name: indeed searching only CMD_L nothing is found.

    Is the the possibility that the program placed in short the nets because of the alias? Or the nets will be different (so not connected) but the search gives both results just because the alias is the same?

    If I only had PCB license I could have an answer about this point without bothering anyone if not necessary!

    Anyway in the netlist nets  have different names,  so I would say that they will not be connected on the PCB; the netlist commands routing if I am right...

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify 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.

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

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