All of the sudden, not sure what happened, SETUP > DISPLAY COLORS will not pull up at all.
This occurs on any layout file I try to do it on, so it is not isolated to one layout file.
What toggle could have turned this off?
Maybe it is somehow coming up now behind the main screen? If so, I can't find it by minimizing or closing other screens.
Thanks
Randy Flowers
Hi Sam,
Yes, the speed is my concern.
Thank you very much for your reply.
Best Regards,
Marben
Is there a script out there that can be used for checking the clearances of nets between layers in the Z dimension?
Thanks
Brian.
Hi
1) Make sure PADS Layout is closed.
2) Locate the powerpcb.ini file. It is default placed in C:\MentorGraphics\PADSVX.1.2\SDD_HOME\Programs\
3) Open powerpcb.ini file in a text editor.
4) In the [dialogs] section - look for 'Display Colors Setup - Position='
5) Delete the entire line and - save the .ini file - close the text editor.
6) Open PADS Layout. Now the Display Colors Setup dialog will be placed in a default position in the middle of the screen.
Hope this helps.
regards Klaus
Dear all,
I am very desperate...
I use Expedition EE7.9.5 (Update 24) on a machine with Windows 7 up last week. But now I get a new machine with Windows 10 and I have make the experience, that EE7.9.5 especially ExpeditionPCB is not able to work on that machine...
Furthermore our company canceled the support contract due to the high cost. So the last version of Xpedition we get from Mentor ist the Version VX.1 in Dezember 2014. But due to possible bugs of this major release, we avoid the installation of this release.
So my question is, what can you recommend at my position. Should I install Windows 7 and EE7.9.5 knowing the Support of Windows 7 ends in 2020?
Or should I install VX.1 on my Windows 10 machine in the hope there are no bigger problems during the use of the main function of Expedition?
Do anybody know which bugs are presented on VX.1?
At moment, it seems there is no intention of reentry into the support contract due to the high cost. Quite the reverse! They thinking about changing to an alternative PCB System
OK. This is solved. First cup of coffee morning revelation.
For each part there are a set of what I'll call "fixed" properties, including Name, ID, Partition, Symbol Name, Name Inverted and *lo and behold* "Forward to PCB". Selection choices for the "Forward to PCB" property are Inherit from Definition, True, False. I never noticed this until this morning.....
I deleted the manually added User Property, applied this "fixed" property to the BOM only items and it all now behaves as expected.
I also note that Borders have a property FORWARD_PCB with a value of "0", which also does not show up in the Property Definition Editor.
Why don't properties like these show up in the Property Definition Editor list?
Why are these properties inconsistently handled?
Ken
Did exactly that, but still no Display Colors Setup dialog box after I re-open PADS layout.
Any other ideas, other than contacting Mentor help?
Thanks
Randy
I meant CAN'T
Assuming that the window actually opens but it goes somewhere out of screen:
- Close and reopen Layout to starts fresh
- Go to Setup->Display Colors
- Now press Alt+space then M
- If the mouse cursor disappears it means that the window is somewhere out of screen. Play with the arrow keys to bring it into view.
- Press Enter when done.
I've been trying to get partquest to work with PADS VX1.2 without any success.
I followed Gary's video but doesn't work as in the video.
I am missing PartQuest directory and partquest.ini file after installation. only folder created was PartQuesttools and its directories
files extracted with .x extension
click on import partquest part
nothing else happens
Wim,
This is a problem some customers have experienced. Unfortunately, we haven't discovered the root cause. You can edit the Sentinel LDK License Manager service and change the Startup type to "Automatic (Delayed Start)". That may help.
Guy
Hi Sam,
How to create xcell for calibre PEX ?
For example I want to exclude I10(and2x1_i) , I11(and2x1_i) and I16(sw002a_i) .
Please give me example .
Best regards,
Marben
Hi Guys,
in the meantime VX 1.2 is available and .... you can not run
a
Hello Rob,
For Silkscreen, we always use the 'vf_std' font. What you see is what you get.
As you have noticed these 'properties' don't show up as properties, this is because they are built-in attributes, not properties managed by the prp file. However, to pass the settings from the symbol definition (the Inherit from Definition option) to the tools requires a property in the symbol editor - hence some inconsistency in what is displayed depending on the editor (symbols are ASCII so we need to embed the data somehow).
You should also take into consideration the 'Part List Exclude' property if you want such items to appear in the BOM but not on the PCB - this is discussed elsewhere on the community and also fully documented in the user guide.
It is not a bug, if you push down to a sheet you have opened the sheet but until you work inside it it is not active, hence you can't pop back out.
Try setting UpdateMappedDevices to 'on' in the 'CONVERSION' section of the translator control file, under the Settings tab of the dialog. If this doesn't work then log an SR with support.
Thank you for the explanation. We use the Part List Exclude property extensively.
Ken
Hi Marben-
The methods have changed slightly over the years, so I'll describe it at a high level, and point you to the manuals for your version for details. I am most familiar with xRC (the manual is xrc_user.pdf), but I am told xACT is more widely deployed these days (xact_user.pdf). You might also be interested in the tips in the section "Improving Run Time" in the "Integration and Troubleshooting" chapter -- xcells aren't the only speed-up.
First, you need an xcell file. The format is similar to an hcell file, but has more options. The options available in your version will be described in the manual in a section titled "Xcell List Format". (xRC's 2016.1 version is at https://supportnet.mentor.com/docs/201601106/docs/htmldocs/mgchelp.htm#context=xrc_user&id=95&tag=ide3fa103b-4964-48cb-8… )
You can supply the xcell to the run using one of three methods:
- In the Calibre Interactive - PEX GUI, enter the filename in the Inputs button > Hcells tab > PEX x-Cells file box.
- If you are running from the command line (batch mode), add it to the -pdb call with -xcell <filename> OR
- (alternative way for batch runs) add it to the SVRF file with the statement PEX XCELL -- check the SVRF manual (svrf_ur.pdf) for which of the three formats to use for your set up.
The xRC and xACT manuals do have some tips on how to choose the cells to best improve performance. The xRC 2016.1 section is
"Tips For Choosing Xcells for Full Hierarchical Extraction". It is in a section ("Hierarchy Control with Xcells", in the "Handling Input" chapter) that also describes how xcells and hcells interact, and some additional features like wildcards and setting the xcell to be a specific cell instance.
Good luck-
Sam.
Nice chatting with you Tom! Good to see PartQuest working on your computer! Thanks for contacting our support team for help.