Sorry I just saw your post. I followed your advise to delete copper0. Thanks to you, I managed to create the jack. Take a look. Jack.fzpz (5.7 KB)
↧
Problem in creating 3.5mm audio jack (SMD)
↧
FC-51 Infrared Obstacle Avoidance Proximity Sensors Module
If its going to Git and everyones is going to get, yes, by all means make it good. It’s about time to draw a line in that sand and make all parts good from now on.
↧
↧
Problem in creating 3.5mm audio jack (SMD)
If you want an SMD part that can be used on either side of the board you need to have copper1 inside a group called copper0 otherwise the pads will get mirrored when used on the wrong side.
↧
Standardization of Fritzing part design
Hello @all,
it has been a long time i wasn’t around in the forum. the discussions are very known about the parts making procedure and it is time to make it much more straight forward.
therefore we begun with some node.js based things. there is now a fritzing-parts-api that uses the fritzing-parts-repository as some kind of api.
the aim is to firstly build a react parts-viewer. we are at a very good starting point at the moment. next would be to make a parts-creator out of the parts-viewer. so, at some point users do not need to get into the fzp business.
if you want to join the development, please let me know…
greetings fabian
↧
Fritzing as web application
hello,
this is a big topic and i am a late on the reply. fritzing should be, indeed, a web-application.
therefore we start to build a static fritzing-parts-api from the fritzing-parts-repository
you can check it out here:
it would be cool to get more people working on this. we already begun with a parts-viewer… let me know if you want to join the development 
↧
↧
Fritzing2Web - looking for contributors
Fritzing is a great tool and in the last time it lags of development. that is mainly because of the “complicated” codebase written in Qt.
Now we already started to build an api-client for the fritzing parts.
api docs:
currently we build a parts-viewer, uses the api-client, as a javascript/react-app that should later become a parts-creator.
Giving fritzing a new future is really what is needed. currently only the api-client is a public repository but the other parts for the app will be public as well when they reach a point where users can use them.
the fritzing qt-code is a good source to start from. the plan is to completely port fritzing to the world of html, css and javascript (mainly react).
if you want to take part of the development, don’t hesitate to let me know.
greetings
fabian
github: el-j
↧
Fritzing2Web - looking for contributors
as next we will make public a fzp parser package. if someone is interested in a preview, send us your github username and we will add you to the repo
↧
Need training on fritzing via team viewer, $40/hr PayPal
Try this, " https://www.youtube.com/watch?v=-lvdhj73ivM " , it is in Portuguese but is very intuitive … there are many lessons related this topic … enjoy
↧
Fritzing2Web - looking for contributors
Is the idea to make Fritzing a cloud based software requiring an internet connection and someone to maintain a fast expensive server just to let us use a piece of software that currently runs on our on systems without those needs? Or am I not understanding your goal?
If it is cloud based you are going for I will not be helping since I avoid all cloud based software at all costs even if it means something will take twice as long or not be possible at all.
If you are talking about making a desktop application that uses web technologies I would like to hear more how you are going to make it as fast as a native application since Fritzing is already slow and when working on complex boards can take minutes to compute stuff like ground fill.
↧
↧
Wire connectors to PCB
Hi there friends
I’ve looked everywhere and i can’t find a particular connector which i m sure its available somewhere since it’s so common and basic
help is apreciatted
↧
Wire connectors to PCB
In Fritzing use the search and search for “male header” or “jst” and you will find a few variations.
↧
Fritzing2Web - looking for contributors
the idea: fritzing have to live on. that’s the main goal.
as it is for now there is no much more development and a list of more than 1000 bugs where nobody knows where to start … i could continue with many more examples.
for now i think the best way would be to keep things in free and open services. so we can handle the parts via github, as well as the maintaining for all of them. i love the idea to create a open and free hardware-based-library as well …
to come to your point: fritzing should become a web-service (imagine the power of a server in doing things like a complex copper fill …) but i want to say: it must stay an offline software, too.
from the performance perspective: a slim and well build, state of the art, webbased-software (hopefully without any bugs 
) and the ability to easily build extensions/plugins for it, would be faster than what we have now. and it would fit the needs of different users and their way how they wanna use fritzing.
↧
Problem in creating 3.5mm audio jack (SMD)
Learned something new again. I was not aware of that and most of the smd parts I have seen are copper1 only. Something else to add to the parts checking script. Thanks!
Peter
↧
↧
Problem in creating 3.5mm audio jack (SMD)
It only became truly apparent in a thread about custom copper logos where I had helped make a part with copper1 only and when used on the back the words were backwards.
↧
Fritzing2Web - looking for contributors
Thank you for the explanation. I agree that Fritzing should continue and since your goal would be to have it run both locally and on a server I feel it to be a good goal. I run a local server in my home that is very powerful and having my own local copy of Friting running on it could be very nice as long as when I’m away from it I could still run it on my laptop with the need to connect to the internet.
Just in case other didn’t quite put it together yet @fa1 is the EL-j the active maintainer of the Fritzing github parts repo and most likely knows more then most of us when it comes to Fritzing code.
↧
Fritzing2Web - looking for contributors
I’m certainly interested in Fritzing and development and being retired, I have time. However I know almost nothing about javascript or react (nor CSS for that matter) but I can probably learn. From this I’m hearing (please correct me if I’m wrong) continuing work on the Qt code base isn’t going to be useful, as the future is something different? I’ll start looking at bringing up the api-client-js code and see if I can figure out how to contribute usefully. I may be of some use (how much I don’t know) on the fzp parser package because I wrote the python parts check script that parses the fzp file to check the parts. How much that knowledge will translate I don’t know (the format of the fzp file certainly will, but the xml parsing is done via lxml) but I’m willing to find out. As with here in Fritzing I’m vanepp on github as well.
Peter
↧
Problem in creating 3.5mm audio jack (SMD)
Your part is mostly OK, except that nonconn1 is an ellipse rather than a circle (usually caused by removing a translate, but there may be other reasons as well). If you export the pcb as gerbers (file->export->for production-> extended gerber) and look at the gerber layers with a gerber viewer (I use gerbv) you will see one hole is producing a drill hole (it is in the drill layer) and the other (which is the ellipse) is not but rather is a copper pad. To fix that, select nonconn1 in the xml editor and change rx and ry to be the same value (I copied the r value from nonconn0 to both). That will make both nonconns holes as you intend. You may also want to copy the breadboard, icon and schematic files from the Sparkfun jack part so you new part has all three views (or if you just need the footprint leave as is). With the change to nonconn1 your part looks fine.
Peter
↧
↧
Problem in creating 3.5mm audio jack (SMD)
Unless I’m missing something (which as you know is always possible 
), I think the two layer approach is only needed for parts with copper logos on both sides. This is a png from gerbv with the corrected jack part above with only copper1 defined. The one on the left was switched to the bottom of the board in inspector and the one on the right is the default top of the board setting. The pads aren’t duplicated as far as I can see. Am I missing something here? I suspect the addition of the copper0 layer is what causes the pads to be duplicated and may be fixable by removing the unwanted copper layer definition in the fzp file (although you would need to do that by editing the file I expect).
Peter
↧
Problem in creating 3.5mm audio jack (SMD)
Interesting. My first guess would be since this part was created originally with both copper0 and copper1 to satisfy the need to have a copy for each side and then changed to only have copper1 it may be allowing this to happen despite not having one within the other. The copper logo thing is actually just an SMD single pin part so the rules that apply to it must apply to these as well.
My second guess is maybe it just mirrors the individual pads and since these pads are rectangles it doesn’t matter. But if the pad was non-symmetrical it would show up. I say this because the copper logo thing was in essence just a single pad that got mirrored.
↧
FC-51 Infrared Obstacle Avoidance Proximity Sensors Module
Yes, of course it is going to be on github repository. I already got approved the next fritzing parts which you have been helping me along with vanepp:
- Seeedstudio LinkIt One Board
- XL4016 DC-DC Converter
- IFR520 MOSFET module
You can check those looking at the commit log here (search for KingDarBoja).
↧