New beta firmware release 1.20beta10
-
I'm sorry, somehow the wrong file got copied to DuetWiFiServer-1.20beta10.bin on github. I have corrected it now.
-
reflot
[[language]] Hi, Added Z probe types 7 (switch connected to Z endstop) and 8 (as type 5 without any filtering, for faster response) Bltouch or Míni Differential Ir Sensor, are affected? -
Wifi beta 10 is working now!
-
reflot
[[language]] Hi, Added Z probe types 7 (switch connected to Z endstop) and 8 (as type 5 without any filtering, for faster response) Bltouch or Míni Differential Ir Sensor, are affected?IR sensor: not affected if you use it in analogue mode as recommended for the Duet. But you could use it in digital mode with the probe type set to 8 if you wish.
BLTouch: if you currently have the probe type set to 5, you could try 8. It might give you slightly more reproducible results.
Here is what the new mode is about. The ADC on the Duets reads every enabled input channel once every millisecond and feeds the values into averaging filters. When you use a digital output Z probe, the ADC is not used but the Z probe is still sampled every millisecond and fed into an averaging filter. This can be useful for debouncing and rejecting glitches. However, it means that there is a variable delay of up to 1ms before the Z probe signal is recognised. If you are probing at 1000mm/minute (as we suggest with the Smart Effector), then the head will move 16.7um in 1ms. So the 1ms sampling introduces an uncertainty in the trigger point of +/- 8.3um. This uncertainty is avoided when you use mode 8. At lower probing speeds, the uncertainty is lower.
-
What debounce value would you suggest in G31 for smart effector? Or does this not apply when using p8?
-
Debounce doesn't apply when using P8. Any value between 1 and 1000 should give the same result.
-
Hi David
On Scara I have a strange problem with
DuetWiFiFirmware-1.20beta10.bin
I have shifts of layers in x / y it does not get well
unusable ….downgrade
DuetWiFiFirmware-1.20beta8+1.bin
DuetWiFiServer-1.20b8.bin
result ok ...
sorry brooken English ...
photo before/after (same file)
-
I also have experienced layer "skewing" with 1.20beta10. Printed a gear bearing from Thingiverse and it came out slanted, but more on one side. Strange effect.
-
yes it's strange about simple shapes square/circles it works
while on complex shapes it does not work anymore … -
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.
