Community
EAGLE Forum
Welcome to Autodeskโ€™s EAGLE Forums. Share your knowledge, ask questions, and explore popular EAGLE topics.
cancel
Showing results forย 
Showย ย onlyย  | Search instead forย 
Did you mean:ย 

Issues when moving to F360

5 REPLIES 5
Reply
Message 1 of 6
mleikvoll
409 Views, 5 Replies

Issues when moving to F360

mleikvoll
Explorer
Explorer

First, do I still call "electronic designs" in F360 for an "Eagle" design? Autodesk appears to want to get rid of the Eagle name, since I see little/nothing of it in F360, but it is not clear to me how to search for help without using "eagle" as key. Using "electronic design" as a keyword will massively pollute my search, and using F360 will give me a lot of irrelevant hits. Please guide.

 

Second, I imported my rather complex Eagle design into F360, and because it is rather big, there is a massive wait (1min 20sec) for F360 to fill the polygons every time I open the design. Apparently there is no manual fill any more. (May I suggest Autodesk internally tesselate all polygons before working on them live?). A side effect of this is that any changes to my vias will add big waits for polygons to auto update. Can I get back the old manual fill way?

 

Third, my polygon fills now leaves a few airwires even if it filled completely on Eagle7.7. Clearly it is no longer 100% compatible. One reason seems to be because via's center point now need to be embedded into the polygon fill to count as included. I guess thats a fair deal. Another more serious reasons seems to be linked to F360 imporing my 0-width cutout polygons wrong. See attached images from Eagle 7.7 vs F360 (current release). Clearly the opening that I made for my artificial thermals are different. Yet I can not understand how that could happen. Did it use something else from a different library?

 

Forth, there is a few homemade features that I cant live without that I can no longer have, since there is no user-context menu anymore. Stuff like

-locating a device in the sch or brd, by simply rightclicking it in sch and choose "locate in brd", and vice versa.

-In board, right click a signal and choose "hide layer"

-In board, right click a signal and choose "display all affected layers"

-plus a few more useful, but less important ones

Can I get those in a near future version?

๐Ÿ˜Š

 

0 Likes

Issues when moving to F360

First, do I still call "electronic designs" in F360 for an "Eagle" design? Autodesk appears to want to get rid of the Eagle name, since I see little/nothing of it in F360, but it is not clear to me how to search for help without using "eagle" as key. Using "electronic design" as a keyword will massively pollute my search, and using F360 will give me a lot of irrelevant hits. Please guide.

 

Second, I imported my rather complex Eagle design into F360, and because it is rather big, there is a massive wait (1min 20sec) for F360 to fill the polygons every time I open the design. Apparently there is no manual fill any more. (May I suggest Autodesk internally tesselate all polygons before working on them live?). A side effect of this is that any changes to my vias will add big waits for polygons to auto update. Can I get back the old manual fill way?

 

Third, my polygon fills now leaves a few airwires even if it filled completely on Eagle7.7. Clearly it is no longer 100% compatible. One reason seems to be because via's center point now need to be embedded into the polygon fill to count as included. I guess thats a fair deal. Another more serious reasons seems to be linked to F360 imporing my 0-width cutout polygons wrong. See attached images from Eagle 7.7 vs F360 (current release). Clearly the opening that I made for my artificial thermals are different. Yet I can not understand how that could happen. Did it use something else from a different library?

 

Forth, there is a few homemade features that I cant live without that I can no longer have, since there is no user-context menu anymore. Stuff like

-locating a device in the sch or brd, by simply rightclicking it in sch and choose "locate in brd", and vice versa.

-In board, right click a signal and choose "hide layer"

-In board, right click a signal and choose "display all affected layers"

-plus a few more useful, but less important ones

Can I get those in a near future version?

๐Ÿ˜Š

 

5 REPLIES 5
Message 2 of 6
grahamUTKMN
in reply to: mleikvoll

grahamUTKMN
Advocate
Advocate

