[Report] QIDI 6.08 Mono is 50% compatible with per layer settings

[human890209]

Hi,
My printer is QIDI 6.08 Mono with original firmware V4.3.11_LCDKM / 1620 x 2560 / F2.21.

I tested the per-layer settings with the script example and some manual changes.
The ExposureTime and LightOffDelay work.

I found some differences:

1. When the layer's LiftHeight is set to 0mm, the firmware uses the General Properties' LiftHeight value. If General Properties's Lift Height value is set to 0, the firmware uses a built-in height value of 6~10mm
   Maybe the walkaround is setting the layer's LiftHeight to 0.001mm manually.
2. Layer Index offset
   Layer1 uses Layer2's LiftHeight value. Layer2 uses Layer3's. Layer3 uses Layer4's...
   I don't know the offset number is constant 1 or the bottom layer count. Maybe I could modify the per-layer script sample to make a simple shift script.

Is there a way to install a generic chitu firmware(>= version 4.3.9) to my QIDI 6.08 Mono to get it 100% compatible?

[sn4k3]

It seens like QIDI have ctb v3 firmware compatible.

1. CTB and others can never use 0mm lift height or it will grab defaults, that's why UVtools set a lift height of 0.1mm by default
   

2. I'm not sure what you mean, it must respect it own layer value and dont look one up...

3. Not a clue if you can install generic firmware, it requires someone to try to know if possible, but i will not risk it. Your firmware is already ctbv3 compatible

I will add that printer to the list
Thanks

[human890209]

I'm confused about the v3 ctb and v4 ctb file format.
My Chitubox slicer 1.9.0 basic outputs x.ctb files not x.v4.ctb files. It's ctbSlicerFile.HeaderSettings.Version is 4 and contains ctbSlicerFile.PrintParametersV4Settings.
What is the v4.ctb file format?

[sn4k3]

.v4.ctb is just a virtual extension i put on UVtools to force convert any file to V4. By default UVtools uses v3 to convert. But when loading it will just load whatever version the file contains.
Please read changelog to know what is happening

[human890209]

1. If I use SaveAs to create a new ctb file, the ctb version is the same as the original file I opened, all data is saved, right?
2. If I open a V2/V3 ctb file and use ConvertTo Chitubox CTBV4, it will override the Version Property to 4, override the EncryptMode to the right value, and add PrintParametersV4Settings data to let the V4 firmware printer print as a version converter, right?

Is changelog the one on the release page? I read that and get confused, and worried I don't save the ctb files in the right version.

[sn4k3]

1. Yes, SaveAs will keep original thing but with other name, but note that if a file need a full encode, if you name it xxx.v4.ctb it will force Version 4 because it will go with Encode method which does that check. If is a soft-save nothing is changed.
2. Correct. And from that on you can open it as normal .ctb on UVtools and it will be handled as v4. When loading files we ALWAYS have the version information so we don't need the virtual extension trick. But when creating files we have no way to user inform which version he want, so that virtual extension does the trick.

Explore code is the best way to understand what is happening: https://github.com/sn4k3/UVtools/blob/master/UVtools.Core/FileFormats/ChituboxFile.cs#L1710

[human890209]

Thanks!