Vehicle-mounted Ethernet test system

Abstract

The utility model relates to the technical field of Internet of Vehicles, and discloses a vehicle-mounted Ethernet test system, which comprises a tested device, a test environment box, a test frame, an opposite terminal device, a test controller, a power supply and a CAN signal generator, the tested device is arranged in the test environment box, the opposite terminal device is arranged on the test frame, the test controller is arranged on the test frame, and the CAN signal generator is arranged on the test frame. The test controller is respectively connected with the tested device and the opposite terminal device, the power supply is respectively connected with the test controller, the tested device and the opposite terminal device, and the CAN signal generator is respectively connected with the test controller and the tested device. According to the utility model, the link time of the tested equipment can be comprehensively and accurately tested under different test conditions and different test environments, so that the tested equipment is ensured to meet performance requirements; meanwhile, the stability of the link establishment process can be ensured, and the reliability of the whole test system is improved.

Description

Technical Field

[0001] This utility model relates to the field of vehicle networking technology, specifically to an in-vehicle Ethernet testing system. Background Technology

[0002] Automotive Ethernet can be categorized by speed into 100Mbps automotive Ethernet (100BASE-T1) and Gigabit automotive Ethernet (1000BASE-T1). In automotive and industrial Ethernet applications, the 100BASE-T1 and 1000BASE-T1 standards provide efficient single-pair twisted-pair cable communication. Link time is a crucial metric for measuring link establishment speed under these standards, directly impacting the real-time performance and reliability of the automotive Ethernet system.

[0003] Existing automotive Ethernet T1 link testing methods struggle to accurately measure the connection time of the device under test (DUT) in a T1 link, especially for applications that require fast and reliable connection establishment in harsh environments. This inaccurate testing can negatively impact the performance of the DUT; for example, excessively long connection times for the DUT can lead to low data transmission efficiency in the entire automotive Ethernet system. Utility Model Content

[0004] The present invention aims to at least solve the technical problem in the prior art that it is difficult to accurately measure the connection time of the device under test in a T1 link, which affects the performance of the device under test.

[0005] To address the aforementioned technical problems, this utility model provides an in-vehicle Ethernet testing system, including a device under test (DUT), a test environment box, a test rack, a peer device, a test controller, a power supply, and a CAN signal generator. The DUT is housed within the test environment box, and the peer device is housed on the test rack. The test controller is connected to both the DUT and the peer device. The power supply is connected to the test controller, the DUT, and the peer device. The CAN signal generator is connected to both the test controller and the DUT.

[0006] After the test controller powers on the device under test (DUT) or the peer device, it tests the connection time between the DUT and the peer device based on the environment inside the test environment box; or the test controller sends a wake-up signal to the DUT through the CAN signal generator, and after the DUT is woken up, it tests the connection time between the DUT and the peer device based on the environment inside the test environment box.

[0007] In some embodiments, the test controller is connected to the test environment box via a USB interface, thereby connecting to the device under test; the test controller is connected to the peer device via a network port.

[0008] In some embodiments, the vehicle-mounted Ethernet test system further includes a BOB box, which has an on / off switch and is connected between the power supply and the device under test, or the BOB box is connected between the power supply and the peer device.

[0009] In some embodiments, the test environment chamber is equipped with at least one environmental sensor, which includes at least one of a temperature sensor, a humidity sensor, and an EMI sensor.

[0010] In some embodiments, the peer device includes a microcontroller and a physical layer, wherein the power supply of the microcontroller and the power supply of the physical layer are switched together.

[0011] In some embodiments, the peer device further includes a filter disposed between the link interface of the peer device and the physical layer.

[0012] In some embodiments, the device under test is a switch, and each link between the device under test and the peer device is tested separately.

[0013] In some embodiments, the test controller includes a link status detection module, which is configured to poll the status register of the peer device to detect the link status between the device under test and the peer device; and when the link status is detected to be active, determine that the device under test and the peer device have established a link.

