delta smart effector hightmap mess

Phaedrux

Try updating to 3.2.2 by uploading this zip file as is to the system tab.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip

Such an exaggerated cone shape of the heightmap seems to indicate a rod length problem based on this: http://boim.com/DeltaUtil/CalDoc/Calibration.html

I've never seen anything so extreme though.

Can you post your bed.g as well?

Lihyon

im going to make the firmware update now.
The rods i got are made by Haydn Huntley's and labeled each 440.35 one of them is 440.34

i tried a couple different bed.g files. My understanding was that the bed.g isn't used for g29 which is run before delta calibration G32 but for all i know this might be totally wrong.
On the side i ordered another smart effector.

M561                    ; clear any bed transform

; If the printer hasn't been homed, home it
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
  G28

; Probe the bed and do auto calibration
G1 X0 Y0 Z10 F10000        ; go to just above the first probe point
while true
  if iterations = 5
    abort "too many auto calibration attempts"
  G30 P0 X0.00 Y150.00 Z-99999 H0
  if result != 0
      continue
  G30 P1 X96.42 Y114.91 Z-99999 H0
  if result != 0
      continue
  G30 P2 X147.72 Y26.05 Z-99999 H0
  if result != 0
      continue
  G30 P3 X129.90 Y-75.00 Z-99999 H0
  if result != 0
      continue
  G30 P4 X51.30 Y-140.95 Z-99999 H0
  if result != 0
      continue
  G30 P5 X-51.30 Y-140.95 Z-99999 H0
  if result != 0
      continue
  G30 P6 X-129.90 Y-75.00 Z-99999 H0
  if result != 0
      continue
  G30 P7 X-147.72 Y26.05 Z-99999 H0
  if result != 0
      continue
  G30 P8 X-96.42 Y114.91 Z-99999 H0
  if result != 0
      continue
  G30 P9 X0.00 Y75.00 Z-99999 H0
  if result != 0
      continue
  G30 P10 X64.95 Y37.50 Z-99999 H0
  if result != 0
      continue
  G30 P11 X64.95 Y-37.50 Z-99999 H0
  if result != 0
      continue
  G30 P12 X0.00 Y-75.00 Z-99999 H0
  if result != 0
      continue
  G30 P13 X-64.95 Y-37.50 Z-99999 H0
  if result != 0
      continue
  G30 P14 X-64.95 Y37.50 Z-99999 H0
  if result != 0
      continue
  G30 P15 X0 Y0 Z-99999 S8
  if result != 0
      continue

  if move.calibration.final.deviation <= 0.07
    break
  echo "Repeating calibration because deviation is too high (" ^ move.calibration.final.deviation ^ "mm)"
; end loop
echo "Auto calibration successful, deviation", move.calibration.final.deviation ^ "mm"

G30 S-3
G1 Z50

; Probe the bed at 6 peripheral and 3 halfway points, and perform 6-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 16 points, 6 factors, probing radius: 170, probe offset (0, 0)
; Auto calibration routine for large delta printer
;M561                    ; clear any bed transform

; If the printer hasn't been homed, home it
G28

; Probe the bed and do auto calibration
G1 X0 Y0 Z10 F10000        ; go to just above the first probe point
G30 P0 X0.00 Y190.00 Z-99999 H0
G30 P1 X122.13 Y145.55 Z-99999 H0
G30 P2 X187.11 Y32.99 Z-99999 H0
G30 P3 X164.54 Y-95.00 Z-99999 H0
G30 P4 X64.98 Y-178.54 Z-99999 H0
G30 P5 X-64.98 Y-178.54 Z-99999 H0
G30 P6 X-164.54 Y-95.00 Z-99999 H0
G30 P7 X-187.11 Y32.99 Z-99999 H0
G30 P8 X-122.13 Y145.55 Z-99999 H0
G30 P9 X0.00 Y95.00 Z-99999 H0
G30 P10 X82.27 Y47.50 Z-99999 H0
G30 P11 X82.27 Y-47.50 Z-99999 H0
G30 P12 X0.00 Y-95.00 Z-99999 H0
G30 P13 X-82.27 Y-47.50 Z-99999 H0
G30 P14 X-82.27 Y47.50 Z-99999 H0
G30 P15 X0 Y0 Z-99999 S7

G1 Z50

M561 ; clear any bed transform
G28  ; home all towers
; Probe the bed at 10 peripheral and 6 halfway points, and perform 6-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y184.9 H0 Z-99999
G30 P1 X108.68 Y149.59 H0 Z-99999
G30 P2 X175.85 Y57.14 H0 Z-99999
G30 P3 X175.85 Y-57.14 H0 Z-99999
G30 P4 X108.68 Y-149.59 H0 Z-99999
G30 P5 X0 Y-184.9 H0 Z-99999
G30 P6 X-108.68 Y-149.59 H0 Z-99999
G30 P7 X-175.85 Y-57.14 H0 Z-99999
G30 P8 X-175.85 Y57.14 H0 Z-99999
G30 P9 X-108.68 Y149.59 H0 Z-99999
G30 P10 X0 Y92.4 H0 Z-99999
G30 P11 X80.02 Y46.2 H0 Z-99999
G30 P12 X80.02 Y-46.2 H0 Z-99999
G30 P13 X0 Y-92.4 H0 Z-99999
G30 P14 X-80.02 Y-46.2 H0 Z-99999
G30 P15 X-80.02 Y46.2 H0 Z-99999
G30 P16 X0 Y0 H0 Z-99999 S6

