New beta firmware release 1.20beta10

DjDemonD

Thank you that's very interesting. So it seems best case scenario it's about 50 microns as expected.

percar

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

dc42

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.

frafa

Hi David
Same error on Scara for me (slicer: Simplify3D & M83 )
Firmware Version: 1.20beta10+2 (2017-11-26)

dc42

@frafa:

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?

Forgvn77

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.

MrBlom

Tryning the new probe mode 7
and sensorless homing
i get this
"Error: Z probe already triggered before probing move started"

any advice ?

Jason K

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?

franzelka

I have a Duet 0.85! can you please also submit 1.20beta10+2 for this model?

deckingman

@Forgvn77:

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.

DjDemonD

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, 0

Even 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?

lolorc

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 ?

frafa

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)

frafa

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 on

Apparently the offsets bugs are only in X …

Forgvn77

@deckingman:

@Forgvn77:

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.

dc42

@DjDemonD:

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, 0

Even 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?

DjDemonD

Hi David,

Yes I can: https://1drv.ms/u/s!Apv79JfGbPIwg4Uh8SjQ7OwE4VuEnA

thank you.