Duet maestro Driver Expansion underpowered?
-
Did you make this config file?
It's difficult to follow with the nest macros.
To verify what the motors are actually configured as can you send these commands by themselves and report back with what they return?
M584
M906
M305
M92Your firmware version is also quite ancient.
I think maybe at this point it would be best to simply update the firmware and generate a new fresh config file set using the online tool. It will be far easier to help support you.
If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
That will get your firmware and DWC up to date.You can see the change logs here:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.xFor your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/StartBackup your existing config files in the sys folder in case you want to switch back to RRF3. IT’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.
These documents will come in handy during the conversion.
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
https://duet3d.dozuki.com/Wiki/Gcode -
PS, you can post your configs and gcode within a code block to make them easier to read. Use the </> button in the post window and place your text where it says UNDEFINED
-
@phaedrux
The config format was made by community members that own the M3D Promega.
</>
M584
Driver assignments: X6 Y5 Z0:1:2:4 E3, 3 axes visibleM906
Motor current (mA) - X:650, Y:650, Z:500, E:0, idle factor 60%M92
Steps/mm: X: 80.220, Y: 80.220, Z: 399.190, E: 3120.000M305
-
; Configuration file for Duet Maestro (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Fri Aug 20 2021 16:20:05 GMT-0600 (Mountain Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Promega" ; set printer name M669 K1 ; select CoreXY mode ; Network M552 P192.168.1.61 S1 ; enable network and set IP address M553 P255.255.255.0 ; set netmask M554 P192.168.1.1 ; set gateway M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P4 S1 ; physical drive 4 goes forwards M569 P5 S1 M569 P6 S1 M584 X6 Y5 Z0:1:2:4 E3 ; set drive mapping M350 E128 I0 ; configure microstepping without interpolation M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation M92 X80.22 Y80.22 Z399.20 E390.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 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 X335 Y317 Z362 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 M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop ; Z-Probe M558 P0 H10 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:215 Y15:195 S20 ; 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 B0 S1.00 ; disable 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 e1temp M950 H1 C"e1heat" T1 ; create nozzle heater output on e1heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off 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 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 ; Custom settings are not defined ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power lossI think this is working better.
I'm having problems with the homing for this new config.
It mostly only moves the z axes when I home x and y, but they move correctly when manually jogged. -
@beej said in Duet maestro Driver Expansion underpowered?:
I'm having problems with the homing for this new config.
It mostly only moves the z axes when I home x and y, but they move correctly when manually jogged.Can you post your previous endstop configuration? You may need to invert the endstop pin. It sounds like it thinks the endstop is triggered already at the start of homing.
-
@beej when I installed it and configured it the first time I had some odd issues too. But after a cold start, the steppers behaved normal. I guess it's a SPI setup thing running after a reset.
-
@phaedrux
Here's the old(In machine_endstoptypes files) M574 X2 Y2 Z2 S0 ; Set xy end-stops types (S0 is active low, applied to XY) (homex file) ; homex.g ; called to home the X axis ; updated September 4, 2018 ; same as homey.g because of coreXY ; Front left corner is (0,0) ; ============= PRE-HOMING ===================== M913 X60 ; drop X motor currents to 60% M913 Y60 ; drop Y motor currents to 60% ; Ignore Machine boundaries M564 H0 S0 ; Turn off bed leveling during homing G29 S2 ; Does the same as M561! ; Switch to Origin Tool T0 ; Relative positioning G91 ; Provide Z height clearance G1 Z10 F750 S1 ; ================== HOME Y ============================ ; Rapid Y until limit switch triggers G0 Y450 F1500 S1 ; Back off to release limit switch G0 Y-6 F1500 ; Slow advance to trigger limit switch G0 Y10 F120 S1 ; Set this location as Y = 341mm G92 Y341 ; Move the gantry slightly away from back of printer, to allow travel past the bolt mounting the gantry bracket G0 Y-2 F1200 ; ============= HOME X ==================== ; Rapid X until limit switch triggers G0 X-450 F1500 S1 ; Back off to release limit switch G0 X6 F1500 ; Slow advance to trigger limit switch G0 X-10 F120 S1 ; Set this location as X = 0mm G92 X0 ; Move away from the limit switch, to prevent damage to it upon next move G0 X5 F1500 ; ============ Post-Homing ============== ; Revert to absolute coordinates G90 ; Re-enable mesh leveling G29 S1 M913 X100 ; X motor currents back to 100% M913 Y100 ; Y motor currents back to 100% M98 Pmachine_axisdimension.g ; Set Axes Limits ; Stop movement across limits, enable boundaries, homing requirement M564 H1 S1 -
@beej
Here's the new homex file and homez file; homex.g ; called to home the X axis ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Fri Aug 20 2021 16:20:05 GMT-0600 (Mountain Daylight Time) ;Home y axis G91 ; relative positioning G1 H2 Z10 F6000 ; lift Z relative to current position G1 H1 Y-322 F1800 ; move quickly to Y axis endstop and stop there (first pass) G1 Y5 F6000 ; go back a few mm G1 H1 Y-322 F360 ; move slowly to Y axis endstop once more (second pass) ;home x axis G1 H1 X340 F1800 ; move quickly to X axis endstop and stop there (first pass) G1 X-5 F6000 ; go back a few mm G1 H1 X340 F360 ; move slowly to X axis endstop once more (second pass) ;G1 H2 Z-10 F6000 ; lower Z again G90 ; absolute positioning -
M574 X2 Y2 Z2 S0 ; Set xy end-stops types (S0 is active low, applied to XY)
S0 means active low, so you will indeed need to invert the pin signal.
So your M547 commands need a ! in front of the pin name, like this:
; 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 M574 Z2 S1 P"!zstop" ; configure active-high endstop for high end on Z via pin zstop -
@phaedrux
awesome that worked It's homing and everything is moving in the right directions.
The steppers are sounding a little grinding, i'm not sure if that's quite the right word.
But they aren't running as smoothly as they have been, would that have to do with the interpolation, or current...? -
M569 P0 S1 D3 V0 ; Drive 0, CoreXY_1 M569 P1 S1 D3 V0 ; Drive 1, CoreXY_2 M569 P2 S1 D3 V0 ; Drive 2, Z Motor ;back right M569 P2 S1 D3 V0 ; Drive 4, Z Motor ;back left M569 P2 S1 D3 V0 ; Drive 5, Z Motor ;front left M569 P2 S1 D3 V0 ; Drive 6, Z Motor ;front rightD3 V0 means you were running them in stealthchop mode before the entire time I believe. That could explain the difference in sound.
-
@beej said in Duet maestro Driver Expansion underpowered?:
awesome that worked It's homing and everything is moving in the right directions.
The steppers are sounding a little grinding, i'm not sure if that's quite the right word.
But they aren't running as smoothly as they have been, would that have to do with the interpolation, or current...?There is a design issue on the 2-driver expansion board (which was not designed by Duet3D) which sometimes causes the P6 driver to run a little rough, but does not affect the P5 driver. So if it's just the motor attached to P6 that sounds rough, this could be the reason. See https://forum.duet3d.com/topic/16124/duet-maesto-stepper-driver-expansion-schematic/24?_=1629705413513 and the following posts for the remedy.
