Skip to content

Add Raspberry Pi Pico, Pico H, Pico W, and Pico WH

Add Raspberry Pi Pico and Pico W from Ki-Lime Pi Pico 2.0.0

Datasheets:
https://datasheets.raspberrypi.com/pico/pico-datasheet.pdf
https://datasheets.raspberrypi.com/picow/pico-w-datasheet.pdf

Source repository: https://gitlab.com/recursivenomad/ki-lime-pi-pico

GIF of Ki-Lime Pi Pico models

These are all the models I've made for this library

The KLC model check passed with 6 "unused" wrl files, but they're really just alternates for rendering.

Okay, so...

Model review should hopefully be easier to digest than the many permutations of symbols and footprints that are joining this merge request 🙂

My primary question comes down to model redundancy. To align with the KLC, I uploaded the same model multiple times, with the only change being vertical offsets for headers/sockets. Is it worth considering only uploading one of each variant (Pico, Pico H, Pico W, Pico WH), and then letting the user set their height manually? I absolutely recognize the convenience of simply toggling off the SMD version and toggling on the THT version; but it feels wasteful to include the same geometry across multiple files.

The other question I have is regarding the STEP format. I am excited to see that a new STEP exporter is on its way in 9.0. Currently, the STEP models I included in this merge request are FreeCAD "Compounds", as this allows them to be exported with their full colours. The downside of this is that hierarchy information like component naming and positions is lost in the Compound process. I have the fully-featured STEP files as well, and I can swap them in if that would be preferred, but I worry about exporting colourless models as a result. Food for thought.

If you're interested, you can check out the FreeCAD source file here (warning: it is built extremely parametrically, and also extremely inefficiently!)

Looking forward to working on this contribution with you all!

Edited by recursivenomad

Merge request reports