Topics created by brendon

@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.

@dc42 @T3P3Tony

The new board arrived and the Out channels are now properly controlling the LED strips. Thank you for helping me sort out my issue. The offending hardware is boxed up and will be arriving to you shortly. Thanks again!!!

@dc42 Thanks for the update, I'll keep an eye on the release notes!

@brendon Sorry to hear you're having problems with the CAN board while connected over the SBC. I'd like to figure out why it is happening, but I will need two separate debug logs for this. Can you please connect your Duet 3 over USB to a computer, open a serial terminal, send M111 P3 S1 and try to reproduce this bug once with the SBC connected and once without it? I hope that will allow me to spot differences in the execution of G/M/T-codes and to track down the underlying bug.

Nevermind, I found the issue in the release notes.

Duet 3 users: there is no longer a default bed heater. To use Heater 0 as the bed heater, put M140 H0 in config.g (later in config.g than your M950 H0 command).

Please try 3.0beta11, along with the corresponding update to DSF unless you are running in standalone mode. Take note of the known issue with some types of Z probe that is described on the release page for 3.0beta11.

Upgrading all of the firmware/softwares resolved the issue. Thank you all for the help!

That sounds odd. Please ensure you are using the latest DSF and RRF, and if the problem still occurs, post your config.g file.