You are not logged in.
Last edited by lenne0815 (2017-06-29 16:42:18)
Offline
Looks awesome!
Offline
Thanks Shahin ! would be a bit easier if you let me pull "BaseLayerAmount" from the input box, but works like this aswell.
Offline
We could have IsBurninLayer (0 or 1), or you think BurninLayers<4 could be more flexible?
Offline
No, that would be just fine ! i think fiddling with burn in layers would be complicated and not really nessecary On a side note, i just realised you added dynamic acceleration aswell, how would i go about testing it ? And we have values for individual cure areas, i didnt realise that, man you are on fire !
Offline
Dynamic acceleration is only available for direct control. RAMPS control acceleration as I know we could not modify it from nanodlp side.
I have added IsBurninLayer to the beta version.
As I know only few people working on complex dynamic formulas. Will be happy to help anytime.
Offline
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 ?
Offline
So i tried the [[IsBurnInLayer]] Variable but it doesnt seem to retunr anything and in the calculator preview i cant put in values to test it ? ( 1553 )
Last edited by lenne0815 (2017-06-30 17:53:26)
Offline
Only pulses get generated on nanodlp side and currently it is far from quality of one generated by arduino. so keep using RAMPS.
Use IsBurninLayer and not IsBurnInLayer
Offline
Tried that aswell, doesnt work either Pulses would be enough if we could still use the Ramps for the rest ?
Last edited by lenne0815 (2017-06-30 19:16:48)
Offline
Are you sure you have upgraded to the latest beta? Do you see keyword in on-screen help?
I have tried it and it working fine.
Offline
Yes i see the keyword in the help section but the descriptions are missing a line aswell, im on 1553, upgraded via (wget http://www.nanodlp.com/nanodlp.beta.tar.gz? -O - | tar -C /home/pi -xz);cd /home/pi/printer;sudo ./setup.sh
Offline
I have rebuilt and push it online again.
Example:
[[IsBurninLayer]]*10+10 (10s cure time for normal layers and 20s for burn-in layers)
Offline
Now setup recons it cant update because im already on the latest version, can i force it somehow ?
Last edited by lenne0815 (2017-06-30 20:20:43)
Offline
use command line interface
Offline
I just googled an hour how to do that but failed, im a total newb when it comes to linux unfortunately
Offline
Sorry, use simple installation process for nanodlp. It will force upgrade.
Also I have pushed couple of bugfix so right now, you can upgrade through program itself too,
Offline
very nice !
Thanks lenne0815.
Offline
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.
Last edited by lenne0815 (2017-07-01 20:19:49)
Offline
It was probably memory usage issue.
{ ([[IsBurninLayer]])*35 + ([[IsBurninLayer]]==0) * ( 45 + 70 / ( 1 + ( 2.718** -( 2 - ( 0.008*[[TotalSolidArea]]) + 2)))) }
Offline
I tried == initially but couldnt get it to work because i couldnt preview it, will do it that way, much more elegant !
The resubmit bug has been plaguing me for quite some time now so im unsure if its memory related, it happens no matter what is slicing at the time ( small or big models ) as soon as i resubmit a second plate or even resubmit the same plate while still slicing the pi stops calculating until i reboot it.
Offline
I could not reproduce the issue. My guess is files are large enough to crash Pi version. Whenever it crashes please share debug file so I could know what have caused the issue.
Offline
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.
Last edited by lenne0815 (2017-07-02 21:40:40)
Offline
would we use some ceil or float before * in equation, could releaf "brain stress" for pi deal with movements?
i think the float numbers would not affect so much when dealing with velocity, in case you working with direct control with dynamic speeds , velocities could influence in rounding errors depending of the driver capabilities. as direct control may have been coded with pulse train, do you think it could improve anyway?
Offline
is it possible to handle [[Slowsection]] in dynamic speed?
Offline