Posts made by koreandi

Hi there,

I have two thing to solve.
Maybe someone has an idea or a solution.

I have a Prusa i3 and converted the Einsy-board with a Duet 3 mini. My slicer of choice is BambuStudio. Thats already on my PC, I am used to it and I want to save further discussions with our IT to get another Slicer.
RepRap uses mm/min and I couldn´t find any way to change it in the slicer. BambuStudio outputs mm/s. The printspeed will be way to slow (by factor 60).
I don´t want to multiply all the speeds by 60 as the flowsettings in the filament won´t work anymore.
Though the max-flowrate for filament is capped to 70 mm³/s which will cap automatically the printspeed again.
Is there any other practical way to solve this?

On the same printer I want to print a part in vasemode,
I want to increase the Printspeed every second loop (Layerheight 0,24 mm) by 5%.

I think for both problems a post-processing script could solve this. But maybe there is any other possibillity.
Would such a script be a big thing?
I couldn´t find a site where the basics of scripts are explained.

Thanks in advance and have a nice day.

@soare0
If I only do M563 D0 the Tool does does not show on the Display, nor anything heats up.
If doing M563 D0 the Tool only shows if I comment out the second drive in all previous M-lines.

I would say both motors are defined:

M569 P4 S1  
M584 X0 Y1 Z2 E3:4

@T3P3Tony
Yes, you are right. Each motor drives a gear. To be more specific it drives a belt driven by this gear.

I will change the ratio to 1:1.

Anyway if trying to get any calibration data with this setup there are no datas collected.

I once got values back when disableing one motor completely in the firmware. I´ve gone through the settings several times.
Hardware works as the LED indicates correct. Also mag and agc are in the right range.

Without setting any further setting, the print pauses regulary (evertime at the same spot). And when reading the values after a print it is:

• no calibration data
• min and max flow 100 %

@soare0
Thanks for your reply.
The E / L / R values are commented out. I tried to change those values to get any other responce, but after it doesn´t even get any calibration-data it was commented out.
To not get any interrupts the complete line is actually commented out.

The sensor is as close as possible to the extruder.

Extruder is a selfmade dual-drive extruder with one nema for each drivegear.
I think the problem is either the dual-motor-setup.
Or the fact that the two motor spin in opposite directions.

And I am not sure if I have to call:

M591 D0...

or

M591 D0:1...

Both variants doesn´t really works.

I only got any usable data when changing firmware to have only one motor for my extruder.

Does the mixing ration in

M567 P0 E0.5:0.5 

Changes anything with the steps/mm? I have read that the numbers don´t have to match up to 1. So it could be also:

M567 P0 E1:1 

without any different in behaviour?

Greetings
Andreas

Re: DUET magnetic filament monitor; No calibration Data

Hi there,
I already started an attemp to get my sensor running. I was these days again on Site where the printer is based.
I changed my IO fomr 5 to 6 just to check if there was anything wrong.
The Sensor blinks 3 x green and if oushing filament through, you can see the green light flashing.
I get responce from the console but always: no calibration Data.
When starting a print, the print pauses everytime on the same area. When finishing the print, there is still no calibration data.

I guess I crooked something in my general settings.
The printer has two physical extruder gears with eacht their own extruder (Drive 3 and 4).
Could it be that I set something wrong?
Also I am not sure if this might be correct:

M568 P0 S0                                      ; enable mixing for tool 0
M567 P0 E0.5:0.5                                ; set mixing ratios for tool 0

This would be my complete config.g:

; Configuration file for Duet 3 Mini 5+ (firmware version 3.3)https://docs.duet3d.com/en/User_manual/Reference/Gcodes
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Jul 05 2022 08:21:28 GMT+0200 (Mitteleuropäische Sommerzeit)

;logTemps (Daemon.g)
if !exists(global.logTemps)
  global logTemps = false
else
  set global.logTemps = false

; General preferences
M575 P1 S1 B57600                               ; enable support for PanelDue
G90                                             ; send absolute coordinates...
M83                                             ; ...but relative extruder moves
M550 P"MH-Professional"                         ; set printer name
M669 K1                                         ; select CoreXY mode

; Network
M552 S1                                         ; enable network
M586 P0 S1                                      ; enable HTTP
M586 P1 S0                                      ; disable FTP
M586 P2 S0                                      ; disable Telnet
M587 S"xxx" P"yyy"			; Wlan LoginDaten

