A test method and apparatus for automotive combination switches
By synchronously collecting and associating multi-domain data from automotive combination switches, the problem of missing cross-domain correlation in existing testing methods is solved, and the accuracy and reliability of cross-domain anomaly localization are achieved.
Patent Information
- Application Number
- CN202611392296.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-08
- Publication Date
- 2026-11-10
AI Technical Summary
Existing automotive combination switch testing methods cannot effectively unify the correlation between mechanical action, contact changes, message updates, and load response, making it difficult to detect transient anomalies and lacking a cross-domain comprehensive analysis mechanism, which can easily lead to misjudgments.
By synchronously collecting mechanical, electrical, and communication status data of the automotive combination switch operating components, multi-domain events are extracted and linked into cross-domain event chains, which are then compared with preset event chains to determine the test results.
It enables unified analysis of multi-domain data within the same operation cycle, provides a basis for cross-domain anomaly localization, and avoids misjudgment due to lack of cross-domain evidence.
Smart Images

Figure CN123066548A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of testing, and in particular to a testing method and apparatus for automotive combination switches. Background Technology
[0002] Current automotive combination switch testing primarily includes manual function checks, automated operation by a fixed-stroke robotic arm, contact continuity testing, and communication testing via CAN or LIN messages read from a bus board. Firstly, mechanical positions, contact continuity, and bus messages are recorded separately. Each domain signal is stored and analyzed independently, lacking a unified correlation between signals from multiple domains generated in the same operation. This makes it impossible to attribute mechanical actions, contact changes, message updates, and load responses to the same operation cycle. Secondly, it typically only judges whether the final continuity state or the final message value meets expectations, lacking a mechanism to comprehensively judge the sequence, time intervals, and state correspondence between mechanical engagement events, initial contact changes, message state changes, and load response establishment. This makes it difficult to detect transient anomalies such as excessive contact bounce, delayed state transitions, short-term errors, and reversed event sequences. Summary of the Invention
[0003] The purpose of this invention is to provide a testing method and device for automotive combination switches, which can obtain complete mechanical-electrical-network-load multi-domain data within the same operating cycle, providing a data foundation for cross-domain comprehensive analysis. It unifies the state changes that were originally scattered in various domains into the same operation according to the operating component identification, target gear, change direction and state code, providing a basis for subsequent anomaly location and avoiding misjudgment of fault conclusions due to lack of cross-domain evidence.
[0004] To solve the above-mentioned technical problems, the present invention provides a testing method for automotive combination switches, comprising: Identify the operating components in the combination switch of the vehicle under test, wherein the operating components include at least one of the following: turn signal lever, light lever, wiper lever, knob, and button; The operating component is driven to move, and multi-domain data during the movement of the operating component is collected synchronously. The multi-domain data includes at least two of the following: mechanical status data, electrical status data, communication status data, and load response data. Multi-domain events are extracted from the multi-domain data, and the multi-domain events are associated as a cross-domain event chain according to the event attributes of the multi-domain events. The event attributes include at least one of the following: the identifier of the operating component, the target gear, the direction of state change, and the state code. The cross-domain event chain is compared with a preset event chain, and the test result of the vehicle combination switch under test is determined based on the comparison result.
[0005] On the other hand, before driving the operating component to move, it also includes: The installation information of the vehicle combination switch under test, the installation position of the operating component, and the connection relationship between the mechanical actuator and the operating component are obtained. The vehicle combination switch under test includes an operating component and a mechanical actuator, and the mechanical actuator is used to drive the operating component. Establish a test coordinate system corresponding to the combination switch of the vehicle under test based on the installation information; Based on the installation position of the operating component and the pose correspondence, the coordinate transformation relationship when the mechanical actuator drives the operating component to move is determined; The mechanical actuator is controlled to drive the operating component to move according to the coordinate transformation relationship.
[0006] On the other hand, before driving the operating component to move, it also includes: The mechanical actuator is controlled to drive the operating component to move in a low-load scanning mode. The low-load scanning is a process of gradually driving the operating component to move in a preset position increment or angle increment under the condition that the preset safety force or safety torque is not exceeded. During the low-load scanning process, position data, angle data, force data, and torque data of the operating component during its movement are collected. Based on the position data, angle data, force data, and torque data, at least one mechanical feature point corresponding to the operating component is determined. The mechanical feature point includes at least one of the following: initial contact point, peak feature point, over-gear feature point, holding feature area, and return feature point. The mechanical motion characteristic parameters of the operating component are determined based on the mechanical feature points; The operating component is driven to move based on the mechanical motion characteristic parameters.
[0007] On the other hand, determining the mechanical motion characteristic parameters of the operating component based on the mechanical feature points includes: The mechanical envelope of the target gear is determined based on the position range of the retaining feature area; The upper limit of the allowable force or the upper limit of the allowable torque are determined based on the force or torque value of the peak characteristic point; Determine the over-gear condition and the target position or target angle corresponding to the target gear based on the position or angle of the over-gear feature point. The holding conditions are determined based on the force range and position range of the holding feature area; The retraction conditions are determined based on the initial contact point and the return feature point. The permissible speed range is determined based on the range of travel or angle between the initial contact point and the overshoot feature point.
[0008] On the other hand, driving the operating component to move based on the aforementioned mechanical motion characteristic parameters includes: The control parameters of the mechanical actuator are determined based on the mechanical motion characteristic parameters, and the control parameters include at least one of motion position, motion angle, driving force, driving torque, motion speed, and holding time; Generate the test motion trajectory corresponding to the mechanical actuator based on the control parameters; The mechanical actuator is controlled to drive the operating component to perform the test action according to the test motion trajectory.
[0009] On the other hand, multi-domain data during the movement of the operating component is collected synchronously, including: Output synchronous clock signals to each acquisition channel; The time offset of the acquisition channel corresponding to the mechanical status data, electrical status data, communication status data, and load response data is determined based on the synchronous clock signal. Time correction is performed on the data acquired from different acquisition channels based on the time offset; The time correction formula is as follows: ; in, Let be the original time of the i-th channel. This is the clock frequency scaling correction factor for the i-th channel. Let be the fixed delay compensation amount for the i-th channel. The time after time correction for the i-th channel; The time-corrected mechanical status data, electrical status data, communication status data, and load response data are all mapped to the same time reference to serve as multi-domain data during the movement of the operating component.
[0010] On the other hand, extracting multi-domain events from the multi-domain data includes: Mechanical events are extracted from the mechanical state data, and the mechanical events include at least one of the following: initial contact event, mechanical over-gear event, mechanical gear-entry event, release event, and return-to-position completion event; Electrical events are extracted from the electrical state data, and the electrical events include at least one of the following: contact first change event, contact bounce end event, resistance value encoding stabilization event, and contact open event; The communication events are extracted from the communication status data, and the communication events include at least one of the following: target message arrival event, status signal change event, error frame event, and recovery message event; Load events are extracted from the load response data, and the load events include at least one of load start-up events, load status establishment events, and feedback stabilization events.
[0011] On the other hand, the multi-domain events are associated as a cross-domain event chain based on their event attributes, including: Based on at least one of the following: the identifier of the operating component, the target gear, the direction of state change, the state code, and the event occurrence time, the extracted mechanical event, electrical event, communication event, and load event are associated as the cross-domain event chain; Obtain a preset event chain, which is established in advance based on the normal test data of qualified samples; The cross-domain event chain is compared with a preset event chain, and the test result of the vehicle combination switch under test is determined based on the comparison result, including: Compare the cross-domain event chain with the preset event chain; Based on the comparison results, determine whether there is at least one of the following: missing events, redundant events, abnormal event order, excessive inter-domain latency, inconsistent state coding, and abnormal recovery state. If it exists, then the test result is determined to be unsuccessful.
[0012] On the other hand, after determining that the test result is unsuccessful, the following also applies: The anomaly neighborhood is determined based on at least one of the following: mechanical position, angle, force, torque, speed of movement, holding time, relative time of the operating part, environmental parameters, and inter-domain delay at the time of the anomaly. Within the safety boundary, reduce the position step, angle step, or time step to re-drive the movement of the operating component; Perform real mechanical operations near abnormal positions or angles with smaller steps or altered hold times to cause the vehicle combination switch under test to re-experience the abnormal boundary. Adjust at least one of the mechanical position, angle, movement speed, holding time, or relative operation time in the direction of normal result and the direction of abnormal result, respectively, to determine the boundary range between the normal result parameter region and the abnormal result parameter region. Based on the defined boundary range, the minimum reproducible triggering condition that can trigger the target anomaly is determined. The minimum reproducible triggering condition includes minimum mechanical displacement, minimum angle change, minimum holding time, or minimum time interval.
[0013] To address the aforementioned technical problems, the present invention also provides a testing device for automotive combination switches, comprising: Memory, used to store computer programs; A processor is used to execute the computer program to implement the steps of the above-described test method for automotive combination switches.
[0014] This application provides a testing method and apparatus for automotive combination switches, relating to the testing field. It includes acquiring complete multi-domain data (mechanical, electrical, network, and load) within the same operating cycle by simultaneously acquiring signals from at least two data domains, providing a data foundation for cross-domain comprehensive analysis. Multi-domain events are linked into a cross-domain event chain, unifying state changes originally scattered across various domains into a single operation based on operating component identification, target gear, direction of change, and state code. Comparing the cross-domain event chain with a preset event chain determines whether the test passed. The cross-domain event chain records events from each domain, providing a basis for subsequent anomaly localization and avoiding misjudgments due to a lack of cross-domain evidence. Attached Figure Description
[0015] To more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the prior art and embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0016] Figure 1 A flowchart of a test method for an automotive combination switch provided by the present invention; Figure 2 This invention provides a schematic diagram of the overall structure of a multi-domain correlation test system for automotive combination switches. Figure 3 This invention provides a schematic diagram of multi-domain signal time alignment and causal event chain. Figure 4 This invention provides a flowchart of gear position feature self-learning and compliant excitation control. Figure 5 This is a schematic diagram of the structure of a test device for an automotive combination switch provided by the present invention. Detailed Implementation
[0017] The core of this invention is to provide a testing method and device for automotive combination switches, which can obtain complete mechanical-electrical-network-load multi-domain data within the same operating cycle, providing a data foundation for cross-domain comprehensive analysis. It unifies the state changes that were originally scattered in various domains into the same operation according to the operating component identification, target gear, change direction and state code, providing a basis for subsequent anomaly location and avoiding misjudgment of fault conclusions due to lack of cross-domain evidence.
[0018] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0019] Figure 1 The flowchart of a test method for an automotive combination switch provided by the present invention includes: S11: Identify the operating components in the combination switch of the vehicle under test. The operating components include at least one of the following: turn signal lever, light lever, wiper lever, knob, and button. The automotive combination switch under test can be a left / right combination switch mounted on the steering column, a steering wheel multifunction switch, a dashboard multifunction switch, or an automotive switch including at least one of the following: levers, knobs, buttons, rollers, and automatic return mechanisms. The automotive combination switch under test can employ at least one of the following forms: hard-wired contact output, resistance-encoded output, sensor output, or vehicle communication network output. The vehicle communication network can employ at least one of LIN, CAN, CANFD, and vehicle Ethernet. For automotive combination switches with purely hard-wired outputs, communication status data can be obtained through the body controller or gateway connected to the automotive combination switch under test; for intelligent combination switches with LIN or CAN interfaces, their communication status data can be directly obtained; for test scenarios that only verify the switch body, load response data can be obtained through load simulation equipment.
[0020] First, identify the operating components in the vehicle's combination switch under test. These operating components receive mechanical actions from the driver or the testing mechanism. They can include at least one of the following: a steering column switch, a light switch, a wiper switch, a knob, and a button. For example, for a steering column combination switch, the left and right turn switches can be identified as operating components; for a wiper control unit, a knob with off, intermittent, low-speed, and high-speed states can be identified as an operating component; and for a combination switch with a washer function, the washer button can also be identified as an operating component. By clearly defining the specific operating components, subsequent mechanical actions, contact changes, communication status changes, and load responses can be attributed to specific operating objects, thereby avoiding erroneous correlations of test data between different operating components.
[0021] S12: Drive the movement of the operating component and simultaneously collect multi-domain data during the movement of the operating component. The multi-domain data includes at least two of the following: mechanical status data, electrical status data, communication status data, and load response data. After identifying the operating component, its movement is driven. The actuator driving the operating component can be at least one of the following: linear servo actuator, rotary servo actuator, combination of linear and rotary actuators, pneumatic actuator, hydraulic actuator, parallel robot, or collaborative robot. The actuator contacts the operating component directly or indirectly through an end effector and performs actions such as tossing, pushing, pulling, rotating, holding, releasing, or returning to its original position according to the actual movement of the operating component. For levers, they can be tossed using a fork-shaped clamp with elastic pads; for knobs, they can be rotated using a gripper with radial compliance; and for buttons, they can be pressed using a push rod with a spherical contact head. By selecting the appropriate end effector method based on the structure of the operating component, the contact deviation between the testing mechanism and the operating component can be reduced, and the testing action can be made closer to the actual operation process in use.
[0022] During the movement of the driven operating component, multi-domain data is simultaneously collected. In this embodiment, the multi-domain data includes at least two of the following: mechanical state data, electrical state data, communication state data, and load response data. Mechanical state data describes the actual movement and force process of the operating component, and may include at least one of the following: position, angle, velocity, acceleration, force, torque, and return process data. Electrical state data describes the working state of the contacts and coded circuits, and may include at least one of the following: contact voltage, contact current, contact resistance, resistance encoding, and digital status. Communication state data describes the communication state with the vehicle's combination switch under test or its connected controller, and may include at least one of the following: LIN message, CAN message, CANFD message, message signal value, error frame, diagnostic response, and communication delay. Load response data describes the actual execution of the corresponding load after the operating component's action, and may include at least one of the following: lamp current, wiper motor status, washer pump status, actuator position, body controller output, and simulated load status.
[0023] S13: Extract multi-domain events from multi-domain data, and associate multi-domain events into a cross-domain event chain based on the event attributes of the multi-domain events. The event attributes include at least one of the following: the identifier of the operating component, the target gear, the direction of the status change, and the status code. Multi-domain events do not simply store continuous waveforms, but rather identify change events with clear state significance from continuously acquired data. For example, mechanical state data can be used to identify events such as mechanical start-up, initial contact, mechanical shifting, mechanical shifting, release, and return completion; electrical state data can be used to identify events such as initial contact change, contact stabilization, contact bounce end, resistance encoding stabilization, and contact opening; communication state data can be used to identify events such as target message arrival, status signal change, error frame, and recovery message; and load response data can be used to identify events such as light fixture activation, wiper activation, washer pump operation, and feedback stabilization. By converting continuous data into multi-domain events with attributes such as event type, occurrence time, state value, and duration, the raw sampled data can be transformed into a data structure that can be used for cross-domain comparisons.
[0024] Furthermore, based on the event attributes of multi-domain events, multi-domain events generated by different data domains are associated into a cross-domain event chain. The event attributes in this embodiment can include at least one of the following: operating component identifier, target gear position, state change direction, and state code. They can also further utilize information such as event occurrence time, expected triggering relationship, and target state. For example, for a left turn operation, the event can first be determined to belong to the left turn lever based on the operating component identifier. Then, the corresponding left turn state can be determined based on the target gear position and state change direction. Finally, the event corresponding to this mechanical action can be selected from multiple contact change events, multiple communication message events, and multiple load events. This avoids incorrectly attributing events generated by other operations to the current operation when multiple messages or multiple contact changes exist in the same test cycle.
[0025] S14: Compare the cross-domain event chain with the preset event chain, and determine the test result of the vehicle combination switch under test based on the comparison result.
[0026] The cross-domain event chain is compared with a preset event chain to determine the test results. The preset event chain can be established based on product design specifications, preset consistency conditions, or normal test data of qualified samples. During the comparison, it can be determined whether the events in the cross-domain event chain are complete, whether the event sequence meets expectations, whether the time relationship between different events meets the conditions, and whether the mechanical state, electrical state, communication state, and load state correspond to the same functional state. For example, a left turn operation can form an event chain of mechanical gear engagement—contact stabilization—target communication state—left turn light load response; if any necessary event is missing, or if there is a discrepancy between the target gear position and the communication state, the test results can be determined to be abnormal.
[0027] Therefore, this embodiment no longer judges solely based on whether a certain contact is ultimately connected or whether a certain message is ultimately generated. Instead, it determines the test result based on the event relationships of multiple data domains during a complete operation, thereby improving the ability to identify instantaneous state anomalies and cross-domain state anomalies.
[0028] This application provides a testing method for automotive combination switches, relating to the testing field. It includes simultaneously acquiring signals from at least two data domains to obtain complete multi-domain data (mechanical, electrical, network, and load) within the same operating cycle, providing a data foundation for cross-domain comprehensive analysis. Multi-domain events are linked into a cross-domain event chain, unifying state changes originally scattered across various domains into a single operation based on operating component identification, target gear, direction of change, and state code. Comparing the cross-domain event chain with a preset event chain determines whether the test passed. The cross-domain event chain records events from each domain, providing a basis for subsequent anomaly localization and avoiding misjudgments due to a lack of cross-domain evidence.
[0029] Based on the above embodiments: In some embodiments, before driving the operating component to move, the method further includes: The installation information of the vehicle combination switch under test, the installation position of the operating component, and the connection relationship between the mechanical actuator and the operating component are obtained. The vehicle combination switch under test includes the operating component and the mechanical actuator, and the mechanical actuator is used to drive the operating component. Establish the test coordinate system corresponding to the combination switch of the vehicle under test based on the installation information; Based on the installation position and pose correspondence of the operating components, determine the coordinate transformation relationship when the mechanical actuator drives the operating components to move; The mechanical actuator is controlled to drive the movement of the operating components based on the coordinate transformation relationship.
[0030] like Figure 2 As shown, the test system may include a test control host, a real-time synchronization controller, a mechanical actuator, a mechanical status acquisition module, an electrical status acquisition module, a communication status acquisition module, a load simulation and acquisition module, an environment and return simulation module, a vehicle-to-test (DUT) combination switch, and an analysis and reporting module. The test control host manages the DUT configuration, test parameters, test status, and test results; the real-time synchronization controller provides synchronization information to the execution and acquisition channels; the mechanical actuator drives the operating components; each acquisition module individually or in combination acquires mechanical status data, electrical status data, communication status data, and load response data; and the analysis and reporting module performs subsequent analysis on the acquired data.
[0031] When installing the automotive combination switch under test, it can be mounted in an adjustable positioning fixture. The positioning fixture can establish a test reference for the automotive combination switch using positioning holes, stops, or steering column simulation axes corresponding to the vehicle's assembly structure. A test coordinate system is established based on the installation information, such as an O-XYZ test coordinate system, so that the positions of the operating components, the ends of the mechanical actuators, and the position data obtained by the acquisition device can be represented under the same spatial reference. For rotary operating components, the rotation axis and rotation center can be further determined; for buttons, the button normal can be determined; and for levers, the lever axis and permissible direction of movement can be determined.
[0032] Subsequently, the installation position of the operating component and the connection relationship between the mechanical actuator and the operating component are obtained. The mechanical actuator may include a servo axis, a force or torque sensor, a compliant joint, and a replaceable end effector. After the end effector contacts the operating component, the movement of the mechanical actuator is not necessarily directly equivalent to the actual movement of the operating component; therefore, it is necessary to determine the position transformation relationship between the mechanical actuator coordinate system and the test coordinate system. In one specific embodiment, the transformation relationship between the end effector coordinate system and the test coordinate system can be obtained through visual positioning, contact detection, or manual teaching.
[0033] During contact detection, a small detection force can be used to approach the operating component from multiple directions to sequentially determine the contact position on the surface of the operating component, and further fit the lever axis, knob center, or button normal. For batch testing of the same model, the geometric model obtained from the first product can be used as the nominal model. Subsequent test samples only need to be quickly detected at key contact points, and translational and attitude deviations are calculated based on the detection results. When the deviation is within the allowable range of the fixture, the corresponding deviation correction is added to the subsequent mechanical motion trajectory; when the deviation exceeds the allowable range, the current test is stopped and a prompt is made to reinstall the automotive combination switch under test. This allows the mechanical actuator to operate according to the actual installation position of each automotive combination switch under test, reducing the direct transmission of clamping deviations to the operating component.
[0034] Based on this, the mechanical actuator is controlled to move to the operating area corresponding to the operating component according to the determined coordinate transformation relationship. When the operating component is a lever, the coordinate transformation relationship is used to convert the linear displacement of the mechanical actuator to the allowable movement direction of the lever; when the operating component is a knob, the coordinate transformation relationship is used to determine the rotation center and rotation direction; when the operating component is a button, the coordinate transformation relationship is used to determine the pressing direction and the contact position of the end effector. Thus, the mechanical actuator can accurately reach the target operating position under different clamping conditions of the automotive combination switches under test, providing a consistent spatial reference for subsequent mechanical status data acquisition.
[0035] In some embodiments, before driving the operating component to move, the method further includes: The mechanical actuator is controlled to drive the operating component to move in a low-load scanning mode. Low-load scanning is the process of gradually driving the operating component to move in a preset position increment or angle increment under the condition that the preset safety force or safety torque is not exceeded. During low-load scanning, position data, angle data, force data, and torque data of the operating components are collected during their movement. Based on position data, angle data, force data, and torque data, at least one mechanical feature point corresponding to the operating component is determined. The mechanical feature point includes at least one of the following: initial contact point, peak feature point, over-gear feature point, holding feature area, and return feature point. Determine the mechanical motion characteristic parameters of the operating components based on mechanical feature points; The movement of the operating components is driven by mechanical motion characteristic parameters.
[0036] In this embodiment, after locating the operating component, a low-load scan is performed on the target operating component. A low-load scan refers to gradually driving the operating component to move in preset position or angle increments, while simultaneously acquiring the mechanical state data of the operating component, under conditions not exceeding a preset safety force or torque. For linearly moving operating components, the movement can be gradually advanced according to preset displacement increments; for rotating operating components, the rotation can be gradually increased according to preset angle increments. The linear displacement increment can be selected from 0.05mm to 0.5mm, the angle increment from 0.05° to 0.5°, the holding time for each step from 2ms to 50ms, and the scanning speed from 5% to 30% of the normal operating speed. The above parameters are examples of a specific implementation method and do not require all automotive combination switches under test to use the same parameters.
[0037] During low-load scanning, for each position or angle increment, the corresponding operating force, operating torque, and auxiliary electrical status are collected. For force-displacement data, zero-bias correction, direction segmentation, and low-pass filtering can be performed first; for torque-angle data, corresponding data correction and filtering methods can be used. The initial contact point can be determined based on the position where the applied force continuously exceeds the predetermined statistical range of the noise baseline; the peak feature point can be determined based on the local peak value of the applied force or torque; the overshoot feature point can be determined based on the decrease in force and changes in the auxiliary electrical status after the peak value; the holding feature area can be determined based on the region where the position, angle, applied force, and applied torque are continuously maintained within a preset stable range; the return feature point can be determined based on the position where the position or angle changes in the opposite direction during release and enters the initial state or the preset return state.
[0038] When the automotive combination switch under test has multiple stable positions, the scanning curve can be segmented according to adjacent peak characteristic points and holding characteristic areas to form a position feature set G, denoted as: G={g1, g2, ..., gn}, where g1 to gn represent different position characteristics. Each position feature can record at least the entry direction, exit direction, position or angle center, mechanical envelope of the target position, peak force or torque, holding force, electrical stability state, and return method. By forming a position feature set, the actual mechanical state of the automotive combination switch under test can be correlated with the pre-set test actions, avoiding complete reliance on fixed position coordinates in the product design drawings.
[0039] Safety checks are also required during low-load scanning. If the measured force or torque reaches a preset safety threshold, or if the position remains unchanged for multiple consecutive scanning steps but the force continues to increase, the scanning can be stopped immediately, and the sample can be retracted along the original path to a safe position. Simultaneously, the current position is recorded as an insurmountable safety boundary. This prevents continuous application of force to the mechanical restraint structure before complete mechanical features are obtained, thereby reducing the risk of abnormal overload on the sample during the feature recognition stage.
[0040] In some embodiments, determining the mechanical motion characteristic parameters of the operating component based on mechanical feature points includes: The mechanical envelope of the target gear is determined based on the position range of the characteristic area. The upper limit of the allowable force or the upper limit of the allowable torque are determined based on the force or torque value at the peak characteristic point; Determine the over-gear conditions and the target position or angle corresponding to the target gear based on the position or angle of the over-gear characteristic point. The holding conditions are determined based on the force range and location range of the holding characteristic region; Determine the return conditions based on the initial contact point and the return characteristic point; The permissible speed range is determined based on the range of travel or angle between the initial contact point and the overspeed feature point.
[0041] The mechanical envelope of a target gear represents the range of mechanical parameters that allow the operating component to stably enter or maintain the target gear. This range can include at least one of the following: position range, angle range, force range, and torque range. For a lever, the target position range can be determined based on the stable position region after the overshift feature point; for a knob, the target angle range can be determined based on the overshift angle and the subsequent stable angle region; for a button, the button holding region can be determined based on the pressing position and the stable force range.
[0042] Based on the force or torque corresponding to the peak characteristic point, the upper limit of the allowable force or torque can be determined. The peak characteristic point can reflect mechanical damping, positioning structure, or state transition boundary, and therefore can serve as a force reference for the subsequent actions of the mechanical actuator. When the actual force is lower than the upper limit of the allowable force, the actuator can continue to advance along the predetermined position trajectory; when the actual force approaches the upper limit of the allowable force, the advance amount or the movement speed can be reduced; when the actual force reaches the emergency threshold, the advancement can be stopped immediately and the mechanical actuator can be controlled to retreat in the opposite direction.
[0043] Based on the position or angle of the overshift feature point, the overshift conditions and the target position or angle corresponding to the target gear can be determined. The overshift feature point can be determined based on at least one of the force-displacement curve, torque-angle curve, position change characteristics, and auxiliary electrical conditions. After the operating component crosses the mechanical damping peak, positioning structure, or state transition boundary corresponding to the target gear, the conditions for entering the target gear can be determined by combining the holding feature area. The holding feature area describes the range of mechanical parameters that the operating component can stably maintain after entering the target gear; its position, angle, force, and torque can be maintained within the corresponding stable range.
[0044] The return conditions can be determined based on the initial contact point and the return feature point. When the operating component is released, the mechanical actuator can be controlled to return at a preset speed, or the mechanical constraint can be released to allow the operating component to return to its original position automatically under the action of the automatic return mechanism. The return feature point is used to determine whether the initial state or the preset return state has been restored. Based on the travel or angle range between the initial contact point and the overshoot feature point, the allowable speed range can be further determined, allowing the mechanical actuator to be tested at a speed suitable for the mechanical structure of the current automotive combination switch after contact.
[0045] In one specific implementation, the target gear position is not a fixed design value, but rather a position with a safety margin is selected within the identified target stability range. For example, a holding position can be selected within the stability range after the gear overshoot feature point, ensuring a preset safety margin between the holding position and the mechanical safety boundary. The mechanical motion characteristic parameters generated in this way are derived from the mechanical data of the current automotive combination switch under test, and can adapt to individual product differences, clamping deviations, and gear drift caused by wear.
[0046] In some embodiments, driving the movement of an operating component based on mechanical motion characteristic parameters includes: The control parameters of the mechanical actuator are determined based on the mechanical motion characteristic parameters. The control parameters include at least one of the following: motion position, motion angle, driving force, driving torque, motion speed, and holding time. Generate the test motion trajectory corresponding to the mechanical actuator based on the control parameters; The control mechanism drives the operating components to perform test actions according to the test motion trajectory.
[0047] Control parameters may include at least one of the following: motion position, motion angle, driving force, driving torque, motion speed, and holding time. A test motion trajectory is generated based on these control parameters, and this trajectory describes the entire process of the mechanical actuator moving from its current state to a target state.
[0048] In one specific implementation, the test motion trajectory includes at least an approach segment, a preload segment, a skip segment, a holding segment, and a release segment. The approach segment controls the mechanical actuator to move rapidly to the vicinity of the operating component; the preload segment reduces the movement speed and enters a controlled state after detecting contact with the operating component; the skip segment allows the operating component to pass the corresponding mechanical feature point and enter the target gear, during which position control and force constraint can be used simultaneously; the holding segment maintains the target state and collects mechanical, electrical, and communication data under stable conditions; the release segment allows the component to retreat at a controlled speed or release constraints to return to its original position via its own return mechanism.
[0049] In transitioning between gears, compliant closed-loop control can be employed. The position command xd represents the target position of the mechanical actuator, the measured force F represents the current force applied by the mechanical actuator to the operating component, and the allowable force limit Flim represents the maximum allowable force. When F is less than Flim, the mechanical actuator continues to advance along the current position trajectory; when F reaches Flim, the current position command can be frozen or the position increment reduced; when F exceeds the emergency threshold Femg, the mechanical actuator is immediately controlled to reverse. For knobs, angular position and torque can be used for corresponding control. By using real-time force or torque feedback to correct the motion, the actual force can be controlled to prevent it from continuously exceeding the set range while entering the target gear.
[0050] The test motion trajectory can also store the expected mechanical, electrical, and communication events for each trajectory segment. For example, the approach segment can correspond to the initial contact event, the overshoot segment to the mechanical overshoot event, the holding segment to the mechanical engagement and electrical stabilization events, and the release segment to the release and return completion events. In this way, when multi-domain data is obtained during the actual test, the expected event information pre-formed from the test motion trajectory can assist in the identification of subsequent events.
[0051] In batch testing scenarios, a gear feature template can be established using the first piece of the same model. For subsequent samples, a low-load short scan is first performed. If the offset of key feature points relative to the template is within the allowable range, the template trajectory can be translated or proportionally corrected; if the offset exceeds the allowable range, a full low-load scan is performed on the current sample. This maintains the mechanical adaptability of each sample while reducing the repetitive scanning time in batch testing.
[0052] In some embodiments, multi-domain data is synchronously acquired during the movement of the operating component, including: Output synchronous clock signals to each acquisition channel; The time offset of the acquisition channels corresponding to mechanical status data, electrical status data, communication status data, and load response data is determined based on the synchronous clock signal. Time correction is performed on data acquired from different acquisition channels based on the time offset; The time correction formula is as follows: ; in, Let be the original time of the i-th channel. This is the clock frequency scaling correction factor for the i-th channel. Let be the fixed delay compensation amount for the i-th channel. The time after time correction for the i-th channel; The time-corrected mechanical status data, electrical status data, communication status data, and load response data are all mapped to the same time base to serve as multi-domain data during the movement of the operating components.
[0053] A unified time reference is established during test operations, enabling mechanical status data, electrical status data, communication status data, and load response data to be mapped to the same time axis. The real-time synchronization controller outputs a synchronization clock signal, a synchronization pulse signal, and / or a hardware trigger signal. Each acquisition channel receives the corresponding synchronization information and records the sampling time using a hardware counter or hardware timestamp. The mechanical actuator controller, analog acquisition device, digital acquisition device, communication interface, and load acquisition device can obtain synchronization information through at least one of the following: hardware trigger line, IEEE 1588 time synchronization protocol, shared backplane clock, or latchable pulse input.
[0054] Time delay calibration is performed before formal testing. The real-time synchronous controller can simultaneously output electrical transition signals and communication trigger messages, and control the mechanical actuator to pass the photoelectric reference position. Each acquisition channel records the occurrence time of the corresponding event. Using the time of the real-time synchronous controller as a unified time reference, the corresponding time correction relationship is calculated based on the event time acquired by each acquisition channel: ti = ai·ti + bi; where ti is the original time of the i-th channel, ai is the clock frequency proportional correction coefficient of the i-th channel, bi is the fixed delay compensation amount of the i-th channel, and ti is the time of the i-th channel after time correction. Here, ai is used to describe the clock rate difference of the i-th channel relative to the unified time reference. When the i-th channel and the unified time reference use the same clock source, ai can be set to 1; bi is used to compensate for the time delay caused by the data transmission, acquisition trigger, or fixed processing link of the channel itself. Through the above relationship, the time information in mechanical status data, electrical status data, communication status data, and load response data can be converted to the unified time reference.
[0055] In one specific implementation, mechanical position and force data can be acquired using a higher sampling frequency, while contact voltage and current can be acquired using an even higher sampling frequency. The communication interface records communication events via hardware timestamps. Since the sampling frequencies and buffering mechanisms of different acquisition channels may differ, the order of events cannot be directly determined by their respective software timestamps; instead, a unified time mapping needs to be completed based on the aforementioned time correction relationship. After time calibration, a common synchronization pulse can be used to check the residual time difference between different domains. If the residual time difference exceeds the preset synchronization tolerance, the formal test is not initiated.
[0056] After time correction, the data is uniformly mapped to the same time base, ensuring that each mechanical, electrical, communication, and load event has comparable time information. This allows for reliable determination of the intervals between mechanical engagement and contact stabilization, contact stabilization and communication status changes, and communication status changes and load response, avoiding misordering of events within the same operation due to time drift caused by independent timing of different devices.
[0057] In some embodiments, extracting multi-domain events from multi-domain data includes: Mechanical events are extracted from mechanical state data. Mechanical events include at least one of the following: initial contact event, mechanical over-gear event, mechanical gear-entry event, release event, and return-to-position completion event. Electrical events are extracted from electrical status data. These electrical events include at least one of the following: initial contact change event, contact bounce end event, resistance value encoding stabilization event, and contact opening event. The communication events are extracted from the communication status data. The communication events include at least one of the following: target message arrival event, status signal change event, error frame event, and recovery message event. Extract load events from the load response data. Load events include at least one of the following: load start-up event, load status establishment event, and feedback stabilization event.
[0058] After completing the unified time reference mapping, mechanical events are first extracted from the mechanical state data. Mechanical start-up events can be determined based on a significant change in the position or speed of the mechanical actuator; initial contact events can be determined based on the force exceeding the contact threshold; mechanical gear skipping events can be determined based on the position or angle of the operating component crossing the gear skipping feature point; mechanical gear completion events can be determined based on the operating component entering the target stable envelope and maintaining it for a preset time; release events can be determined based on the operating component starting to move along the release direction; and return-to-position completion events can be determined based on the operating component re-entering the initial state or a preset return-to-position state.
[0059] When extracting electrical events from electrical state data, the initial contact change event can be extracted based on changes in voltage, current, or resistance. By detecting continuous on / off changes in contact level within a short period, contact bounce clusters can be formed, and multiple bounces can be grouped into the same contact state transition based on the time interval between adjacent bounces. When the target level, target resistance, or target code remains stable for a preset time, an electrical stability event can be determined. Electrical stability events not only focus on the final state but also retain the initial change time, stability time, number of bounces, and bounce duration, thereby enabling the identification of contact anomalies occurring within a short period.
[0060] When extracting communication events from communication status data, the target message arrival event can be determined based on the message identifier, message signal value, verification result, and message arrival time. If the first message that meets the target status and is correctly verified appears, the time corresponding to that message can be determined as the occurrence time of the communication status change event; if a message timeout, verification failure, or error frame occurs, corresponding communication events are generated respectively. For LIN communication, master node scheduling and slave node responses can be collected; for CAN or CANFD communication, wake-up, network management, and service message status can be recorded.
[0061] When extracting load events from load response data, load start-up events, load state establishment events, and feedback stabilization events can be determined based on the actual load current, actuator position, speed, or controller feedback signal crossing a target threshold. For example, a left turn signal ignition event is determined when the left turn signal load current crosses a target threshold; a wiper state establishment event is determined when the wiper motor reaches and stabilizes within the corresponding speed range; and a washer pump response event is determined when the washer pump feedback reaches the corresponding operating state.
[0062] The preferred definition for a mechanical position reaching a stable position event is when the operating position enters the target stable envelope for a duration of not less than T_pos, while the operating force does not exceed the holding force limit. The preferred definition for an electrical stability event is when the target level, resistance, or code remains continuously held at T_elec without any further bouncing during this period. The preferred definition for a network state change event is the time of the first message carrying the target state value and with correct verification.
[0063] For contact bounce, each flip is first identified by the voltage or current crossing high or low thresholds. Then, multiple flips with adjacent flip intervals less than a preset merging interval are grouped into the same bounce cluster. The time of the first change, the time of the last change, the number of bounces, and the total duration are recorded to avoid masking short-term bounces with only low-sampled digital input. Table 1 shows the multi-domain event types and extraction criteria.
[0064] Table 1
[0065] Assuming the mechanical shift time for a left turn operation is 1.250000 s, the contact settling time is 1.253200 s, the first occurrence time of the LIN target state is 1.263800 s, and the load simulator detects the left turn signal output time is 1.270500 s, then ΔtME = 3.2 ms, ΔtEN = 10.6 ms, and ΔtNL = 6.7 ms. If the baseline allowable ranges are 0–5 ms, 5–15 ms, and 0–10 ms respectively, then the event chain satisfies the time delay constraint. If the contact state is left turn and the LIN signal is right turn, even if the load does not ultimately move, it should be judged as a state coding inconsistency, and a hierarchical fault analysis should be performed in conjunction with the initial deviation domain and subsequent propagation relationship, rather than simply judging it as a communication timeout. Table 2 is an example table of data organization for actual cross-domain event chains.
[0066] Table 2
[0067] In some embodiments, associating multi-domain events as a cross-domain event chain based on the event attributes of the multi-domain events includes: Based on at least one of the following: the identifier of the operating component, the target gear, the direction of the status change, the status code, and the event occurrence time, the extracted mechanical events, electrical events, communication events, and load events are associated as a cross-domain event chain; Obtain the preset event chain, which is established in advance based on the normal test data of qualified samples; The cross-domain event chain is compared with the preset event chain, and the test results of the vehicle combination switch under test are determined based on the comparison results, including: Compare the cross-domain event chain with the preset event chain; Based on the comparison results, determine whether there is at least one of the following: missing events, redundant events, abnormal event order, excessive inter-domain latency, inconsistent state coding, and abnormal recovery state. If it exists, then the test result is determined to be unsuccessful.
[0068] At least one of the following events can be selected as a reference event: mechanical start-up event Em0, initial contact event, mechanical gear engagement event Em1, release event, or return event, to establish a time anchor point for one operation cycle. Then, based on the operating component identifier, target gear, direction of state change, target state code, expected triggering relationship, and allowable time window, events corresponding to this mechanical operation are determined from the electrical event set, communication event set, and load event set, forming an actual cross-domain event chain. The event chain can be represented as: Ck = {Em0, Em1, Ee, En, El}, where Em0 represents the mechanical start-up event, Em1 represents the mechanical gear engagement event, Ee represents the electrical event associated with this operation, En represents the communication event associated with this operation, and El represents the load event associated with this operation. In practical implementations, it is not required that each event chain contain all event types, but it must include at least mechanical events and at least one of electrical, communication, and load events. When associating multiple candidate events, they can be filtered step-by-step based on event attributes. For example, when multiple communication messages of the same type exist within the same allowed time window, they can be filtered based on the operating component identifier and corresponding status code; when multiple contact flip events exist, they can be further filtered based on the direction of status change and the target gear; when multiple load responses exist, they can be filtered based on the current test status, the expected event sequence, and the time difference relative to the reference event. If the associated events cannot be uniquely determined, multiple candidate cross-domain event chains can be retained and the association confidence level recorded, and further differentiation can be achieved in subsequent tests using more stringent operation timing or mechanical position conditions.
[0069] Cross-domain event chains can also record time intervals between different data domains. The mechanical-to-electrical delay can be expressed as: ΔtME = tEe - tEm1; where tEe is the occurrence time of the electrical event corresponding to the current operation, and tEm1 is the occurrence time of the mechanical arrival event. The electrical-to-communication delay can be expressed as: ΔtEN = tEn - tEe; where tEn is the occurrence time of the communication state change event. The communication-to-load delay can be expressed as: ΔtNL = tEl - tEn; where tEl is the occurrence time of the load response event. The mechanical-to-final-load delay can be expressed as: ΔtML = tEl - tEm1; where tEl is the occurrence time of the load response event, and tEm1 is the occurrence time of the mechanical arrival event. All the above time intervals are established under a unified time base, thus enabling direct cross-domain comparisons. For certain combination switches where the electrical state is allowed to be established before the mechanical arrival event, it is not required that all inter-domain delays be positive; instead, a directional allowable time window can be established based on the baseline event chain and normal test data.
[0070] The preset event chain can be obtained by repeated testing under preset environmental and power supply conditions based on design specifications, preset consistency constraints, or multiple confirmed qualified samples. For repeated samples, the allowable time window can be determined based on the event time statistics, such as using the median, quantile range, mean plus or minus tolerance, or other statistical ranges to determine the normal time range. Subsequently, the actual cross-domain event chain is compared with the preset event chain to at least determine whether the expected events are missing, whether there are redundant events, whether the event sequence is correct, whether the inter-domain delay exceeds the allowable range, whether the mechanical target gear, electrical coding, and communication status correspond to the same functional state, and whether each data field recovers within the preset recovery time after release or return. For example, in a left-turn operation, assuming the mechanical gear shift time is 1.250000s, the contact stabilization time is 1.253200s, the first occurrence time of the LIN target state is 1.263800s, and the load simulator detects the left-turn light output time is 1.270500s, then the mechanical-to-electrical delay ΔtME is 3.2ms, the electrical-to-communication delay ΔtEN is 10.6ms, and the communication-to-load delay ΔtNL is 6.7ms. If the corresponding baseline allowable ranges are 0-5ms, 5-15ms, and 0-10ms respectively, then the event chain satisfies the delay condition. If the mechanical state and contact state correspond to a left turn, but the communication state code is a right turn, even if the load ultimately does not move, it should be judged as a state code inconsistency, and cannot be simply classified as a communication timeout. Hierarchical fault analysis uses the event domain that deviates from the baseline event chain or preset consistency constraints under a unified time base, and can explain the subsequent abnormal propagation, as the initial deviation domain. To avoid misjudgments caused by errors from a single sensor, when a mechanical domain anomaly is triggered by only one measurement, at least one of the following can be used for cross-verification: servo encoder, external displacement sensor, visual measurement results, or force measurement results. When a network domain anomaly occurs, at least one of the following can be used for verification: original bus frame, parsed signal value, verification results, and diagnostic response. Table 3 shows the rules for the initial deviation domain and priority investigation hierarchy.
[0071] Table 3
[0072] In some embodiments, after determining that the test result fails, the method further includes: The anomaly neighborhood is determined based on at least one of the following: mechanical position, angle, force, torque, speed of movement, holding time, relative time of the operating part, environmental parameters, and inter-domain delay at the time of the anomaly. Within the safety boundary, reduce the position step, angle step, or time step to re-drive the movement of the operating component; Perform real mechanical operations near abnormal positions or angles with smaller steps or altered holding times to make the vehicle combination switch under test re-experience the abnormal boundary. Adjust at least one of the mechanical position, angle, movement speed, holding time, or relative operation time in the direction of normal result and the direction of abnormal result, respectively, to determine the boundary range between the normal result parameter region and the abnormal result parameter region. Based on the boundary range, determine the minimum reproducible triggering condition that can trigger the target anomaly. The minimum reproducible triggering condition includes minimum mechanical displacement, minimum angle change, minimum holding time, or minimum time interval.
[0073] When an anomaly is determined to exist after comparing the cross-domain event chain with the preset event chain, at least one parameter is saved from the following: mechanical position, angle, force, torque, speed, holding time, relative time of the operating component, environmental parameters, and inter-domain delay, corresponding to the operation cycle in which the anomaly occurred. An anomaly neighborhood is then established based on the mechanical position interval, force interval, and time interval corresponding to the first occurrence of the anomaly. The anomaly neighborhood represents the search range formed around the parameter area that has triggered the anomaly, and can simultaneously include mechanical parameters, time parameters, and environmental parameters.
[0074] For example, in the case of cross-operation of the wiper knob and the washer button, if the washer button is pressed while the wiper knob is shifting gears, and the resistance code is found to be correct, but an incorrect gear code appears briefly in the communication state, then the knob angle at the time of the anomaly and the relative time of the washer button's movement relative to the knob are saved. A preset range before and after the abnormal angle and a preset range before and after the relative time are defined as the abnormal neighborhood. Within this abnormal neighborhood, the operating components are re-driven to perform the actual cross-operation, instead of directly replaying the already recorded communication messages. This allows the mechanical contacts, internal circuitry, and controller to re-experience the actual abnormal boundary.
[0075] During the reproduction of the anomaly neighborhood, the position step size, angle step size, and time step size are reduced within the safety boundary. First, multiple real mechanical operations are repeatedly executed according to the original anomaly parameters. When the anomaly can be reproduced, the mechanical position, mechanical angle, movement speed, holding time, or relative time of the operating parts are adjusted towards both the normal and anomaly result directions, thereby gradually narrowing the boundary between the normal and anomaly parameter regions. The search method can employ binary search, decreasing step size search, or grid search. Each search involves re-executing the real mechanical operation, continuing to be subject to constraints such as applied force, applied torque, and safe travel.
[0076] Once the anomaly boundary is identified, the minimum reproducible triggering condition that can reliably trigger the target anomaly can be determined. The minimum reproducible triggering condition can include minimum mechanical displacement, minimum angle change, minimum hold time, minimum time interval, or a combination thereof. For example, in the cross-operation of the wiper knob and the washer button, the range of abnormal angles and the relative operation time range of the washer button can be gradually narrowed down to ultimately determine the angle-time boundary that can reliably trigger the erroneous communication state. In multi-operation concurrent testing during automatic return, the return axis speed, the relative time of the second operation, and the degree of effect of the second operation can be adjusted to determine the minimum time interval that will not cause an anomaly and the combined conditions that can reliably trigger the anomaly.
[0077] If the original abnormal parameters cannot trigger the abnormality again, it is not directly identified as a stable defect. Instead, the original multi-domain waveform, mechanical trajectory, and environmental parameters are saved, and the abnormality is marked as an intermittent abnormality. This allows for the distinction between stable reproducible abnormalities and intermittent abnormalities, facilitating subsequent product design analysis and prototype disassembly.
[0078] It can generate test sequences such as operating the second operator while holding the first operator, initiating the second operator while the first operator is in a transition phase, releasing the first operator in reverse after the second operator completes, operating other operators during automatic return, and performing rapid switching near the minimum and maximum allowable intervals. For operation combinations that share the same contact slider, resistance network, microcontroller input port, communication signal group, or power supply branch, it can increase the execution priority of the corresponding combination test, thereby discovering cross-operation anomalies that are difficult to detect with traditional single-function tests.
[0079] In a specific embodiment, the vehicle combination switch under test can be a left / right combination switch mounted on the steering column, a steering wheel multifunction switch, an instrument panel multifunction switch, or an on-board switch that includes two or more operating elements such as levers, knobs, buttons, rollers, and automatic return mechanisms. Its output can be a hard-wired contact, resistance encoding, Hall effect or photoelectric position sensor, Local Interconnect Network (LIN) slave node, Controller Area Network (CAN) node, or a Controller Area Network (CAN FD) node with flexible data rates.
[0080] For purely hard-wired combination switches, the network domain can be formed by the output messages of the body controller or gateway connected to the combination switch; for intelligent combination switches with built-in LIN or CAN interfaces, the network domain directly collects the network messages of the device under test; for scenarios where only the switch body needs to be verified, the load domain can be formed by a programmable electronic load or a digital input simulation module.
[0081] In this embodiment, one operation cycle is defined as the process from when the operating component leaves the stable state, through the establishment of the target gear, the stabilization of electrical output, the update of network status and load response, until the operating component maintains or returns to the preset state. One operation cycle may include a single action of one operating component, or it may include a combination of actions of multiple operating components that overlap in time.
[0082] The sampling frequency, threshold, time window, step size, and number of repetitions in this embodiment are merely examples. Those skilled in the art can adjust them equivalently based on the switch structure, allowable operating force, communication cycle, and test objectives. The core principle lies in using a calibrable common time axis for each domain and defining the true excitation boundary based on the mechanical characteristics of the device under test.
[0083] like Figure 2 As shown, the test system includes a test control host 100, a real-time synchronous controller 110, an adaptive mechanical excitation module 120, a mechanical domain acquisition module 130, an electrical domain acquisition module 140, a network domain acquisition module 150, a load simulation and acquisition module 160, an environmental and return simulation module 170, a vehicle combination switch under test 180, and an analysis and reporting module 190. The mechanical excitation module 120 preferably uses a replaceable end effector. The end of the lever can use a fork-shaped clamp with elastic padding, the end of the knob can use a gripper with radial compliance, and the end of the button can use a push rod with a spherical contact head. A six-dimensional force sensor is placed between the servo axis and the end effector to directly measure the force or torque applied to the operating element. The compliant joint allows the end effector to have limited float in a direction perpendicular to the main operating direction to reduce lateral forces caused by clamping errors. Table 4 shows the composition and function of the test system modules.
[0084] Table 4
[0085] like Figure 3 As shown, at least one of the following events is used as a reference operation event: mechanical start-up event Em0, initial contact event, mechanical gear shift event Em1, release event, or return event. Based on the operating component identifier, target gear, direction of change, expected state code, expected triggering relationship, and allowable time window, an event Ee corresponding to the current operation is selected from the electrical event set, an event En is selected from the network event set, and an event El is selected from the load event set, forming the actual cross-domain event chain Ck = {Em0, Em1, Ee, En, El}. Not every implementation must include all event types, but the actual cross-domain event chain must include at least one of the following: mechanical domain events, and electrical domain events, network domain events, and load domain events.
[0086] The actual cross-domain event chain records the inter-domain delays between related events, including the mechanical-to-electrical delay ΔtME=tEe-tEm1, the electrical-to-network delay ΔtEN=tEn-tEe, the network-to-load delay ΔtNL=tEl-tEn, and the mechanical-to-final-load delay ΔtML=tEl-tEm1. For the test switchgear whose electrical state allows establishment before the mechanical-to-load event, a directional allowable time window can be determined based on the baseline event chain, preset consistency constraints, and / or normal test data of qualified samples, without requiring all inter-domain delays to be positive.
[0087] When multiple messages of the same type, multiple contact flip events, or multiple candidate load response events exist within the same allowed time window, the event association module can determine candidate associated events based on at least one of the following: operator identifier, corresponding signal code, direction of change, current node in the test state diagram, target gear, expected event sequence, and time difference between the event and the reference operation event. If a unique association cannot be achieved, multiple candidate actual cross-domain event chains can be retained, and the corresponding event association confidence levels can be recorded. In subsequent anomaly neighborhood reproduction, differentiation can be achieved by reducing the operation interval, changing the relative operation time, and / or reducing the mechanical position or angle step size.
[0088] Specific Implementation Example 1: Steering Lever Mechanical-Contact-LIN-Lighting Fixture Correlation Test 1) Install the steering column combination switch with LIN interface into the steering column simulation fixture, and configure the left turn, right turn and automatic return operation components; connect the lamp load simulator to the output of the body controller; 2) Perform a low-load scan in the left-turn direction to identify the initial contact point, over-gear feature point, left-turn holding feature area, and return feature point, and set the upper limit of the operating force to 90% of the upper limit of the sample's technical requirements; 3) Generate approach, overdrive, hold for 500 ms and release trajectories, and collect lever angle, operating torque, internal contact voltage, LIN message and left turn signal load current with a unified time reference; 4) Construct the actual cross-domain event chain of "mechanical gear shift - contact stabilization - LIN left turn status - left turn light current establishment", and determine whether the four types of events have occurred, whether the order is correct, and whether the time delay of each segment has exceeded the limit. 5) Drive the steering wheel simulation shaft back to center through the return simulation mechanism, and collect data on the mechanical return of the lever, contact disconnection, LIN state cancellation, and disappearance of lamp current; 6) If the machine has returned to its original position but the LIN left-turn state continues for more than the allowed cancellation time, then the electrical state holding or LIN node state recovery will be determined as the priority direction for investigation, and the minimum reproducible trigger condition will be repeatedly searched by fixing the return angle and reducing the return speed step size.
[0089] Specific Implementation Example 2: Cross-operation test of wiper knob and washer button: 1) Establish four knob states: wiper off, intermittent, low speed, and high speed, as well as the wash button's pressed and released states; mark the knob codes and wash button as sharing internal power supply or communication node resources; 2) First, test each steady state individually, and then generate the following cross sequence: Press the wash button during the intermittent speed change from off to intermittent speed change; during the wash hold period, switch from intermittent speed to low speed; and rotate the knob back to off within 20 ms after the wash is released. 3) Synchronously collect knob torque, button pressure, resistance encoding, wiper mode and washing request in LIN messages, and simulation feedback of wiper motor and washing pump; 4) If the resistance value encoding is correct when mechanically switching gears, but the LIN message briefly shows a high-speed gear encoding, then save the knob angle and the relative time when the washing machine was pressed when the error occurred. 5) Establish an abnormal neighborhood with an abnormal angle of 1° before and after and a relative time of 15 ms before and after, gradually reduce it to 0.1° and 1 ms, repeat the real crossover operation to obtain the angle-time boundary that stably triggers the error code; 6) Based on evidence that the mechanical and electrical coding is normal but the network status is incorrect, determine the node input sampling, debouncing, or status coding logic as the priority direction for troubleshooting the network layer.
[0090] Specific Implementation Example 3: Early Contact Degradation and Bounce Abnormality Test: 1) Select the high and low beam toggle contacts, and synchronously collect the contact voltage and current under rated load and low current measurement branch, with the sampling frequency set to 100 kS / s; 2) After each preset number of durability cycles is completed, perform a low-speed characteristic scan and a standard speed operation, and record the peak force of the gear shift, the change of the first contact point, the number of bounces, the duration of the bounces, the stable contact voltage drop, and the message update time. 3) If the mechanical peak force is still within the reference envelope, but the bouncing duration increases for several consecutive inspection cycles and the network update time is delayed accordingly, then it is determined that the electrical layer has a degradation trend. 4) Adjust the operating speed and overshoot depth on the abnormal sample, perform abnormal neighborhood reproduction, and confirm whether the bounce abnormality only occurs at a specific mechanical speed or a specific contact pressing depth. 5) The actual cross-domain event chain of maintaining normal output mechanical curves, first causing electrical waveform drift, and then network response delay provides a priority basis for disassembly analysis of contact surface contamination, elastic component attenuation, insufficient contact of sliders, or abnormal internal coding.
[0091] Specific Implementation Example 4: Concurrent Testing of Multiple Operators During Automatic Return Period: 1) Put the steering lever into the left turn holding state, and drive the steering column simulation shaft gradually close to the return trigger angle by the return simulation mechanism; 2) Operate the high beam lever or headlight knob within the time window when the pin has just contacted the return mechanism and the lever has not yet been fully released; 3) Synchronously collect data on the return mechanism angle, lever torque, steering contact, light contact, network status, and lighting feedback; 4) If the second operation causes the steering lever to return to its original position prematurely or the steering state is not cancelled, then lock the abnormal window between the contact of the locking pin and the completion of the mechanical return. 5) Change the return axis speed, the relative time of the second operation, and the force of the second operation to perform a boundary search, and obtain the minimum time interval that will not cause a conflict and the combination of conditions that stably trigger an exception. 6) Based on the initial deviation domain and abnormal propagation relationship, analyze at least one of the following situations: mechanical coupling causing premature return, normal mechanical return but failure to restore electrical status, and normal mechanical return but failure to restore network status, and output the corresponding priority investigation level.
[0092] Figure 5 This is a schematic diagram of a testing device for an automotive combination switch provided by the present invention. The testing device for the automotive combination switch includes: Memory 51 is used to store computer programs; The processor 52 is used to execute the steps of the above-described test method for automotive combination switches when executing a computer program.
[0093] The description of the testing device for automotive combination switches provided in this application is given in the above embodiments and will not be repeated here.
[0094] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0095] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.
[0096] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A test method for automotive combination switches, characterized in that, include: Identify the operating components in the combination switch of the vehicle under test, wherein the operating components include at least one of the following: turn signal lever, light lever, wiper lever, knob, and button; The operating component is driven to move, and multi-domain data during the movement of the operating component is collected synchronously. The multi-domain data includes at least two of the following: mechanical status data, electrical status data, communication status data, and load response data. Multi-domain events are extracted from the multi-domain data, and the multi-domain events are associated as a cross-domain event chain according to the event attributes of the multi-domain events. The event attributes include at least one of the following: the identifier of the operating component, the target gear, the direction of state change, and the state code. The cross-domain event chain is compared with a preset event chain, and the test result of the vehicle combination switch under test is determined based on the comparison result.
2. The test method for automotive combination switches as described in claim 1, characterized in that, Before driving the operating component to move, it also includes: The installation information of the vehicle combination switch under test, the installation position of the operating component, and the connection relationship between the mechanical actuator and the operating component are obtained. The vehicle combination switch under test includes an operating component and a mechanical actuator, and the mechanical actuator is used to drive the operating component. Establish a test coordinate system corresponding to the combination switch of the vehicle under test based on the installation information; Based on the installation position of the operating component and the pose correspondence, the coordinate transformation relationship when the mechanical actuator drives the operating component to move is determined; The mechanical actuator is controlled to drive the operating component to move according to the coordinate transformation relationship.
3. The test method for automotive combination switches as described in claim 1, characterized in that, Before driving the operating component to move, it also includes: The mechanical actuator is controlled to drive the operating component to move in a low-load scanning mode. The low-load scanning is a process of gradually driving the operating component to move in a preset position increment or angle increment under the condition that the preset safety force or safety torque is not exceeded. During the low-load scanning process, position data, angle data, force data, and torque data of the operating component during its movement are collected. Based on the position data, angle data, force data, and torque data, at least one mechanical feature point corresponding to the operating component is determined. The mechanical feature point includes at least one of the following: initial contact point, peak feature point, over-gear feature point, holding feature area, and return feature point. The mechanical motion characteristic parameters of the operating component are determined based on the mechanical feature points; The operating component is driven to move based on the mechanical motion characteristic parameters.
4. The test method for automotive combination switches as described in claim 3, characterized in that, Determining the mechanical motion characteristic parameters of the operating component based on the aforementioned mechanical feature points includes: The mechanical envelope of the target gear is determined based on the position range of the retaining feature area; The upper limit of the allowable force or the upper limit of the allowable torque are determined based on the force or torque value of the peak characteristic point; Determine the over-gear condition and the target position or target angle corresponding to the target gear based on the position or angle of the over-gear feature point. The holding conditions are determined based on the force range and position range of the holding feature area; The retraction conditions are determined based on the initial contact point and the return feature point. The permissible speed range is determined based on the range of travel or angle between the initial contact point and the overshoot feature point.
5. The test method for automotive combination switches as described in claim 4, characterized in that, Driving the operating component to move based on the aforementioned mechanical motion characteristic parameters includes: The control parameters of the mechanical actuator are determined based on the mechanical motion characteristic parameters, and the control parameters include at least one of motion position, motion angle, driving force, driving torque, motion speed, and holding time; Generate the test motion trajectory corresponding to the mechanical actuator based on the control parameters; The mechanical actuator is controlled to drive the operating component to perform the test action according to the test motion trajectory.
6. The test method for automotive combination switches as described in claim 1, characterized in that, Synchronously collect multi-domain data during the movement of the operating component, including: Output synchronous clock signals to each acquisition channel; The time offset of the acquisition channel corresponding to the mechanical status data, electrical status data, communication status data, and load response data is determined based on the synchronous clock signal. Time correction is performed on the data acquired from different acquisition channels based on the time offset; The time correction formula is as follows: ; in, Let be the original time of the i-th channel. This is the clock frequency scaling correction factor for the i-th channel. Let be the fixed delay compensation amount for the i-th channel. The time after time correction for the i-th channel; The time-corrected mechanical status data, electrical status data, communication status data, and load response data are all mapped to the same time reference to serve as multi-domain data during the movement of the operating component.
7. The test method for automotive combination switches as described in any one of claims 1 to 6, characterized in that, Extracting multi-domain events from the multi-domain data includes: Mechanical events are extracted from the mechanical state data, and the mechanical events include at least one of the following: initial contact event, mechanical over-gear event, mechanical gear-entry event, release event, and return-to-position completion event; Electrical events are extracted from the electrical state data, and the electrical events include at least one of the following: contact first change event, contact bounce end event, resistance value encoding stabilization event, and contact open event; The communication events are extracted from the communication status data, and the communication events include at least one of the following: target message arrival event, status signal change event, error frame event, and recovery message event; Load events are extracted from the load response data, and the load events include at least one of load start-up events, load status establishment events, and feedback stabilization events.
8. The test method for automotive combination switches as described in claim 7, characterized in that, The multi-domain events are associated into a cross-domain event chain based on their event attributes, including: Based on at least one of the following: the identifier of the operating component, the target gear, the direction of state change, the state code, and the event occurrence time, the extracted mechanical event, electrical event, communication event, and load event are associated as the cross-domain event chain; Obtain a preset event chain, which is established in advance based on the normal test data of qualified samples; The cross-domain event chain is compared with a preset event chain, and the test result of the vehicle combination switch under test is determined based on the comparison result, including: Compare the cross-domain event chain with the preset event chain; Based on the comparison results, determine whether there is at least one of the following: missing events, redundant events, abnormal event order, excessive inter-domain latency, inconsistent state coding, and abnormal recovery state. If it exists, then the test result is determined to be unsuccessful.
9. The test method for automotive combination switches as described in claim 8, characterized in that, After determining that the test result is unsuccessful, the following steps are also included: The anomaly neighborhood is determined based on at least one of the following: mechanical position, angle, force, torque, speed of movement, holding time, relative time of the operating part, environmental parameters, and inter-domain delay at the time of the anomaly. Within the safety boundary, reduce the position step, angle step, or time step to re-drive the movement of the operating component; Perform real mechanical operations near abnormal positions or angles with smaller steps or altered hold times to cause the vehicle combination switch under test to re-experience the abnormal boundary. Adjust at least one of the mechanical position, angle, movement speed, holding time, or relative operation time in the direction of normal result and the direction of abnormal result, respectively, to determine the boundary range between the normal result parameter region and the abnormal result parameter region. Based on the defined boundary range, the minimum reproducible triggering condition that can trigger the target anomaly is determined. The minimum reproducible triggering condition includes minimum mechanical displacement, minimum angle change, minimum holding time, or minimum time interval.
10. A testing device for automotive combination switches, characterized in that, include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the steps of the test method for an automotive combination switch as described in any one of claims 1 to 9.
