I was trying to use the good old bmp2asc program to import a bitmap into Layout.
But I couln't figure out a way to make it working under Win 7 x64.
So I gave up bmp2asc and I wrote my own script which can be run from within Layout and it also presents a GUI.
The file is attached to this message. Please post your questions here in case you have problems.
Enjoy!
BR
Hello sir
In PCB design , how i calculate the distance between two trace both are operate in 3V3 volts, one trace is signal and another is power supply.
what is the formula for calculate for this
Hi,
can someone to help me to remove the extra line the splice?
Thanks,
Jagadhees
I just posted AATK Version 1499 to SourceForge. In this release, we have made changes in the FlipChip menu to support VX, Win64 and Linux. Not all functions work with Linux since some scripts interface directly with Microsoft Excel.
Just a reminder that AATK has hundreds of scripting examples. Most are vbs or forms but there are C#, JScript, TCL examples as well. AATK is not just for Expedition, it has examples for CellEditor, Drawing Editor, Dx, Fablink, HyperLynx, HyperLynx DRC, Library Manger, PathFinder, Quiet Expert, CES....
You can download the toolkit off of the OpenSource website SourceForge. All the scripts have source code and should be used at your own peril. SInce we give you the source code, if something doesn't work, you can fix it to work yourself and then send me your fix and I will update AATK. Our standard discalimer is we, especially Me, My team of contributers and Mentor Graphics are not held liable for anything whacky happening to your database! We are really just trying to help so don't blame us for a delay or crash, these scripts are meant to help you do your job faster and better.
You can download AATK from here:
https://sourceforge.net/projects/uwtoolbox/
This software is NOT officially supported by Mentor Graphics.
###########################################################
###########################################################
## The following software is "freeware" which Mentor Graphics ##
## Corporation provides as a courtesy to our users. "Freeware" ##
## is provided "as is" and Mentor Graphics makes no warranties ##
## with respect to "freeware", either expressed or implied, ##
## including any implied warranties of merchantability or fitness ##
## for a particular purpose. ##
###########################################################
###########################################################
By downloading and installing, you agree to this Acceptable Usage Policy
Hey all, just a quick heads up that today's live Google Hangout with Digi-Key and Mentor Graphics is due to start in about fifteen minutes (12 p.m. CST). The topic is "Using Reference Designs to Accelerate Product Development," and it should be a good one! You can access the Hangout here: Hangout on Air with Digi-Key and Mentor Graphics
If you have any questions during the Hangout, feel free to tweet them using the hashtag #DKHOA. Also, feel free to discuss the event here!
I've been using the DDRx Batch Simulation tool (HyperLynx 8.1.1) to simulate an implementation of DDR3 memory, and I noticed that the tool seems to be ignoring the differential thresholds defined in the IBIS model for the Micron memory I'm using, and is using 0V instead.
For single-ended signals (address, control, command, data), it seems to be using the correct VIH(AC) and VIL(AC) thresholds (VTTref +/- 160mV in this case) for determining setup and hold times. But for differential signals (clock and data strobes), it seems to be using Vdiff = 0 rather than VIH,diff(AC) and VIL,diff(AC) (+/- 320mV for this part) for determing setup and hold times. In my simulations, there is ~50 ps between Vdiff = 0 and Vdiff = +/- 320mV, so all setup and hold times reported in the results spreadsheets are off by ~50 ps. This is causing some of my data signal setup times to be reported as failures under worst-case conditions, when manual inspection of the waveform files shows that they are actually passing when using the correct differential voltage thresholds for the DQS signals.
Is this behavior expected? I checked the "Use all four receiver AC/DC thresholds" option in the DDRx Batch-Mode Wizard setup, and I assumed that they would be used for differential as well as single-ended signals.
I'm looking for a automation method to check, whether a design is packed or not.
We are creating partlists but this only makes sense, when the design is packaged. So if the design is not package we want to warn the user, that he should package first.
I have been trying to install the modelSim SE on my linux OS,
after setting the environment variable like this:
LM_LICENSE_FILE:export LM_LICENSE_FILE=/<my path>/license.dat
Set the path to MoselSim binaries:
export PATH=$PATH:/<my path>/bin
I started ModelSim with this command: vsim
unfortunately I got this message:
Unable to checkout a viewer license necessary for use of the ModelSim graphical user interface. Vsim is closing.
The screen below was displayed:
Anyone can tell me how to solve this problem?
I really need a help.
Please
Is there a solution to manage "Name" origins and sizes of symbol by default?
We're having problem especially with Link symbols which Net Names becoming un-oriented.
If have a pin property in the Library Signal which shoudl be styled to be visible on the diagram. Since the library properties can not be altered we need to provide a mechanism to allow a user to display an alternate property. A pin property Pin Function was created in the project object type information section. We have both properties listed in the styling. the pin function property has no query, and the signal property has this query for (DevicePin) evaluate (not (value exists (property PIN FUNCTION)))
The issue is this query appears not to be checking if a value exist for Pin Function, but if the property itself exist as if we add the property (auto assign) the signal property will not show.
How do we right a query so that when there is a value for the pin function property the signal property is not visible.
Hi,
I have following script:
Set dxdapp = GetObject(,"Viewdraw.Application")
set dxdview = dxdapp.ActiveView ' View Object
dxdapp.Visible = False
If Not dxdView Is Nothing Then
Set dxdblock = dxdview.ActiveBlock
sTopBlock = dxdblock.GetName(SHORT_NAME)' Get the name of the top level schematic
WalkDesign (sTopBlock)
SchematicSheetDocuments.Close
Scripting.sleep 100
dxdapp.SchematicSheetDocuments.Open sTopBlock, "1"
Else
msgbox "Kein Schaltplan geöffnet"
End IF
dxdapp.Visible = True
If I call this script the second time, I always get the error message:
Source:'Laufzeitfehler in Microsoft VBScript'
Line:58 Char:0
Error:0x800a01ad 'ActiveX-Komponenten kann kein Objekt erstellen: 'GetObject''
What is wrong?
Kind regards,
Markus
I am attempting to write a script that will re-annotate the designators in a set pattern in Pads Layout so as to neaten the board design. I discovered that you can read the names using ActiveDocument.Components(x).Name, however it throws an error when I attempt to change the name by assigned that property a new text string (ActiveX Incorrect number of parameters). What must I do or what must I use to accomplish this?
I am currently using Pads Layout vX.0
I'm just wondering how people like the notification streams in the new communities.
Is there a tutorial, preferably a video, that shows how to route interactivly?
Using EE7.9.5.
Hello, I'm fairly new to the PADS environment, and am running into a problem that has stumped me so far. I've tried forwarding my schematic from xDxDesigner to PADS Layout, but when I do, only a few of the parts in my schematic actually show up. The decals are in different libraries, but I'm fairly certain I've included all the relevant libraries in the project. Is there anything I'm missing, or some place I can look for help with this problem? Thanks for your help.
Hi all,
I am tying to add a component attribute "Part Number" to the existing script file "Origin_Centroid_17 - Excel Part List Report.bas".
Attached is the schipt file. Let me know if you need any other info.
Hi,
I am using EE7.9.5 flow for Board Station to Expedition migration. The PCB part is successfully trasnslated but the DA2DX transcript stopped with the above error while reading design data.
To check the references I switched back to board station and verified that the PCB-Schematic are in sync. What references is this script referencing to and where should i check?
Thank you.
Saad
Last year, for various reasons, we decided to take the plunge and move over to Expedition. I had had exposure to Expedition previously under the old VeriBest guise and I knew DxDesigner from my old PADS days, so I was well positioned to handle the change over.
The first and most obvious question we need to answer is what to do with legacy designs. Do we pay for, or try to convert them ourselves? Or do we maintain a Boardstation seat to handle sustaining engineering tasks? In the end it was decided that the most cost effective solution was to keep BS designs where they were - For the time being at least. Only new product and complete retracks would be put onto expedition.
Second, libraries, how do we recreate the extensive work we had put into our libraries in expedition?
For DxDatabook entries, we wrote a script to extract the information needed for each component type, from Boardstation catalogs. This was piped into a SQL database.
I am sure there are ways to translate symbol graphics, properties and mapping files into Expedition, but I do not believe there is an easy way to do it. In addition to this, regenerating symbols by hand as it were allows you to review your libraries, which will contain a legacy of symbols stretching back a decade and beyond. It gave us a chance to review the way we draw symbols, what properties we use by default and when and so on. To this end, we wrote a spec on how to create a symbol which ensured that every single symbol was drawn in the same manner, to the same scale.
In order to decide what symbols were essential and what symbols were perhaps less important, we extracted, from our MRP system, a list of the most used parts and cross matched those part numbers to symbols - Giving us a priority list. We could then see which symbols were going to be unlikely to be required for new product, and therefore not waste time recreating them.
Where we recreated symbols, we ensured that we used the same pin names and symbol names as the Boardstation libraries, in order to expedite processing of Boardstation mapping files to help create Expedition Parts.
Padstacks were recreated manually, it would have been a fairly easy process to ASCII out pads from Boardstation and import them into Expedition (using a handy little program called "geom2cell") but we wanted to take advantage of the Padstack Editor in Expedition, which, vastly reduced the size of our padstack library.
Cells were the easiest task. We simply created ASCII files of geometries per partition, and then ran them through the geom2cell program, and since we have named the newly created Expedition padstack library in the same way as our Boardstation one, the conversion was painless, and with a few click we had a fully populated cell library.
Expedition part creation was a mixture of manual and automatic processes. We wrote a script to look at Boardstation catalogs and cross match those to Boardstation mapping files, and it then creates an ASCII file in Expedition Part format. We then ASCII in that part to the relevant partition and check that the symbol and cell marry up as expected.
Things like Drawing Borders etc fro assembly drawings all came over as ASCII files, all we had to do was make sure we created the user layers we required in Library Manager.
Templates don't exist as such in Boardstation, so these all had to be created from scratch. But I like the concept of them, so we have made extensive use of them rather than just have a simple "vanilla" template. These were created on a per layer count/copper weight basis for layouts and CES (infact we have several CES templates due to creepage and clearance requirements)
The final phase was testing, from installation (which we wrote a spec for to ensure that each machine picks up exactly the right customisation files) all the way through to gerber/neutral file output.
We are at a point now where we could go "live", but since the need to have it installed is a few weeks away, we are using the time to write automation scripts in DxDesigner and Expedition to help with post processing.
The entire process, thus far, has taken around a year, of course during that time we have had to cope with ongoing project work on Boardstation. We have had regular progress meetings and documented everything we have done on a wiki site, we have a project plan and a schedule for each task which is updated regularly.
It is without question a huge undertaking, but it can be done, so long as you for allow enough time for preparation and planning and track your progress.
Hello,
In Design Capture (2005) cross probing worked wonderfully for us during design reviews. For instance, if we wanted to review a DDR layout we would:
When we did this, we didn’t have to hold down CTRL or anything like that. Highlights held until we cleared them with the lampshade (clear highlights) button.
When we upgraded to Design Capture 2007, things got goofy. Cross probing was “updated” so that highlighting didn’t hold the highlight as you moved from part to part unless you held CTRL. I was told that this is what the customers wanted, which sounds funny since that’s how Select works. And the parts wouldn’t highlight pads solidly unless you messed around with the Display Solid Color button. Doesn’t make a lot of sense to me. However, I found a way to trick it into working like it did in the 2005 version (long story). This was irritating, but it could still be used if you knew the “trick”.
Now I’m evaluating DxDesigner. I can’t do what I want to do (as described in # 1-4 above). Highlights don’t stay highlighted. I can’t “trick” it into working. I can’t cross probe across multiple pages without the highlights disappearing when I go to a new page. Am I doing something wrong? Is this how it is supposed to work?
Thanks