@aubrey: IIRC, NXP also has an extensive line of SPI and I2C serial to parallel devices (and they are far less obnoxious than Infineon in their download conditions). I can't cite part numbers as I have been away from the HW implementation side for several years, but I know there are parts like this from other suppliers (including Asian ones too).
This is great information. I am pleased that some companies still see a market in serial drivers. Since it is targeted to the automotive market, I am surprised that there aren't more competitors.
One thing though. On some of the products before you download the data sheet you have to accept an "AGREEMENT ON THE USE OF PRODUCT INFORMATION" which states
"Any Product Information disclosed to you after clicking the "Accept & Open" button is confidential information of or made available by Infineon and shall (a) be used and copied by you only for deciding on the purchase of the respective product, its evaluation or application, (b) not be distributed, disclosed, or disseminated in any way or form by you to anyone except your employees contractors or customers, provided they have a reasonable need to know such confidential information for the purpose of (a) and are bound to confidentiality by their agreements or otherwise not less stringent than under the obligations of these terms; and (c) be treated by you with the same degree of care to avoid unauthorized disclosure to any third party as with respect to your own confidential information of like importance but with no less than reasonable care."
which is followed by
The obligations as per Section 1.1 shall not apply to any Product Information which you can prove, (a) is at the time of disclosure already in the public domain or becomes available to the public through no breach by you, except that such information shall not be deemed to be in the public domain merely because a part of the Product Information is embodied in general disclosures or because individual features, components or combinations thereof are now or become known to the public;
Which seems to negate the first paragraph completely and since you are downloading a datasheet which I think is considered in the public domain it seems to be a meaningless (and irritating exercise). If I am wrong about it being in the public domain, it means that you can't write about it on a blog...
Nevertheless these are good looking devices and bound to be included in my future products.
I forgot to make an admission. This blog is a re-run (slightly modified) from one that was on the departed MCC. I said about Supertex in the blog "They also appear to make an 80V HV5812 which is an equivalent to the TL5812". I can now confirm this.
I had a legacy product that included the TL5812, or at least the Allegro successor, the A6812. We had an order and we couldn't find any more, so as luck would have it as a direct and coincidental result of my research on this blog I successfully substitued the HV5812.
I spoke to the rep who said that Supertex has never obsoleted anything, but that was before Microchip took them over. That is not to say that Microchip has a history of obsoleting parts- my experience is in fact the opposite, having only felt the anguish once in many years and across many parts.
I recently got some MM5451 chips...these have serial inputs (data / clock) and 35 LED outputs with variable brightness...much like the chips you cite but only 12V / 15MA outputs
These look quite interesting. Despite their vintage I see they are still in production from Micrel and in plentiful supply from Mouser and Digikey. Could have used them instead of the ST parts (STP16CP05) since I had to general the 15V anyway- it could have just as easily been 12. I will keep it in mind for next time.
Max (and Aubrey) I am not sure whether this would be any use....I recently got some MM5451 chips...these have serial inputs (data / clock) and 35 LED outputs with variable brightness...much like the chips you cite but only 12V / 15MA outputs. I got 4 of them for $6.50. There are a few chips that do this sort of thing. But if you want higher voltage or more current, you'd need to get something else or use driver transistors on each output. If you would like some, I can order you some, that's a special price at the moment so you'd want to be quick.
This topic has a particular interest for me -- although my problem was to have lots of 5V outputs. Several years ago, when I first started to experiment with the electronuics fot my Inamorata Prognostication Engine, I realized I wa sgoing to need to drive ~120 tri-colored LEDs (along with monitoring switches and knobs and driving meters and suchlike)
Do you remember my Awesome Art of Bodacious Breadboards blog? The photo of the breadboards actually showed chains of shift-registers used to monitor multiple switches as inputs and drive multiple LEDs as outputs.
In my case, the solution was to use Adafruit's NeoPixels, which allow me to control all 120 tri-colored LEDs using a single microcontroller output pin, but I will be very interested to hear what other people are doing in this area.
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.