1. If you want to understand how product development is done in the "real world", get a job in your field of choice. learn, think critically on the job, ask people smarter than you in the job to gain insights and gotchas.
Thanks for sharing your perspective. I’m approaching this as a hobby project, not as a commercial product. My main goal is to learn how engineers go through requirements and make design decisions in a systematic way.
I’ve already gone through the basics of embedded systems, Protocol's and develop mini projects and now I want to challenge myself by attempting a more advanced project that I find interesting. That’s why I’m asking these kinds of technical and design questions. For me, this exercise is less about building a finished, production-ready system and more about understanding the thought process behind solving real-world problems.
Even if I can’t complete everything exactly as it would be done in industry, I want to follow the same steps requirements, specifications, design, development, and testing because I believe that’s how I’ll really learn.
What you have there are vague wishes. and a semi decent business analyst (forget an engineer, they are far more expensive) will blow your wants out of the water.
Which is it? a soap manufacturing or a qr code scanner for small sellers ? both are opposite in use cases - one is mass manufacturing and the other is low volume. one is perennial manufacturing , the other not so much.
One of them needs to be specced to handle the throughput of several hundreds of thousands daily, the other very infrequently.. you see where I m going with this...
Actually, I wasn’t trying to define an exact business case like soap manufacturing vs. small sellers. What I was really looking for was a use case where information is printed on a card/package and then verified . So I just came up with an example scenario to work with, to make the problem more concrete.
secondly, lets take the image you provided.. what happens if there is an error in any stage? how should it be "handled" what do you do with the already printed qr codes that have been rejected ? reworked or discarded? how about the storage of the printed codes ? 1 ? 100? 1 million ? where ?? how do you want a machine to take a printed code and move it on the conveyor belt? what should the system do when there is an error ? stop the line and wait for human intervention or discard and continue?
more importantly, why not just invest in a good industrial printer with a high dpi to ensure the qr code is printed correctly? they have very very very low printing errors?
You need to have a much much more clearer idea of what you want your system to do than just those bullet points..
Yes,
this is exactly the part I want to discuss more deeply, so thank you for raising it. For example, if the system detects a continuous series of 10 defective cards, it should generate an alert message and stop the production line to minimize losses. The reason for stopping at that point is to reduce waste and minimize losses, instead of continuing to produce more defective items.
Regarding rejected cards, once a QR code is found to be defective, that card cannot be reused or reprinted. All such cards will be diverted and collected in the reject bin shown at the end of the conveyor in the diagram. Right after the reject bin, I am planning to add another collection bin for the verified (good) cards so that separation is automatic and clear.
As for the card movement, you can see in the image that at the start of the conveyor there is a vertical frame that holds the stack of cards. From the bottom, each card is released and moves onto the conveyor belt in sequence, which then carries it through the printing and inspection stages.
Of course, I understand that industrial-grade printers with high DPI are designed to minimize printing errors, and yes, they can provide very reliable results. However, in my concept, verification still has the highest priority. Even with a high-quality printer, errors can happen occasionally due to any factors By verifying every printed card, the system ensures that only correct and readable card reach the final collection bin, while any defective ones are automatically rejected
In short, my main focus here is to design a system that not only prints but also actively verifies and handles errors in a controlled way with alerts, automatic rejection, and proper collection of both good and defective cards. That’s the part I’m most interested in learning
