New beta firmware release 1.20beta10
-
Hmm it seems something odd is going on. Last night I set a tray of parts printing and this morning there was a completed tray but with a nasty layer shift (never seen this happen on this printer before). Assuming it was because I was messing about with probing and might have lowered my motor currents and did not put them back, I started the print again today, same issue despite running all motors at 1.2A/1.68A.
I will try again but on a different firmware version, I need to get these parts printed.
M122 if it helps: https://1drv.ms/t/s!Apv79JfGbPIwg4QskvIqENNjz_mSWA -
I had the same issue with the skew.
=== Move ===
MaxReps: 130, StepErrors: 123, FreeDm: 240, MinFreeDm 120, MaxWait: 2228747316ms, Underruns: 0, 0
Scheduled moves: 2721, completed moves: 2721
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000seems like there are a lot of step errors for 3 layers
-
Something is definitely odd with this firmware release.
First image 1.20beta10, totally messed up. Second one 1.20beta8, all going well until now! -
Mine wasn't as dramatic just a nasty layer shift towards -y (on a delta)
But those were 2 of 16 parts on the build plate, and then I reproduced the same error on the next 16, but cancelled the print as soon as it happened.
Interestingly I'm running the same FW on my corexy no issues so far, is this a delta problem?
-
Please can those of you who have experienced a layer shift using the latest release do the following:
1. State what machine architecture you are using (Cartesian, Delta etc.)
2. If you have a model that reproduces the issue easily, post a link to it
3. If possible, with 1.20beta10 loaded, connect a PC via USB, and send M111 S1 P4. Then print the model. Each time a step error is recorded, debugging info will be reported via USB. Post 50 or so lines of that debug info in this thread.
-
1. Delta (Kossel Mini T3DP3D)
2. https://www.thingiverse.com/thing:2323213/#files -> Apple-Watch-Phone-Stand_V7.0.stl
3. there are no lost steps. No debugging output from USB logging and M122 didn't show any problemsIt seems that after finishing the two solid layers every new layer gets skewed. With 1.20beta8 I could finish the print without any problems.
-
Thanks, I'll try printing that on my delta. Please share your config.g file.
-
I'm running beta 10 on a cartesian, no problems to report.
Seems to be a delta/scara kinematics problem… -
Hi,
#1 Delta
#2 Benchy : https://www.thingiverse.com/thing:763622
#3 no bug reported
Additional notes : the bug is not consistent, it's not happening each time at the same place with the same gcode file. In my case on 4 benchy, it happens 3 times and each time this "offset" was temporary (see picture)
my config :
;############################## ;#### General preferences ##### ;############################## M111 S0 ; Debugging off G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M555 P5 ; Set firmware compatibility to look like Repetier M665 R182.25 L360.26 B150 H363.70 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; Put your endstop adjustments here, or let auto calibration find them M208 Z-2 S1 ; Set minimum Z ;################## ;#### Endstops #### ;################## M574 X2 Y2 Z2 S0 ; Define active high microswitches ## PROBE ; Setup Sensitivity : M672 S105:aaa:bbb ; Current : M672 S105:20:235 ; Reset : M672 S131:131 M558 P5 T10000 R0.4 F200 H2 ; Smart Effector ; R= Delay, F= Probe speed, H= Dive height, T= Travel speed G31 P100 X0 Y0 Z-0.10 ; Set Z probe trigger value, offset and trigger height M557 R120 S20 ; Define mesh ;################ ;#### Drives #### ;################ M569 P0 S1 ; (X) Drive 0 goes forwards M569 P1 S1 ; (Y) Drive 1 goes forwards M569 P2 S1 ; (Z) Drive 2 goes forwards M569 P3 S1 ; (E0) Drive 3 goes forwards M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation M92 X80 Y80 Z80 E405 ; Set steps per mm M84 S30 ; Set idle timeout M566 X1200 Y1200 Z1200 E1000 ; (JERK) Set maximum instantaneous speed changes (mm/min) ; #OLD_1# E1200 M203 X18000 Y18000 Z18000 E3600 ; Set maximum speeds (mm/min) M201 X3600 Y3600 Z3600 E1200 ; Set accelerations (mm/s^2) M906 X1200 Y1200 Z1200 E1200 I70 ; Set motor currents (mA) and motor idle factor in per cent ;############################ ;#### Extruder (ADVANCE) #### ;############################ M572 D0 S0.2 ; Extruder 0 (D) Pressure advance default S0.1 ; #OLD_1# S0 ;M207 S3 R-0.05 F2500 T1200 Z0.4 ; Firmware retraction ;################# ;#### Heaters #### ;################# M143 H1 S260 ; Set maximum heater temperature to 300C M143 H0 S150 ; Set maximum bed temperature to 150C M305 P0 T100000 B3950 C0 R4700 ; #BED# Set thermistor + ADC parameters for heater 0 M305 P1 X200 ; #NOZZLE# Set thermistor + ADC parameters for heater 1 ;############### ;#### Tools #### ;############### M563 P0 D0 H1 ; Define tool 0 (P) uses extruder 0 (D) ,heater 1 (H) (and fan 0 -- default) 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 PDelta ; Set machine name M552 S1 ; Enable network M586 P0 S1 ; Enable HTTP M586 P1 S1 ; Enable FTP M586 P2 S0 ; Disable Telnet ;############## ;#### Fans #### ;############## M106 P0 S0 H-1 I0 F100 ; FAN 0 (P) default off (S) Thermostatic control OFF (T). M106 P1 T35 S1 H1 ; FAN 1 (P) triggered above 35° (T) at 100% (S) on Heater 1 ;################ ;#### CUSTOM #### ;################ M501 ; Loading config-override.g T0 ; Default tool to be deleted at start-up -
Hi David,
1. State what machine architecture you are using (Cartesian, Delta etc.)
DeltaFirmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.20beta10 (2017-11-23)
WiFi Server Version: 1.20b10
Web Interface Version: 1.19.3Took two attempts to load wifiserver via sd card. I am not getting as far as being able to get to the point of the layer shift. First attempt the machine threw a heater fault (normally completely reliable) just after warmup and delta calibration so i restarted it. The console debugging is in this file
https://1drv.ms/u/s!Apv79JfGbPIwg4RptjqtFRPVBjLS6w
labelled console.txt.
Then I tried again, and it crashed, stopped printing at around layer 8 nozzle on the print, nothing for a few seconds then a full reset. I powered back up saved m122, and have included console (console2.txt), eventlog and config.g.
Hope this helps but I'm downgrading for now.
-
Thanks. Unfortunately the M122 file is empty. However, I see some extruder step error reports in one of the console logs and I will take a detailed look at those. The full reset sounds as if it may be a watchdog timeout, which one other user has reported getting in beta 7 and later.
-
config.g below
[c]
; Configuration file for Mini Kossel Release 3 kit from Think3DPrint3D
; For additional help see http://reprap.org/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer and
; http://reprap.org/wiki/Configuring_and_calibrating_a_delta_printer_using_the_dc42_fork_of_RepRapFirmware; Prologue and communications section
M111 S0 ; Debug off
M550 PMiniKossel ; Machine name and Netbios name (can be anything you like)
M551 Preprap ; Machine password (currently not used)
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address
;*** Adjust the IP address and gateway in the following 2 lines to suit your network
M552 P0.0.0.0 ; Un-comment for DHCP
M555 P2 ; Set output to look like Marlin
M575 P1 B57600 S1 ; Set auxiliary serial port baud rate and require checksum (for PanelDue)G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves; The following section is not required for Firmware V1.09r and above
; Turn off fans: by default PWM fans on Duet V0.8.5 are inverted
; M106 I1 ; fans are inverting
; M106 S0 ; Turn off Fan 0; Movement section
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
M569 P4 S1 ; Drive 4 goes forwards
M574 X2 Y2 Z2 S1 ; 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 R106.156 L215 B85 H246.073, X-0.501 Y1.067; set delta radius, diagonal rod length, printable radius and homed height
X2.53 Y0.90 Z-3.43 ; put your endstop adjustments here, or let auto calibration find them
M92 X80 Y80 Z80 ; Set axis steps/mm
M906 X1000 Y1000 Z1000 E800 I60 ; Set motor currents (mA) and increase idle current to 60%
M201 X1000 Y1000 Z1000 E1000 ; Accelerations (mm/s^2)
M203 X20000 Y20000 Z20000 E3600 ; Maximum speeds (mm/min)
M566 X1200 Y1200 Z1200 E600 ; Maximum instant speed changes mm/minute; Heater and thermistor section
;*** If you have a Duet V0.6 board NOT stickered "4.7K" change R4700 to R1000 to the following M305 commands. Leave at R4700 for all Duet V0.8.5 boards
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. DC42 recommends 4388 for E3D V6 with Semitec 104-GT2 thermistor
M305 P2 T100000 B4388 R4700 H0 L0 ; Put your own H and/or L values here to set the second nozzle thermistor ADC correction.
M570 S180 ; Hot end may be a little slow to heat up so allow it 180 seconds
M143 S285 ; Allow up to 285°; Tool definition section
M563 P0 D0 H1 ; Define tool 0
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
;*** If you have a dual-nozzle build, un-comment the next 2 lines
;M563 P1 D1 H2 ; Define tool 1
;G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures
M92 E402 ; Set extruder steps per mm; Z probe section
;*** If you have a a switch as a zprobe 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 Z1.47 P500 ; Put your own value of Z-probe height here during calibration. Z1.55; Epilogue
;*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0 ; Axis compensation hereM208 S1 Z0.0 ; set minimum Z - can be negative but not recommended. Use G92 instead.
;
M501
T0 ; select first hot end
[/c] -
Thanks. Unfortunately the M122 file is empty. However, I see some extruder step error reports in one of the console logs and I will take a detailed look at those. The full reset sounds as if it may be a watchdog timeout, which one other user has reported getting in beta 7 and later.
Sorry about the m122. I will reduce extruder steps/mm which is quite high on 1/16th with Nimble 1/8th or 1/4 would work just fine.
-
btw I simulated the high E steps/mm on my delta by configuring and selecting a dummy extruder, and I still wasn't able to get any step errors. So I'll take a look at your config and see what's different.
-
on scara I use
M82 ;Set extruder to absolute mode
can be bug come from there?
I can not test until Tuesday … -
Just to report I have had no luck getting wifiserver1.20beta10 onto my other machine a corexy, the only difference here is its a 1.02 board. Tried via the memory card several times, normal console messages installing etc but get failed to initialise wifi module, code -10. I did check I was using the updated file, not the first one which didn't work. Beta 9 wifi server working perfectly, however.
-
I have the same layer shift problem with beta10
-
I also have layer shift on my cartesian printer with external drivers. My stepper/driver has encoder that will generate fault signal if there is a large positional error. I did not get any fault from my driver which means there must be some thing wrong with the input signal they are receiving.
-
btw I simulated the high E steps/mm on my delta by configuring and selecting a dummy extruder, and I still wasn't able to get any step errors. So I'll take a look at your config and see what's different.
printed 3 benchy, with 3 layer offset (different on each print) nothing in step error through a M122
-
I'm running beta 10 on a cartesian, no problems to report.
Seems to be a delta/scara kinematics problem…I had the issue on my Cartesian printer. I have since restored to the previous firmware and it is fine now. I just pulled off the whole y-axis to do some tweaking so I cant pull up anymore info.
I sliced using S3d.
