1 – Clearly show how your wires are connected

You will rely on wires to define the connections between symbols on the schematic. In Jupiter, these are called networks. Whatever you call them, there are a few guidelines to keep in mind.

First, whenever two wires form an intersection and share a device connection, there needs to be an electrical node at that intersection. This is standard practice in every schematic design, and certain tools (such as Jupiter) will automatically add electrical nodes for you.

However, cross wires without electrical nodes do not have electrical links, but are only visually crossed.

When adding electrical nodes to intersecting wires, it is also recommended to avoid using 4-way intersections, as this may increase confusion when reading the circuit.

Instead, choose a set of shared intersections, as shown below, where each intersection has its own unique connection. This makes it easier to understand exactly the right connection and avoid misunderstandings.

2 – Complete the network connection when it makes sense

The goal of schematics is to make your circuit more readable or as easy to understand as possible when handing it over to other engineers, so minimize any unnecessary network connections.

When there are multiple pins that need to be connected, do not use the wire to connect, which will make the drawing disorganized, you can use the network label instead of the wire, and the master and slave devices place the network label of the same name as the connection, which can enhance the readability of the schematic without adding any unnecessary confusion.

Similarly, we recommend that your web name be as short and in all caps as possible. Naming the network “CLK” is much simpler than naming the network “10 MHz clock to PIC”.

3 – Always use the same symbol for the same device

If this is one of your schematics, then you may be surprised to learn that there are several different ways to draw schematic symbols. Different places have different standards for schematic symbols.

To keep things organized and consistent on the schematic, use the same symbols to represent the same device. For example, placing an IEEE resistor on a schematic and then drawing an IEC resistor will only lead to confusion.

4 – Make sure each part has a unique indicator

This is another tip for improving the consistency and readability of schematics.

Each symbol on the circuit needs to have its own unique indicator so that each part is easily identifiable. For example, each resistor should follow a consistent naming order of R1, R2, R3, etc. Batch editing is available in Jupiter.

5 – Keep text placement consistent

When placing symbols on a schematic, take the time to Orient all names and values in the same direction, regardless of the location of the component. This will make your schematics easier for your peers to read and refer to. In Jupiter, this process is quite simple. There are three ways to do this,

1. Right-click rotate button.

2. Menu bar rotate.

3. Shortcut key R. Shortcut key space.

Batch operation: Ctrl select multiple objects.

6 – Keep the schematic logically arranged

When drawing the schematic, it is important to keep in mind the logical flow of the circuit.

For most electrical schematics, with some minor exceptions, the signal input will always come from the left and the signal output will always be on the right. Power will start at the top and ground, or the negative voltage will go into the bottom.

When drawing the schematic, make sure that the placement of symbols and the connection of the network always follow this logical flow. This will make it easier to refer to schematics in the future and will also make it easier for other engineers to read.

7 – Divide the schematic into logical blocks

If you’re designing a complex circuit that has multiple functions and can be logically layered,

So do this:

Hierarchical and hierarchical organization by function or module.

This makes it easier to check and troubleshoot circuit faults when the main functional area is clearly defined on a separate sheet.

Also, don’t be afraid to leave blank space on your schematic drawings. The goal is not to fill every inch of the schematic, but to keep the circuit logically layered and organized so that it is easy to read.

8 – Design your schematics for easy print ability

We recommend always drawing schematics that can be easily printed and viewed on standard paper. In the United States, it is 8.5 inches x 11 inches, and in Europe, the A4 size used is 210 mm x 297 mm. The current domestic use is the European size.

Why limit the schematic to this size? Because most people can only use printers with standard page sizes.

Due to this size limitation, we also recommend using multiple schematic drawings when needed to guarantee that the logical diagram is easy to view without panning. Even if the schematic is not printed out, it is easier for a functional schematic block to flip pages between multiple worksheets in a PDF than it is to pan a large drawing manually.

9 – Place the decoupling capacitor next to the device

If the schematic is made purely for electrical connections, not for rules about placement, with one exception, then it is for decoupling capacitors. These components are crucial when you need to smooth power signals from sensitive components such as integrated circuits. When placing the decoupling capacitor on the schematic, position it close to where the component will be placed in the physical PCB layout. This will help layout engineers quickly understand the intent of a set of capacitors.

10 – Remember your title bar

And last but not least,

Remember to always include a title bar on each page of the schematic! It’s a simple tool that helps you keep track of multiple schematics, know who designed them, and know which version of the design you’re looking at. When adding a title bar, place it in the bottom right corner of the worksheet and include the following information:

1. Line name, your name and date of creation

2. Schematic drawing number (if there is more than 1 page)

3. Also, consider adding a revision number to make it easier to distinguish between versions