You are not logged in.
Unfortunately automated brightness change is not possible as it integrated on the slicer not on viewer. So every time you change brightness everything must calculated again.
It could be moved to run time section so before viewing image brightness get applied to the layer. But it will affect performance of viewing layers which is not something we want.
But you know if the picture is out of focus for projector you can get big solid piece (larger than expected) or nothing at all.
Some of the mask usage countering focus problem for projectors. Your suggestion could be useful for LCD users.
Looks like recent version of nanodlp for windows has issue. I am trying to fix it, please use it old version until I find what is wrong with windows version.
You are using RAMPS so you need to tweak firmware and gcode boxes on nanodlp. It is nothing to do with nanodlp itself everything being handled on RAMPS side you just need to keep position correct on nanodlp side too.
Try latest version, if you have enough space on SD card, system would not crash
Do you count on changing size of pillars to measure light intensity? Do you think it is linear correlation between two?
Have you tried latest version?
I have checked out difference since version was working and only things changed on gl module are mouse disabled on new version and go compiler upgrade. I can push versions without these features to see if it makes it work or not.
Thank you.
You need to expand SD card.
I did not get the point. How they will know how much they should input for the individual point?
I have checked out code, for a long time there were no major change to windows build. Mentioned error is not important.
Could you upload version which works fine with your computer?, so I could check out which build is it.
Done
Probably a new bug on a browser. What is it firefox or chrome? and which version?
Please, try the latest beta version.
Could you provide a screenshot?
Reason to have different height for burn-in layers is to handle possible issues with floor calibration and PDMS. It is intended behavior to have same height as normal layers. It is easy to handle slice in different heights, but would not possible to handle floor calibration issues this way.
I am not sure what you want to achieve by having different values.
About the low quality layers, it could speed up process during support area by skipping some layers.
Could you let me know previous version which worked fine? If you do not remember version, how old it was 2 3 months or older?
It is extremely slow connection, will try to change timeout to see if it makes any difference.
All RAMPS related distro, should works well with touchscreen interface.
I can change it but it is major change. I am not sure if anybody prefer current usage.
Generic version relay on rpi gpio to make movements instead of sending commands RAMPS.
I have not seen your wiring but it quite possible you are getting too much amp out of rpi. Blinking also indicate so. Checkout red LED if it is not stable you have power issue.
1) You should check out functionality on touchscreen side, there is route on nanodlp to trigger shutdown but I am not sure if it is supported by software you are using for touch interface.
2) It could be power supply issue, you need atleast 3 4A power supply for rpi.
Could you let me know how much it takes to get this error?
Usually timeout should kicks in when upload process stalls for defined duration. So even if upload takes couple of minutes it is fine as long as upload does not get stalled.
On profile, infill section
Other boxes are dimmed, are they create any issue during measurement?
Whatever you put in front of projector keyword will be sent to your projector so it should support any command