[0014] In some embodiments, the test controller includes a link time evaluation module, which is configured to:

[0015] The link performance of the device under test is evaluated based on the link time; and / or

[0016] The time variation during the link establishment process between the tested device and the peer device is evaluated based on the link time.

[0017] In some embodiments, the link time used for the evaluation includes at least one of the average link time, the shortest link time, and the longest link time.

[0018] The vehicle-mounted Ethernet testing system provided in this embodiment of the utility model includes a device under test (DUT), a test environment box, a test rack, a peer device, a test controller, a power supply, and a CAN signal generator. The DUT is located inside the test environment box, and the peer device is located on the test rack. The test controller is connected to both the DUT and the peer device. The power supply is connected to the test controller, the DUT, and the peer device. The CAN signal generator is connected to both the test controller and the DUT. After the test controller powers on either the DUT or the peer device, it tests the connection time between the DUT and the peer device based on the environment within the test environment box. Alternatively, the test controller sends a wake-up signal to the DUT via the CAN signal generator. After the device under test (DUT) is activated, the connection time between the DUT and the peer device is tested according to the environment inside the test environment box to determine whether the connection time meets the requirements, thereby testing the performance of the DUT. This allows for comprehensive and accurate testing of the connection time of the DUT under different test conditions and environments, ensuring that the DUT meets performance requirements. Furthermore, the test system of this embodiment can automate test steps, reducing human error and further improving test accuracy. In addition, placing the DUT inside the test environment box and fixing the peer device on the test rack ensures the stability of the link establishment process, improves the reliability of the entire test system, and allows for accurate test results in a relatively relaxed test environment, eliminating the need for stringent test conditions, making testing convenient and quick. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this utility model or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this utility model. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a first test block diagram of the vehicle-mounted Ethernet test system according to an embodiment of the present utility model (the peer device is powered on);

[0021] Figure 2 This is a first test block diagram of the vehicle-mounted Ethernet test system according to an embodiment of the present invention (with the device under test powered on);

[0022] Figure 3 This is the first test block diagram of the vehicle-mounted Ethernet test system according to an embodiment of the present invention (with the device under test powered on). Detailed Implementation

[0023] Various embodiments and features of this utility model are described herein with reference to the accompanying drawings.

[0024] It should be understood that various modifications can be made to the embodiments described herein. Therefore, the above description should not be considered as limiting, but merely as an example of embodiments. Other modifications within the scope and spirit of this invention will be apparent to those skilled in the art.

[0025] The accompanying drawings, which are included in and form part of this specification, illustrate embodiments of the present invention and, together with the general description of the present invention given above and the detailed description of the embodiments given below, serve to explain the principles of the present invention.

[0026] These and other features of the present invention will become apparent from the following description of preferred forms of embodiments given as non-limiting examples, with reference to the accompanying drawings.

[0027] It should also be understood that although the present invention has been described with reference to some specific examples, those skilled in the art can certainly implement many other equivalent forms of the present invention, which have the features described in the claims and are therefore all within the scope of protection defined herein.

[0028] The above and other aspects, features and advantages of the present invention will become more apparent when taken in conjunction with the accompanying drawings and in view of the following detailed description.

[0029] Specific embodiments of the present invention will now be described with reference to the accompanying drawings; however, it should be understood that the claimed embodiments are merely examples of the present invention, which may be implemented in various ways. Well-known and / or repeated functions and structures have not been described in detail to avoid unnecessary or redundant details that could obscure the present invention. Therefore, the specific structural and functional details claimed herein are not intended to be limiting, but merely to serve as the basis and representative basis for the claims to teach those skilled in the art to use the present invention in a variety of substantially any suitable detailed structures.

[0030] This specification may use the phrases “in one embodiment,” “in another embodiment,” “in yet another embodiment,” or “in other embodiments,” all of which may refer to one or more of the same or different embodiments according to the present invention.

[0031] First, let's briefly describe the relevant terminology for automotive Ethernet:

[0032] 1. 100BASE-T1 and 1000BASE-T1 standards

