Overview
1. Example: Testing the synchronization of multiple infotainment screen signals
Figure 1. The infotainment system and example test system consists of an NI PXIe-8135 controller, NI PXIe-1085 chassis, and five NI PXIe-1491 HDMI/DVI analyzers. Note that you can also test LVDS interfaces using PXI modules from NI Alliance partners.
Here is an example of automotive testing that requires a comprehensive, high-performance solution to ensure synchronization of multiple screens in an infotainment system. Human senses can detect slight lags between multiple screens and lip-sync delays between audio and video. Testing these aspects of a system continuously is very challenging. Test systems to detect these issues require multi-sync high-definition acquisition, synchronization, and automation capabilities.
The PXI test system consists of the following parts:
- NI PXIe-1085 Chassis
- NI PXIe-8135 controller
- NI PXIe-1491 HDMI and Mobile HD Analyzer—one for each multimedia link in the system under test
- (Optional) Alfamation VA-01 LVDS Analyzer - required if the interface is LVDS instead of DVI or HDMI
Each test requires putting the infotainment system on a specific output and having the PXI system automatically run the test. Lip sync is a consideration here.
Figure 2. A video event (white box) is followed by an audio event (single sound playback).
Using this type of structured content, the lag between audio and video can be automatically detected.
By automating the device under test, the infotainment system, a lip sync delay is generated as shown in Figure 2. The PXI test system then uses the NI PXIe-1491 to acquire the data stream and runs a lip sync test using NI Image Quality Analysis software to obtain milliseconds of audio-video lag.
Figure 3. You can use NI Image Quality Analysis software to test lip sync, analyze image quality using measurements such as the Structural Similarity Index (SSIM), and test multiscreen synchronization using user-defined processors.
Major infotainment system manufacturers are now realizing the growing importance of automation for these applications, as the complexity and frequency of testing entire infotainment systems are increasing. Without automation, fully testing an infotainment system can take weeks and many man-hours. A software team might be able to compile a new software stack for an infotainment system every two to three weeks, but it would be impossible for a company to conduct comprehensive testing that frequently due to the resources required. An automated infotainment test system can complete testing that previously took weeks in a matter of hours. As a result, companies can test each software stack as soon as it is compiled, rather than waiting for months. In addition, because the system can be easily replicated and adapted, the testing process for different software stacks can be executed in parallel, whether for high-pressure development or high-throughput production testing.
Previous article:Envelope Tracking Basic Principles and Test Solutions
Next article:Configuring a Software-Defined WLAN Test System
- Popular Resources
- Popular amplifiers
- From probes to power supplies, Tektronix is leading the way in comprehensive innovation in power electronics testing
- Seizing the Opportunities in the Chinese Application Market: NI's Challenges and Answers
- Tektronix Launches Breakthrough Power Measurement Tools to Accelerate Innovation as Global Electrification Accelerates
- Not all oscilloscopes are created equal: Why ADCs and low noise floor matter
- Enable TekHSI high-speed interface function to accelerate the remote transmission of waveform data
- How to measure the quality of soft start thyristor
- How to use a multimeter to judge whether a soft starter is good or bad
- What are the advantages and disadvantages of non-contact temperature sensors?
- In what situations are non-contact temperature sensors widely used?
- LED chemical incompatibility test to see which chemicals LEDs can be used with
- Application of ARM9 hardware coprocessor on WinCE embedded motherboard
- What are the key points for selecting rotor flowmeter?
- LM317 high power charger circuit
- A brief analysis of Embest's application and development of embedded medical devices
- Single-phase RC protection circuit
- stm32 PVD programmable voltage monitor
- Introduction and measurement of edge trigger and level trigger of 51 single chip microcomputer
- Improved design of Linux system software shell protection technology
- What to do if the ABB robot protection device stops
- Analysis of the application of several common contact parts in high-voltage connectors of new energy vehicles
- Wiring harness durability test and contact voltage drop test method
- From probes to power supplies, Tektronix is leading the way in comprehensive innovation in power electronics testing
- From probes to power supplies, Tektronix is leading the way in comprehensive innovation in power electronics testing
- Sn-doped CuO nanostructure-based ethanol gas sensor for real-time drunk driving detection in vehicles
- Design considerations for automotive battery wiring harness
- Do you know all the various motors commonly used in automotive electronics?
- What are the functions of the Internet of Vehicles? What are the uses and benefits of the Internet of Vehicles?
- Power Inverter - A critical safety system for electric vehicles
- Analysis of the information security mechanism of AUTOSAR, the automotive embedded software framework
- How to get a multi-channel reference power supply
- TMS320F28335GPIO Example - Light up the LED
- Analysis of 2020 E-sports Contest C: The realization process of the 99-point ramp car
- MSP430F4152 development board schematic diagram
- ON Semiconductor - FOD83xx/T series is coming! Answer the questions to win prizes and apply for free samples
- #Power supply roadblock#Experience sharing summary
- Programming example of msp430 keypress
- Are there any recommended books for beginners in circuit development?
- MSP430 G2553 Launchpad implements capacitance measurement
- [GD32L233C-START Review] 12. Button - External Interrupt