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?
๐
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?
๐
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
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
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.
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.
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,
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,
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:
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:
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,
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,
Can't find what you're looking for? Ask the community or share your knowledge.