We're totally on the same page. My reaction was, "Never again." Their ASIC business closed, but they still make other kinds of chips. I don't flat-out refuse to consider their product, but on the other hand, if there is an alternative, I do sort of lean that way.
I know you probably won't name the ASIC company, but the flippant response they gave you really irks me. If I hear that someone has had problems with say a certain appliance manufacturer, car etc, they will never get my business. The ASIC company was at fault and should have owned up to it right away. Anything less is reason to go somewhere else.
A coworker came up with a complement of the 5 Why process. The "5 Who" process used to determine "Who will pay?" First it got a laugh and then we realized that, more often than not, it reflected reality.
The fact is that while the customer is NOT always right, THEY ARE the ones with the money. I have showed customers that the "build to print" they supplied would not work, and that customer was grateful, responding with a PO to make the design work. But not all sales weasels are as cooperative as they were at that employer.
Many years ago (at a company I am no longer with) the salesheads pressured engineering into a product modification which they them sold to customers prior to a repeat of RF emissions testing to FCC Part 15. My own project had been suddenly canceled and I got pulled into the mess when the subsequent RF emissions testing revealed that the modified product vastly exceeded allowable FCC radiated limits.
After I did much physical and mechanical redesign and got the product to pass FCC testing, sales response was "How do we explain to the customers why they need to make this change? Can't you fix the problem without having to make all these changes?"
To which I basically replied "That's YOUR problem. YOU decided to sell the modified product prior to emissions testing."
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.