Demonstration: Detect and Solve Electromechanical Design Problems with Creo View ECAD

Designing electromechanical products is challenging, as it requires the carefully coordinated efforts of electrical and mechanical design teams. Problems often result from poor or lack of communication of required design changes between disparate electrical and mechanical design systems.

The problem traditionally has been that the design data is held in separate systems, ECAD and MCAD systems. It’s akin to trying to communicate in two completely different languages. In order to collaborate effectively, the data needs to be visualized and inspected in a form familiar to users of both systems.

Creo View ECAD provides comprehensive capabilities for viewing, interrogating, detecting, and marking up electronic designs, including PCB layout, schematic, and related mechanical assemblies.

Users can quickly view and analyze ECAD information — view components, trace signals, measure critical parameters – resulting in faster design reviews and increased product quality.

Mark Caradonna, Product Manager at PTC, demonstrates how Creo View ECAD and Creo View MCAD together can help solve real world design problems and provide intelligent access to all PCB design data without requiring ECAD or CAD systems.

This entry was posted in What's in Creo 2.0 and tagged , , , , , , , . Bookmark the permalink. Trackbacks are closed, but you can post a comment.

Post a Comment

Your email is never published nor shared. Required fields are marked *

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s

You may use these HTML tags and attributes: <a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <pre> <q cite=""> <strike> <strong>