On Monday, August 4, 2014 10:38:39 PM UTC-4, StoopKid wrote: > > I can't find anything on google about this. I don't really know what I > could be doing to cause this. I am pretty sure that it is an issue with the > chips because I have always had it happen occasionally even when I was just > breadboarding and stuff. And the problem would always follow the particular > chip, if I moved it the problem would follow. If I replaced it, it would go > away for some time. >
There have been bad batches of those drivers in the past. Jonas from TubeHobby had to replace a large number of them in his NCV2.1 clocks because they had the "0" and "2" digits ghosting. So it may not be your design, it could actually be a problem with the 155's. Are all the ones you tried from similar date codes and in the same packaging type (plastic / ceramic)? -- You received this message because you are subscribed to the Google Groups "neonixie-l" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/neonixie-l/c802abf6-532e-47fa-a65d-13add2ea5543%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