; Drives
M569 P0 S0                                    ; physical drive 0.0 goes forwards
M569 P1 S0                                    ; physical drive 0.1 goes forwards
M569 P2 S1                                    ; physical drive 0.2 goes forwards
M569 P3 S0                                    ; physical drive 0.3 goes forwards
M569 P4 S1                                    ; physical drive 0.4 goes forwards
M584 X0 Y1 Z2 E3:4                 		  ; set drive mapping M584 X0 Y1 Z2 E3:4   
M350 X16 Y16 Z16 E16:16 I1                    ; configure microstepping with interpolation 16
M92 X80 Y80 Z400 E157:157                		; set steps per mm 154,5; 230,6; 192,2; 183,0; 179,4; 181,2; 177,7; 169,2; 154;156; 163
M566 X900 Y900 Z60 E120:120                  ; set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z360 E1200:1200              ; set maximum speeds (mm/min); Z180
M201 X500 Y500 Z20 E250:250                  ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1000:1000 I30              ; set motor currents (mA) and motor idle factor in per cent :1000
M84 S30                                       ; Set idle timeout

; Axis Limits
M208 X0 Y-34 Z0 S1                                ; set axis minima ;M208 X0 Y-10 Z0 S1   
M208 X126 Y180 Z165 S0                          ; set axis maxima ;M208 X160 Y180 Z165 S0

; Endstops
M574 X2 S1 P"!io2.in"                             ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"!io3.in"                             ; configure active-high endstop for low end on Y via pin ystop

; Z-Probe
M574 Z1 S2                                      ; Set endstops controlled by probe
M558 P5 C"io4.in" H1.5 F300 S0.1 T12000            ; set Z probe type to switch and the dive height + speeds   ;M558 P5 C"io4.in" H5 F120 S0.1 T6000
M557 X10:110 Y10:110 P4:4                      ; define mesh grid
G31 X0 Y35 Z0.65					           ;Alt 0,55; 0,58 ;0,6 --> Wenn Z Wert größer wird, ist die Düse Näher am Bett

; filament diameter sensor
;M591 D0 P3 C"io5.in" S1 ;E0.5 L25.13 R99:101					; filament monitor connected to IO_5 magnetic sensor P3 
												;Sn 0 = disable filament monitoring (default), 1 = enable filament monitoring when printing from SD card. Filament monitors accumulate calibration data (where applicable) even when filament monitoring is disabled.
												;Raa:bb Allow the filament movement reported by the sensor to be between aa% and bb% of the commanded values; if it is outside these values and filament monitoring is enabled, the print will be paused; without given values the allowed span is from 60 to 160 %  
; Fans
M950 F1 C"out3" Q500							; Wasserkühlung-Steuerung
M106 P1 C"Hotend" S1 H1 T50                    ; set fan 1 name and value. Thermostatic control is turned on

M950 F0 C"out6" Q500                            ; create fan 0 on pin out6 and set its frequency
M106 P0 C"Partcooling" S0 H-1 L255 X255                   ; set fan 0 name and value. Thermostatic control is turned off. low speed=max=255=high speed

; Heaters
; Bed
M308 S0 P"temp0" Y"thermistor" A"Plattenheizung" T100000 B4138    ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                              ; create bed heater output on out0 and map it to sensor 0
M307 H0 B0 R0.961 C279.1 D5.93 S1.00 V24.2      ; PID-tuning bed 
M140 H0                                         ; map heated bed to heater 0
M143 H0 S100                                    ; set temperature limit for heater 0 to 100C
; Hotend
M302 S100										; cold extrusion temperature to 100C
M308 S1 P"temp1" Y"thermistor" A"Düsenheizung" T100000 B4138    ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1                              ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 R3.025 C139.2 D2.87 S1.00 V24.3		; PID-tuning Phaetus Dragon watercooled 	Altes HF Hotend Lüfter AUS H1 B0 R2.282 C279.9 D5.03 S1.00 V24.3	Neues SF Hotend Lüfter AUS M307 H1 B0 R2.748 C262.2 D3.74 S1.00 V24.3
M143 H1 S220                                    ; set temperature limit for heater 1 to 220C

; Tools
M563 P0 D0:1 H1 F0 S"Hotend"                             ; define tool 0  M563 P0 D0:1 H1 F0 S"Hotend" 
G10 P0 X0 Y0 Z0                                 ; set tool 0 axis offsets
G10 P0 R0 S0                                    ; set initial tool 0 active and standby temperatures to 0C
M568 P0 S0                                      ; enable mixing for tool 0
M567 P0 E0.5:0.5                                ; set mixing ratios for tool 0

;Paneldue
M575 P1 S1 B57600
:T0

Some questions from my site:

1. Drivermapping and Name

X0 Y1 Z2 E3:4  

