Duet 3 6HC Output_0 always on
-
Fair point, but this is the same behavior that it does when everything else is connected. What would be a good/valid test to perform?
-
@razrudy Ok, so I'll connect both and give it a shot and see what the results are and will report back.
-
@tpyoknig said in Duet 3 6HC Output_0 always on:
Fair point, but this is the same behavior that it does when everything else is connected. What would be a good/valid test to perform?
So you are saying with power applied to VIN and OUT 0 POWER IN and a valid config.g file OUT 0 is active?
Frederick
-
@fcwilt Correct. Anytime there is power applied to OUTPUT 0 POWER IN then OUT 0 will output power as noted by my bed led lighting up.
Having power on VIN or not doesn't change that. Its why in my testing I disconnected the SBC that had the config and disconnected any and everything else to reproduce the issue with minimal things connected.
Here's the same with VIN and OUTPUT Power IN showing power being supplied - when not being told to do so by any config.
-
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
Remove the groung from OUT_0 input and leave only the V+ see what's happening.
This is how is mine connected
Still building my enclosure so a little messy at this point.
Also the OUT_0 output is controlling a mosfet ( that's the reason for that "thick" wires on output )
I also have separate PSU for the bed controlled by the mosfet.Another idea.....connect the temp sensor for bed just to eliminate this from equation too
-
@fcwilt My config, right now is a default/stock one from RRF's configurator that I've not reconfigured as I replaced/reflashed firmware/image etc to troubleshoot this. This is was my config prior
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; GCode Dictionary: https://duet3d.dozuki.com/Wiki/Gcode ; General preferences G21 ; work in mm M555 P2 ; Set Marlin-style output G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name M669 K1 ; select CoreXY mode ; Drive Mapping/Config M569 P0.0 S0 D3 V5 H5 ; Drive 0.0 E goes forwards / Extruder M569 P0.1 S1 D3 V5 H5 ; Drive 0.0 X goes backwards / Left M569 P0.2 S1 D3 V5 H5 ; Drive 0.1 Y goes backwards / Right M569 P0.3 S1 D3 V5 H5 ; Drive 0.2 Z goes backwards / Left Z M569 P0.4 S1 D3 V5 H5 ; Drive 0.4 Z goes backwards / Right Z M569 P0.5 S1 D3 V5 H5 ; Drive 0.5 Z goes backwards / Back Z - triple Z M584 E0.0 X0.1 Y0.2 Z0.3:0.4:0.5 ; set drive mapping - triple Z M906 X800 Y800 Z800 E800 I30 ; Leveling M350 X16 Y16 Z16:16:16 E16 I1 ; configure microstepping with interpolation M915 X Y S2 F0 H200 ; X / Y Axes M566 X900.00 Y900.00 Z60 E3000 ; set maximum instantaneous speed changes (mm/min) M201 X2500.00 Y2500.00 Z100.00 E2500.00 ; set accelerations (mm/s^2) M203 X12600 Y12600 Z900 E25200 ; Maximum speeds (mm/min) M204 P3000 T3000 M208 X0:300 Y0:300 Z0:330 ; set axis min & max for X/Y M92 X99.60 Y100.35 Z1604.11 E419.6 M84 S30 ; Set idle timeout ; Endstops M574 X1 Y1 S3 ; configure sensorless endstop for low end on X & Y ; Bltouch M950 S0 C"io7.out" ; create servo pin 0 for BLTouch M558 P9 C"^io7.in" H5 R1 F800 T6000 A5 S0.02 B1 ; set Z probe type to bltouch and the dive height + speeds M671 X-25:335:152 Y40:40:350 S2 ; leadscrews at left (connected to Z) and right (connected to E1), Rear Z is E2, set max correction to 3.5mm (S) M557 X20:280 Y20:280 S20 ; define mesh grid (subtracting values for mesh to account for Z probe offset in X/Y) G31 P25 X-19 Y13 Z1.980 ; set Z probe trigger value, offset and trigger height ; Mesh Bed Compensation M376 H5 ; Set taper height 10mm ; Thermistors M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 / Bed M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1 / HotEnd ; Heaters M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 / Bed M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 / HotEnd ; Bed M140 H0 ; map heated bed to heater 0 M307 H0 B0 R0.292 C478.8 D1.12 S0.90 V23.7 ; disable bang-bang mode for the bed heater and set PWM limit ; Hotend M307 H1 R1.523 C339.7 D6.57 S1.00 V23.9 M570 S180 H1 P10 T15 ; Hotend allows 10sec for anomaly, permits 15deg excursion, abandons print after 180s ; Fans ; Part Cooling M950 F0 C"out2" Q500 ; create fan 0 on pin out2 and set its frequency M106 P0 C"PartCoolingFan" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off ; Hotend M950 F1 C"out3" Q500 ; create fan 1 on pin out3 and set its frequency M106 P1 C"HotEndFan" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on ; Tools M563 P0 S"E3DHotEnd" D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 R0 S0 ; set tool 0 axis offsets ; Custom settings are not defined M575 P1 S1 B57600 ; enable support for PanelDue 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 ; FEEDRATE CONVERSIONS ; 20mm/s = F1200 ; 35mm/s = F2100 ; 50mm/s = F3000 ; 70mm/s = F4200 ; 100mm/s = F6000 ; 120mm/s = F7200 ; 133mm/s = F8000It keeps being flagged as spam.
-
@razrudy With the thermistor connected and the bed connected, it still heats. It goes into fault state but power is still being supplied on OUTPUT_O regardless which is what has me scratching my head. Removing either lead positive or negative from INPUT_0 stops the power that's being output for OUTPUT_0 as expected.
-
@razrudy said in Duet 3 6HC Output_0 always on:
Also the OUT_0 output is controlling a mosfet ( that's the reason for that "thick" wires on output )
I also have separate PSU for the bed controlled by the mosfet.Why is the OUT_0 output controlling a MOSFET?
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
This is my working config , not complete but everything works
Configuration file for Duet 3 (firmware version 3) ; Configuration for Chiron+Titan Aero+Volcano+BlTouch+ SBC Pi4 ; executed by the firmware on start-up ; General preferences G21 ; works in mm G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Chiron" ; set printer name ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards X M569 P0.1 S0 ; physical drive 0.1 goes backwards Y M569 P0.2 S0 ; physical drive 0.2 goes bacwards ZL M569 P0.3 S0 ; physical drive 0.3 goes backwards ZR M569 P0.4 S1 D2 ; physical drive 0.4 goes forwards E M584 X0 Y1 Z2:3 E4 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80 Y100 Z400 E400.96 ; set steps per mm ;M566 X1200 Y1200 Z12 E120 ; set maximum instantaneous speed changes (mm/min) M566 X600 Y360 Z24 E1200 ; in mm/min-Marlin values ;M203 X9000 Y9000 Z180 E1200 ; set maximum speeds (mm/min) M203 X6000 Y6000 Z1200 E4800 ; set maximum speeds-Marlin values transform to mm/m ;M201 X1000 Y800 Z250 E250 ; set accelerations (mm/s^2) M201 X350 Y350 Z50 E30000 ; set accelerations-Marlin values M906 X1100 Y1100 Z1100 E1100 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X-6.0 Y-9.0 Z-20 S1 ; set axis minima M208 X400 Y400 Z445 S0 ; set axis maxima-need to remeasure this M671 X-40:440 Y200:200 ; leadscrews position at right and left of the X axis ; Endstops M574 X1 S1 P"!io0.in" ; configure active-high endstop for low end on X via pin io0.in M574 Y1 S1 P"!io1.in" ; configure active-high endstop for low end on Y via pin io1.in ;M574 Z1 S1 P"io2.in+io3.in" ; configure active-high endstop for low end on Z via pin-for original endstop's M574 Z1 S2 ; endstop set to z-probe ;Stall Detection ;M915 P0 S-5 F0 H200 R0 ; P=drive motor , S= sensitivite , H=motorstep/sec ( check home file) ; Z-Probe M950 S0 C"io5.out" ; create servo pin 0 for BLTouch M558 P9 C"^io5.in" H5 F60 T6000 R0.2 A10 ; set Z probe type to bltouch and the dive height + speeds G31 P25 X41.13 Y2.69 Z1.537 ; set Z probe trigger value, offset and trigger height M557 X40:400 Y0:400 S72:80 ; define mesh grid ; Piezo Z-probe ;M558 P8 C"io5.in" I1 R0.4 F300 X0 Y0 Z1 ;new piezo ;G31 X0 Y0 Z-0.1 P100 ;new piezo ; Heaters M308 S0 P"temp0" Y"thermistor" 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 R0.286 C453.000:453.000 D1.10 S0.50 V24.0 B0 ; 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" 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 R1.840 C275.300:275.300 D4.10 S0.50 V24.0 B0 ; disable bang-bang mode for heater and set PWM limit M143 H1 S285 ; set temperature limit for heater 1 to 285C ; Fans M950 F0 C"out4" Q25000 ; create fan 0 on pin out4 and set its frequency M106 P0 S0 H1 T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"out5" Q25000 ; create fan 1 on pin out5 and set its frequency M106 P1 S0 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"out7" Q25000 ; create fan 2 on pin out7 and set its frequency M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off ;M950 F3 C"out8" Q500 ; create fan 3 on pin out8 and set its frequency ;M106 P3 S0 H-1 ; set fan 3 value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F0:2 ; define tool 0 G10 P0 X-6.0 Y-7.0 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 M572 D0.4 S0.05 ; Miscellaneous ;M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss ;M564 H0 ; moving axes before/without homing ;M591 P1 C"io4.in" S1 D0 ; filament run out sensor - work in progressM308 and M950 are not on the same order. Not sure how important is
-
@razrudy I don't think this is config related as replacing my config with a default one, or not one at all the same behavior exists.
@fcwilt I don't know. Could that be related to the fuse that I replaced that was loose at the start that was causing the bed to power on and off randomly? Or something else?
-
@fcwilt said in Duet 3 6HC Output_0 always on:
@razrudy said in Duet 3 6HC Output_0 always on:
Also the OUT_0 output is controlling a mosfet ( that's the reason for that "thick" wires on output )
I also have separate PSU for the bed controlled by the mosfet.Why is the OUT_0 output controlling a MOSFET?
Frederick
Separate PSU for bed. Is there any other way to control the mosfet?
-
@razrudy said in Duet 3 6HC Output_0 always on:
Separate PSU for bed. Is there any other way to control the mosfet?
The 6HC has the separate power input for OUT 0. If the current rating of OUT 0 is adequate you can connect the bed power supply to OUT 0 POWER IN and the bed directly to OUT 0.
Just verify that the grounds of both power supplies are connected together if the two board ground connections are not.
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
I've tried this with seperate supplies, the same supply and new power supplies to no change in the problem I'm experiencing so I don't think it's related to the power suppl(y/ies).
-
-
@razrudy That was my conclusion as well but per Filastruder I have to have a mod/admin approve to get an RMA issued.
-
@razrudy said in Duet 3 6HC Output_0 always on:
@fcwilt 1000W 40A PSU too much for the board
Your bed heater draws 40 amps?
Wow.
Frederick
-
It would appear that the mosfet for Out_0 has failed closed. Not a good situation. Please contact your vendor and initiate a warranty exchange and include a link to this thread as authorization.
-
Can you see any damage or something on the mosfet on the board? Maybe one "leg" is not soldered properly
-
