Hi David, The reason I'm worried about them is that I'm not as familiar with Kicad and the ERCs helped me find things that I did wrong because I'm a newbie. For example, I couldn't see on the screen two identical components on top of one another or where a wire wasn't connected, but the ERC did. I don't like it when Kicad is complaining and I don't understand why. Assuming I'm always right is certainly wrong in my case. If there is smoke there is likely fire, and I want to find it before I get my circuit board back with mistakes.
Are there a lot of bugs in the ERC code? If so, I'd like to figure out what they are and fix them. Sorry for ranting back. You're right that I've spent entirely too much time trying to figure out what the ERC is trying to tell me. It would be nice to figure out what is making it so difficult to understand ERC and fix that as well. Rob David wrote: > > > Hi, > I read a lot of posts in this forum about ERC errors produced by > EESchema ERC function. Why do people waste so much time trying to find > out why EESchema produces these errors instead of relying on basic > electrical first principles? When I'm drawing a schematic I set all > pins that cause me problems (in EESchema) to passive. Instead I rely > on a thorough study of any device data sheets and Kirchoffs > laws/electrical principles. I can understand if someone has not had > any electronics training/experience but surely the designer of the > circuit, i.e you, have a better understanding of how things should be > connected. > Sorry for the rant. > > David. > > -- Rob Frohne, Ph.D., P.E. E.F. Cross School of Engineering Walla Walla University 100 SW 4th Street College Place, WA 99324 (509) 527-2075 http://people.wallawalla.edu/~Rob.Frohne/
