Tutorial For Good Hardware Circuit Design Ideas To Share

We have learned a lot of knowledge about components, but we still can’t design the circuit we want at will. This is a problem that troubles many people. After all, we lack theoretical knowledge, and ideas of circuit design, and practical experience

In the design of a hardware circuit, in addition to the need to master the hardware design foundation, a variety of design software, tool operation skills, and so on, it is more important to develop good hardware circuit design ideas, which can help you better, targeted to complete it.

How to train the design ideas of hardware circuits, the following for everyone to organize the basic process of design.

Circuit Design Ideas

1) General idea.

Designing the hardware circuitry, the big frame and the architecture has to be figured out, but it’s not easy to do that. Some of the big frameworks may be their boss, teachers have already thought, I just put the idea of concrete implementation; But for others, you need to design your own framework, figure out what you want to do, and then find out if there’s a reference board that can do the same or similar thing. (Learn to use other people’s work as much as possible; the more experienced you are, the more likely you are to borrow from others.)

2) Understand circuits.

If you find the reference design, then congratulations, you can save a lot of time (including pre-design and post-debugging). Copy right away? On the one hand, it can improve our ability to understand the circuit and avoid mistakes in the design.

3) No reference design found?

It doesn’t matter First determine the large IC chip, find the Datasheet, see whether its key parameters meet their requirements, which is the key parameters they need, and can understand these key parameters, are the embodiment of the ability of the hardware engineer, which also needs to be accumulated slowly for a long time. During this period, you should be good at asking questions, because you can often be reminded by one word of something you don’t know, especially hardware design.

4) Hardware circuit design is mainly three parts, schematic diagram, PCB, BOM table.

Schematic design is to convert the previous ideas into circuit schematics. It’s very much like the circuit diagram in our textbook. The PCB refers to the actual circuit board, which is converted from the schematic diagram to the mesh table (the mesh table is the bridge between the schematic diagram and the PCB), and the specific components are placed (laid out) on the circuit board, and the electrical signals (wiring) are connected according to the fly wires (also known as the pre-pull wires). After the PCB layout and wiring are completed, the components to be used should be summarized, so we will use the BOM table.

5) Assemble PCB and prepare BOM table, which can be directly derived from a schematic diagram.

However, it is important to note that the schematic diagram which parts of the components, which parts of the components should not be on, to do mental well. For small batches or research boards, it is also convenient to use Excel to manage yourself (large companies often need specialized software to manage). For beginners, for the first version, it is not recommended to directly hand over to the assembly factory or welding factory to weld all the materials of the BOM, which is not convenient for troubleshooting. The best way to do this is to prepare your own components according to the BOM. Wait until the board came, step by step on the components, debugging.

6) Debugging problems.

When ready to debug a plate must be serious to do a visual inspection, first to check whether it is visible in the process of welding circuit and pin tin problems, check whether there is a component model error, the first foot placed wrong, leakage problems such as assembly, then use a multimeter to measure the power supply to ground resistance, to check whether there is a short circuit. This is a good habit to avoid damaging the veneer after rashly turning on the power.

In the process of debugging, we should have a peaceful state of mind, and it is very normal to meet problems. What we should do is to do more comparison and analysis, and gradually eliminate the possible causes. We should firmly believe that “everything has a way to solve” and “there must be a reason for the problem” so that we can finally debug successfully.