Hi Vamsi,
Due to performance issue, we prefer users to do "Update Border" to refresh the plugin tables. Plugins are written externally and some of them may be too complicated. Getting every thing refreshed dynamically is going to hit the performance of the tool. Hence, as you said, "Update Border" is the best way to get the plugin table refreshed.
Thanks
Saurabh
Hi Saurabh
Thanks for the response .
But automatic update worked in earlier version 2014.1
Newer Version 2015.1
Is there a change in Design the way this Plugin Table updates ?
Kindly confirm
Also if a part Number is updated , it is automatically getting updated in The Table
But if Instance name or description or Object Addition or Deletion doesnt update
IS this the way it is designed to be , Kindly confirm this too.
Regards
Vamsi Krishna
VX.2 is now available on SupportNet.
Thanks! What would you say the main advantage would be over Access?
Looks like I have some reading to do
It is cross platform, so Linux and Windows. Works on both 32-bit and 64-bit software without the complicated dependencies on ODBC drivers (Microsoft issue) and is free.
If you don't like the output from the command File-->Export-->General Interfaces-->Generic AIS that Charles pointed out, there is a sample script in \MentorGraphics\EEVX.1.2\SDD_HOME\standard\examples\pcb\Automation\Scripts called AIS.vbs. You could modify this to meet your needs. I'm attaching one that I have used in the past
Thanks! The fact that it doesn't use ODBC drivers is what peaked my interest when I saw the video.
The Auto-Route is very good but when we talk about ground nets/wires!
Why Auto Route leaves ground conductors so short?
Is there a way to edit or increase this length from ground conductors in autoroute?
Hi,
I am using the version X-ENTP VX.1 (32-bit)
kind regards
raliesch I solved my license problems (the hardware dongle driver had to be updated) so I was able to open the PCB with expedition. Once inside expedition I could open the central library (without a crash) and it was converted to the new format, as you suggested.
So, now it is possible to work with the PCB. Opening the schematic with DxDesigned (both from windows and from expedition) it still crashes!
The behaviour is: the schematic opens but the first time you click on the schematic sheet, or select a menu voice or push a button in the bar it immediately crash!
regards
Davide
Have you tried deleting the contents of the WDIR as suggested previously? If that works I would not suggest you put the contents of the old WDIR back - it would indicate that something in the WDIR is causing the problem. To migrate the WDIR contents uninstall and then re-install VX.2 and use the option on the WDIR path dialog to copy the contents between the old and new WDIR. This will ensure only good data is copied.
Have any of these suggestions solved your problem? If so please mark the question as solved.
Thx.
Hello,
You can get a "snapshot" of what licenses are in use from the command:
lmutil lmstat -f <featurename> -c <path_to_license_server>
For example:
lmutil lmstat -f dmscapacuser -c 1717@myserver
However, I do not recommend you use "lmstat" regularly in a script more than once every 10 minutes. "lmstat" takes priority over license checkouts, and will cause slow checkout performance if used too much.
Regarding xDM Library Server, I believe that you will see all the licenses checked out by "mgcserveruser" or your local equivalent user. You can then use the Admin tool to get details of the actual users. This is probably too complex to answer in the discussion forum, so please raise a service request via Supportnet and a local support engineer can give you more details if you need them.
Regards,
David
see technote MG593636
regards, Charles
okay.
I tried also running DxDesigner with an empty WDIR. I have 2 paths in the WDIR variable: one is local, the other one is a network path (contains the company-wide settings). Both were empty. It still crashes.
regards
Davide
I tried also the migration of the WDIR content. Only the local one was migrated. The other one is still empty.
It still crashes.
regards
Davide
Then you will need to contact support, we've pretty much exhausted all the obvious solutions.
I agree. I'm already in contact with my local support. Just one last question: when I install the VX2@64bit, then a message window appear warning me about the installation of the ODBC driver. How can I be sure that the correct driver is running?
regards
Davide
If Databook works you have the right driver, assuming you are using Databook and if you are using it you are using ODBC as the connection. If not then you don't have to worry about the message.