MOST150: End-of-line testing for Quality Assurance
30 January 2013
Since the first generation of MOST networks in vehicles, the range of users is still growing, with the result that many different suppliers are developing electronic control units (ECU) providing a MOST interface.
Detailed compliance testing is required in order to eliminate faults and to ensure the correct behaviour of different MOST interfaces in the same network. By focusing on the challenge of testing, the PXI standard and simultaneous test philosophies have led to the development of the first PXI MOST150 interface.
Test systems must accurately simulate real environments
To test the functions of a MOST ECU, it must be installed in a realistic vehicle environment to provide the input and output information it needs to perform its control tasks. Therefore, the test system must accurately simulate the vehicle environment. In the majority of cases, an ECU with MOST interface has a number of different communication interfaces other than MOST that have to be supported. One reason could be that the ECU has to act as a gateway and/or system components are combined into one unit.
An important issue in managing the manufacturing and industrial environments is to consider the established standards used for the hardware that is simulating the MOST interface. Especially for hardware, the standards are restricted to interchangeable systems/components and to hardware set-ups that are easy to expand. An often-used standard for such measurement and simulation systems is the PXI bus. Using PXI takes advantage of a robust, PC-based, and high-performance measurement and automation system. With PXI, the benefits of low cost, performance, flexibility, and a wide range of available cards form the basis of a multiplicity of test systems. So clearly the MOST appropriate solution, where possible, is to use PXI cards to provide the MOST interface.
Among the technical facts to manage the tests of MOST communication and peripheral hardware conditions, some tests enforce simultaneous control of a quantity of DUTs (Device Under Test), e.g. reliability or long duration tests of several hours and days. To perform this method of testing, a modular structured system has to correlate with the abilities of the MOST networking architecture for the case of homogeneous DUTs.
System and Architecture
Basically the first step is to have a working PXI-based MOST150 interface, which can be part of any automated test system. GOEPEL introduced its first fully compliant MOST150 PXI6161 (oPhy) board some time ago. It follows the forerunner, PXI3060 (MOST25 oPhy), and is compliant to the current revision of the MOST specification.
The PXI6161 module is part of the well-established Series 61 product family, with a programmable communication controller that is supported by a PowerPC in combination with extensive on-board firmware. This relieves strain on the host PC, and valuable bandwidth for additional application is obtained, enabling complex and CPU-intensive processes to be executed on the board. Based on the INIC OS81110 and the corresponding SpyNIC, the PXI6161 is fully capable of generating and streaming MOST content. A number of additional functions are integrated, e.g. the ring break diagnosis (RBD), several trigger inputs and outputs, and the functionality for creating a parallel CAN/LIN. One module is able to be a master, a slave and/or a spy, and by using several modules in a PXI system the results are various unique MOST networks.
For implementation of test systems used for screening, end-of-line, and reliability, a mature architecture of hardware is proved. As requirements change, the modular architecture of the tester opens up the possibility of system upgrades covering a variety of communication interfaces. In addition to the obvious benefit of cost saving, the main thrust of this approach is in testing gateway functions between different communication networks. The ability of the PXI bus to trigger and synchronise its instruments is invaluable in establishing a common timing basis for these tests.
The modular hardware architecture enforces efficient software for organising all application tasks. The advantage of swapping out critical real-time communication processes to the hardware is that it allows the possibility of easy-to-use windows based user software. In a test sequencer including various communications and verifying routines, automated quality inspections can be defined.
Regarding previous MOST25 implementations using the PXI standard, the test departments of OEMs, suppliers and test houses are able to update their hardware resources with minimum effort.
Two philosophies exist on how to handle more than one MOST network, as there are different views on technical and economic efficiencies. The first and most obvious solution is to use every MOST network to test a unique communication partner, which results in a group of MOST modules. The benefits are strictly separated hardware resources and the benefit of using iterative software tasks, which only have to be addressed by the individual hardware module.
In addition, some test specifications require this philosophy of parallel networks, because it is clear, straightforward and provides some kind of redundancy. The only problem is a high degree of costs and hardware components. An alternative way of realising simultaneous testing is the substitution of several PXI boards through a MOST splitter, e.g. a hub for MOST as shown in figure 1.
This is a cost effective arrangement and allows a lot of basic tests. More difficult are the software tasks, the testing of the ring break diagnosis or the limited bandwidth caused by only one simulated interface. Another problem that exists belongs to the DUTs, because still a huge number of communication units are not able to perform dynamic addressing, with the consequence of multiple equal instance identifiers.
Image 1: Strategies for MOST PXI test systems
Contact Details and Archive...