Integrating Subsystems
At Endigit, we have a lot of experience building automated test systems. We have automated tests for R&D, production testing, post-production quality testing, and automating the production process. Our experience is especially valuable because we have come across many of the pitfalls and challenges in automated tests. We know the questions that need to be asked, and the considerations that need to be made before starting. Some tests have a broad scope and there are latent needs that we can anticipate and make appropriate adjustments.
Turn-key Remote Monitoring
Endigit was working with a customer doing remote monitoring of building infrastructure. Our initial system was subject to harsher conditions than it was designed for and struggled with network connectivity. When our customer planned expansion to other sites we proposed a hardware solution that was suited for harsh conditions and used a cellular connection to ease installation and integration. We worked the solution completely, including:
- hardware selection
- drawings
- manufacture and assembly of the system
- software
- integration
Standardized Instrumentation
Another way we like to improve efficiency is to standardize a fleet of testers. A standard platform is different from a universal tester. A universal tester attempts to handle every possible connector and I/O. By doing this, each tester is overequipped with useless features (though they may be useful to test a different unit) and costs much more in hardware than it needs to. It also doesn’t allow for as much customization and thus limits functionality. A standard tester platform is built on common source code which lowers cost of development, but since it isn’t locked in, it can be customized to each unit under test. The hardware is modular in a standard system as well. That way, you purchase and include only the hardware that is necessary for this specific tester. This lowers hardware costs dramatically.
