Duet3 6HC does not restart after M999
-
@kvi94 could this be related to:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta-&-RC#reprapfirmware-340beta6There is no longer a power supply control pin assigned by default (in previous firmware versions, PS_ON was assigned by default). Therefore, M80 and M81 will not work until you have assigned a power control pin. If you want to control the power supply, you should use assign a pin using either M80 or M81 with the C parameter in config.g. Use M80 if you want to start with power on, or M81 if you provide separate 5V power and you want to start with VIN power off.
-
@t3p3tony i did the necessary modification regarding M80 in my config.g but still M999 switches it off completely.
-
@T3P3Tony are there any changes regarding PS_ON in firmware 3.3?
To me, it is like there has been a modification between firmware 3.2.2 and 3.3.
Is there any test I can do to locate the issue?
Thank you.
-
Post your config
-
@phaedrux please find below my config.g, take a look and let me know if anything is wrong.
Thank you.
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; Input Power M80 C"pson" ;Enable ATX Power On ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"VCorePro" ; set printer name M669 K1 ; select CoreXY mode ; Network M552 P9.9.1.3 S1 ; enable network and set IP address M553 P255.0.0.0 ; set netmask M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S0 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S0 ; physical drive 0.3 goes forwards M569 P0.4 S0 ; physical drive 0.4 goes forwards M569 P0.5 S0 ; physical drive 0.5 goes forwards M584 X0.2 Y0.1 Z0.3:0.4:0.5 E0.0 ; set drive mapping M671 X206:-206:-206:206 Y-206:-206:206:206 P0.5 ; Levelling screw position M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm M566 X500.00 Y500.00 Z50.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z1000.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z100.00 E250.00 ; set accelerations (mm/s^2) M906 X1000 Y1000 Z800 E400 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X-206 Y-195 Z0 S1 ; set axis minima M208 X206 Y195 Z400 S0 ; set axis maxima M564 S0 H0 ; allow movement outside print volume without homing ; Endstops M574 X1 S3 ; configure sensorless endstop for high end on X M574 Y2 S3 ; configure sensorless endstop for high end on Y M915 X Y S1 R0 F0 H200 ; configure motor stall detection M574 Z0 ; using Z-Probe as endstop ; Z-Probe M950 S0 C"io7.out" ; create servo pin 0 for BLTouch M558 P9 C"^io7.in" H5 F1000 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X-30 Y-13 Z4 ; set Z probe trigger value, offset and trigger height M557 X-162:170 Y-156:180 P6 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" A"Bed" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 R0.593 C389.7 D3.93 S1.00 V0 ; 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"temp1" Y"thermistor" A"Hotend" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 R1.680 C233.0:193.0 D6.75 S1.00 V23.7 ; 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"out8" Q500 ; create fan 0 on pin out7 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"out7" Q500 ; create fan 1 on pin out8 and set its frequency M106 P1 T45 H1 ; set fan 1 value. Thermostatic control disabled ; Filament Sensor M591 D0 P1 C"io2.in" S1 ; create filament sensor for pin io2 M581 T2 P2 S0 R0 ; filament runout trigger ; Tools M563 P0 S"E3D V6" D0 H1 F0:1 ; define tool 0 G10 L1 P0 X-5 Y-13.6 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 R24 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss ; MCU temp calibration M912 P0 S-4.2 ;MCU & Driver Temp M308 S10 Y"mcu-temp" A"MCU" ; to read MCU temperature M308 S11 Y"drivers" A"Steppers" ; to read driver temperature ; Tool Select T0 ; select first tool -
-
@kvi94 said in Duet3 6HC does not restart after M999:
M80 C"pson"
I'm not exactly sure how the change to the default pin and use of M80 works now. Can you try adding another M80 below that line? Assuming that the M80 C"pson" defines the pin, and the second M80 enables it.
-
Hi,
@phaedrux i just tried your suggestion, unfortunately still having the same behaviour.
According to changelog for firmware 3.3, there are no changes regarding PS_ON. Hence, M999 should behave exactly like firmware 3.2.2. However, that is not the case.
Do you know who compiles the .bin firmware file? Probably they can help.
Additionally, do you know anyone that is using PS_ON to control an ATX/meanwell power supply? I suppose they should also be facing this issue.
Thank you.
-
I've got confirmation Re M80/M81: M80 C"pin" allocates the pin and sets the pin in the power on state. M81 C"pin" allocates the pin and sets it in the power off state (for use when providing external 5V power).
Regarding M999 behaviour I'm not sure yet.
-
@Phaedrux please do let me know if you get anything regarding M999 behaviour.
Thank you.
-
M999 just resets the board. If the board relies on M80 in config.g to keep the 5V supply on, then of course it will power off. There has been no intentional change.
-
@phaedrux said in Duet3 6HC does not restart after M999:
M999 just resets the board. If the board relies on M80 in config.g to keep the 5V supply on, then of course it will power off.
I perfectly understand and agree on this fact. But the behaviour of M999 on firmware 3.2.2 is totally different. Hence if there has been no changes, the mechanics of M999 on firmware 3.3 should produce the same outcome as on firmware 3.2.2 .
As for firmware 3.4b6, I agree there will be an issue due to the modification made (power supply control pin is not assigned by default).
I am not an expert, as far as I understand this issue will impact a user trying to control an ATX/meanwell power supply straight from the duet board, since the lost of 5V would set the power supply in standby mode. Please do correct me if i am wrong.
Thank you.