This calls out physical drive 3 and 4 for the E-axis. Will 3 be automatically be "extruder drive 0" and 4 "extruder drive 1"?

2. Is the tool declaration correct?

M563 P0 D0:1 H1 F0 S"Hotend"

The heater didn´t work with only D0.

3. Value D in M591

M591 D0 P3 C"io5.in" S1 ;E0.5 L25.13 R99:101

Is D0 refferring to what?! Is this assigned to my tool or extruder, or physical drive?

4. Rotaion of the dual-E-drives
Could it be that the Filament sensor has problems with the dual driven extruder (turning the stepper in different directions)?

I used temporary only one of the stepper drivers and dissabled all the references to physical drive 4 (second extruder motor). After that the sensor showed some values an behaved a little more like it should.
But I was not able to output any consitent materialflow.

I hope someone coul dlook over my config.g.
I am happy for any hints and help and will try to test the system as soon as I can access via remote.

Greetings
Andreas

@droftarts
Great News.
Thanks a lot for your answer.

I think I will go to 24 V even if my setup won´t have any moving axis, except of the stepper.

Greetings
Andreas

Hi there,

can I use a Duet 3 Mini 5+ to hook up 3 hotend / thermistors?
I need to build a small test-rig. The Setup will have one extruder and can be (manually) switched between 3 hotends. Additional I plan to add a Duet magnetic filament sensor.

Can the temp0 and out0 also be used with a hotend or is it restricted to hotbed?
I would like to have a single-board-controller without any extensions boards, if possible. I prefer an ethernet version.

And another question:
Is there any general recommendation about 12V / 24V system?
As I need to purchase the components anyway, it doesn´t matter for me. I have heard that 24 volts runs more smoothly than 12 volts.

Thanks and have a nice day.

Hi there.

I want to have the possibillity to track the temperature-curve of my hotend and bed while printing. In DWC there is the small log-window. But I could not find any way to grab or export the data.

My thought was to use a do/while-lood or while/do-loop in the gcode file that does the following:

do {
G4 P1000
M105
} while (
...printcode...
)

or

while (
...printcode...
)
do {
G4 P1000
M105
}

Will something like this work?
Or am I thinking too comlpicated and there is an easier way?

My goal:
Get the temps each x-seconds and be able to use them in Excel or any other database.

thank a lot.

@droftarts

Hi Ian,

thanks a lot for your advice.

Regarding the firmware.
As I said: this machine is used in an experimental phase and we want to keep everything as stable as possible. And since we did not recognise any advantage with a newer version we kept it as it was.

About the filament sensor:
We just used

M591 D0 P3 C"io6.in" S1

in our config.g.

Then we started a small manual programm:

• homing
• move z to 50 mm
• extrude 200 mm filament
• end

Here are the results from the console in timed order:

18.7.2023, 09:56:29
M32 "0:/gcodes/Test extrusion filament sensor.gcode" File 0:/gcodes/Test extrusion filament sensor.gcode selected for printing

18.7.2023, 09:56:46
Duet3D rotating magnet filament monitor v4 on pin io6.in, enabled, sensitivity 28.80mm/rev, allow 60% to 160%, check every 3.0mm, version 4, mag 129 agc 82, no calibration data

18.7.2023, 09:57:51
Finished printing file 0:/gcodes/Test extrusion filament sensor.gcode, print time was 0h 1m

After typing M591 D0 into the console we got this message:
18.7.2023, 09:58:11
Duet3D rotating magnet filament monitor v4 on pin io6.in, enabled, sensitivity 28.80mm/rev, allow 60% to 160%, check every 3.0mm, version 4, mag 130 agc 82, no calibration data

Are there any further advices?
Anything that we can change and try.
The communication seems to work. But there must be any other mistake we did.
Or another possibility could be a faulty device/part.

greetings
Andreas

Dear printing-friends.

I have an experimental 3d-printer.

The built is roughly:

• DUET 3 Mini 5+ @ 3.3 RC2
• CoreXY 120 mm x 120 mm x 120 mm
• Dualmotorised extruder

As the printer is meant to print brittle filament I installed the DUET magnetic filament sensor to monitor slipping in the extruder system as well as cloggings. It is the version without switch.

As far as I can judge the wiring seems to be fine. Communication to the DUET board works. No abnormal or awkward blinking. The agc-value is in the recommended range. While extruding, the sensor blinks and the blinking also reacts very sensitive when pulling slighly on the filament.

I used the following line in config.g

M591 D0 P3 C"io6.in" E0.5 L25.13 S1 R99:101

