KiCad

@sundberg84 thank you again. I'll do like you say :)

For a very long time I’m looking for an application where the NRF24L01 + will be, but I can’t find it. So if someone tells me I will be grateful.

@hek it's a python script that can be runned standalone from the terminal. By the way it's the only way I could make it work on my system. Apparently some linux versions of KiCad 5 are build without scripting support, so it crashes with segfault when this script is present in kicad's plugin folder. But as a command line script it needs only *.kicad_pcb file as an argument to work.

@ericperonnin thanks a lot for the videos, I've just started with KiCad (with PCB design generally speaking) and starting from your tutorial has been an excellent way to get up to speed in a short time!

Hi, I'm still rather new at this myself, but here are a few questions/remarks: How did you label your connections? I would think you need "global labels" which are surrounded by an arrow like shape in KiCad. Yours look like regular text. Why add +5V and +3.3V labels to your power inputs? They are globally accessible without additional labeling. AMS1117-3.3v datasheet mentions a single tantalum capacitor of 22uF on output only. I'm unsure why you put the other capacitors on those regulators. I used the same regulator and went by the discussion here. You should run the annotation tool and electronic rules check. It will probably complain about the power not being driven. You can solve this by connecting the input power and ground with the PWR_FLAG power symbol. You should mark the unused connections on the MCU with "no connect" cross mark. I hope this helps.

Answer to myself: There is one from Sparkfun.

@mtiutiu For me, D doesn't do anything at all. m acts as set in the dialog.

FTDI pins are not on the footprint because they are typically used for a connector on the arduino module itself. And having them included in the footprint would unnecessarily complicate routing as it would more or less box in the routs underneath the module.

Spacing out is done by all, glad it was such a simple "fix" :)

@mfalkvidd Thx, this definitly saves some Google time. ;)

@dbemowsk Welcome to the wonderful land of kicad :) As already mentioned, we have a kicad parts library on git hub, which we use for the mysensors components. There are setup instructions as well, so you can get started. I think we already have a nano in our repository (I'm not near my computer at the moment so can't check).

@Mateusz-Pięta I use PCB Stackup to generate SVGs from the gerber files. The svgs get converted (on the fly) to rasterised images in the browser. I build a model in three.js where I "punch out"/drill holes in the 3d model based on the transparent areas of the rasterised image. I was surprised of the result myself. Here's a gist with the relevant javascript for creating the 3d-object from front/back svgs: https://gist.github.com/henrikekblad/292349f928fe67ff574cb975fdaa7488

@emc2 I updated the footprint on github (and yes, I also chose the easy route, and swapped pins 1 and 2 on the footprint) :)