#qi-hardware IRC log for Tuesday, 2016-07-12

DocScrutinizer05whitequark: idea about kicad ERC:18:32
DocScrutinizer05[2016-07-12 Tue 19:42:38] <DocScrutinizer05> wpwrak: (ERC) I guess we could do a proof of concept resp rapid prototyping first approach based on netlists, where for each pin an associated rule (code) gets executed, with a list of properties of all other connected pins as parameter18:32
DocScrutinizer05[2016-07-12 Tue 19:48:33] <DocScrutinizer05> while read property; do case $property in *INPUT* || *SIGNAL-IN*) ;; *) exit $ERROR;; esac; done18:32
DocScrutinizer05[2016-07-12 Tue 19:51:18] <DocScrutinizer05> we could even define impedance matched lines as virtual components with special footprints (one trace) and no component, like this. Property "50OHM"18:32
whitequarkthat sounds like a basic ERC, yes18:35
DocScrutinizer05less basic than what we seem to have in kicad and eagle18:42
whitequarkyou can quite easily do that in eagle with an ULP18:43
DocScrutinizer05seems both only know a fixed limited number of net classes and predefined ultra-naive rules for those18:43
DocScrutinizer05aah yes18:43
DocScrutinizer05alas you can't assign properties to pins in eagle, afaik18:44
DocScrutinizer05best case implicitly, or very explicitly in a coded list of pin names18:44
DocScrutinizer05background: we now (need to) switch from eagle to kicad for Neo90018:45
DocScrutinizer05eagle's ULP are nifty but crippled, in that you can't do *any* modifications to *any* objects18:46
DocScrutinizer05that "exit $path/to/scropt.scp" is an abomination18:47
whitequarkhm, yeah, you can't assign any pin properties18:48
whitequarkand you can't even look within a part with a ULP18:48
whitequarkwell, you can always read XML and do ERC on the XML schematics, right?18:48
DocScrutinizer05this *might* have changed with most recent release18:48
DocScrutinizer05right, that's a nice aspect of 'new' eagle project files: XML format18:49
--- Wed Jul 13 201600:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!