Valor Trilogy 5000/Vsure's Netlist Analyzer Often Failed on Metric-unit ODB++ Databse Output From Expeditionpcb. I have logged this issue on the supportnet(
SR #23908840). The issue is in Expeditonpcb side or in Valor side? I guess it's a resolution issue. We also use ODB++ inside for Allegro, and the metric-unit odb++ data can be analyzed by Trilogy 5000. I don't like hear an anwser just like" you can output imperial-unit odb++". We are standarderized on the metric system and world all have been migrated or migrating metric system. Antother issue is Expeditionpcb always output gerber data with Self-Intersection-Polygons and make Valor Trilogy 5000/Vsue wrongly rasterization.
Now, Valor is a part of Mentor SDD, How to Perfrom to build?