"out9" appears to always be enabled
-
I am looking to use out8 and out9 for LED strips. I have both enabled identically, but I am unable to control the level of (or turn off) out9 (it is always on, even at boot). Out8 works as expected.
I am running RRF3.4-beta5
Any help is greatly appreciated!!!
Here is the relevant config.g
; lights, right M950 F3 C"out8" M106 P3 S0 ; lights, left M950 F4 C"out9" M106 P4 S0
Control of brightness:
; lights off M106 P3 S0 M106 P4 S0 ; lights on M106 P3 S255 M106 P4 S255
Here is the entire config.g file
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Thu Oct 08 2020 13:25:03 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"CustomCore" ; 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 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M569 P0.4 S1 ; physical drive 0.4 goes forwards M569 P0.5 S1 ; physical drive 0.5 goes forwards M584 X0.1 Y0.2 Z0.5:0.3:0.4 E20.0 ; set drive mapping M350 X16 Y16 Z16:16:16 E16 I1 ; configure microstepping with interpolation M92 X160 Y160 Z3200:3200:3200 E398 ; set steps per mm M566 X700 Y700 Z180:180:180 E300 ; set maximum instantaneous speed changes (mm/min) M203 X60000 Y60000 Z600:600:600 E5000 ; set maximum speeds (mm/min) M201 X2500 Y2500 Z200:200:200 E5000 ; set accelerations (mm/s^2) M906 X1600 Y1600 Z1600:1600:1600 E1500 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 X320 Y300 Z300 S0 ; set axis maxima ; Endstops M574 X1 S3 ; configure sensorless homing for low end of x M574 Y2 S3 ; configure sensorless homing for high end of Y M574 Z1 S2; P"io3.in" ; configure Z-probe endstop for low end on Z M915 X Y S5 R0 F0 ; Z-Probe M558 P9 C"20.io0.in" H5 F360 T20000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds M950 S0 C"20.io0.out" ; create servo pin 0 for BLTouch G31 P500 X0 Y-43 Z1.76 ; set Z probe trigger value, offset and trigger height, -z separates from bed, +z brings nozzle tip closer M557 X38:295 Y-3:252 P5 ; define mesh grid ; leadscrew locations M671 X-18:354:169 Y77:77:343 S3 ; 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 M140 H0 ; map heated bed to heater 0 M143 H0 S150 ; set temperature limit for heater 0 to 150C M308 S1 P"20.temp0" Y"pt1000" L-25 ; configure sensor 1 as PT1000 on pin temp1 M950 H1 C"20.out0" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 A407.5 C228.4 D2.9 M143 H1 S400 ; Fans M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"20.out1" ; create fan 1 on pin out4 and set its frequency M106 P1 S1 H1 T80 ; set fan 1 value. Thermostatic control is turned on ; part cooling ssr M950 F2 C"out7" M106 P2 S0 ; lights, right M950 F3 C"out8" M106 P3 S0 ; lights, left M950 F4 C"out9" M106 P4 S0 ; Tools M563 P0 D0 H1 F2 ; 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
-
-
The issue appears to go back to at least RRF 3.2.2
-
@brendon do you get any error messages when you run M98 P"config.g" ?
-
@dc42 No error messages. Is it possible that out9 is shared with something else by default and needs to be disabled?
-
@brendon the laser connection uses out9 too
-
@jay_s_uk Thanks for checking in. I had seen this mentioned in the documents but didn't see anything mentioned about having to disable it to use out9.
-
@brendon you should not need to disable it, because it should not be enabled by default.
If you power up the board with no SD card inserted and no SBC connected, does OUT9 turn on?
-
@dc42 Yes. If you remove the SD card (I am not using an SBC), the LEDs are enabled at power on.
-
I have the out 4-6 jumper between V_OUTLC1 + 12v and the out 7 - 9 jumper between V_FUSED + V__OUTLC2. Moving the out 4-6 jumper to V_FUSED + V_OUTLC1 has no effect.
Moving the out 7-9 jumper between V_OUTLC2 + 12v causes out9 to always be +12v.
-
@brendon it could either be a hardware fault or a firmware bug. Can you try reverting to the last RRF version when you had it working? Alternatively, if you are comfortable loading firmware with Bossa, you can try erasing the firmware and seeing whether OUT9 comes on when you press the reset button.
-
@brendon said in "out9" appears to always be enabled:
Moving the out 7-9 jumper between V_OUTLC2 + 12v causes out9 to always be +12v.
Do you mean 12V between the two OUT9 pins, or do you mean OUT9_NEG is at +12V (so OUT9 is off)?
-
@dc42 Technically it has 'never worked'. I wired up the LED strips when I assembled the machine, but just got around to connecting them this week. How far back in firmware releases should I try?
-
@dc42 +12v between the 2 output pins.
-
@brendon it sounds to me like a hardware fault then. warranty@duet3d.com.
-
PS - if you are into hardware, you could try measuring the voltages between each end of R52 and ground. They should both be at/close to 0V for OUT9 to be off.
-
@dc42 Is it not worth downgrading the firmware to see if it works on any other versions?
-
@brendon i just replicated the same setup with a 6HC and it works fine with 3.4b5 so i think its likely that the hardware is faulty. the quickest way to check is erase it using the jumper on the board and see if it still turns on.
-
@t3p3tony If I erase it, will I have to use Bossa to re-write firmware?
-
@brendon yes you will.
-
@t3p3tony @dc42 Erasing and reflashing with Bossa did not resolve the issue. I will reach out to warranty@duet3d.com. I appreciate the assistance!
-