Hi,
I have been designing a PCB which includes an ESP32 module.
I am now looking at integrating a bypass capacitor for the board. The board will be powered from a 7V input terminal which will pass to a 5V switch-mode voltage regulator. The output of the 5V regulator will be passed into a 5V plane.
The ground of the regulator will pass into a GND plane.
For the life of me I can't work out how to integrate a bypass capacitor without suffering from DRC errors. The problem is that I have my DC input on it's own nets, but when I wire them into the regulator with the GND and output pins tied into the 5V and GND nets, I get the DRC errors. I have yet to find any explanation of how to design the PCB inside easyeda to avoid these DRC errors.
Can someone point me to a sample project which explains how to tie to different net's together, or how I should include a bypass capacitor which ties to a GND plane?
I have the same problem with a de-coupling capacitor which I will apply to an ESP32 module, but I am fairly sure once I can include the bypass capacitor the same theory would apply to the de-coupling capacitor
I have made the project public while getting support
https://easyeda.com/angus_grant/ESP32_BCDeviceSupport
This is my first full PDB design, and I had problems understanding how to design the schematic correctly, so there is only a PCB design in my project. Feel free to provide any further feedback on other component design
My board includes a 3rd party ESP32 development board, and includes the option for reading temps from PT100/PT1000 RTD or a DS18B20 one-wire temp probes. It will then feed out a 5V signal through a relay module to an external high-powered relay to control a chilling system.
Thanks,
Angus.
I'm having some trouble with a simple schematic that I made. I'm getting a host of incomplete nets and I'm not sure why. About a week ago this was working perfectly but something has changed and I'm not sure what. For the ground it's saying that the netlabel is not connected with any pin which I find confusing because it does seem to be connected. Also, just nothing seems to be connected like it should. Can anyone give me an explanation? Even when I start over from scratch I'm getting the same errors, especially with my 3PDT switch. Thanks!
https://easyeda.com/canarywood/2019-12-27-dallas-rangemaster
#Schematic#I can't seem to figure out what I'm doing wrong. I've enclosed my board with a Copper Area, but it's not filling. The PCB outline appears to be closed and I've redrawn it and used the Set Board Outline tool to draw an outline. I don't have any DRC errors nor do I have any net errors. Copper Zone is set to visible. The Net is set to GND. I've tried modifying various properties of the copper area including clearance, pad connection, keep island, fill style, and improve fabrication, but nothing seems to have any affect. What am I doing wrong? Thanks in advance.
Here's a link to the project:
https://easyeda.com/davron12/ESP-RS485-Adapter_copy
I tried running this simulation:
https://easyeda.com/editor#mode=sim,id=1b5570af67cd4649ab524a89757e69f5
but it would not run.
There were no errors or warnings and it will not generate an LTspice netlist.
Just nothing happens.
I have tried replacing the switch, the pot, the two Jfets, the NPN and PNP transistors with parts from the EELib but the only way I can get it to run is if I delete all of those parts so that only the voltage sources and the Rs and Cs are left.
I have tried running several other sims that I have corrected for LTspice compatibility and that I know would run because they were successfully tested before V6.3.22.
Basically anything that has anything other than V and I sources and RLC components in it does nothing.
- The change appears to have occurred between V6.2.46 and V6.3.22 because I was trying to fix the problem described in this post:
where the sim was failing with errors when it was run with V6.2.46 but was at least trying to run and was generating error reports but not it does nothing.
#Bug Reports#Introduction
Believe that the vast number of electronic engineers will encounter the problem of package/footprint name naming, and now EasyEDA to provide everyone with a reference scheme - "EasyEDA Footprint Naming Rule Reference".
Each company should have its own package/footprint naming specification,EasyEDA is no exception, EasyEDA has more than 180,000 of official library (LCSC library), multiple engineers in the construction of package/footprint, more need unified library rules and package/footprint naming rules to ensure library consistency and package/footprint/PCBlib reuse.
Written by LCSC engineering department and EasyEDA team, after close one year of running in, now we are very happy to release the "EasyEDA Footprint Naming Rule Reference".
EasyEDA has been established according to the new package naming specification PCBlibs for more than half a year, and EasyEDA will continue to draw new library according to this rule.
The majority of EasyEDA users can also according to this rule:
1. Find the components of the specified package type;
2. Create your own or team's or company's package according to this rule;
3. Quickly reuse the official PCBlib/package/footprint.
Characteristics:
1. The rules of "package type _ feet number - body width - foot distance - body length - foot azimuth - polarity direction _ series name" are adopted in naming\, so that users can quickly and clearly package most of the information
2. It covers most common component classification and encapsulation types and can quickly locate and query
3. Continuously expand new naming rules according to new components or packaging types\, and continuously update and maintain
4. Public distribution\, free of charge for both individuals and enterprises
Disadvantages:
Titles of some package types are too long
Preview:


Update record:
2019.12.27 First release
Download:
EasyEDA Footprint Naming Rule Reference.pdf
Notice:
It is translated from Chinese to English by web translator, that may some incorrect grammars, if you find out, please let us know.
Thanks
EasyEDA Team
#Skill#







