Do we know what release will have variable support?

I've been getting into customizing various aspects of my printer, and in a few scenarios variables are pretty much mandatory.

Are we looking at 3.2, 3.3, something even further out?

I personally prefer to make things as simple as possible, and can't get much simpler than a hard wired touch screen.

if anything was to change, I'd vote for larger screen higher resolution screen option, Perhaps a 10" model.

I'm not sure what the cost would be but you can find a lot of 10" 1080p tablets today for under $100 USD.

@deckingman said in Whats does the roadmap look like for variables?:

@pixelpieper This isn't a matter of which new features should take priority. This is a case of restoring basic functionality that already exists in version 2 firmware to version 3 firmware before adding new features.

I'm a developer by trade i think you need to consider a few things!

• Just because a piece of software functionality worked on one piece of hardware doesn't mean it will work on another with different architecture.
• I'd be willing to bet their are substantially more v2 boards in the wild than v3, so the wants and needs of v2 users will most likely take precedence.
• Some of the new features might make it easier to fix outstanding issues. On several occasions i have done this, mainly because it involved rewriting a sub system from scratch.
• From what I can tell, your use case is very much and edge case, so you should expect issues imo.

@deckingman said in Whats does the roadmap look like for variables?:

I'll bear that in mind but I suspect anyone who bought the latest generation of a product such as a 'phone would be somewhat miffed if many of the bundled apps (which worked on the previous version and are still bundled with the new version), didn't work.

The underlying hardware architecture for phones hasn't changed in a long time though. I think almost every phone on the market is based on ARM. If the next generation was x86 based, people would go mad because all kinds of things would break.

If people don't want to deal with issue, then they shouldn't be an early adopter. Doesn't matter if it's phones, sbcs, tvs, cars etc.

@CaLviNx said in Whats does the roadmap look like for variables?:

As a user I expect the "evolution" equipment (that I have paid for) to "fit for purpose" its not as if the end user is forcing the supplier into supply, but the supplier does use the "evolution" features to entice existing (and new) users into making a purchase.

No one is forcing you to buy it, and it's on you if you fall for a sales pitch, or can't control your consumerism!

@CaLviNx said in Whats does the roadmap look like for variables?:

I must thank you for this post, it has reminded me why it is folly to try hold a cognitive discussion with a fool who thinks he is clever, as it is akin to playing chess with a pigeon, because no matter how good you are at chess, said pigeon is still going to shit on the board and strut around like it won anyway.

And on that note any further input from myself is pointless.

I wouldn't call you a pigeon, but if that's how you see yourself then so be it!

@deckingman said in Whats does the roadmap look like for variables?:

But as you profess to being (quote) "a developer by trade" your statement is a classic excuse that I see is becoming more and more prevalent among your profession. Personally I find it insulting to blame purchasers of products for what is essentially inexcusably bad conduct on the part of the person who has not done his/her job properly.

You can be insulted all you want but your comments imo show a lack of understanding with regards to the subject at hand. No developer, team of developers, company, or even massive tech industry giant can ensure no user ever has issues, specially when you are talking about non trivial applications.

The number of potential issues grows almost exponentially with the complexity of the software. Thus, project/product managers usually focus on bugs/features/issues that are of a concern to the majority of the user/revenue base.

For example what would you fix first? A bug related to one users who is running a 15 year networking card, or a bug (that's not your fault) that affects several thousand people because Microsoft decided to make a change and then push it out in an automatic update without telling down stream companies/developers/manufactures?

Now scale that up to hundreds or thousands of bugs and feature requests.

If you had a trade person in to undertake some work which turned out to be sub-standard, would you find it an acceptable excuse if that trade person turned around and told you that he/she hadn't been in business or hadn't been doing the job for long, therefore it's your fault for being an early adopter?

I personally wouldn't find myself in that situation as i can do most trade stuff myself. Plumbing, electrical, carpentry, care repair etc. Even if i didn't have the skills I do, i'd still check a contractor's credentials.

@CaLviNx said in Whats does the roadmap look like for variables?:

As a user I expect the "evolution" equipment (that I have paid for) to "fit for purpose" its not as if the end user is forcing the supplier into supply, but the supplier does use the "evolution" features to entice existing (and new) users into making a purchase.

No one is forcing you to buy it, and it's on you if you fall for a sales pitch, or can't control your consumerism!

@deckingman said in Whats does the roadmap look like for variables?:

I'll bear that in mind but I suspect anyone who bought the latest generation of a product such as a 'phone would be somewhat miffed if many of the bundled apps (which worked on the previous version and are still bundled with the new version), didn't work.

The underlying hardware architecture for phones hasn't changed in a long time though. I think almost every phone on the market is based on ARM. If the next generation was x86 based, people would go mad because all kinds of things would break.

If people don't want to deal with issue, then they shouldn't be an early adopter. Doesn't matter if it's phones, sbcs, tvs, cars etc.

@deckingman said in Whats does the roadmap look like for variables?:

@pixelpieper This isn't a matter of which new features should take priority. This is a case of restoring basic functionality that already exists in version 2 firmware to version 3 firmware before adding new features.

I'm a developer by trade i think you need to consider a few things!

• Just because a piece of software functionality worked on one piece of hardware doesn't mean it will work on another with different architecture.
• I'd be willing to bet their are substantially more v2 boards in the wild than v3, so the wants and needs of v2 users will most likely take precedence.
• Some of the new features might make it easier to fix outstanding issues. On several occasions i have done this, mainly because it involved rewriting a sub system from scratch.
• From what I can tell, your use case is very much and edge case, so you should expect issues imo.

@arhi The firmware will run on the DUET 2 ETHERNET/WIFI already, so it doesn't need to be tied to the DUET 3 issues.

Someone just mentioned the fan/axes cheat to me in a discord conversation, but it seems like that could cause potential problems if you wanted to share a macro you made with someone else. Basically you could override someone else's config.

Do we know what release will have variable support?

I've been getting into customizing various aspects of my printer, and in a few scenarios variables are pretty much mandatory.

Are we looking at 3.2, 3.3, something even further out?

@BoA I think you missed my point. the panels you want to use are the panels that are being mass produced, so you can get them at a good price.

The benefit of a larger panel would to fit more information on the screen.

@BoA said in PanelDue future hardware direction:

IMO panel due is just fine. HD display with milions of colors? This is not a multimedia player. It is just not needed.

That's what the major panel manufacturers are making now.

for example 10.1" seems to be the most prolific panel size for tablets now. The most common resolutions seems to be 1024x600, 1280x800, and 1920x1200