God bless you for making that part, I really needed it for my project. Can you upload it to github repository or shall I do it for you? 
↧
FC-51 Infrared Obstacle Avoidance Proximity Sensors Module
↧
FC-51 Infrared Obstacle Avoidance Proximity Sensors Module
That part was made so long ago it probably doesn’t pass Van’s standards. 
It could use a PCB outline.
↧
↧
Standardization of Fritzing part design
This was actually discussed, but it didn’t go far.
Basically there are 3 main part makers, 2 wanted it with one knowing how to implement stds to parts and me that didn’t, and 1 that didn’t citing that if it worked who cares. I’ve seen another EDA go through a major overhaul of their parts and put in place a very strict system to ensure quality parts, which is mandatory to be professional, but they were able to do it because they have a huge work force of contributors to draw from.
FZ is kind-of it own worse enemy because it’s for beginners and beginners aren’t smart enough to help FZ.
↧
FC-51 Infrared Obstacle Avoidance Proximity Sensors Module
Sure, feel free to submit this improved version @Old_Grey is correct it had a few errors). I intended to do so when I got time, but so far time hasn’t appeared …
fc-51.fzpz (21.3 KB)
Peter
↧
Standardization of Fritzing part design
That’s me. If the only way to make parts was the way @vanepp explains I would not use Fritzing at all. In all honesty I can’t even follow 99% of what he says and I believe it only makes part creation harder than it needs to be and scares away more people than it helps. For all the parts I make for making PCBs if it takes more than half an hour to make a part I have done something wrong. If Fritzing would allow parts with embedded PNGs into the main repo for Breadboard view it would easy. You would just take a picture of a real part and add the connectors.
I would say this is true but for a different reason. I think Fritzing is a great EDA and the only part that makes it look like a toy and makes making parts hard is the Breadboard view. If it didn’t have it people would take it much more serious and parts creation would be a breeze. You would start with a generic ic to generate the schematic and then the only thing left would be make the PCB view which is easy because it is only copper and silkscreen.
↧
↧
Standardization of Fritzing part design
The part std is too advanced for me too, but non std bad parts aren’t great either. Some old parts are so strange in their format and have so much junk attached you just have to throw them away and start again because it’s too confusing to just do a simple mod to make into something else. Standardised parts would make mods much more simple and would be faster than making new. Basically it pain now for reward latter.
You can ‘Trace to Bitmap’ PNGs in INK - I have a tutorial - and just add some connectors. For one-off or low demand parts this is probably the best way.
I was thinking about getting rid of the BB view, or changing svg drawing to CAD drawing so we have 3D view because it’s the same work as now, but basically BB view is the only reason it should exist because there is plenty of other EDAs. Besides helping beginners it’s good a documenting stuff for tutorials.
BB view is complex to draw, but everyone trips up on the group structure of PCB view so it’s probably not as simple as getting rid of BB view.
↧
FC-51 Infrared Obstacle Avoidance Proximity Sensors Module
Thanks! Indeed, I can see the improvements on pcb view, but breadboard can be improved a bit more 
I do rather want to change the background color, place both smd led on the board and copper stuff on the infrared ones like this image.
↧
FC-51 Infrared Obstacle Avoidance Proximity Sensors Module
Fine by me, go for it!
Peter
↧
FC-51 Infrared Obstacle Avoidance Proximity Sensors Module
It would be nice to make everything perfect, but these things change so fast it’s probably not worth the time.
↧
↧
Standardization of Fritzing part design
The same can be done here but of course, with the help of devs and the part makers. I really learned it quickly and even though I am not the fastest (since I spent like 2 days per part), I feel pleased with the final results.
It’s because most people doesn’t like making parts or don’t have time to make one since they just want those for their projects.
That’s true, maybe vanepp has too much experience and his instructions would be complex at first, but after following them carefully (and digging into Inkscape featureS), you will catch up quickly.
For example, his most recent tip regarding how grid alignment works, made me understand (and save time) while making part fixes.
I didn’t understood this line, what is std part?
Breadboard view is what makes Fritzing so good
As I can say as newbie user, we should redo the tutorials.
↧
FC-51 Infrared Obstacle Avoidance Proximity Sensors Module
I know most Arduino stuff changes a lot but this part is currently missing from fritzing-parts repository and could be great if it looked like a real one (just minor fixes away). After that, just pull-up request and wait for admins to approve it.
@vanepp If you get time, please make a list with all the parts you have designed so far
↧
Standardization of Fritzing part design
I meant that Van’s part standardisation was so complex I didn’t understand it.
I have no experience in this field at all so it took me over 1 year to make a part because I had to learn FZ and INK from scratch. I asked the forum for part help about 2 years ago and didn’t get one response - basically there was no one here -, and when I looked at the guides they weren’t comprehensive enough to make parts and expected you to already know stuff. Basically there was nothing for a total beginner that never heard of this stuff before. Even now we are discovering new stuff as we stumble across it, because the creators never told anyone anything.
↧
FC-51 Infrared Obstacle Avoidance Proximity Sensors Module
I asked him before but he is way too busy trying to make guides to get FZ complied on all platforms.
↧
↧
Standardization of Fritzing part design
The main reason I use Fritzing over Eagle which I used to use is because the views are tied together. I can lay everything out on the PCB and then make the schematic after based on the ratsnests to confirm I made it as I have it in my head. With some other EDAs you could work on the PCB first too but after that you would have to start over to make the schematic and never know if you got the PCB right. You can also use it to reverse engineer things by working in PCB first.
I can make a part in 1/10 the time it takes him and they work as they are supposed to so there is nothing to catch up on.
As for the alignment tip if you had used a generic IC to generate the Schematic and assign its labels you wouldn’t have ever needed the tip. It is only because things are being done the hard way that that information is even needed. And if you assign the pins in the Editor instead of wasting time putting them in the SVG I believe it aligns them correctly for you (I could be wrong as 99% of the parts I use/make are SMD since they are so much easier to solder and I turn off the grid because the alignment I need is so fine it makes Fritzing unusable).
Have you read my Inkscape tips and tricks thread?
↧
Standardization of Fritzing part design
Yeh, FZ has some nice features - that’s why I like it -, but if you switched to the slower work flow EDAs it would be negated by faster part making. You get used to other EDAs eventually.
↧
FC-51 Infrared Obstacle Avoidance Proximity Sensors Module
Here is a list from my created_parts directory. They should all be in the forums somewhere, but are probably (mostly!) not as good as current standard because many predate the creation of the parts check script. Many of them I don’t remember making, some of them may not be mine and just in the wrong directory . Then there are a bunch of user submitted parts that I have fixed up over the years that aren’t in this list (and because they aren’t mine, aren’t mine to submit to core either).
1x4 Membrane Matrix Keypad.fzpz
3.2in tft touch screen.fzpz
3.5mm switching Jack.fzpz
5-channel flame detector module.fzpz
6 circuit slip ring.fzpz
12circuit slip ring.fzpz
74LVC8T245.fzpz
74x125.fzpz
74x367.fzpz
74x541.fzpz
18650 battery holder.fzpz
Ceramic Capacitor top view.fzpz
DM860A Stepper Motor Driver.fzpz
DC 3.3v-10v TO ± 12V Mini DC converter.fzpz
DC 3.3v-12v TO ± 15V Mini DC converter.fzpz
DC 5V TO ± 12V Mini DC converter.fzpz
DC 5v-12V input to ± 12V DC-DC converter.fzpz
Electrolytic Capacitor top view.fzpz
fc-51.fzpz
Goouuu Mini-S1 ESP8266 Nodemcu.fzpz
gtm2088argb-21.fzpz
hcmmodu0083.fzpz
sen136b5b.fzpz
HSM-A43 LED Indicator.fzpz
IL612-2e.fzpz
ITG-3200.fzpz
JOYSTICK_10mm_fixed_pcb1.fzpz
Keyes l9110 Fan module.fzpz
kmr1_8_spi_tft.fzpz
KWM-R30881CUAB.fzpz
KY-026.fzpz
ky-038.fzpz
LM386_fixed.fzpz
sheilded_nomag.fzpz
Membrane Matrix Keypad_mine.fzpz
Micro Slide Potentiometer.fzpz
Mini-360 DC-DC Buck converter.fzpz
MOSFET-NCHANNEL_fixed.fzpz
non-restable_thermal_fuse.fzpz
nrf24le1 larger (probably not finished as no fzpz file)
nrf24le1 small "
PH10PIN-2.0MM.fzpz
Pololu QTR-8 Reflectabce Sensor array.fzpz
roborio.fzpz
Rotary_Switch_4x1.fzpz
S-350-60 Power Supply.fzpz
SBX DSUN.fzpz
sct-013.fzpz
Shortened_LED.fzpz
SMA Antenna Connector.fzpz
soic20.fzpz
STEF12 fuse.fzpz
Stereo POT.fzpz
SWITCH-DPDT-latching.fzpz
tlp185.fzpz
TLV431.fzpz
TO-220-2lead.fzpz
TO-220-3lead.fzpz
TO220-4lead.fzpz
top View TO-92.fzpz
tp4056.fzpz
VA250LA40BP.fzpz
Vex Voltage regulator module_improved.fzpz
Wemos ESP-Wroom-02.fzpz
Wemos lolin32.fzpz
xr10910_qfn40.fzpz
Peter
↧
Standardization of Fritzing part design
This in my view is the underlying issue here. There are not that many people making parts, and basically no one developing. The original developers or even anyone familiar with the code base do not appear to respond in the forums so development is a challenge to say the least. That is the number one issue that we need to address in my view. If we can kick start development we maybe can make progress. The parts check script is a start to making the parts maintainer’s job easier. He is almost the only one of the original developers (AFAIK) that is doing much, and he expressed the desire for a more automated way to check parts for inclusion in core. That is where the standardize parts thread started, but there are too few of us involved to come to any useful conclusion I fear.
Since my first part (with 4 whole pins in a DIP package) took me about 2 months to get to a semi reasonable state and probably about 6 months of elapsed time learning about Fritzing and Inkscape don’t feel bad .
A number of complex parts I’ve made have taken me very long times (about 6 months for Brad’s education board) but through it all I learn more and more. That knowledge of the internals of parts are what drove the parts check script.
and as I have said before, in my view, breadboard is the unique feature of fritzing. It allows documenting the interconnection of modules in breadboard to document a project made of a series of modules (with no pcb views in use). No other package I know of does this.
Peter
↧
↧
Problem in creating 3.5mm audio jack (SMD)
↧
Problem in creating 3.5mm audio jack (SMD)
It is not letting me upload the svg file.
↧
Problem in creating 3.5mm audio jack (SMD)
To upload the svg, rename it from .svg to .fzpz and upload it as an fzpz and tell us it is really an svg.The forum sometimes has trouble rendering the svgs. The best thing would be to upload the entire part as a .fzpz file though, as then we have all the files that make up the part (4 svgs and the fzp). To do that right click on the part in its bin and click export part which will write an fzpz file that you can then upload. However I can answer your question just from the xml editor lines. This is an old part, in an old format. The copper0 isn’t needed any more. If you delete nonconn2 and nonconn3 and the copper0 group that should work fine (you probably need to also remove the copper0 definitions from the fzp file as well though). From the looks of the image in the svg you may also have translates usually caused by moving elements in a group without ungrouping it (which usually removes the translates). Sometimes that causes problems in gerber generation although in this case it looks to have happened in Inkscape as well.
Edit: I grabbed the part you started from and converted it to current norms (rescaled schematic and pcb, removed copper0 from pcb). The fzp file had in fact been correctly converted so just deleting copper0 in the pcb svg should work fine for you if thats what you choose to do.
AUDIO-JACK2_converted.fzpz (5.9 KB)
Peter
↧