Here's a question... is it a problem to call G31 with a different Z-trigger height from the slicer's "start up" gcode block? I've also been thinking about using G92 to change the current Z position after homing. My thinking is to just offset the known current height (post home) with the delta between the two G31 calls in my original post. I was also thinking about using M206 with one of the material types to express the offset delta. If anyone else has ideas, I'd appreciate it. If it helps, I'm using S3D for my slicer. Thanks!

@bearer Fair comments. Just bear in mind that almost all gcodes can be input at any time - even "on the fly". Sometimes that can useful....

@dc42 you are amazing there was a M307 H2 in the config override g, i removed it and rebooted and all works like a charm. i have included my override g just to see if there is anything that shoudent be there. the line g code now works i owe you a drink ; config-override.g file generated in response to M500 at 2019-03-26 17:29 ; This is a system-generated file - do not edit ; Heater model parameters M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1 M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0 M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0 M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0 M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0 M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0 M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0 G10 L2 P1 X0.00 Y0.00 Z0.00 G10 L2 P2 X250.00 Y420.00 Z59.00 G10 L2 P3 X0.00 Y0.00 Z0.00 G10 L2 P4 X0.00 Y0.00 Z0.00 G10 L2 P5 X0.00 Y0.00 Z0.00 G10 L2 P6 X0.00 Y0.00 Z0.00 G10 L2 P7 X0.00 Y0.00 Z0.00 G10 L2 P8 X0.00 Y0.00 Z0.00 G10 L2 P9 X0.00 Y0.00 Z0.00

Thank's that was it. Now it works again.

I'll put an adheisve magnetic sheet on top of the aluminium, the steel sheet will then stick to the magnet. Meanwhile ahesive PEI straight on the aluminium. Its good to 120C so hopefully it'll cover my needs for ABS and PETG for now. With the bed being 120x120mm I only use about 70 watt or so, so I went with the small SSR modules with 2 channels, so I can add enclosure heater from the same heater wire. SSR only get up to 30C wihtout heatsink or active cooling at that load so it'll be fine as it is.

@dc42 said in Duet 2 Maestro Error: Short-to-ground on drivers 1: M569 P1 Gcode reports the following. Connecting... Printer is now online. M569 P1 SENDING:M569 P1 Drive 1 runs in reverse, active low enable, step timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, tpwmthrs 2000 (4.7 mm/sec) What have I done wrong again

@dc42 Oh how do you cancel the old one? I had assuming the new trigger declaration would over write the old one...

The Slice thermistor has extremely high resistance at low temperatures and will report as min temp on most firmwares using standard thermistor tables. The table linked here needs to be defined: https://docs.google.com/spreadsheets/d/e/2PACX-1vTHfmSmnGNEuHzjCHEjkA9_DUgnCD9z5E_7Gk1BjUgBYEBtJ6Dlj3hhnFuhFeOfnIc_7zE69VS1tAbx/pubhtml

@paboman No, this file is only for the Wifi version.

@Phaedrux @dc42 @davea Success A big thanks to all of You for Your help and Your patience. It's greatly appreciated. It's a bummer that I can't return the favor. At least not any time soon... I'm officially retracting my claim in my first ever post on here, that I thought I understood the basics of how the Duet boards work. That's clearly not the case, but I hoping to slowly learn as I go along in this endeavor.

0_1553613727447_heightmap.csv Delta height map

@dc42 the processor is in right orientation. I have got this thing soldered by a professional, and I myself have verified that its touching the right places! can the clock go bad in this??

The heating fault occurred nearly 2 hours before the communications error. In recent firmware versions, the default behaviour when there is a heating fault is to give you a few minutes to sort it out, and if you don't then it assumes the machine is unattended and tries to shut it down.

They are very different types of connection. You can probably get die sets which would allow one handle to be used, but this is usually the more expensive option.

@martin1454 great! thank you!

I have installed: Firmware Name: RepRapFirmware for Duet Firmware Electronics: Duet 0.85 Firmware Version: 1.24beta2+1 (2019-03-25b5) Web Interface Version: 1.22.6 Settings in config.g: M307 H0 A463.6 C845.6 D3.3 S1.00 B0 M307 H1 A432.5 C186.7 D8.1 S1.00 B0 M307 H5 A-1 C-1 D-1 ; Disable Heater M307 H4 A-1 C-1 D-1 M307 H3 A-1 C-1 D-1 M307 H2 A-1 C-1 D-1 ; heater6 shares pin with fan1, so do not use M563 P0 D0 H1 ; Define tool 0 with 'extruder drive 0' and 'heater 1', default fan 0 M106 P0 S0.1 I0 F100 H-1 M106 P1 S0.3 I0 F100 H-1 Duet 0.85 is sitting on the test bench with termistor on bed input and a resistor on E0 input so the reading is 83.7 degC. M106 P2 and P3 are possible, but the mapping with A parameter is all over the place. So i tried to find out whats going on with P1. Measures are at fan header F0 and F1, heater header on 50pin connector H3 (pin 18), H4 (pin 21), H5 (pin 22) and E1 heater with oscilloscope. After reboot: F0 PWM ok and you can adjust it, F1 PWM ok and you can adjust it, BUT same signal(inverted) on H3, this is wrong H4, H5 low M106 P1 I-1 (disable F1): F1 low H3 low M106 P1 A2 S0.5: E1 heater PWM ok H3, H4, H5 low M106 P1 I-1: E1 heater off, ok M106 P1 A3 S0.5: PWM on E1 heater (wrong) H3, H4, H5 low M106 P1 I-1: E1 heater off M106 P1 A4 S0.5: PWM on F1 and H3(inverted to F1) (wrong) H4, H5 low M106 P1 I-1: F1 low (LED lit), H3 high H4, H5 low M106 P1 A5 S0.5: F0 !! PWM is set to 0.5 (very wrong) you can set F0 with P0 AND P1 H3 high, H4, H5 low M106 P1 I-1: F0 low (LED lit), no pwm on F0 M106 P0 S0.2 brings PWM back on if I now use P2 I get the same behavior. I hope you can solve it.

See https://duet3d.dozuki.com/Wiki/How_to_include_a_web_camera_image_in_Duet_Web_Control for how to include a camera image in DWC.

It's often necessary to run the side-to-side bed levelling more than once, because the effect of adjusting the leadscrews on the bed tilt isn't quite the same as theory predicts. The important thing is that when you run it multiple times, the corrections it makes are smaller each time. If it consistently under-corrects, use the M671 F parameter to force an over-correction.

Did you run the individual motor tests as I suggested? You should also be able to move 2 or 3 motors together, for example to move both X and Y motors you can do this: G91 G1 S2 X10 Y10

Go to System and use the "upload system files button" in DWC2.