Cannot set PCB pad size = hole size (V1.9.1 & V1.11.1)

BUG

Concise problem statement:

In:

https://easyeda.com/bbs_view_966.htm

you suggest that to make an unplated mounting hole:

Why not put a PAD or Via with pad size = hole size?

I just tried to:

i) modify a pad to make pad size = hole size;

ii) create a new PCB lib hole with pad size = hole size.

I could not do it.

The minimum (pad-hole) size alway had to be 10mil.

I tried setting a track size of 0 in case it was the DRC that was preventing me from doing it but that does not work because the DRC does not allow a track width of 0.

What am I doing wrong?

Steps to reproduce bug:

  1. Place default pad (60mil pad, 36mil hole);

  2. Edit hole to 60mil;

  3. Hole stays at 36mil;

  4. Edit hole to 50mil;

  5. Hole increases to 50mil;

  6. Edit hole to 51mil;

  7. Hole stays at 50mil;

Results: see above

Expected results: expect to be able to set hole size = pad size to make unplated hole with no pad.

Url:

Browser: Chrome on W7

#Bug Reports#
Bug Reports
Support file input for .inc, .lib and things like XSPICE State Machine

As you know, I am building the new digital parts library based on XSPICE parts.

Low level gates like 2 ip NAND and JK Flip Flops are no problem.

Higher level functions like 4 bit binary and Decade counters can be built from these low level gates but it would be good (less memory hungry!) if we could use the XSPICE State Machine to build them instead.

http://ngspice.sourceforge.net/docs/ngspice-manual.pdf#subsection.12.4.18

The problem is that each State Machine needs a definition file but I do not think we have a way to upload and read (or write) a user file.

This is also a problem because it means that we can not use things like the File Source:

http://ngspice.sourceforge.net/docs/ngspice-manual.pdf#subsection.12.2.8

and we do not have a nice way to include files for things like user libraries or defining lots of parameters that may be common to many circuits or models.

This makes many of our models much bigger than they need to be because each one has to have all the parameters in.

If the common parameters could be stored in separate files then it would be much easier to change parameters in many models at once.

A good example here is the new logic devices library. The first set of devices are based on CMOS 4000 series logic and all have the same logic family parameters.

To create a new logic family, the family parameters in each model have to be edited. If they were in a separate file that was read (.lib or .inc) by each model then only that one parameter file would need to change to createa new logic family.

#Feature Requests#
Feature Requests
Look out for `µ` in place of `u` in imported LTspice .asc and netlist files.

Schematics and spice netlists created in and imported from LTspice can sometimes contain the µ character in place of the u character to represent micro (i.e. 1e-6).

So for example a current source of 1uA may be shown in the LTspice .asc file or the LTspice netlist as 1µ.

In EasyEDA, ngspice does not understand what µ means and ignores it without warning.

This turns the intended 1uA source into a 1A source!

This sort of error can cause unexpected - and sometimes very hard to diagnose - effects in the circuit when it is run in EasyEDA. A circuit or netlist that is otherwise perfectly capable of running in ngspice will produce silly voltages or currents for no obvious reason and with no errors reported.

Not good unless you like to waste your time going through netlists character by character to try to spot the fault ...

So, if unexpected things happen, it is often worth doing a search of EasyEDA schematic and/or the netlist files (or the original LTspice files: they are all human readable) for the µ character and doing a search and replace with the u character.

If you are the one that generated the LTspice file then another way to spot it is, in LTspice ensure that:

Tools > Control Panel > Netlist Options > Style/Convention > Convert µ to u

is ticked.

If the option is not ticked then a u character entered will be converted to µ.

If the option is ticked then a µ character entered will be converted to u.

Note that this option only works at the time the character is entered. To update any instances already in a schematic then the option must be selected, the schematic closed and then reopened.

#Skill#
Circuit Design