• 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. skill code for design Sheet Size need help

Stats

  • Replies 8
  • Subscribers 159
  • Views 17431
  • Members are here 0
More Content

skill code for design Sheet Size need help

Junior0304
Junior0304 over 10 years ago

Hi guys,

I am writing a skill code that will check Design parameters that include User Units, Accuracy and Size.

I was able to get the units and the accuracy using axlGetParam("paramDesign"), but no luck on the sheet size.

Can somebody please help help.

my  code is something like this

d = axlGetParam("paramDesign");
if(nequal(d->units "millimeters") then
       axlUIConfirm("Design unit defined is non-standard, change to millimeter and try again.")

else

)

if(equal(d->accuracy 4) then
...
else
...
);if

  • Cancel
  • Sign in to reply
Parents
  • eDave
    eDave over 10 years ago

    There can be no possible impact to not having standard design extents. That said. I understand why you would be reluctant to fight a long-standing company norm and large extents shouldn't cause any problems other than zoom-world will cause you to lose your part on the screen.

    This code might help you with dimension checking:

    defun( DE_DimensionParametersCheck ()
    let((exts, maxExt, txtBlk, arrowWidth, arrowLength, paramFileName, p, ln, data, dimTxtBlk, dimArrowWidth, dimArrowLength, msg, flag)
    exts = axlExtentDB()
    when(exts, maxExt = max(x2(exts) - x1(exts), y2(exts) - y1(exts)))
    txtBlk = cond((!exts || maxExt > axlMKSConvert(5.0, "mm"), "2"), (maxExt < axlMKSConvert(2.0, "mm"), "3"), (t, "1"))
    arrowWidth = case(txtBlk, ("1", 0.25), ("2", 0.625), ("3", 0.125))
    arrowLength = arrowWidth * 2
    paramFileName = strcat(getTempDir(), "\\", axlCurrentDesign(), "commandParams.prm")
    if(axlExportXmlDBRecords(paramFileName, '("Application or Command Parameters")) then
    p = axlDMOpenFile("ALLEGRO_PARAMETER_FILE", paramFileName, "r")
    while(p && gets(ln, p) && !(dimTxtBlk && dimArrowWidth)
    when(ln
    data = parseString(DE_Ltrim(ln), "<>")
    case(car(data)
    ("dt_textblock", dimTxtBlk = cadr(data)); <dt_textblock>2</dt_textblock>
    ("dl_arrowlen_l", dimArrowLength = axlMKS2UU(cadr(data))); <dl_arrowlen_l>1.250 MM</dl_arrowlen_l>
    ("dl_arrowwid_l", dimArrowWidth = axlMKS2UU(cadr(data))); <dl_arrowwid_l>0.625 MM</dl_arrowwid_l>
    )
    )
    )
    axlDMClose(p)
    deleteFile(paramFileName)
    unless(dimTxtBlk, flag = "?")
    and(
    dimTxtBlk
    msg = list("ERROR", sprintf(nil, "Dimension Text Block is %s - should be %s", dimTxtBlk || "empty", txtBlk))
    dimTxtBlk == txtBlk
    msg = list("ERROR", sprintf(nil, "Dimension Arrow Head width (%g) - should be %g.", dimArrowWidth, arrowWidth))
    axlGeoEqual(arrowWidth, dimArrowWidth)
    msg = list("ERROR", sprintf(nil, "Dimension Arrow Head length (%g) - should be %g.", dimArrowLength, arrowLength))
    axlGeoEqual(arrowLength, dimArrowLength)
    msg = list("OK", "Dimension settings appear to be OK")
    flag = t
    )
    else
    msg = list("ERROR", "Could not export design parameters to a file in your temp folder")
    )
    msg
    ))

    defun( DE_Ltrim (txt @optional (ch " "), "St"), while(txt && substring(txt, 1, strlen(ch)) == ch, txt = substring(txt, strlen(ch) + 1)), txt || "")

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • eDave
    eDave over 10 years ago

    There can be no possible impact to not having standard design extents. That said. I understand why you would be reluctant to fight a long-standing company norm and large extents shouldn't cause any problems other than zoom-world will cause you to lose your part on the screen.

    This code might help you with dimension checking:

    defun( DE_DimensionParametersCheck ()
    let((exts, maxExt, txtBlk, arrowWidth, arrowLength, paramFileName, p, ln, data, dimTxtBlk, dimArrowWidth, dimArrowLength, msg, flag)
    exts = axlExtentDB()
    when(exts, maxExt = max(x2(exts) - x1(exts), y2(exts) - y1(exts)))
    txtBlk = cond((!exts || maxExt > axlMKSConvert(5.0, "mm"), "2"), (maxExt < axlMKSConvert(2.0, "mm"), "3"), (t, "1"))
    arrowWidth = case(txtBlk, ("1", 0.25), ("2", 0.625), ("3", 0.125))
    arrowLength = arrowWidth * 2
    paramFileName = strcat(getTempDir(), "\\", axlCurrentDesign(), "commandParams.prm")
    if(axlExportXmlDBRecords(paramFileName, '("Application or Command Parameters")) then
    p = axlDMOpenFile("ALLEGRO_PARAMETER_FILE", paramFileName, "r")
    while(p && gets(ln, p) && !(dimTxtBlk && dimArrowWidth)
    when(ln
    data = parseString(DE_Ltrim(ln), "<>")
    case(car(data)
    ("dt_textblock", dimTxtBlk = cadr(data)); <dt_textblock>2</dt_textblock>
    ("dl_arrowlen_l", dimArrowLength = axlMKS2UU(cadr(data))); <dl_arrowlen_l>1.250 MM</dl_arrowlen_l>
    ("dl_arrowwid_l", dimArrowWidth = axlMKS2UU(cadr(data))); <dl_arrowwid_l>0.625 MM</dl_arrowwid_l>
    )
    )
    )
    axlDMClose(p)
    deleteFile(paramFileName)
    unless(dimTxtBlk, flag = "?")
    and(
    dimTxtBlk
    msg = list("ERROR", sprintf(nil, "Dimension Text Block is %s - should be %s", dimTxtBlk || "empty", txtBlk))
    dimTxtBlk == txtBlk
    msg = list("ERROR", sprintf(nil, "Dimension Arrow Head width (%g) - should be %g.", dimArrowWidth, arrowWidth))
    axlGeoEqual(arrowWidth, dimArrowWidth)
    msg = list("ERROR", sprintf(nil, "Dimension Arrow Head length (%g) - should be %g.", dimArrowLength, arrowLength))
    axlGeoEqual(arrowLength, dimArrowLength)
    msg = list("OK", "Dimension settings appear to be OK")
    flag = t
    )
    else
    msg = list("ERROR", "Could not export design parameters to a file in your temp folder")
    )
    msg
    ))

    defun( DE_Ltrim (txt @optional (ch " "), "St"), while(txt && substring(txt, 1, strlen(ch)) == ch, txt = substring(txt, strlen(ch) + 1)), txt || "")

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

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

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