[0033] • Definition: 100BASE-T1 and 1000BASE-T1 are standards designed for automotive and industrial Ethernet applications, optimizing the communication performance of a single pair of twisted-pair cables.

[0034] Features: Supports high-speed data transmission while reducing cost and complexity.

[0035] Applications: Widely used in automotive safety systems, in-vehicle networks, and other industrial applications requiring real-time communication.

[0036] 2. Linking process

[0037] • Initialization: When the device is powered on or restarted, the Physical Layer (Phy) enters the initialization state and sends an initialization sequence.

[0038] • Link detection: Sends special signal patterns to detect the existence of a physical connection.

[0039] • Capability negotiation: Exchange device capability information, such as supported speeds and duplex modes.

[0040] • Automatic negotiation: Determines the optimal link configuration.

[0041] • Link stability: Once negotiation is complete, the link enters a stable state, and data transmission begins.

[0042] • Continuous monitoring: Monitor the link status and restart the link process if problems occur.

[0043] 3. The Importance of Link Time

[0044] • Fast response: Reduced startup latency, suitable for real-time applications.

[0045] • Reliability ensures the consistency of data transmission.

[0046] • Energy saving: Reduce energy consumption, especially for battery-powered devices.

[0047] • System Integration: Simplify the system integration process for multiple devices working together.

[0048] • User experience: Improve user satisfaction.

[0049] As can be seen from the above, link time is very important for in-vehicle Ethernet systems. In view of this, this utility model provides an in-vehicle Ethernet testing system that can accurately measure the link time of the device under test in the link, ensuring that the device under test meets the performance requirements of the in-vehicle Ethernet system.

[0050] Figures 1 to 3 A schematic diagram of the structure of the vehicle-mounted Ethernet testing system provided in an embodiment of this utility model is shown. Figures 1 to 3 As shown in the figure, this utility model embodiment provides an in-vehicle Ethernet test system, including a device under test (DUT) 1, a test environment box 2, a test rack 3, a peer device 4, a test controller 5, a power supply 6, and a CAN signal generator 7. The DUT 1 is disposed in the test environment box 2, and the peer device 4 is disposed in the test rack 3. The test controller 5 is connected to both the DUT 1 and the peer device 4. The power supply 6 is connected to the test controller 5, the DUT 1, and the peer device 4. The CAN signal generator 7 is connected to both the test controller 5 and the DUT 1.

[0051] After the test controller 5 powers on either the device under test (DUT) 1 or the peer device 4, it tests the connection time between DUT 1 and the peer device 4 based on the environment inside the test environment box 2; or the test controller 5 sends a wake-up signal to DUT 1 through the CAN signal generator 7, and after DUT 1 is woken up, it tests the connection time between DUT 1 and the peer device 4 based on the environment inside the test environment box 2.

[0052] The test controller 5 controls the testing process of the device under test (DUT) 1. The test controller 5 can be a desktop computer (PC), server, tablet computer, digital TV, or other terminal device. DUT 1 has at least one connection interface, and the peer device 4 also has at least one connection interface to establish a connection with DUT 1. The test environment box 2 provides the testing environment for DUT testing. The power supply 6 supplies power to the test controller 5, DUT 1, and peer device 4. The test controller 5 can control the power supply 6 and the power supply to DUT 1 or peer device 4 to test the connection time of DUT 1 under different test conditions (trigger conditions) (DUT 1 powered on or peer device 4 powered on). The connection time is the time required for DUT 1 to establish a connection with peer device 4.

[0053] The CAN signal generator 7, connected between the test controller 5 and the device under test 1, can test the connection time of the device under test 1 under another test condition (the device under test 1 is awake).

[0054] By testing the connection time of device under test (DUT) 1, it can be determined whether the connection time meets the requirements. If the connection time does not meet the performance requirements of DUT 1, adjustments can be made to ensure the reliable operation of the vehicle Ethernet system connected to DUT 1. For example, the connection time of DUT 1 can be accelerated, startup delay reduced, the response speed of the vehicle Ethernet system improved, and the overall efficiency of the vehicle Ethernet system enhanced.

