This shows you the differences between two versions of the page.
software:system-commander:quick-start-guide:quick-start-page-2 [2013/01/03 04:42] aaron [Quick Start Guide Page 2 - System Commander] |
software:system-commander:quick-start-guide:quick-start-page-2 [2013/01/09 04:53] (current) aaron [Port Testing] |
||
---|---|---|---|
Line 14: | Line 14: | ||
\\ | \\ | ||
{{ :software:system-commander:quick-start-guide:system_commander_firmware_raw.png?nolink |}} | {{ :software:system-commander:quick-start-guide:system_commander_firmware_raw.png?nolink |}} | ||
- | We will assume for this video that our hardware has all the latest firmware installed. For more details on how to update firmware, see our [[hardware:firmware-update|Firmware Updating page.]] | + | We will assume for this video that our hardware has all the latest firmware installed. For more details on how to update firmware, see our [[hardware:firmware-update|Firmware Updating page.]]\\ |
+ | [[http://www.youtube.com/watch?feature=player_detailpage&v=w-UwmiZx1cU#t=331s|Click here to see this section in a video guide.]] | ||
===== Automatic ID Conflict Resolution ===== | ===== Automatic ID Conflict Resolution ===== | ||
CommandFusion hardware communicates with each other over a peer-to-peer bus called CFLink. This bus requires each device to have a unique ID for communications - this ID is called the CFLink ID. From the factory, devices of the same model all come set to the same CFLink ID.\\ | CommandFusion hardware communicates with each other over a peer-to-peer bus called CFLink. This bus requires each device to have a unique ID for communications - this ID is called the CFLink ID. From the factory, devices of the same model all come set to the same CFLink ID.\\ | ||
Line 21: | Line 21: | ||
Unlike other control systems, during auto discovery System Commander will report any ID conflicts on the CFLink network and handle assigning unique ID’s to all conflicting devices.\\ | Unlike other control systems, during auto discovery System Commander will report any ID conflicts on the CFLink network and handle assigning unique ID’s to all conflicting devices.\\ | ||
{{ :software:system-commander:quick-start-guide:automatic_id_conflict_resolution.swf?700x394 |}} | {{ :software:system-commander:quick-start-guide:automatic_id_conflict_resolution.swf?700x394 |}} | ||
- | The end result is no more conflicts and a healthier CFLink network without having to manually connect individual devices to assign their ID. | + | The end result is no more conflicts and a healthier CFLink network without having to manually connect individual devices to assign their ID.\\ |
+ | [[http://www.youtube.com/watch?feature=player_detailpage&v=w-UwmiZx1cU#t=397s|Click here to see this section in a video guide.]] | ||
===== Basic Configuration of Device Properties ===== | ===== Basic Configuration of Device Properties ===== | ||
After devices have been discovered, you can click on them in the CFLink Devices tree to bring up their configuration options.\\ | After devices have been discovered, you can click on them in the CFLink Devices tree to bring up their configuration options.\\ | ||
Line 35: | Line 35: | ||
The reset button will force the device to reboot, whilst the refresh button will request the configuration properties from the device and update System Commander with the current details.\\ | The reset button will force the device to reboot, whilst the refresh button will request the configuration properties from the device and update System Commander with the current details.\\ | ||
- | {{ :software:system-commander:quick-start-guide:system_commander_basic_device_configuration.png?direct&600 |}} | + | {{ :software:system-commander:quick-start-guide:system_commander_basic_device_configuration.png?direct&600 |}}\\ |
+ | [[http://www.youtube.com/watch?feature=player_detailpage&v=w-UwmiZx1cU#t=442s|Click here to see this section in a video guide.]] | ||
===== Port Testing ===== | ===== Port Testing ===== | ||
Devices with control ports such as relays, I/O, IR or serial ports can be tested using the System Commander interface.\\ | Devices with control ports such as relays, I/O, IR or serial ports can be tested using the System Commander interface.\\ | ||
Line 48: | Line 48: | ||
\\ | \\ | ||
For IO ports, we can see their current input or output state, as well as trigger their output state when the port is configured in one of the output modes.\\ | For IO ports, we can see their current input or output state, as well as trigger their output state when the port is configured in one of the output modes.\\ | ||
- | {{ :software:system-commander:quick-start-guide:system_commander_port_testing_io.png?direct&600 |}} | + | {{ :software:system-commander:quick-start-guide:system_commander_port_testing_io.png?direct&600 |}}\\ |
+ | [[http://www.youtube.com/watch?feature=player_detailpage&v=w-UwmiZx1cU#t=510s|Click here to see this section in a video guide.]] | ||
===== Page 3 ===== | ===== Page 3 ===== | ||
This quick start guide is broken up into multiple pages. \\ | This quick start guide is broken up into multiple pages. \\ | ||
[[software:system-commander:quick-start-guide|<<Go back to page 1]] | [[software:system-commander:quick-start-guide:quick-start-page-3|Go Forward to Page 3>>]] | [[software:system-commander:quick-start-guide|<<Go back to page 1]] | [[software:system-commander:quick-start-guide:quick-start-page-3|Go Forward to Page 3>>]] |