Would You Be Interested in Roadtesting KiCad EDA?

An interesting idea. As someone who chooses ease of use and simplicity I have struggled to convince myself to switch from EasyEDA to KiCad. Maybe this is what I need to see what all the fuss is about and give it proper structured evaluation.

As far as format goes, I would limit the size of the printed circuit board to say no bigger than a raspberry pi or compatible hat because when it comes to design the challenge is using the power of the EDA, and it's design rules checking system, to handle the concentration and routing of traces. No doubt there are other design tools included in the KiCad package that should also prove whether something like KiCad is worth it's street cred.

Similarly you could also place a limit of whether it's a 2 layer board or a 4 layer board. Maybe the road-tester can explore going more complex as an option but if fabrication is required that's usually a higher cost.

As an offer, I think paying for the fabrication of the PCB would be nice. I am sure you have contacts with various vendors who could do this for you.

I wasn’t sure how to vote on this one, perhaps I’m missing the point.  Isn’t “road testing” software essentially producing a tutorial on how to use it?  There are dozens of those already and Shabaz has a popular one on YouTube.  

Maybe an approach would be to look at this in terms of problem resolution - how well does KiCad fit into a set of (open-source) engineering applications, e.g LTSpice for simulation.   Define a complex problem that requires serious thought to layout and board setup, see how well KiCad supports the engineer in “getting there” with an iterative design approach.  Defining a component and its footprint in Kicad is a trivial exercise but board layout for, say, high-frequency, high-speed operation isn’t so how does KiCad support such a scenario and what tools are available to help? 

my preference would be:

• free to submit any design proposal in the road test application, not restricted to analog, microcontroller, hat, power, ...
• a reasonable shopping cart for components
• a pc manufacturer budget/voucher, allowing for several spins of a small board, or a single big board spin
• creative freedom in the design and the format/content of the report

shabaz said:

I'm still working on the RA4M1 symbol, since it's a 100-pin part:

KiPart is ideal for making high-pin-count schematic objects. If you have a list of the pins in datasheet or elsewhere:

 KiCAD lovers, check out KiPart 

Create my first KiCad part with KiPart utility

I presume the objective is to increase the number of people using KiCad, more than trying to increase the complexity of PCBs designed by existing users. Showcasing the learning experience of new users and entry level tutorials would be good for this, and both new users and seasoned veterans could do one or other of these approaches. I also like learn-by-doing methods because they add extra motivation to the exercise, so a real working PCB has more appeal to me. It shouldn't be too complex, as learning the tool is hard enough for a contest. 

PCB fabrication is pretty low cost these days, with some suppliers even offering the first proto order for free. So I don't think the logistical nightmare of element14 supplying board shop vouchers is worth it.

As for supplying multiple spins of fabrication, that would make schedules too long, without adding much value. Everyone knows if you spin it enough times eventually you will get it right. If you have to hack up your prototype a bit to get it to work, that is interesting too, especially if you designed it to be hackable.

Friendly reminder it is spelled “KiCad” and not “KiCAD” …

Ironically EAGLE is spelled with all caps, or it was when CadSoft owned it. 

Hmmm, I just checked and not all of my votes registered .... So I now made sure they did.

   Hell yes!! This is my daily ecad driver.  This is a drawing of my Fire Switch Interconnection 3 fire switches to one DB25, I have modified the plan to use Molex Connectors to the fire switches not the interface. Then I need a 4-pin Molex for Lamp Power and Lamp Ground

Each Fire Switch has 4  SPDT switches  - 1 common 8 contacts, Lamp Power & Ground.

I really only care when the switch is on in which case the switch's NO pins will go to ground.

Ahh.. a RP2040 board would be very neat. Although currently each time I end up using the Pico since it's fairly compact anyway, but it would definitely be a fun project to at least attempt a RP2040 board sometime, and in particular resolve the 1.8V GPIO thing (i.e. allow the GPIO to be 1.8V, which is not possible on the Pico board without a level converter, which isn't easy when you're quickly prototyping and would rather just have it on the board already). A RP2040 with adjustable capability (1.8V and 3.3V) would very useful. Also with a reset button on it, and space for another RP2040 with the PicoProbe!  I can't live without that feature now, ever since Jan Cumps  suggested it for the Pico Eurocard.

Incidentally I'm currently making a Renesas RA4M1 board, because the ready-made one is a bit awkward for some things (particular LCD wiring). So this board will simplify that a bit. I'm still working on the RA4M1 symbol, since it's a 100-pin part:

Gough Lui said:

I still feel that the purpose of an EDA is to build the files necessary to generate a physical item.

I agree with you that getting to that stage would be a part of testing the software. I partly replied to robogary about this here  RE: Would You Be Interested in Roadtesting KiCad EDA? 

Gough Lui said:

Without it, given the software is free, what is the incentive for the RoadTester?

That's why we have the question of what would be expected in a 'kit' for this RoadTest, that would be a part of it.

I've also considered that we would offer discount code(s) for the online store, or we would order a basket value of parts from the online store.

And as mentioned, actually fabricating the PCBs. Then there's also being given the platform to share your opinion about the software and for that to be shared.