[0055] The vehicle-mounted Ethernet testing system provided in this embodiment of the utility model includes a device under test (DUT) 1, a test environment box 2, a test rack 3, a peer device 4, a test controller 5, a power supply 6, and a CAN signal generator 7. The DUT 1 is located inside the test environment box 2, and the peer device 4 is located on the test rack 3. The test controller 5 is connected to both the DUT 1 and the peer device 4. The power supply 6 is connected to the test controller 5, the DUT 1, and the peer device 4. The CAN signal generator 7 is connected to both the test controller 5 and the DUT 1. After the test controller 5 powers on either the DUT 1 or the peer device 4, it tests the connection time between the DUT 1 and the peer device 4 based on the environment inside the test environment box 2; or the test controller 5 sends a signal to the DUT through the CAN signal generator 7. 1. A wake-up signal is sent. After the device under test (DUT) 1 is woken up, the connection time between DUT 1 and the peer device 4 is tested according to the environment inside the test environment box 2 to determine whether the connection time meets the requirements. This allows for comprehensive and accurate testing of the connection time of DUT 1 under different test conditions and environments, ensuring that DUT 1 meets performance requirements. Furthermore, the test system of this embodiment can automate test steps, reducing human error and further improving test accuracy. Additionally, placing DUT 1 inside the test environment box 2 and fixing the peer device 4 on the test rack 3 ensures the stability of the link establishment process, improves the reliability of the entire test system, and allows for accurate test results in a relatively relaxed test environment, eliminating the need for stringent test conditions, making testing convenient and quick.

[0056] It should be noted that, as Figure 1 and Figure 2 As shown, when testing is not required after the device under test 1 is woken up, there is no need to set up the CAN signal generator 7.

[0057] In some embodiments, the test controller 5 is connected to the test environment box 2 via a USB interface, thereby connecting to the device under test 1; the test controller 5 is connected to the peer device 4 via a network port.

[0058] The test environment box 2 may include an environment controller. After the test controller 5 is connected to the test environment box 2 via a USB interface, the test controller 5 can control and adjust the test environment inside the test environment box 2. At the same time, since the device under test 1 is located inside the test environment box 2, the device under test 1 can be connected to the environment controller, thereby connecting to the test controller 5 via the USB interface on the test environment box 2 and / or the test controller 5, reducing the number of connection lines.

[0059] In other embodiments, the test controller 5 is connected to the test environment box 2 via a USB interface. The test controller 5 can also be directly connected to the device under test 1 via a wireless connection; however, a wireless connection may interfere with the test environment and affect the test results. Therefore, in this embodiment, the device under test 1 is preferably connected to the environment controller, and then connected to the test controller 5 via the environment controller and the USB interface.

[0060] In some embodiments, as Figure 1 and Figure 2 As shown, the vehicle-mounted Ethernet test system also includes a BOB (Booster Buck) box 8, which is equipped with an on / off switch. The BOB box 8 is connected between the power supply 6 and the device under test 1, or the BOB box 8 is connected between the power supply 6 and the peer device 4.

[0061] like Figure 2 As shown, the BOB box 8 is connected between the power supply 6 and the device under test 1, and the BOB box 8 is also connected to the test controller 5. The test controller 5 can control the on / off state of the switch inside the BOB box 8, thereby controlling the power supply to the device under test 1; as shown Figure 1 As shown, the BOB box 8 is connected between the power supply 6 and the peer device 4, and the BOB box 8 is also connected to the test controller 5. The test controller 5 can control the on / off state of the switch inside the BOB box 8, thereby controlling the power supply to the peer device 4. The BOB box 8 is preferably connected to the test controller 5 via a USB interface for easy connection.

