Yes this is a consequence of using floating point. The round offs cause small errors. One of the things I hope to make FritzingCheckPart do eventually is round off all the numbers (or at least most of them) to 2 or 3 digits after the decimal which should cure this problem, but I’m not there yet.
Peter
See how you go with this one (pads 1.447mm/0.058in).
Amica_NodeMCU_DevKit_1.0 (v2).fzpz (56.8 KB)
This one works and the NodeMCU amica fit without problems
Rather than start a new post, I thought I’d keep everything in one place and add these parts for recently released updates to the Heltec Dev Boards here.
The CubeCell V2 update is pin-compatible with the original, but I’ve also updated the PCB and Schematic elements of the original part, so they’re both included. The only real difference between the two is some minor changes to the Breadboard view to reflect the presentation of the updated module.
Heltec CubeCell Dev-Board.fzpz (54.0 KB)
EDITED: Please note, this part file has been corrected in line the recommendations offered below in this thread.
Heltec CubeCell Dev-Board V2.fzpz (62.2 KB)
The WiFi LoRa 32 V3 and Wireless Stick Lite V3 parts are based on a new ESP32-S3 processor so, while they each share the same form factor as their respective predecessors, they are not pin compatible with earlier (V1 & V2) versions.
Heltec WiFi LoRa 32 V3.fzpz (58.4 KB)
Heltec Wireless Stick Lite V3.fzpz (59.7 KB)
I ran FritzingCheckPart.py against the files which detects the following error:
$ FritzingCheckPartw.py part.Heltec_CubeCell_Dev-Board.fzp
Error 69: File
‘svg.breadboard.Heltec_CubeCell_Dev-Board_breadboard.svg.bak’
At line 25
Found a drawing element before a layerId (or no layerId)
This will cause the part to not export as an image (svg, jpg, png etc.) to fix it, do an Edit->select all then Object->group (assuming Inkscape!) then name the resulting group “breadboard”
$ FritzingCheckPartw.py part.Heltec_CubeCell_Dev-Board_V2.fzp
only warnings which don’t affect functionality so fine as is.
$ FritzingCheckPartw.py part.Heltec_WiFi_LoRa_32_V3.fzp
Again only warnings which don’t affect functionality so fine as is.
FritzingCheckPartw.py ‘part.Heltec_Wireless_Stick_Lite_V3.fzp’
Again only warnings which don’t affect functionality so fine as is.
Peter
My first reaction was “Gee, I ran FritzingCheckPart on that and it didn’t report any errors…”. Then I looked again at the output and, sure enough, it did! But the strange part is that I didn’t change anything in the breadboard file, so that problem’s been there all along.
Fixing it was slightly more complicated because I use Illustrator, but all should be OK now.
EDITED: Following the recommendation offered by @microMerlin below, I have amended the file available through the link above.
As a matter of interest though, when we rectify a problem like this, are we able to automatically link the new file to the old posting, or disable the old link, or have it point to the updated post automatically?
Thanks.
If you have enough privilege, you can just edit the original post with the bad uploaded part. Delete that link from the post, and upload the new one. Optionally with an “EDITED” note to explain what you did.
Thanks @microMerlin, I believe that I have modified the relevant link and included appropriate comments in the above posts.
Yep, the new file appears fine so all should be well.
Peter
I just wanted to say thank you for making the fritz file for the V3 module. A huge help, I wanted to ask if you could put something else together…https://www.amazon.com/Screw-Terminal-Breakout-Module-BeagleBone/dp/B08LKBKCDY.
I need this for a project and I tried to make it myself not working well any assistance would be appreciated!!
The B08LKBKCDY module looks like a lot of work, certainly for me because I have nothing like that upon which to build. @vanepp might be the man for that job… if he has the capacity…
Thanks for the recommendation @UniquePete! @vanepp if you could please look into this it would be very much appreciated, I am very new to this software and this build would be great for a group of us using these. Thanks again!!
A part will be up in a bit.
Peter
Thank you, I really appreciate it. Let me know if you need any additional details.
OK here is a part that should do what you want. I suppressed pcb as it doesn’t appear useful as this is a shield and it is set that if you stack it on top of a beagleboard black (the Adafruit one I believe) in breadboard it will connect to the shield in schematic (you however may not want that once you see what happens in schematic 
.)
Screw-Terminal-Block-Breakout-Board-Module-for-BeagleBone-Black.fzpz (22.5 KB)
Peter
I really appreciate it, huge help! Looks great!
Once again, I figured this was the best place to keep adding Heltec parts. I have run this one through FritzingCheckPart.py.
Heltec WiFi Kit 32 (V3).fzpz (34.6 KB)
Oh Jesus this is exactly what I needed! Thanks a lot!
Could you explain me where are the inkscape commands to modify the PCB part?
I only found those to modify the schematic and in the XML list I didn’t found any PCB references.
The pcb items are in the pcb svg. There are typically 3 (sometimes 4) svgs in a part, breadboard, schematic and pcb (and optionally icon, often replaced by the breadboard svg) as well as the fzp file (which ties them all together.) In this case unzipping the fzpz file gives this
the pcb svg is svg.pcb.Heltec_WiFi_Kit_32_V3_pcb.svg
which looks like this in Inkscape
Peter
Oh gosh!
I took for granted that Schematic and PCB was all in one file, like in Fritzing…
Thanks, now it’s clear to me why I couldn’t find… what isn’t there
Parts creation takes more than a bit of getting used to. There are also interactions between the fzp file (which is XML and describes or refers to elements in the svgs) and the various svg files as well as rules for layout. It is uncomfortably complex to make parts. I believe there is ongoing development work to finish parts editor (it was incomplete when development stopped in 2016) but that hasn’t been released yet (and is a large part of the reason I don’t use parts editor!) FritzingCheckPart.py helps by checking for and flagging the common errors.
Peter
