RepRapFirmware 3.2 planned improvements
-
It's hardly a continual push back. The 3.2 release includes nearly 40 improvements, not counting bug fixes.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 said in RepRapFirmware 3.2 planned improvements:
It's hardly a continual push back. The 3.2 release includes nearly 40 improvements, not counting bug fixes.
let me re-phrase then : why the push back ?
-
@CaLviNx Market conditions?
-
@Phaedrux said in RepRapFirmware 3.2 planned improvements:
@CaLviNx Market conditions?
which means what exactly ?
I think there is more than a few users waiting on functionality fixes (which in my opinion should have be a priority) which would allow the correct use of pre-purchased equipment to be used/maintained properly/easily
-
In short, there is a global shortage of 2660 drivers used in the duet 2 (turns out they are used in ventilators) and the Maestro is discontinued, so work on the mini5+ was pulled forward.
3.2 beta is in the works, so things are coming. We all appreciate the patience.
-
Could we gat a URL that lists the likely changes for 3.2?
I know DC42 said "You can see what's implemented in 3.2 in the RRF3 whatsnew file." but I have not been able to find that file ....
-
-
Two questions.
From the 3.2. planned improvements link it says - quote
"[Duet 3 expansion and tool boards] Increased performance, in particular the maximum step rate is higher than before"
I'm a bit fed up of asking the question because I've asked it multiple time over the last 12 months and never yet had an answer but I'll try one more time so here goes.....
Question 1. What is the maximum step pulse frequency for expansion and tool boards now, and what will it be?
There remains a long list of limitations for expansion boards which I have been trying to use for over a year. https://duet3d.dozuki.com/Wiki/Duet_3_firmware_configuration_limitations
Some of the fixes have been pushed back to being planned for release 3.3.0 now while some don't have any planned release number assigned to them. So .....
Question 2. What is the likely release date for 3.3.0 and for those items on the list of limitations which are not planned to be fixed in 3.3.0, is there any plan to fix them and if so when, or will they be permanent limitations?
-
@Phaedrux said in RepRapFirmware 3.2 planned improvements:
3.2 beta is in the works, so things are coming. We all appreciate the patience.
do people have a lot of choice ?
-
Looking at the link
I notice it is always very quickly updated with the firmware revision number in which you advise they will be rectified
The cynical among us would say maybe its time to remove the number to save yourselves the extra work of having to update that number on such a regular basis...
-
@CaLviNx said in RepRapFirmware 3.2 planned improvements:
do people have a lot of choice ?
¯\_(ツ)_/¯ -
Whilst I'm disappointed that my Wishlist items ( variables & multi-choice messages boxes) aren't in the mix for 3.2, we need to remember a few things.
- We all purchased the boards based on the functionality as at that day, and anything further is a bonus
- The vendor has to make a living in order to continue development, so sometimes that's going to alter the development path.
- The firmware is open source, so there's plenty of scope for people to help development if there's something that's critical to them. If it's critical to your business, then hire a programmer.
- Even this forum has a cost to the vendor
Everyone has the right to ask about promised features and especially bug fixes, but the above are the cold hard facts.
-
I believe your sentiments are accurate and warranted, though whether it’s my fault for not seeing the fine print - if I was more aware of some of the limitations of the tool board (the ones I am most concerned with) I may not have immediately designed a hotend around it until they were part of the firmware. When I went to buy it (actually the second one, since there’s been an improvement since I bought the first) the vendor’s page didn’t have a link or any reference to the limitations of the hardware/firmware. I don’t think that would a stretch to ask that such links be required of authorized vendors. The lack of pid tuning via the tool board is a pain, even with workarounds. Now watching 3.2 make its beta rounds before even getting to a 3.3 beta is going to be a bit painful.
I don’t fault the development team, it is what it is - I’d be curious what items would be more important to people if the user base were polled.
-
@Nuramori said in RepRapFirmware 3.2 planned improvements:
if the user base were polled
to be clear, I don't mind things as they are right now, I love that "planned" document exist, that's updated so we know what's going on, as for the pace and what's actually on the list and how it is put there I have confidence that it's done the best way possible with way more input than I have... I just want to comment on the "user base were polled" thing.
Altium was a great tool, most of it's original popularity came as it came as continuation of some of the best tools on the parket (p-cad, protel...) but then the owners got some crazy ideas and invested a huge amount of resources (human, time, money...) in to those ideas. Huge % of the user base did not care about that and Altium lost the huge chunk of the market, spent huge amount of resources in designing things noone wanted and they let the main product get stale... After some years of that they came to idea to create a "voting system", every paid customer have certain number of points and can vote for features. Features with highest number of points are worked on irrelevant to what "management" think is important. This brought Altium back to being one of the most influential and most used professional EDA tools out there.
Of course, not a fair comparison, the number of users, type of users etc. is very different. Size of the product too. That's why I believe the "management" of the Duet ecosystem probbly have all the info they need to know where to focus, but yes, pooling is a nice and open way to handle stuff... the only difference is, my "vote" as a person with 3 duet boards can't be the same as a "vote" of a company that's purchasing 100 boards a month
and if they need a feature it's understandably more important than some convenient feature I'd like to have 
I'm sure we can agree. -
@OwenD All good points. On the other hand, some of us were very early adopters. In my case, one of the main driving forces for that early adoption was for the Duet guys benefit. - so that they could use my machine to demonstrate their hardware at the TCT show. At that time, no list of limitations existed. One's natural expectation is that a later generation product would have features over and above what a previous generation product would have. Yet here I am over 14 months since I converted my machine and I still don't have the basic functionality that my Duet 2 used to have. Furthermore, we are still on 3.1 with 3.2 being planned soon but basic things like tuning heaters have been pushed back to 3.3. So on that basis, it could be another year or more before I get that basic functionality back. I'm sorry to say that I used to be a huge fan and spent weeks of my own time supporting Duet on their trade stands, but now that no more trade shows are planned, my usefulness to them is over so they have to thrown me under a bus. That's how I feel.
-
I absolutely get the frustration of seeing important features being delayed from 3.2 to 3.3 (and especially in @deckingman case, features similar to ones you used on Duet 2 that have been pending for a while). We don't make these decisions lightly.
During the update from 3.0 to 3.1 we had quite a drawn out period of betas and RCs -it was clear the release process needed to be improved. You will have seen that in 3.1.1 where RRF, DSF and DWC are now on the same firmware build versions, released at the same time. The key change was to reduce the time between releases, which necessarily reduced how many new features are on each release.
We have a finite amount of software development time. That said, certain things that members of this community already do absolutely help maximise what we can achieve, things like:
- Testing beta builds and reporting issues, especially on a wide variety of machines.
- Helping new users with issues.
- Contributing bug fixes and features.
- Posting examples of your machines and projects that show all of the many types of configurations using RRF.
- All the other activity that makes this a good place to interact and learn.
-
@deckingman said in RepRapFirmware 3.2 planned improvements:
Question 1. What is the maximum step pulse frequency for expansion and tool boards now, and what will it be?
I can only answer that for the tool board here. When it started it used to be as low as 10-12kHz. A first improvement increased this to a still low 20kHz. Latest firmware increased it to around 110kHz.
Manuel
Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
with probably always latest firmware/DWC (incl. betas or self-compiled)
My Tool Collection -
@OwenD said in RepRapFirmware 3.2 planned improvements:
Whilst I'm disappointed that my Wishlist items ( variables & multi-choice messages boxes) aren't in the mix for 3.2, we need to remember a few things.
Let’s just break this little fawning fandom down a bit, and provide an opinion from the other side of the coin.
You made a critical Faux Pas I’m afraid, I will explain why at the bottom in reply to your final point.
- We all purchased the boards based on the functionality as at that day, and anything further is a bonus
INCORRECT.
Maybe YOU did, but you CANNOT know what ANYONE else based THEIR reason for purchase on. It is not unreasonable (And certainly NOT a bonus) for those who were early adopters to at the very least "expect" the very same "functionality" of the Duet-2 Equipment from what is/was being pushed as "next-gen" equipment.- The vendor has to make a living in order to continue development, so sometimes that's going to alter the development path.
You could construe that as throwing the current "loyal" user base under the bus for the sake of future sales, a very dangerous game and a double edged sword. Alienating some of your greatest technical bleeding edge power users for the sake of the guy fitting a duet to his Ender-3 is a very good way to lose support very quickly. Remember even the Roman Empire fell....
- The firmware is open source, so there's plenty of scope for people to help development if there's something that's critical to them. If it's critical to your business, then hire a programmer.
This has already been covered above and also covered very well By Ian "Deckingman" suffice to say it is NOT unreasonable for the end user to "expect" what was/is listed as a premium product to AT THE VERY LEAST have the same functionality of equipment on the Duet-2 platform
- Even this forum has a cost to the vendor
Prey tell who is holding a Gun to their head to force them to provide a forum?
On the other side of that coin you could say that the forum allows them to gauge and collate large amounts of marketable data which could allow them to improve their profit margin, so it could be argued that a forum is a positive cost expenditure. Just as you cant make money unless you spend money.....
- Everyone has the right to ask about promised features and especially bug fixes, but the above are the cold hard facts.
This is where you committed the major Faux Pas. The above are:
YOU’RE OPINION (which you are entitled to) but you are not entitled to try to call them facts.
And the last time I looked at the definition of "opinion" in the dictionary it doesn't contain anything about "cold hard facts" as you so eloquently "tried" to put it, unless of course you are placing yourself in the category of being an "expert" in which case such an "opinion" is based on the following :
- a statement of advice by an expert on a professional matter.
And if that is the case, my question would be: What allows you to place yourself in the category of "expert"?
I personally never even knew there were ANY Firmware/Functionality limitations when I started purchasing Duet-3 Ecosystem equipment.
For both my personal and work units I had personally budgeted (and had obtained my work budget) to transition everything over from all Duet-2 to Duet-3 with tool boards, that equates to 7 personal machines and now a total of 21 work machines which are replaced on a fixed short term cycle, duet control boards on work machines are utilized by my university students to design/build/test & tune their own 3d printers in small groups and those printers are provided to local schools in the surrounding community after graduation of the current intake, and then the cycle repeats. My budget is already in place, my contract is up for renewal early next year and as an engineering educator I think I will take a sabbatical, so yet another reason to use the Duet ecosystem will be removed.
I had made my duet-3 hardware purchase based on the minimum "expected" functionality with that "expectation" being based upon the functionality of the Duet-2 Eco system. I don’t think it is unreasonable to expect the very same functionality AS A MINIMUM.
I had purchased a small number of Duet-3 boards to allow familiarization with the functionality of the hardware in readiness for the full transition over to the ecosystem. I was initially prepared to wait a certain amount of time for the functionality to come online.
But the continual :
-
adjective
-
forming a sequence in which the same action or event is repeated.
Yes continual, "deferment" of some basic functionality means that I have become unwilling to keep waiting until "who knows when" for some of that basic functionality to be rolled out.
The whole reason for using the Duet Ecosystem is functionality and ease of use, remove those aspects and the ecosystem no longer stands head and shoulders above other equipment.
In light of this I have taken the decision to abandon the use of the Duet Platform for work related projects and we will switch to suitable quality Marlin based Hardware with the integration of an Rpi with Octoprint, The students wont know any different and it means i have to sit down and work out a marlin/octoprint template instead.
This also means I will re-direct the annual financial offset towards other aspects of the project. I will continue with the Duet-2 Platform on home machines as I like the ease of functionality but the Use case & purchases for Duet-3 has been put on hold and the projects that they were to be used on is now on hold too, I do not wish to spend the extra time undertaking temporary hardware modifications or spending the extra time doing something manually with something that is for the most part an automated process with a Duet-2
-
@wilriker said in RepRapFirmware 3.2 planned improvements:
@deckingman said in RepRapFirmware 3.2 planned improvements:
Question 1. What is the maximum step pulse frequency for expansion and tool boards now, and what will it be?
I can only answer that for the tool board here. When it started it used to be as low as 10-12kHz. A first improvement increased this to a still low 20kHz. Latest firmware increased it to around 110kHz.
Thanks Manuel. No wonder it has been kept secret and no wonder my Z axis with 1mm lead screws choked at anything other than a crawl! The last figure I had for Duet 2 was 200kHz. So it has improved from being one tenth the speed of Duet 2 to around half the speed. Which probably explains why buying three new 2mm lead screws (more expense) with half the steps per mm allowed me to run my printer Z axis at the speed I used with Duet 2.
When you say "latest firmware", is that 3.1.1 or the forthcoming 3.2.? Just wondering if there might be further improvements planned for say another years time.
I guess I can forget running my extruders at the micro-stepping required to get the necessary resolution with a mixing hot end whilst still being able to retract at a reasonable speed. With Duet 2, I used to get hiccups at 128x so had to settle for 64x and was rather hoping that gen 3 with its faster processor would allow me to run that 128x. But it seems the opposite is true and now with Duet 3, I'll be limited to 32x or half what I had before.
-
@deckingman Hey Ian, you might have missed that I was talking exclusively about tool boards when it came to step rates. As you do not have tool boards (single driver, tiny form-factor) but expansion boards (3 drivers, larger) this does not apply to you. Nor does it apply to the main board. For both expansion boards and main board the step rates have been increased as well but not even near as much as for the tool boards. But they should be able to run your extruders with x64 I'd assume (might need some testing though).
I was referring to the upcoming RRF 3.2 since this bug was only found after RRF 3.1.1 had been released.
Manuel
Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
with probably always latest firmware/DWC (incl. betas or self-compiled)
My Tool Collection
