Wrong cube calibration 20x20x80

chris4

@dc42 said in Wrong cube calibration 20x20x80:

M92 without parameters

Should now try M92 without parameters in config.h

chris4

Homing failed without M92 parameters on config.h file, have tried to send M92 on G code but nothing happens

chris4

noticed that when I move Z axis +0,5 =2mm, +5 = 20mm, +25 = 100mm up is it correct?

aidar

@chris4 said in Wrong cube calibration 20x20x80:

M92 X160.00 Y160.00 Z1600.00 E837.08

Your M92 command in config.g file should looks like this M92 X160.00 Y160.00 Z400.00 E837.08

chris4

Have tried it with M92 X160.00 Y160.00 Z1600.00 E837.08,
but it will be the same

dc42

No, send M92 without parameters from the console. It will report the current M92 settings. Use this to check that the value that you think you have set in config.g is the value being used by the firmware.

aidar

@chris4 said in Wrong cube calibration 20x20x80:

Have tried it with M92 X160.00 Y160.00 Z1600.00 E837.08,
but it will be the same

It is same, if your Z value is 1600. You should change it to 400.

chris4

@dc42 said in Wrong cube calibration 20x20x80:

No, send M92 without parameters from the console. It will report the current M92 settings. Use this to check that the value that you think you have set in config.g is the value being used by the firmware.

The answer from the console :
M92
Steps/mm: X: 160.000, Y: 160.000, Z: 1600.000, E: 837.080

And from config.h
M92 X160.00 Y160.00 Z1600 E837.08 ; set steps per mm

Phaedrux

Change your config.g

M92 Z1600 should be M92 Z400

droftarts

@Phaedrux that’s six times now we’ve told him to change Z1600 to Z400!

Ian

Phaedrux

@droftarts Ten if you count the times I've shouted it at the screen.

chris4

@droftarts
have tried with the M92 Z400 it too but it will be the same height on the Z axis.
Changing the Z steps/mm from 1600 to 400 cannot fail to reduce the Z height by a factor of 4.

chris4

@droftarts
have tried with the M92 Z400 it too but it will be the same height on the Z axis.
Changing the Z steps/mm from 1600 to 400 cannot fail to reduce the Z height by a factor of 4.

chris4

@Phaedrux
have tried with the M92 Z400 it too but it will be the same height on the Z axis.
Changing the Z steps/mm from 1600 to 400 cannot fail to reduce the Z height by a factor of 4.

aidar

How have you "tried" this? Have you changed your config file? Btw its config.g, not config.h

deckingman

@aidar said in Wrong cube calibration 20x20x80:

Btw its config.g, not config.h

@chris4 Repeat - Change the M92 in CONFIG.G from 1600 to 400

chris4

@deckingman
As I had written earlier in posts I have tried with the Z400 in config.g
And it became the same height on the Z axis (80mm).
because you said, I have tested again and it became the same height (80 mm)

Phaedrux

Post your entire config.g please.

chris4

; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat Mar 07 2020 00:00:28 GMT+0100 (centraleuropeisk normaltid)

; General preferences
G90                                     ; send absolute coordinates...
M83                                     ; ...but relative extruder moves
M550 P"My Printer"                      ; set printer name

; Network
M552 S1                                 ; enable network
M586 P0 S1                              ; enable HTTP
M586 P1 S0                              ; disable FTP
M586 P2 S0                              ; disable Telnet

; Drives
M569 P0 S1                              ; physical drive 0 goes forwards
M569 P1 S1                              ; physical drive 1 goes forwards
M569 P2 S0                              ; physical drive 2 goes backwards
M569 P3 S0                              ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3                        ; set drive mapping
M350 X16 Y16 Z16 E16 I1                 ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z400 E837.08       ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00     ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00     ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30            ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                        ; set axis minima
M208 X260 Y240 Z240 S0                  ; set axis maxima

; Endstops
M574 X1 Y1 Z1 S1                        ; set active low and disabled endstops

; Z-Probe
M558 P0 H5 F120 T6000                   ; disable Z probe but set dive height, probe speed and travel speed
M557 X15:215 Y15:195 S20                ; define mesh grid

; Heaters
M305 P0 T100000 B4138 R4700             ; set thermistor + ADC parameters for heater 0
M143 H0 S120                            ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700             ; set thermistor + ADC parameters for heater 1
M143 H1 S280                            ; set temperature limit for heater 1 to 280C

; Fans
M106 P0 S0 I0 F500 H-1                  ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45               ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 D0 S"TitanAero" H1 F0           ; define tool 0
G10 P0 X0 Y0 Z0                         ; set tool 0 axis offsets
G10 P0 R0 S0                            ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

droftarts

@chris4 your config.g is correct, with z400 in the M92 command. But have you reset the printer, or power off/power on, or sent M999, or pressed emergency stop in DWC, or sent M98 P”config.g”?

Because the settings in config.g won’t take effect until the machine is rebooted, or the config.g is run again.

I suggested you sent M92 Z400. I didn’t specify how to do this, unfortunately. You can send gcode commands directly in the DWC, in the console window, to see the response. This is also where you can send M92 on its own to see the current setting.

I’m sorry if this is not obvious to someone who is new to Duet, but most of these basic interactions are covered in the documentation.

Ian