Weird Z behavior with first attempt with RTOS firmware on Delta
I finally upgraded my DuetWiFi today after not using it since early May. I upgraded from the release version of 1.21 to the current Beta:
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet Firmware Electronics: Duet WiFi 1.0 or 1.01 Firmware Version: 2.01beta1(RTOS) (2018-06-23b1) WiFi Server Version: 1.21 Web Interface Version: 1.21.2-b1
I've tested each access, the endstops, the fans, and the heaters. All seem to work OK, but when I use the Machine Control tab to try to move X, Y, or Z, the corresponding carriages move, but I was expecting Z to move the effector up and down, X to move left and right, Y to move forward and back. It is acting as if it does not know it is a Delta.
This is a T3P3 Kossel Mini V3-based machine.
I'm pretty sure whatever I am doing is user error. Please help this user see the error of his ways.
Here is my config.g
; Configuration file for Duet WiFi (firmware version 1.20 or newer) - Edited 27 Apr 2018 - osh ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool on Tue Jan 02 2018 16:25:12 GMT-0600 (CST) ; General preferences M111 S0 ; Debugging off G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M555 P2 ; Set firmware compatibility to look like Marlin M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Configure automatic saving on power loss ; *** The homed height is deliberately set too high in the following - you will adjust it during calibration. ; Set delta radius, diagonal rod length, printable radius and homed height ; M665 R105.6 L215.0 B85 H250 ; default M665 form T3P3 Kossel Mini M665 R87.290 L215.15 B85.0 H222.600 X-0.135 Y-0.180 Z0.00 M666 X-0.11 Y0.35 Z-0.33 ; Put your endstop adjustments here M208 Z-0.1 S1 ; Set minimum Z ; Endstops M574 X2 Y2 Z2 S1 ; Set active high endstops M558 P1 H8 F120 T2400 ; Set Z probe type to unmodulated and the dive height + speeds ; ; Tip: A larger trigger height in G31 moves you CLOSER to the bed G31 P500 X0 Y-11 Z0.235 ; Set Z probe trigger value, offset and trigger height ; G31 P500 X0 Y-11 Z0.240 ; Starting Point Feb 4 2018 M557 R75 S20 ; Define mesh grid ; Drives M569 P0 S1 ; Drive 0 goes forwards M569 P1 S1 ; Drive 1 goes forwards M569 P2 S1 ; Drive 2 goes forwards M569 P3 S1 ; Drive 3 goes forwards M350 X16 Y16 Z16 E16 I0 ; Configure microstepping without interpolation M92 X80 Y80 Z80 E402 ; Set steps per mm - osh - re-set from 404 to 425 now to 402 4/14/2018 M566 X1200 Y1200 Z1200 E1200 ; Set maximum instantaneous speed changes (mm/min) M203 X18000 Y18000 Z18000 E1200 ; Set maximum speeds (mm/min) ; M201 X1000 Y1000 Z1000 E1000 ; Set accelerations (mm/s^2) - default M201 X1750 Y1750 Z1750 E1500 ; Set accelerations (mm/s^2) - test 2/25/2018 M906 X1000 Y1000 Z1000 E800 I40 ; Set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Heaters M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0 M143 H0 S120 ; Set temperature limit for heater 0 to 120C M305 P1 T100000 B4388 C0 R4700 ; Set thermistor + ADC parameters for heater 1 M143 H1 S280 ; Set temperature limit for heater 1 to 280C ; Tools M563 P0 D0 H1 ; 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 ; Network M550 PCharlotte3D ; Set machine name M552 S1 ; Enable network M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet ; 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 M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on ; Custom settings are not configured M579 X0.998 Y0.993 ; adjusted based on 100mm XY square - 2/12/2018 - osh ; Miscellaneous T0 ; Select first tool
autsch last edited by
I had the same problem. Downgrade the web interface (www content) and it's working again. Problem is the Java Script in the Web Interface.
@autsch I will try that - thank you!
As @autsch suggested, reverting from
1.21.1for the web interface fixed my issue.
I really appreciate that help. I did not think the DWC would have caused an issue like that!
autsch last edited by autsch
Shit happens, John
Btw: New Version is out and working