nanoDLP

True, didnt think of that, i obviously have an M106 in there before. Thanks !

? this is the whole point of the script and besides the error when it falls below 1 it works fine ( Atleast as far as i can tell )

Maybe this is a misunderstanding

Could you find out what happens to the "wait before print for the base layers or should i add it to the dynamic cure box ?

The speed difference should be exactly the other way around as calculated by my script, for the large layers is should only add feedrates of about F1 to F2 to the basic F35

Check this; at 1000 Total solid area it should give out a value close to 0

https://www.google.de/search?q=(100%2F( … x)%2B2))))

Shahin, big problem !

I dont know if this is exactly the problem but i think once [[TotalSolidArea]] reaches 1000 the speed calculation completely tilts, i used this:

{([[IsBurninLayer]])*35 + ([[IsBurninLayer]]==0)*(110/(1+(2.718**-(2-(0.008*[[TotalSolidArea]])+2))))}

For dynamic speed which worked fine for a small part but now ive ran a bigger part and everything over 1000mm2 gets calculated at F500 ( should be around 1,9 ) which in turn means F2000 for retracts so my printer luckily just tilted on the retract movements and nothing happend

This definitely didnt happen before so i think there must be an error in the recent additions.

actually your more right than i was ( I forgot the up and down movement ) but its only 8mm because a rounding error is 50% worst case.

But it still stands; it would only work with direct driving the stepper with a stepper driver on full step settings which causes all kinds of problems ( https://www.youtube.com/watch?v=dmk6zIkj7WM ) reducing the overall accuracy to just 0,015 for my example.

Im not even sure how the stepper driver themselves handle these inaccuracies, i would guess they "remember" unsolvable pulses with microstepping and add / substract them on the next possible movement.

If driven by a ramps i would guess that the ramps takes over this function and only sends out possible movements, queuing unsolvable movements and executing them the next time possible.

No matter how you look at it trying to get pulses and movement distances in sync via nanoDLP seems like a complete waste of time, switching over to a 0,9° stepper and a 2mm pitch screw alone would drive worst case error accumulation down to 0,62mm for 8k slices in comparison to 8mm shrink with a low shrink ( 2% ) resin.

Your link is broken.

Confirmed working ! This actually explains a lot of problems i had in the past, i never checked it thoroughly so i didnt realise it wasnt working and i was just unable to get it dialed in,now that it works i already shaved of another 5 minutes of one of my 45min testprints with it Thank you very much for the quick fix Shahin !

( i think especially the new details section helps a lot with figuring out dynamic lifts / speeds, again thank you very much for your work ! )

Upgrade to 1556 and give it a try, it should atleast do something. I dont have a D7 so you need to dial it in by yourself, it works very similar to the dynamic lift speed for which i already made a lengthy explanation.

One more thing, maybe its specific to my setup but auto populating the name of a new plate by filename stopped working.

I reinstalled nanoDLP twice and the layer calculation is still a bit erratic but while doing so another problem reared its head;

Dynamic lift height ( which i get with [[ZLiftDistance]] ) only calculates full values not the decimals, if i change ([[IsBurninLayer]])*3.5 to 4 5 6 etc it works, decimals ( like my calculation ) dont get calculated.

An example of a dynamic lift script:

{ ([[IsBurninLayer]])*3.5 + ([[IsBurninLayer]]==0) * (1 / ( 0.7 + ( 2.718**-(0.02*[[LargestArea]] - 3))) +1.7 ) }

It does start working correctly when i put it directly in the Gcode after each layer box though:

M107
G1 Z{[[LayerPosition]]+([[IsBurninLayer]])*3 + ([[IsBurninLayer]]==0) * (1 / ( 0.7 + ( 2.718**-(0.02*[[LargestArea]] - 3))) +1.7 ) } F[[ZSpeed]] P1
[[WaitForDoneMessage]]
[[PositionSet [[LayerPosition]]]]

returns the proper z height values.

Holy eff, what a mission I got it figured out though:

{ ([[IsBurninLayer]])*35 + (abs([[IsBurninLayer]]-1)) * ( 45 + 70 / ( 1 + ( 2.718** -( 2 - ( 0.008*[[TotalSolidArea]]) + 2)))) }

I needed to invert the isburnin layer values and the calculation preview is still not working for IsBurninlayer but for testing i just exchanged it to a different call so i could figure out how to make it work.

While testing another "bug" became apparent, if you resubmit a plate before it has been finished nanoDLP becomes unresponsive and the pi needs to be rebooted.

Now setup recons it cant update because im already on the latest version, can i force it somehow ?

Tried that aswell, doesnt work either Pulses would be enough if we could still use the Ramps for the rest ?

Julien Delnatte is still working on his UV Led daugtherboard for the Pi, as soon as he makes it available il change over to direct control ! How do you drive the stepper directly ?