New firmware 1.21RC1 available

nyt

I've been noticing some oddities with bed leveling, even before this release.

I run compensation, and average level is above 0, run it again, it's below, run it again, it's above, etc. It's like it's using old values every time it runs. I tracked this down and fixed it with G29 S2 at the top of bed.g, but shouldn't bed leveling disregard old values anyway?

also great work w/ the new bed leveling averaging. Going to test the pressure advance stuff for stupid slicers now. I've been harassing simplify3d to fix their broken g-code, but they're dense.

dc42

@nyt:

I've been noticing some oddities with bed leveling, even before this release.

I run compensation, and average level is above 0, run it again, it's below, run it again, it's above, etc. It's like it's using old values every time it runs. I tracked this down and fixed it with G29 S2 at the top of bed.g, but shouldn't bed leveling disregard old values anyway?

Please post your bed.g file.

timcurtis67

I ran my printer for a good 30+ hrs over the weekend after the upgrade and didn't run into any bugs or issues.

The only thing I think could be happening is slower uploads when I load gcode files? Maybe its my imagination but it seems like the upload speeds are half as fast now? I thought I was seeing 700+ speeds but now 400 is the fastest I have seen.
1. I'll try resetting my router tonight.
2. I can revert back to 1.20 to make sure but I'm really happy with this version so far.

Great work dc42! Thank you.

nyt

@dc42:

@nyt:

I've been noticing some oddities with bed leveling, even before this release.

I run compensation, and average level is above 0, run it again, it's below, run it again, it's above, etc. It's like it's using old values every time it runs. I tracked this down and fixed it with G29 S2 at the top of bed.g, but shouldn't bed leveling disregard old values anyway?

Please post your bed.g file.

Just added the G29 S2 which fixed it…

G29 S2 ; clear height map
M376 H10 ; correction taper after 10mm
M557 X10:394 Y4:390 S55:52
G28 ; home
G1 X0 Y0 ; move to 0,0
M400 ; wait for move to complete
G29 ; probe bed
G1 Z5 ; position

DaveA

@Jackal:

I have just updated from 1.20 to 1.21RC1 and not sure why the mesh bed compensation shows a rectangular bed instead of a circular bed for my delta. I didn't change my config.g, maybe I missed something that I should change?

I have M558 P1 R0.4 X0 Y0 Z0 H1.5 F100 T3000 I0 in my config.g and M557 R100 S15 in my bed.g

Just noticed the same thing. When I do a G29 it probes the bed using my correct delta geometry but when it brings up the heightmap it is shown as a rectangle.
There are also some real "flyers" near the border of the delta area. Dropped back to 1.20 and the delta shape is back and the flyers are gone.

Is this intentional?

dc42

There are some new bugs in G29 bed probing in firmware 1.21RC1. I will fix them in the next RC.

DocTrucker

Hi,

Just to clarify if I see a RepRapFirmware.bin file in the release folder it is safe to assume it runs on the Duet v0.6?

Saw some notes on the 1.20 that this was the last release that you planned for v0.6 / v0.8.5 boards other than 1.20.x bug fixes (such as the 1.20.1RC)?

Thanks.

dc42

Version 1.20.1 got turned into 1.21 because I added some new features. It will be available for the older Duets.

DocTrucker

Ah ok, that makes sense. Thanks for the explanation.

To save me bothering you in the future if there is a RepRapFirmware.bin in a release folder then it is safe to upload onto the v0.6?

dc42

Yes.

okercho

@dc42:

There are some new bugs in G29 bed probing in firmware 1.21RC1. I will fix them in the next RC.

Hi David, What is this bug related to? I'm having some issues with my bed levelling that is driving me nuts, but I think in my case is a mechanical problem (I've bought a new rods to discard the issue, hopefully I will get them by the end of this week).

Cheers

dc42

The known issues are:

G92 on a delta causes a square height map to be displayed
The new multi tap facility doesn't work with G92

okercho

