[PCB_FORUM] Re: IDF Data Exchange

To All,
 
Randy Rix from Intel wrote me directly:
*********************************************
Tony, 
Good job figuring it out.  One other thing; you said: 
"IDF File "Electrical Component Section" - Record 2 field 2 issue with
Allegro: 
It appears that allegro 15-5.1 is using a part number attribute to
populate this field but in the event that the part number field is blank
or the attribute does not exist then the software fails to generate the
proper syntax by leaving the field blank. The 14.2 version of Allegro
seems to have completely ignored this attribute and simply populated the
device name in this field. I was able to manually update my IDF files by
placing data in this field and it works. So, I have a manual work around
now but it is a pain to manually edit the files. "
FYI, instead of manually updating the IDF files, you could try setting
the following user preference and see if that helps:
Setup->User Preferences->IDF->idf_ignore_part_number
*********************************
 
Turns out that this was a great idea - thanks Randy. In fact Allegro
version 14.2 does not have an IDF Category in the User Preferences and
its default is to use the device type. However, in Allegro 15-5.1 it
does have an IDF Category that includes the idf_ignore_part_number
setting and others. If set the idf output will ignore the component
definition part number property and instead export the component
definition device type. I set this user preference and the resultant IDF
output indeed populated Record 2 field 2 of the electrical component
section with the device type just as it did in Allegro 14.2.
 
Question:
Why did they not leave the default the same as it was before? If you
want the newly available part number data to appear in the IDF output
then you should have to set an attribute such as
idf_include_part_number. Changing the original default setting can
really throw you off and then users waist time, as I did, trying to
figure out why something does not work anymore from one version to
another. 
 
Do we still have a bug?
Well, in my opinion YES! If the default is to include the part number in
record 2 field 2 of the Electrical Component Section then the software
should ensure that this field is not left blank. Cadence could fill this
in with anything (as long as it is not blank) or send the user an error
message letting them know that this field is blank. Even a warning would
work but simply writing out an invalid IDF file does not seem like
something that should be acceptable so I will be contacting Cadence this
morning.
 
Thanks to everyone for your support,
Tony Cosentino
Tekelec
919-460-3656 office
919-414-2083 cell
tony.cosentino@xxxxxxxxxxx
www.tekelec.com
 
________________________________

From: icu-pcb-forum-bounce@xxxxxxxxxxxxx
[mailto:icu-pcb-forum-bounce@xxxxxxxxxxxxx] On Behalf Of J Wages
Sent: Wednesday, June 13, 2007 5:52 PM
To: icu-pcb-forum@xxxxxxxxxxxxx
Subject: [PCB_FORUM] Re: IDF Data Exchange



Thanx Tony. 

I know I will be using the IDF interface in the near future. I have not
used it recently (currently using DXF), but will keep your notation on
file. I have a funny feeling that I will need it.

Thanx again

Jim

 

Jim S. Wages / SR. PCB Layout Designer:  

Cary, NC - H: 919-466-1596 Cell: 919-484-2963

 

-----Original Message-----
From: icu-pcb-forum-bounce@xxxxxxxxxxxxx
[mailto:icu-pcb-forum-bounce@xxxxxxxxxxxxx] On Behalf Of Cosentino, Tony
Sent: Wednesday, June 13, 2007 4:49 PM
To: icu-pcb-forum@xxxxxxxxxxxxx
Cc: Cosentino, Tony
Subject: [PCB_FORUM] Re: IDF Data Exchange

 

To All,

 

Setting the stage:

We are using Cadence Allegro version 15-5.1-43DD and Pro-E (PTC)
Wildfire 2

We have created two IDF files out of Allegro 15-5.1. The first is IDF
version 3.0 file and the second is IDF version 2.0 file. 

 

Problem:

Neither of these files will read into PTC's Wildfire 2. However, if I
create an IDF file out of Allegro 14.2 it reads without error into
Wildfire 2. For reference, the IDF output of Allegro 14.2 is version
2.0. 

 

First step in solving this problem:

We called PTC and they told us that the IDF data (both versions 2.0 &
3.0) from Allegro 15-5.1 was corrupt and this is the reason it will not
read into Wildfire 2. Corrupt, meaning the files do not follow the
required IDF formats. 

 

Second step in solving this problem:

I polled the user community and received several ideas (Thanks). After
reviewing the IDF files and the IDF specifications I found differences
in Electrical Components Section between Allegro's outputs for 14.2 and
15-5.1. 

 

Allegro's 14.2 output always placed the symbol name in record 2 field 1,
placed the device name (if one exists but if one does not exist then it
adds "") in record 2 field, placed the units in record 2 field 3 and
placed the height information in record 2 field 4. *See the Electrical
Component Section below*

 

Allegro's 15-5.1 output always places the symbol name in record 2 field
1, randomly places different attributes in record 2 field 2 (and
occasionally leaves this field empty which actually causes the failure
when reading the data into Wildfire - more comments will be posted
below), always places the units in record 2 field 3 and always places
the height information in record 2 field 4.

 

Next step in fixing the problem:

I will report this IDF syntax error to Cadence and indicate that leaving
record 2 field 2 blank causes errors. Additionally, leaving this field
blank does not meet the syntax required by the IDF specifications
version 2.0 or 3.0.

 

Electrical Component Section

Record 1 = Field, Description Type Value

1. Section keyword string = .ELECTRICAL

Record 2 = Field, Description Type Value

