@alankilian
I tried buying the duet one last year but was unable to find it at that time.
It uses some special parts if I'm not mistaken, for my design
you need 4 flanged bearings, 2 X-seal rubbers, a couple of washers, a magnet and a hal effect sensor, on my board the sensor is connected directly to the board and works as on/off switch, I think this is possible on a duet board as well.
Posts made by brampie
-
RE: rotating filament runout/clog sensor
-
rotating filament runout/clog sensor
Hi,
I've been working on a rotating filament sensor (with a magnet + hal effect sensor).
I've gotten to the point where it seems to be working well and reliable (3 weeks now, on a printer running marlin).
I'm using rubber X-seals to ensure good contact with the filament without adding too much resistance.Do any of you think it's an interesting device to have ?
It detects both when the filament spool is empty and when the print head is clogged.
I do "a lot" of 3d printing and these 2 cases seem to account for +90% of my failed prints (I often print flame resistant abs and this can clog at times)I've made a small video, https://youtu.be/DCe-7jBzin0
I posted this on the reprap forum last week but there was zero response
thx
Bram -
RE: My Duet Experiences
@blacksheep99
Hi,
I'm selling my duet board, duet ethernet + paneldue + pt100 + duex
Used for 100 (printing) hours, I was hoping to get 200 euros for everything (cost me 420 euro new) -
RE: paid support
The documentation does suggest this but:
-When printing on some surfaces that are less flat I find that delta calibration can cause skewed prints, maybe because it's difficult to tell the difference between a bed that is mounted at an angle and a tufnol plate that is somewhat warped.
I do delta calibration on a clean flat aluminium plate, then if I need to print on something other than that plate, I switch plates and do mesh compensation.-With my printer delta calibration requires the head to be in the halfway position, this requires manual intervention
You think this causes me to have these issues ?
-
RE: paid support
I managed a couple of prints without further adjustments, after 3 prints I needed to adjust the head -0.9mm with babystepping, homing again did not help here.
Resetting did help somewhat, but I'm now on +0.2mm with babystepping.
I did M500 before rebooting hoping that the config would be saved, I did not do delta calibration after reboot. -
RE: paid support
My bad, I was using the smartphone and pressed the y-50 button by accident, a nice scratch info the new aluminium plate.
Shouldn't duet stop at the height of the offset when the head is active actually, or at least ask for confirmation before going to 0 ?
I guess not using the buttons X,Y,Z on the web interface solves that, maybe a head1-z=0 macro button insteadYes, I get that, but if I print the first layer with head1, and I see it needs to be lower, and I change the value, will duet, while printing, see that Z is no longer correct and adust while printing in this case.
I thought there was an issue (read it on the forum somewhere that the nozzle only moves when the next Gcode run that includes a Z height) that prevented this.
Or can you confirm that this does work, using these command while printing the head/nozzle does lower "immediately" ? -
RE: paid support
This would mean
G31 P500 X-12.5 Y-17.5 Z0
and for head 1:
G10 P0 X-4.32 Y-4.5 Z-2.45This does have the downside of being able to crash the head into the bed as I've just found out (should have used an old bed to try this), but it does make more sense.
Does this solve the issue of adjusting while printing, should I be able to use this command to lower the nozzle while printing the first layer and then pasting to commands in the config file.
-
RE: paid support
@luke-slaboratory
thx for your infoNo I have:
G31 P500 X-12.5 Y-17.5 Z-2.07
to set the probe trigger height
and then
G10 P0 X-4.32 Y-4.5 Z0
G10 P1 X4.32 Y4.5 Z-0.2A command like G10 P0 X-4.32 Y-4.5 Z10 does not really have the effect of the head going up.
You have G10 Z commands where the head does move while you send the command ? I was under the impression this was not possible.I have been able to get good repeatable results, but setting the height for 2 heads this way takes too long when dealing with filament that clogs easily
I'm really looking for a way like the G10 command that actually moves the head up and down so I all have to do is check with the G10 command what the correct height is and then copy past that into the config.
It would also make adjusting while printing and applying that adjustment later easier.
Not, adjusting with babystepping, applying that different to the config file, rebooting, checking, make another small adjustment.
This would save me so much time.thx
-
RE: paid support
It couldn't hurt to ask I guess.
I don't really have specific issues I think.
I have observed that I need to double babystepping when starting my second print, I don't home between prints, I would like to know if this is a known bug/issue or an issue on my end.
I would prefer to not use babystepping at all, and set the head offset directly.
However, setting the Z offset of the head/tool does not actually alters the height of the head directly ? This is still the case ?Both these issues seem to have the end result that setting the correct Z height for a dual head printer is a lot of work, this means I end up spending more time tuning the printer than printing.
I would like to know if there is a better way, it's not so much that I can't get it to work , it's more that these settings will only be good until the next clog and that clog could cost me hours in setting the correct height again.
Some (all) of this is off course user error.So, is it possible to just avoid babystepping and have something similar that is saved between prints and reboots and allows me to set the Z height of head 1 & head 2 using an up or down button and/or with the offset command so the head moves to the new position and also remembers that this z-offset needs to be applied from now on until I change it again.
I have included an image of the printer, it's really a very simple kossel based design with dual extrusion.
both heads are on a rotating part bringing either head 1 or head 2 down.
probing can be done by putting an M6 bolt between the mechanism so both heads are placed "symetrical", the endstop is a simple microswitch on the bottom of the part cooler/blower.
Switching itself is a simple on/off that switched a valve fills one of the both ends of the pneumatic cylinder.
It works well fairly well actually but still needs some work for it to work well in +50 degrees celcius. -
paid support
Hi,
I'm still having z height issues on my dual hotend delta.
It's not that it doesn't work or print but it's extremely time consuming to set it up, I feel like my config could be better and/or I'm running in to some issues where I don't really understand why the settings I'm changing don't seem to affect the print height at all, at times, and then they do, other times.Is anyone offering paid support ?
The printer is actually very simple, maybe I should try another firmware ?
duet looks really nice and when it prints it prints well, but I don't think I've done many print where I'm not compensating with babystepping, which doesn't always seem to work very well either.thx
Bram -
RE: z-offsets - babystepping - macro question
On the effector I have 2 hotends that can rotate, if head 1 is active head 2 sits a couple of mm above the print bed.
The difference in height between the 2 heads is minimal, 0.2mm or so, and can vary a bit every time I replace or remount the nozzle, in my experience remounting the nozzle can have a small impact on the z-height.I don't home between prints, so that shouldn't cause the issue
-
z-offsets - babystepping - macro question
Hi,
I have a dual extrusion delta printer, while it works I have an issue concerning Z offsets.
If I do a print and see the head is a bit high I can adjust it with babystepping.
However every time I stop the print and restart it seems babystepping it reset in the printer but not in the web interface.
Say I move the printhead 0.4mm down and it was still 0.1mm to high, if I cancel and resume the print I then need to set babystepping to -0.9mm (which is -0.5mm)
I find this a bit confusing, is this a configuration error on my end ?
With 2 nozzles I also find it very confusing because it's not because head 1 now has a new height the height of head 2 should be changed, it could, but it's not always the case.Can a macro be made [offset head 1 +0.05mm] and [offset head 1 -0.05mm]
And then the same for head 2, so I can adjust them independent from each other ? (in a way that actually moves the head up and down like babystepping)
Ideally in a way that is saved , so when I set the head 1 to -0.35mm it will remain this way for the next print, the next day.Anyone has any idea on how to do this or point me in the right direction ?
I think this would save me a lot of time.thx
Bram -
RE: G10 Z offset ignored for second tool ?
I think I got it working , I made a couple of wrong assumptions, most importantly offset Z needs to be -0.2 is the second head is 0.2mm higher.
thx for your help -
RE: G10 Z offset ignored for second tool ?
Is there a workaround ?
If I use relative positioning can't I just put the offset in the tool change script and move the head a bit up or down as needed ?
This would be a problem if a tool select is executed twice, no idea if the firmware detects that and doesn't run the script ? -
RE: G10 Z offset ignored for second tool ?
@bot
The gcode file above is already that, it starts printing with tool 1 (the second one) and it starts wrong.
Switching back to tool 0 is:
;
; *** Cooling Extruder 2 to 230 C ***
; Same extruder, about to deselect, maybe retract before cooling down
; RETRACT HERE IF YOU WANT
G4 P0
M104 S230
;
;
; *** Selecting and Warming Extruder 1 to 250 C ***
; Head to the start of the next path
G1 X3.100 Y0.000 F6000
G4 P0
; Select the Tool (extruder)
T0
; Correct position for multi-nozzle
G1 X3.100 Y0.000 F6000
G4 P0
; Set temp and then wait
M104 S250
M109 S250 -
RE: G10 Z offset ignored for second tool ?
@bot
the gcode is like this (kissslicer):
; *** Selecting and Warming Extruder 2 to 250 C ***
; Head to the start of the next path
G1 X-1.400 Y0.000 F6000
G4 P0
; Select the Tool (extruder)
T1
; Correct position for multi-nozzle
G1 X-1.400 Y0.000 F6000
G4 P0
; Set temp and then wait
M104 S250
M109 S250
; PURGE OR PRIME HERE IF DESIRED
;
;
; PREHEAT time 93.750000
; PREHEAT subtracting full 93.750000
;
; 'Prime Pillar Path', 0.5 [feed mm/s], 20.0 [head mm/s]
G1 X-1.4 Y0 Z0.15 E0 F9000
G1 X-1.4 Y0 Z0.1 E0 F300My knowledge of gcode isn't great but from what I understand there are G1 Z commands after the toolchange, also, shouldn't babysteps then jump the offset at the first babystep (it just moves the amount it says an the button, not that amount + the offset).
Is setting the offsets like I did correct, or is there a better way to work with dual nozzle setups ?
-
RE: G10 Z offset ignored for second tool ?
The config.g file :
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"dualKossel" ; set printer name
M665 R170.5 L360.27 B145 H368 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them; Network
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S0 ; physical drive 0 goes forwards <- back
M569 P1 S0 ; physical drive 1 goes forwards <- back
M569 P2 S0 ; physical drive 2 goes forwards <- back
M569 P3 S0 ; physical drive 3 goes forwards <- back
M569 P4 S0 ; physical drive 4 goes forwards <- back, was 9 ?
M584 X0 Y1 Z2 E3:4 ; set drive mapping
M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolationM92 X200.00 Y200.00 Z200.00 E418.00:418.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.00:1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z18000.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z1000.00 E1000.00:1000.00 ; set accelerations (mm/s^2)
M906 X1680 Y1680 Z1680 E800:800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 Z0 S1 ; set minimum Z; Endstops
M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop; Z-Probe
M558 P5 C"!zprobe.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
;M558 H5 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X0 Y50 Z0.72 ; set Z probe trigger value, offset and trigger height, was Z2, 0.5-0.06=0.44 -> 0.74 -> 0.72
M557 R85 S20 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"spi.cs1" Y"rtd-max31865" ; configure sensor 1 as thermocouple via CS pin spi.cs1
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S320 ; set temperature limit for heater 1 to 320C
M308 S2 P"spi.cs2" Y"rtd-max31865" ; configure sensor 2 as thermocouple via CS pin spi.cs2
M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2
M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S320 ; set temperature limit for heater 2 to 320C; Fans
M950 F0 C"fan0" Q500M950 F1 C"fan1" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P1 S1 H1 T60 ; set fan 0 value. Thermostatic control is turned onM950 F2 C"fan2" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P2 S1 H2 T60 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X5 Y-4.5 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H2 F0 ; define tool 1
G10 P1 X5 Y4.5 Z5 ; set tool 1 axis offsets 0.4 -> 0.48 -> -
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C; define output for tool switch
M950 P0 C"!exp.heater3"; Custom settings are not defined
M501
; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDuetpre0.g:
M42 P0 S0tpre1.g:
M42 P0 S1 -
G10 Z offset ignored for second tool ?
Hi,
I have a delta printer with 2 print heads (latest firmware, 3.1.1 ).
This is defined like this:
; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X5 Y-4.5 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H2 F0 ; define tool 1
G10 P1 X5 Y4.5 Z5 ; set tool 1 axis offsets 0.4 -> 0.48 -> -
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0Cwith tool 1, it doesn't seem to matter if I enter Z5, Z50 of Z0,it will just print at the same height as with tool 0, the other offsets (x and y do seem to work)
What is weird to me is that the display does say that the current z height is 5 or 50 while the print head is not.
doing baby steps to get it up works, but then it's wrong for tool 0.What is the way this should be done ? The head swivels so one is in the air while the other one is active.
thx for your time