Sorry for answering to this old post. And this is only for info:
I have finished the work on my prototype watercooled hotend. Now it's ready to make first tests...
The heating block and heatbreak is from a DTO hotend.
Here are some images
Sorry for answering to this old post. And this is only for info:
I have finished the work on my prototype watercooled hotend. Now it's ready to make first tests...
The heating block and heatbreak is from a DTO hotend.
Here are some images
@andreic I think your ducts produces to much back pressure. You should test the fan in "free air" for comparison...
@matt3o Well done! And a very nice Print!
@tinchus I think you can solve the problem with putting an ";E" after the comment semi-colon, like this:
G1 Z400 ;E drop the print bed (E to exclude from layer count)
(Obviously, you need to be in absolute positioning mode for this to work)
@educatingsavvas i think T-1 should work
@cr3d I don't know which macro is called when the filament out sensor triggers...
But in that macro you can "store" the actual Extruder Value in a variable, make your math, and call another macro after 50cm of extruding.
Eventually is daemon.g also a good option to put the code in...
@agusano Which FW Version are you using?
Eventually you can invert it with a leading "!" in the M950 command
M950 F2 C"!Fan2" Q25000
@peirof @engikeneer ASA is more or less like ABS. It's really good for outdoor usage, because of very good uv-stability. The max temp is approx. 90-95°C
Small parts are no problem to print without warping. For big objects a (heated) chamber will help.
@dr_ju_ju said in DWC Custom Configuration:
As I said, I want an EASY way to modify the pages, without reverting to code bashing !!
Perhaps the BtnCmd PlugIn is something for you?
https://forum.duet3d.com/topic/22776/btncmd-dwc-plugin-create-custom-layouts-action-buttons
An easy way to create individual tabs inside DWC. All object based, with very less coding. At the moment i use 3 tabs:
One tab for preheating, homing/leveling, important infos:
the second for endstop status, spezial functions, links
the third tab will soon be used for FW retract tuning:
@mikeabuilder said in Bainbridge BARN Mark4:
but we're thinking of moving it to a location under the printing zone
try to install the electronics with good accessibility... it's much easier to make changes or checking some things.
@code7 where would you like to do the loop?
in a print file or in a macro?
EDIT:
If it is in a macro then something like this:
while iterations < X
your gcode
I'd like to ask if it is possible to connect a pwm mosfet module to a free heater pin on the expansion connector for controlling more fans?
The pwm module looks like this and it is for 3.3VDC input:
Do i need some "special wiring" like a fuse or diode somewhere to protect the duet?
@leav
Are you shure that your delta is built correctly?
bed in right angle to the towers, rod length, radius, ...
I think, some wrong parameters/dimensions can cause this "mushrooming".
EDIT: can it be that the effector is tilting?
@ratrig0331 Yes. I think this should work
@ratrig0331 if you define your output with a M106, you can set the max. speed with the X parameter.
@norder Yes. You're right. It would be better to place the in/outlet on opposite sides. But i haven't the space for that.
I don't have "bridge" between the ports. But i'm sure, the cooling will be sufficient.
@mandragora said in heatsink for watercooled hotend, dimensions?:
Are those brass barbs custom or off the shelf?
They are more like custom. They were used as gearbox ventilation fitting in an old f1 car.
I have glued them in a carbon tube. They're from nitrated titanium, very light.
I try to reduce wheight on my effector (Delta).
@owend
I've found the error in my start.g, where i set the variable to 0.
Sorry for that!
I have the following definition of variables in config.g:
; AutoFanOff Feature
global EnableAutoFanOff = false ; create variable for enable/disable automatic fan shut off
global StartTimeAutoFanOff = state.upTime ; create variable for cache the fan start time
global DurationAutoFanOff = 240 ; create variable for AutoFanOff duration
Then in daemon.g i have:
; daemon.g
; frequently called routine (0.1 Hz)
; used for checking AutoFanOff Feature
; AutoFanOff (some routines switch the layer fan on for faster cooldown. this code checks if it is time to shut down the fan)
if global.EnableAutoFanOff = true ; check if automatic fan shut down is activated
if state.upTime > {global.StartTimeAutoFanOff + global.DurationAutoFanOff} ; check if the fan was running for the desired time
M106 P0 S0 ; LayerFan off
M291 P"AutoFanOff has stopped fan!" R"daemon.g" S0 T5 ; message
set global.EnableAutoFanOff = false ; disable automatic fan shut off
When i run this config i get the following error:
Error: in file macro line 6 column 46: meta command: cannot convert operands to same type
Is it possible, that the variable set in config.g (global EnableAutoFanOff = false) is not a boolean?
I use Cura4.8 and i'd like to print a 100mm cube for PA tuning.
But i struggle to positioning the z-seam to the front!?
I have positioned the z-seam and also layer start point in front. But cura does it always in the corner!?
Does somebody know why?
Thanks in advance