Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. alil2096
    • Profile
    • Following 1
    • Followers 0
    • Topics 12
    • Posts 63
    • Best 1
    • Controversial 0
    • Groups 0

    alil2096

    @alil2096

    2
    Reputation
    4
    Profile views
    63
    Posts
    0
    Followers
    1
    Following
    Joined Last Online
    Website www.lillia.net

    alil2096 Unfollow Follow

    Best posts made by alil2096

    • Job report

      Hi, there is the possibility to create a report when the print is finished?

      Maybe inserting the complete graph of temperature, for monitoring the temp during all job, or with the total real time, consumed material, total height, time for layer, or another data?

      maybe being able to export it in excel format or something similar.

      It's possible?

      posted in Firmware wishlist
      alil2096undefined
      alil2096

    Latest posts made by alil2096

    • Issues after upgrading to 3.5.4 | Duet2wifi

      Hi All,

      yesterday I've ugraded my Duet2 wifi from 3.2.x (i think, I don't remember the correct version), to the last stable release, the 3.5.4.

      After that, I 've a lot of problem:

      1. fans don't work. Before the update I was using one always on fan for cooling the heatsink (using one of two pins always on) and one fan for cooling print on fan0 pin. After update no one is working. I've partially resolved wiring the always on fan directly on the power supply (24V); for the second fan I've tried to change the pin (from fan0 to fan1 and fan2), but none of them work.

      2. Z probe issue: after the change my probe doesn't work well. The pritner start to print with about 1mm of air between the nozzle and the heatedbed. I've tried to recalibrate, but I haven't solved

      3. z motor: my printer is a custom coreXY, and I've two motor nema23 for z-axis. After the update it seems that the motors do not have enough power to raise the plane, but I have not changed anything in the firmware or hardware. The motors now act as if they are delivering little power

      Here my config.g:

       ; Configuration file for Duet WiFi (firmware version 3.3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.15 on Fri Mar 17 2023 09:18:48 GMT+0100 (Ora standard dell’Europa centrale)
      
      ; General preferences
      G90                                          	   ; send absolute coordinates...
      M83                                           	  ; ...but relative extruder moves
      M550 P"M3D400 - RRF3"                         	  ; 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
      
      ; Drives
      M569 P5 S1 T3:3:3:3									; Driver X (originale T3:3:3:3)
      M569 P6 S1 T3:3:3:3									; Driver Y (originale T3:3:3:3)
      M569 P2 S1											; Driver Z
      M569 P3 S1											; Driver U
      M569 P1 S0											; Extruder 1
      M569 P4 S0											; Extruder 2
      M584 X5 Y6 Z2:3 E1:4								; set drive mapping
      M350 Z16 U16 E256:256 I1							; configure microstepping with interpolation
      M92 X133.33 Y133.33 Z640 U640 E6550:6550			; set steps per mm
      M566 X600 Y600 Z120 E200:200						; set maximum instantaneous speed changes (mm/min)
      M203 X27000 Y27000 Z1000 E1800:1800					; set maximum speeds (mm/min)
      M201 X10000 Y10000 Z250 E3000:3000					; set accelerations (mm/s^2)
      M906 Z1200 E800:800 I30								; set motor currents (mA) and motor idle factor in per cent
      M84 S30												; Set idle timeout
      
      ; Axis Limits
      M208 X0 Y0 Z0 S1									; set axis minima
      M208 X370 Y330 Z398 U398 S0							; set axis maxima
      
      ; Endstops
      M574 X1 S1 P"xstop"									; endstop X
      M574 Y1 S1 P"!ystop"								; endstop Y
      M574 Z1 S1 P"e0stop+zstop"							; endstop Z axes with two motors
      
      ; Z-Probe
      ;M558 P5 C"^zprobe.in" H5 F420 T6000				; OLD set Z probe type to switch and the dive height + speeds
      M558 P5 C"!zprobe.in" H5 F420 T6000					; set Z probe type to switch and the dive height + speeds
      G31 P500 X0 Y0 Z0								; set Z probe trigger value, offset and trigger height
      M557 X15:375 Y20:320 S60							; 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 R0.156 K0.158:0.000 D4.67 E1.35 S0.90 B0		; 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"e1temp" Y"thermistor" T100000 B4138			; configure sensor 1 as thermistor on pin e0temp
      M950 H1 C"e1heat" T1									; create nozzle heater output on e0heat and map it to sensor 1
      M307 H1 R2.966 K0.432:0.000 D8.06 E1.35 S1.00 B0 V24.2	; disable bang-bang mode for heater  and set PWM limit
      M143 H1 S280											; set temperature limit for heater 1 to 270C
      M308 S2 P"e0temp" Y"thermistor" T100000 B4138			; configure sensor 2 as thermistor on pin e0temp
      M950 H2 C"e0heat" T2									; create nozzle heater output on e1heat and map it to sensor 2
      M307 H2 R3.450 K0.490:0.000 D4.61 E1.35 S1.00 B0 V24.2	;disable bang-bang mode for heater  and set PWM limit
      M143 H2 S280											; set temperature limit for heater 2 to 270C
      
      ; Fans
      ;M950 F0 C"fan0"                                		; create fan 0 on pin fan0 and set its frequency
      ;M106 P0 S255 H-1 C"ventola0"                                        ; set fan 0 value. Thermostatic control is turned on
      ;M950 F1 C"fan1"                                		; create fan 0 on pin fan0 and set its frequency
      ;M106 P1 S255 H-1 C"ventola1"                                        ; set fan 0 value. Thermostatic control is turned on
      ;M950 F2 C"fan2"                                		; create fan 0 on pin fan0 and set its frequency
      ;M106 P2 S255 H-1 C"ventola2"                                         ; set fan 0 value. Thermostatic control is turned on
      
      ; Tools
      M563 P1 S"Supporto" D0 H1 F0					; define tool 1
      G10 P1 X0 Y0 Z0									; set tool 1 axis offsets
      G10 P1 R0 S0									; set initial tool 1 active and standby temperatures to 0C
      M563 P0 S"Principale" D1 H2 F0					; define tool 0
      G10 P0 X-14 Y0 Z0								; set tool 0 axis offsets
      G10 P0 R0 S0									; set initial tool 0 active and standby temperatures to 0C
      
      
      ; Tools originale e funzionante
      ;M563 P0 S"Principale" D1 H2 F0					; 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
      ;M563 P1 S"Supporto" D0 H1 F0					; define tool 1
      ;G10 P1 X14 Y0 Z0								; set tool 1 axis offsets
      ;G10 P1 R0 S0									; set initial tool 1 active and standby temperatures to 0C
      
      ; Custom settings are not defined
      
      
      

      I disabled the fans now and put the Z probe value back to 0, but then I wanted to try and it gave me the motor problem. They are not warm and until yesterday work well.

      Any ideas?

      Thanks,

      Andrea

      posted in Firmware installation
      alil2096undefined
      alil2096
    • News on Servo Motors Duet3d

      Hi, at Formnext in Novmber, I saw the fantastic servo-motors from Duet..

      Any news on the release date?

      Today I'm using two Clearpath from Teknic, but I'm totaly unsatisfied..

      posted in General Discussion
      alil2096undefined
      alil2096
    • RE: MIgration from RRF2 to RRF3 problem commands

      @Phaedrux Yes, the problem was there.

      For those reading this, I solved it like this:

      ; homeall.g
      ; called to home all axes
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.15 on Fri Mar 17 2023 09:18:48 GMT+0100 (Ora standard dell’Europa centrale)
      G91							; relative positioning
      G1 H1 X-395 F3000			; move quickly to X and stop there (first pass)
      G1 H1 Y-345 F3000			; move quickly to Y and stop there (first pass)
      G1 X5 F1800					; go back a few mm
      G1 Y5 F1800					; go back a few mm
      G1 H1 X-395 F360			; move slowly to X and Y axis endstop once more (second pass)
      G1 H1 Y-345 F360			; move slowly to X and Y axis endstop once more (second pass)
      ;G92 X0 Y0
      G1 H1 Z410 F1800			; move Z up until the endstop is triggered
      G92 Z410					; set Z position to axis maximum (you may want to adjust this)
      G1 Z-5 F1800				; go back a few mm
      G1 H1 Z410 F1800			; move slowly to X and Y axis endstop once more (second pass)
      G92 Z410					; set Z position to axis maximum (you may want to adjust this)
      G90							; absolute position
      

      The single code are then reported in the single axes home files.

      posted in Firmware installation
      alil2096undefined
      alil2096
    • RE: MIgration from RRF2 to RRF3 problem commands

      Another problem with homing...

      When I use the "Home All" command, i've the error "G28 Error: G0/G1: insufficient axes homed", while if I use the single home buttons, I don't have this error.

      Therefore, when a try to lunch a job with the start G-code only "G28", the print fails because I0ve se same error..

      Here my HomeAll code:

      ; homeall.g
      ; called to home all axes
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.15 on Fri Mar 17 2023 09:18:48 GMT+0100 (Ora standard dell’Europa centrale)
      G91  	                 ; relative positioning
      ;G1 H2 Z5 F6000        ; lift Z relative to current position
      G1 H1 X-395 Y-345 F3000 ; move quickly to X or Y endstop and stop there (first pass)
      G1 X5 Y5 F1800      ; go back a few mm
      G1 H1 X-10 Y-10 F360       ; move slowly to X axis endstop once more (second pass)
      G1 H1 Z410 F1800	; move Z up until the endstop is triggered
      G92 Z410			; set Z position to axis maximum (you may want to adjust this)
      G90					; absolute position
      

      Home X:

      ; homex.g
      ; called to home the X axis
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.15 on Fri Mar 17 2023 09:18:48 GMT+0100 (Ora standard dell’Europa centrale)
      G91					; relative positioning
      ;G1 H2 Z5 F6000		; lift Z relative to current position
      G1 H1 X-395 F3000	; move quickly to X axis endstop and stop there (first pass)
      G1 X5 F1800			; go back a few mm
      G1 H1 X-395 F360	; move slowly to X axis endstop once more (second pass)
      ;G1 H2 Z-5 F6000	; lower Z again
      G90					; absolute positioning
      

      Home Y:

      ; homey.g
      ; called to home the Y axis
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.15 on Fri Mar 17 2023 09:18:48 GMT+0100 (Ora standard dell’Europa centrale)
      G91					; relative positioning
      ;G1 H2 Z5 F6000		; lift Z relative to current position
      G1 H1 Y-345 F1800	; move quickly to Y axis endstop and stop there (first pass)
      G1 Y5 F6000			; go back a few mm
      G1 H1 Y-345 F360	; move slowly to Y axis endstop once more (second pass)
      ;G1 H2 Z-5 F6000	; lower Z again
      G90					; absolute positioning
      

      Home Z:

      ; homez.g
      ; called to home the Z axis
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.15 on Fri Mar 17 2023 09:18:48 GMT+0100 (Ora standard dell’Europa centrale)
      G91					; relative positioning
      G1 H1 Z410 F1800	; move Z up until the endstop is triggered
      G92 Z410			; set Z position to axis maximum (you may want to adjust this)
      G90					; absolute position
      

      Any ideas?

      Andrea

      posted in Firmware installation
      alil2096undefined
      alil2096
    • RE: MIgration from RRF2 to RRF3 problem commands

      @droftarts

      **I think your y homing macro is wrong**
      

      THATS'S RIGHT!!!

      With the new RRF3 the macro is that of the configurator, which was different from my RRF2.

      Now I've modify the macros and X and Y work fine!!! I've copied the old macro in the RRF3. Easy.

      Now for Z axes: I've two motor, this is the old configuration (RRF2):

      ; homez.g
      ; called to home the Z axis
      G91						; relative positioning
      G1 H2 Z-1 F250			; lift Z relative to current position
      						; split Z motor control to Z and U
      						; for it to work we have to show U (param P4) in the UI
      M584 Z2 U3 P4			; show U dirver
      G1 H1 Z410 U410 F500	; move Z down until the endstop is triggered
      M584 Z2:3 P3			; hide U driver
      G92 Z410				; set Z position to axis minimum (you may want to adjust this)
      
      

      And now is the new (RRF3):

      ; homez.g
      ; called to home the Z axis
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.15 on Fri Mar 17 2023 09:18:48 GMT+0100 (Ora standard dell’Europa centrale)
      G91              ; relative positioning
      G1 H1 Z-1 F6000   ; lift Z relative to current position
      G1 H1 Z410 F1800 ; move Z up until the endstop is triggered
      G92 Z410         ; set Z position to axis maximum (you may want to adjust this)
      
      ; Uncomment the following lines to lift Z after probing
      ;G91             ; relative positioning
      ;G1 Z5 F100      ; lift Z relative to current position
      ;G90             ; absolute positioning
      
      
      

      I've read that in RRF3 is no longer necessary to split the motor, that's right?

      EDIT:
      resolved also the Z axes. I've follow this guide:
      https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors#Section_In_RepRapFirmware_Num_3

      (in the bottom of page), and now my zhome.g is:

      ; homez.g
      ; called to home the Z axis
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.15 on Fri Mar 17 2023 09:18:48 GMT+0100 (Ora standard dell’Europa centrale)
      G91              ; relative positioning
      G1 H1 Z-1 F6000   ; lift Z relative to current position
      G1 H1 Z-410 F1800 ; move Z up until the endstop is triggered
      G92 Z-410         ; set Z position to axis maximum (you may want to adjust this)
      
      ; Uncomment the following lines to lift Z after probing
      ;G91             ; relative positioning
      ;G1 Z5 F100      ; lift Z relative to current position
      ;G90             ; absolute positioning
      
      posted in Firmware installation
      alil2096undefined
      alil2096
    • RE: MIgration from RRF2 to RRF3 problem commands

      @dc42 Here you are:

      ; Configuration file for Duet WiFi (firmware version 3.3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.15 on Fri Mar 17 2023 09:18:48 GMT+0100 (Ora standard dell’Europa centrale)
      
      ; General preferences
      G90                                             ; send absolute coordinates...
      M83                                             ; ...but relative extruder moves
      M550 P"M3D400 - RRF3"                           ; 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
      
      ; Drives
      M569 P5 S0 T3:3:3:3								; Driver X
      M569 P6 S0 T3:3:3:3								; Driver Y
      M569 P2 S0                                      ; Driver Z
      M569 P3 S0                                      ; Driver U
      M569 P4 S1                                      ; Extruder 1
      M569 P1 S1										; Extruder 2
      M584 X5 Y6 Z2:3 E1:4							; set drive mapping
      M350 Z16 U16 E32:32 I1							; configure microstepping with interpolation
      M92 X200 Y200 Z640 U640 E394:394				; set steps per mm
      M566 X1000 Y1000 Z12 E120:120					; set maximum instantaneous speed changes (mm/min)
      M203 X24000 Y24000 Z600 E1200:1200				; set maximum speeds (mm/min)
      M201 X1000 Y1000 Z20 E250:250					; set accelerations (mm/s^2)
      M906 Z800 E800:800 I30							; set motor currents (mA) and motor idle factor in per cent
      M84 S30                                         ; Set idle timeout
      
      ; Axis Limits
      M208 X0 Y0 Z0 S1								; set axis minima
      M208 X390 Y340 Z398 U398 S0						; set axis maxima
      
      ; Endstops
      M574 X1 S1 P"xstop"								; endstop X
      M574 Y1 S1 P"ystop"								; endstop Y
      M574 Z1 S1 P"zstop"								; endstop Z
      M574 U1 S1 P"e0stop"							; endstop U
      
      ; Z-Probe
      M558 P5 C"^zprobe.in" H5 F420 T6000				; set Z probe type to switch and the dive height + speeds
      G31 P500 X0 Y0 Z-0.031							; set Z probe trigger value, offset and trigger height
      M557 X15:375 Y20:320 S60						; 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"e1temp" Y"thermistor" T100000 B4138   ; configure sensor 1 as thermistor on pin e0temp
      M950 H1 C"e1heat" 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 S270                                    ; set temperature limit for heater 1 to 270C
      M308 S2 P"e0temp" Y"thermistor" T100000 B4138   ; configure sensor 2 as thermistor on pin e0temp
      M950 H2 C"e0heat" 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 S270                                    ; set temperature limit for heater 2 to 270C
      
      ; Fans
      M950 F0 C"fan0" Q500							; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H0 T45								; set fan 0 value. Thermostatic control is turned on
      M950 F1 C"fan1" Q500							; create fan 1 on pin fan1 and set its frequency
      M106 P1 S1 H1 T45								; set fan 1 value. Thermostatic control is turned on
      
      ; Tools
      M563 P0 S"Principale" D0 H1 F0                  ; 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
      M563 P1 S"Supporto" D1 H2 F0                    ; define tool 1
      G10 P1 X14 Y0 Z0                                ; set tool 1 axis offsets
      G10 P1 R0 S0                                    ; set initial tool 1 active and standby temperatures to 0C
      
      ; Custom settings are not defined
      
      
      

      What is not clear to me is why with the same configuration (same parameters), with RRF2 everything worked fine and with RRF3 the axes of the motors are reversed and the Y endstop is not recognised and the mdriver map is wrong.

      Could there be some sort of cache to clear?

      posted in Firmware installation
      alil2096undefined
      alil2096
    • RE: MIgration from RRF2 to RRF3 problem commands

      @dc42 Absolutly no change of wirings.. and yes, all my endstops are in NC mode..

      When I push the micro, the status change from "trigged=true" to "trigged=false"

      posted in Firmware installation
      alil2096undefined
      alil2096
    • RE: MIgration from RRF2 to RRF3 problem commands

      @dc42 yes, it does

      posted in Firmware installation
      alil2096undefined
      alil2096
    • RE: MIgration from RRF2 to RRF3 problem commands

      @dc42 Yes, that's the problem!! Endstop Y is "trigged=true".

      Wiring is ok, How I can invert the logic? Because if I change the S1 in S0 or S2, then I have "1=null" in Object Model Browser..

      posted in Firmware installation
      alil2096undefined
      alil2096
    • RE: MIgration from RRF2 to RRF3 problem commands

      @dc42

      Ok, maybe the movement is Z+5, but the Y axes doesn't move when I try to home Y 🙃

      For the second point, If I send G91 and then G1 2 Y5 (safety first) I see an inclinated movement of axes, because only one motor of my Corexy is moving.

      But both motors working because if I send the command for homing X, both motor work and the carell go correctly to home.

      posted in Firmware installation
      alil2096undefined
      alil2096