TRS-ECU Interface Using CAN for Low-Battery Engine Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing transport refrigeration systems face inefficiencies in power consumption, redundancy, wiring complexity, and safety during non-running modes, particularly when using non-industrial engines like automotive engines, which affect battery drain and system reliability.
Innovation Solution
A transport refrigeration system (TRS) controller to engine control unit (ECU) interface is developed, incorporating a keyswitch connection, run signal connection, and CAN communication to manage engine operations, diagnostics, and power management, reducing current draw, eliminating redundancy, and enhancing safety by using existing engine sensors and wireless communication protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a non-industrial engine is integrated into the TRS without an ECU interface, then the system can operate in electrical mode, but battery current consumption increases and low voltage startability deteriorates
Solution Approach 1:
The ECU acts as an intermediary between the TRS controller and the engine, managing power consumption by controlling engine operations and enabling the system to operate in electrical mode without excessive battery drain. The ECU interface coordinates communication between the TRS controller and engine control systems, optimizing power usage during non-running modes.
2Ease of operation
If the TRS controller directly controls the engine without ECU interface, then control is direct, but safety against unintended startup is reduced
Solution Approach 1:
The ECU serves as a safety intermediary between the TRS controller and engine startup control. It receives commands from the TRS controller but independently verifies startup conditions using engine sensors (crankshaft position, oil pressure, temperature) before allowing engine startup, thereby preventing unintended startups while maintaining operational control.
3Reliability
If engine sensors are not integrated with the TRS controller, then the TRS system is independent, but engine diagnostics during electrical mode are not enabled
Solution Approach 1:
The ECU interface enables multi-functionality by allowing the TRS controller to access engine sensor data for both engine control and TRS operational decisions. The same ECU hardware and communication bus serve dual purposes: managing engine operations and providing diagnostic information to the TRS controller during electrical mode, eliminating the need for separate sensing systems.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
Embodiments of a TRS Controller to ECU interface are provided. The interface includes a TRS Controller connected to an ECU that is part of an engine. The interface includes a keyswitch connection that is configured to send a keyswitch message from the TRS Controller to the ECU, a run signal connection that is configured to send a run message from the TRS Controller to the ECU, and a CAN communication connection that is configured to provide two-way communication between the TRS Controller and the ECU.