CommandFusion Wiki

Documentation Resources

User Tools

Site Tools


hardware:cflink:cflink-introduction

Differences

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

Link to this comparison view

hardware:cflink:cflink-introduction [2013/06/02 12:48]
jarrod
hardware:cflink:cflink-introduction [2014/02/20 11:57] (current)
jarrod [Commands and Replies]
Line 43: Line 43:
   * **<​TYPE>​** = 1 char, types are documented below.\\   * **<​TYPE>​** = 1 char, types are documented below.\\
   * **<​DEVICE>​** = 3 chars representing the model name of the device or type of port we are targeting (or the device/port type that the reply came from).\\   * **<​DEVICE>​** = 3 chars representing the model name of the device or type of port we are targeting (or the device/port type that the reply came from).\\
-  ​* The **<​DEVICE>​** name ''​CFX''​ can be used to target any device. It is useful for when you are sending a command that any device should respond to, ''​WHO''​ for example.\\+    ​* The **<​DEVICE>​** name ''​CFX''​ can be used to target any device. It is very useful for when you are sending a command that any device should respond to, ''​WHO''​ for example.\\ ​It is also useful when you don't need to know the exact device type receiving the command, such as for [[hardware:​cflink:​on-board-rs232-port-protocol|on-board COM ports]] which share a common protocol across all devices.\\ However, all //​replies/​notifications//​ will be sent with the correct 3 character device identifier for the device sending the data (''​CFX''​ is never used in replies except from bootloader notifications).
   * **<​COMMAND_NAME>​** = 3 chars representing the name of the actual command being performed.   * **<​COMMAND_NAME>​** = 3 chars representing the name of the actual command being performed.
- 
 ==== Queries ==== ==== Queries ====
  
hardware/cflink/cflink-introduction.1370177299.txt.gz ยท Last modified: 2013/06/02 12:48 by jarrod