Library Expert PADS PCB ASCII Versus CADint ASCII

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi,

I am using Library Expert Pro 2014 PADS PCB to generate ASCII for CADint 4.40

I have discovered that I am getting parsing errors when importing to CADint.

I have done some testing with Library Expert Lite 2017. I created a PADS PCB 2007 ASCII
file for both PADS PCB and CADint with the following results

PADSPCB.asc
I get "error parsing file line --> 29" when I import to Cadint
line 1    !PADS-POWERPCB-V2007.0-BASIC! DESIGN DATABASE ASCII FILE 1.0
line 29  OPEN 2 0.12 26 -1

Cadint.asc
I can import without errors
line 1    !PADS-POWERPCB-V2007.0-BASIC! DESIGN DATABASE ASCII FILE 1.0
line 29  OPEN 2 180000 26 -1

Note that the format is different as indicated in line
PADS-POWERPCB-V2007.0-METRIC  versus  PADS_POWERPCB-V2007.0-BASIC
Also note how line 29 is different.

Of course the solution to my problem is to upgrade to Library Expert Pro 2017,
however, I am curious as to why there is the difference in output and also why
I am unable to select the Cadint format when targeting PadsPCB

Comments greatly appreciated and thanks for a great tool.

Best regards,
Noel Diviney.

PADS-POWERPCB-V2007.0-METRIC   versus  PADS-POWERPCB-V2007.0-BASIC

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
divner Members Profile Send Private Message Find Members Posts Add to Buddy List New User Joined: 15 Nov 2012 Location: Melbourne Austr Status: Offline Points: 3	Post Options Post Reply Quote divner Report Post Thanks(0) Quote Reply Topic: Library Expert PADS PCB ASCII Versus CADint ASCII Posted: 25 Jan 2017 at 4:50pm
	Hi, I am using Library Expert Pro 2014 PADS PCB to generate ASCII for CADint 4.40 I have discovered that I am getting parsing errors when importing to CADint. I have done some testing with Library Expert Lite 2017. I created a PADS PCB 2007 ASCII file for both PADS PCB and CADint with the following results PADSPCB.asc I get "error parsing file line --> 29" when I import to Cadint line 1 !PADS-POWERPCB-V2007.0-BASIC! DESIGN DATABASE ASCII FILE 1.0 line 29 OPEN 2 0.12 26 -1 Cadint.asc I can import without errors line 1 !PADS-POWERPCB-V2007.0-BASIC! DESIGN DATABASE ASCII FILE 1.0 line 29 OPEN 2 180000 26 -1 Note that the format is different as indicated in line PADS-POWERPCB-V2007.0-METRIC versus PADS_POWERPCB-V2007.0-BASIC Also note how line 29 is different. Of course the solution to my problem is to upgrade to Library Expert Pro 2017, however, I am curious as to why there is the difference in output and also why I am unable to select the Cadint format when targeting PadsPCB Comments greatly appreciated and thanks for a great tool. Best regards, Noel Diviney. PADS-POWERPCB-V2007.0-METRIC versus PADS-POWERPCB-V2007.0-BASIC



chrisa_pcb Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 29 Jul 2012 Location: San Diego Status: Offline Points: 772	Post Options Post Reply Quote chrisa_pcb Report Post Thanks(0) Quote Reply Posted: 25 Jan 2017 at 5:08pm
	If I recall, CADInt requires a very specific form of PADS ASCII that was relevant at the time that it was written. So as such, it needs to be in basic units and v2007 in order to parse properly. Your line there.. .12mm is the line width for the piece which has 2 points(a line). The Basic Unit equivalent of that being 180000 basic units. So its saying the same thing, just in different unit types, and CADInt doesn't read metric. Whoever wrote that parser probably just looked for whole numbers and when it saw a period threw the error. Simply a constraint of their importer, which is why our specific CADInt generator should put out files in BASIC units.

divner Members Profile Send Private Message Find Members Posts Add to Buddy List New User Joined: 15 Nov 2012 Location: Melbourne Austr Status: Offline Points: 3	Post Options Post Reply Quote divner Report Post Thanks(0) Quote Reply Posted: 25 Jan 2017 at 6:54pm
	Thanks for the explanation. I will upgrade to Pro in due course. Regards Noel Diviney