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

    Audi2502

    @Audi2502

    0
    Reputation
    1
    Profile views
    6
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Audi2502 Unfollow Follow

    Latest posts made by Audi2502

    • RE: Torque vs. Current on Firmware 3.11

      I found out during printing and then researched on this and other forums. Doubble checked nearly everything which came out out.

      When I push the DWC buttons or sending a gcode command it is the same behavior.
      I already checked the wiring and everything looks fine to me.

      I did not test with removed the Duex5, due to the fact that my bltouch is on the DUEX5.

      What I can tell is that when I only use the Duet2 Wifi extruder ports, it is the same behaviour.

      posted in General Discussion
      Audi2502undefined
      Audi2502
    • RE: Torque vs. Current on Firmware 3.11

      Hi jay_s_uk,

      this concerns me as well, therefore I am asking.

      As long as I use only one extruder 900 mA the torque of the Nema 17 with 44 N are fully enough.
      As soon as I add another in the configuration the torque drops and I have to increase the current.

      posted in General Discussion
      Audi2502undefined
      Audi2502
    • RE: Torque vs. Current on Firmware 3.11

      Hi drofarts,

      here is config.g.

      I skipped only the

      G90                                                    ; send absolute coordinates...
      M83                                                    ; ...but relative extruder moves
      M550 P"Davinci"                                        ; set printer name
      M669 K1 X-1:-1:0 Y1:-1:0 ; CoreXY System
      
      ; Network
      M552 S1                                                ; enable network
      M586 P0 S1                                             ; enable HTTP
      M586 P1 S1                                             ; enable FTP
      M586 P2 S1                                             ; enable Telnet
      
      ; Drives
      M569 P0 S1                                             ; physical drive 0 goes forwards
      M569 P1 S1                                             ; physical drive 1 goes forwards
      M569 P2 S0                                             ; physical drive 2 goes forwards
      
      M569 P3 S0 ;Heater 3                                             ; physical drive 3 goes forwards
      M569 P4 S0  ;Heater 4                                           ; physical drive 4 goes forwards
      M569 P5 S0	;Heater 1										   ; physical drive 5 goes forward
      M569 P6 S0	;Heater 2										   ; physical drive 6 goes forward
      
      M584 X0 Y1 Z2 E3:6:5:4                                     ; set drive mapping
      M350 X16 Y16 Z16 E16:16:16:16 I1                             ; configure microstepping with interpolation
      M92 X156.4 Y156.4 Z2540 E873.08:873.08:873.08:873.08         ; set steps per mm
      M566 X900.00 Y900.00 Z12.00 E120.00:120.00:120.00:120.00             ; set maximum instantaneous speed changes (mm/min) = 15 mm/s
      M203 X6000.00 Y6000.00 Z180.00 E3000.00:3000.00:3000.00:3000.00        ; set maximum speeds (mm/min) 6000 mm/min = 100 mm/s
      M201 X3000.00 Y3000.00 Z20.00 E250.00:250.00:250.00:250.00             ; set accelerations (mm/s^2)
      M906 X900 Y900 Z900 E2500:2500:2500:2500 I50		                      ; set motor currents (mA) and motor idle factor in per cent
      M84 S30                                                ; Set idle timeout
      
      ; Axis Limits
      M208 X-6 Y-22 Z0 S1                                   ; set axis minima
      M208 X237 Y195 Z200 S0                                 ; set axis maxima
      
      ; Endstops
      M574 X2 S1 P"xstop"                                    ; configure active-high endstop for high end on X via pin xstop
      M574 Y1 S1 P"ystop"                                    ; configure active-high endstop for low end on Y via pin ystop
      
      ; Z-Probe
      M950 S0 C"duex.pwm5"                                 ; create servo pin 0 for BLTouch
      M558 P9 C"^zprobe.in" H10 F120 T6000         ; set Z probe type to bltouch and the dive height + speeds
      
      G31 P500 X-38 Y42 Z3                               ; set Z probe trigger value, offset and trigger height
      M557 X50:150 Y50:150 S20                               ; define mesh grid
      
      ; Bed Configuration 
      M308 S0 P"bedtemp" Y"pt1000" R4650					;PT1000 configuration directly on the Motherboard
      M950 H0 C"bed_heat" T0                                 ; create bed heater output on bedheat and map it to sensor 0
      M307 H0 A92.4 C667.4 D0.7 V11.4 B0					;enable PID mode for the bed heater 
      M140 H0                                                ; map heated bed to heater 0
      M143 H0 S120                                           ; set temperature limit for heater 0 to 120C
      
      
      ;Heater 1
      M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
      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
      
      ;Heater 2
      M308 S2 P"e1temp" Y"thermistor"  T100000 B3950 C7.06e-8 ; configure sensor 2 as thermistor on pin e1temp
      M950 H2 C"e1heat" T2                                   ; create nozzle heater output on e1heat and map it to sensor 2
      M307 H2 A257.6 C184.2 D5.0 V12.0                       ; Set Heater2 from autotuning
      
      ;Heater 3
      M308 S3 P"duex.e2temp" Y"thermistor" T100000 B3950 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
      M950 H3 C"duex.e2heat" T3                                   ; create nozzle heater output on e0heat and map it to sensor 1
      M307 H3 A257.6 C184.2 D5.0 V12.0                                        ; disable bang-bang mode for heater  and set PWM limit
      
      ;Heater 4
      M308 S4 P"duex.e3temp" Y"thermistor" T100000 B3950 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
      M950 H4 C"duex.e3heat" T4                                   ; create nozzle heater output on e0heat and map it to sensor 1
      M307 H4 A257.6 C184.2 D5.0 V12.0                                      ; disable bang-bang mode for heater  and set PWM limit
      
      
      
      ; Fans
      M950 F0 C"fan0" Q500                                   ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H1:4 T45 L1.0                    ; set fan 0 value. Thermostatic control is turned on // L is setting minimum Fan-Speed lets try
      M950 F1 C"fan1" Q500                                   ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S0 H2:3 T45 L1.0                                    ; set fan 1 value. Thermostatic control is turned on
      M950 F2 C"fan2" Q500                                   ; create fan 2 on pin fan1 and set its frequency
      M106 P2 S0 H-1                                         ; set fan 2 value. Thermostatic control is turned off
      M950 F3 C"duex.fan3" Q500                               ; create fan 3 on pin duex.fan3 and set its frequency
      M106 P3 S0 H-1                                          ; set fan 3 value. Thermostatic control is turned off
      
      
      ;GPIO PORTS
      M950 P6 C"duex.fan6" 
      M950 P7 C"duex.fan7"
      
      
      ; Tools
      M563 P0 S"Maker_2R" 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
      M591 D0 P1 C"e0_stop" S1								;Filament Sensor for Extruder Drive 0
      
      M563 P1 S"Maker_1L" D1 H2 F1                            ; define tool 1
      G10 P1 X-34 Y-19 Z0                                        ; set tool 1 axis offsets
      G10 P1 R0 S0                                           ; set initial tool 1 active and standby temperatures to 0C
      M591 D1 P1 C"e1_stop" S1							   ; Filament Sensor for Extruder Drive 1
      
      M563 P2 S"Maker_2L" D2 H3 F1 ;                           ; define tool 1
      G10 P2 X0 Y0 Z0                                        ; set tool 1 axis offsets
      G10 P2 R0 S0                                           ; set initial tool 1 active and standby temperatures to 0C
      
      M563 P3 S"Maker_1R" D3 H4 F0  ;                          ; define tool 1
      G10 P3 X0 Y0 Z0                                        ; set tool 1 axis offsets
      G10 P3 R0 S0                                           ; set initial tool 1 active and standby temperatures to 0C
      
      
      

      And this is the outcome of M115:

      1.7.2020, 11:16:28 	M115
      FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2020-05-19b2
      
      posted in General Discussion
      Audi2502undefined
      Audi2502
    • RE: Torque vs. Current on Firmware 3.11

      Sorry being unprecise: DUET 2 WIFI with DUEX5 extension board.

      posted in General Discussion
      Audi2502undefined
      Audi2502
    • Torque vs. Current on Firmware 3.11

      Hi,

      my Duet Wifi with Duex5 extension board should drive 4 extruder.

      When I used only one Extruder the M906 command was
      M906 X900 Y900 Z900 E900 I30

      As soon as I added another Extruder with 900mA the Extruder0 looses torque.
      With 4 Extruders working on 900mA, I even have no torque on any of the extruders.

      Therefore I changed the current to nearly three times the original value,
      but beeing still below 2.8 A.

      Now my M906 command is :
      M906 X900 Y900 Z900 E2500:2500:2500:2500 I50

      Is this correct to do so, or do I miss something?

      Thanks for your replies.

      posted in General Discussion
      Audi2502undefined
      Audi2502
    • RE: BL Touch

      Dear PR10R,
      the BL touch should be able to reach all corners of your bed.
      Where you attach it to your carriage is more or less uninportant, because
      you can add the offset parameters to your config.

      When the BL-Touch is in PIN_Down mode, it needs to hit the bed
      before the hotend touches the bed. My PIN_Down offset is approx. 3mm to the
      lowest part of the hotend.

      Hope this helps.
      One good website is www.betrue3d.dk to get more information.

      posted in General Discussion
      Audi2502undefined
      Audi2502