@dc42:

The known issues are:

G92 on a delta causes a square height map to be displayed

The new multi tap facility doesn't work with G92

Mechanical issue is still winning the raffle then xD

Captain_sq

@dc42:

The known issues are:

G92 on a delta causes a square height map to be displayed

The new multi tap facility doesn't work with G92

Do you mean G29 or G92?

Captain_sq

This evening my Duet 0.6 quit midprint due to a software reset. Diagnostics points to the Network loop. I'm running with fixed IP address.

[[language]]
M122
=== Diagnostics ===
Used output buffers: 2 of 32 (10 max)
=== Platform ===
RepRapFirmware for Duet version 1.21RC1 running on Duet 0.6
Static ram used: 44836
Dynamic ram used: 40972
Recycled dynamic ram: 208
Stack ram used: 1192 current, 4316 maximum
Never used ram: 7972
Last reset 00:00:16 ago, cause: software
Last software reset at 2018-02-01 22:59, reason: Stuck in spin loop, spinning module Network, available RAM 5496 bytes (slot 1)
Software reset code 0x6041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0000080f, BFAR 0xe000ed38, SP 0x20087cd4
Stack: 000c0f57 0000000a fffffff9 00000000 7f7f8000 0000000f 0000000a 01010101 000a89f9 000a89f8 81000000 000000be 00000004 000babb1 000ac38f 0000003a 00000001 00000006 2007a9e0 20087d4e 2007ab18 20087d90 20087d48 00000027
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 27.5, current 28.5, max 28.7
Date/time: 2018-02-01 22:59:43
Slowest main loop (seconds): 0.004105; fastest: 0.000100
=== Move ===
MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 100, MinFreeDm 100, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 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 idle 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 ===
Free connections: 15 of 16
Free transactions: 23 of 24
Locked: 1, state: 4, listening: 0x20071bf0, 0x20071bd4, 0x0

robm

for the filament monitor, m591 r-1:-1 or similar gives 'allowed movement 2147483647% to 2147483647%' for the probe result - which makes sense to me but is probably not desirable. This is on P3 the rotating magnet filament monitor.

Is there a new way to enter the calibration mode?

thanks
Rob.

dc42

@Captain_sq:

This evening my Duet 0.6 quit midprint due to a software reset. Diagnostics points to the Network loop. I'm running with fixed IP address.

On my list to look at.

dc42

@robm:

for the filament monitor, m591 r-1:-1 or similar gives 'allowed movement 2147483647% to 2147483647%' for the probe result - which makes sense to me but is probably not desirable. This is on P3 the rotating magnet filament monitor.

Is there a new way to enter the calibration mode?

thanks
Rob.

The parameters for filament monitors have been changed in firmware 1.21. See https://duet3d.com/wiki/G-code#M591:_Configure_filament_sensing. However, I haven't tested the rotating magnet sensor with firmware 1.21RC yet.

robm

@dc42:

The parameters for filament monitors have been changed in firmware 1.21. See https://duet3d.com/wiki/G-code#M591:_Configure_filament_sensing. However, I haven't tested the rotating magnet sensor with firmware 1.21RC yet.

Thanks, I saw that - but don't see anything in the 1.21 section at all re: calibration mode other than that the 'data will be collected even when filament monitoring is disabled'.

Current print with R-1:-1 is generating calibration data so seems to be working and apparently -1 still puts it into calibration mode

thanks,
Rob.

robm

Also on the report message for the P3 monitor, it seems to be truncated at the end:

Duet3D rotating magnet filament monitor on endstop input 3, disabled, sensitivity 28.80mm/rev, allowed movement 2147483647% to 2147483647%, check every 3.0mm, current position 298.5, measured sensitivity 26.29mm/rev, measured minimum 3%, maximum 6% over 6

From other messages I am guessing that is over 6xx mm extruded.

Otherwise 1.21RC1 working beautifully on my DIY Prusa i3 variant.

Cheers,
Rob.