I do not get any sensor calibration data after or while printing.
When requesting M591 D0 I get the following message:

Duet3D rotating magnet filament monitor v4 on pin io6.in, enabled, sensitivity 25.13mm/rev, allow 99% to 101%, check every 0.5mm, version 4, mag 132 agc 81, no calibration data

The print does not pause or stop. And in this case I know that the filament overextrudes.

In another scenario I started the print without any filament loaded and extruded 400 mm. The sensor needed nearly 200 mm until the print paused.
This was the result of M591 D0:

Duet3D rotating magnet filament monitor v4 on pin io6.in, enabled, sensitivity 28.80mm/rev, allow 99% to 101%, check every 0.5mm, version 4, mag 130 agc 85, measured sensitivity infmm/rev, min 0% max 0% over 192.6mm

So I am confused right now what the fault is.
Four Five questions came into my mind:

1. Why do I get no calibration data?
2. Why does the print not pause or stop when setting the limits to 99 % - 101%?
3. Why does the sensor need 200 mm of filament to recognize there is a underextrusion?
4. Why can L be set manually? I thought this represents the filament movement per revolution. Shouldn´t this value be fixed or well known by the wheel-diameter?
5. What am I doing wrong?

I hope to get here help and some suggestions what might be wrong.

Here is my config.g:

