it's ok with b7+7, thanks 👏 😊

@dc42 - After several more days of testing, we are going to mark this as solved, however something still feels wrong as the only way to reliably stop the heater faults was to raise the C value to 200x the actual time it takes to fully heat our chambers. That isn't how the documentation describes the C parameter, but we'll run with it unless we're told additional changes are made in the firmware.

@dc42 My printer uses a hotend other than e3dv6. the thermistor there is located closer to the heater. Perhaps for this reason he is more sensitive. However. As a result of several experiments, with the implementation of the M303 with different blowing power, I stopped at the option when calibration occurs with a blowout of 35 percent. Fluctuations when switching within 3 degrees. The best with this configuration can not be achieved, I think.
photo_2022-01-20_21-02-14.jpg photo_2022-01-20_20-51-09.jpg

@dc42 Yep! That did it!
Silly me

ok the geometry and type of material affect the pid adjustment

I'm still hopeful someone will post instructions I can follow for converting a Duet2Ethernet to d2+SBC as I'd like to have the extra processing ability for some of the hoped to have plugins.

@deckingman

well its a nice solution, ill be using it in other places too 🙂

@arnold_r_clark said in RRF3.4.0beta7+4 error on Duet 2 Wifi:

Thanks but.... if you follow the link listed by @dc42 as being +7 the link actually takes you to the +4 file location which is still faulty...

Look at the file dates - he seems to be upgrading them in place, rather than keep creating different sets.

Firmware 3.4 beta 7+7 solved the heater problem when starting a new print. the heater is fine part good also the bl touch seems to be fine. I do further tests and communicate news

@dc42 - UPDATE: in BETA7+7 is called filament-error.g . Not filament_error.g.
(6HC + 1LC + SBC + MFM)

@dc42 Excellent!

The issue is gone on my 2 delta and on my CoreXY, first prints are fine - Thanks!
Fingers crossed 🙂

From my perspective, this thread can be flagged are resolved.

@phaedrux No, nothing bad is happening

@zapta we're hoping to release 3.4.0rc1 next week.

@dc42

Update worked. Thanks!

@dc42
3.4.0b7+4 does appear to have fixed the issue I was experiencing when G10 R0 S0 was used.
I put it back in and the macros perform correctly.

Given the graphs I showed and the fact that the ambient temp is in excess of 30 degrees here, I disagree with the 25 degree thing, but it's a moot point.

Thanks for the quick action!

@arnold_r_clark This is fixed in 3.4.0beta7+2, see https://forum.duet3d.com/topic/26787/unofficial-rrf-3-4-0beta7-2-files.

@jay_s_uk Ahh, so there is a just typo in the error message from M587 - I'll fix that. The docs describe the parameters correctly, though.

Use L for the DNS server and C for the country code.

@dc42 I did check the console and it had no errors reported. But I’m not clear that it captures anything when my laptop is asleep. I feel like it skips over anything incoming while asleep.

Is there a mode I can set the treats M0 like M1? I can’t ever think when I’d use M0. I never have before. More likely I think is your theory on SD read error (though I don’t know what that would happen either, just more likely). But wouldn’t that get captured in M122? Also the failure mode there should be a pause by firmware to allow for restart, e.g don’t turn off bed heater or motors and send warning. I was lucky that I happened to catch it. I was about to go to bed and it would have been ruined the next morning.

It is fixed in B7+2 🙂
see my post here 🙂

https://forum.duet3d.com/topic/25720/g30-stop-values-increasing-each-time/26?_=1641577026578

to confirm, Z is back on 3HC and multiprobing each point is giving good results again.

1ff898ec-e00f-498a-85ec-5bfe6c70528d-image.png

5fdb28ba-84da-43a8-8c68-edcaa5b31450-image.png

Thankyou @Phaedrux and @dc42