1. Geometry name string = Any

2. Part number string = Any

3. Units definition string = MM or THOU

4. Component height float = Any

 

IDF File "Electrical Component Section" - Record 2 field 2 issue with
Allegro:

It appears that allegro 15-5.1 is using a part number attribute to
populate this field but in the event that the part number field is blank
or the attribute does not exist then the software fails to generate the
proper syntax by leaving the field blank. The 14.2 version of Allegro
seems to have completely ignored this attribute and simply populated the
device name in this field. I was able to manually update my IDF files by
placing data in this field and it works. So, I have a manual work around
now but it is a pain to manually edit the files. 

 

It is completely possible that even newer versions of Allegro still have
this error but because a company may be using the tool differently it
may not be failing. Allegro is possibly populating this field with and
actual part number or some other value that it finds. In our case it
seems we end up with at least one part on every board where the field
ends up blank and the IDF files will not load. 

 

This syntax error needs to be fixed by Cadence so that a blank never
appears in this field or any other required field. Next stop Cadence.

 

Thanks for listening,

Tony Cosentino

Tekelec

919-460-3656 office

919-414-2083 cell

tony.cosentino@xxxxxxxxxxx <mailto:tony.cosentino@xxxxxxxxxxx> 

 

________________________________

From: icu-pcb-forum-bounce@xxxxxxxxxxxxx
[mailto:icu-pcb-forum-bounce@xxxxxxxxxxxxx] On Behalf Of Cosentino, Tony
Sent: Wednesday, June 13, 2007 2:21 PM
To: Peter Cerbone (pcerbone); icu-pcb-forum@xxxxxxxxxxxxx
Subject: [PCB_FORUM] Re: IDF Data Exchange

Peter, 

 

The message back reads:

Failed - Errors in imported data.

The log file also indicates what line of the emn file caused the error
and I am currently looking at this specific entry but have not come to
any conclusions yet.

 

Thanks

Tony

 

________________________________

From: Peter Cerbone (pcerbone) [mailto:pcerbone@xxxxxxxxx] 
Sent: Wednesday, June 13, 2007 1:35 PM
To: icu-pcb-forum@xxxxxxxxxxxxx
Cc: Cosentino, Tony; Peter Cerbone (pcerbone)
Subject: RE: [PCB_FORUM] IDF Data Exchange

Hey Tony,

 

What does the error message say?

 

We are presently using Allegro 15.5.1 & 15.7 and PTC's Wildfire 2..

 

Peter

 

________________________________

From: icu-pcb-forum-bounce@xxxxxxxxxxxxx
[mailto:icu-pcb-forum-bounce@xxxxxxxxxxxxx] On Behalf Of Cosentino, Tony
Sent: Wednesday, June 13, 2007 1:12 PM
To: icu-pcb-forum@xxxxxxxxxxxxx
Cc: Cosentino, Tony
Subject: [PCB_FORUM] IDF Data Exchange

To All,

 

Setting the stage:

We are using Cadence Allegro version 15-5.1-43DD and Pro-E (PTC)
Wildfire 2

We have created two IDF files out of Allegro 15-5.1. The first is IDF
version 3.0 file and the second is IDF version 2.0 file. 

 

Problem:

Neither of these files will read into PTC's Wildfire 2. However, if I
create an IDF file out of Allegro 14.2 it reads without error into
Wildfire 2. For reference, the IDF output of Allegro 14.2 is version
2.0. 

 

First step in solving this problem:

We called PTC and they told us that the IDF data (both versions 2.0 &
3.0) from Allegro 15-5.1 was corrupt and this is the reason it will not
read into Wildfire 2. 

 

Questions:

Has anyone out there experienced an issue with the IDF data from Allegro
version 15-5.1?  

Is anyone using Pro-E Wildfire 2? If so, are you reading in IDF data
formats?

Has anyone out there experienced an issue with loading IDF data into
Wildfire 2?

 

Next step in solving the problem:

I plan on talking with Cadence if I do not get feedback from this group.

 

Thanks in advance for your support,

Tony Cosentino

Tekelec

919-460-3656 office

919-414-2083 cell

tony.cosentino@xxxxxxxxxxx

 

 

We're Building Tomorrow's Smart Networks Today <http://www.tekelec.com/>


 

Tony Cosentino
PCB Design Engineer 

5200 Paramount Parkway
Morrisville, NC 27560
<http://maps.yahoo.com/py/maps.py?Pyt=Tmap&addr=5200+Paramount+Parkway&c
sz=Morrisville%2C+NC+27560&country=us>  

Tony.Cosentino@xxxxxxxxxxx <mailto:Tony.Cosentino@xxxxxxxxxxx> 
www.tekelec.com <http://www.tekelec.com/> 
AIM: 

tel: 
fax: 
mobile: 
Skype ID:
SkypeIn #:

919-460-3656  
<http://www.plaxo.com/click_to_call?src=jj_signature&To=919-460-3656&Ema
il=TCGJ4@xxxxxxx> 
919-466-3031
919-414-2083  
<http://www.plaxo.com/click_to_call?src=jj_signature&To=919-414-2083&Ema
il=TCGJ4@xxxxxxx> 

 

Add me to your address book...
<https://www.plaxo.com/add_me?u=30065719686&v0=1892503&k0=936198173> 

Want a signature like this? <http://www.plaxo.com/signature>

GIF image

GIF image

Other related posts: