Im working on a Fusion360 post processor to make SVG files for +Scorchworks K40

Lasers
,
1

Im working on a Fusion360 post processor to make SVG files for +Scorchworks K40 Whisperer.

For some reason K40 Whisperer draws the contours of my SVG file black and will not cut them. If I load the SVG file in Inkscape and resave it the contours come out red in K40 Whisperer. What am I missing?

This is an postprocessor output sample:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2

There are many idiosyncrasies in SVG files that I am still learning about. This file shows one of them. K40 Whisperer looks for the line color in a “style” inside of the path definition. This SVG file does not put the color inside of a “style” so K40 Whisperer is not seeing it.

K40 Whisperer will get better with SVG files over time.

For now, opening a new Inkscape document and importing the SVG will solve 99% of the incompatibilities. (I only of one oddball that requires changing the line color after it is imported into Inkscape.)

3

Can you show an example line on how you expect the style property to look? I can probably generate it in the Fusion360 post.

4

Here your SVG is with two quadrants working (one red one blue). I also had to add an “id” value which is just a unique identifier for each path.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
5

That worked fine when implemented in Fusion360 post.
Do you use the “id=” property for something?
I tried without it and tried with the same id for all segments and that seemed to be accepted also.

6

When I used the same id for two of them they both ended up the same color even though one was red and one was blue. The last color overrides all of the other colors if the id values are all the same. so if you are only interested in red it will not be a problem to use the same id value for all of them.

7

Thanks for the clarification. I just implemented a running unique id= to be safe.