T/CI 150-2022 Transit traction electric drive system fault testing specification Part 1: Hardware-in-the-loop simulation platform
T/CI 150-2022 Transit traction electric drive system fault testing specification Part 1: Hardware-in-the-loop simulation platform
Basic Information
Scope
Scope: This document specifies the platform configuration, technical requirements, and implementation guidelines for the fault test (hardware-in-the-loop simulation platform) of traction electric drive systems in rail transit. This document is applicable to the traction electric drive systems on locomotives and EMUs (not limited to control, monitoring, diagnostic, and isolation protection algorithms) for completeness and performance testing under fault simulation, risk analysis, and overall evaluation. Other types of vehicles' traction electric drive systems can refer to this document for implementation. Main technical content: - Technical requirements 5.1 - Functional requirements 5.1.1 - Hardware-in-the-loop simulation of traction electric drive systems: a) Support simulation of the traction electric drive system under various line operation curves. b) Support adding, setting, deleting, and replacing components of the traction electric drive system, including but not limited to traction converters, traction motors, traction control units, and sensors. - Fault injection: a) Support multiple fault injection modes, including real-time activation, scheduled activation, and event-triggered activation. b) Support setting the range of fault injection conditions. c) Cover common fault simulation components and their types in traction electric drive systems, including but not limited to traction converters, traction motors, traction control units, and sensors. d) Support adding, setting, deleting, and replacing fault models. - Algorithm testing: a) Support functional testing of control, monitoring, diagnostic, and isolation protection algorithms under fault injection. b) Support multi-fault injection testing capabilities. - Algorithm evaluation: a) Cover common evaluation indicators for the tested algorithms, including but not limited to quantitative and qualitative indicators. b) Suppo