[0062] Power supply 6 is preferably a programmable power supply. Programmable power supplies are controlled by computers or other automated equipment, which can realize program control of the output current and voltage of the power supply, thereby achieving precise control; moreover, the output voltage and current range of programmable power supplies are wide and can be adjusted arbitrarily as needed.

[0063] In some embodiments, the test environment chamber 2 is equipped with at least one environmental sensor, including at least one of a temperature sensor, a humidity sensor, and an EMI (Electromagnetic Interference) sensor. The environmental sensor can be connected to the environmental controller of the test environment chamber 2 to monitor the environmental information within the chamber in real time, and transmit this information to the test controller 5. The test controller 5 then adjusts the test environment based on the environmental information. Table 1 shows the test environment configuration of the device under test (DUT) within the test environment chamber 2.

[0064] Table 1. DTU Test Environment Configuration Table

[0065]

[0066]

[0067] When testing the device under test 1 using the test environment box 2, first ensure that the test environment box 2 is in a stable state. Then, set the test environment box according to the test environment selected in Table 1 above, put the device under test 1 of the T1 link into the test environment box 2, and ensure that the test environment in the test environment box 2 reaches the set value (i.e., ensure that the test environment is stable). Then, measure the connection time of the device under test 1 under different test conditions.

[0068] In some embodiments, as Figures 1 to 3 As shown, the peer device 4 includes a microcontroller (μC) and a physical layer (Phy), and the power supply of the microcontroller and the power supply of the physical layer are switched together.

[0069] The microcontroller and the physical layer's Ethernet interface are respectively connected to power supply 6, so that their power supplies switch together to ensure test reliability.

[0070] In some embodiments, as Figures 1 to 3 As shown, the peer device 4 also includes a filter, which is disposed between the link interface of the peer device 4 and the physical layer, so as to filter the signal received by the peer device 4 during the link test between the device under test 1 and the peer device 4, thereby measuring the link time of the device under test 1 more accurately.

[0071] In some embodiments, the device under test 1 is a switch, and each link between the device under test 1 and the peer device 4 is tested separately. When the device under test 1 is a switch, all the link interfaces of the switch need to be tested individually to achieve comprehensive testing of the link interfaces of the device under test 1, facilitating its subsequent use.

[0072] In some embodiments, the test controller 5 includes a link status detection module, which is configured to poll the status register of the peer device 4 to detect the link status between the device under test 1 and the peer device 4; and when the link status is detected to be active, it determines that the device under test 1 and the peer device 4 have established a link.

[0073] The link status detection module can poll the status register of the peer device 4 during the link establishment process between the device under test (DUT) 1 and the peer device 4 to detect the link status. If the link status changes to active, it confirms that the connection has been established. The time period from the start of the link status detection module to the link status changing to active is the link time t between the device under test 1 and the peer device 4. up .

[0074] In some embodiments, the test controller 5 includes a link time evaluation module, which is configured to:

[0075] The link performance of the device under test 1 is evaluated based on the link time; and / or

[0076] The time variation during the link establishment process between the tested device 1 and the peer device 4 is evaluated based on the link time.

[0077] The link time evaluation module can evaluate the link time based on the measured link time t. up Determine whether the device under test 1 and the peer device 4 establish a connection within a preset time. If so, determine that the connection performance of the device under test 1 is qualified. If it exceeds the preset time, determine that the connection performance of the device under test 1 is poor and needs to be optimized.

[0078] In this embodiment, multiple link times t can be obtained through repeated measurements. up This is to avoid inaccurate measurement results caused by a single measurement.

[0079] After multiple measurements, the link performance of the device under test 1 can be evaluated based on at least one of the average link time, the shortest link time, and the longest link time.

[0080] If multiple link times fall within the aforementioned preset time, then each link time is evaluated and judged, that is, the time change during the link establishment process is evaluated, and it is judged whether the link time has a large time change. If it does, it is determined that the link time fluctuates greatly and the link stability and reliability are poor; if the link time fluctuates little, the link stability and reliability are good.

[0081] Link time fluctuations include large differences between a specific link time and the average link time, large differences between the shortest and longest link times, and large differences between two adjacent link times.

