[phpBB Debug] PHP Warning: in file [ROOT]/phpbb/session.php on line 574: sizeof(): Parameter must be an array or an object that implements Countable
[phpBB Debug] PHP Warning: in file [ROOT]/phpbb/session.php on line 630: sizeof(): Parameter must be an array or an object that implements Countable
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/feed.php on line 195: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3937)
[phpBB Debug] PHP Warning: in file [ROOT]/feed.php on line 196: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3937)
Build Your Own SLA/SLS A forum dedicated to helping you build your own SLA/SLS-based 3d printer 2016-04-11T06:47:02-04:00 https://www.buildyourownsla.com/forum/feed.php?f=11&t=4997 2016-04-11T06:47:02-04:00 2016-04-11T06:47:02-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14564#p14564 <![CDATA[Re: Extending DLP print area for large build volume]]>
Photoshop of course might be an good option to modify the files. But for me it is unclear how you want to put these back into the toolchain later on for printing. Beside that I don't like the G-Code approach to control all the motors and stuff on the machine. I like a more comprehensive approach but that is probably also because I come from embedded development background :)

Your idea with a kind of 'snap' mechanics to lock the projector into position sounds good. With that one could use low-cost mechanics while still having great repeatability. The only downside: this mechanism needs to be controlled too e.g. with a motor/solenoid or something else. I'll consider that...

Beside programming my stuff I also design the electronics. Not that hard at all - just takes a lot of time :lol:

Thanks,
radi2k

Statistics: Posted by radi2k — Mon Apr 11, 2016 6:47 am


]]>
2016-04-10T07:35:14-04:00 2016-04-10T07:35:14-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14558#p14558 <![CDATA[Re: Extending DLP print area for large build volume]]>
I'll bet one could use Photoshop with a Photoshop action script to slice up the slice images for experimenting around. I've used Photoshop before to do something like that.

As for the mechanics, the best way to do it would be to just move the light coming from the projector. One would need to find a way to turn the light coming from the projector into a beam so that it could easily be directed around. Failing that, one would be left with moving the projector or the build tray. For this, one way to get around the repeatability problem would be to use adjustable detents. So, the projector or build tray would be positioned using regular means and then when close to the projection position it would stop there and a solenoid would active a locator pin that would insert into a locator hole and then the projector would project the image for that position. The locator holes would be made to be adjustable, such that they could all be positioned at the exact locations needed for perfect alignment of the projected image every time.

That's pretty cool that you're creating your own slicer! I wish I knew computer programming. That's the one thing I was never good at when it came to building stuff.

Statistics: Posted by James — Sun Apr 10, 2016 7:35 am


]]>
2016-04-10T05:24:09-04:00 2016-04-10T05:24:09-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14557#p14557 <![CDATA[Re: Extending DLP print area for large build volume]]>
my projector and reservoir both were fixed. I just wanted to do some tests before the machine is redesigned in total e.g. additional moving mechanics. Yes, I use my own software for stepper control and the UI + projector image generation. I generate my slices using the free version of netfabb - a custom slicer is work in progress. Thus I don't use CW. I'm a software developer on my own and like to do my own stuff :D I have big plans but I'll keep that on my own for the moment.

For the test setup:
My projector has 1280x800 resolution. I split the image in two parts: Left and right, both exposing after each other and then the tilt move. That's why the repeatability is so good. Regarding mechanics to move the projector later on I don't have plans yet. I'll probably consolut my brother who is a really good mechanical engineer. But in general I do invest good amounts of money...

And yes, repeatability for the projector moves is critical. If the projector has 50µm resolution the mechanics should be much better so there is no chance for gaps as you mentioned. I'd like to avoid special post processing stuff since that's kind of bodge :lol:

Thanks,
radi2k

Statistics: Posted by radi2k — Sun Apr 10, 2016 5:24 am


]]>
2016-04-08T16:29:49-04:00 2016-04-08T16:29:49-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14542#p14542 <![CDATA[Re: Extending DLP print area for large build volume]]>
Also, I reread your first post too and found, "However, no results yet - software not fully ready yet." Are you coding a completely new slicer or are you using CW and post processing the output images in some way?

