3 ms·
1998 - automated troubleshooting program for use by people on the production line for power conversion hardware. Worked, but system abandoned by employer after
by BJBBB 6y ago
1998 - automated troubleshooting program for use by people on the production line for power conversion hardware. Worked, but system abandoned by employer after I quit.
2001 - 'real-time' monitoring and analysis of data coming from the ATE stacks on the factory floor with various trending graphs and other stuff for consumption by quality and manufacturing engineers. It worked well, but politics in the Mexico factory sunk it to create more jobs to do this stuff manually.
2006 - automation of XRF process. The technician blew the power head, so most of this testing was eventually outsourced to a local lab.
2007 - automation of "Type" tests and high-speed data acquisition for single fault conditions and thermals and other stuff. UL was too stupid to understand anything, and would not accept data unless the tests were done manually and data was hand recorded.
2019 - 'universal' environmental recording and control systems for use in test chambers and agricultural. Reliable and accurate, but too expensive and required the customer to understand a bit of physics to implement the zone mixing feature.
- escapist16 6y agoThat is impressive. Automated troubleshooting program in 1998 was cool. Do production lines today have that sort of ability?
- BJBBB 6y agoFor that type of stuff, probably a stupid idea because the root cause was poor process control by the factory. Typically modern production lines mitigate troubleshooting and re-work by building it correctly, which was supposedly the original reason for all of the ISO 9k hoopla. And re-working stuff on the factory floor does bad things to long-term product reliability, so my solution to the problem at hand was doubly stupid.