Would You Be Interested in Roadtesting KiCad EDA?

I've used KiCad for 18 months now, and enjoy it. For sure some bits of it are clunky compared to EAGLE which I used for many years, but I have no intention to go back to EAGLE, since the positives of KiCad now outweigh (for me) the positives of EAGLE). KiCad is also miles better than CircuitStudio, which looks exactly like a cut-down version Protel DXP, which was quite a stinky product.

Just throwing out some more ideas, in case any of these sound interesting:

* RoadTest with an enclosure, with each RoadTester getting a different enclosure.
It could be handy for the output to include PCB layouts that fit the enclosures, since that saves others from having to do that if they wish to use the same enclosure for a different project. Bonus points if the project includes a PCB front panel layout too.

* Build an add-on, or Build a dev-board
This is just extending the Raspberry Pi HAT idea, perhaps to allow the RoadTesters to choose Pi or Pico. The add-on could be a HAT, or perhaps build an add-on or dev-board for the Pi Pico. This might also help in case Raspberry Pi availability is low at the time of the RoadTest.

* Build-from-a-Book
RoadTesters could receive either "The Art of Electronics" or "ARRL Handbook 100" (the Roadtester's choice, since some may already have AoE) and the challenge would be to design a PCB for a circuit either directly from the book, or inspired by the book.

I've used KiCad for 18 months now, and enjoy it. For sure some bits of it are clunky compared to EAGLE which I used for many years, but I have no intention to go back to EAGLE, since the positives of KiCad now outweigh (for me) the positives of EAGLE). KiCad is also miles better than CircuitStudio, which looks exactly like a cut-down version Protel DXP, which was quite a stinky product.

Just throwing out some more ideas, in case any of these sound interesting:

* RoadTest with an enclosure, with each RoadTester getting a different enclosure.
It could be handy for the output to include PCB layouts that fit the enclosures, since that saves others from having to do that if they wish to use the same enclosure for a different project. Bonus points if the project includes a PCB front panel layout too.

* Build an add-on, or Build a dev-board
This is just extending the Raspberry Pi HAT idea, perhaps to allow the RoadTesters to choose Pi or Pico. The add-on could be a HAT, or perhaps build an add-on or dev-board for the Pi Pico. This might also help in case Raspberry Pi availability is low at the time of the RoadTest.

* Build-from-a-Book
RoadTesters could receive either "The Art of Electronics" or "ARRL Handbook 100" (the Roadtester's choice, since some may already have AoE) and the challenge would be to design a PCB for a circuit either directly from the book, or inspired by the book.

shabaz said:

* Build an add-on, or Build a dev-board
This is just extending the Raspberry Pi HAT idea, perhaps to allow the RoadTesters to choose Pi or Pico. The add-on could be a HAT, or perhaps build an add-on or dev-board for the Pi Pico. This might also help in case Raspberry Pi availability is low at the time of the RoadTest.

RP2040 breakout board is also something I'd find interesting, or "<microcontroller> breakout board" a lot of 'dev kits' certainly don't give you access to everything.

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:

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

That looks very good! I'll try that out on my next component symbol with a reasonable amount of pins.

Friggin amazing JC!

Can I safely assume it will work with the latest version of KiCad?

I was going to going to ask what operating system it is supported in but realize a pip load makes it O/S independent. YES!

Hi Jan Cumps  I tried KiPart, and followed your KiPart video - it was just what I needed.

I managed to do this 64-pin chip in a fraction of the normal time! I specified in the CSV file which side I wished everything to be, and it's all perfect. I will move some of the left side pins around because I had not figured out the order at the time, but all other sides are exactly how I planned them to be.

see  shabaz' work