11/14/2023 0 Comments Import dxf librecad![]() There are and have been non trivial issues regarding interoperability between Autodesk and non Autodesk programs with those formats. The interoperability issues between native Autodesk dwg and dxf aren't specific to F360. ) that's an issue.īeing able to work with lowest common denominator, non Autodesk dwg and dxf files is a must. As you have also found it's the interaction between non Autodesk native apps (for example the rest of the world. What I have exported as an STL or directly to Simplify 3D works quite well. That's been my experience as well though I don't export 2D drawings from F360 so I can't comment on that. I think what he's saying is that between the traditional Autodesk desktop applications the data interchange works as expected. I haven't used Inventor regularly in a couple of years but some ipt files I made at Techshop imported into F360 nicely. In my experience importing formats dxf and dwg directly from an Autodesk product largely works as expected. When I have files that read as expected in everything but F360, I don't consider that a file issue but rather the way F360 deals with those files. While it's gotten better, there is still work to do. I just kudoed one on the front page that explained issues with coincident points that are hidden and not able to be extruded. There are several posts over the last couple of years that document some of the issues F360 has with importing/working with dxf files. It's not a practical real world solution to require what is basically a several thousand dollar translations solution particularly considering that in most if not all of my cases the culprit is F360 and not the other programs. ) As you say the workaround is to put it into Autocad prior to Fusion and that seems to work all the time. It worked great.I can't think of a single instance (there may have been a few) in the several files I've had that had issues in F360 that didn't work as expected in a variety of other tools including Draftsight, Solidworks, Corel, Illustrator, Inkscape, Autocad, Freecad, Flow Path, Torchmate, Sheetcam and V-Carve. The version of gschem I am using, 1.8.2, allows scaling the image prior to instantiation by dragging the opposite corner, as well as rescaling the instantiated image, by dragging a corner. Note to the LCAD devs: It might be a good thing to look into the gschem image import code. It looks like I can continue to use LCAD for drawings not needing an image import, while continuing to use gschem for drawings I need to import an image for. That is why I wanted to use LCAD for this process. To that end, I wanted to use the PCB image output for the base LCAD drawing in order to keep the accuracy and not re-draw the image.Īfter posting my message, I ended up importing my image into the gEDA gschem schematic capture program, which has limited mechanical drawing capabilities. The whole idea of CAD/EDA is to make the processes easier and less error-prone. To maintain two scales of the same object in PCB is not acceptable. I cannot scale the original PCB drawing, since it is obvious it must be the size of the circuit board in the real world. ![]() It looked very coarse, but still the large size. I did try reducing the PCB PPI option, with the results you warn about. As I said, I even tried importing the PNG file into Inkscape and converting to a DXF file, as the LCAD manual suggests, with the fatal crash results in LCAD when I tried to import it. I had tried several adjustments to the PCB PNG output parameters, such as changing the Pixels Per inch (PPI) option, with virtually the same results in LCAD. It was generated from the gEDA PCB printed circuit board editor as a PNG file. Alas, I don't think I can change the scale of the original image. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |