Why does G0 G1 move code turn off aux. fan?

I don't understand why if I issue a M106 S255 in the gcode console (or in a file) to turn on the fan, it remains on until the next G0 or G1 move is issued.
I expect the fan to stay on until M107 is received.

This is with RepRapFirmware-1.09a-dc42.bin but I doubt that makes a difference - I'm guessing its more fundamental

---

RS Components Reprap Ormerod No. 481

Quote
Radian
I don't understand why if I issue a M106 S255 in the gcode console (or in a file) to turn on the fan, it remains on until the next G0 or G1 move is issued.

That is expected behaviour if you have used the M571 command to repurpose the fan output pins to follow extrusion. Otherwise, it should indeed remain on until you use M106 or M107 to turn it off. I'm not aware of version 1.09a of my fork having a bug in that area, but if you are sure you have not used M571 then I suggest you try my latest version (1.09c) anyway.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Hi dc42, yes, as you probably guessed I'm using the Duet in a Laser but I've not issued a M571 for several power cycles - I'm trying an Inkscape Laser pulg-in that issues M106/M107 commands to enable the laser inline with the Gcode.

I can see no reason for M571 to stick around between power cycles (how else would it be disabled?) so after switching on, sending the following ought to keep the laser on for the cut (which it isn't):

G21		; set units to millimeters
G90		; use absolute coordinates
G0 F3000	; 50mm/s
G0 X0 Y0	; go to 0,0
M106 S255	; turn on fan to max. (laser)
G4 P100		; pause 100ms (to see it spark at the very least)
G1 X100 Y100	; cut to 100,100
M107 S0		; turn off fan (laser)

I've got to haul the Laser to a PC to update the firmware so I'll try that next thanks.

---

RS Components Reprap Ormerod No. 481

So, I just updated the firmware and get exactly the same issue.

Straight after flashing with 1.09c I enter M106 S255 in the web console and see the Fan driver go on. Then I enter G0 X0 Y0 and the fan driver goes off. This shouldn't be happening.

---

RS Components Reprap Ormerod No. 481

Quote
Radian
So, I just updated the firmware and get exactly the same issue.

Straight after flashing with 1.09c I enter M106 S255 in the web console and see the Fan driver go on. Then I enter G0 X0 Y0 and the fan driver goes off. This shouldn't be happening.

Sorry, I can't reproduce that. The fan stays on for me after the G1 X0 Y0. You could try sending M571 with no parameters, to see if the firmware thinks extrusion PWM is set nonzero.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

M571 reported Extrusion ancillary: 1.000 directly after a firmware flash so its either the default or held in nv ram? Setting to 0 fixes it anyway so that's great thanks.

---

RS Components Reprap Ormerod No. 481

The ancilliary PWM is set to 0.0 in the init code, I checked. It isn't stored in NVRam, and in any case nvram doesn't survive flashing the firmware.

Are you quite certain that you don't have a M571 command in config.g? If you run config.g again using M98, does it set the ancilliary pwm to 1 again?

Edited 1 time(s). Last edit at 07/28/2015 05:28PM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

That was it dc42! Sorry for the nuisance. I thought I had cleared that out from the config file when I moved it into slic3r setup codes a while ago. Out of sight, out of mind. Well, I'm obviously out of my mind.

---

RS Components Reprap Ormerod No. 481