[0082] The following section provides a detailed explanation of the testing process and link time evaluation process of the test system under different testing conditions.

[0083] Example 1

[0084] like Figure 1 As shown, the test condition is that the peer device 4 is powered on.

[0085] (1) Test Overview:

[0086] This test aims to ensure that the device under test (DUT) 1 establishes a link within a preset time after the peer device 4 is powered on, without significant variations in link time. In other words, the test objective is to successfully establish a link within the preset time frame and to evaluate the time variations during link establishment.

[0087] (2) Prerequisites:

[0088] 1) The device under test 1 is connected to a stable power supply 6.

[0089] 2) The device under test 1 is in normal operating mode.

[0090] 3) The test system needs to provide special wake-up conditions for the device under test 1, such as a wake-up line or a network management CAN message.

[0091] 4) If the device under test 1 is a switch, then all links must be tested individually.

[0092] 5) The test system needs to provide the average startup time of the connected peer device 4.

[0093] (3) Test settings:

[0094] 1) Connect the device under test 1 to the peer device 4 using the appropriate master / slave configuration, and ensure that the polarity of the communication channel is correct.

[0095] 2) The power supply of the device under test 1 should be controlled by the test controller 5 of the test system.

[0096] (4) Test steps:

[0097] 1) Ensure that the device under test 1 is active and ready to establish a link.

[0098] 2) Turn on the power to the connected peer device 4 and record the start time t. start .

[0099] 3) Continuously poll the status register of the linked peer device 4 until the link status is detected to be active, and record the time t. stop .

[0100] 4) Calculate the link time t from power-on to link establishment. up , i.e. t up =t stop -t start .

[0101] 5) Turn off the power to the peer device 4 of the link.

[0102] 6) Repeat the above steps multiple times to obtain multiple link times t. up And perform the following calculations:

[0103] a. Calculate the average time The t obtained from multiple measurements up After adding the values, divide by the number of measurements n.

[0104] b. Calculate the standard deviation σ of the link time. t First, calculate t for each measurement. up With average time The square of the difference between the measurements is calculated, then these squared values ​​are added together, divided by the number of measurements minus one (n-1), and finally the square root is taken.

[0105] c. Determine the shortest time t min and the longest time t max That is, t in multiple measurements up The minimum and maximum values.

[0106] (5) Evaluation criteria:

[0107] 1) Standard deviation σ t It should be less than or equal to 50 milliseconds, i.e., σ t ≤50ms.

[0108] 2) Shortest time t min It should be greater than 10 milliseconds plus the average startup time of the peer device 4. Right now

[0109] 2) Longest time t max It should be less than 100 milliseconds plus the average startup time t of the peer device 4. ready1 , i.e. t max <100ms+t ready1 .

[0110] (6) Remarks:

[0111] 1) The test system should switch the power supply of the microcontroller (μC) and the physical layer (Phy) of the peer device 4 together, according to the design of the peer device 4.

[0112] 2) If the device under test 1 contains a switch, then test each port (link interface) of the device under test 1.

[0113] 3) Execute the test environments (environments 1 to 10) listed in Table 1 above.

[0114] Example 2

[0115] like Figure 2 As shown, the test condition is that the device under test 1 is powered on.

[0116] (1) Test Overview:

[0117] This test aims to ensure that the device under test (DUT) 1 establishes a link within a preset time after power-on, without significant variations in link time. In other words, the test objective is to successfully establish a link within the preset time frame and to evaluate the time variations during link establishment.

[0118] (2) Prerequisites:

[0119] 1) The peer device 4 for linking needs to be connected to a stable power supply 6.

[0120] 2) The test system needs to provide special wake-up conditions for the device under test 1, such as a wake-up line or network management CAN message.

[0121] 3) The test system needs to provide the average startup time t of the device under test 1. ready2 .

[0122] (3) Test settings:

