RepRapFirmware 3.0 first official beta is out

gtj0

I think I solved my Z 0.700 issue. I don't know how but...

G31
Current reading 0, threshold 500, trigger height 0.70, offsets X0.0 Y0.0

Nowhere in my configs to I set 0.700 for anything.
Anyway, a restart seems to have solved that issue.
I'm retesting mesh probing and the heightmap thing now.

stewwy

@dc42 bed leveling using the bed leveling probe (an ir sensor, one of yours )

gtj0

Yeah I still have the issue with the Z height changing when homing XY when a heightmap is in effect.

dc42

@gtj0 said in RepRapFirmware 3.0 first official beta is out:

Yeah I still have the issue with the Z height changing when homing XY when a heightmap is in effect.

On my list to investigate, but may have to wait until after TCT.

gtj0

@dc42 said in RepRapFirmware 3.0 first official beta is out:

@gtj0 said in RepRapFirmware 3.0 first official beta is out:

Yeah I still have the issue with the Z height changing when homing XY when a heightmap is in effect.

On my list to investigate, but may have to wait until after TCT.

No problem. I'll nose around a bit this weekend.

kraegar

Odd one. Heater faulted halfway through a print. Print kept going, but shows 100% for a status (can't cancel it anymore). Obviously not extruding, just still moving. DWC went unresponsive on me, too. Really odd.
No idea why the heater faulted yet.

wilriker

@kraegar This means this issue has not been fixed, yet.

EDIT: which version of DSF are you using? That might make my above assumption incorrect.

Marco Bona

With this build I encounter problems with heater mapping. The values found are -273 with the exception of the heated chamber which is correct.

; 9 _ HEATERS

M308 S0 P"bed_temp" Y"thermistor" A"Bed thermistor" T100000 B3950
M308 S1 P"spi.cs1" Y"rtd-max31865" P"spi.cs1" A"RTD1"
M308 S2 P"spi.cs2" Y"rtd-max31865" A"RTD2"
M308 S3 P"e2_temp" Y"thermistor" A"Chamber thermistor" T100000 B4725 C7.06e-8

M950 H0 C"bed_heat" T0
M950 H1 C"e0_heat" T1
M950 H2 C"e1_heat" T2
M950 H3 C"duex.e2heat" T3

T3P3Tony

@Marco-Bona said in RepRapFirmware 3.0 first official beta is out:

M308 S1 P"spi.cs1" Y"rtd-max31865" ~~P"spi.cs1"~~ A"RTD1"

are you definitely using .cs1 and .cs2 not .cs0 and .cs1 (i.e you have one daughter board) also remove the second P value

T3P3Tony

@kraegar I recommend using DSF 1.0.3.3

Marco Bona

@t3p3tony
Sorry but the second P value was a bonding problem.
For DSF I realized that it was only for Duet3, I'm using Duet2. If it is to be installed where can I find the file?

T3P3Tony

@Marco-Bona No you are right DSF is only Duet 3

kraegar

@T3P3Tony Thanks - I wasn't pointing to the unstable repo. Also, easy fix, but might trip up someone not linux savvy, you're missing a sudo on the apt-get install line of the instructions.

kraegar

Failed again, at 14.50mm of an 80mm print. Reports it's 100% but definitely is not.

kraegar

I'd only used systemctl to restart all the duet processes. Trying a print from a known reliable slice from my duet2, with a fresh boot on the latest software on the unstable branch.

T3P3Tony

@kraegar Please can you check the firmware viserion uning M115 and the versions on DSF you have through this command on the Rpi:
apt list 2>/dev/null | grep duet | awk -F'[/ ]' '{print $1" "$3 }'

(thanks @wilriker for the awk foo)

kraegar

@T3P3Tony said in RepRapFirmware 3.0 first official beta is out:

apt list 2>/dev/null | grep duet | awk -F'[/ ]' '{print $1" "$3 }'

FIRMWARE_NAME: RepRapFirmware for Duet 3 v0.5 FIRMWARE_VERSION: 3.0beta10 ELECTRONICS: Duet 3 prototype v0.5 FIRMWARE_DATE: 2019-09-12b1

duetcontrolserver 1.0.3.3
duetruntime 1.0.3.3
duetsd 1.0.2
duetsoftwareframework 1.0.3.3
duettools 1.0.3.3
duetwebcontrol 2.0.0-4
duetwebserver 1.1.0.0

wilriker

@T3P3Tony said in RepRapFirmware 3.0 first official beta is out:

apt list 2>/dev/null | grep duet | awk -F'[/ ]' '{print $1" "$3 }'

(thanks @wilriker for the awk foo)

@bearer is the one to deserve credits for the awk-foo. I try to avoid awk where I can.

A Former User

@wilriker said in RepRapFirmware 3.0 first official beta is out:

@bearer is the one to deserve credits for the awk-foo. I try to avoid awk where I can.

you mean you don't want the blame? ... awkward!

kraegar

awk is great. Learn to love it

I meant to kick off a ~4 hour print. Grabbed the slice and didn't check it, closer to a ~14 hour print. I'm a bit over 2 hours into it. So, this should be a good test of the duet3 after a fresh startup, so far so good.