Mail Archives: geda-user/2023/05/10/06:33:02
Igor2:
...
> If you are a gschem/lepton user, what could make sch-rnd interesting:
>
> - sch-rnd doesn't depend on guile, python, autotools, glib; smaller
> footprint, easier to compile, less likely to break with major version
> bumps of any of the above deps (e.g. when you upgrade your system)
That is very commendable, appreciated.
> - sch-rnd + pcb-rnd + camv-rnd achieves something gschem/lepton + pcb +
> gerbv never managed: although each component is a separate project, the
> UIs look and work similar. Same UI logic, same mouse bindings, largely the
> same (multi-stroke) keyboard bindings, very similar menus, same config
> file format/conventions.
As a detail, I have problem doing fast zooming in and out with pcb-rnd
since it uses a two keystroke combination, which doesn't work when I do
a lot of zooming. My guess that you can zoom with the mouses scroll
wheel, but for thoose with (old) three button mice, zooming is
troublesome.
I know that you can configure the keystroke combinations, but you are
advertising support for old hw, will there be available alternate configs
for thoose systems ?
> - sch-rnd has support for gtk2 and gtk4 (and for no-gui batch/cli, and to
> some degree for lesstif)
Have there been any progress with the lesstif (or rather motif) hid ?
The last problem was that devuan/debian libXt didn't work out of the
box.
...
> Things that sch-rnd doesn't support yet but will in the foreseeable future
> (in ~12..18 months):
>
> - hierarchic multisheet
Testing with hierarchic design in pcb with help of
https://aspodata.se/git/openhw/bin/get_sub_pcbs.pl
I found out that it works perfectly well doing that with pcb and some
manual interventions. So I can have a leaf sch file, e.g. a ldo+caps,
design that in pcb. In a higher up sch file I call for that ldo
subsheet, and in the corresponding higher up pcb file, I can, with
the help of the script above (which collects all need subpcbs, adj. them
for refdes) so that I can load them in the higher up pcb file.
The problem areas I identified is:
a, in pcb thoose sub pcbs isn't treated as a group, like if I want to
move it after placement unless I do some selections which is prone
to errors.
b, the refdeses tend to be annoyingly long, and you cannot know how long
when designing the subpcb.
c, pcb cannot move a sub pcb to the other side of the board complete
with footprints and tracks and all.
In your design notes there are a passus about shortening the refdes,
also a, should be possible in pcb-rnd.
Any thoughts ?
...
> - simulation backends (ngspice and maybe gnucap); with an option to
> back-annotate data from the simulation to the sheet
Regarding gnucap, Al Davis wants to be able to recreate the sch file
from the vams file. Ideally he wants to be able to go from
qucs - gnucap - lepton/gschem, back and forth. Perhaps if you have a
good idea how to connect and communicate between program, that could
be an alternative to store file format specific things (e.g. a dump
of the sch file) in the vams file.
> - an optional mechanism for managing alternate pin functions of CPUs/MCUs
I have a symbol generator
https://aspodata.se/git/openhw/pdftosym/pintosym.pl
which, with a control file, can pick out different subparts of a mcu.
e.g. in https://aspodata.se/git/openhw/share/gschem/_mcu/
stm32f100lm.inc contains pin defs. for that mcu complete with alt.
functions. So with stm32_analog.inc and the pin def file above, I
can get symbols for just the analogue parts of the mcu, whith the
analogue alt.func. as pinlabels, e.g. stm32f100lm.analogs.LQFP48.sym.
Does your mechanism do something more than that ?
Regards,
/Karl Hammar
- Raw text -