Hi,

 

I'm sorry I can't help you, but I'd like to know more about your home made features as they sound really useful!

 

-locating a device in the sch or brd, by simply rightclicking it in sch and choose "locate in brd", and vice versa.

-In board, right click a signal and choose "hide layer"

-In board, right click a signal and choose "display all affected layers"

 

Thanks,

 

G

0 Likes

Hi,

 

I'm sorry I can't help you, but I'd like to know more about your home made features as they sound really useful!

 

-locating a device in the sch or brd, by simply rightclicking it in sch and choose "locate in brd", and vice versa.

-In board, right click a signal and choose "hide layer"

-In board, right click a signal and choose "display all affected layers"

 

Thanks,

 

G

Message 3 of 6
mleikvoll
in reply to: grahamUTKMN

mleikvoll
Explorer
Explorer

You can find my old tool (MLutils.ulp) in old archives, like here

 

https://raw.githubusercontent.com/loneFunction/Library/master/ULP/GLOBAL/MLutils.ulp

 

Please try it on an old Eagle7.7 installation.

 

0 Likes

You can find my old tool (MLutils.ulp) in old archives, like here

 

https://raw.githubusercontent.com/loneFunction/Library/master/ULP/GLOBAL/MLutils.ulp

 

Please try it on an old Eagle7.7 installation.

 

Tags (1)
Message 4 of 6
jorge_garcia
in reply to: mleikvoll

jorge_garcia
Autodesk
Autodesk

Hi @mleikvoll ,

 

Is that you Morton? If it is, it's nice to hear from. You can hide the polygon fill so it won't take so long, under the polygon menu in the design section you'll see the option to hide all polygon pour fills.

 

In regards to custom shortcuts and menus that is something we want to restore. We are looking for ways to do this so stay tuned.

 

In regards to the polygons, the implementation in Fusion 360 is different than the one in EAGLE. The outlines come in with some thickness. You can edit the part in the library and redo the cutout. It's a one time effort.

 

Thanks for the feedback.

 

Best Regards,



โ€‹Jorge Garcia
โ€‹Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
0 Likes

Hi @mleikvoll ,

 

Is that you Morton? If it is, it's nice to hear from. You can hide the polygon fill so it won't take so long, under the polygon menu in the design section you'll see the option to hide all polygon pour fills.

 

In regards to custom shortcuts and menus that is something we want to restore. We are looking for ways to do this so stay tuned.

 

In regards to the polygons, the implementation in Fusion 360 is different than the one in EAGLE. The outlines come in with some thickness. You can edit the part in the library and redo the cutout. It's a one time effort.

 

Thanks for the feedback.

 

Best Regards,



โ€‹Jorge Garcia
โ€‹Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
Message 5 of 6
mleikvoll
in reply to: jorge_garcia

mleikvoll
Explorer
Explorer

Hi Jorge, yes that's me ๐Ÿ˜Š I figured I should have a more friendly username, so I changed it now.

We needed F360 here at work for 3d drawings, so I figured I could give "Eagle" (or whatever I should call it, you didnt answer that question ๐Ÿ˜‰) another try.

 

Regarding polygon fill and delays, turning off the visibility did have a good impact on load speed. It came as a surprise that turning it off actually took a long time to execute. Turning it on will be like old ratsnest, wich I expected to take a long time. It is also nice to see that I can ratsnest single nets's polygons to check how it fills, but it was unexpectedly slow when I first tried it. It appears like if polygons are all filled, then hidden, single net ratsnest seems to process even the hidden polygon fills, altho not showing them. When first loading the board without the fills, the single net ratsnest i fast. Maybe you can get that issue fixed.

 

Bringing back user context menu will be very nice, but how about just adding these functions to standard builtin features? They are very useful and rather easy to code.

 

When it comes to polygon edge vs pour, Eagle used "wire width" for both. Under no curcumstances I can imagine how this got converted wrong for my library part. Wire width should not affect this specific case. This must be a bug? I also notice that my original polygon arc cutout got converted into wire segments, and F360 doesnt support arcs. Maybe that is where the bug happened?

 

