Allegro X Scripting - Skill - Recent Threads

RE: How to check BGA minimum pitch using Allegro Skill language

Hoangkhoipcb — Fri, 17 Jul 2026 04:24:49 GMT

Hi SG20260713408,

Whenever you have some free time, I’d love to connect and discuss automation and skill development. I really appreciate your time.

BR

HoangKhoi

How to check BGA minimum pitch using Allegro Skill language

BZ202408076026 — Mon, 13 Jul 2026 06:33:23 GMT

I want to check BGA minimum pitch. If BGA pitch is less than 0.5mm, need to highlight these BGA in PCB layout. Does anyone have experience to write script to do the check?

RE: How to check BGA minimum pitch using Allegro Skill language

BZ202408076026 — Thu, 16 Jul 2026 02:10:12 GMT

Hi SG20260713408 ,

I have tried the script and it works well. Many thanks!

RE: How to check BGA minimum pitch using Allegro Skill language

BZ202408076026 — Tue, 14 Jul 2026 07:17:38 GMT

Hi Hoangkhoipcb

Thank you for your quick answer! Our BGA property is stored in symbols->DFA_DEV_CLASS.

RE: How to check BGA minimum pitch using Allegro Skill language

SG20260713408 — Tue, 14 Jul 2026 03:30:15 GMT

안녕하세요..

아래 코드가 도움이 되시길 바랍니다.

1. BGA 핀 PITCH가 정사각형 모양일 경우만 해당됩니다.

2. 정사각형이므로 핀 2개만 체크하여 결과를 출력합니다.

3. 코드입니다. Hoangkhoipcb 님의 코드를 일부 인용했습니다.

4. 명령어는 min_pitch_bga 이며

체크할 pitch값을 수정하고 싶으시면

min_pitch_bga 0.9 를 사용하시면됩니다.

