You are not logged in.
Do you still experience the same issue after slicing gets completed?
the layer half shade was a mask issue as you mentioned, i tested the ascii & bin, but still lacking the mesh area information
The "halfshade" was mask issue, strange why its was activated, maybe accidently...i solved spherical distortions physically lens set, it was not required feature before, but some way i resolve to check anyway... thankyou
But the main issue still happening, the missing layering information inisde (Toggle Details) which we use to plan the strategy on formula box.
I export tha same stl both in ascii and bin versions, the same result.other files was test with slc too same results....
It could be a mask issue. Remove it see if rendering become normal
mask is turned-off
may i send wetransfer link?
yes
all parts ( even with AA turned off) (bright-255) are reurning in half shade slices... its being an issue for me, and sensitive enough to 25µ pixel size, making dynamic cure not that eficiently
i have tried(stl binary,slc) upload again, with no success.
it seems that formula is being calculated, but theres no info from layers section
even if i disable the AA, the output image is retuning an halfshade on every parts with quads area
Hi,
when im upload a stl or SLC file(new plates after update only), no information is displayed on "[ Toggle Details ] "???
@jcarletto27 @shahin @backXslash,
have you ever tried Gaussian Distribution formula? im trying to print parts which contains very small super tiny dots with large areas at a same slice... i think it will only be possible if we could separate( as discussed before) cure defined by [[LargestArea]] or [[SmallestArea]] to achieave a double pattern exposition, to obtain a fairly great control of individual features, what do you think about it? i'm wondering to run plates in parallels....:)
it will be fancy
this crashs happens when you get print fire?
Scipy library could handle diferential equations with the avaliable [[variables]] as inputs?
preview tab would be a layering strategy page
yes for shure, i think its a great ideia inside a preview page, we always need to open a separate tab to define the strategy layers , its clever to integrate it inside preview page.
group layers would be trickier too, as we have burn-in and normal layers we also would have add-sectors incremently added on demand just as plates.
Put formula inside { } to see the result instead of replaced values. I have added a note for this one on the latest build.
Would be possible to add a resource to verify the math error in the formula page? like a button that verify like a dry run to see whats returning, printing?
I would like to not start printing until theres no printing error and explorate maths possibilities befere fire it.
due to the fact when you have resin on tank you start print and it could fail at some level, than you have to remove the resin, filter...
its a straight delicate for me, becouse im research materials and i formulate small quantities like 1g 2g samples, so this math tool should be my companion in lab
I see on trello board that is aimed to prevent print failure, i consider to place some attention inside (F)ormula window
A lot of people that would be using nanodlp in future may have lacks in math and it would become time consuming to concatenate when you re working with nano as a research development tool.
when i use [[AverageArea]] its not working, result prints me the same formula upside.
them i change to something else like [[TotalSolidArea]] and result prints me the time in seconds (that works)
Hi i trying to use Cure Calc excel tool but every input print me errors
return :
Math issue ((4<6)*15)+(1*(8,5869*(2,71828182845905**([[AverageArea]]/(-250))))<0,3)*0,3+(1*(8,5869*(2,71828182845905**([[AverageArea]]/(-250))))>0,299)*(1*(8,5869*(2,71828182845905**([[AverageArea]]/(-250)))))
-1 Invalid token ‘[’
Whats wrong with excel sheet?
Hello fellows,
For shure,
Currently my setup is running with direct drive ( Applied Motion STR8 driver ), on early versions i had experiencing some cogging effect, maybe influenced for step emulation ( 20.000 steps / rev) which affect some velocity issues, them i had to stepdown this emulation and change velocities.
today i updated to Build 1537 and turn the drive to max emulation (20000steps/rev) and its running flowsly.
just to ensure i measure it with digital dial 0,001mm
one more time i would like to thank you for the impeccable work and to enable us to drive our machines with this greatest tool!
I have found an issue. Please, upgrade and let me know if it fix the issue.
Issue Fixed !
thank you very much!
there's no movement, reboot the babe, the log says its done with routine put physicaly nothing changes,
I just come to lab ( did not turned the machine down) and see on trello board that you havve update pre -calculated pulse length so i just update it,
then the "buildhead" stay parked on 6mm waiting position, after update its showing on calib. page that its currently on 0000000 position but its not, so no movement was done after upgrade
Direct control with Rasp + applied motion driver
printer.mem
2017-06-03 07:39:15.808 {"Layer":"2","module":"Hardware","level":"Notice","msg":"Initializing build # 1465 - generic"}
2017-06-03 07:39:15.857748 {"Layer":"2","module":"Hardware","level":"Debug","msg":"Stepper motor enabled"}
2017-06-03 07:39:15.858013 {"Layer":"2","module":"Shutter","level":"Debug","msg":"Shutter Close"}
2017-06-03 07:39:15.858048 {"Layer":"2","module":"Pulsing","level":"Debug","msg":"Moving to top"}
2017-06-03 07:39:15.858199 {"Layer":"2","module":"Terminal","level":"Notice","msg":"Terminal Reader Activated"}
2017-06-03 07:39:15.858307 {"Layer":"2","module":"Pulsing","level":"Debug","msg":"Moving Up 100000000 pulses 100000 mm"}
2017-06-03 07:39:15.858453 {"Layer":"2","module":"GPIO","level":"Notice","msg":"Limit has been touched"}
2017-06-03 07:39:15.858615 {"Layer":"2","module":"Pulsing","level":"Warning","msg":"Limit touched position reset"}
2017-06-03 07:39:15.858768 {"Layer":"2","module":"Pulsing","level":"Debug","msg":"Movement Finished Pulse 0 / 100000000 ; Height 6000 / 0 ; Time 0.000310098"}
2017-06-03 07:39:15.858848 {"Layer":"2","module":"Pulsing","level":"Debug","msg":"Moving to Stop Position"}
2017-06-03 07:39:15.858932 {"Layer":"2","module":"Pulsing","level":"Debug","msg":"Moving Down 6000 pulses 6 mm"}
2017-06-03 07:39:16.010105 {"Layer":"2","module":"WIFI","level":"Warning","msg":"WIFI interface wlan0 detected"}
2017-06-03 07:39:16.022457 {"Layer":"2","module":"WiFi","level":"Debug","msg":"Status Monitoring"}
2017-06-03 07:39:16.078338 {"Layer":"2","module":"WIFI","level":"Warning","msg":"Connecting to FFff0987"}
2017-06-03 07:39:19.030341 {"Layer":"2","module":"Pulsing","level":"Debug","msg":"Movement Finished Pulse 6000 / 6000 ; Height 0 / 6000 ; Time 3.171171042"}
2017-06-03 07:39:26.023126 {"Layer":"2","module":"WiFi","level":"Debug","msg":"Connected to FFff0987"}
z axis won't move after update
is 2.718 a jacob's constant?
yes,
my nano was suffering from near-death experiences,
so rebuild everything and then update to 1448. now its working ok thanks