{"id":17918,"date":"2017-08-16T08:00:24","date_gmt":"2017-08-16T15:00:24","guid":{"rendered":"http:\/\/www.autodesk.com\/products\/eagle\/blog\/?p=1454"},"modified":"2023-09-25T12:21:47","modified_gmt":"2023-09-25T19:21:47","slug":"fusion-360-integration-eagle","status":"publish","type":"post","link":"https:\/\/www.autodesk.com\/products\/fusion-360\/blog\/fusion-360-integration-eagle\/","title":{"rendered":"Fusion 360 Integration with EAGLE How-To"},"content":{"rendered":"

How to Use the New Fusion 360 Interoperability in Autodesk EAGLE 8.3<\/h1>\n\n\n

We\u2019ve all been there, whether you\u2019re working for a giant company with thousands of engineers, or just a handful, you\u2019ll always encounter the same ECAD\/MCAD collaboration<\/a> problems. Know what we\u2019re talking about? That endless cycle of sending project files through email, or tracking changes through spreadsheets. Or maybe you\u2019ve hacked together your own version control system. But at the end of the day, it\u2019s all the same struggle. The fight to work together as electrical and mechanical engineers. So where does the solution to this process-driven problem begin? In our tools. With the release of Autodesk EAGLE 8.3, it\u2019s time to bring ECAD and MCAD together, with Fusion 360 Interoperability.<\/span><\/p>\n\n\n

ECAD\/MCAD Problems of Today<\/h2>\n\n\n

Regardless of what tools you happen to be using for your design process, the underlying problems with ECAD\/MCAD collaboration are the same. It doesn’t matter what kind of file formats you\u2019re trying to juggle; the root issue is all about the data<\/span><\/a>. Why the data? Because we don’t have tools that communicate with one another because they don\u2019t have a common foundation of data. And so of course, it\u2019s a natural byproduct that <\/span>you need to rely on exchange file formats<\/span><\/a> like STEP, IDF, IGES, etc.\u2026 to play the middleman.<\/span><\/p>\n\n\n\n

But over at Autodesk, we took a look at this problem differently. While we could have made a better file format, we realized a more sustainable and long-term solution is to simply get your design tools talking to one another, directly. This is what Fusion 360 Interoperability in Autodesk EAGLE 8.3 is all about.<\/span><\/p>\n\n\n\n

Need to streamline your electrical and mechanical design workflows together?<\/span><\/p>\n\n\n\n

Yes! This is exactly what you need. With this feature, there aren\u2019t any files being exchanged, just an underlying set of data and communication channels that bring ECAD and MCAD together. How does it work?<\/span><\/p>\n\n\n\n