Consider female header pins.
Something like this, depending on you’re needs.
This way the pico is removable if edits are required.
Not the only way, but a way.
As Jonny mentioned header pins are your best bet, if you like we can get the 2x20 header pins used on PiicoDev expansion boards on the website, having 2 rows next to each other really keeps things clean.
What do you mean by this? Have you destroyed the LiPo charging IC?
No, nothing destroyed, but given the existing LiPo charger is built into the platform module, I’m expecting I will to replace this on my custom PCB with something else.
@Pixmusix Yeah sure… I think I will be using a full 40-pin socket, my query really is… how to cater for “Dang, I forgot something”, so basically making provision for patching some wires to the PCB rather than soldering directly onto the Pico.
I haven’t done tbhis bit before (ie making a PCB for a micro) but it seemed to be prudent to plan ahead!. Worst case I guess I could just solder on a second header next to the one holding the Pico… but, no, scratch that idea… I really don’t want Dupont wires anywhere on this! A row of vacant holes connected to the header? As you can tell, I’m just making this up as I go along!
Are you going to make a PCB using mainly modules or SMT IC’s?
The same IC as used on the PiicoDev Expansion boards are available from Makerverse (LiPo USB-C).
Another tid-bit of advice, use test-points and open solder jumpers if you are commissioning a design, having parts of a circuit ‘opt in’ allows for connections to breadboards to debug.
The way I have approached a build is to prototype, prototype, prototype until I am absolutely in love with my design. Then I go for a soldered solution.
If I was really keen to try to leave myself some opportunity for adding later I would leave an i2c port exposed. There isn’t a peripheral on earth that some guy with two much time on his hands hasn’t made an i2c breakout for; a little bit of re-programming and you’ll be able to append a last minute addition.
Dang…just discovered the KiCAD symbols for Pico/Pico2W are RUBBISH! Researched it last night, the “best” resource I found was a git repo called ki-lime-pi-to-go, but there also the pin placements and assignments are so wrong it is not funny.
Does anyone have a reference to a correct KiCAD symbol? Otherwise it looks like making it myself… which seems truly bizzare for such a widely used device!
@Liam120347 SMT is a hurdle still be crossed! I’ll just be using THT stuff. AS per last post I am now stuck for lack of a correct KiCAD symbol for a Pico…
I have not looked but be aware that the PC board through hole footprints are the copper side viewed from the top (component side) looking through the board. This might look a bit strange but it is when printed the actual printing contacts the board when photo exposed for etching. Prevents the transparency material thickness causing parallax errors in the exposure process.
This should not affect the schematic symbol however. If this is what you are referring to I agree, it is time a correct symbol is available.
I think I figured something out… it may not be as bad as I thought. The schematic looks all wrong… but the pin assignments may still be correct, so the circuit diagram won’t really reflect the physical layout of pins on the device… but I can live with that. As long as the PCB “gets it right”, hey?
On another topic… I have used your recommended LMC6482 opamp… and am planning on using it in another audio circuit … nothing Core-related. Was wondering if we could have an offline chat about that? If you are up for it I’ll send my contact details…
@Robert93820 Hi Bob… firstly, Ryan advised I just start a new topic re the other project, which is an audio signal tracer amp thing… so I’ll try that first.
Second… I’m approaching readiness to get a PCB made for my main Pico tank monitoring widget… on which I have placed a quad LMC6484, giving me the option of adding something later using the two as-yet unused units. Currently, my schematic has the unused inputs going to GND - but that sort of defeats the purpose! I am planning on adding some jumpers or whatever on the IN+, IN- connections so I can connect future sensors as and when required - or leave them grounded if usused… which leaves the output pins open… unless I hard-wire them to the unused ADC ports on the Pico.
This won’t matter. The outputs are push pull and low impedance. It is the high (10TΩ) impedance inputs which will cause some bother if left floating. Grounding these will prevent any potential trouble and will not affect the operation of used inputs.
If that is what you wanted to discuss off Forum that is fine.
For some reason the private messaging facility seems to have disappeared. Don’t know why. Makes it a bit difficult as Core frown on private contact details being posted (quite rightly) and are likely to remove it anyway I think.
Cheers Bob
@Robert93820 … Bob, I’ve just posted a new thread, title “Audio signal tracer circuit”… hoping you can offfer me sage advice.
Removing the PM function is a pity… when I inquired last week about contacting you, Core Customer Service suggested I provide my contact details in this forum, which I was reluctant to do. Anyway… the other thread in this forum will suffice, I hope.
