An alternative to buying a bad kit for $300-500
Posted by the_digital_dentist
|
Re: An alternative to buying a bad kit for $300-500 March 10, 2017 11:17AM |
Nice and clean advancedrescue , I like it 
Edited 1 time(s). Last edit at 03/10/2017 11:20AM by fg dude.
Edited 1 time(s). Last edit at 03/10/2017 11:20AM by fg dude.
|
Re: An alternative to buying a bad kit for $300-500 March 10, 2017 11:57AM |
See if this works:
|
Re: An alternative to buying a bad kit for $300-500 March 11, 2017 03:55PM |
Here's a few from today in the cubepro housing. I really wish I could find a way to either make the little screen work or get another screen that fits there. Would be nice to get maybe a pause/play/stop, and or time remaining. Anything really.
For the most part I'll probably use the printer out of the housing unles I start using it for ABS. It's in the housing now because I had to bring it home from the fire station. I probably won't have time to mess with it for awhile at home so for the time being I'll leave it in the housing to protect it.
Edited 1 time(s). Last edit at 03/11/2017 03:57PM by advancedrescue.
For the most part I'll probably use the printer out of the housing unles I start using it for ABS. It's in the housing now because I had to bring it home from the fire station. I probably won't have time to mess with it for awhile at home so for the time being I'll leave it in the housing to protect it.
Edited 1 time(s). Last edit at 03/11/2017 03:57PM by advancedrescue.
|
Re: An alternative to buying a bad kit for $300-500 March 14, 2017 07:27PM |
Quote
advancedrescue
I've printed a lot with it and it prints great, but need to figure out why the layer fans don't come on. Has something to do with Simplify3d. I can type in M106 P0 in the duet web interface and they come on as they should, just can't get them to respond from S3D. Also got to figure out the mirrored print.
Have you checked what's in the gcode, you should be able to see what S3D is outputting, especially if you add a change at say layer 2.
Realised I hadn't posted anything I had printed.
This is ASA but ABS prints as well, could not print these before as they always warped, the part is 210mm x 105mm
Edited 1 time(s). Last edit at 03/14/2017 07:27PM by Firefox3D.
|
Re: An alternative to buying a bad kit for $300-500 March 19, 2017 03:50PM |
Got to play a little with it some more as I'm limited on time. Tho I did make some progress on the layer fan.
Up infill the other day no matter what I did in S3D, including making changes to the FFF firmware configurations like you mentioned fox didn't do anything. I even checked the g code from all the prints before, and it never attempted to turn the fans(no M106 codes in the file). There's a bunch of older prints that I sliced with S3D and I'll admit I might have actually randomly checked ones that I didn't actually have the FFF altered, but I doubt:/.
So now I made sure the FFF was set to M106 P0, although not sure what the S_ should be. I tried S0 and S255 for max. I then went into the duet config file and actually defined fan 0 as P0 via M563 codes. Now the print file code from S3D actually puts the M106 code in at the beginning of the second layer as it should, as a simple "M106", but not including P0.
Here exactly the current point I'm at, as I tend to ramble and this maybe help cut down on confusion.
-With the FFF defined as M106 P0 S0 or S255, and duet config fan 0 defined via M563 the code appears in the print file g code as "M106" at the appropriate start point I set. The fan still doesn't turn on. I monitored the duet g code console to see the commands in real time and it did send the M106 command like the print file intended.
I believe the problem is I need to define more in the duet config or the FFF. If it's the duet config perhaps I need to define the perimeters, or if it's the S3D FFF need to figure out exactly what to do with the S value. The FFF has S$ and S% in the description. So perhaps I should put it as S$ or S% but with it defined as M106 PO S$ or S%. If I set up M106 P0 in the duet config file I can manually enter in the M107 P0 and it will shut off and M106 P0 will turn it back on. I took this out of the config file though because it being in the config file turned them on when the machine powers up of course. So right now the only M106 codes I have in the config file is for the 2 E3D cooling fans and the work like intended by coming on once the HE get over 45.
Here's a picture of the S3D firmware configuration FFF, how it's set up before I made the changes, but shows the description I'm talking about. Also a picture of the duet live gcode console showing it trying to execute the M106 command. This gives a lot of insight as it shows the values. In the pictures it shows numerous starts and cancels from my attempts.
Thanks guys again for putting up with me, hopefully one day I might be able to return the favor. Sorry for not posting the codes, I'm currently not on the computer, if really needed I'll do that ASAP.
Up infill the other day no matter what I did in S3D, including making changes to the FFF firmware configurations like you mentioned fox didn't do anything. I even checked the g code from all the prints before, and it never attempted to turn the fans(no M106 codes in the file). There's a bunch of older prints that I sliced with S3D and I'll admit I might have actually randomly checked ones that I didn't actually have the FFF altered, but I doubt:/.
So now I made sure the FFF was set to M106 P0, although not sure what the S_ should be. I tried S0 and S255 for max. I then went into the duet config file and actually defined fan 0 as P0 via M563 codes. Now the print file code from S3D actually puts the M106 code in at the beginning of the second layer as it should, as a simple "M106", but not including P0.
Here exactly the current point I'm at, as I tend to ramble and this maybe help cut down on confusion.
-With the FFF defined as M106 P0 S0 or S255, and duet config fan 0 defined via M563 the code appears in the print file g code as "M106" at the appropriate start point I set. The fan still doesn't turn on. I monitored the duet g code console to see the commands in real time and it did send the M106 command like the print file intended.
I believe the problem is I need to define more in the duet config or the FFF. If it's the duet config perhaps I need to define the perimeters, or if it's the S3D FFF need to figure out exactly what to do with the S value. The FFF has S$ and S% in the description. So perhaps I should put it as S$ or S% but with it defined as M106 PO S$ or S%. If I set up M106 P0 in the duet config file I can manually enter in the M107 P0 and it will shut off and M106 P0 will turn it back on. I took this out of the config file though because it being in the config file turned them on when the machine powers up of course. So right now the only M106 codes I have in the config file is for the 2 E3D cooling fans and the work like intended by coming on once the HE get over 45.
Here's a picture of the S3D firmware configuration FFF, how it's set up before I made the changes, but shows the description I'm talking about. Also a picture of the duet live gcode console showing it trying to execute the M106 command. This gives a lot of insight as it shows the values. In the pictures it shows numerous starts and cancels from my attempts.
Thanks guys again for putting up with me, hopefully one day I might be able to return the favor. Sorry for not posting the codes, I'm currently not on the computer, if really needed I'll do that ASAP.
|
Re: An alternative to buying a bad kit for $300-500 March 24, 2017 09:28PM |
layer fan success!!
Nothing I did in the FFF firmware still helped the fan situation, at least on its own it didn't. From googling I found where someone mentioned something about the M106 codes in the S3D scripts. To get to where I'm talking about you go to -edit process setting/scripts/starting scripts, then in the bottom half of this page you'll see post processing section. S3D has some "additional terminal commands" entered here already.
Mine had:
{REPLACE "M106 S0" "M107"}
{REPLACE "M106" "M106\n;"}
And then more additional commands in not sure if I actually need.
Solution:
I simply removed these codes, also set the FFF to M106 P0 S$ and now everything works as it should. I can set the the speed and print layer in which I want the layer cooling fan to turn on.
When I kept the FFF set to M106 S$ without the P0 it would for some reason shut my E3D fans off when the print would hit the M106 S153(the speed set). So adding the P0 to the FFF fixed that and is also visible in the g code pictures.
Picture of the FFF the way it was preset
The preset S3D commands under the scripts/start scripts. These are the codes I removed later.
The print file gcode. The simple M106 by itself did nothing, also lacks the fan speed defined from S3D cooling options I'd set
Here's the print file gcode without the addition commands in the start script, but with the FFF set to the default M106 S$. This would actually turn my E3D fans off mentioned earlier.
Finally the end result where it's working as it should. M106 P0 S$ entered in the FFF settings, with the additional commands involving the M106 removed completely from the scripts in the process settings.
Nothing I did in the FFF firmware still helped the fan situation, at least on its own it didn't. From googling I found where someone mentioned something about the M106 codes in the S3D scripts. To get to where I'm talking about you go to -edit process setting/scripts/starting scripts, then in the bottom half of this page you'll see post processing section. S3D has some "additional terminal commands" entered here already.
Mine had:
{REPLACE "M106 S0" "M107"}
{REPLACE "M106" "M106\n;"}
And then more additional commands in not sure if I actually need.
Solution:
I simply removed these codes, also set the FFF to M106 P0 S$ and now everything works as it should. I can set the the speed and print layer in which I want the layer cooling fan to turn on.
When I kept the FFF set to M106 S$ without the P0 it would for some reason shut my E3D fans off when the print would hit the M106 S153(the speed set). So adding the P0 to the FFF fixed that and is also visible in the g code pictures.
Picture of the FFF the way it was preset
The preset S3D commands under the scripts/start scripts. These are the codes I removed later.
The print file gcode. The simple M106 by itself did nothing, also lacks the fan speed defined from S3D cooling options I'd set
Here's the print file gcode without the addition commands in the start script, but with the FFF set to the default M106 S$. This would actually turn my E3D fans off mentioned earlier.
Finally the end result where it's working as it should. M106 P0 S$ entered in the FFF settings, with the additional commands involving the M106 removed completely from the scripts in the process settings.
|
Re: An alternative to buying a bad kit for $300-500 April 02, 2017 04:55AM |
Quote
KmanOz
Hi Guys
New to this printer. Just bought a Duo and have read this long thread multiple times. To be honest I am none the wiser as to which way to go. I would have thought by now that maybe someone would have redesigned (printed) a whole new print head assembly. To me it seems that may be the easiest thing to do but of course I may be wrong. That with a couple or 3 e3d v6 on a custom print head assembly would be ideal but correct me if I am wrong. Also I'd want to move the print bed itself into the center so all 3 heads had the same coverage and add a heater.
Has anyone documented any of the connectors and wiring harnesses anywhere. I guess I can trace all the wring back to the controller but clearly it's been done before many times.
I feel there will be more people finding considering you can pick up this printer for next to nothing.
Anyway hi and look forward to giving this a go.
Kman
Hi Kman, welcome.
Don't understand, I have done the conversion, I did find anything needed to do so here and what I did not find I ask for, and help was not far away, so if you have questions allong you conversion, just ask here.
Just go step by step and you be fine.
Cheers.
Sorry, only registered users may post in this forum.