Differences

This shows you the differences between two versions of the page.

--- hardware:cflink:cflink-bus-faults [2013/08/09 04:42]
aaron created
+++ hardware:cflink:cflink-bus-faults [2013/08/20 04:43] (current)
aaron
@@ Line 1: / Line 1: @@
 ====== CFLink Bus Faults ======
-<WRAP center round todo 20%>
+===== CFLink Faults - No ACK Received =====
-**Coming Soon**
+Messages from an individual sender to an individual recipient are typically acknowledged by the recipient to confirm that the message went through.  If the sender does not receive an expected ACK, it will send the packet again, up to 30 times.  As soon as it receives a valid ACK packet, the send message operation is complete and status is reported to the application.  If no ACK is received after all retries, the operation is terminated and fail status is reported (which the CFLink Fault is lit). To give you an example: The user sends a command to CFLink ID 0x30 which doesn’t exist through LANBridge. The LANBridge should have CFLink Fault LED lit as it will not receive any ACK after 30 retries.
-</WRAP>
+The CFLink Fault usually happens when:
+  - User carelessly transmits a message to a CFLink ID which doesn’t exist.
+  - User sets wrong ID in the Target Notification tab (in system Commander).
+===== Clearing The CFLink Fault Indicator =====
+The only way to clear the CFLink fault indicator is to power off the device, wait 30 seconds then power it back up.
+If the CFLink Fault still exists then the reason for the fault is still present. Check your rules etc.

CommandFusion Wiki