@chrishamm

Something to wait for, appreciate your efforts with RRF.

@droftarts Thanks for the keen eye. This behavior didn’t start until I just updated to 3.4.0. I will update my homing files and see if that fixes the issue.

@steviegregory said in Can’t store heater fault details in returned message:

@owend Is it possible to do this on RepRap 3.1.x, before the addition of events in RepRap 3.4?

No.

@braeden-0 Nevermind the issue was my router. 🙂

@tron_lives said in Manually extruding issues with new interface:

@flyscha I've checked my config and it looks like I'm still having the same problem despite having the correct lines. Is there anything else I can check? I'm only able to get the retract and extrude to come up if a start a job and then immediately cancel it.

You can only extrude and retract if two conditions are met. 1. A tool must be active. 2. The tool must be hot.

From what you say about starting and cancelling a job, it sounds like you still don't have "T0" in your config.g file as I suggested before. So you are relying on there being a "T0" in your sliced gcode file.

@jay_s_uk Yeah i am trialing the revo hotend with the upgraded smart efficator board (a lot more accurate and less prone to the vibration issues when bed levelling) and using a fixed mounted hemera extruder not the flying spring mounts, seems to be more stable and prints faster.

@jay_s_uk I already added it to the upcoming release candidate 2 so no worries. In a future version (3.5) I may change the build script to add it automatically; at present I always have to add it manually after building, so sometimes I happen to forget that step.

The object model changes since 3.4.0 were pretty marginal, so the OM explorer should continue to work fine for most keys. The OM plugin won't crash if it fails to find a certain key either.

Thank you, @dc42.

I was getting a bit tied up with this last night, but in the cold light of day - and after a good nights sleep! - a clear look at the problem certainly helps.

My thanks to @JoergS5 for pointing me towards the Z height, and everyone else who joined me on this journey.

Now all I have to do is find out why and prevent it from ruining my day again! 👏 👏

@dc42 Looking forward to it! Thank you all for the help.

@nightowl999 Easiest way: Right click the file for the 3d gcode viewer.

Thank you, @oliof

@brendon said in Temperature warnings are so frequent that DWC control is lost:

it's not a huge leap to imagine that if more drivers started emitting incessant warnings that the actual machine performance could be affected. It's also possible that the loss of DWC control was not due to the volume of warnings, but some other gray area WRT thermal accumulation. I can only speculate as the last thing I saw in DWC before it disconnected was a flood of warnings.

Yes this will be investigated. Thank you for reporting it.

@phaedrux Wow! This is a real fast response. One more reason to be very pleased to pick up an original Duet. Thank you for your prompt answer phaedrux. I can confirm that solved the problem, because meanwhile is what I’ve done and now works again. It seems that the DNS was not resolving the address correctly, isn’t it?
Thank you so much again. Have a nice evening.

@nxt-1 Right, that's a dependency of DWC and it's used by the temp+layer charts and the IS+CL plugins. I'll check if I can upgrade that one as part of DWC 3.5.

@ccs86 said in DWC Seems to Crash After Uploading a Print:

Bug seems to be gone in 3.4.1 RC1

Thanks for confirming this. Based on your report and on another one on a Duet 2, I suspected that in some configurations parts of the object model might be getting too large to fit in the available buffer space to send to DWC. So in 3.4.1 I increased the buffer space on Duet 2 and Maestro, and shrunk the object model data a little.

@ritz One mistake I see is people keeping the negative modifier in the G31 value, as the default value we provide with the printers is G31 Z-3, just so that in the initial setup it

So if you'd for example get a value of 1.25, from the Z-offset maco, and you don't erase the -, but just replace the 3 with 1.25, you'd get a G31 value of Z-1.25 instead of Z1.25. And with that, the nozzle would be 1.25+1.25 away from the print surface.

You can always reach our support directly at support@modix3d.com, preferably with a copy of your config.g files so we can check that as well.

@vrghost I don't see this behaviour on my test setup, when HTTP code 503 is returned DWC stays active and only attempts to reconnect after 2 failed retries. What browser are you using?

@jay_s_uk Thanks for the reminder, I think I found the problem and will fix it in 3.4.1(-rc2).

I figured out the issue. The cables I was using were crap. Replaced them with a higher quality cable (I bought these from amazon: https://www.amazon.com/dp/B07GD2PHX9?ref=ppx_yo2ov_dt_b_product_details&th=1) and it's working without issues with default sampling rate, resolution, and SPI clock frequency:

M955 P0
Accelerometer 0 type LIS3DH with orientation 50 samples at 1344Hz with 10-bit resolution, SPI frequency 2000000

Thanks, @mintytrebor. I'm looking at your BtnCmd already, but I never thought to add macros as you've suggested.

Thank you 👍