Configuring tool board(Push Pull) remote extruder Issue
-
I'm wondering if the issue I'm having is due to incorrect Gcode or if the duet software doesn't work with the configuration I'm trying to use on the 3HC boards. I have a tool board connected to tool 0 on driver 20.0 with a direct drive extruder and a remote stepper motor on the opposite end of the Bowden tube to push filament. I was configuring the remote stepper motor to driver 1.2(3HC board) and was having issues where it would seem to cause the y stepper motors(all y stepper motors are on the 3hc board) to become unsynchronized and they would begin to lose steps and make noise. I ended up switching the remote extruders driver from 1.2(3HC board) to 0.4 (Main Board) now its working but would like to add more remote stepper motors for other tools in the future. Can someone inform me on the software limitations, I couldn't find anything specifically on this. thanks.
; Configuration file for Duet 3 (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.2 on Tue Sep 21 2021 11:41:45 GMT-0700 (Pacific Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name ; Wait a moment for the CAN expansion boards to start G4 S2 ; 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 P1.2 S0 ; X axis physical drive 0.4 goes forwards M569 P2.2 S0 ; X axis physical drive 0.5 goes forwards M569 P2.0 S0 ; Y axis physical drive 2.0 goes forwards M569 P2.1 S0 ; Y axis physical drive 2.1 goes forwards M569 P1.1 S1 ; Y axis physical drive 1.1 goes forwards M569 P1.0 S1 ; Y axis physical drive 1.3 goes backwards M569 P0.0 S0 ; Z axis physical drive 0.0 goes forwards M569 P0.1 S0 ; Z axis physical drive 0.1 goes forwards M569 P0.2 S0 ; Z axis physical drive 0.2 goes forwards M569 P0.3 S0 ; Z axis physical drive 0.3 goes forwards M569 P20.0 S0 ; Tool 1 physical drive 20.0 goes forwards M569 P21.0 S1 ; Tool 2 physical drive 21.0 goes forwards M569 P0.4 S0 ; Tool 2 physical drive 21.0 goes forwards M584 X1.2:2.2 Y2.0:2.1:1.1:1.0 Z0.0:0.1:0.2:0.3 E20.0:21.0:0.4 ; Four Z motors connected to driver outputs Z axis M671 X-30:-30:890:890 Y-30:1150:1150:-30 S3 ; leadscrews at rear left, front left, front right, rear right (connected to Z) M208 X0:845 Y0:890 ; X carriage moves from 0 to 870, Y bed goes from 0 to 870 M350 X4 Y4 Z16 E16:16:16 I1 ; configure microstepping with interpolation M92 X40.00 Y40.00 Z3200.00 E837.00:837.00:830.00 ; set steps per mm M566 X110 Y110 Z270.00 E7000.00:7000.00:7000.00 ; set maximum instantaneous speed changes (mm/min) M203 X7250.00 Y7250.00 Z350.00 E10000.00:10000.00:10000.00 ; set maximum speeds (mm/min) M201 X115.00 Y115.00 Z290.00 E8000.00:8000.00:8000.00 ; set accelerations (mm/s^2) M906 X2500 Y2500 Z2100 E550:550:550 I20 ; set motor currents (mA) and motor idle factor in per cent M84 S20 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X845 Y890 Z780 S0 ; set axis maxima ; Filament sensors M591 D0 P1 C"20.io1.in" S1 ; filament monitor connected to pin 121.io1 M591 D1 P1 C"21.io1.in" S1 ; filament monitor connected to pin 121.io1 ;Extra sensor M308 S10 Y"mcu-temp" A"MCU" ; Endstops M574 X1 S1 P"2.io2.in" ; configure active-low endstop for low end on X via pin 2.io2.in M574 Y1 S1 P"1.io2.in" ; configure active-low endstop for low end on Y via pin 1,io2.in ; Z-Probe M558 P8 C"!21.io0.in" H3 F300 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X0 Y0 Z-0.28 ; set Z probe trigger value, offset and trigger height M557 X60:820 Y60:820 S65 ; define mesh grid X/Y and probe spacing ; Heaters M308 S0 P"temp0" Y"thermistor" A"Bed" T100000 B3950 ; configure Bed sensor 1 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 1 M307 H0 R0.224 C219.6 D7.78 S1.00 V24.1 ; PID auto tune results for Tool 1 bed heater M140 H0 ; map heated bed to heater 1 M143 H0 S120 ; set temperature limit for heater 1 to 120C M308 S1 P"20.temp0" Y"pt1000" A"Tool 0" ; configure sensor 0 as thermistor on pin 20.temp0 M950 H1 C"20.out0" T1 ; create nozzle heater output on 20.out0 and map it to sensor 0 M307 H1 B0 R1.858 C109.4 D2.96 S1.00 V23.6 ; PID auto tune results for Tool 0 Titan Aqua 1.75 M308 S2 P"21.temp0" Y"pt1000" A"Tool 1" ; configure sensor 0 as thermistor on pin 20.temp0 M950 H2 C"21.out0" T2 ; create nozzle heater output on 20.out0 and map it to sensor 0 M307 H2 B0 R1.717 C105.7:98.6 D2.95 S1.00 V23.9 ; PID auto tune results for Tool 0 Titan Aqua 1.75 ;fan M950 F0 C"out8" Q250 ; create fan 0 on pin out8 and set its frequency M106 P0 T115 S0.10 H1:2 C"Radiator Fan" ; set fan 0 value. Thermostatic control is turned on M950 F1 C"20.out2" Q250 ; create fan 1 on pin out9 and set its frequency M106 P1 T205 S0.10 H1 C"Titan Aqua 1.75 T1 Hot end Fan" ; set fan 1 value. Thermostatic control is turned on M950 F2 C"21.out2" Q250 ; create fan 0 on pin out8 and set its frequency M106 P2 T205 S0.10 H2 C"Titan Aqua 1.75 T2 support material Fan" ; set fan 0 value. Thermostatic control is turned on ; Tools M563 P0 S"Titan Aqua 1.75" D0:2 H1 F0:1 ; define tool 0 M567 P0 E1.00:1.00 ; Mix drive E0 and drive E2 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M563 P1 S"Titan Aqua 1.75 support" D1 H2 F0:2 ; define tool 1 G10 P1 X-15.4 Y0 Z0 ; set tool 2 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C ; Custom settings are not defined T0 ; select first tool -
@aprz You are mixing E0:2 with mixing ratio 1:1, but the steps/mm are different? (837 vs 830)
Wouldn't you be better off when you'd wire both steppers to the same driver? (in series, as it was frequently done for dual Z motors ) -
@aprz what firmware versions are you running on the main board, the 3HC and the expansion board? Use M115 B# to check (where # is the CAN address of the board).
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@o_lampe The steps are different due to the gear ratios being different on each motor. I was going to try to run the motors on the same driver that's on the tool board but I just didn't want to run the wires from the tool board that's on the extruder to the remote stepper motor and have extra wires running from inside the print chamber. Also the peace of mind knowing I wont push the driver on the tool board too hard, which is something I didn't want to worry about since it can only use up to 1.6A. but good point I did consider that.
-
@dc42 Here's the response I got, looks like all boards are running on the same firmware.
m115 b20
Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58)m115 b21
Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58)m115 b1
Duet EXP3HC firmware version 3.3 (2021-06-15 16:12:41)m115 b2
Duet EXP3HC firmware version 3.3 (2021-06-15 16:12:41)m115 b0
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-06-15 21:45:56
