Layer number change not picked up - causing premature stop

Kreeper · 2018-07-03 10:02:44

What I did:
Change resin profile to have smaller layer numbers.
Regenerate plate due to new settings. (it does not show a message to remind you to do so which I think is a another bug?)
Start print BEFORE it is finished regenerating.

What went wrong:
Print stops on a much earlier plate number as if everything was fine. I think, but cannot be 100% sure, this is the plate number of where it was up to in the regenerate when you started the print.
Note: Plate screen, which had finished regenerating long ago, shows the correct number of plates/images.

Version: 1833 on RPi

Seen this twice now. Did not realize what it was the first time around.

Workaround:

Wait until all plates are generated before printing!

Last edited by Kreeper (2018-07-03 10:09:24)

Shahin · 2018-07-08 05:30:31

You are right, layer count get updated once just after it get created, and once the slicer finish slicing.

I think it is a rare case and should not cause issue for majority of users.

Kreeper · 2018-07-08 08:21:51

It happened to me twice in a few days as I was trialling smaller layer numbers.
Now I think of it, I got another strange bug going the other way. It attempts to load too many images when you move from small to large layer heights. The print process stalls and attempts to reload the next image at that point. I just realised that now.

Also the message tells you explicitly you can "start printing immediately" when you cannot which is doubly confusing for a user who cannot debug it like I could.

I think one of those is a bug that needs fixing?
I think that there will be more than a few people who will have a print sliced for one size and want to move smaller/larger or realise that mistakenly used the wrong sized profile.
Then they will follow the on screen instructions which say "print now" and be left scratching their heads when it fails half way through.

I think I saw someone else talk about it entering a loop halfway through on the forum somewhere - that is what happens when you move from smaller to larger.

What needs to happen is the print job needs to have the final layer total updated once the processing has completed slicing. Currently it just leaves it with the wrong value...

I cannot say for sure but I am pretty sure I have done this process in the past and it did not cause problems. So perhaps this is a new bug? Or maybe I just got lucky and by chance waited each time for it to complete...

Or maybe I just chalked it up to "my print failed to adhere halfway through"?

Anyway you slice it (pun intended) this is an insidious bug...assuming I have it right...

Last edited by Kreeper (2018-07-08 08:31:34)

Shahin · 2018-07-09 06:32:44

Ok will check layer count on start of slicing, will push updated beta version in couple of days.

Kreeper · 2018-07-09 09:09:14

Thanks Shahin.

It might save some support headaches down the road.

elshad66 · 2018-07-09 13:36:01

HI Shahin

The printer is working fine,but sometimes marriage happens
as if one layer does not come
but such a moment
it was noticed by my son when he looked as opens and closes Shutter
and I later also catch these moments
when Shutter opens comes at once image ..but sometimes comes late
through 3,,,5,,7 ...sec .always different
can be at this moment a layer cure time decreases

Shahin · 2018-07-10 20:32:45

I guess it is slow movement on servo. Put shutter mode into once per print or try another servo motor.

elshad66 · 2018-07-10 21:16:05

not servo
Stepper motor connected to the x axis,connected x min/max
,opens without delay ..normaly
but images arrive with a delay ,not always very rarely
sometimes son monitors

Code After Each Layer
G1 X0 F2000
G1 Z{[[LayerPosition]]+[[ZLiftDistance]]} F{[[ZSpeed]]/3-(([[LayerNumber]]<5)*35)} P1 ; Lift to wait position
[[PositionSet [[LayerPosition]]]

Code Before Each Layer
G1 Z[[LayerPosition]] F[[ZSpeed]] P1 ; Move to layer position
G1 X20 F2000
[[PositionSet [[LayerPosition]]]]

Last edited by elshad66 (2018-07-10 21:19:03)

Shahin · 2018-07-11 01:12:22

Could you post dashboard log, debug file after slow down. And indicate which layer you have observed slowdown?

elshad66 · 2018-07-18 11:20:36

Shahin wrote:

Could you post dashboard log, debug file after slow down. And indicate which layer you have observed slowdown?

HI Shahin

I tried to catch, it's very difficult,
you need to sit and watch the whole day

sometimes I have time, and copied post dashboard log
I compared the next layer and the previous layer, they are exactly the same, no difference
the difference in delay is different, approximately 1-3 seconds
it happens chaotically 20,56, 125,,356 ,645 layers
if the delay + cure time(15sec ) is correct,that is normal
if the cure time - delay(15sec-delay ) is no correct,that is no normal
and it too is difficult to catch with a stopwatch
but the quality of printing layers, normal,
thick or thin layers, in support and in the item,I did not notice
I will try to catch and make a video

Last edited by elshad66 (2018-07-18 12:11:23)

Shahin · 2018-07-19 14:51:18

Maybe it is thermal slowdown on CPU. Make sure you have heatsink

nanoDLP

#1 2018-07-03 10:02:44

Layer number change not picked up - causing premature stop

#2 2018-07-08 05:30:31

Re: Layer number change not picked up - causing premature stop

#3 2018-07-08 08:21:51

Re: Layer number change not picked up - causing premature stop

#4 2018-07-09 06:32:44

Re: Layer number change not picked up - causing premature stop

#5 2018-07-09 09:09:14

Re: Layer number change not picked up - causing premature stop

#6 2018-07-09 13:36:01

Re: Layer number change not picked up - causing premature stop

#7 2018-07-10 20:32:45

Re: Layer number change not picked up - causing premature stop

#8 2018-07-10 21:16:05

Re: Layer number change not picked up - causing premature stop

#9 2018-07-11 01:12:22

Re: Layer number change not picked up - causing premature stop

#10 2018-07-18 11:20:36

Re: Layer number change not picked up - causing premature stop

#11 2018-07-19 14:51:18

Re: Layer number change not picked up - causing premature stop

Board footer