Member: HYUNDAI AUTRON
Featured Standard: ASAM XIL
Today, the automotive industry is already dealing with highly electrified and motorized vehicles. With the development of autonomous driving, additional complexity is added. The general rule is: The more complex the vehicle gets, the more Verification is needed at the development state. But vehicle testing requires a lot of manpower and time.
To keep the effort as low as possible, the importance of HIL (hardware-in-the-loop) Verification, which is simulating the environment, is increasing. In this study, a HIL automation Verification tool was developed based on the ASAM XIL framework API and applied to the Verification of the convenience/chassis domain using C# language. The study confirmed that a common test case can be created and a vendor-independent Verification environment can be developed.
We support ASAM XILbecause it enables vendor-independent operation of testing equipment. All, NI, dSPACE and ETAS Hardware and Software can be controlled.
BeomSeop Kim, Team Leader, Hyundai Autron
The Electronics Control Validation Team at Hyundai Autron has developed an in-house tool for application programming. The problem was that HILs system equipment manufacturers each have their proprietary system. There is not one standardized operating tool, but each company has its specific approach for each domain. Therefore, it is necessary to get familiar with each tool and prepare test case scenarios specific to each tool’s purpose.
ASAM XIL introduces the concept of a framework to run these tools even in heterogeneous tool environments without modifying the test case.
One great feature of our automated evaluation tool (mobilgene X Studio) is the ability to perform vendor independent testing. To this end, the ASAM XIL API was implemented based on the IFramework interface. ASAM XIL API provides C# and Python interfaces. Own automated evaluation tools developed with the application program are designed to operate based on C#, and use the ASAM XIL API version 2.1.0.
The HIL automation evaluation tool was developed based on the ASAM XIL framework API and applied to domain-specific Verification. This way, it was ensured that a test case can be created with a single evaluation tool and an evaluation environment can be established that is not dependent on tools and equipment of a specific vendors. But once the test environment is built, changing or extending this environment is difficult. As each vendor uses his own, proprietary tool and test case format, expanding the test environment usually requires products of the same vendor. This makes it difficult to cope with the rapidly changing demands of the test environment. In addition, there is a probability that the method of developing tests will be uniform when relying on the technology of one specific vendor. Dependence on one particular vendor is also a major burden at company level.
Own automated evaluation tools developed by an application program can solve these problems. The same applies to the test case: Test cases written with a proprietary technology complicates the change of the test environment. Depending on the test environment, all test cases may need to be migrated, and test authors must learn a new language and skills every time the environment changes. Therefore, as time passes and the number of test cases increases, it becomes more difficult to change the according environment. A self-developed automated evaluation tool solves this challenge by using C#, a general-purpose language that allows to perform tests on various tools or equipment without modifying the test case. The advantages of general-purpose languages, such as a thick user base and rich documents, will do the same for writing better tests.
The ASAM XIL API cannot only be used in HIL tests, but also in MIL (Model in the loop) or SIL (Software in the loop) testing environments. So far, we have checked the self-developed test automation tool only in HIL equipment, but it can be expected that it will work just as well and provide the same advantages in MIL or SIL environments. Ultimately, the cost of maintaining and validating test cases can be reduced.