In xDx use "Tools - Update Libraries" to update xDx Databook with the latest Library information.
↧
Re: Updating xDx Databook
↧
Re: Export Expedition library parts to other formats
Hi,
The HKP files are encrypted ASCII files.
This is the old way to export.
Now you have to write a script that creates the output.
↧
↧
Re: Length Matching of Traces
Hi,
How can I create a matched group?
Thank you
↧
What can I do with xPCB Basic Automation?
Hi all,
I have only the license for VX.1.1 xDx and xPCB and so xPCB Basic Automation.
No license for the Library Manager.
I found some Library scripts on the communities, but they are not working.
Sometimes I get the error "Cannot acquire a Library Manager license" and/or "Cannot acquire Automation Pro license"
This is correct because I don't have these licenses.
My question is: what can I do with the xPCB Basic Automation?
Is there a document which explains the differences for Basic and Pro?
Which statements can I use in Basic Automation?
Thanks.
Wim.
↧
Forward Annotation to replace existing parts in xPCB
Hi all,
I am using xPedition VX.1 with xPCB. In one of my design I had to change a set capacitors which have 201 package type. But when I try to forward annotate ,I get the following error all the time. I have tried all the options available in Project Integration toolbox in order to update the local library. But it wasn't successful.
Error : Cell Name 'CAPC1005_IS0402L' is not a valid cell for Part Number 'CAP-0201-X5R-100nF-10V-10%'.
Thank you
↧
↧
Re: Export Expedition library parts to other formats
Thanks for the reply.
It is helpful, not exactly what I want to hear, because I cannot write scripts.
At least I know the answer.
↧
Re: Length Matching of Traces
Hi,
You can find this in the CES user manual on page 228 (VX1). It works the same for previous releases.
I do not know if you have this manual, but I have attached it to this mail.
Regards, Charles.
↧
Re: Catia V6 ixf implementation
Thank you.
↧
Re: Catia V6 ixf implementation
If you need further information about process, i can happily share it.
↧
↧
Re: Ground Refinement
Hi Simon,
I am able to combine the grounds into two groups. However the issue that I am having is with the ground signals. Once the grounds are combined into two groups (in two different slots), all of the signals from both groups are combined into one single signal.
So even though the ground devices are divided between two groups, high and low, the signals are not being divided between high and low.
↧
Re: Forward Annotation to replace existing parts in xPCB
I have had this problem as well with 7.9.1.
Don't know if there is an automated method to sort it out (hopefully someone from Mentor can provide details if there is)
The way I have resolved the problem, is within the schematic click on the properites of the part/symbol and it will list the cell name proporty. Just delete this value (leave the property).
Then you will be able to package your design.
Tip - When you do the project integraption within the pcb, click on additional options and un-select the Back annotate cell names to schematic option.
This works in 7.9.1 so think it is about the same in VX.
↧
Re: Export Expedition library parts to other formats
Hi Greg,
I have the same problem.
We used the ASCII HKP format to drive our netlist translator.
In the old days it was ASCII and everything was working.
In EE2007.5 Mentor switched to encrypted HKP but you could get a Encrypt/Decrypt license for free. So it was working.
Last year we switched to EE7.9.5. and now to VX.1.1 and the Mentor solution is to write scripts to get output.
I also cannot write scripts and I'm having the same problem you have.
I'm also not so happy about this .
↧
Re: Ground Refinement
Hi John,
I think I need a picture (or some data) to understand what's happening. When you combine devices, their signals are combined. Therefore, if you have a signal (net) that is connected to more than one ground device and these devices are in the different groups (high and low) then this would be a way that all the signals get combined. However, I can't at the moment see any other way that the signals would be combined.
Note that the usual way of handling grounds is that each ground device is connected to a unique net which is connected to the ground device and a single additional device (although it may sometimes be connected to a very small number of related devices if you know they must be grounded identically). If you do this, then the signals will only be combined when the ground devices are combined. So in your case I would expect to have two groups of combined ground devices and therefore two ground signals.
As I said, it may be necessary to see a picture or two to understand exactly your situation.
Simon
↧
↧
Re: Place Via in conductive shape
Maybe you shouldn't consider Net0 as being "a net".
It is just a default flag for conductive features that DON'T have a net assigned.
I'm pretty sure you will not have a problem adding vias to actual nets.
Jack
↧
Re: Ground Refinement
Thank you Simon.
I went back and checked all of my ground devices and nets. I had the properties crossed on one instance. After cleaning this up everything is acting as I would expect (and want).
Thanks again for your help!
↧
Re: Place Via in conductive shape
I can confirm the behavior is the same in VX.1 for (Net0) - you should stick to a specific net assignment if possible.
↧
Licensing Error - ModelSim
I'm tech support for a company using your software. When I try to install a license (extended/renewed) I receive the attached error re: HostID. I understand that the HostID is the same as the MAC address. The user informs me that the motherboard, with embedded NIC, was replaced a few months ago, thus I believe this to be the cause of the error....Am I correct?
If so, how do I go about installing the extended license?
Thanks
↧
↧
Re: Catia V6 ixf implementation
We already support IXF for CATIAV6 in Capital, which as you've indicated, uses the instance name as the CATIA Reference Designator. CATIAV6 instance name handling is different from CATIAV5 and so the exported xml is also changed to remove the UID and include the instance name as the id. I am trying to get in touch with the VeSys product architects to know if there was a reason why IXF for CATIAV6 was excluded from Vesys. My own thinking is that CATIAV6 integrates with a much larger software ecosystem to support the design of much larger platforms, and for which Capital is an excellent adjacent-domain application. VeSys being a mid-level application was possibly never envisioned to integrate with CATIAV6.
However, I'd recommend that you let us know your contact details, so that our folks get in touch with you, get some more details and see how best we may serve your design needs.
↧
Re: Licensing Error - ModelSim
Host ID can be a MAC ID or Dongle ID.
In the image all the IDs listed are the USB dongle ID (starts with 9) , which means the license is tied to those dongles.You need to plug in the dongle to use application
or it can be the case that you are using a wrong license file.
↧
Re: Catia V6 ixf implementation
Hi - when we introduced our ability to exchange wiring with CATIA V6, we decided to make this feature for Capital and not for VeSys. This was mainly because our VeSys customers are typically in smaller teams / organisations / projects and these were unlikely to be using CATIA V6 and more commonly use MCAD products targeted at this segment (e.g. Solidworks and Creo). However, your request shows that this is not always the case and so we will enable the VeSys wiring exchange with V6 in a service pack later this year.
↧