Slave Device Boot Report for Master-Slave Communication Reconnection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In master-slave communication systems, such as those using the CAN bus, communication interruptions due to external interference or abnormalities can disrupt the connection between master and slave devices, requiring manual intervention for restoration.
Innovation Solution
A communication method where the slave device sends a boot report with identity information at power-up and continuously sends it at predetermined intervals if no heartbeat message is received from the master device for a predetermined time, allowing automatic reconnection once the connection is restored, utilizing the CANopen protocol for message types like BOOTUP and NMT state commands.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the slave device uses standard BOOTUP message sending at power-up only, then the communication protocol remains simple and standardized, but the communication connection cannot be automatically restored after interruption
Solution Approach 1:
The slave device is configured to continuously send BOOTUP messages at predetermined intervals after detecting communication interruption (when heartbeat messages are not received for a predetermined time). This preliminary action of continuously sending identification messages enables automatic reconnection when the master device recovers, resolving the contradiction by adding restoration capability without fundamentally changing the BOOTUP message protocol structure
Solution Approach 2:
The slave device autonomously detects communication status through heartbeat message monitoring and automatically initiates reconnection by sending BOOTUP messages without requiring manual intervention. This self-service mechanism improves reliability while maintaining protocol simplicity, as the device uses existing protocol elements (BOOTUP messages and heartbeat monitoring) rather than introducing complex new protocols
2Reliability
If the slave device continuously sends BOOTUP messages after communication interruption, then automatic reconnection is enabled, but message transmission frequency increases
Solution Approach 1:
The slave device sends BOOTUP messages at predetermined intervals rather than continuously without pause. This periodic action allows the device to balance automatic reconnection capability with energy conservation, as the communication module can enter low-power states between predetermined transmission intervals while still enabling restoration when needed
Solution Approach 2:
The slave device monitors heartbeat messages in advance to detect communication interruptions and only then initiates the periodic BOOTUP message sending. This preliminary detection mechanism ensures that increased message transmission occurs only when necessary, avoiding unnecessary energy consumption during normal communication operation
Data Source
Figure 1~2
Figure 3~4
AI summary
The present disclosure relates to a communication method for a slave device in a master-slave communication structure, comprising: sending a boot report to the master device at power-up to report that the slave device is booting, wherein the boot report includes identity information for the slave device; receiving a heartbeat message from the master device; and if no heartbeat message is received from the master device for more than a predetermined time, the boot report is continuously sent to the master device at predetermined intervals until a feedback message of successful connection is received from the master device. Further, the present disclosure relates to a communication method for a communication system having a master-slave communication structure, a communication device for a slave device in a master-slave communication structure, and a communication system having a master-slave communication structure.