Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.
-
@Danal have exactly the same issue...
-
@dc42 said:
There are no plans for a RRF 3.01-RC7 release, because there are no bugs in 3.01-RC6.
-
@chas2706 said in Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.:
because there are no bugs in 3.01-RC6.
I would think its obvious that we're talking about "known" bugs; and plans change.
Virtually no amount of testing can prove the absence of bugs.
-
Same print job finished just fine, about 3 hours, on RC4 and friends.
Duet Web Control 2.0.7
Board: Duet 3 MB6HC v0.6 or 1.0 (MB6HC)
DSF Version: 1.2.5.0
Firmware: RepRapFirmware for Duet 3 MB6HC 3.01-RC4 (2020-03-16b1) -
I would report all DSF issues to @chrishamm on github...
https://github.com/chrishamm/DuetSoftwareFramework/issues
or in this thread... https://forum.duet3d.com/topic/15343/dsf-1-3-1-unstable-released -
@gtj0 How would I determine whether to post in RRF 3.0RC6 vs. DSF 1.3?
Delta / Kossel printer fanatic
-
@Danal run the job in Duet 3 standalone with the same settings and firmware version?
Ian
-
@Danal said in Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.:
@gtj0 How would I determine whether to post in RRF 3.0RC6 vs. DSF 1.3?
I have asked that question many times and I've never received a satisfactory response.
@droftarts said in Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.:
@Danal run the job in Duet 3 standalone with the same settings and firmware version?
Ian
Don't get me started.
It's not always easy to just "run in standalone mode". In my case, I have to remove the covers from the printer to get to the sd card and remove the cable between the Duet and the SBC.
I also don't believe it's the user's responsibility to have to determine which component of the system is at fault. That should be Duet3D's responsibility. The fact that RRF and DSF seem to be owned and operated by 2 separate companies irks me to no end.
-
I agree. From a user's perspective, DSF and RRF are the same thing. Gcode goes in one end and motion comes out the other.
For example, it is incredibly weird that M999 restarts RRF but not DSF, even when it is absolutely reproducible that any number of hangs are cleared ONLY by restarting DSF. Which a user of this "gcode everywhere" system has no way to do (other than on the Pi, and with sudo no less!)
I love Duet and have been a happy advocate for at least a few years. I am aghast at the latest directions and actions. I sincerely hope they course correct. (To be clear, I'm all in favor of SBC/Pi integration. It is the way that's being accomplished that is going to send a great company downhill if they don't change something).
Delta / Kossel printer fanatic
-
Also, as regards how easy to "reproduce in stand-alone", I don't have any ethernet that will reach. I am not the first owner of this house, and there is not an inch of Cat anything in it (except about 1 foot (1/2 meter) between the cable modem and the main wireless router). I'm also not real motivated to make a special SD card, run special ether, etc, etc, to run the printer in a mode which I will literally never run. It goes back to DSF and RRF being layers of the same thing, and they should be supported that way.
-
OK, rant over. Sort of.
Delta / Kossel printer fanatic
-
And here I am, just sad that RRF 2 isn't getting the attention it needs and deserves! We need an LTS team!
-
@Danal said in Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.:
I agree. From a user's perspective, DSF and RRF are the same thing.
I had my sarcastic rant earlier when I quoted DC42's statement that RRF 3.01-RC6 has no bugs.
I agree, I too am not interested if any particular bug is within the RRF, DCS, or DSF. They should all work together as one whole package.
The issue I have is that like you I love the idea of Duet 3 with SBC but there are many problems at the minute and all I seem to get is "It works ok in standalone mode".
If I wanted "stand alone" I would not have purchased RRF 3 and Raspberry Pi 4!
Rant over!
-
@Danal said in Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.:
and with sudo no less!
this was a topic way back when, sort of intermingled with permissions on the /opt/dsf/sd folder and /dev/spi nodes and the priority was to get it working first, then revisit.
as such i didn't poke in great detail, but as access to the spi node can be solved by group permissions, listening to port 80 (or any port below 1024) sounds like the last hurdle. the easy woraround would be nginx and a reverse proxy which would also ease setting up ssl with sometihng like letsencrypt (even if not exposed to the internet)
There are larger issues to deal with first i guess - but I will say the state of the supporting firmware and software has not been clearly communicated following the release of the hardware.
I believe I in August said I expected to run RRF2 as the stable version for 6-12 months, and the unfortunate truth of it is that with the limited team developing RRF3 + DSF they need the depend on the community for testing to stand a chance at getting ready for main stream use in such a short timeframe.
At the end of the day its up to the user to choose something tried and true, or accept that early adoption comes with a price tag in more than one sense.
-
@gtj0 said
Don't get me started.
Okay, sorry I mentioned it.
@Danal said
OK, rant over. Sort of.
Okay, sorry, won't mention it again! We appreciate all your support!
@chas2706 said
Rant over!
No, really, I'm sorry for suggesting it, I'll never say it again!
@bearer said
At the end of the day its up to the user to choose something tried and true, or accept that early adoption comes with a price tag in more than one sense.
I agree. It's just taking time to get DSF (which is pretty much brand new) up to speed with the rest of the firmware (painstakingly developed over many years). But without community interest and expertise getting it working, reporting bugs and fixing, it will take much longer. So once again, thank you all for your continued support.
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@droftarts said in Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.:
I agree. It's just taking time to get DSF (which is pretty much brand new) up to speed with the rest of the firmware
The activity shown on GitHub regards DSF says it all.
-
@gtj0 said in Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.:
It's not always easy to just "run in standalone mode". In my case, I have to remove the covers from the printer to get to the sd card and remove the cable between the Duet and the SBC.
I find that I can switch between standalone and SD mode just by inserting the SD card or not, without removing the SBC cable.
-
@chas2706 said in Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.:
I had my sarcastic rant earlier when I quoted DC42's statement that RRF 3.01-RC6 has no bugs.
I was sure I typed "no known bugs" when I composed the message, however I composed it on a smartphone and somehow the "known" got lost.
There are now some known bugs in RRF 3.01-RC6 so we are preparing to release 3.01-RC7 along with updated DSF and DWC. See https://github.com/dc42/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md for the changes to RRF.
-
@bearer said in Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.:
At the end of the day its up to the user to choose something tried and true, or accept that early adoption comes with a price tag in more than one sense.
Disconnects in the way that RRF vs DSF are being handled by Duet the company are equally applicable to the 'full' releases.
-
@bearer said in Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.:
and with sudo no less!
this was a topic way back when, sort of intermingled with permissions on the /opt/dsf/sd folder and /dev/spi nodes and the priority was to get it working first, then revisit.
as such i didn't poke in great detail, but as access to the spi node can be solved by group permissions, listening to port 80 (or any port below 1024) sounds like the last hurdle. the easy woraround would be nginx and a reverse proxy which would also ease setting up ssl with sometihng like letsencrypt (even if not exposed to the internet)
I withdraw my comment regarding sudo. It diverted attention from the real issue: What is the GCODE to restart the system ?
