PCB Libraries Forum Homepage
Forum Home Forum Home > PCB Footprint Expert > Questions & Answers
  New Posts New Posts RSS Feed - Orcad 17.2 Decimal Separator Issue
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Orcad 17.2 Decimal Separator Issue
 Post Reply Post Reply Page  <123>
Author
Message
  Topic Search Topic Search  Topic Options Topic Options
jpderuiter View Drop Down
Active User
Active User


Joined: 11 Nov 2013
Location: Eindhoven
Status: Offline
Points: 26 		Post Options Post Options   Thanks (0) Thanks(0)   Quote jpderuiter Quote  Post ReplyReply Direct Link To This Post Posted: 08 Feb 2017 at 12:39am
Hi Chrisa,

OK, thanks for looking into this.
I'll try to chase Cadence, see what they can do.

Best regards,
Jan Pieter
Back to Top
Back to Top
BennsPCB View Drop Down
Advanced User
Advanced User


Joined: 30 Jan 2013
Location: Sweden
Status: Offline
Points: 98 		Post Options Post Options   Thanks (0) Thanks(0)   Quote BennsPCB Quote  Post ReplyReply Direct Link To This Post Posted: 14 Feb 2017 at 3:59am
Hi guys!

We also use decimal-comma instead of decimal-point for regional settings.
This leads to that generating footprints in OrCAD Professional 17.2-2016 S012 from PCB Library Expert v. 2016.14 will NOT work.

As I see it OrCAD can handle regional settings, such as decimal-comma, but PCB LE can not.

We cannot accept this and need a fix instead of workarounds.

Cheers, ...
/Benn
Back to Top
Tom H View Drop Down
Admin Group
Admin Group
Avatar

Joined: 05 Jan 2012
Location: San Diego, CA
Status: Offline
Points: 5717 		Post Options Post Options   Thanks (0) Thanks(0)   Quote Tom H Quote  Post ReplyReply Direct Link To This Post Posted: 14 Feb 2017 at 7:47am

Good news from a Cadence reseller:

I’m just writing to let you know I got feedback on the case I filed to Cadence with respect to this issue and it should get fixed with 17.2s013 – I expect this to be out sometime during the weekend of 18th – 19th of February.


The problem is not Library Expert, it's on the Cadence side and they are fixing their bug.
Stay connected - follow us! X - LinkedIn
Back to Top
BennsPCB View Drop Down
Advanced User
Advanced User


Joined: 30 Jan 2013
Location: Sweden
Status: Offline
Points: 98 		Post Options Post Options   Thanks (0) Thanks(0)   Quote BennsPCB Quote  Post ReplyReply Direct Link To This Post Posted: 15 Feb 2017 at 12:31am
???
... but still the scripts you are generating have decimal point instead of decimal comma, despite of regional settings. When I change the point to comma, the scripts works fine in OrCAD.

/Benn
Back to Top
jpderuiter View Drop Down
Active User
Active User


Joined: 11 Nov 2013
Location: Eindhoven
Status: Offline
Points: 26 		Post Options Post Options   Thanks (0) Thanks(0)   Quote jpderuiter Quote  Post ReplyReply Direct Link To This Post Posted: 15 Feb 2017 at 12:57am
Originally posted by Tom H Tom H wrote:

I’m just writing to let you know I got feedback on the case I filed to Cadence with respect to this issue and it should get fixed with 17.2s013 – I expect this to be out sometime during the weekend of 18th – 19th of February.
Hi Tom, that's great news.
Thanks for chasing this.

I'm wondering how they will 'fix' this, since to me it seems that switching to regional settings was intended by Cadence.
But we'll see.
Originally posted by BennsPCB BennsPCB wrote:

... but still the scripts you are generating have decimal point instead of decimal comma, despite of regional settings. When I change the point to comma, the scripts works fine in OrCAD.
Hi Benn, as Tom said this is really a Cadence issue, not PCB libraries. The decimal point as seperator has always been there, only Cadence changed it recently.
Back to Top
cioma View Drop Down
Advanced User
Advanced User


Joined: 17 Jul 2012
Status: Offline
Points: 149 		Post Options Post Options   Thanks (0) Thanks(0)   Quote cioma Quote  Post ReplyReply Direct Link To This Post Posted: 15 Feb 2017 at 2:29am
Well, generally speaking Benn is right: Library Expert doesn't support regional settings (i.e. point is hardcoded as decimal separator). And once Cadence finally caught up with the world it broke import from Library Expert. So ideally Library Expert needs to be changed to use decimal separator from the regional settings but at least there are workarounds.
Back to Top
jpderuiter View Drop Down
Active User
Active User


Joined: 11 Nov 2013
Location: Eindhoven
Status: Offline
Points: 26 		Post Options Post Options   Thanks (0) Thanks(0)   Quote jpderuiter Quote  Post ReplyReply Direct Link To This Post Posted: 15 Feb 2017 at 3:06am
OK, fair point.
However, then Cadence has to be consistent all over, so not only for the Pad designer script needs to use the regional setting, but also for the Orcad PCB script (which still uses the fixed dot as seperator).
Back to Top
BennsPCB View Drop Down
Advanced User
Advanced User


Joined: 30 Jan 2013
Location: Sweden
Status: Offline
Points: 98 		Post Options Post Options   Thanks (0) Thanks(0)   Quote BennsPCB Quote  Post ReplyReply Direct Link To This Post Posted: 15 Feb 2017 at 4:58am
It seems that OrCAD padstack editor obeys regional settings, but when I changed to decimal comma in all .scr files, the generated footprint was not correct/complete.
It looks that there are still some issues with decimal comma in OrCAD.

Cheers, ...
/Benn
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 (0) Thanks(0)   Quote chrisa_pcb Quote  Post ReplyReply Direct Link To This Post Posted: 15 Feb 2017 at 12:39pm
One of the customers put in a ticket on this a bit ago and received an email that Cadence is working on the comma issue for S013 and that they expect the fix to be available like Feb 18th or 19th.

So we'll see what they come up with before doing anything.
Back to Top
jpderuiter View Drop Down
Active User
Active User


Joined: 11 Nov 2013
Location: Eindhoven
Status: Offline
Points: 26 		Post Options Post Options   Thanks (0) Thanks(0)   Quote jpderuiter Quote  Post ReplyReply Direct Link To This Post Posted: 20 Feb 2017 at 1:36am
Hi all,

I just tried hotfix 17.2s013, and I can confirm that this hotfix fixes this issue.
Apparently they reverted back to fixed dot as decimal seperator.
Back to Top
 Post Reply Post Reply Page  <123>

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.219 seconds.