Delta semi-automatic calibration (M558 P0) along X axis instead of Z
I'm using delta printer without z-probe. I used to use semi-automatic calibration many times before (using DWC, where popup with up-down controls for Z axis shown). Today I replaced hotend heater block and decided to re-calibrate printer, but I ran into an incomprehensible problem - instead of up/down (Z axis) controls DWC shows me controls for X axis:
[[language]] Adjust height until the nozzle just touches the bed, then press OK Use the following controls to adjust X:
Seems like I should change something in configs after upgrading to firmware version 1.19, but I don't understand where I'm wrong.
Current firmware version is:
[[language]] Firmware Name: RepRapFirmware for Duet WiFi Firmware Electronics: Duet WiFi 1.0 Firmware Version: 1.19 (2017-08-14) WiFi Server Version: 1.19 Web Interface Version: 1.19
[[language]] M561 ; clear any bed transform, otherwise homing may be at the wrong height G31 X0 Y0 ; don't want any probe offset for this G30 P0 X0 Y75 Z-99999 G30 P1 X64.95 Y37.5 Z-99999 G30 P2 X64.95 Y-37.5 Z-99999 G30 P3 X0 Y-75 Z-99999 G30 P4 X-64.95 Y-37.5 Z-99999 G30 P5 X-64.95 Y37.5 Z-99999 G30 P6 X0 Y0 Z-99999 S6 G1 X0 Y0 Z150 F4000 ; get the head out of the way of the bed
[[language]] M111 S0 ; Debug off M550 PMiniKossel ; Machine name and Netbios name (can be anything you like) M552 S1 ; Enable WiFi M551 Preprap ; Machine password (used for FTP) M555 P2 ; Set output to look like Marlin G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M569 P0 S1 ; X M569 P1 S1 ; Y M569 P2 S1 ; Z M569 P3 S0 ; E M574 X2 Y2 Z2 S1 ; set endstop configuration (all endstops at high end, active high) M92 X100 Y100 Z100 E450 ; Set axis steps/mm M201 X3000 Y3000 Z3000 E3000 ; Accelerations (mm/s^2) M203 X12000 Y12000 Z12000 E4200 ; Maximum speeds (mm/min) M350 X16 Y16 Z16 E16 I1 ; Set 16x microstepping with interpolation M566 X600 Y600 Z600 E600 ; Maximum instant speed changes mm/minute M906 X1500 Y1500 Z1500 E1000 I60 ; Set motor currents (mA) M665 R105.70 L214.35 H239.36 B85.00 X-0.48 Y-0.80 Z0.00 M666 X1.51 Y-1.03 Z-0.48 M563 P0 D0 H1 ; Define tool 0 G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures M106 P1 T50 H1 ; Thermostatic fan M558 P0 ; No Z probe present M556 S100 X0 Y0 Z0 ; Axis compensation here M208 S1 Z-0.3 ; set minimum Z M106 P0 L0 ; Minimum fan speed M143 H0 S130 ; Maximum bed temperature M143 H1 S270 ; Maximum hotend temperature M305 P0 T100000 B4388 R4700 H0 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction M305 P1 T100000 B4725 R4700 H0 L0 C7.060000e-8 M307 H0 A250.8 C426.6 D7.7 B0 ; Heater 0 model: gain 250.8, time constant 426.6, dead time 7.7, max PWM 1.00, in use: yes, mode: PID M307 H1 A681.8 C179.0 D7.0 S1.00 B0 ; Heater 1 model: gain 681.8, time constant 179.0, dead time 7.0, max PWM 1.00, mode: PID M570 H0 T25 ; Permitted temperature excursion from the setpoint for this heater M570 H1 T25 ; Permitted temperature excursion from the setpoint for this heater M501 ; load sys/config-override.g T0 ; select first hot end
I think you are using incompatible versions of DWC and RRF. Use a more recent version of RRF or an older version of DWC.
It seems for me that I'm using latest available release version:
But anyway I will try to re-upload & update, thank you.
Upgrading to latest stable firmware files that available on github (1.19) did not fix this issue.
But latest edge version is working OK (1.20beta10). I hope beta10 stable enough for production printing
Latest stable firmware uis 1.19,2, not 1.19. See https://github.com/dc42/RepRapFirmware/releases.
There have been reports of some layer shift issues with 1.20beta10. I haven't been able to reproduce these yet.
Oh… thank you again. I thought that latest version is available here: https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-WiFi/Stable
I did not think of looking at the releases page at github at https://github.com/dc42/RepRapFirmware/releases
I will try to downgrade back to 1.19.2.
Yes, I need to remove the "Stable" folders, because stable versions are now released using the Github Release mechanism.
Yes, I need to remove the "Stable" folders
By the way, this was useful for those who know about [c]git pull[/c] command. I'm one of those who used this command - just two words to get latest available firmware, readmes and source code together. But I agree that releases page is more appropriate place for binary files.