; Configuration file for Duet 3 Mini 5+ (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Jul 05 2022 08:21:28 GMT+0200 (Mitteleuropäische Sommerzeit)

; General preferences
M575 P1 S1 B57600                               ; enable support for PanelDue
G90                                             ; send absolute coordinates...
M83                                             ; ...but relative extruder moves
M550 P"MH-Professional"                         ; set printer name
M669 K1                                         ; select CoreXY mode

; Network
M552 S1                                         ; enable network
M586 P0 S1                                      ; enable HTTP
M586 P1 S0                                      ; disable FTP
M586 P2 S0                                      ; disable Telnet
M587 S"xxx" P"yyy"				; Wlan LoginDaten

; Drives
M569 P0 S0                                    ; physical drive 0.0 goes forwards
M569 P1 S0                                    ; physical drive 0.1 goes forwards
M569 P2 S1                                    ; physical drive 0.2 goes forwards
M569 P3 S0                                    ; physical drive 0.3 goes forwards
M569 P4 S1                                    ; physical drive 0.4 goes forwards
M584 X0 Y1 Z2 E3:4                     	; set drive mapping
M350 X16 Y16 Z16 E16:16 I1                    ; configure microstepping with interpolation
M92 X80 Y80 Z400 E163:163                 		; set steps per mm
M566 X900 Y900 Z60 E120:120                   ; set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z360 E1200:1200              ; set maximum speeds (mm/min)
M201 X500 Y500 Z20 E250:250                   ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1000:1000 I30              ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                       ; Set idle timeout

; Axis Limits
M208 X0 Y-34 Z0 S1                                ; set axis minima  
M208 X126 Y180 Z165 S0                          ; set axis maxima

; Endstops
M574 X2 S1 P"!io2.in"                             ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"!io3.in"                             ; configure active-high endstop for low end on Y via pin ystop

; Z-Probe
M574 Z1 S2                                      ; Set endstops controlled by probe
M558 P5 C"io4.in" H1.5 F300 S0.1 T12000            ; set Z probe type to switch and the dive height + speeds
M557 X10:110 Y10:110 P4:4                      ; define mesh grid
M591 D0 P3 C"io6.in" E0.5 L25.13 S1 R99:101					; filament monitor connected to IO_6 magnetic sensor P3; 
												

; Fans
;M950 F1 C"out5" Q500                            ; Lüftersteuerung Luftkühlung create fan 1 on pin out5 and set its frequency
M950 F1 C"out3" Q500							; Wasserkühlung-Steuerung
M106 P1 C"Hotend" S1 H1 T50                    ; set fan 1 name and value. Thermostatic control is turned on

M950 F0 C"out6" Q500                            ; create fan 0 on pin out6 and set its frequency
M106 P0 C"Partcooling" S0 H-1                   ; set fan 0 name and value. Thermostatic control is turned off

; Heaters
; Bed
M308 S0 P"temp0" Y"thermistor" A"Plattenheizung" T100000 B4138    ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                              ; create bed heater output on out0 and map it to sensor 0
M307 H0 B0 R0.961 C279.1 D5.93 S1.00 V24.2      ; PID-tuning bed
M140 H0                                         ; map heated bed to heater 0
M143 H0 S100                                    ; set temperature limit for heater 0 to 100C
; Hotend
M302 S100										; cold extrusion temperature to 100C
M308 S1 P"temp1" Y"thermistor" A"Düsenheizung" T100000 B4138    ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1                              ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 R2.282 C279.9 D5.03 S1.00 V24.3		; PID-tuning Phaetus Dragon watercooled
M143 H1 S220                                    ; set temperature limit for heater 1 to 220C

; Tools
M563 P0 D0:1 H1 F0 S"Hotend"                             ; define tool 0
G10 P0 X0 Y0 Z0                                 ; set tool 0 axis offsets
G10 P0 R0 S0                                    ; set initial tool 0 active and standby temperatures to 0C
M568 P0 S0                                      ; enable mixing for tool 0
M567 P0 E0.5:0.5                                ; set mixing ratios for tool 0

;Paneldue
M575 P1 S1 B57600
T0

If I should test or change something just let me know.
I don´t want to have the sensor as a decoration.

I wish you a happy day and looking forward for some replies.

Greetings from Germany
koreandi

@T3P3Tony
Yes, now I remember this again.
This question was at the beginning for this pfoject and now the project changed from scratch to a finished printer.
And I have to commmit that I didn´t react to this question:

What is the preferred communication method between the filament width measuring system and the Duet: async serial, or something else?

I couldn´t tell tell answer back then and even not today.

I know this device from Qualup from earlier days and I am missing some Information about the implementation with DUET/RFF. I will contact them and ask for any succesfull projects.

@dc42
Just a quick reply...
I replaced the mosfet with:
AOSS32334C

It was a little challenging to solder but I could replace the part and the board just works fine again.

Thanks for the support.

Re: Fillament-thickness sensor

I was wondering if there are any new thought or ideas about hardware and software to compensate the flowrate dynamic by measruing the filament.

There is a reason why I pull out this old topic.

I built a laborytory printer based on a DUET-board.
The material I print is non-commercial and metal-filled.

The parts need to be 100% filled to get a 100% dense part after debinding and sintering.
As the material I print is still in developement there are only small batches done and the diameter is quite inconsistant. And though the tolerances are mostly stable nowadays... On filaments with Ø 1,75 mm and a deviation of 0,01 mm the cross-section of the filament will vary 1%.

I hope to get some good advices or even some links or documentation to any built up setup.

Best wishes from Germany
koreandi

@moth4017
Thanks a lot. Is there any electrical schematic availiable?
After a quick research the named component has 4 legs (3+1) But the component on my board only has 3 legs (2+1).

BOARD:

BUK9880-55A:

Dear DUET-users,

I blew up my temp-controll for FAN out 5/6 by using the wrong voltage. The FAN runs permanently now and the temp-controll does not work anymore. 24V are still applied.
I can see clearly that the Transistor TR6 with the component-label LSDL 1K is blown. I would like to change it to see if that fixes my problem.
A spare DUET Board is already on the way but I wanna give it a try.
Does anybody know what component that exactly is?
My Board is DUET 3 Mini 5+ V1.01.

Thank a lot in advance.

@alex-cr

The hardware should not be the problem.
It is the firmware/software implementation.

@oliof said in Filament diameter tolerance compensation:

Schnekenstruder

Thanks oliof for your quick reply.

The printers extruder is based on two belts transporting the material. The Belts eliminate any grabbing into the material and the feedrate is not influenced by any change in filamentdiameter that results to another circumference on the driving wheel.
The filament used is a WC-Co-filled fialement which is extremly brittle. I am not sure if such a rotaryextruder (simmilar to fuselab-design) might work.

Dear DUET-Team and DUET-Users,

I don´t want to grab out such an old topic...
But I am standing on a point to decide wheter I keep on going with DUET or Marlin/SKR.
I need to print parts with highly metallic-filled filament. The parts will be debindered and sintered and need to be filled by 100% in volume.
Having am Filament with 1,75 mm +/- 0,05 mm means the deviation can be 12 %. Most of the filament I tested so far do even have higher deviation within small sections on the spool.

Is there any way to use a softwarecompensation triggered by any kind of sensor?

There is M221 or M404 to influence it. But compared to Marlin there is no M405 to set the distance.

It would be nice to hear about any solution.
I want to stay with DUET and know a printer-developer that highly want to use such a feature.

Greetings
Andreas

@koreandi
Okay.. I rerolled 3.3 and afterwards 3.4B6 worked...
I will test the functions.

Thanks a lot.

@pcr
Hmm. I still don´t manage to get any other version installed.
Still the same message:

Error: M997: In-application programming binary "0:/firmware/Duet2_SDiap32_WiFiEth.bin" not found