[0123] 1) Connect the device under test 1 to the peer device 4 using the appropriate master / slave configuration, and ensure that the polarity of the communication channel is correct.

[0124] 2) The power supply of the device under test 1 should be controlled by the test controller 5 of the test system.

[0125] (4) Test steps:

[0126] 1) Ensure that the device under test 1 is active and ready to establish a link.

[0127] 2) Turn on the power to the device under test 1 and record the start time t. start .

[0128] 3) Continuously poll the status register of the linked peer device 4 until the link status is detected to be active, and record the time t. stop .

[0129] 4) Calculate the link time t from power-on to link establishment. up , i.e. t up =t stop -t start .

[0130] 5) Turn off the power to the device under test 1.

[0131] 6) Repeat the above steps multiple times to obtain multiple link times t. up And perform the following calculations:

[0132] a. Calculate the average time The t obtained from multiple measurementsup After adding the values, divide by the number of measurements n.

[0133] b. Calculate the standard deviation σ of the link time. t First, calculate t for each measurement. up With average time The square of the difference between the measurements is calculated, then these squared values ​​are added together, divided by the number of measurements minus one (n-1), and finally the square root is taken.

[0134] c. Determine the shortest time t min and the longest time t max That is, t in multiple measurements up The minimum and maximum values.

[0135] (5) Evaluation criteria:

[0136] 1) Standard deviation σ t It should be less than or equal to 50 milliseconds, i.e., σ t ≤50ms.

[0137] 2) Shortest time t min It should be greater than 10 milliseconds plus the average startup time of device 1 under test. Right now

[0138] 2) Longest time t max It should be less than 100 milliseconds plus the average startup time of device 1 under test. Right now

[0139] (6) Remarks:

[0140] 1) If the device under test 1 contains a switch, then test each port (link interface) of the device under test 1.

[0141] 2) Execute the test environments (environments 1 to 10) listed in Table 1 above.

[0142] Example 3

[0143] like Figure 3 As shown, the test condition is that the device under test 1 is woken up.

[0144] (1) Test Overview:

[0145] This test aims to ensure that device 1 under test establishes a connection within a preset time after being woken up, without significant variations in connection time. The test objective is to successfully establish a connection within the preset time range and to evaluate the time variations during the connection establishment process.

[0146] (2) Prerequisites:

[0147] 1) The device under test 1 and the connected peer device 4 need to be connected to a stable power supply 6.

[0148] 2) The device under test 1 is in normal operating mode.

[0149] 3) The test system needs to provide special wake-up conditions for the device under test 1, such as a wake-up line or a network management CAN message.

[0150] 4) The test system needs to provide the current consumption I of the device under test 1 in sleep mode. sleep .

[0151] 5) The test system must provide the average wake-up time of the device under test (DUT) 1.

[0152] (3) Test settings:

[0153] 1) Connect the device under test 1 to the peer device 4 using the appropriate master / slave configuration, and ensure that the polarity of the communication channel is correct.

[0154] 2) The power supply of the device under test 1 should be controlled by the test controller 5 of the test system.

[0155] (4) Test steps:

[0156] 1) Ensure that the device under test 1 is in sleep mode and the peer device 4 is active and ready to establish a connection.

[0157] 2) Turn on the wake-up signal of the device under test 1.

[0158] 3) When the current consumption I of the device under test 1 DUT Current consumption I greater than in sleep mode sleep At that time, record the wake-up time t. start .

[0159] 4) Continuously poll the status register of the linked peer device 4 until the link status is detected to be active, and record the time t. stop .

[0160] 5) Calculate the connection time t from wake-up to connection establishment. up , i.e. t up =t stop -t start .

[0161] 6) Switch the device under test 1 back to sleep mode.

[0162] 7) Repeat the above steps multiple times to obtain multiple link times t. up And perform the following calculations:

[0163] a. Calculate the average time The t obtained from multiple measurements up After adding the values, divide by the number of measurements n.

