pcb-rnd knowledge pool

 

Our new EDA suite

suite by Tibor 'Igor2' Palinkas on 2018-01-01

Tags: insight, ecosystem, suite, eda, project, management, strategy

node source

 

 

Abstract: pcb-rnd is a PCB layout editor tool. When it started in 2013, I didn't foresee it would be the flagship of an EDA suite, which will be part of an EDA ecosystem. This node describes the relation between these terms.

  From inside out: pcb-rnd is a layout editor software. It is part of a (yet unnamed) suite, among with cschem, edakrill, etc. The suite is part of the EDA ecosystem effort , which in turn has two rings.

It's probably easier to understand it looking at the following diagram:

stackup of terms ecosystem, suite and pcb-rnd

The rings are, from outside to in:

The main difficult part is to see the difference between the Suite and the ecosystem. The key is realizing how tightly coupled the goals are:

On the other hand, the ecosystem contains tools from various sources, developed by different people (with small or no overlap with our developers). Development goals and styles are rarely the same. But at the end, tools within the same ecosystem have some practical connection for the end user.

The following drawing shows the relations between pcb-rnd, the suite and the rest of the ecosystem (without dividing the ecosystem into two rings this time):

connections between the suite tools and ecosystem tools
legend for the suite

Thus the connection between ecosystem tools are much weaker then the connection between the tools within the same suite. The ecosystem model is further divided into two rings, depending on whether the participant is willing to join the ecosystem (tight ring) or just lured in (loose ring). Paths to and from loose ring tools are more likely to break as developers of those tools won't consider ecosystem aspects.

Please note: being free software is orthogonal to this splitup. For example gEDA/pcb or lepton EDA are both free software, but they are in the loose ring becuse they don't do anything for interoperability within this ecosystem. On the other hand, there's no actual example yet, but there might be a proprietary software or service that decides to use the tEDAx file format, which effectively makes it part of the tight ecosystem.

Members of our suite

project state purpose
pcb-rnd stable printed circuit board editing
edakrill stable "cloud" - web based user data lib (footprints, symbols, etc.)
tEDAx stable Trivial EDA eXchange - cheap-to-implement file formats for interoperability
genxproj alpha generic project manager
cschem planned schematics editor
camv-rnd alpha PCB CAM file viewer
(gerber, excellon, etc.)