Actuator Controller Router for Redundant CAN Bus
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for providing redundant communications in Controller Area Networks (CAN) require multiple communication channels, increasing cost, weight, and complexity, and can lead to asynchronous operation of nodes due to latency differences and message-based protocols.
Innovation Solution
Implementing an actuator controller with dual communication ports and a router that routes messages based on addresses, allowing for redundant communication paths and synchronization information exchange between nodes, reducing the need for multiple communication channels and central controller involvement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple communication channels are used for redundant communications, then communication reliability is improved, but system complexity and cost increase
Solution Approach 1:
The patent combines multiple communication channels into a single CAN bus by implementing a virtual channel architecture where multiple logical communication paths are multiplexed over one physical bus. The controller and nodes use protocol-level multiplexing to distinguish between different communication channels through message identifiers and routing information, eliminating the need for separate physical channels while maintaining redundancy and reliability.
Solution Approach 2:
The single CAN bus is designed to serve multiple communication functions simultaneously by implementing a universal communication protocol that supports different message types, priorities, and routing patterns. The system can handle control commands, status reports, synchronization data, and redundant communications all through the same physical medium, making the bus multi-functional and replacing what would traditionally require multiple dedicated channels.
2Reliability
If multiple communication channels are used for redundant communications, then communication reliability is improved, but weight increases
Solution Approach 1:
The patent merges multiple communication channels into a single physical CAN bus, thereby eliminating the need for multiple separate cables and connectors. This consolidation significantly reduces the weight of the communication harness while maintaining redundant communication paths through logical channel differentiation at the protocol level.
3Device complexity
If message-based serial protocol is used, then device complexity is reduced, but synchronization precision deteriorates
Solution Approach 1:
The patent implements preliminary synchronization actions by embedding timing information and synchronization markers within the message stream before critical operations occur. The controller proactively sends synchronization messages and timing data in advance, allowing nodes to pre-synchronize their operations and maintain precise coordination despite the asynchronous nature of the message-based protocol.
Solution Approach 2:
The system incorporates feedback mechanisms where nodes report their timing status and synchronization state back to the controller through the same CAN bus. The controller uses this feedback to adjust timing parameters and send corrective synchronization messages, continuously refining synchronization precision while maintaining the simplicity of the message-based protocol.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
The subject matter of this specification can be embodied in, among other things, an actuator controller that includes a first communication node (301) associated with a first communication address, a first communication port (310), a second communication port (312) associated with a second communication address, and a router (314). The router (314) is responsive to messages received at the first communication port (310) and the second communication port (312) to route a first message received at the first communication port (310) and including the first communication address to the first communication node (301), route a second message received at the first communication port (310) and including the second communication address to the second communication port (312), and route a third message received at the second communication port (312) and including the first communication address to the first communication node (301).