Yep, that should do the job. hopefully at some point we will get to being able to fix code upload, but I have been saying that for 2+ years now .
Peter
Yep, that should do the job. hopefully at some point we will get to being able to fix code upload, but I have been saying that for 2+ years now .
Peter
Hallo
I am new and beginn to work with Fritzing.
I am searching for th part of the MMA845X like this:
Does anyone know where I can get this file ?
Thank you very much
A google search for “fritzing part GY-45 MMA8452” turns up several part references. On is in the adafruit library, another looks to be in core parts (I not currently on a machine with fritziing loaded so I can’t check). A search in the parts bin (the magnifying glass) for MMA8452 or perhaps MMA8451 may turn up a part. The adafruit library is not loaded by default so you have to load it (either the individual part or the whole library).
Peter
Thanks for reply.
I don’t have any output because I don’t know how to use “eagletofritzing”.
Yes, now I noticed… But I didn’t give much attention to the schem terminal points…
But, pin number is very important…
I’ve 30+ parts to submit, lots of them are provided by fritzing with wrong pitch of BB & PCB pins (or maybe different variant), that I had to edit… Hope that will help someone…
Now, I’ve to re-check them before submit…
Thanks…
OK, I’ll make a part in a bit (I have a few other things in queue before it).
Peter
You may want to run them through my part checking script available here:
which will happily complain about lots of things (and I am working on making it complain about even more ). As well, if you want to modify parts in core submitting here is no longer sufficient. The only way updates to core are being accepted now is by making a pull request on the parts repository on github. Long term (after getting development working) I hope to go through and clean up all the parts in core. Many of them as you note are wrong. All help doing so is appreciated.
Peter
OK below is how I would make the part if someone had asked for it. Please use it as a base (if you don’t like some of the changes I made) as it is internally a better part. Changes to breadboard are: I converted the names to be the same as the picture of the pcb on the web site so they match the physical board (you may want to change them back if there is a reason they were different in your part). I changed all the pins from female to male except the ioref pins. Male is the normal connector type in breadboard and will automatically connect to the breadboard if placed on top of it. The 3 ioref pins however would short if inserted in a breadboard, so they are set female so they will not automatically connect, you need to attach a wire to them to get a connection. Icon: I changed to the standard copy of the breadboard file, but I see that your original had a custom logo file instead, just copy the original icon file in to the icon file in the fzpz file if you would like to keep the original icon. Schematic has changed substantially. I favor a schematic which matches the layout of breadboard and pcb as it makes debugging easier so I changed to that format. As well space in schematic is at a premium so I reduced the size of the part as small as it would go given the text on the pins. I also added the ioref pins (as being easier than supressing the pins). I also shortened the pins a bit. PCB got worked over as well. I added the 3 ioref connectors because if someone wants to mount the board on a larger PCB (which is done with UNOs) the ioref pins will be hidden. I changed the pad sizes to be the standard 20thou width and 0.038 hole suitable for .1 header connectors. I removed all the printing and changed the outline path to have no fill because the Fritznig gerber processing was giving a solid color for silkscreen with no connector outline of mounting hole circles. I also corrected the bus definitions so the the grounds, 3.3V and 5V pins are bused. If you click on a bused pin in any view it and all the other members of the bus will light up yellow. If there are any other shared pins they should be bused as well, but I didn’t see any.
HiFive1_improved.fzpz (48.6 KB)
Peter
Thank you sir.You are so kind to me.Thanks a lot.
Hi Peter,
WOW, it was really fast! Will check your version shortly.
Meanwhile, I also did some progress with the part addressing the issues you pointed in the first place and some of the fixes you mentioned in your last post including the addition of new buses. Yesterday, I submitted a pull request with the fixed version of the part into fritzing-parts GitHub (pull request #167).
Once you get over the learning curve (which is fairly steep) , parts creation is fairly easy. That is why I tend to make parts for folks that ask, its easy for me, but not necessarily for them.
Peter
Hi Peter,
Some comments after reviewing the HiFive1_improved.fzpz part:
I am wondering why one would like to do this in Fritzing if it cannot be done with a real board?
The intention is to stick to the Arduino UNO Rev3 part style as much as possible in terms of look and feel. This was the reason for deriving this part from the Arduino UNO Rev3 part.
The UNO uses female pins and it works great for people currently using it. Our board is very similar in design and so we want to build our part as close as possible to their general design.
I used the breadboard image in the first drafts but finally prefered the SiFive’s logo to mimic the Arduino UNO board icon style.
In the schematics component, the multiple physical pins like GND, VDD and similar are usually represented by a single “logical” connection. This also reduces the number of connection points of the component (in our case by 7) allowing shrinking its size even more. For example, having several 3.3V connections to the component in the schematics view could be misleading making one think that these connections were separated intentionally since perhaps are originated from different power sources with different current capabilities… For this reason, I think it would be better to stick to the Arduino UNO schematics view layout.
Yes, I did it as well in the pull request. (the site does not allow to post a link to the pull request, sorry).
Sure, there are additional buses - SCL, SDA, IOREF as can be seen in the fzp file in the pull request.
I think we should continue this collaboration on the Fritzing parts GitHub.
Michael
thanks - i will tested.
regards Jan
This is a Project made with Fritzing, Arduino&Teensyduino. named Venti POV 80HD.
Completed in summer 2018. Thanks for all the help from Fritzing community and PJRC community
Defined to used in Flow arts, poi or staff spinning, and drawing pictures by Persistence Of Vision (POV)
a 3-part board with a Teensy holder, a touch pad cap, and 2 sides of apa102 LED strips(hard PCB style)
Hardware starring: Fritzing designed PCB boards, Teensy 3.6 development board, Apa102 I.A. RGB LEDs.
I’m no professional and very-unnoticed about any rules in schematics,
I use pads and holes like whatever I like, not sure but they did work.
so if you see any unreasonable design in your sight,
please reply so I can understand and fix them
for more details about the project see PJRC forum for reference :
https://forum.pjrc.com/threads/53088-Venti-POV-v2-0-80HD
Also the three maded board in the same file :
80HD_2018board.fzz (265.8 KB)
Please focus in the PCB view, I made no effort in other views.
circle: touch pin extended to reach user easily, and worked nice
USB slot was done by many holes, another slot is for a DC1.3mm plug so I can charge the battery thru.
I use thin wires to separate ground-fill to some shape intended. (this takes long time on ground-filling if your shape was complicated. )
80 apa102 LED strips: 80HD means 80 leds in a High Density of 4LEDs / Cm. Some hard time wiring and soldering. The back of the board is extra pads for extra possible places for battery connections. Carefully connected to ground, but not MOS-drain, so apa102 was not powered without T3.6’s pulling.
The N-mos drain is connected all the way pass the board so every LED gets the same resistance from wiring, and shows same brightness.
holder: with a MOS controller,battery level divider resistors and capacitors for Lithium battery.
I didn’t use all the pins from Teensy 3.6 so not all the pins are placed and soldered. (I’m so lazy)
Also it was better focused with less pins laid.
Hello, I’ve created 35 parts. Lots of them are provided by fritzing with wrong pitch (or maybe different variant), that I had to edit… Hope that will help someone…
Maybe, Most of them are already created, I did not found.
Maybe, most of them you can find also wrong, but I created them comparing with my parts that I work with.
I’m very lazy person. So, BB view of the new parts maybe look dull to you, but I worked till my self-satisfaction.
Please, check the description in the image before use.
I also provided actual picture of some parts…
If there is any error, problem, mistake… Please Let Me Know…
01. Transformer 1.fzpz (5.7 KB) (Ferrit Core * )
02. Transformer 2.fzpz (5.9 KB) (Ferrit Core * )
03. Battery Holder.fzpz (7.4 KB)
04. 78Lxx (TO-92).fzpz (6.6 KB)
05. TL431-1 (TO-92).fzpz (6.3 KB) (Shunt Regulator)
06. TL431-2a (TO-92).fzpz (6.4 KB)
07. TL431-2b (TO-92).fzpz (6.4 KB)
08. KA2281.fzpz (6.7 KB) (or TA7666P)
09. Trimpot - 5mm.fzpz (8.9 KB)
10. Button - 5mm.fzpz (6.1 KB)
11. Pro-Mini - MU.fzpz (19.4 KB)
12. LM 358 - min.fzpz (10.4 KB) (Single ** )
13. LM 393 - min.fzpz (7.6 KB) (Single ** )
14. USB Micro b.fzpz (7.1 KB) (ID pin)
15. Audio Jack 3.5mm S1.fzpz (7.1 KB)
16. Audio Jack 3.5mm S2.fzpz (8.1 KB) (Screw)
17. Audio Jack 3.5mm M1.fzpz (7.2 KB)
18. Audio Jack 3.5mm M2.fzpz (8.3 KB) (Screw)
19. ICL7107.fzpz (9.7 KB) (3.5 Digit A/D Converters)
20. PCF8563.fzpz (6.2 KB) (RTC)
21. Relay.fzpz (12.4 KB)
22. NPN-BCE (TO-92).fzpz (5.3 KB)
23. PNP-BCE (TO-92).fzpz (5.3 KB)
24. Terminal S Green 2.fzpz (5.2 KB)
25. Terminal S Green 3.fzpz (5.5 KB)
26. Terminal M Black 2.fzpz (5.3 KB)
27. Terminal M Red 2.fzpz (5.4 KB)
28. Terminal M Green 2.fzpz (5.2 KB)
29. Terminal M Green 3.fzpz (5.5 KB)
30. Terminal L Green 2.fzpz (5.4 KB)
31. Terminal H Green 2.fzpz (5.3 KB)
32. DPDT Sw 8-508.fzpz (5.3 KB) (8mmx8mm, 5.08mm Pin column pitch)
33. DPDT Sw 8-550.fzpz (5.3 KB) (8mmx8mm, 5.5mm Pin column pitch)
34. DPDT Sw 10-508.fzpz (5.3 KB) (10mmx10mm, 5.08mm Pin column pitch)
35. DPDT Sw 400.fzpz (6.0 KB) (6mm Pin column pitch, 4mm row pitch)
Please Like and reply if any of these helps you…
Thank You…
Hello, I’m trie to find in the forum, but unsuccessfully.
Someone have this conector?
Need the 4 pin, 2pin, 3pin, 5pin.
I’m new to PCB and electrical. I know only the very basics.
While it is unclear from the picture what the pin spacing is (.1, 2mm etc.) typing jst in to the parts bin search bar turns up a number of items. If that doesn’t do a google search for “fritzing part jst” turns up more in other places. There appears to be some in the adafruit library on github (which isn’t loaded in to fritzing by default, you need to download and install it).
Peter
You likely need to move the boards to one board per file. DRC (design rules check) fails because of more than one board. Visually it looks like some of the spacing is too close but DRC would verify that (if it worked …)
Peter
While I wasn’t here in the early days of fritzing, I think the idea is that it does match the real world. When you push a part in to the breadboard it connects in the real world, you can’t push in Fritzing so this does the same thing. The reason for female pins is that when you have a perpendicular row of pins, if the autoconnect rule applies the pins will short (because of the breadboard strip connecting vertically) which is unexpected by new users. If you wish to leave the pins female it is not a big deal (your part, your rules ) either way will work. It is just more common to use male pins and only use female when there is a reason to.
Again no big deal, just copy your original icon file across (or leave it alone if it is already there) .
Again this is more a style issue, both ways are in use. I prefer to have all the pins in breadboard or pcb represented in schematic so the three views are identical, but there are lots of parts that do it the other way. Using the original schematic is fine if you wish.
You should be able to just copy the github url in to the message like this one from my parts check repo:
or am I missing something (github still confuses me most of the time ).
This is a case where Fritzing terms are unfortunate. In Fritzing a bus is a collection of pins that connect together internally, where as in most EDA packages it is a group of pins (such as a data bus) that are treated as one. So what I meant here is if there are any more shared pins (in the Uno, a4 and a5 are shared with scl and sda I think and are thus in the Fritzing sense bussed together). I think the gnd, 3.3V and 5V pins are the only ones with internal connections but if there are others they should be bused in ths Fritzing sense as well.
We can do that, although I read this forum more than github usually. However I would prefer to continue here, as this is as much about education for other users as anything else, and more users read this forum than github (especially new users).
Peter
Sorry but I’m too lazy to check the parts, but the all the variants of screw terminal are in FZ already. You select the spacing and number of pins in Inspector.