DCS Crash with 3.01-R10 / DWC 2.1.5 / DSF 2.1.1
-
@Danal
Yup, that sounds in-line with the sort of things I'm seeing. I wonder if your first failed power cycle was temperature related? The first time I left the crash unnoticed it cooked the Pis CPU - I noticed the smell of something warm before realising it had all crashed. After this it took a couple of resets to get things to boot normally again.
I've had occasions where it'll boot and I can SSH in with a couple of simultaneous sessions but as soon as I click connect on the DWC session on the Pi (chrome and DWC auto-load on boot), then it'll cause the crash sometimes.@gtj0 said in DCS Crash with 3.01-R10 / DWC 2.1.5 / DSF 2.1.1:
@Garfield I can reproduce your crash. It's the M591 command for the filament sensor. I'll add more info to the GitHub issue.
Which filament sensor do you use? I have a laser one that I disconnected a few versions back as it caused another bug and because I never managed to get useful data from it. I might try re-connecting to see if it's the same bug I was seeing before as the current descriptions sound very similar.
-
I use the Duet magnetic one, has worked pretty well up till now although the data reported wasn't always 'accurate'
-
Data point: Printing for 4.5 hours as I type this.
Filament Sensor: None.
Also, not that it should make any difference, it is a toolchanger.
-
@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.serviceand 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.@Garfield I could reproduce your problem, too, and it will be fixed in the next DSF version. This error won't occur again in future versions. Sorry for the inconvenience.
I'm happy to help but please keep in mind that the
unstablepackage feed is primarily for testing purposes and that bugs can occur - even though I perfectly understand they can be quite annoying. So thanks again to everyone testing it and reporting issues.Duet software engineer
-
No complaints here, apology not needed, got into the RC stream, knew the risks, happy to help diagnose and fix.
I started work on a test plan but it is kind of hard to know what to test beyond normal user interraction, when things blow up as a result of previously functional code it is hard to know how to report it, harder to know the information needed to assist in the debug / analysis / remediation.
I find it frustrating and interesting - just sometimes it is more frustration - and even then more frustration at a lack of ability to trace through the fault.
Blunt question - Is it possible to seperate the apps such that loss of DCS does not prevent access to the web console, yes I know information won't be updating but a big red status flag 'No DCS Communication' or similar could be added. Make it possible to access diagnostic logs and still be able to edit .g files from the web gui. Possibly have some 'macro' to collect basic diagnostic information for submission.
I'm not a linux fan, I don't fully understand the code, I'm trying to understand, sometimes the frustration hits the keyboard.
You want me to do some tests just reach out, I think I'm getting pretty good at switching versions in and out, which is a big thank you to all that have stepped in and helped.
-
I have just released DSF 2.1.2 which fixes both issues reported by @Garfield and @ChrisP. Please let me know if you notice any other problems.
Duet software engineer
-
Other 'problems' - well not a problem but how can I get 'All' my fans to display - and I do mean all not just those allocated to a tool.
My MCU fan will not appear, the thermostatic doesn't (would be nice to have that up there with adjustable on / off thresholds).
Hows that for off topic
-
@chrishamm confirmed functional thank you.
-
@Garfield Thanks for confirming! Thermostatic fans don't show up yet. If other fans aren't visible, check the "Print Status" page -> Fans -> Change visibility.
-
They don't appear in the 'visibility' options, only one that does is my part cooling. Will start another 'thread' ...
-
Put 2.1.2 on, and this is a very soft data point, I could easily be letting expectation affect perception...
The Pi seems "snappier" at the command prompt.
Will print and post hard data later.
-
@Danal With the DCS no longer classified as a "real-time" process, the command line should be a little snappier.
-
@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.serviceand 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
