Stats

  • State Not Answered
  • Replies 3
  • Subscribers 159
  • Views 654
  • Members are here 0
More Content

Importing parameter file does not change units to mm?

MR20250507523

Hi,

I have set up design parameters, including changing the default units from mils to mm.

I export all these settings to a .prm file.

When I open a new design and import the .prm file, the default units do not change to mm, they stay as mils and all the other param settings are corrupted.

If I open a new design, then manually change the default units to mm, then import the .prm file, all my settings are imported correctly.

Why does importing the parameter file not change the units?

Parents
  • 0

    Hi  . What version and Hotfix are you experiencing this on?

  • 0 in reply to JuanCR

    I replicated the issue using

    22.1-2022 S008

    and

    23.1-2023 S003

    The basic issue appears to be the design size & units are not exported to the parameter file...

    In my test-case design it has the following values from axlGetParam("paramDesign") in the .jrl file

    in Microns:

    (00:00:56) units "microns" xy
    (00:00:56) (-11680.0 -8500.0) width
    (00:00:56) 123340.0 height 130960.0

    in Millimeters:

       (00:03:06)     units "millimeters" xy
       (00:03:06)     (-11.68 -8.5) width
       (00:03:06)     123.34 height 130.96

    however searching the output .prm files shows nothing with the those coordinates, for example:

    C:\Temp\symbols>dir *prm
     Volume in drive C has no label.
     Volume Serial Number is 46E1-12D0

     Directory of C:\Temp\symbols

    07/16/2025  10:02 AM           228,932 np.prm
    07/16/2025  10:00 AM           229,809 op.prm
                   2 File(s)        458,741 bytes
                   0 Dir(s)  63,897,620,480 bytes free

    C:\Temp\symbols>grep -i units *prm

    C:\Temp\symbols>grep 123 *prm
    np.prm:      <blue>123</blue>
    np.prm:      <number>123</number>
    np.prm:      <penNumber>123</penNumber>
    np.prm:      <name>COLOR_123</name>
    np.prm:    <mixedPriority>123</mixedPriority>
    op.prm:      <blue>123</blue>
    op.prm:      <number>123</number>
    op.prm:      <penNumber>123</penNumber>
    op.prm:      <name>COLOR_123</name>
    op.prm:    <mixedPriority>123</mixedPriority>

    C:\Temp\symbols>grep 130 *prm
    np.prm:      <red>130</red>
    np.prm:      <green>130</green>
    np.prm:      <number>130</number>
    np.prm:      <penNumber>130</penNumber>
    np.prm:      <name>COLOR_130</name>
    np.prm:    <mixedPriority>130</mixedPriority>
    op.prm:      <red>130</red>
    op.prm:      <green>130</green>
    op.prm:      <number>130</number>
    op.prm:      <penNumber>130</penNumber>
    op.prm:      <name>COLOR_130</name>
    op.prm:    <mixedPriority>130</mixedPriority>

    C:\Temp\symbols>

Reply
  • 0 in reply to JuanCR

    I replicated the issue using

    22.1-2022 S008

    and

    23.1-2023 S003

    The basic issue appears to be the design size & units are not exported to the parameter file...

    In my test-case design it has the following values from axlGetParam("paramDesign") in the .jrl file

    in Microns:

    (00:00:56) units "microns" xy
    (00:00:56) (-11680.0 -8500.0) width
    (00:00:56) 123340.0 height 130960.0

    in Millimeters:

       (00:03:06)     units "millimeters" xy
       (00:03:06)     (-11.68 -8.5) width
       (00:03:06)     123.34 height 130.96

    however searching the output .prm files shows nothing with the those coordinates, for example:

    C:\Temp\symbols>dir *prm
     Volume in drive C has no label.
     Volume Serial Number is 46E1-12D0

     Directory of C:\Temp\symbols

    07/16/2025  10:02 AM           228,932 np.prm
    07/16/2025  10:00 AM           229,809 op.prm
                   2 File(s)        458,741 bytes
                   0 Dir(s)  63,897,620,480 bytes free

    C:\Temp\symbols>grep -i units *prm

    C:\Temp\symbols>grep 123 *prm
    np.prm:      <blue>123</blue>
    np.prm:      <number>123</number>
    np.prm:      <penNumber>123</penNumber>
    np.prm:      <name>COLOR_123</name>
    np.prm:    <mixedPriority>123</mixedPriority>
    op.prm:      <blue>123</blue>
    op.prm:      <number>123</number>
    op.prm:      <penNumber>123</penNumber>
    op.prm:      <name>COLOR_123</name>
    op.prm:    <mixedPriority>123</mixedPriority>

    C:\Temp\symbols>grep 130 *prm
    np.prm:      <red>130</red>
    np.prm:      <green>130</green>
    np.prm:      <number>130</number>
    np.prm:      <penNumber>130</penNumber>
    np.prm:      <name>COLOR_130</name>
    np.prm:    <mixedPriority>130</mixedPriority>
    op.prm:      <red>130</red>
    op.prm:      <green>130</green>
    op.prm:      <number>130</number>
    op.prm:      <penNumber>130</penNumber>
    op.prm:      <name>COLOR_130</name>
    op.prm:    <mixedPriority>130</mixedPriority>

    C:\Temp\symbols>

Children
No Data
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.