I am a high school student and I have a rather important project for someone I know and I would need an opinion on the hardware diagram I made. I think it is quite good, but I would like other opinions if there is a hardware problem.
I'll warn you about something I mentioned in another post today -
I'm not a PC board designer but I've worked in electronics a long-long time and I don't remember EVER seeing a PCB design come-back right the first time. Sometimes it's a design error and sometimes it's a layout error. And sometimes the board can be made to work with "cuts & jumps".
I recently made my 1st computer-designed board. It was small & simple but I still made a couple of mistakes. These were "dumb" layout mistakes, not design-schematic errors. (Version 2 is good.) I tried to make sure it was perfect, I thought I was perfect, and I was hoping it was perfect. But from what I've seen in the companies I've worked for, I wasn't really surprised and I was mentally prepared for the wasted time & cost. But of course I was still disappointed.
...A long time ago before personal computers I made some boards from hand-made artwork. I don't remember if they were "perfect" but they were usable.
Hello! Thank you very much for the answer! What can I say?:)) It's like Russian roulette in this case and I can only hope that maybe it will work, at least partially. Yes, I prototyped it and I hope there are no mistakes in the schematic, because in terms of PCB, a lot of things can come into play and not work well.
I don't see the correct processor for a Nano Every; your board uses the 328P. If it's indeed based on the 328P, you can move your topic to e.g. the Nano section. Instructions can be found e.g. Moving topics yourself
The USB interface looks rather complex with 2 chips.
Check the external capacitor requirements of the voltage regulators
The pin numbering on the ICSP header (Burn-Port) is non-standard
The level shifting TX/RX 3v/5v looks rather elaborate. 5v Tx to 3v Rx needs only a voltage divider resistor pair.
For things like the battery management and the usb interface, it is probably good to look at a schematic for an existing arduino board which incorporates such features and copy them. That leaves you with fewer unknowns to test. In this case, you can then focus on the bluetooth and MPU6500 devices which you could anyway test together just using a standard (3.3v) arduino board. This since it looks like the purpose of the board is simply to integrate an MPU6500 with bluetooth.
Hello! Thanks for the observations! The coil is used to conect a Qi wireless charger, it is a wearables device. My concern is with the MPU6500. The battery management is an open-source tested schematic, so it wouldn't be a problem i think, but i am not so sure with the MPU :))
Thank you!
If you want to start testing with an MPU6500 and bluetooth, maybe start with an ESP32 board, which is anyway 3.3 volt and has bluetooth, for a proof of concept. Get the software right then start thinking about the final platform to run it on which may be more suitable for a wearable device.
Incidentally, the 3 volt supply to the HM-10 bluetooth module does not look very effective in your schematic.
My process is:
Research
Brainstorm
Research some more
Draw schematics of individual parts of project
Set up on breadboard
Tweek
When a part works move on to other part
Connect parts and tweek/test
When all is working as intended design pcb
Get pcb and then test why it doesn’t work
Tweek and modify
Move to version 2
Do you have an oscilloscope? Very handy for tracing issues with logic, particularly I2c etc. also will let you discover noise and interference issues and correct with capacitors etc. I had some problems with traces affecting the I2c signal.