Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PyEDB exported port configuration bug #1040

Open
2 tasks done
raindigoa opened this issue Feb 26, 2025 · 2 comments
Open
2 tasks done

PyEDB exported port configuration bug #1040

raindigoa opened this issue Feb 26, 2025 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@raindigoa
Copy link

Before submitting the issue

  • I have searched among the existing issues
  • I am using a Python virtual environment

Description of the bug

Hi

I'm looking for a method to reuse the ports that have been defined in an existed h3d design.

And I found an interesting example in PyEDB page:
https://edb.docs.pyansys.com/version/stable/examples/use_configuration/import_ports.html

Instead of editing the port config file manually, I inclined to export the port config from an existed design with well-defined ports and reimport the config to a new design (assume it's an updated layout comparing to the former one)

Please refer to the steps to get the detail of this issue.

In a short, the export information of cirucit ports doesn't collect the correct port information for both pos and neg terminal. It's an obvious bug for this function. Please help fixing it.

One more thing, there would be another set of "circuit" port information if there were "edge ports" existing in the design. I will describe this in another request post.

Thank you.

Steps To Reproduce

  1. loading a edb.def file by Edb module.
  2. export the port config by
    edbapp.configuration.export(
    file_path="export_config",
    stackup=False,
    package_definitions=False,
    setups=False,
    sources=False,
    ports=True,
    nets=False,
    pin_groups=False,
    operations=False,
    components=False,
    boundaries=False,
    s_parameters=False,
    padstacks=False,
    general=False)
  3. check the export JSON file.

And when I check the JSON file, I saw some bugs for the cirucit ports.
Please check the comment that I write after "=>" symbol.

{
"name": "CACpad_C",
"type": "circuit",
"reference_designator": "",
"positive_terminal": {
"coordinates": {
"layer": "UNNAMED_000", => this layer desc is correct
"point": [
0.005531,
0.127472
],
"net": "Port1" => this net desc is incorrect, there is no net called Port1
}
},
"negative_terminal": {
"coordinates": {
"layer": "UNNAMED_000", => this layer desc is incorrect, it supposes to be L2
"point": [
0.005931,
0.127072
],
"net": "InternalPort4" => this net desc is incorrect, there is no net called InternalPort4
}
}
},

  1. reimport the configuration will raise error.

Which Operating System are you using?

Windows

Which Python version are you using?

3.9

Installed packages

pyedb==0.30.0
pyaedt==0.14.1

@raindigoa raindigoa added the bug Something isn't working label Feb 26, 2025
@Samuelopez-ansys
Copy link
Member

Hi @raindigoa , This is not a PyAEDT issue, I will transfer it to PyEDB repository

@Samuelopez-ansys Samuelopez-ansys transferred this issue from ansys/pyaedt Feb 26, 2025
@hui-zhou-a hui-zhou-a self-assigned this Feb 27, 2025
@hui-zhou-a
Copy link
Collaborator

@raindigoa thanks for submitting the bug. However, I am not able to reproduce this bug on my side. Could you share your design with me?

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants