No Calibration and no compensation….Grrrpffddsdf!!!!!!!!!!!

dc42

So you need H505 in the M665 command, not H550.

Dougal1957

ok in that case you have an error in your Config.g

This line M665 R165 L360.25 B175 H550 needs to be M665 R165 L360.25 B175 H505

Also until you have it successfully calibrated comment out the M501 line at the end

peirof

ok…

later try...

This, change [c]M665 R165 L360.25 B175 H550[/c] for [c]M665 R165 L360.25 B175 H505[/c], can be the cause for autocalibration causes a headcrash?

If i send a [c]AUTOCALIBRATION[/c]…. they should not stop the movement of Nozzle, when ZStop was on? When head reach bed, whatever the order M665

peirof

Results of [c]M122[/c], in case it gives more information:

[[language]]
M122
=== Diagnostics ===
Used output buffers: 3 of 32 (8 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20 running on Duet WiFi 1.0
Board ID: 08DGM-95BNL-MGPSN-6JKDL-3S06L-92W7W
Static ram used: 15448
Dynamic ram used: 99024
Recycled dynamic ram: 216
Stack ram used: 1392 current, 4504 maximum
Never used ram: 11880
Last reset 00:03:12 ago, cause: power up
Last software reset at 2018-01-20 12:49, reason: User, spinning module GCodes, available RAM 7784 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 24.7, current 32.8, max 32.9
Supply voltage: min 24.6, current 24.7, max 24.9, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2018-01-21 07:28:43
Cache data hit count 735649989
Slowest main loop (seconds): 0.075306; fastest: 0.000041
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
Network state is running
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.20
WiFi MAC address 2c:3a:e8:0b:05:a1
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 13960
WiFi IP address 192.168.1.106
WiFi signal strength -66dBm, reconnections 0, sleep mode modem
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

Dougal1957

@peirof:

ok…

later try...

This, change [c]M665 R165 L360.25 B175 H550[/c] for [c]M665 R165 L360.25 B175 H505[/c], can be the cause for autocalibration causes a headcrash?

If i send a [c]AUTOCALIBRATION[/c]…. they should not stop the movement of Nozzle, when ZStop was on? When head reach bed, whatever the order M665

Yes because in the M558 line you have H10 this tells the firmware to run down to the bed (H550 in your M665) to 10 mm short at high speed then slow down to probe for the last 10mm because you have the starting hight set to 45mm longer than you Z Actually is it tries to travel to 35mm below the bed before it starts to probe.

The other thing you could do is to increase the H Value in the M558 to say 60 and try it but do remember that once the Calibration has finished and you put the correct figures into your Config.g (And you should do this) then you will have to reduce that M558 H back down to 10 or even 5.

Hope this helps

Doug

peirof

I have a dude…

i do this:

1- Power on Duet printer
2- Homing
3- Test Z-Probe (Mini IR Sensor). Seems work, in DWI, Zprobe=538
...
and the problems
...
4- Test autocalibrate
5- The nozzle goes down slow
, in the way i put an obstable in Mini Ir Sensor, the same works, zprobe=558... but movement dont stops
6- Power off printer for avoid headcrash

why dont stops to go down?
G30 S-1... works, object stops go down nozzle

peirof

More info…

Bed compensation.... WORKS!!!!!!!

Why "cojones" [c]autocalibration[/c] fail??????????????????????

peirof

Hi,

Bed compensation works…. but strange results...

When you makes a [c]calibration[/c], Duet do the[c] bed.g[/c] contents, no?

my bed.g, for if someone can see the fail….

[[language]]
; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool on Sun Jan 21 2018 07:57:47 GMT+0100 (Hora estándar romance)
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 Y154.58 H0 Z-99999
G30 P1 X87.61 Y120.59 H0 Z-99999
G30 P2 X138.78 Y45.09 H0 Z-99999
G30 P3 X138.78 Y-45.09 H0 Z-99999
G30 P4 X87.61 Y-120.59 H0 Z-99999
G30 P5 X0 Y-154.58 H0 Z-99999
G30 P6 X-91.11 Y-125.4 H0 Z-99999
G30 P7 X-147.41 Y-47.9 H0 Z-99999
G30 P8 X-147.41 Y47.9 H0 Z-99999
G30 P9 X-91.11 Y125.4 H0 Z-99999
G30 P10 X0 Y76.76 H0 Z-99999
G30 P11 X60.2 Y34.76 H0 Z-99999
G30 P12 X60.2 Y-34.76 H0 Z-99999
G30 P13 X0 Y-76.76 H0 Z-99999
G30 P14 X-67.12 Y-38.75 H0 Z-99999
G30 P15 X-67.12 Y38.75 H0 Z-99999
G30 P16 X0 Y0 H0 Z-99999 S6
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

Another strange thing, is when i do a single [c]G30 S-1[/c], works. But when i try to [c]calibrate.g[/c], a series of G30 gcodes….DON'T WORK...

dc42

1. In your M558 command, aset a high H value for now (e.g. H40) until you have calibration working.

2. If that doesn't help, what happens if you send the first G30 lin from your bed.g file, i.e. G30 P0 X0 Y154.58 H0 Z-99999 ?

3. Confirm that X0 Y154.58 is reachable by the IR sensor, and not off the edge of the bed or closer than 10mm to the edge.

peirof

More info…

i have try, to do 1 line of [c]bed.g[/c], by console.

I have sended [c]G30 P0 X0 Y154.58 H0 Z-99999[/c], and…

The first thing, this command by console don't works.

In this moment, i have sended [c]G30 X0 Y154.58 H0 Z-99999[/c], without P0 and… partially works, the nozzle goes down, until Zprobe trigger, and stop the movement, until this point works, but the nozzle dont go to [c]X0 Y154.58[/c], the test is meassured WHERE THE NOZZLE WAS…. i dont know if this behavoir is normal...

NOTE: i have read the message of DC42, after post...

peirof

RESPOND

@dc42:

1. In your M558 command, aset a high H value for now (e.g. H40) until you have calibration working.

2. If that doesn't help, what happens if you send the first G30 lin from your bed.g file, i.e. G30 P0 X0 Y154.58 H0 Z-99999 ?

3. Confirm that X0 Y154.58 is reachable by the IR sensor, and not off the edge of the bed or closer than 10mm to the edge.

1- In this moments, i have this [c]M558 P1 Z1 H40 F120 T4800[/c], think this change yesterday, i haved read in forum

2- This is what I just tried and commented on the previous post

3- In teory, yes. The bed has 310 mm of diameter/2= 155 mm, in the limit, i go to down this measure

peirof

NEWS!!!!!!!!!!!!!!!!!!!!!!!!!!!!

WORKS….WORKS..... WORKS.......

DC42.....YOU ARE THE BEST........

MANY THANKS ..... MILLIONS OF THEM. If you come to Valencia (Spain) you are invited to a Paella Valenciana