New beta firmware release 1.20beta10
-
I have the same layer shift problem with beta10
this is my config.g
; Configuration file for Mini Kossel kit from Think3DPrint3D for testing Duet WiFi
; Communication and general
M111 S0 ; Debug off
M550 PKosselXXLWiFi ; Machine name and Netbios name (can be anything you like)
M551 Preprap ; Machine password (used for FTP)
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address
;*** Wifi Networking
M552 S1 ; Enable WiFiM555 P2 ; Set output to look like Marlin
M575 P1 B57600 S1 ; Comms parameters for PanelDueM586 P1 S1 ; Enable FTP
M586 P2 S1 ; Enable TelnetG21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves; Axis and motor configuration
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes forwards
M569 P4 S0 ; Drive 4 goes forwards
M574 X2 Y2 Z2 S0 ; set endstop configuration (all endstops at high end, active high)
;*** The homed height is deliberately set too high in the following - you will adjust it during calibration;M665 L503.000 R245.982 H575.060 B132.5 X0.022 Y0.073 Z0.000 ; set delta radius, diagonal rod length, printable radius and homed height
;M666 X-0.056 Y-0.024 Z0.079 A0.00 B0.00 ; put your endstop adjustments here, as given by auto calibrationM665 L503.000 R245.965 H589.90 B132.5 X0 Y0 Z0.000
M666 X0.08 Y0.01 Z-0.09 A0 B0;M350 X16 Y16 Z16 E16 I1 ; Set 16x microstepping with interpolation
;M92 X100 Y100 Z100 ; Set axis steps/mmM350 X16 Y16 Z16 E16 I1 ; Set 16x microstepping with interpolation
M92 X100 Y100 Z100 ; Set axis steps/mmM906 X1400 Y1400 Z1400 E1400:1400 I60 ; Set motor currents (mA) and increase idle current to 60%
M201 X1800 Y1800 Z1800 E800 ; Accelerations (mm/s^2)
M203 X18000 Y18000 Z18000 E4600 ; Maximum speeds (mm/min)
M566 X900 Y900 Z900 E1800 ; Maximum instant speed changes mm/minute; Thermistors
M305 P0 T100000 B3950 R4700 H0 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B4388 R4700 H0 L0 ; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
M305 P2 T100000 B4388 R4700 H0 L0 ; Put your own H and/or L values here to set the second nozzle thermistor ADC correction; Fans
;M106 P1 H-1 ; disable thermostatic mode for fan 1
M106 P1 L255 S255 H1 T45
;M106 P2 L255 S255 H0:1:2 T40M106 P0 L255 S255 H100:101 T35 ; defino al fan 2(el que esta en la caja de la electronica como termostatico y controlado por la temperatura de la CPU y de los STEPPER DRIVERS)
; Tool definitionsM563 P0 D0 H1 F2 ; Define tool 1
G10 P0 S0 R0 X0 Y0 ; set tool 0 temperatures and offsets
M563 P1 D1 H1 F2 ; tool 0 uses extruder drive 0 and heater 1 y Fan 2 en lugar de 0 ya que esta quemado
G10 P1 S0 R0 X0 Y0 ; Set tool 1 temperatures and offsets;M92 E663:663 ; Set extruder steps per mm
;M92 E146:418.5:663:663:663:663
;M92 E146:837:663:663:663:663
;M92 E146:830:663:663:663:663
;M92 E806:806:663:663:663:663
M92 E804:804:663:663:663:663; Z probe and compensation definition
;*** If you have a switch instead of an IR probe, change P1 to P4 in the following M558 command
;M558 P1 X0 Y0 Z0 ; Z probe is an IR probe and is not used for homing any axes
;G31 X0 Y0 Z4.80 P500 ; Set the zprobe height and threshold (put your own values here)
M558 P1 X0 Y0 Z0 ; Z probe is a DC42 Differential IR PCB and is not used for homing any axes
G31 X0 Y0 Z0.490 P500 ; Set the zprobe height and threshold (put your own values here);*** If you are using axis compensation, put the figures in the following command
;M556 S78 X0 Y0 Z0 ; Axis compensation hereM208 S1 Z-0.2 ; set minimum Z
;M579: Scale Cartesian axes
;On a Cartesian RepRap you can get prints exactly the right size by tweaking the axis steps/mm using the M92 G Code above. But this does not work so easily for Delta and other RepRaps for which there is cross-talk between the axes. This ;command allows you to adjust the X, Y, and Z axis scales directly. So, if you print a part for which the Y length should be 100mm and measure it and find that it is 100.3mm long then you set Y0.997 (= 100/100.3).M579 X1.012 Y1.012 Z1
; Configurar la retraccion por hardware
;M207 S4.0 R-0.1 F3600 T1200 Z0.075
M207 S4.5 R-0.2 F2600 T1800 Z0.09
;M207 S4 R-0.05 F2200 T1800 Z0.0;Pressure advance M572
M572 D0 S0.08
;M572 D1 S0.1;pid autotune parameters
;M307 H0 A141.2 C398.4 D1.9 B0
;M307 H1 A758.3 C275.8 D5.8 B0M570 H1 P5 T20
M557 R110 S22 ; definir un grid de radio 130 cada 22 mm para compenzar la cama
M581 E0 S0 T2 C1 ; configurar el trigger 2 con el sensor del Extrusor 0, activo cuando esta imprimiendo
M581 E1 S0 T3 C1 ; configurar el trigger 2 con el sensor del Extrusor 0, activo cuando esta imprimiendo
M404 N1.75 D0.4 ; setear diametro de filamento y de nozzleM912 P0 S-15.4 ; Calibrar temperatura de la CPU
T0 ; select first hot end
-
DjDemonD: here are my Z probe repeatability metrics:
https://docs.google.com/spreadsheets/d/15TNWrQdryhAFkfltrYofC_Zl10F0TGuRSZ4mP1esJtI/edit?usp=sharingOverall, my BLTouch clone achieves a range of about 60-50µm, and a standard-deviation of less than 15µm.
1.20beta10 with Z-Probe type 8 didn't change very much for me though.
Biggest impact was probing speed and maybe my latest upgrade to Tr8x2. -
Thank you that's very interesting. So it seems best case scenario it's about 50 microns as expected.
-
I too have had the shift while printing after upgrading to 1.20 beta 10. I changed back to an earlier version and the shift went away. I tried the same print 3 times with shift each time….
My printer is cartesian -
Pleased can some of you who experienced layer shift on a Duet WiFi with 1.20beta10 try this version https://www.dropbox.com/s/tr3be3v9o5iqxxa/DuetWiFiFirmware.bin?dl=0 and let me know if it solves the layer shift issue.
-
Hi David
Same error on Scara for me
(slicer: Simplify3D & M83 )
Firmware Version: 1.20beta10+2 (2017-11-26) -
Hi David
Same error on Scara for me (slicer: Simplify3D & M83 )
Firmware Version: 1.20beta10+2 (2017-11-26)Thanks for testing it. Were there are step errors reported by M122 afterwards?
-
I tried the DropBox version. Unfortunately I wasn't able to determine if a layer shift problem exists because the extruders were not extruding correctly. I had defined and selected an equal mix (Tool 3) of four defined tools and three physical extruders. The first of the three extruders was the only one feeding filament. I selected another tool to see if the problem could resolve itself and I received an error in DWC "Trying to extrude without a tool selected." This has not happened before.
-
Tryning the new probe mode 7
and sensorless homing
i get this
"Error: Z probe already triggered before probing move started"any advice ?
-
I installed the new firmware and I have been good so far…
Cartesian Printer. Running at 256 microsteps. unfortunately i didnt get any good diagnostics when i was having the error. Is there anything I can pull that would be helpful?
-
I have a Duet 0.85! can you please also submit 1.20beta10+2 for this model?
-
I tried the DropBox version. Unfortunately I wasn't able to determine if a layer shift problem exists because the extruders were not extruding correctly. I had defined and selected an equal mix (Tool 3) of four defined tools and three physical extruders. The first of the three extruders was the only one feeding filament. I selected another tool to see if the problem could resolve itself and I received an error in DWC "Trying to extrude without a tool selected." This has not happened before.
I just tried this on my machine with 1.20 beta8 (not the dropbox version) and all extruders/tools work as expected.
-
So running that last version from dropbox with wifiserver 1.20b10 and now 1hr37min into a print with no odd behaviour, so far.
Still getting step errors:
MaxReps: 6, StepErrors: 655, FreeDm: 120, MinFreeDm 120, MaxWait: 672927154ms, Underruns: 0, 0Even though I've changed my extruder to 1/8th microstepping from 1/16th with interpolation. No issue in the print itself though.
EDIT Print finished no issues.
Was it the free ram? -
hi,
to free even more ram, is it possible to disable the whole network stack at compile time ?
if not, would you agree to add the feature ? -
My M122 on Scara
[[language]] M122 === Diagnostics === Used output buffers: 3 of 32 (15 max) === Platform === RepRapFirmware for Duet WiFi version 1.20beta10+2 running on Duet WiFi 1.0 Board ID: 08DDM-9FAM2-LW4SD-6JKFA-3SD6K-K3WZX Static ram used: 15488 Dynamic ram used: 98184 Recycled dynamic ram: 1016 Stack ram used: 1368 current, 9212 maximum Never used ram: 7172 Last reset 00:09:26 ago, cause: power up Last software reset reason: User, spinning module GCodes, available RAM 7352 bytes (slot 0) Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff Error status: 0 Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms MCU temperature: min 34.8, current 35.5, max 35.7 Supply voltage: min 11.9, current 12.1, max 12.3, under voltage events: 0, over voltage events: 0 Driver 0: ok Driver 1: ok Driver 2: standstill Driver 3: ok Driver 4: standstill Date/time: 2017-11-28 15:16:10 Cache data hit count 2079191923 Slowest main loop (seconds): 0.081784; fastest: 0.000110 === Move === MaxReps: 9, StepErrors: 0, FreeDm: 145, MinFreeDm 142, MaxWait: 0ms, Underruns: 0, 1 Scheduled moves: 10524, completed moves: 10494 Bed compensation in use: none Bed probe heights: 0.000 0.000 0.000 0.000 0.000 === Heat === Bed heater = 0, chamber heater = -1 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.8 === GCodes === Segments left: 1 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 doing "G1 X178.167 Y155.229 Z0.580 E0.0044" 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.20b8 WiFi MAC address 5c:cf:7f:a4:05:41 WiFi Vcc 3.35, reset reason Turned on by main processor WiFi flash size 4194304, free heap 28352 WiFi IP address 192.168.111.155 WiFi signal strength -52dBm, 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) -
On Scara Activate M111 S1
return:[[language]] 15:18:54 Error: Can't open 0:/sys/retractprobe.g to read, error code 4 15:18:50 Error: Can't open 0:/sys/deployprobe.g to read, error code 4 15:18:25 M32 TwistRound.gcode File TwistRound.gcode selected for printing Heater 0 switched on Heater 1 switched onApparently the offsets bugs are only in X …
-
I tried the DropBox version. Unfortunately I wasn't able to determine if a layer shift problem exists because the extruders were not extruding correctly. I had defined and selected an equal mix (Tool 3) of four defined tools and three physical extruders. The first of the three extruders was the only one feeding filament. I selected another tool to see if the problem could resolve itself and I received an error in DWC "Trying to extrude without a tool selected." This has not happened before.
I just tried this on my machine with 1.20 beta8 (not the dropbox version) and all extruders/tools work as expected.
Yes, that's right. Previous versions have not done this. The previous beta's issue was not with the extruder, but the layer shift.
-
So running that last version from dropbox with wifiserver 1.20b10 and now 1hr37min into a print with no odd behaviour, so far.
Still getting step errors:
MaxReps: 6, StepErrors: 655, FreeDm: 120, MinFreeDm 120, MaxWait: 672927154ms, Underruns: 0, 0Even though I've changed my extruder to 1/8th microstepping from 1/16th with interpolation. No issue in the print itself though.
EDIT Print finished no issues.
Was it the free ram?I think the issues with beta10 were down to insufficient free RAM.
I still can't reproduce your extruder step errors, even though I have set up a dummy tool that uses the same extruder settings as in the config.g you supplied. Can you provide a GCode file that provokes them?
-
