Hi!
I was digging quite a lot in Mentor PADS's ASCII stuff in the past. Some lately
introduced "features" are still undocumented but not too difficult to guess.
If somebody needs some help in testing/debugging in that area, please let me
know.
Regards,
Clemens
On 2018-04-19 10:54, Marco Ciamp
On Thu, Apr 19, 2018 at 10:34:24AM +0200, Clemens Koller wrote:
> I strongly belief that Mentor PADS 9.x.y...VX.x.y does _not_ rely on the file
> extension to work correctly.
> However it makes loading of the file more simple as file dialogs ask for
> ".asc" or ".txt".
>
> The header / first lin
I strongly belief that Mentor PADS 9.x.y...VX.x.y does _not_ rely on the file
extension to work correctly.
However it makes loading of the file more simple as file dialogs ask for ".asc"
or ".txt".
The header / first lines look important - i.e.:
Netlist:
!PADS-POWERPCB-V9.0-METRIC! NETLIST FILE
If no one can confirm that other EDA applications require a fixed file
extension to work correctly, I would leave it as is. If there is any
requirement later, we can always tweak it as part of a bug fix release.
Cheers,
Wayne
On 04/18/2018 07:06 PM, Jeff Young wrote:
> If no one else is familia
If no one else is familiar with this either then we can just go with what we
have now.
But I thought I’d ping the dev group one more time in case someone does….
Cheers,
Jeff.
> On 26 Mar 2018, at 01:04, Jeff Young wrote:
>
> The PADS-PCB netlist evidently needs an extension of .asc to be rea
The PADS-PCB netlist evidently needs an extension of .asc to be read
correctly[1].
I implemented a reg-ex which takes the pen-ultimate file extension from the XSL
file and applies it to the output file. So the script for the above-mentioned
netlist exporter is now:
netlist_form_pads-pcb.asc.x
6 matches
Mail list logo