The clock looks great!
It seems we have the same PCB manufacturer. Only 402 orders so far? I'm
already at 418 :-)
--
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
The tubes are direct drive but the issue is that the tubes which display
only a dash (instead of a colon) are cycling on and off every second, so
the LEDs would be constantly turning on and off. It is only when one
segment or DP is energized that the dark turn-on is an issue, so it would
be to
No problem; amazing what you can do with 500nm.
Since they actually are UV LEDs, you may want to tweak the software so they
can be turned off after a few seconds if your clock is direct-drive. If
it's multiplexed, you probably need the UV on continuously in the dark
(would be very informati
Hi Greg, The LEDs were 385nM, not 885nM. Clearly the LEDs were UV. I
initially thought the 365nM would be more effective but they were not. The
365nM parts might have also been less desirable from a safety standpoint and
were also quite a bit more expensive. The 405nM UV LEDs are less expens
885-890nm ? That's infrared. If the LEDs are always-on, then I'm glad
you're using IR instead of UV because it's much less harmful (perhaps
harmless ?) to materials and humans/pets, etc.
BTW, those are really interesting tubes. I dont think I've ever seen tubes
with a solid/opaque anode.
On Mo
