Topics created by ChrisP

What kind of names are you creating that are longer than 32 characters?

It would be worth testing with the recent 3.2 Beta releases.

@stewwy I've added this to the work list for RRF 3.4.

I have put new internal builds of RRF at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0 that report the virtual extruder posiion in 'move.virtualEPos'.

Please try that with the latest DSF/RRF bundle. I fixed an issue with filament sensors in it.

Thanks for that! As it happens, I'm actually using this on setups with D3 with SBC,and I guess in these cases the limit is in DCS?
However, I do have other systems running D2, so this is still really useful to know.

@chrishamm said in DCS Crash with 3.01-R10 / DWC 2.1.5 / DSF 2.1.1:

@ChrisP Thanks for reporting this, I've been able to reproduce it and it looks like this is related to CPUSchedulingPolicy=fifo. Once that line is removed from /usr/lib/systemd/system/duetcontrolserver.service and the Pi is restarted, the problem does not seem to occur any more. So I'll remove that particular line in the next version again.

Yeh, this was the conclusion I came to too after commenting it out. Have updated to 2.1.2 and it's now all running well - thanks 👍

@Garfield said in DCS Crash with 3.01-R10 / DWC 2.1.5 / DSF 2.1.1:

No complaints here, apology not needed, got into the RC stream, knew the risks, happy to help diagnose and fix.

Yup, I'm the same. While the ideal is to have a working printer, tracking down the bugs is interesting too 😆

@chrishamm

Thank you for the assistance.

I'm on RRF2 until SeeMeCNC updates to RRF3 as I enjoy their help and they aren't supporting RRF3 yet. I'm not yet ready to fly on my own. 👶

@chrishamm Not fixed with DSF commit d46965d
and RRF commit 56c8e1d583d7f17e5c4266c7ce8cc227d40e3bdd (SBC improvements)

Still hanging for many seconds. No messages in DCS log.

@chrishamm Thanks.

@ChrisP said in Duet3 SBC Power Warnings:

vcgencmd get_throttled

I have a Pi4B with a Logitech C270 USB camera being powered by the "default" jumpers and ribbon cable. No throttling. (No display either, so I can't say if lightning bolt or not). It is actively printing as I'm checking.

At various points in time, I've also had a 7" touchscreen powered from the Pi. I will put it back on when a long print finishes (about 8 hours from now), and check throttle and the lightning bolt.

But, as a 'soft' data point for right now, no issues with Pi, touch, Camera.