axlCmdRegister("min_pitch_bga" 'min_pitch_bga ?cmdType "interactive")

procedure(min_pitch_bga(@optional (argu_bga_pitch "0.5") "S")

let((min_bga_pitch total_count symbols symbol_refdes sym_pins

sym_pins all_pin_numbers a1_pin a2_pin a3_pin a4_pin a1_a2_dis a2_a3_dis a3_a4_dis)

min_bga_pitch = atof(argu_bga_pitch)

total_count = 0

symbols = setof(e axlDBGetDesign() -> symbols e -> type == "PACKAGE" && length(e -> pins) > 10)

foreach(symbol symbols

symbol_refdes = symbol -> refdes

sym_pins = symbol -> pins

all_pin_numbers = sym_pins ~> number

a1_pin = car(member("A1" all_pin_numbers))

a2_pin = car(member("A2" all_pin_numbers))

a3_pin = car(member("A3" all_pin_numbers))

a4_pin = car(member("A4" all_pin_numbers))

if(a1_pin && a2_pin then

a1_pin = car(axlSelectByName("PIN" strcat(symbol_refdes "." a1_pin)))

a2_pin = car(axlSelectByName("PIN" strcat(symbol_refdes "." a2_pin)))

a1_a2_dis = axlDistance(a1_pin -> xy a2_pin -> xy)

when(a1_a2_dis < min_bga_pitch

axlHighlightObject(symbol)

total_count = ++total_count

printf("RefDes(%s) , Pitch(%f)\n" symbol_refdes a1_a2_dis)

)

else

if(a2_pin && a3_pin then

a2_pin = car(axlSelectByName("PIN" strcat(symbol_refdes "." a2_pin)))

a3_pin = car(axlSelectByName("PIN" strcat(symbol_refdes "." a3_pin)))

a2_a3_dis = axlDistance(a2_pin -> xy a3_pin -> xy)

when(a2_a3_dis < min_bga_pitch

axlHighlightObject(symbol)

total_count = ++total_count

printf("RefDes(%s) , Pitch(%f)\n" symbol_refdes a2_a3_dis)

)

else

if(a3_pin && a4_pin then

a3_pin = car(axlSelectByName("PIN" strcat(symbol_refdes "." a3_pin)))

a4_pin = car(axlSelectByName("PIN" strcat(symbol_refdes "." a4_pin)))

a3_a4_dis = axlDistance(a3_pin -> xy a4_pin -> xy)

when(a3_a4_dis < min_bga_pitch

axlHighlightObject(symbol)

total_count = ++total_count

printf("RefDes(%s) , Pitch(%f)\n" symbol_refdes a3_a4_dis)

)

printf("Min_BGA_Pitch(%f) - Checking Symbol Count = %d\n" min_bga_pitch total_count)

)

이상입니다.

RE: How to check BGA minimum pitch using Allegro Skill language

Hoangkhoipcb — Mon, 13 Jul 2026 13:46:39 GMT

Hi BZ202408076026,

I hope this will be helpful

axlCmdRegister("min_pitch_bga" 'min_pitch_bga )

defun( min_pitch_bga ()

let((tmp_list)

pins = car(setof(e axlDBGetDesign()->symbols e->refdes =="BGA"))->pins

if(length(pins) > 0 then

foreach(pin pins

tmp = nil

foreach(item setof(e pins e != pin) push(list( axlDistance(pin->xy item->xy) item) tmp))

push(append1( car(sortcar(tmp 'lessp)) pin) tmp_list)

)

tmp_list = sortcar(tmp_list 'lessp)

printf("Min pitch: %.3f\n " caar(tmp_list))

axlHighlightObject(cdr(car(tmp_list)))

)

BR

HoangKhoi

RE: Shape Degassing parameters extraction using SKILL in allegro APD

Hoangkhoipcb — Mon, 13 Jul 2026 10:31:58 GMT

Hi AnanthVedalaLM,

I hope this will be helpful.

axlShell("degas;skill values = nil fw = _axlFormHook(\"degassing_menu\") foreach(field fw->fields push(list(field axlFormGetField(fw field)) values)) axlShell(\"done\")")

printf("Degassing Values %L\n" values)

BR,
HoangKhoi

Shape Degassing parameters extraction using SKILL in allegro APD

AnanthVedalaLM — Wed, 08 Jul 2026 23:02:08 GMT

I'm trying to extract the values set for a specific degassing pattern using skill , but instead of name , i'm unable to get anything else , is there any way we can extract the void array parameters and void spacing constraints that we set in the shape degassing tool, instead of using GUI, is there any other option to set those parameters for a pattern and also extract them

usually i'm getting the pattern name in this way

shapedbId->shapeBoundary->prop->DEGAS_SHAPE_PROPERTIES

which just leaves me with the name of the pattern used on the shape, but unable to figure out how do we actually get these parameters using skill

other questions i have ,

Are these parameters for the dynamic shapes global or local ? and how are these parameters stored in the database

RE: Shape Degassing parameters extraction using SKILL in allegro APD

B Bruekers — Mon, 13 Jul 2026 05:35:15 GMT

It looks like these parameters are stored in an attachment: axlGetAttachment("lbd_param" 'string)->data

Perhaps this helps?

RE: Shape Degassing parameters extraction using SKILL in allegro APD

AnanthVedalaLM — Fri, 10 Jul 2026 15:06:19 GMT

Yes , I'm Talking about the following values that we set in the shape degassing menu, once we set these values, we can save them as patterns, i'm tying to get those values using SKILL, to use for other purposes and trying to modify them to create a new pattern

RE: Shape Degassing parameters extraction using SKILL in allegro APD

JuanCR — Fri, 10 Jul 2026 14:32:15 GMT

Hi. What do you mean global or local? with respect to what? Yes, they are in the database. When you say "parameters", I assume you're talking about the type of shape of the void, size of it, separation, etc. right?

RE: axlOpenDesignForBatch( works differently between 22.1 and 25.1 ( appears broken )

Mhawley1 — Wed, 08 Jul 2026 11:58:28 GMT

Nope , nevermind . I am an idiot . There is a variable in preferences that needs to be set true for that command to work with no prompts .

It called NOCONFIRM . Once that is checked the skill works as expected .

axlOpenDesignForBatch( works differently between 22.1 and 25.1 ( appears broken )

Mhawley1 — Tue, 07 Jul 2026 13:05:43 GMT

I just found something interesting today and would be nice for someone to test.

It would seem like axlOpenDesignForBatch( no longer runs without a save prompt in 25.1 under the WF mode . Can someone try this out . Try out the example and see if you can batch open two dra's without the prompt coming up .

axlOpenDesignForBatch("u.dra" "wf") ( tested in 25.1 S 30 )

Should I make a ticket ?

How to import a techfile through SKILL

JuanCR — Thu, 02 Jul 2026 12:30:33 GMT

axlRunBatchDBProgram can be used to import a techfile.

Open the design in Allegro X PCB Editor or Package Designer and type skill at the command line:

Command > skill

The command line changes to the Skill prompt:

Skill >

The following skill code will create a log file and import a techfile. In the following skill code, replace mytechfile.tcfx with your own techfile name including the .tcfx extension:

Skill > axlRunBatchDBProgram("techfile" "techfile -$ -r mytechfile.tcfx %s" ?reloadDB t ?logfile "techfile")

Wait while the techfile (apd) runs:

The view of the techfile UI will appear. Scroll to view the summary.
Close the file.
In the database, to exit from the skill prompt, type exit:

Skill > exit

The Command window changes from Skill > to Command >:

Command >

axlDesignFlip()

DavidAhl — Fri, 26 Jun 2026 10:06:26 GMT

Hi,

Im using the axlDesignFlip() in a script. In version 23.1 it worked great but when i run the script in version 25.1 it wont flip back the design. From the documentation i cant see that anything has changed. Is this a known bug in 25.1 or have i missed if something changed?

I tried this in both 23.1 and 25.1, both gave the same print out but in 25.1 the design doesnt flip back..

best regards

david

RE: axlDesignFlip()

DavidAhl — Thu, 02 Jul 2026 06:37:45 GMT

I got confirmation from our support that it is a bug in 25.1. They have created a case with Cadence to get it fixed.

RE: axlDesignFlip()

DavidAhl — Mon, 29 Jun 2026 07:02:40 GMT

Thank you for your reply,

I get the same result as before when trying this. It flips back in 23.1 but in 25.1 is stays flipped.

RE: axlDesignFlip()

DavidAhl — Mon, 29 Jun 2026 06:58:18 GMT

Just to print out what the program thinks the status is. Since it was behaving wierd.

RE: axlDesignFlip()

Ejlersen — Fri, 26 Jun 2026 17:18:38 GMT

According to the documentation you can do the following to toggle the display of flipping the design

axlDesignFlip( !axlDesignFlip())

RE: axlDesignFlip()

Elecguy — Fri, 26 Jun 2026 16:42:33 GMT

May I ask why sometimes you pass an argument to the function and why sometimes you don't?

RE: Place Via Array Boundary

zpofrp — Thu, 18 Jun 2026 09:53:48 GMT

Hi HoangKho and karthikeyank,

Could you share the skill to place via on both sides of cline.

Place Via Array Boundary

karthikeyank — Mon, 04 Nov 2024 09:08:27 GMT

Hi All,

I want to do some operations like Place->Via Array->Boundary, I have additional requirements. I don't know how to place via in ODD and ARC Segments. Can anyone plz help me out.

Program:

foreach(ClineDtlp ClineDt
foreach(ClineSegDtlp ClineDtlp->segments
ObVal = ClineSegDtlp->objType
XpointF = xCoord(car(ClineSegDtlp->startEnd))
YpointF = yCoord(car(ClineSegDtlp->startEnd))
XpointS = xCoord(cadr(ClineSegDtlp->startEnd))
YpointS = yCoord(cadr(ClineSegDtlp->startEnd))
println(ObVal)
if(ObVal == "line" then
LnVal = sprintf(nil "%s", ClineSegDtlp->lineType)
if(LnVal == "vertical" then
FirstVal = axlDBGetLength(ClineSegDtlp)
println(FirstVal)
FirstVal = round(FirstVal)
PassVal = FirstVal / 30
PassStr = sprintf(nil "%d", PassVal)
PassPrseStr = atoi(nth(0 parseString(PassStr "-")))
println(PassPrseStr)
if(YpointF > YpointS then
for(i 1 PassPrseStr
myvia = axlDBCreateVia("DUMMY_20MIL", XpointF + 50:YpointF, nil, nil, 0.0, nil)
YpointF = YpointF - 30
)
else
for(i 1 PassPrseStr
myvia = axlDBCreateVia("DUMMY_20MIL", XpointF + 50:YpointS, nil, nil, 0.0, nil)
YpointS = YpointS - 30
)
)
else
if(LnVal == "horizontal" then
;Code
else
if(LnVal == "odd" then
;Code
)
)
)
else
if(ObVal == "arc" then
;Code
)
)
)
)

Image:

customized GUI to control artwork film

MZ20250602835 — Mon, 01 Jun 2026 05:45:19 GMT

Dear all,

i would like to use film_domain.form as the base to create a customized GUI in which the user/Layouter can assign specific artwork films for Artwork and PDF domains(the Domains IPC2581 and Visibility will not be displayed).

may i ask in my case which skill should i used to achieve the expected function?

Many thanks

Moyan

RE: customized GUI to control artwork film

MZ20250602835 — Tue, 09 Jun 2026 06:30:10 GMT

Dear techiecs,

glad to give a update:

I created the skill with your help(axlFilmCreate ) and it works as i expect. Many thanks again for your help and support.

Many thanks again and best Regards

Moyan

How to start SKILL IDE from APD or Allegro in Linux?

JuanCR — Fri, 05 Jun 2026 23:35:51 GMT

The debugger environment is not so convenient for APD / Allegro debug. It is more oriented for SKILL DFII development. SKILL Debugger is incapable to debug the axlSKILL (Allegro specific) functions.

There is no graphical debugger for axlSKILL, but you can set the telskill environment variable to open a SKILL development window.

If you are looking for line debugger with Allegro, there are some command line debugging options available to you:

installDebugger() and axlDebug() are functions you can use to set debug mode.

The following is an extract from the axlIsDebug() function description in cdnshelp, which describes what axlDebug enables:

When this mode is set, AXL may print additional AXL API argument warnings when arguments to AXL functions are incorrect. Many warnings do not obey this variable because they are considered serious or edge conditions. Warnings supported are less serious and are known from user feedback to be troublesome to program around.

Typically, when an AXL API function encounters an argument error, it will print a warning and return nil.
When unset, the code runs in development mode and eliminates many of these warnings. You should have this mode enabled when developing SKILL code.

Another function available to you is sstatus. Refer to the online documentation to get the full list of the internal variable names and switch values available to you through this command.

sstatus(
s_name
g_switchValue
)
=> g_switchValue

Description: Sets the internal system variable named to a given value. This is a syntax form. Internal variables are typically Boolean switches that accept only the Boolean values of t and nil. Efficiency and security are the reasons why these system variables are stored as internal variables, which can only be set by sstatus, rather than as SKILL variables you can set directly.

Other things you can do are set breakpoints with breakpt and then progress through your code with step and continue etc.

Note: The online document, SKILL Development Functions Reference, is helpful for describing the functions. However, you must be aware that any reference to a graphical interface for debugging does not apply to axlSKILL. As with any programming language, you can set a debug variable and then make conditional checks for it. If set, you can have your code print values of variables from your code.

The other way to check the code before delivery is to launch the SKLINT tool and to try to solve all warnings, errors given by this tool.

Steps to use SKLINT on UNIX:

Run setenv TELSKILL in your local env file.
Run Allegro and then keep Allegro iconified.
In the current shell window, the prompt becomes SKILL>. Launch SKILL> sklint ?file "filetodebug.il".
filetodebug.il is the file name you want to debug.