2 ms·
For the customer-replacement case, you simply tell the customer to replace just one bulb at a time - and the computer can update the mapping. In the factory, y
by londons_explore 4y ago
For the customer-replacement case, you simply tell the customer to replace just one bulb at a time - and the computer can update the mapping.
In the factory, you fit the bulbs in a certain order every time, and the computer knows that order.
- culturestate 4y ago> For the customer-replacement case, you simply tell the customer to replace just one bulb at a time Just imagining the customer support for this is gonna give me nightmares. “Sir, you need to make sure your vehicle’s ignition is turned to accessory mode. Then wait for the light to blink twice, that’s the vehicle’s confirmation that it correctly identified the new light. If it blinks three times, it can’t confirm the light’s location, so you should try removing it and re-inserting it. If it blinks four times, that means you didn’t replace the bulbs in the correct order so you need to initiate a manual reset procedure by going to the driver’s seat and…”
- robocat 4y ago> simply I’m guessing you’ve never worked in customer support. The failure modes of mistakes would be nasty. Even smart people swap bulbs around when diagnosing faults. Simplicity (good usability) is most always crushingly hard to achieve, doubly so for hardware. Calling things “simple” is often a sign of shallow thinking in my experience - something a customer or manager might naively say but an engineer cannot (because they have to deal with all of the real requirements). For example, the engineers that build cars can’t say “you simply push a button to start a car” - as an engineer the complexity behind that simple operation is very very deep.
- JohnFen 4y agoBoth of those sound like hopelessly error-prone processes likely to lead to visits to the repair shop.