3.2.2 external drivers mapped to conn LCD not working
-
Re: New stable firmware bundle 3.2 released
Hello I recently tried to update to 3.2.2 and I have 2 external motor drivers are connected to conn LCD driver 10 and 11 my set up is CoreXY so when I sent M564 S0 H0 to test movements for some reason the X motor is always locked and the Y motor is free to move. When I was on 3.1.1 everything was working fine. Do yo know what’s causing this problem on 3.2.2. Thank you
-
Hi,
What Duet hardware are you using?
What does your config.g file look like? You can post it using the </> tag.
Frederick
-
I have Duet Ethernet and Duex5 when I'm on 3.1.1 everything works fine but on 3.2.2 external X-axis motor doesn't move only the Y-axis. the X-axis is locked with no movements.
; Configuration file for DuetE thernet (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Oct 13 2020 21:14:55 GMT-0500 (Central Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"MyPrinter" ; set printer name M669 K1 ; select CoreXY mode ; 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 P10 R1 T3:3:3:0 S1 ; physical drive 0 goes forwards M569 P11 R1 T3:3:3:0 S1 ; physical drive 1 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M569 P4 S1 ; physical drive 4 goes forwards M569 P5 S1 ; physical drive 5 goes Backwards M569 P6 S1 ; physical drive 6 goes Backwards M569 P8 S1 ; physical drive 7 goes Backwards M569 P2 S1 ; physical drive 9 goes backwards M584 X10 Y11 Z5:6:8:2 E3:4 ; set drive mapping M671 X50.0:450.0:450.0:50.0 Y50.0:50.0:450.0:450.0 S2 ; ZBelts Near Locations M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation M92 X40 Y40 Z412.00 E415.00:415.00 ; set steps per mm M566 X8000 Y8000 Z800 E1200:1200 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z1000 E3600:3600 ; set maximum speeds (mm/min) M201 X8000 Y8000 Z1200 E800:800 ; set accelerations (mm/s^2) M906 X1800 Y1800 Z1000 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 X500 Y500 Z500 S0 ; set axis maxima M574 X1 S1 P"!xstop" ; configure active-high endstop for low end on X via pin !xstop M574 Y1 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin !ystop M574 Z1 S2 ; configure Z-probe endstop for low end on Z M574 Z2 S1 P"!zstop+!duex.e2stop+!duex.e3stop+!duex.e5stop" ; configure active-high endstop for high end on Z ; Z-Probe M558 P1 C"zprobe.in" H5 R0.2 F200 T3000 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X5 Y29 Z1.5 ; set Z probe trigger value, offset and trigger height M557 X20:460 Y20:460 S40 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4725 C7.06e-8 ; 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 A11 C99000 D2000 B1 ; 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.cs2" Y"thermocouple-max31856" ; 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 S360 ; set temperature limit for heater 1 to 280C M308 S3 P"duex.e2temp" Y"thermistor" T10000 B3950 ; configure sensor 3 as thermistor on pin duex.e2temp M950 H3 C"e1heat" T3 ; create chamber heater output on duex.e2heat and map it to sensor 3 M307 H3 A11 C99000 D2000 B1 ; enable bang-bang mode for the chamber heater and set PWM limit M141 H3 ; map chamber to heater 3 ; Fans M950 F0 C"fan1" Q500 ; create fan 0 on pin fan1 and set its frequency M106 P0 C"WATER COOLING" S1 H1 T45 ; set fan 0 name and value. Thermostatic control is turned on M950 F1 C"duex.fan6" Q500 ; create fan 1 on pin duex.fan6 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"duex.fan7" Q500 ; create fan 2 on pin duex.fan7 and set its frequency M106 P2 S1 H1 T45 ; set fan 2 value. Thermostatic control is turned on ;Led-Indicators M950 P6 C"duex.e2heat" Q500 ; Assign to P6 M950 P7 C"duex.e3heat" Q500 ; Assign to P7 M950 P8 C"duex.e4heat" Q500 ; Assign to P8 M950 P9 C"duex.e5heat" Q500 ; Assign to P9 M42 P6 S0; M42 P7 S0; M42 P8 S0; M42 P9 S0; ; Tools M563 P0 S"MAIN EXTRUDER " 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"SECOND EXTRUDER" D1 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 ; Custom settings are not defined ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first tool -
@moe-adams9093 I can’t see anything in the release notes https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x#reprapfirmware-32 but I vaguely remember some discussion of changed behaviour. @dc42 ?
Ian
-
Hi,
I have external drivers on my Duet 3 Mini 5 running 3.2.2.
The Mini 5 external driver numbers are 5 and 6.
For the external drivers this is what I have based on information I was given here on the forum.
M569 P5 S1 T2:2:10:10
M569 P6 S1 T2:2:10:10M584 X5 Y6
M92 X204.75 Y204.75 - these values were determined by the 8192 "steps per revolution" setting of the external driver and the belt travel created by one revolution of the 20 tooth pulleys.
8192 / belt travel = 204.75
In M906 I have no reference to the external drivers
Frederick
-
Thanks for your responses and suggestions I have tried to Change some of my external driver parameters setting just to see if I can move the x axis but still nothing I think something in 3.2.2 it’s causing driver 10 and 11 not to work probably I’m not sure maybe @dc42 can help identify the issue thanks you
-
I see what happened. I accepted someone else's changes to support 12864 LCDs on Duet WiFi/Ethernet, but I now see that the change disabled driver 11. For now I'll build the forthcoming 3.3beta2 release with 12864 LCD support disabled on Duet WiFi/Ethernet.
