"Auto Bed Compensation" problems using DC42 IR Z Probe

Dear Forum,

I'm using a DC42 IR Z Probe with Duet 0.8.5 board on a cartesian printer.
Firmware Version: 1.09r-dc42 (2016-01-16) also tried version m
Web Interface Version: HTML: 1.08, JS: 1.08

My problems is that I cannot get auto bed compensation to run correctly.

The relevant parts of the config.g are:

M558 P1 X0 Y0 Z0
G31 X10.0 Y0 Z2.11 P500

I have tried 3, 4 and 5 points, but I encountered every time different problems.

With 3 points like the following I got crashes of the board.

M561
G30 P0 X0 Y0 Z-99999 H0
G30 P1 X100 Y70 Z-99999 H0
G30 P2 X200 Y140 Z-99999 H0 S0

With 5 points like the following, I got floods of error messages like "triangle is out of..." (or similar, I don't remember right now), bringing the web interface to disconnect from the board.

M561
G30 P0 X0 Y0 Z-99999 H0
G30 P1 X0 Y140 Z-99999 H0
G30 P2 X200 Y140 Z-99999 H0
G30 P2 X200 Y0 Z-99999 H0
G30 P2 X100 Y70 Z-99999 H0 S0

With 4 points I got best results working, but I could not get a good print, there was always some part to close to the bed or to far away.
I tried to use the H parameter, but was not successful.
Every time I changed one of the H parameters, it changed also other points height on the print simultaneously.
It made no sense to me, because putting pout 3 higher made also point 4 higher, but i needed point 4 lower and vice versa.
Here is an example bed.g:

M561
G30 P0 X0 Y0 Z-99999 H0
G30 P1 X0 Y140 Z-99999 H0.1
G30 P2 X200 Y140 Z-99999 H-0.2
G30 P2 X200 Y0 Z-99999 H0.2 S0

Does anybody know what I'm missing completely?
I'm really lost.

the X=0 and Y0 are wrong since the probe will be outside the Bed thats why you get the error message. try adjusting so the sensor is over the glass. as for the H problem i dont know ,it works for me.

Edited 1 time(s). Last edit at 01/30/2016 06:35PM by Darathy.

The M558-parameter also seems to be wrong. I think it should be Z2 instead of Z0. I could look later for this.

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

i have nothing else then M558 P1 H3.5

H being the start hight of the probing.

Edited 1 time(s). Last edit at 01/30/2016 07:48PM by Darathy.

You need this only (like Darathy said):

M558 P1                             ; Use a simple modulated Z probe (change to P1 for an intelligent Z probe)

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

I'm having problems with auto compensation as well - I get the following error:

Quote

AJAX alert - SyntaxError: Unexpected token a

Chrome console - Error! The following JSON response could not be parsed:
model.js:972 {"status":"I","coords":{"axesHomed":[1,1,1],"extr":[0.0],"xyz":[nan,nan,nan]},"currentTool":-1,"params":{"atxPower":1,"fanPercent":[0.00,0.00],"speedFactor":100.00,"extrFactors":[100.00]},"seq":284,"sensors":{"probeValue":173,"probeSecondary":[174],"fanRPM":0},"temps":{"bed":{"current":21.1,"active":-273.1,"state":0},"heads":{"current":[20.9],"active":[-273.0],"standby":[-273.0],"state":[1]}},"time":351.2,"coldExtrudeTemp":160,"coldRetractTemp":90,"endstops":0,"geometry":"cartesian","name":"spanky","probe":{"threshold":593,"height":0.80,"type":2},"tools":[{"number":0,"heaters":[1],"drives":[0]}]}

Running it through JSONLint, I see it's choking on the array of nan values for xyz. Why are they all NaN?

I'm not using dc42's IR probe, just the proximity sensor from Replikeo. I've just completed the bed.g file from the RRP commissioning page. Here it is:

Quote

M561 ; Zero any previous bed compensation
G1 Z10 F200 ; Move 10mm off the bed

G1 X40 Y160 F2000 ; *** First probe point
G30 P0 Z-100000 ; Probe the bed
G1 Z10 F200 ; Move back up

G1 X190 Y160 F2000 ; *** Second probe point
G30 P1 Z-100000 ; Probe the bed
G1 Z10 F200 ; Move back up

G1 X190 Y0 F2000 ; *** Third probe point
G30 P2 Z-100000 ; Probe the bed
G1 Z10 F200 ; Move back up

G1 X40 Y0 F2000 ; *** Fourth probe point
G30 P3 S Z-100000 ; Probe the bed and use the four measured points to set the bed equation
G4 P1500 ; Pause to give the web interface time to report the points
G1 Z10 ; Move back up

Perhaps I've started at the wrong corner of the bed? The documentation says to start at origin and work clockwise - on an Ormerod 2, I've assumed this is the one closest to the Y stepper motor

Edited 2 time(s). Last edit at 01/31/2016 02:29AM by 0x0000.

You have to start with X40 Y0.

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

That fixed it, thanks Treito!

Origin is always pointing to X0, Y0, Z0.

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

In my next firmware release I intend to review the whole bed probing mechanism, including making it robust and generating error messages where appropriate.

---

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].

