Missing Interval value in the Material Library xml

As an experiment, I opened Lightburn, created a shape and set its cut mode to fill. I then made a new Material library, and used the shape cut mode to create an entry for the library. I then saved the library and opened the xml file in NotePad++, and I do not see an interval entry in the xml. Is this an error? The dialog box for editing the cut does show an interval of 0.1mm. Here’s a listing:

And by the way, I then edited the cut to a slightly different interval value, and the resulting xml now reflects that.

Have I missed something obvious?

Maybe it defaults to 0.10mm and doesn’t bother to write it out if that’s the value…

If you load the original, is there an interval?

:smile_cat:

I believe it does default to 0.1mm, as you suggested. Perfectly fine for my xTool diode laser, which claims an effective laser dot of 0.1mm, I found the issue because I wrote an Excel application which scrapes out all the data in the Material Library, for ease of viewing in Excel. I also wanted to calculate the Watt-secs/mm^2 for all my cuts, to compare things a bit. A Watt-sec is a Joule, I know. For fill cuts I needed that interval number, and discovered they were missing until I edited them from the nominal.

I also confirmed (again) that at least some deleted cut definitions In the library are randomly still in the xml file after literally years since deleting. Can’t imagine why.

I further confirmed that editing the cut back to an interval of 0.1mm causes the original behavior to reoccur (i.e. no reference to interval in the xml file). I haven’t seen this documented anywhere, so I believe it a bug, albeit a minor one. I think no further action is needed on this…

We’ll have to :pray: for more technical help from Lightburn…

Maybe @Rick can supply you with some answers… I don’t know how this is built internally.

:smile_cat:

Thank you for bringing this to our attention. Will investigate further and report back. :slight_smile:

:wave:
I can confirm this is working as intended and is not a bug.
We don’t emit default values because it saves file size. That’s really the only reason.
We’ve added a task to our list to add a “verbose” mode that will always emit all values. It’s something we’ll likely need for some upcoming plans anyways.
At this time though, there’s no way to emit everything to the file, I’m sorry. But if there are specific values you need the defaults for let me know and I’ll provide them.

4 Likes

Adam…No need to make any changes for me, now that I see the reasoning. I only came across it when I sucked the library into Excel so I could calculate the energy flux for my burns (Joules/mm^2), and the beam width was in the denominator of that calculation. Simple enough for me to default it to 0.1 mm in Excel. Same for the number of passes, which defaults to one, of course. Thanks for your quick reply, and thanks, as always, for your contributions to a truly great product. Joy to use…Jack

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.