I am trying to create a wiring diagram, and I know that Fritzing is best for this, but I need an online alternative for Fritzing. What are some good ones?
Many here would disagree
Try EasyEDA for creating your schematic
Then you are very very much mistaken. It is a pile of crap and should be avoided. Just use a good normal 2D drawing package, you will be much better off.
I know, I know, but to be honest, I don't know how to read normal schematics, so I prefer Fritzing style diagrams, so I can see exactly how to connect things on a breadboard.
Build some diagram in Fritzing, show me and i make schematic of them.
You will see it is not very different.
Well, I am trying to make this circuit on a protoboard, but I am not completely sure how to build it.
Then drawing a physical layout diagram is not going to help you in the long term. If you can read a circuit diagram you just follow it when you lay it out on the board. It is a lot easier than you think. This is because it is almost self checking. When you wire up a connection from one point to the other, if you find a wire already connected to that point that is unexpected you know a mistake has been made either with the wire you are currently connecting of the one that is there already.
So in the circuit above, place all the parts on the board and make sure the strips are broken so that no pin is connected to any other. Then go round the chip and wire all the grounds to the ground connector. The same for the Vcc.
Then wire pin 10 of the chip to where it is going and so on until all the compare connected together.
There are 4 conectors on the left:
J3 is +5V power supply input,
U1 is connector to digital pin 2 with power supply,
J4 - connector to analog pin A0 with pull-down resistor of 10 kiloohm and with power supply,
J2 - connector to digital pin 7 and ground wire.
J1 - Two pinheaders or one socket for inserting Arduino Nano.
between +5V and ground is condensator 100 microfarad
Are there any "better than fritzing" tools that will generate nice protoboard pictures?
Don't waste your time with anything resembling Fritzing.
Anyone can learn to read and draw schematics. Start here for a good introduction How to Read a Schematic - SparkFun Learn
No need to learn any new software, either. Pencil and paper work surprisingly well.
I understand that Fritzing is an easy graphic program to layout prototype assemblies.
The alternative I use is the actual product datasheet drawing and a pencil + paper.
For your design it is really quite simple.
Line up your connectors on your prototype board. And for every green trace in the above you run a wire. I'm not trying to be a wise a** but once you start the first one you will see there is no magic.
There is nothing inherently wrong with fritzrig.
What we consider the cartoon view is what you see as a 3D view.
The problem we have is that the cartoon view is not as accurate or as informative as the schematic view.
There is little difference between the fritzrig schematic and any other program.
BTY x might do a mirror flip of the part.
And r might rotate 90deg
That is when it is done correctly. Most people with that skill level know of better ways of producing their schematic.
One big big problem is that the pin numbers around a chip are in a fixed position. You can not produce good quality schematics like that. A good quality schematic has short connections with the minimum of crossings. So the inability to move the pin to a position on the chip symbol (box), so that the crossings are reduced and at a convenient place is a big disadvantage.
ABSOLUTELY !
my comment about x and r was to get those other devices to turn around. silly to cross over things when not needed.
and you are 1,000% right that once you know how to make a schematic, it really don't matter if you use a pencil or software.
IMHO, the OP gets some points for posting an actual schematic and not the cartoon.
but, hopefully, he can figure how to mirror or rotate bits to eliminate confusing over-laying wiring.
NETs go a long way and his use of Vcc and Gnd did a lot to clean up his schematic. And to ease that wire crossing problem
as a comment about nets, I use easyeda since my WinQcad went south.
and the traces use the net name, so that makes board layout even easier.
Personally, the first thing I do is erase the frame. I doesn't need an artificial border.
I do miss the autotrace and the ability to have multiple pages for schematics on one project.
Love the description. I'm gonna use it in the future.
OP: Pretty Fritzing pictures are useless to an engineer. Many of us on this forum won't bother to decrypt the cartoon image, especially if it's complex. Using Fritzing pictures limits the potential audience of volunteers here who would be able to assist you.
The Fritzing "schematic" is NOT a schematic that an engineer would understand. It is no more than a 2D picture of the 3D drawing.
If you rely on Fritzing pretty pictures to assemble a project- you have learned nothing about how the circuit works. All the pretty Fritzing picture does is show you how to connect the parts.
Fritzing is ok for schematics , what people don’t like is the bread board view ( which we often see on here ) or the auto routing.
I started and still use this , need to move on , but can’t be ar*ed to learn a new one atm
Although I'm not a fan of Fritzing I appreciate that is provides a stepping stone for many folks just starting out with circuitry. Kinda like training wheels on a bike.
As such I think it provides a useful stepping stone and a place to get things accomplished while learning.
Before I switched to Kicad I used TinyCad for quick and dirty schematics. I think it works great for that goal. If a newbie started with TinyCad instead of Fritzing I'm sure the schematic would be no more readable.
IMHO
Did we eve help you with the next step?
In easyeda. Save.
Then to the right of center in the menu bar you create a layout of the chips.
They go over to the layout like dumping a box of chips on the table.
You drag them around till you like the arrangement.
Wait, are the same people here that are ok with Fritzing.. The same ones that argue that delay() is ok in some cases?
-jim lee