Lihyon

it fails to upload the firmware files
Edit: i managed to install it

Lihyon

@Lihyon said in delta smart effector hightmap mess:

it fails to upload the firmware files
Edit: i managed to install it

the results aren't much different

Number of points: 277
Probing radius: 185 mm
Probe area: 1075.2 cm²
Maximum deviations: -0.870 / 15.173 mm
Mean error: 7.258 mm
RMS error: 4.668 mm

Phaedrux

bed.g is G32.

What order are you running things? There should be G28 to home the towers, G32 to do an auto calibration, and then G29 to map the bed surface.

engikeneer

@Lihyon Looking at the errors in your results, one point is measured 15mm above the z=0 datum!

In your bed.g, you need to uncomment the M561 to make sure you don't have mesh compensation enabled when ddoing the calibration. if you don't it will be calibrating a mesh-compensated bed and you'll only bake in the errors you're seeing in your heightmap.

Lihyon

@Phaedrux i found my biggest mistake so far, its silly

M665 R190 L440.35 B190 H415                           ; Set delta radius, diagonal rod length, printable radius and homed height

R is supposed to be R230.6.
and i was running M561 - g29 s2 - g29 - g32 but i guess im suppose to do g32 - g29 so i added g29 on the end of my bed.g for now

now im facing this issue that the probe doesn't trigger at some point and runs into the bed but not right away like halve way through probing

21.3.2021, 22:02:40	Error: Z probe was not triggered during probing move   while g29
21.3.2021, 21:58:29	Z probe trigger height set to 0.018 mm                  G30 S-3 included in bed.g
21.3.2021, 21:58:28	G32
Calibrated 8 factors using 16 points, (mean, deviation) before (-0.643, 0.353) after (-0.000, 0.037)
Auto calibration successful, deviation 0.037mm

Lihyon

@engikeneer but M561 disables any existing bed compensation or not?
EDIT: well i tried and didn't make a difference

Lihyon

This post is deleted!

Phaedrux

Maybe a sensitivity issue?

https://duet3d.dozuki.com/Wiki/Smart_effector_and_carriage_adapters_for_delta_printer#Section_Commissioning

Lihyon

setting the sensitivity just doesn't work its suppose to blink 3 times when changed but does not

example
M672 S105:25:255

i found the firmware for it but im struggling to find out how to use Atmel Studio 7 to compile it or upload it

https://github.com/Duet3D/SmartEffectorFirmware

Phaedrux

How old is the smart effector? Does it have a revision number on the PCB?

What does it respond with if you send M672 by itself?

Lihyon

its says pcb Revision 2.0 CERL OHL 1.2 on it
and M672 spits out

Error: M672: No program bytes provided

dc42

@Lihyon said in delta smart effector hightmap mess:

setting the sensitivity just doesn't work its suppose to blink 3 times when changed but does not
example
M672 S105:25:255
i found the firmware for it but im struggling to find out how to use Atmel Studio 7 to compile it or upload it

https://github.com/Duet3D/SmartEffectorFirmware

You don't need to build it, you can download the .elf or .hex file from the release at https://github.com/Duet3D/SmartEffectorFirmware/releases/tag/2.01.

garyd9

@Lihyon said in delta smart effector hightmap mess:

setting the sensitivity just doesn't work its suppose to blink 3 times when changed but does not

I've noticed oddities with changing the sensitivity of the smart effector. At times, the smart effector seems to lose the sensitivity setting (often after a reset or power off/on) and it has to be set again.

When this happens, about 50% of the time sending either the "set" (M672 S105:aaa:bbb) or "revert" (M672 S131:131) commands does nothing whatsoever in regards to the smart effector LED and I have to power it off/on again.

My suggestion would be to power off the machine, wait 10 seconds, and power it back on again. Then set the sensitivity and see if the smart effector responds properly. (It should blink 4 times in response.)

example
M672 S105:25:255

That's not a valid combination. If the first number is 25, the second number should be
230 (255-25 = 230)

Lihyon

Thank you for everyone's help i really appreciate it !
After installing a new smart effector it seems to work !

@dc42 after uploading .hex to the printer it saves my sensitivity
@garyd9 that was the last puzzle piece i completely misunderstood the instructions given

To program the sensor, send command M672 S105:aaa:bbb replacing aaa by the desired sensitivity and bbb by 255 - aaa.

garyd9

@Lihyon said in delta smart effector hightmap mess:

@dc42 after uploading .hex to the printer it saves my sensitivity

Umm.. I thought the only way to update the smart effector's firmware was using special hardware.

Is that ability built into the duet firmware now? (I'd love to get that fix on my smart effector, but didn't think it would be feasible for me.)

Lihyon

@garyd9 i got no clue how the firmware works, but when i remove the hex it only flashes 2 times when i turn on the printer and when i include it i get 3 flashes because of my config. its wierd and i wont question it

garyd9

@lihyon said in delta smart effector hightmap mess:

@garyd9 i got no clue how the firmware works, but when i remove the hex it only flashes 2 times when i turn on the printer and when i include it i get 3 flashes because of my config. its wierd and i wont question it

(Edit: due to the forum s/w change, I lost track of a reply)

In another thread, @dc42 suggested that the firmware can only updated via special hardware. Just sticking the .hex file on the duet isn't enough:

https://forum.duet3d.com/topic/22399/smarteffector-sensivity-unable-to-change-it

Phaedrux

@garyd9 Yeah I'm curious what's actually going on with the hex file being present in the sys folder would actually do.