Reinforced pads for XT60 connector

Hi,

I'd like to create pads to anchor an XT60 connector onto a PCB, and I was hoping someone could give me some pointers.

Here's an example of what I'm talking about:
https://www.dquad.nl/wp-content/uploads/2017/02/Dquad-Obsession-13-copy-2-uai-516x290.jpg

Notice that there are a couple large pads on the right side of that board where the XT60 connector can be soldered to. The pads have holes (plated I'm assuming) in order to create extra strength where the connector is attached, and keep the pads from ripping off the board if the connector is bumped.

What would be the best way to create a pad like this? Would it be a copper area on the top and bottom layers, and a bunch of vias to connect the two together? Or, would it be better to use holes instead?

Thanks in advance for the help!

#PCB#
Circuit Design
How to create a stencil with openings that differ from the pads of the PCB?

For example, the TPS2115A in the DRB package has an exposed thermal pad, and the datasheet recommends that the stencil has a 66% coverage.

Is this what the "TopPasterLayer" and "BottomPasterLayer" are for, and if not, what are these layers for?

Thank you.

#PCB#
Circuit Design
Auto clean-up of traces

Feature Request

Brief title for your desired feature: Auto clean-up of traces when editing

How would you like the feature to work?

Currently, traces are often created as multiple sections. When selecting a trace, only a given section is selected, even though the endpoints are the same. This behavior demonstrates that the traces while connected net-wise, are still separate entities. If they share the same end point, they should be merged when the edit results in such. Since the traces are not the same, when moving the connection point (or via where they connect) only moves the selected on or just the via if it is selected.

What should happen is when connecting a new trace to an existing one is they become the same trace if the end points are the same. Likewise if a via is at the same point, the two traces should be separate, but moving either endpoint or the via should move them all at the same time.

BTW, the same behavior applies to the schematic as well. Sometimes net connections to a pin become one, other times they are separate in that when moving one or the other, only one is moved.

Why is this feature important to you?

EasyEDA implements a novel way of handling connections in the schematic and PCB editor. Most programs maintain an internal entity that governs the behavior of subsequent edits. As a result, if they work it is great, if they have a bug, things get real messy.

In contrast EasyEDA makes the internals match what the user does on the screen. I know I am not explaining it very well, but basically the EasyEDA way works better when it is buggy than do most programs. Unfortunately, it is still buggy. The nice thing is that it appears to still know what it is doing electrically anyway. Therefore, the only thing required is to change the graphical entities to match the already correct electrical entities.

,

#Feature Requests#
Feature Requests
Way to connect different nets in PCB without merging

Feature Request

Brief title for your desired feature: Means to connect two different nets without merging them.

How would you like the feature to work?

A special schematic component which has two pins - one for each net. In the PCB the two nets would need to be connected to satisfy the netlist. Alternatively, allow the user to create a component with a footprint connecting the two nets with copper in the footprint. Currently, when attempting this latter method, the PCB editor flags this component and its connections with several DRC violations.

Why is this feature important to you?

When doing mixed analog/digital circuits, the analog portions often require isolation from the digital portions, but at some time their supply and ground connections must be joined. Requiring both to be the same net in the schematic causes confusion and makes proper PCB layout more difficult.

A second use case is when connecting schematic pages or reusing a schematic module. The net names on one page or module may not match the ones on the other page. There can be a number of reasons to do so, most likely clarity. For example, connecting pins between two ICs - one IC may use one name and the other a different name. When connecting by name which one should be used? Often it would be best to name them differently and then connected them up.

A zero ohm resistor is how many designers accomplish this task. However, that requires another component to be placed during assembly. It would be nice just to be able to do it in the program. If you look at the Eagle schematic and layout for the Arduino Leonardo, you will see they do this magically somehow.

#Feature Requests#
Feature Requests
Simulation is not working

https://easyeda.com/ashah140/temp-0060e7c04d904ed78c2fd969147762f6

My simulation got failed and I have checked all possibilities as per previous posts but could not resolve issue. So please help me to solve one. I put this project on public mode.

Here is the netlist for it.

good* no system model for CSD18532KCS, you can create a model by yourselfUntitled
V2 R5_2 GND 3.3V
V1 C2_1 GND 16V
RSNS C2_1 U1_1 4m
RPWR GND RPWR_2 15.8k
R5 U1_8 R5_2 100k
R4 GND U1_4 4.22k
R3 U1_4 C2_1 47.5k
R2 GND U1_3 8.25k
R1 U1_3 C2_1 47.5k
Q2 Q2_1 U1_1 VOLPROBE1 CSD18532KCS
CTIMER A GND 1u
C2 C2_1 GND 1u
C1 VOLPROBE1 GND 1u
.param pi = 3.141593
.func LIMIT(x, y, z) {min(max(x, min(y, z)), max(z, y))}
.func PWR(x,a) {(MAX(ABS(x), 1e-313))*a}
.func PWRS(x,a) {sgn(x)
PWR(x,a)}
.func stp(x) {u(x)}
.func log10(x) {ln(x)/ln(10)}
.func SQRT(x) {(MAX(x, 1e-313))*0.5}
.func INT(x) {sgn(x)
floor(ABS(x))}
.func URAMP(x) {max(x,0)}
.func POW(x,a)

  • {(((a-(int(a)))==0)||(sgn(x)>=0))( max(exp(ln(uramp(x))a),0) +
  • (2(0.5-ABS((int(a))-2int(a/2))))max(exp(ln(uramp(-1x))*a),0) )}

.control
tran 1u 1m 0

probe V(VOLPROBE1)

quit
.endc

.END

#Simulation#
Circuit Design