PCB Libraries Forum Homepage
Forum Home Forum Home > PCB Footprint Expert > Questions & Answers
  New Posts New Posts RSS Feed - Cadence OrCAD PCB 17.2 CAD Output Issue
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Cadence OrCAD PCB 17.2 CAD Output Issue

 Post Reply Post Reply Page  12>
Author
Message Reverse Sort Order
jameshead View Drop Down
Expert User
Expert User
Avatar

Joined: 20 Mar 2012
Location: Oxfordshire, UK
Status: Offline
Points: 576
Post Options Post Options   Thanks (0) Thanks(0)   Quote jameshead Quote  Post ReplyReply Direct Link To This Post Topic: Cadence OrCAD PCB 17.2 CAD Output Issue
    Posted: 10 Oct 2017 at 4:22pm
Sorry for the delay in replying to this issue. 

There's something screwy with the Cadence OrCAD installation on the computer that I inherited here, probably as a result of the last user keeping both the current version 17 and the previous version 16 of OrCAD on the computer because of the need to convert legacy designs, and version 16 allows output of a certain format of PCB file apparently.

We may have a work around but to be honest the issue isn't relevent now because the company has decided to move from OrCAD to Pulsonix now.

Back to Top
 
Back to Top
Tom H View Drop Down
Admin Group
Admin Group
Avatar

Joined: 05 Jan 2012
Location: San Diego, CA
Status: Offline
Points: 6031
Post Options Post Options   Thanks (0) Thanks(0)   Quote Tom H Quote  Post ReplyReply Direct Link To This Post Posted: 06 Sep 2017 at 6:53am
Are you good to go now?

Stay connected - follow us! X - LinkedIn
Back to Top
JamesHeadOI View Drop Down
Active User
Active User


Joined: 05 Sep 2017
Status: Offline
Points: 40
Post Options Post Options   Thanks (0) Thanks(0)   Quote JamesHeadOI Quote  Post ReplyReply Direct Link To This Post Posted: 06 Sep 2017 at 5:00am
It also involves running the script from inside the PCB Editor tool.
Back to Top
JamesHeadOI View Drop Down
Active User
Active User


Joined: 05 Sep 2017
Status: Offline
Points: 40
Post Options Post Options   Thanks (0) Thanks(0)   Quote JamesHeadOI Quote  Post ReplyReply Direct Link To This Post Posted: 06 Sep 2017 at 3:52am
Parrallel Systems, the reseller, advised removing the top of the script for the footprint, i.e. this section:

# Allegro Script
# File: C:\_JH\PCBLibraries\Orcad\HARTING_09185507324\harting_09185507324.scr
version 17.2

setwindow pcb
new
newdrawfillin "harting_09185507324.dra" "Package Symbol"

So the first line is "color". This seems to work.
Back to Top
JamesHeadOI View Drop Down
Active User
Active User


Joined: 05 Sep 2017
Status: Offline
Points: 40
Post Options Post Options   Thanks (1) Thanks(1)   Quote JamesHeadOI Quote  Post ReplyReply Direct Link To This Post Posted: 05 Sep 2017 at 11:43pm
I've managed to get the batch file running now. It seemed to be the case on this Windows 10 system that the PATH environment variable was entered for the local admin account and not the user account.

I still don't get a .dra file created though. The padstack is created but no .dra file but no error messages are shown.
Back to Top
JamesHeadOI View Drop Down
Active User
Active User


Joined: 05 Sep 2017
Status: Offline
Points: 40
Post Options Post Options   Thanks (1) Thanks(1)   Quote JamesHeadOI Quote  Post ReplyReply Direct Link To This Post Posted: 05 Sep 2017 at 11:18pm
There's both 16.6 and 17.2 on the system. I understand 16.6 has been left on because it's the only method to import old Orcad Layout designs and libraries.

I've checked that both CDSROOT and PATH both now point to the 17.2 installation, and only that installation. The exe files required are in the tools/bin folder but still the error message appears.
Back to Top
chrisa_pcb View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 29 Jul 2012
Location: San Diego
Status: Offline
Points: 772
Post Options Post Options   Thanks (1) Thanks(1)   Quote chrisa_pcb Quote  Post ReplyReply Direct Link To This Post Posted: 05 Sep 2017 at 11:03am
Originally posted by JamesHeadOI JamesHeadOI wrote:

I've already noted the "known cadence issue" subject under "bugs" on this forum.
My environment variables appear to be set up okay:
CDSROOT is C:\Cadence\SPB_16.6
PATH is
%CDSROOT%\tools\libutil\bin;%CDSROOT%\tools\pcb\bin;%CDSROOT%\tools\bin;%CDSROOT%\openaccess\bin\win32\opt;%CDSROOT%\tools\fet\bin;%CDSROOT%\tools\specctra\bin;%CDSROOT%\tools\pspice;%CDSROOT%\tools\pspice\library;%CDSROOT%\tools\capture;


If using 17.2, the CDSROOT must be set to the 17.2 root directory in order for the paths to resolve to the 17.2 binaries. The CDSROOT variable is a mechanic used by Cadence Switch Release to easily swap to a different version of OrCAD. It does this by changing the base directory for the product, which always has to match whichever version of allegro you're trying to access.
Back to Top
JamesHeadOI View Drop Down
Active User
Active User


Joined: 05 Sep 2017
Status: Offline
Points: 40
Post Options Post Options   Thanks (1) Thanks(1)   Quote JamesHeadOI Quote  Post ReplyReply Direct Link To This Post Posted: 05 Sep 2017 at 7:27am
Yes, I had read both the user guide and the known issue post prior to posting.
I had already gone through and checked the environment variables were all set up correctly.
I'll dig out Chris's e-mail.
Back to Top
Tom H View Drop Down
Admin Group
Admin Group
Avatar

Joined: 05 Jan 2012
Location: San Diego, CA
Status: Offline
Points: 6031
Post Options Post Options   Thanks (1) Thanks(1)   Quote Tom H Quote  Post ReplyReply Direct Link To This Post Posted: 05 Sep 2017 at 7:24am
Did you read this?
https://www.pcblibraries.com/forum/known-cadence-17-2-issue-read-here_topic2081.html

And this?
http://www.pcblibraries.com/products/fpx/userguide/default.asp?ch=205

If you have any CAD tool interface issues, please contact Chris Arnold.

Stay connected - follow us! X - LinkedIn
Back to Top
JamesHeadOI View Drop Down
Active User
Active User


Joined: 05 Sep 2017
Status: Offline
Points: 40
Post Options Post Options   Thanks (1) Thanks(1)   Quote JamesHeadOI Quote  Post ReplyReply Direct Link To This Post Posted: 05 Sep 2017 at 5:40am
I've already noted the "known cadence issue" subject under "bugs" on this forum.
My environment variables appear to be set up okay:
CDSROOT is C:\Cadence\SPB_16.6
PATH is
%CDSROOT%\tools\libutil\bin;%CDSROOT%\tools\pcb\bin;%CDSROOT%\tools\bin;%CDSROOT%\openaccess\bin\win32\opt;%CDSROOT%\tools\fet\bin;%CDSROOT%\tools\specctra\bin;%CDSROOT%\tools\pspice;%CDSROOT%\tools\pspice\library;%CDSROOT%\tools\capture;
Back to Top
 Post Reply Post Reply Page  12>

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.328 seconds.