Statistics: Posted by James — Fri Apr 08, 2016 4:29 pm


]]>
2016-04-08T16:13:41-04:00 2016-04-08T16:13:41-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14541#p14541 <![CDATA[Re: Extending DLP print area for large build volume]]>
One idea I thought of while writing this just now is the linear exposure positions could be spaced slightly during the build. Once finished the resin would be held in place by capillary action, which could then be post process cured to "weld" everything together.

Not germane, but that brings up something else. If that worked, one could use that to alleviate shrinkage issues for regular SLA printing, maybe.

That's cool Steve that you're willing to work on this! Definitely a way to get more people interested in CW since a working machine and software combination would generate quite a bit of interest on AM news sites and maker news sites.

Statistics: Posted by James — Fri Apr 08, 2016 4:13 pm


]]>
2016-04-08T15:20:54-04:00 2016-04-08T15:20:54-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14539#p14539 <![CDATA[Re: Extending DLP print area for large build volume]]>
Image

First exposed one side and then the other. In the light reflections you can see it but structure is good. Also inspected it under a microscope. Looks like one piece.

Almost forgot it: no special pixel blending on the overlapping area was used to get that result. Probably also because I have very short exposure time of only 150ms (FunToDo Standard black)

However, I didn't move the projector for that. Now after that test I can redesign my whole machine!

Thanks,
radi2k

Statistics: Posted by radi2k — Fri Apr 08, 2016 3:20 pm


]]>
2016-04-07T23:27:23-04:00 2016-04-07T23:27:23-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14533#p14533 <![CDATA[Re: Extending DLP print area for large build volume]]> -Steve

Statistics: Posted by PacManFan — Thu Apr 07, 2016 11:27 pm


]]>
2016-04-07T16:56:13-04:00 2016-04-07T16:56:13-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14525#p14525 <![CDATA[Re: Extending DLP print area for large build volume]]> Statistics: Posted by James — Thu Apr 07, 2016 4:56 pm


]]>
2016-04-07T10:50:37-04:00 2016-04-07T10:50:37-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14522#p14522 <![CDATA[Re: Extending DLP print area for large build volume]]>

Let's see if I can contribute some efforts making this home-ready. This evening I'll do some tests...

Thanks,
radi2k

Statistics: Posted by radi2k — Thu Apr 07, 2016 10:50 am


]]>
2016-04-07T08:07:43-04:00 2016-04-07T08:07:43-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14518#p14518 <![CDATA[Re: Extending DLP print area for large build volume]]> viewtopic.php?f=17&t=57

I wonder if Steve (the owner of this forum and the creator of Creation Workshop) has ever had a chance to work on this.

Statistics: Posted by James — Thu Apr 07, 2016 8:07 am


]]>
2016-04-07T06:30:35-04:00 2016-04-07T06:30:35-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14515#p14515 <![CDATA[Re: Extending DLP print area for large build volume]]>
Even the commercial machines only provide poor printing area with DLP based systems. I want to take the benefit of DLP precision but scale build volume up.

Thanks,
radi2k

Statistics: Posted by radi2k — Thu Apr 07, 2016 6:30 am


]]>
2016-04-06T20:34:23-04:00 2016-04-06T20:34:23-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14508#p14508 <![CDATA[Re: Extending DLP print area for large build volume]]> Statistics: Posted by Redrichie — Wed Apr 06, 2016 8:34 pm


]]>
2016-04-06T15:42:08-04:00 2016-04-06T15:42:08-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14503#p14503 <![CDATA[Re: Extending DLP print area for large build volume]]> Statistics: Posted by SlowSL — Wed Apr 06, 2016 3:42 pm


]]>
2016-04-06T09:04:18-04:00 2016-04-06T09:04:18-04:00 https://www.buildyourownsla.com/forum/viewtopic.php?t=4997&p=14501#p14501 <![CDATA[Extending DLP print area for large build volume]]> Statistics: Posted by radi2k — Wed Apr 06, 2016 9:04 am


]]>