for a PCB Assy: INSERT>SHARED DATA>FROM FILE - EMN file. Check INVESTIGATE PLACEMENT. The comparison tool should check only movement out of tolerance - not ANY change in distance.
When exporting an EMN file, the EMN shows the component distances from the origin to 5 decimal places of a mil.
When using an EMN file from the PCB software it only goes to 2 decimal places.
Example - for a sample dimension (in mils)
When doing the COMPARE GEOMETRY feature in ProE, it checks to see if there is even the smallest change and it flags it as an error. This is going to be VERY common due to rounding errors when going back and forth. The comparison should not flag an error for any discrepancies that are smaller than the standard number of decimal places of the part. We have set 3 decimal places. If the difference is .0001, it should not flag it as an error. Otherwise, we need a config option for this. We can't leave it like this - no one wants to compare the EMN files this way.
We are getting a lot of errors and users don't want to use this functionality. We have no way of controlling or fixing this roundoff issue/error.
This happens because:
1. A Mechanical Engineer inserts a component using design intent, and not based on the origin of the component
2. When the Mechanical Engineer exports the EMN, it exports 5 decimal places of a mil from the origin of the board to the origin of the component. Since this distance wasn't a driving factor for placement, it doesn't have to be a perfect distance to the mil. It can go past 3 decimal places.
3. The PCB Engineer imports the EMN file.
4. They work on the board and export it back out as another EMN file.
5. The Mechanical then has to review the EMN file to ensure there were no unintentional changes made. This new EMN file doesn't export to the same number of decimal places as ProE. When comparing Geometry, it flags these items as a CHANGE even though their movement is miniscule and irrelevant.