We've finally found a combination that is working:
M307 H2 B1 C1800 D350 R.02
If anyone has any suggestions, we'd be all ears about how to better tune chamber heaters as we have not been able to get auto-tuning to finish. Or does it really matter? We are leaning towards it not mattering.. Thanks
For additional completeness, here is a link to the esphome integration which handles all "flavours" of DHT sensors including DHT11, DHT22, AM2302, RHT03, and SI7012 with links to their various data sheets.
@dc42 the two contour lines get thinner and thinner at the end so that there is a gap between them.
Now I try to lower PA value again.
If you mean the two perimeter lines, they are joined in the perimeter at the top, joined for part of the length of the perimeter on the right, and not joined at all in the perimeter at the bottom. The difference between top and bottom suggests to me that you have chosen an unfortunate wall thickness and the slicer has failed to ensure consistent infill by altering the extrusion widths - so that whether the perimeters are joined or not is very sensitive to small changes. I am assuming that the thickness of all three walls is supposed to be the same.
I also have problems with pressure advance and input shaping with de PA values I already got finetuned without input shaping.
Top one: input shapping ei3 @48Hz + PA 0.1 (orbiter extruder direct)
Bottom one: just input shapping and no PA
Both 100mm/sec, 6000mm/s2 acceleration
You can see corners are ok with the PA, and bulges with no PA...
Same here: I upgraded my Duet Wifi (v1.02) from 3.2.0 (my first v3 firmware) to 3.2.2 and the printer got stuck and required additional help to get WiFi running again. I had used the new update procedure for the PanelDue (5" v3.0) just before that, just to mention that in case it helps. SD card seems fine though, if I can trust Windows...
@dc42 While searching on how to do this, I found your wiki help section "Installing and Updating Firmware" seems a bit outdated. It is still talking about iape4e/iap4s.bin being needed. Thankfully the M997 command complained about the missing Duet2_SDiap... file instead of showing me obscure error codes as some other systems might do.
(thanks @T3P3Tony for getting my account running again btw, the Akismet spam tool drove me nuts... now I can at least post something again even if it still bugs me now and then...)
I don't have time to write a BME280/BME680 right now, but if anyone else wants to then I will provide advice. It should use SPI protocol and the primary sensor class should be derived from SpiTemperatureSensor.
@dc42 What did you end up doing here? For clarity does the Gcode dictionary reflect the changes you made as the thread went cold and no definitive answer?
For my 0.9 LDO motors I have M915 X S-50 F0 H400 R0 on the mini, it homes but im having a hell of a game with motors banging, crashing, thumping however you want to call it. I had some help to try to keep spreadcycle active except for homing but still the bang / layer shift continues.
when I purchased the board @T3P3Tony said the 2209's ran nicely with 0.9's (bit off topic here) but I could seriously do with some help, im on the verge of scrapping it.
@garyd9 It only evaluates properties from the DSF object model that have the LinuxProperty attribute. This is done in Model/Expressions.cs and I think I will need to add a fix for round braces to that file. When those expressions have been replaced, the remaining term is sent to RRF for final evaluation.
Is there a dynamic roadmap document that is periodically updated somewhere on the Github? I fully appreciate the complexities of working on projects like this and understand dates move, but perhaps a dynamic document with estimates for the next release date and a confidence level would save mods and Duet staffers fielding the same question repeatedly?
Not yet, but we're working on making our development more transparent after the 3.3 release.