Really useful, nowadays I still use some personal Python / Matlab algorithm to this work.
Propose, if it is not already done: could have a button in each option line to “place” the calculated configuration. The focus change to Eeschema and the cursor will place the configuration with the connection (as happens with the parts).
Other idea: in the log write the maximum and minimum value reached with the resistor-solution and the nominal tolerance selected.
Something like this where it can find optimal resistor values from the e12/e24 series for a voltage divider would be my suggestion for a resistor tool.
Nice tool, this web site.
The “resistances to divide a voltage (to branch a current)” could use the maximum power rate desired to each resistors.
I think, when @janvi is release and tested for us. We could write some “improvement request” at Gitlab group.
The first version of my altium board importer was merged.
Sadly the forum does not support duplicating a post so here the original comment by @JeffYoung that i moved to its own thread as it sparked a discussion.
Does anybody know if the new schematics format being introduced these days also includes cache of used symbols in the same file, or is this yet to be changed?
3D model “preview” flag changed to “show” flag (and persisted in files). See Footprint Properties > 3D Settings.
Did I ever announce sub- and superscript for Eeschema? Use ‘^’ to signal superscript and ‘#’ to signal subscript. (You have to turn processing on in Schematic Setup since I didn’t want existing schematics to be reformatted.)
I’m not sure superscript is really that necessary, but subscript is used a lot by some.
Hmm, ‘_’ is a more common notation for subscript (see LaTeX etc). Is there a reason this wasn’t used/is it too late to change?
Yeah, that was my first choice too. However, since we don’t allow spaces in labels, a lot of schematics already have underscores in them and you’d have to escape all of them with “__”.
I also considered double-underscore for subscript, but it felt really weird for it to be backwards from ~ (overbar) and ~~ (escape for tilda).
How does the # play with the current “feature” of using that spezial character for indicating symbols not to be included in the BOM nor for exporting to pcbnew (power symbols, logos, …).
That’s nice!
Would it be possible to add a feature to reset all 3D-viewer models to visible (as a default option)?
Something added to the 3d-viewer ‘Preferences’ menu (which reset the view statement for SMD, TH and Virtual models)?
Particularly it would be useful to have a menu item to reset all 3d-models view option to visible as a different item from reset default settings, allowing to reset all 3d preview flags of model viewer without touching other parameters (i.e. board colors).
Preferences
— Reset to Default Settings
— Reset Visibility for all 3D models
To answer my own question. Currently the eeschema launched from project manager will save original .sch files (although the file header shows the file format version has been bumped to version 5). If you launch eeschema in stand alone mode you can save and load new .kicad_sch files. And currently they don’t containing the symbols cache.
Hmm… good question. I didn’t know about that one.
I think I’m going to go back to “_” (and fix Find/Replace so that you can escape all of them en masse).
I think of this more as a footprint property than a viewer property. Trouble is the footprint reset will reset it to the library footprint’s settings, rather than to “all visible”.
Conceptually it might better fit into a sibling of Edit > Edit Text and Graphics Properties. If we added Edit > Edit Footprint Properties we could also do bulk changes to locked flags, footprint attributes, and footprint paste and mask settings…
Don’t know how difficult will become the program. If I recall right, the # character must be the first character of the reference in order to make a symbol not exported to the pcb.
And it is not usual to have a reference beginning with an underscore.
NB: the syntax for super/subscript has changed to ^{foo}
and _{foo}
(which allows us to both use more standard characters and to get rid of the checkbox to enable processing).
Here’s an example from one of my schematics:
FR_{-3dB} DC - 960KHz
Slew rate 60^{V}/_{uSec}
A_{OL} 83dB
A_{CL} 26dB
Stability margins 69º, 24dB