You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I try to adapt this test for the Elegoo Mars. Basically porting it to ChiTuBox Fileformat Version 2.
Looking at the current *.photon files i have few questions. Let's take the 50µm exposure test as example.
Why are the first two layers exposed at the same Z Height? Wouldn't that give you a single layer with twice the exposure time, instead of 2 layers with the set bottom exposure time?
So 0,05mm with 200s instead of 2 x 0,05mm with 100s. Is this intentional?
The next two layers are black. Layer 3 has a Z-Height of 4mm, the next one is at 0,1mm.
Is this to simulate the "peeling" for the bottom layer when the peeling motion is disabled with the GCode? So Move upwards with a set "offTime", then downwards again?
With layer4 we continue to print the real exposure test at 0,1mm basically on top of our 200s exposed base layer.
Is my understanding correct?
(Maybe the V2 test can be done without the GCode hack, as it has separate values for the bottom layers and the normal layers. Haven't tried how the HW behaves when you set for example "Lifting distance" and "Lifting speed" to zero and keep "Bottom Lift distance / speed" set.
The text was updated successfully, but these errors were encountered:
Hi!
I try to adapt this test for the Elegoo Mars. Basically porting it to ChiTuBox Fileformat Version 2.
Looking at the current *.photon files i have few questions. Let's take the 50µm exposure test as example.
So 0,05mm with 200s instead of 2 x 0,05mm with 100s. Is this intentional?
Is this to simulate the "peeling" for the bottom layer when the peeling motion is disabled with the GCode? So Move upwards with a set "offTime", then downwards again?
Is my understanding correct?
(Maybe the V2 test can be done without the GCode hack, as it has separate values for the bottom layers and the normal layers. Haven't tried how the HW behaves when you set for example "Lifting distance" and "Lifting speed" to zero and keep "Bottom Lift distance / speed" set.
The text was updated successfully, but these errors were encountered: