Export DXF with fill for ShapeString

[Lerche]

Hi!

I've been googling my head of and looking thorugh this forum for an answer.

I've designed a 2D drawing, with text(ShapeString), and several other paths, created from sketches, but also from drafts.
The draft is no issue, everything work as expected.

When I export as DXF using legacy exporter (using the new exporter, the exported file is not recognized by the online lasercutting/engraving service, as well as other services[online DXF file viewers]), I only get the lines from shapestring, no fillcolor, so no possibility to raster-engrave this area.
Anyone has a workaround?

I have tried upgrading the shapestring through draft without luck.

Am I misunderstanding the DXF format, so the DXF is not possible to create "flat colored areas"?

Thanks in advance.

DATA:
OS: Windows 10 Version 2009
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.24291 (Git)
Build type: Release
Branch: releases/FreeCAD-0-19
Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
Python version: 3.8.6+
Qt version: 5.15.2
Coin version: 4.0.1
OCC version: 7.5.0
Locale: Danish/Denmark (da_DK)

[Roy_043]

The DXF format supports solid hatch patterns, but the FreeCAD DXF exporter does not create them.

As a workaround you might try using Draft_Hatch. Note that this results in linework when exported to DXF, and I do not know how a lasercutter would distinguish the hatch pattern from the outline that needs to be cut.

If your lasercutting service accepts SVG then that would be an option.

[Lerche]

I tried the Hatch, but only after updating to 0.20.

Now the Draft Layer is breaking the DXF export. File not recognized by cutter service (or other online DXF file viewers).
I removed the layes and export the whole thing by clicked each draft, text, everything. Works (still with no fill color for the shapestring).
Afterwards I setup layers again, now the DXF is not recognized.

Data:
OS: Windows 10 Version 2009
Word size of FreeCAD: 64-bit
Version: 0.20.29177 (Git)
Build type: Release
Branch: releases/FreeCAD-0-20
Hash: 68e337670e227889217652ddac593c93b5e8dc94
Python 3.8.10, Qt 5.15.2, Coin 4.0.1, Vtk 8.2.0, OCC 7.6.2
Locale: Danish/Denmark (da_DK)
Installed mods:
* 3D_Printing_Tools
* Assembly4
* dxf-library
* fcgear
* kicadStepUpMod 10.11.9
* Manipulator

[thomas-neemann]

...

can you upload the fcstd and dxf file somewhere?

[Lerche]

Sure thing - I just created and checked these: https://we.tl/t-KvRuJFH8mL

Simple files, but they perform just the others I work with.

[thomas-neemann]

...

when i open the file without layers in librecad, layers are shown.

Bildschirmfoto_2022-08-19_13-14-37.png (46.46 KiB) Viewed 957 times

[Lerche]

They are placed within the layers structure, and I just tried exporting by having both cut and raster highlighted, this works.

So highlighing only the "Layers" structure will not export correctly, as it does in ver 0.19.

So far so good - Do you have any idea of hos to infill the text in the DXF? I have tried all advises here, nothing works.

Thanks!

[thomas-neemann]

... Do you have any idea of hos to infill the text in the DXF? I have tried all advises here, nothing works.

...

as far as i know dxf only contains lines, arcs, splines and points. the iges format can transfer faces

[Roy_043]

I have tried all advises here, nothing works.

As already explained, using a hatch works fine. See attached files.

[catman]

When I export as DXF using legacy exporter (using the new exporter, the exported file is not recognized by the online lasercutting/engraving service, as well as other services[online DXF file viewers]), I only get the lines from shapestring, no fillcolor, so no possibility to raster-engrave this area.
Anyone has a workaround?

Some years I had a similar problem with a machine that would not accept the exported FreeCAD DXF. My workaround was to import it into Corel Draw and export it from there again as DFX 2007. This file could be read by the software. Maybe exporing SVG and then convert it to DXF is also a workaround. In find that Inkscape can be used very well to inspect the file and clean up any errors, e.g. multiple generated lines.