Feature: T&M


Modern automotive electronics can be real-world tested with the right equipment


By Raphael Grech, Technical Strategist, Position Navigation Timing, Spirent Communications T


raditionally, testing of new automotive sensors is conducted at predetermined stages or at the end of the design process.


However, the proliferation of sensors and the increasing complexity of sensor fusion software demand a shift to continuous testing, verification and validation. Here, using the right tools and development methods will shorten time to market, save money by avoiding expensive road testing and, ultimately, deliver a product that meets or exceeds expectations.


Automotive electronics complexities A new approach to vehicle electronics design is needed as systems and operating environments grow ever more complex. Inside the vehicle, systems and subsystems are proliferating as manufacturers respond to demands for added functionalities – from infotainment and environmental controls to navigation and assisted


26 June 2023 www.electronicsworld.co.uk


driving. We are seeing a proliferation of inputs throughout the vehicle, which must be collected, processed, interpreted and combined to create the best driving conditions and vehicle performance. But even though all these electronic


systems will improve driving and comfort, there’s an underlying problem that it’s just now beginning to surface – that of these components interacting in unexpected ways, potentially causing loss of performance and even failure. Complex systems are also more vulnerable to cybersecurity threats as attackers use external signals including GNSS, Wi-Fi, radar and V2X to implant malware. In such a complex ecosystem of


diverse components, it becomes increasingly difficult to test in a way that ensures thoroughness, repeatability and transparency whilst achieving cost efficiency, flexibility and long-term adaptability. To address this problem, automotive


electronics engineers need a new approach to testing.


Not the sum of its parts A common assumption in design and engineering is that the system as a whole will function as expected based on the aggregate performance of its components; sadly, practice shows otherwise. Components must coexist on a shared


communication system, leading to potential problems with out-of-band interference, power draw and confl icting sensor outputs. On the soſt ware side, components


must function in harmony to avoid everything from signal collision and system overloads to data corruption and security breaches. Soſt ware developed in a fi xed, programmatic fashion is prone to failure and post-delivery patching, a problem that led soſt ware engineers to develop a new, more fl exible way of working, a methodology which recognises that complexity itself is becoming a design constraint. Agile methodology – popularised


over 20 years ago and now widely used in the development of complex soſt ware applications – is a continuous process that involves breaking a project into phases.


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44