@Ethelred
To get further help you're going to need to state the firmware versions for duet, paneldue and DWC
Also whether your running stand alone or SBC
Plus the results of M112 and M98 P"config.g"
You should not need to send M292 explicitly (and I don't see where you have)
I am not experiencing the same issue on my Duet 2 using RRF3.5b4 and the latest PanelDue firmware (not near the machine to check"
@Ethelred it should be possible to use the E1 heater output to drive a small DC motor, however you will need to connect a flyback diode in parallel with the motor because Duet 2 does not have flyback diodes on the heater outputs. Without the flyback diode, the back emf from the motor will burn the mosfet out. Connecting the flyback diode the wrong way round will also burn the mosfet out.
The heater pins on the expansion header provide 3.3V at low current, so not suitable for driving a motor directly.
@ethelred input shaper should be ei3 not e13.
It's showing on paneldue but not DWC because DWC is loading later.
Run M98 P"config.g" to see what errors you have
@alankilian
Thanks to all heaters finally sorted. Mainly typos with a spoonful of stupidity.
Installed 3.4.1 and did a character by character proof.
No, not 137F ( a pleasant 82F today). The displayed 57c was, I guess, a clever artifact of my config.g construct.
For 3d printing G0 and G1 are the same? I believe laser and/or CNC mode they differ, where G0 will be a rapid move at machine max speed and G1 will move at whatever feedrate specified.
That's correct; except for one other difference between G0 and G1 on some architectures. A G0 move will not necessarily be done in a straight line, if a curved move is simpler and potentially faster and does not result in Z dropping below the straight-line value. So on a SCARA or Polar machine, the move will not be segmented to approximate a straight-line move, instead it will be executed as a single move.
@dc42 Simple solution at last - had I but known of the pesky T0 tool set in config.sys. As you must know ( but I didn't ) the "T-1 P0" is inoperative if a tool selection has already been made. Re-reading the g-code Tools section doesn't seem to me to make that point.
One semi-related opinion from me is that it would be helpful in these situations if there were a line-by-line g-code step-through ( or at least an ability to set break points ). I think I might have quickly determined the problem.
It can be reproduced even with newest 2.1.8. Load the page, force reload (ctrl+f5), type any command in the input field and press the button. Nothing happens. Press again and it sends, and seems to work untill a new force reload.
In the source there is a comment "// FIXME There must be a better solution than this", so I guess chrishamm is aware.
Replacement probe arrived and installed. Works perfectly and converged at 0.003mm - good enough for government work. I must have somehow bumped or otherwise disturbed the optical alignment.
AND the good news is the latest I-R probes now have surface mount emitter/detector optics which are impossible to move out of alignment. Thanks DC42 or Tony or whoever.
@T3P3Tony I get this too but I'm on a slightly earlier version of DWC (2.0.0-RC8-b4) and using Firefox. There are certain window widths where I get 3 digits and others where I only get 1 or 2. Toggling side bars on or off has the same effect.
Edit. To test, just click on the active temperature to bring up the drop down list, then drag the right hand edge of the window to make it smaller. It will "jump" to 3 digits at various window widths.
