Package synchronization Eagle/Fusion

[dieter.menne]

I still have problems with package sychronization between EAGLE and Fusion Electronics.

The component to the right has been created with EAGLE, it has a package with Version 9.

I am absolutely sure that the online-library has been recreated - tried many times.

The version in Fusion is 3/5, it has no schematic and no footprint.

I have a different package (CO2SENSOR) which looks ok.

[engineeringNCMXB]

Glad you posted this. I have been struggling with library issues and trying to figure out if it is user error or a bug.
This looks like an early launch bug.

I will see if I can recreate this on my system.

[jorge_garcia]

Hi @dieter.menne,

I hope you're doing well. You haven't pushed the version in EAGLE to the cloud, you have local changes that you haven't pushed. Therefore it's not surprising that the library in Fusion360 is incomplete because it's grabbing whatever is currently available on the cloud.

Let me know if there's anything else I can do for you.

Best Regards,

[engineeringNCMXB · Accepted solution]

@jorge_garciaThis? Create/Push changes to the cloud from EAGLE so that F360 will have access?

[dieter.menne]

I am sure I have over and over again recreated the online library - if you forget this, there will be an * at the devices name printed in bold.

However, there was an update to the program this morning which mentioned that some problems with synchronization have been corrected. I am not yet sure if everything is ok now, but it means that the developers are aware of the problem.

So lets postpone this for a few days until the dust has settled.

[engineeringNCMXB]

A CRITICAL clarification that is not obvious:

You can import a library into Fusion360 but there is NO PATH TO GO BACK TO EAGLE.
If you make or edit a library in Fusion 360 - you cannot pull those changes into Eagle.

Considering the current issues and limitations in Fusion 360 - this effectively means that classic Eagle is the only way to reliably design electronics.

[kb9ydn · Accepted solution]

Or at the very least use the Eagle library manager with managed libraries that can be accessed from Fusion and Eagle.

C|

[dieter.menne]

Could someone confirm what @kb9ydn wrote: Managed is two way? I never see any changes from revisions show up in Fusion.

[engineeringNCMXB]

Two replies up.....
The library sync is not 2-way.
Useless.

[kb9ydn]

---

@dieter.menne wrote:

Could someone confirm what @kb9ydn wrote: Managed is two way? I never see any changes from revisions show up in Fusion.

---

Even after you create the new version on library.io there are a couple more steps to do to get Fusion's designs updated.  First you have to tell Fusion to use the updated version of the library on library.io.  When you open the library manager in Fusion it will scan the managed libraries for updates and show you that updates are available.

After you click the update button Fusion will then use the updated library version for any newly inserted components.  By design, components already in any existing schematics will NOT be updated unless an additional step is performed.  Under the library tab in Fusion, there are two buttons called "Update design from library" and "Update design from all libraries used".  The first allows you to update all components in a schematic that originate from a chosen library.  The second will update all components in a schematic that have updates from all used libraries.

And that should get your schematics updated with the new libraries.  Note that at the moment I have yet to try any of this with PCBs, so it's possible there may be bugs with synchronizing packages and footprints.

C|

[kb9ydn]

---

@engineeringNCMXB wrote:

Two replies up.....
The library sync is not 2-way.
Useless.

---

That is correct.  Technically speaking it is not two way.  In other words you can't edit managed libraries from within Fusion.  At the moment Fusion can only edit libraries stored directly in Fusion, which are not available outside of Fusion.  Managed libraries are edited from Eagle and are available to Eagle AND Fusion.  This is why for now it is better to use managed libraries and not native Fusion libraries.

Whether or not this is useless depends on your needs.

C|

[engineeringNCMXB]

---

@kb9yd wrote:

Whether or not this is useless depends on your needs.

---

What makes it useless to me is that Fusion Electronics is not ready to engage a professional project. Putting any effort into Fusion libraries is merely an exercise for me since I have to do any 'real' work in Eagle.

On that note, I am struggling to figure out how to make use of my typical workflow - design the MCAD and PCB outlines in Fusion. Push the PCB shapes to Eagle and layout the PCB. At the moment, I cannot get a PCB out of Fusion and into Eagle.

It is either broken or obfuscated enough that I cannot see it.

WITH SUCH A WEAK RELEASE OF FUSION ELECTRONICS - THE ORIGINAL/CLASSIC EAGLE NEEDS TO REMAIN TOTALLY UNTOUCHED SO THAT I AM NOT LOSING BUSINESS!!!!

@jorge_garcia
Autodesk - keep the known-good stuff working. Put a tall fence around it and protect the working elements until Fusion gains value for professional work. I have been fiddling all morning trying to get a Fusion designed PCB outline into Eagle. That is not how I wanted to spend my Saturday.

[jorge_garcia]

Hi @engineeringNCMXB,

Other users have reported this issue and that's how we found out that the Fusion to EAGLE workflow is currently broken right now. This is the highest priority fix we are working on now and it is not trivial.

In the meantime you can workaround it by making the PCB in Fusion and then exporting and EAGLE board file from Fusion (File > Export). That EAGLE board file can then be used to bring your complex board shape into EAGLE. I know it's not ideal but it's an unforseen issue and we are trying to resolve it as fast as we can.

Another option is to push from EAGLE first then edit the PCB in Fusion 360 and pull it back. The workflow works if you start from EAGLE first, the problem occurs when you start from Fusion and then try to go back into EAGLE.

We are on it.

Best Regards,