During my internship, my task is to manufacture USB devices. This includes everything from design to testing.
In my college class, I am familiar with several different microcontrollers, so I chose my favorite microcontroller and did more research. I have studied similar microcontrollers that can be incorporated into USB, but not everyone can. After that, I used the data sheet provided by the manufacturer to understand how to program the equipment. Then, I created a schematic diagram according to the pin arrangement of the microcontroller and other components that need to make the circuit work normally. I showed the schematic diagram to my manager, and he laughed and laughed. He told me that it was a good schematic diagram, but they didn't teach me all the knowledge applicable to this industry. He gave me some instructions, most of which were integrated capacitors to ensure the integrity of the signal, and then I started working again.
After completing the schematic diagram and getting the manager's approval, I began to make PCB with software. This design has been confirmed by another manager and then sent to production.
My design used about 80 parts, all of which were welded by hand with a microscope. After studying hard, the boss showed me the pick-and-place machine. It is fascinating to watch the circuits come together in record time. I spent about 10 hour soldering PCB. It took about 45 seconds to assemble this machine.
Then, I learned about all kinds of welding, wave welding, reflow welding, manual welding, spot welding and so on. These parts were refluxed, and in less than 10 minutes, my circuit changed from parts and plastics to complete sets of equipment. excellent
After the assembly is completed, it is time to program the firmware of the microcontroller. This is by far the hardest and longest part. It took more than a month to ensure normal work. Many manufacturers call and provide firmware samples.
After I think it can work normally, it's time to test. I must put forward a test protocol, which not only proves that the equipment works normally, but also proves that it will not be damaged by faults or errors.
After that, I must create a data manual for my own circuit and write user instructions.
I had a great internship experience, which inspired me a lot.
My day in EE is full of learning and growth in the company. A typical day is trying to determine the next step of firmware and how to program the device to make it run normally without being damaged. It took weeks to figure it out. This is a bunch of solutions to the problem. I helped, but my help made them try their best to let me solve the problem by myself. I'm glad they did.
It involves advanced mathematics, design and design company policies.
EE A typical day in life includes many different tasks, none of which is trivial at first.
Now, in my current position, I will test the code of proprietary projects. It's hard, it involves more planning and writing than the actual test, but it's part of the job. I'm getting better and better at this, but such little things are rare.
As a typical EE day, you stay alert and completely immersed in your work. Different jobs will do different things, but your education will come in handy. Almost every engineer will be smarter than you, so don't be afraid to answer "I don't know" when asking questions. Your career is based on continuous learning and growth. So, as an EE, please study hard and grow.