Home > On-Demand Archives > Q&A Sessions >
Live Q&A - Running Up That HIL: A Guide to Starting with HIL
Ander Galisteo - Watch Now - Duration: 20:38
Thanks for your nice comment! Yes, sometimes we focus too much on the technical details and forget the overall picture; HIL is done to reduce costs and/or make our lives easier. We should always focus on how to obtain maximum benefit with minimum effort. How much is the overall overhead of having a REST-API infrastructure for the tests?
This question I cannot answer right now, Ander. It is still a fresh started project and we have to learn. The test adapter runs an embedded Linux as REST-API server, performing the initiated actions. One interesting point here is the possible remote access, allowing automated tests from an other location. An other advantage is the hardware independent control interface,
10:42:47 From BobF : I think there's some overlap with 'virtual-twin' as well. For photo-typing when the required product (that is to be controlled) is not yet available, to commence controller elements but with HIL available. However, to fully emulate an end-product, this must quickly become immensely difficult. Any thoughts? 10:48:05 From BobF : I think Michael's talk has covered this! 10:48:39 From Michael Kirkhart : Yes, I believe so. 10:48:58 From BobF : HIL is hardware based, as we know! 10:49:34 From Michael Kirkhart : Someone once said "All models are wrong, but some are useful". 10:51:40 From BobF : Reacted to "Someone once said ..." with 👍 10:52:35 From Stephane to Ander Galisteo(Direct Message) : Thank you very much, Ander!
Your talk contains real interesting view points, Ander. The testing costs are often underestimated. Testing early, automatically and continuously improves the product quality and reduces the overall costs. Especially duration tests bring up some issues as well and should be an important part. In our company, for internal usage, we started with a REST-API controlled test adapter for remote testing new firmware images.