Quote
dc42
In my next firmware release I intend to review the whole bed probing mechanism, including making it robust and generating error messages where appropriate.

<3

Ok, I got it somehow running, it was not M558, X0 Y0 Z0 means not used for homing.
Trying all possible orders of the probing points I found one (5 points) that worked and does only log one "Triangle interpolation: point outside all triangles!", not flooding the console with hundreds during print leading to connection losses.
The one is printed when the first end switch is triggered, it seems, although I'm not completely sure.
The algorithm seems very sensitive to the order of probing points.
There are still some issues, but I can print now at least, also the H parameter worked better, but I think that there is still something to improve.
Anyway, thank you dc42 for the software.

There are also web interface connection losses during print with the new firmware (r), the prior I used (m) did not have this issue.
The error is:

[Log] Error! The following JSON response could not be parsed: (model.js, line 971)
[Log] {"status":"P","coords":{"axesHomed":[1,1,1],"extr":[0.0,0.0,0.0,0.0],"xyz":[184.18,44.39,0.25]},"currentTool":0,"params":{"atxPower":1,"fanPercent":[100.00,100.00],"speedFactor":100.00,"extrFactors":[100.00,100.00,100.00,100.00]},"seq":359,"sensors":{"probeValue":540,"fanRPM":0},"temps":{"bed":{"current":-273.1,"active":-273.1,"state":0},"heads":{"current":[88.6,28.5,29.4,26.6],"active":[190.0,0.0,0.0,0.0],"standby":[0.0,0.0,0.0,0.0],"state":[2,0,0,0]}},"time":1211.5,"coldExtrudeTemp":160,"coldRetractTemp":90,"endstops":0,"geometry":"cartesian","name":"Printer","probe":{"threshold":500,"height":2.11,"type":1},"tools":[{"number":0,"heaters":[1],"drives":[0]},{"number":1,"heaters":[2],"drives":[1]},{"number":2,"heaters":[3],"drives":[2]},{"number (model.js, line 972)

The log is not complete, Safari cuts some part of...
Maybe this is of some help.

Thank you all for your help!

If that parsing error is reproducible, then it would be helpful if you can attach a Wireshark trace of the traffic to/from the Duet around the point of the error. I can think of two likely causes, and it would be helpful to know which one it is.

Another thing you can do which might be easier is to attach Pronterface as well as the web interface. When that json parsing error happens, immediately run M122 in Pronterface and tell me what buffer usage stats it reports.

---

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].

The error is reproducible, i will record the traffic and also run M122 after the error, problem is only my limited time...
I will come back to you as quick as possible.

Quote
Sergio
The error is reproducible, i will record the traffic and also run M122 after the error, problem is only my limited time...
I will come back to you as quick as possible.

No rush. I am moving home and office over the next couple of days, so unlikely to get a chance to do any more on this until later next week.

---

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].

Ok, will move this to: Link