A few more issues:

  • I want to see the name of the nets I rightclick. The "info" popup is sometimes very slow to appear and its not placed in the context where it should be. In Eagle, it was always visible in the status line. Can I get the signal name at top of the context menu so I clearly can see what got rightclicked?
  • When F360 has a modal property window open, clicking the main F360 window does not bring it to front. This causes some GUI challenges, where F360 and the small property window is stuck behind other windows (like my browser). You have to go to the windows taskbar to get it into front, or hide the window you put in front. I think this is a quick fix to change so that clicking the main F360 window will bring it to front even when modal requesters are open.
  • When I open a footprint, nothing seems tells me what it is that I got open. Im trying to add 3d packages to my library and get very confused.

 

 

0 Likes

Hi Jorge, yes that's me ๐Ÿ˜Š I figured I should have a more friendly username, so I changed it now.

We needed F360 here at work for 3d drawings, so I figured I could give "Eagle" (or whatever I should call it, you didnt answer that question ๐Ÿ˜‰) another try.

 

Regarding polygon fill and delays, turning off the visibility did have a good impact on load speed. It came as a surprise that turning it off actually took a long time to execute. Turning it on will be like old ratsnest, wich I expected to take a long time. It is also nice to see that I can ratsnest single nets's polygons to check how it fills, but it was unexpectedly slow when I first tried it. It appears like if polygons are all filled, then hidden, single net ratsnest seems to process even the hidden polygon fills, altho not showing them. When first loading the board without the fills, the single net ratsnest i fast. Maybe you can get that issue fixed.

 

Bringing back user context menu will be very nice, but how about just adding these functions to standard builtin features? They are very useful and rather easy to code.

 

When it comes to polygon edge vs pour, Eagle used "wire width" for both. Under no curcumstances I can imagine how this got converted wrong for my library part. Wire width should not affect this specific case. This must be a bug? I also notice that my original polygon arc cutout got converted into wire segments, and F360 doesnt support arcs. Maybe that is where the bug happened?

 

A few more issues:

  • I want to see the name of the nets I rightclick. The "info" popup is sometimes very slow to appear and its not placed in the context where it should be. In Eagle, it was always visible in the status line. Can I get the signal name at top of the context menu so I clearly can see what got rightclicked?
  • When F360 has a modal property window open, clicking the main F360 window does not bring it to front. This causes some GUI challenges, where F360 and the small property window is stuck behind other windows (like my browser). You have to go to the windows taskbar to get it into front, or hide the window you put in front. I think this is a quick fix to change so that clicking the main F360 window will bring it to front even when modal requesters are open.
  • When I open a footprint, nothing seems tells me what it is that I got open. Im trying to add 3d packages to my library and get very confused.

 

 

Message 6 of 6
jorge_garcia
in reply to: mleikvoll

jorge_garcia
Autodesk
Autodesk

Hi @mleikvoll ,

 

Within Fusion, we are calling it Fusion 360 Electronics. As time goes on it going to change so much that it won't look like EAGLE anymore, under the hood, the bones, are EAGLE.

 

We are looking to implement the more popular ULP functions natively but like everything it just has to be prioritized.

 

The library stuff, is one of our big priorities for the year so expect to see that continue to be developed.

 

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

 

Best Regards,



โ€‹Jorge Garcia
โ€‹Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
0 Likes

Hi @mleikvoll ,

 

Within Fusion, we are calling it Fusion 360 Electronics. As time goes on it going to change so much that it won't look like EAGLE anymore, under the hood, the bones, are EAGLE.

 

We are looking to implement the more popular ULP functions natively but like everything it just has to be prioritized.

 

The library stuff, is one of our big priorities for the year so expect to see that continue to be developed.

 

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

 

Best Regards,



โ€‹Jorge Garcia
โ€‹Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report