Job status by filament usage



  • Something happened to break this some time back and there was supposed to be a fix, but IIRC, there's no more active development for the 2.x series firmware. Is this going to be fixed?

    Bump, @dc42 ...



  • I also have this issue. It appears it's not properly cosidering the return on retraction in the filament tracking, so each retraction offsets the filament usage improperly. Bump. @dc42



  • This post is deleted!


  • @dc42 bump bump



  • @dc42 bump bump bump



  • is it true that there is no more active development of the duet 2 board firmware or RRF2?
    If so this sucks because why? the new board does not have the possibility to install servo drives.



  • @NitroFreak No it isn't true. David recently said in another thread - quote :

    "................I want to look at this again, but I don't have time right now because I have to finish RRF 2.04, RRF 3 and Duet 3 expansion board support. Please remind me in 2-3 weeks."

    end of quote.



  • @NitroFreak And from this thread

    https://forum.duet3d.com/topic/11005/news-on-duet-3-release/2

    David has said that the Duet 2 will still remain the mainstream board will minor development.

    Regards,
    Sam


  • administrators

    Firrmware development will shift to RRF 3 which runs on Duet 2 and Duet 3. Don't expect major new features for RRF 2.



  • @deckingman this is another example of what I believe to be improper prioritization.

    I've brought this up before. There is a large install base using the duet 2 boards. Current customers shouldn't be ignored to do new product development.

    You're not going to keep those users. If there was a comparable alternative, I would have switched long ago.

    This particularly ticks me off because it's a regression.

    Seems like they could use a DevOps guy to help build tools that can automate testing, code analysis, etc.



  • @gnydick RRF3 works on duet 2 boards as well as duet 3, so I really don’t see what the problem is. RRF3 gives more flexibility in regards to assignment of motors, end stops and heaters and hopefully soon conditional g code which will be a great feature. People can move onto it if the so choose. They also have not said that development on the duet 2 family hardware will stop entirely. The changes between the last two releases of duet 2 boards has been minimal, so again I don’t see what the problem is.

    My 2cents worth anyway.

    Sam



  • @gnydick You talk like I'm part of the Duet team. I'm not. I'm just an end user like you. So don't shoot the messenger.
    But unlike you, I quite like the Duet range of products. If you actually read the quote from DC that I posted, and also the response that Tony posted, you'll understand that it is in fact the current user base that is being given priority. For further confirmation of that, I can also say that my printer which uses prototype expansion boards is in a non working state and has been ever since those boards were fitted. This is because there are some as yet unresolved issues with the expansion board firmware. But I'm not making a fuss because I understand that these issues are being given lower priority than issues related to current, non prototype boards.



  • @deckingman I didn't mean to. I was using the general "you".



  • @samlogan87 my issue is that, every time I have reported a bug, I was told it is fixed in the next release and encouraged to use the RC until the next stable came out. Well, the RC invariably broke something else. So, I end up waiting for MONTHS for the next stable because I don't want to find a new bug. Also, when the fix is already known, he refuses to apply it to the current release. Fixes only go forward. This is not an acceptable software development practice IMHO.



  • @samlogan87, oh, also, I wouldn't touch RRF3 with a ten foot pole until it's been out at least 18mo. I can guarantee it will not be as stable as RRF2.



  • Time for my opinion! 😂

    I greatly appreciate the Duet team, and their support is always far above-par! I find it quite impressive that they do their customer support themselves, and come out with major new features on the time schedule that they do! Software and hardware development take an enormous amount of time, and somehow they're still on the forums seemingly almost 24/7!

    Hats off to the Duet team, @dc42 and @T3P3Tony, as well as all the "regulars" such as @deckingman, @Phaedrux, @zapta, and all the others! Your tremendous work and dedication make the Duet ecosystem what it is - awesome boards with great support and insanely fast development!

    @gnydick, a board with even slightly better support would be almost unbelievable! Be sure to tell me if you can find one! 🤣

    I've tinkered with software development before, and I think their support is far above what's required or even expected.

    Thanks again!



  • @JadonM There's a difference between keeping up to date with questions on the forum where people need help with configuration and bugs. The former is fantastically supported, you are right. It's the bugs that get short shrift.



  • I wasn't going to comment but you're acting like bugs are ignored. Bugs do get fixed, they just don't get back ported into every old version of the firmware. And for some reason this really sticks in your craw. But frankly it's pretty unrealistic to expect from such a small software team. Even a long term service style release would require an inordinate amount of work.



  • @Phaedrux you're allowed your opinion. I'm not asking for things to be back ported to every old version. I'm asking that a known bug-fix be incorporated into just the last single stable release.

    As for not being ignored. I've reported one bug that I've managed to reproduce with video evidence on 4 different duet boards and it's just been dropped on the floor. As far as I can tell, it will never be fixed.



  • @gnydick said in Job status by filament usage:

    @Phaedrux you're allowed your opinion. I'm not asking for things to be back ported to every old version. I'm asking that a known bug-fix be incorporated into just the last single stable release.

    As for not being ignored. I've reported one bug that I've managed to reproduce with video evidence on 4 different duet boards and it's just been dropped on the floor. As far as I can tell, it will never be fixed.

    It will be fixed when a new version goes stable.
    Job status by filament usage isn't a critical thing with need be fixed immediately.
    So don't be rude and wait for RRF 3 to be stable.


Log in to reply