[0164] b. Calculate the standard deviation σ of the link time. t First, calculate t for each measurement. up With average time The square of the difference between the measurements is calculated, then these squared values ​​are added together, divided by the number of measurements minus one (n-1), and finally the square root is taken.

[0165] c. Determine the shortest time t min and the longest time t max That is, t in multiple measurements up The minimum and maximum values.

[0166] (5) Evaluation criteria:

[0167] 1) Standard deviation σ t It should be less than or equal to 50 milliseconds, i.e., σ t ≤50ms.

[0168] 2) Shortest time t min It should be greater than 10 milliseconds plus the average wake-up time t of the device under test 1. ready3 , i.e. t min ≥10ms+t ready3 .

[0169] 2) Longest time t max It should be less than 100 milliseconds plus the average wake-up time t of the device under test 1. ready3 , i.e. t max <100ms+t ready3 .

[0170] (6) Remarks:

[0171] 1) If the device under test 1 contains a switch, then test each port (link interface) of the device under test 1.

[0172] 2) Execute the test environments (environments 1 to 10) listed in Table 1 above.

[0173] The above description is merely a preferred embodiment of this utility model and an explanation of the techniques used. Those skilled in the art should understand that the scope of disclosure involved in this utility model is not limited to the technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in this utility model.

[0174] Furthermore, although the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. Multitasking and parallel processing may be advantageous in certain environments. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this invention. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0175] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A vehicle-mounted Ethernet testing system, characterized in that, The system includes a device under test (DUT), a test environment box, a test rack, a peer device, a test controller, a power supply, and a CAN signal generator. The DUT is housed in the test environment box, and the peer device is housed in the test rack. The test controller is connected to both the DUT and the peer device. The power supply is connected to the test controller, the DUT, and the peer device. The CAN signal generator is connected to both the test controller and the DUT. After the test controller powers on the device under test (DUT) or the peer device, it tests the connection time between the DUT and the peer device based on the environment inside the test environment box; or the test controller sends a wake-up signal to the DUT through the CAN signal generator, and after the DUT is woken up, it tests the connection time between the DUT and the peer device based on the environment inside the test environment box.

2. The vehicle-mounted Ethernet testing system according to claim 1, characterized in that, The test controller is connected to the test environment box via a USB interface, thereby connecting to the device under test; the test controller is connected to the peer device via a network port.

3. The vehicle-mounted Ethernet testing system according to claim 1, characterized in that, The vehicle-mounted Ethernet test system also includes a BOB box, which has an on / off switch. The BOB box is connected between the power supply and the device under test, or between the power supply and the peer device.

4. The vehicle-mounted Ethernet testing system according to claim 1, characterized in that, The test environment chamber is equipped with at least one environmental sensor, which includes at least one of a temperature sensor, a humidity sensor, and an EMI sensor.

5. The vehicle-mounted Ethernet testing system according to claim 1, characterized in that, The peer device includes a microcontroller and a physical layer, and the power supply of the microcontroller and the power supply of the physical layer are switched together.

6. The vehicle-mounted Ethernet testing system according to claim 5, characterized in that, The peer device also includes a filter, which is disposed between the link interface of the peer device and the physical layer.

7. The vehicle-mounted Ethernet testing system according to claim 1, characterized in that, The device under test is a switch, and each link between the device under test and the peer device is tested separately.

8. The vehicle-mounted Ethernet testing system according to claim 1, characterized in that, The test controller includes a link status detection module, which is configured to poll the status register of the peer device to detect the link status between the device under test and the peer device; and when the link status is detected to be active, it determines that the device under test and the peer device have established a link.

9. The vehicle-mounted Ethernet testing system according to claim 1, characterized in that, The test controller includes a link time evaluation module, which is configured as follows: The link performance of the device under test is evaluated based on the link time; and / or The time variation during the link establishment process between the tested device and the peer device is evaluated based on the link time.

10. The vehicle-mounted Ethernet testing system according to claim 9, characterized in that, The link time used for the evaluation includes at least one of the average link time, the shortest link time, and the longest link time.

Images