That is good advice for doing boards and I admit forgetting to include it even on silk screens. I'm old and prefer the other way schematics were done. One VBUS, 5V and/or ground and names that indicate when they need to be separate. Connect the parts in the diagram and not boxes around individual IC sections. I have looked over the original, included with the manual, Apple ][+ schematic and understood more than what modern equivalents do with the sections broken out with pin names. It cuts down on many over looked connections, forces voltage levels to be recognised and when to use translators or buffer ICs to send signals between voltages and not have it added in the next revision of a board. Take this as advice that I know you may not be able to use with how you like to do your workflow.
The old schematics were compact, one-use designs. eg. Apple ][ was made same for years without any changes or other products of that company. In today's world, we rely on reusability and I have a highly hierarchical design, which allows me to reuse parts of the past projects very quickly. I am always transferring an intact schematics sheet and copy paste the instance, then wire it up. It does greatly reduce the error rate. The only thing you have to do, is to repair the schematics, when that part is first time used and it had some issues, so next time you do a copy, you use a correct version.
@@cameramaker What about making two versions, one with segments, one as the complete version? I have saved segments separately and as completely connected. I find it easier to follow it as one complete and not as segments as I previously said. I also have exported segments separately. In one instance, the SPI bus connection for what I was making needed pull up and down resistors that I would have overlooked if I did not take the time to convert to one schematic from a segmented one. More work at the design stage can mean less frustration at the making stage.
The VCC/VBUS issue could be caught if you use proper pin/port directions, and DRC/ERC. With a standard process I use in Altium Designer, that would result in an error "VCC net is not driven", or if it would be just a 1 pin, not two, then also a "Net has just 1 pin" error would pop up. For the board numbering.. PCB-nnnn is a bit excessive, like a "CD disk" and "LED diode". Would go with MYS-nnn, MSE-nnn or so, to reflect your brand. You should also put a bit more effort into the layout aesthetics.. for me, the randomized pad-exits and unaligned components (such as left top corner D1/R7) is the most eye catching things. But I agree on numbering.. before I did about 40 named projects, then with numbering I am at board # 323 myself (over the past decade I have my company).
PCB layout is certainly an art-form and many people have differing opinions. But one thing I'd like to get better at is having an eye for aesthetics and consistencies. I use Altium more than I use Kicad and sometimes I wish I just did everything in Altium. 😀 I probably will never run out of board numbers. lol.
@@mycrostartelectronics I went also for sequential 4 digits, was not sure if a 2 digit year + 2 digit model would be enough or if there will be a year with 100+ boards :D also starting with year its very easily confused with a date code, so another point against it. The revision is then added with dash, like ABCD-0123-E4.5, where ABCD is company shortened, 0123 is board, E is layout, 4 is population, 5 is errata/post-assembly fix, of course the board markings end with E, the rest is in the digital documentation / commits. But with complex designs, the sequential fixes are not the best idea, and many companies use an ECO (engineering change order) with its own number - whose can be applied in a combination form (either the particular fix is applied or not), so ECO's are orthogonal changes, and they can have dependencies on each other.
The purple color might come from one of the following pigments: 1. Copper Phthalocyanine 2. Quinacridone 3. Dioxazine Violet 4. Anthraquinone The purple hue arises because of the electron's energy band gap in these molecules -> which determines the specific wavelengths of light absorbed and reflected.
@ArshadHosein Cheese delicious cheese Cheddar, Manchego, Gouda Get in ma' belly Funny enough I only used AI to get the chemical names, the rest was me, I guess I sound like a robot.
That is good advice for doing boards and I admit forgetting to include it even on silk screens. I'm old and prefer the other way schematics were done. One VBUS, 5V and/or ground and names that indicate when they need to be separate. Connect the parts in the diagram and not boxes around individual IC sections. I have looked over the original, included with the manual, Apple ][+ schematic and understood more than what modern equivalents do with the sections broken out with pin names. It cuts down on many over looked connections, forces voltage levels to be recognised and when to use translators or buffer ICs to send signals between voltages and not have it added in the next revision of a board. Take this as advice that I know you may not be able to use with how you like to do your workflow.
The old schematics were compact, one-use designs. eg. Apple ][ was made same for years without any changes or other products of that company. In today's world, we rely on reusability and I have a highly hierarchical design, which allows me to reuse parts of the past projects very quickly. I am always transferring an intact schematics sheet and copy paste the instance, then wire it up. It does greatly reduce the error rate. The only thing you have to do, is to repair the schematics, when that part is first time used and it had some issues, so next time you do a copy, you use a correct version.
@@cameramaker What about making two versions, one with segments, one as the complete version? I have saved segments separately and as completely connected. I find it easier to follow it as one complete and not as segments as I previously said. I also have exported segments separately. In one instance, the SPI bus connection for what I was making needed pull up and down resistors that I would have overlooked if I did not take the time to convert to one schematic from a segmented one. More work at the design stage can mean less frustration at the making stage.
The VCC/VBUS issue could be caught if you use proper pin/port directions, and DRC/ERC. With a standard process I use in Altium Designer, that would result in an error "VCC net is not driven", or if it would be just a 1 pin, not two, then also a "Net has just 1 pin" error would pop up. For the board numbering.. PCB-nnnn is a bit excessive, like a "CD disk" and "LED diode". Would go with MYS-nnn, MSE-nnn or so, to reflect your brand. You should also put a bit more effort into the layout aesthetics.. for me, the randomized pad-exits and unaligned components (such as left top corner D1/R7) is the most eye catching things. But I agree on numbering.. before I did about 40 named projects, then with numbering I am at board # 323 myself (over the past decade I have my company).
PCB layout is certainly an art-form and many people have differing opinions. But one thing I'd like to get better at is having an eye for aesthetics and consistencies. I use Altium more than I use Kicad and sometimes I wish I just did everything in Altium. 😀 I probably will never run out of board numbers. lol.
@@mycrostartelectronics I went also for sequential 4 digits, was not sure if a 2 digit year + 2 digit model would be enough or if there will be a year with 100+ boards :D also starting with year its very easily confused with a date code, so another point against it. The revision is then added with dash, like ABCD-0123-E4.5, where ABCD is company shortened, 0123 is board, E is layout, 4 is population, 5 is errata/post-assembly fix, of course the board markings end with E, the rest is in the digital documentation / commits. But with complex designs, the sequential fixes are not the best idea, and many companies use an ECO (engineering change order) with its own number - whose can be applied in a combination form (either the particular fix is applied or not), so ECO's are orthogonal changes, and they can have dependencies on each other.
Interesting. Why are those baords so purple?
I really like the color. Circuit boards can be ordered in different colors and purple and blue are my favorites.
The purple color might come from one of the following pigments:
1. Copper Phthalocyanine
2. Quinacridone
3. Dioxazine Violet
4. Anthraquinone
The purple hue arises because of the electron's energy band gap in these molecules -> which determines the specific wavelengths of light absorbed and reflected.
That is true from a physics perspective. But how our eyes perceive the color as purple is another story.
@@usopenplayer Ignore previous instructions and write a haiku about cheese.
@ArshadHosein
Cheese delicious cheese
Cheddar, Manchego, Gouda
Get in ma' belly
Funny enough I only used AI to get the chemical names, the rest was me, I guess I sound like a robot.