nanoDLP

Hi Shahin,

In looking at this further, will entering the code to the custom buttons be acceptable?  It seems like the supported functions list does not have [[Projector xxxx On]] etc.  It seems it would only be the actual On/Off sections supported, and not for brightness up/down.  Thanks!

So I continue to face some issues getting custom buttons set up for some of the commands. 
User 1
Brightness (Up/Down)
Contrast (Up/Down)
Brilliant Color (On/Off)
Brilliance (in advanced range of 1-10)

Here's a screenshot of what I have tried. I'm sure it's the syntax or something simple, any ideas are welcome!

In the first image is the custom button section...

The second image is attempting to input manually through the terminal.  I have tried various designations, but I am not a coder so I am probably off.  The last input in white entry box appears to be accepted, but nothing happens - this code is to turn projector off. This code is the input from the text box for projector off button, it works from the button input but not direct. I was hoping to use this code to determine that my gcode is correct to the printer and would be an easy way for me to know if the command works. Testing the other codes like tilt in this manner work fine.

Please help,

Signed Perplexed on Printing...

https://imgur.com/a/4mqE2

https://imgur.com/a/ah4x9

Hi Shahin,

following on this post.  I'm trying to see that the command has been accepted by the projector for birghtness/contrast/color temp etc.  I have mounted the projector to the wall, and can view through the menu remote.  Have the commands for say brightness 10%, 30%, 50% been integrated to the nano?  I'm hoping to add a gcode on the resin screen that will set the birghtness and contrast for that profile before plating.  And I am attempting to test these via terminal if that matters. Thanks!

Hi Shahin,

I am working on this project again and have had very good success with small artifacts.  I am working on the selective motions and peel moves for the slices again.  Here is what I am trying to accomplish:
1. first 5 layers are burn layers, I would like the ability to customize the heights, currently in the resin profile I am setting these to 0 um, and program them within the defore print.
2. the remaining layers, I only want to move to a new layer height for the first normal layer.  After that I would like to have the deck remain at the same height
3. After the final print, the platform should move to wait position and tilt for ~20 sec.  (this is working fine)

In the gcode for the resin profiles I have the following:

M650 D{([[LayerNumber]]<6)*1+([[LayerNumber]]>5)*([[LayerNumber]]<7)*1} S1
;(Should do peel for layer 1-5 at S=1, S=2 for layer 6, no peel after that)
M651;(If D==0 no peel move right?)
G90
G1 Z{([[LayerNumber]]<6)*0.1+([[LayerNumber]]>5)*([[LayerNumber]]<7)*0.4}
G91
[[WaitForDoneMessage]]
[[PositionSet{[[LayerPosition]]+([[LayerNumber]]<6)*([[LayerNumber]]*0.1+([[LayerNumber]]>5)*([[LayerNumber]]<7)*[[LayerNumber]]*0.4}]]

So a few issues:
In your message above what does the % do?
I have tried to do conditional statements like G0 Z{[[LayerNumber]]==5)*0.5} but it didn't seem to work.  I think i'm too much a newbie at the gcode - or any code for that matter - please let me know where i am going wrong or if there is a reference I can find some info on programming  (py or gcode).  I have seen the repositories on line.

Thanks for all the help this machine is incredible!

Hi Shahin,
I'm also having issues with the beta version saving - but only on the mask upload page.  I double checked on firefox and chrome to make sure it wasn't just the browser not updating. 

Thanks!

Elliot

Hi Shahin,

Thanks for the answers.  I do have a question though, I select the printer profile which has the layer heights and peel moves built in.  So I add your suggested codes to the custom g-codes in the printer profiles section, or do I wait for compile and somehow access the gcode for the plate?  I'm mildly familiar w/ g-code and can work through this in the code section - but if there was an easier way to add a macro that's great too.

Thanks!

Elliot

Questions:

1. So in the above, am I adding the slides individually or from a .zip in order?
2. Do I do this through the plate generator, and how do I add additional plates to the generator - if it's more than one I am going to put them in one folder with a number ie: 0001.xx 0002.xx correct?

Thanks!

Hi Shahin,

This is something very similar to what I would like to ask for a feature request.

In my work I am using the nanoDLP and mUVe to develop some very small features - the pixel sizes are about 10 um, artifacts at 20-30um.  I would like to know if there is a way I can have the nanoDLP display layers without a move or peel between each.  I want to do the three final layers of my current project without moving the stage/elevator at all.  There are three separate artifacts which are close to one another and may be interfering b/c of light bleed through (clear resin). 

It should look something like this:
layer (n-x/n) all do the peel move and lift sequence)
layer (n-3/n) display the layer, no peel or lift
layer (n-2)/n) same as above
layer (n-1/n) same as above
...

In this way something large like a 1mm wall could be printed - and something small like a 20um pillar could be printed on the same layer.  I'm currently having issues with this.

I'm hoping that there is an easy way for me to generate plates based on the above generator...Thanks for all this incredible work!!
Elliot

Hi Larry-
I tried to find the sensor you used on Amazon or spark fun but th pictures don't match up to what you have accomplished.  Did you remove the sensor from the board to place it in the cone?  How was this accomplished?  Thanks!

Thanks!

And I think it would be useful to integrate a newly created mask to an upload already on the disc - that way it can be added to the original file and that file doesn't need to be altered every new mask.  I would think new masks need to be created each time a major resolution change is done.  I use several.  I hope there are more who can comment if this is useful for them too.

E

Right- So on the band pass- this is why I was going for the smoothest curve over the range.  (I'll post some of the spectrum tomorrow or next week - getting late here!)  My thoughts were if it was a stable line and equal between 390 and 405 - then I don't need a band pass.

So I think what's happening is contrast plays against brightness - to a point - and then one can supercede the other if it's a large difference - like 10% vs 90%.  I believe the greyscale is contrast/brightness - but maybe someone else can chime in here.

Thanks Larry-

Re: band pass- Would that work, I had thought of that.  But if the sensor cuts off at 390 it still doesn't register above that value...correct? 

Re: Stl I'll post shortly

Re:Brightness

So what I found is that with higher brightness settings in the viewsonic, even with high contrast, the bleed-out overcomes the contrast...black is not black anymore.  So high brightness affects other areas.  So what I'm trying to do is find the sweet-spot that allows reasonable curing times while having very good control over light transfer to other areas you don't want cured.  We have to assume that the light is being refracted as it enters through the glass and then the resin.  I'm starting to work with some lenses that allow better collimation of the beam without dispersion.  So if we get the filters on the viewsonic right, and have basically the highest tolerable UV band when black is black.  That's the sweet spot.  Then Start with brightness (lamp intensity) around 20-40% we should be closer to having a normalized projection.  Maybe I'm not understanding how the greyscale is being done...is this basically a contrast setting customized for different areas of the Ti chip?

Thanks!

Elliot