RepRapFirmware 3.2-RC2 released

bot

Thank you for the continued development work! Happy Holidays to the entire Duet/Think3dPrint3d/Escher team!

GTech

This post is deleted!

Veti

completed a 12 hour print on rc2. no problems.

mikep419

Installed RC2 last night including updating the PanelDue firmware using M997 S4, which is nice. Tuned heaters this morning using new M303. Everything working as expected.

Thanks for the hard work. Happy New Year.

@mikep419 said in RepRapFirmware 3.2-RC2 released:

Installed RC2 last night including updating the PanelDue firmware using M997 S4, which is nice. Tuned heaters this morning using new M303. Everything working as expected.

Thanks for the hard work. Happy New Year.

Have you seen within M303 the new T-parameter?

+1

Thanks everybody!

Veti

Just adjusting my printer

For some reason i can not set Toff to 1

M569 P3 F1
Error: M569: Bad off time for driver 3

M569 P3 F2
This works

according to the data sheet
https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2209_Datasheet_V103.pdf

toff 1 is a valid setting

It does not work on the maestro with tmc2224 either.

dc42

It's because the datasheet says you must use toff=1 only with tbl >= 2. What have you set tbl to ?

Veti

it does not work with that either

M569 P3 D2 S1 F1 B2
Error: M569: Bad off time for driver 3

the datasheet says this

Hint
Highest motor velocities sometimes benefit from setting TOFFto 1 or 2 and a short TBLof 1 or 0

Veti

ok i have to set the tbl first and then i can set the toff

M569 P3 D2 S1 B2
M569 P3 D2 S1 F1

dc42

I can change the code to set tbl before toff, however if I do that then you would face the same issue if you try to set tbl=1 and toff>1 in the same command.

Veti

@dc42
if you do the check on the values to be set it should work both ways

i.e if the commands set tbl or toff use those values for the check
if one or the other is not set use the current value.

mitch

@dc42 Any idea why the new 3.2 RC2 no longer recognizes this meta code?

if sensors.filamentMonitors[0].filamentPresent = false

Error: meta command: unknown value 'filamentPresent'

dc42

@mitch said in RepRapFirmware 3.2-RC2 released:

@dc42 Any idea why the new 3.2 RC2 no longer recognizes this meta code?
if sensors.filamentMonitors[0].filamentPresent = false
Error: meta command: unknown value 'filamentPresent'

Are you running with SBC or in standalone mode?

Is 'sensors.filamentMonitors[0]' non-null? Send M409 K"sensors.filamentMonitors[0]" to check.

Veti

@dc42 said in RepRapFirmware 3.2-RC2 released:

It's because the datasheet says you must use toff=1 only with tbl >= 2. What have you set tbl to ?

can you please add that info to this page

https://duet3d.dozuki.com/Wiki/Reducing_Stand-Still_Noise

mitch

@dc42 said in RepRapFirmware 3.2-RC2 released:

M409 K"sensors.filamentMonitors[0]

Running Duet2 Eth. No SBC.

{"key":"sensors.filamentMonitors[0]","flags":"","result":{"calibrated":{"percentMax":107,"percentMin":95,"sensitivity":101,"totalDistance":562.7},"configured":{"calibrationFactor":0.418,"percentMax":110,"percentMin":90,"sampleDistance":3.0},"enabled":false,"status":"ok","type":"laser"}}

dc42

This change is documented in the release notes for 3.2beta3 at https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md. When RRF 3.2 stable is released, the change will be copied over to the release notes for that version.

mitch

@dc42

Thanks, Sorry, I went from 3.1.1 straight to 3.2 RC2 and I missed that note back in beta 3.

if sensors.filamentMonitors[0].status  =  "noFilament"

button

Printing from yesterday:
alt text

Workimg whitout any issues.
Updated everything - reprapfirmware, dwc, paneldue.

Great job guys! Like usually