You are not logged in.
here is an image I made up quickly to show the general idea...the supports are the red parts of course...
These happen to have two branches but really one would be fine having more might be nice but just putting down
another support would be no big deal and would keep things simple.
I know this might have been done other ways ... spool could have been printed in a different orientation etc but sometimes that is just not possible.
By the way : just started using BETA 1415....I see all sorts of new features we have discussed..awesome.
I would like to request a new support type...It works similar to bridge support but I would like to use created support using a cone/sphere and body
but be able to specify two points (maybe more would be nice) the first point is the same as how a typical non bridge support works and specifies
the location of the penetration point on the model...the second would specify where the body will bend at a 90 degree angle
so that the body will then be drawn to the build plate...additional points bend would on occasion be helpful getting tricky places
I think...however I haven't run into that myself yet....I notice some automated support generators create this type of structure.
There are several other ways I can think to do this but this seemed like the simplest within the current support system.
My basic desire here is to have supports that can stand out away from the model so as to avoid intersecting the model.
EDIT: I have found I can do some of this using a BASIC support and some bridge supports but it seems to require some special
cases on the model like it have overhead parts near the offset area that needs support..and bridge supports have to be somewhat
uniform so a cone shaped detachment is not possible if a heavier support is needed maybe due to the angle require...I still
think my original idea would be helpful and easier to use in more situations.
I know this might be a tricky thing to do given how nanoDLP seems to function.
But I would surely like to be able to go back to a plate that almost worked but for lack of a support here or there
and edit the support structure...
I know alot of people rely on automated support generation but I have yet to find a program that does a great job (suggestions welcome)
Therefore I find I almost always add supports manually inside nanoDLP...however I sometime miss one or put one in a location
that poses a problem I didn't see before printing...the way the system seems to work now I must create a new plate
and manually replace all the supports, this is can be painful when all I need is to add a simple support somewhere.
I imagine I could maybe download the plate stl and maybe add it back as a new plate but that doesn't work when wanting
to move ore remove a support.
I have been doing a lot of variations to find a resin profile that will work with a current project that required both fine gaps and heavy lines.
I would now like to to see a way to lock a plate or at least a resin profile so that without explicitly unlocking first it can't be modified.
This might obviously be in the resin profiles list however ideally I think it would be nice to lock all the details of a plate.
Once I get the details sorted out I would like to lock the plate and the profile together so that nothing about it can be changed
without explicitly performing some two step confirmation type process.
My use case here is after I do a lot of work to get a plate just so, that will print successfully and look good I want to lock it down
so that I can't accidentally change some detail (like the resin profile or some other printer detail) that might prevent it from
printing exactly the same way next time.
So far the only browser I can can seem to add custom supports for are chrome derivatives.
I would be nice if FireFox or Safari could work too...as other things that work in say firefox like the log viewer don't always
work in chrome...(iOS)
Even in chrome once I leave the browser and come back the custom supports are gone...maybe that is the intended operation
but I have a few I used alot that I would like to keep.
Next this is sort of a feature add but leaving support to move to a different view usually means my support disappears even when
returning to the support view...maybe that is a bug / browser issue too.
Also is there a way to add or removed support once a place is created with out total recreation?
Finally this is a feature add for sure but having a hide show support check box would help placing support.
Often I find the support hides the model in an area where I want to add another support. I have found a work around
by using very thin supports with now base then using the unify base at the end so they actually stick but even that
the support column can often hide something.
Lastly I find (due to the issue of portrait vs landscape viewing) that I can't get to the bottom of some models there needs
to be a scroll bar if the model extends past the bottom of the browser window...maybe again a browser issue.
nanoDLP is a great tool but difficulties in the browser interface make it hard to use.
Thanks
Darren
okay I think I got the dimming feature figured out....pretty cool, however so far it hasn't resolved my exposure issue but I am going to run a few more variations....I think I need more dimming and maybe no outline. I have heavy walls separated by thin lines that keep ending up a solid mass. This is a model that can be done on the FDM machine but I am hoping to get a cleaner output on the SLA....maybe a different kind of resin will help..I will try that if the pixel dim doesn't do it.
Thanks for the assist...
Is there a tutorial on how to use dimming to reduce my exposure issues or just in general?
The video link didn't seem to be much of anything. But I am on a phone so maybe it didn't go where it should.
Okay not sure this is a new idea but it just popped into my head as I was trying to tune in a new resin.
I will call it MicroSlicing (ms) and it is named after the idea that a stepper can do MicroSteps which are kinda make believe steps between real steps...
What I propose is Micro Slices which are slices that are in theory 'thinner' than the specified slices...maybe this is akin to continuous printing but here is how I think it might work.
Say you choose a step size for Z like 100 nm
Then the slicer not only generates the usual images that are 100nm apart but it also analyses each image and generates say 10 intermediate images between each main image.
The images are displayed sequentially spread out over the cure time of the layer.
I do not expect the stepper to actually move for each image (may or may not even be possible depending on the HW) but what the slicer does is find large continuous areas
on the main image and maybe the next main image...it then removes some these large areas in the intermediate generated images..this is akin to how the auto calibration
plate works in nanoDLP. The goal, as I think you can, see is to reduce total cure time for large areas while smaller areas get the normal cure time.
My thinking here, and possibly I have this backward, is that large exposed areas get alot of light into an area which can result in bleeding or over exposure of areas
that are supposed to remain unexposed in that plate. in particular a problem when you have two larger areas separated by a smaller unexposed area.
Also small exposed areas like one or two pixels might need the full exposure time just to cure enough to stick well to the previous layer and not break apart.
What I find is that I am often walking a line where I want more exposure time to keep my prints from pulling
apart and be sure my small details get put down but I also find that large details that are close together need less exposure or I start to loose the open areas
between them. Think like small holes in a generally filled in area...the holes either get closed up from over exposure or the print pulls apart in some area due to under exposure.
Ideally the slicer could figure out that a large exposed area containing small unexposed areas might need a little less UV than other areas that maybe have the opposite ratio of exposed to unexposed.
Well there is my big thought for the day...
Thanks for all the hard work that goes into nanoDLP
Darren
Didn't keep the exact code but I think it had to do with comments in lines with calculations...I removed the comments and all was well...
This was just a thought, I concur it should probably be taken care of on the printer side...I am looking into firmware changes for that.
I know this I am suggesting after a print info be retained....simply that when the print is started a time stamp is made like in the logs then when the last command executes the difference between start time and current time will be the time to print...
it doesn't have to be perfect but it should be pretty close assuming yo change nothing from print to print ... if you wanted to juice it up a bit you could subtract any user pause time but I don't really thing that is critical. obvious the date and time of the last time this print was completed would also be available just for general information. no real calculations involved in this type of system....
Yes I am using the Y on the setup page....I really didn't want to, preferring to use just the X/Y but everything I edit the page it puts 0.0000 in as the default for Y instead of leaving it blank then the other changes I make are rejected until I delete the 0.00s so that the page can be accepted and sometimes I forget and my other changes do not take place....so I think either the page should accept 0.000 as a null entry or better do not put the 0.000 in if there is no value in Y.
I had this happen the other day....something crashed or got stuck due to bad gCode....the lamp just stayed on for hours...not good.
anyway I propose a separate thread that will deactivate the lamp if not touched by the main process for some reasonable max period...or maybe the cure time is
on a separate thread that even if the parsing or gcode fails or something hangs it can reset the serial connection (if needed for RAMPS systems) and shut off the lamp.
I am going to look at my firmware and see if there is a way to do this there but having it both places seem like it could still be good.
that would work too....
I would like to see a couple info lines on a plate after it has been printed:
would be nice if it showed LAST PRINT TIME and TIME REQUIRED FOR PRINT
This would just be helpful when comparing print tweaks and also when selecting a previously printed model to reprint...knowing how long it will take
helps decide the order of multi part print jobs.
That would be perfect...if the recreate button was present during a slice if it stopped and restarted that would be just what I want.
This has come up a few times for me. I like to be able stop the slicing process so I can tweak it and re-run. Sometimes I notice I have selected the wrong resin profile is similar issue. A simple stop slicing button on the plate screen would suffice.
I wanted to scale down a previously printed plate....
I cloned the original resin profile
At the bottom of the cloned profile I changed the X/Y Model size modifier and the Z Model Modifier to 50 (precent)
I then resliced...
This did result in the number of Z layers being cut down and also either X or Y being scaled (not sure which) but not both.
I can see this in the first layer which is supposed to be a circle but with the scaling it becomes very elliptical. Hence my guess that only one
of X or Y was changed.
Am I doing this wrong? Do I need to put something in the Override X/Y resolution (which would seem to scale my 'pixel' size which would not be
correct as that doesn't really change.
Thanks
Darren
I was thinking whenever changing an existing plate to a new resin profile with a different thickness it might be nice to just invalidate old slice data or even auto reslice...
However I can imagine there might be issues there so my feature request would be an indicator on the Plate screen that tells what thickness that last
plate was sliced at....maybe this is not needed if NanoDLP already makes sure to interpolate slice thickness of the current profile and the images it
created for the last profile but I don't think it does and I can't see that as being the best way to handle a thickness change. Nor do I think the slicing
should be invalidated if you just change profiles except maybe if the thickness changes...but maybe a warning that the current profile and the
sliced images do not align? I have never really seen what happens here as I just always reslice before printing...but still I can see it happening
where I change a profile and forget to reslice.
Ok I understand that...I will try that and be a little more aggressive. When it didn't move I figure I must be doing it wrong but probably I gave up too easily.
I am updating my nanodlp profiles now to match what you sent...while not critical the resume print Code is also cut off I think....and I have never had anything in that box from my previous profiles....can you post the full code?
I will check to see if I can adjust the bearing block again....last time I tried I could not budge it even after removing the two small set screws...I think maybe it got some loctite in it...It does slide on easily and doesn't seem overly loose but certainly not 'tight' or hard to get on either....I did have a bent stepper and screw and wanhao is sending replacements but I put in my own for now....along with the flex coupler so to my eye at least it moves smoothly. I will be installing the fan shroud tonight as well so I will check voltages while I have it open...possible the stepper is skipping I suppose...
The wavy Z statement might not be a good description....after fixing the bends etc I have much reduced the waves on the sides of the object what I am seeing now is waves on the flat surfaces at either end of a print....not sure what to call that..but say I print a cube the top and bottom (if it is on supports) both have a non flat surface...I don't want to suspect maybe the exposure is uneven as no one else seems to have that issue and I am printing smallish object in the center so it should, I would think be pretty evenly exposed..but not sure what causes it...
Thanks James,
The sketch compiled fine I will see about getting it uploaded to my printer tonight.....
I am not sure how this all plays out...obviously many people use your original firmware and NanoDLP and get good results but I see a few people like me get the strange Z reductions..not sure about the wavy surfaces that might be unique to my setup somehow....I will know more when I get home to look at my latest set of test objects.
James....Thanks I will download and try to build...
the G4 P1 command I see following a move...I initially thought this might be for the resin to settle before UV exposure but I see P1 is only 1ms which I thought initially was S1 which equals 1 second....what is the point of a 1ms delay? Even 1 second seems a bit short for settle time....
I will defer to James about this but if I understand this correctly if we move the current shutter (really in this case the LED activation) M106/M107 and t [[WaitForDoneMessage]] commands in the Hardware Setup to the Printer Profile sections called "Before Each Layer" and "After Each Layer" we will solve the out of order issue?
I have a question .... What command actually caused the Layer image to be displayed on the LCD / DLP? Does this just happen when we move to a Z position?
Note to Shahin.....I would suggest a change to the heading "Printer Profiles" to "Print Profiles" or maybe Layer or Slice or RESIN profiles or some combination of those. This is mostly because, to me at least, the name Printer Profile implies this is a setup which universal for the printer hardware which is not the case here...that section is called reasonably Hardware Setup
I didn't really write the Printer Setup so I am not 100% certain what it is doing but I have been looking at it.
My printer is an Arduino driver/Repetier Firmware LCD based unit...the Shutter open and close corresponds to the LED UV source being turned on and off with each exposure (M106,M107).
This is why it happens every frame.
I think all the [[WaitForDoneMessage]] are there to simply wait for the Arduino to complete the command and send an acknowledgement..this seem reasonable but maybe I am missing something.
I know some people just use a fixed delay..and I could probably skip the wait and the delay in the case of the shutter/LED commands it happens near instantly.
Not sure if nano would have a problem with the acknowledgement messages coming in even if there was no explicit wait for them to do so.
I don't quite grasp what you were saying about the WaitForMessage and the Z_move_comp and how the shutter could case Z movement.
I don't think the LCD stuff is really important as the only LCD is the exposure plate and that is driven by the Pi/nanoDLP directly...So I imagine I can remove that external script call.
Thanks for the analysis, I will try to clean things up especially the shutter code and see if I can get a good Z print...