Picking resistors with readable color codes was part of speccing the component back in the thru-holes days. Yes there were these cheap cylindrical brown ones that were almost impossible to read. We used the peanut shaped beige ones which were readable and the 1% resistors had color codes, too. The 1% had an extra color line. I use to train assemblers to read the color codes and use them to inspect boards. Color codes were very useful. Even if they didn't read the codes, comparing to a known good board, a wrong color component was visibly different. Try that with tiny printing.
Exactly -some of the paints are so unclear -red, orange brown can be hard to distinguish. Sometimes the brown band to designate 1% is the same width as all the other bands - so which end do you read from? And if the body colour is other than neutral, be careful - the body colour can mix with the bands to make them undecipherable.
Another PO (no, not Purchase Order) is those thru-hole resistors printed with text - when reverse engineering a board, the damn value is always facing DOWN against the pcb. Same with thruhole caps and diodes - ARRRRGGGHH!
@Max "the colored bands on the resistors served to distinguish their values,"
Speak for yourself!
By that I mean what if you can;t distinguish resistor colors? In particular ,red, green, brown. I can't and haven't for many years. Even at my first job, I always used 1% resistors because the values were printed with numbers.
I once write a piece called "Help me read this resistor." Perahps it's time to dig it up and post it here.
I just received this from the Managing Director at Yageo:
We are in process with Digieky to make all their inventory in "Marking Product". Then you just order as usual. However this process is still running and we can not make a digital swtich. Please understand.
I think I'll steer clear of their product for a while until you folks use up all of the unmarked stuff. Whoever uses the last unmarked resistor, please give me a heads-up!
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.