It was only about a week ago that you posted a glowing review of how great your first two months were with this printer, and how awesome the output quality is. Suddenly you’re in here ranting about how Velleman owe you constant software updates for an open source package?
You haven’t made a clear case for why this bug fix is so urgent to you, or should be to anyone else. I have not seen this behavior in my printer, I haven’t seen other people complain about it, and you yourself haven’t explained what problem you are experiencing. If you expect a vibrant developer community here, and you expect the company to share your urgency, you need to tell us what the actual problem is.
You made an oblique reference to having your printer somehow go out of bounds, but I haven’t seen you describe what you were doing or what you were printing at the time. You haven’t given the folks at Velleman, (or any of the community members here) any way to reproduce your issue, and you don’t seem to have a plan to determine whether updating your firmware actually addresses any issue.
I question your methodology. If you don’t know how you made it happen, you cannot evaluate whether the new firmware fixes it!
If you have a real-world scenario where this bug could affect all of us, I would appreciate if you would actually share those details with the community. And if you don’t have that, then admit that you are simply grasping at straws, applying patches because the description fits a symptom you think you might have seen.
Velleman have delivered a more than functional product. As a company, they need to balance your desire for cutting-edge features against the basic goal of providing a stable product. Unless there is a compelling reason for them to promote a new firmware update, it only creates extra work and confusion for all of their customers. You haven’t made a case for why this patch is necessary.
So good luck with your printer. I hope you will continue to contribute to this community and share your experiences. I am sure you will learn a lot, now that you have started looking at the code.