CommandFusion Wiki

Documentation Resources

User Tools

Site Tools


hardware:cflink:cflink-bus

Differences

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

Link to this comparison view

hardware:cflink:cflink-bus [2012/11/07 03:14]
jarrod
hardware:cflink:cflink-bus [2014/01/20 02:15] (current)
aaron
Line 17: Line 17:
 Any 5-core or greater cable can be used, including CAT5/6.\\ Any 5-core or greater cable can be used, including CAT5/6.\\
 \\ \\
-For CAT5/6, we recommend that two cores be used for Power and for ground, then core for each data and isolated ground (using a total of 7 cores).\\+For CAT5/6, we recommend that two cores be used for Power and two for ground, then one core for each data and isolated ground (using a total of 7 cores).\\
 This is to reduce the resistance in the power wiring.\\ This is to reduce the resistance in the power wiring.\\
 +
 +==== CFLink Power Calculator, Cabling Diagrams and Best Practices ====
 +For CFLink cabling diagrams, best practices and a power calculator, [[hardware:​cflink:​cflink-wiring-examples|see this page.]]
  
 ===== Benefits Over Ethernet ===== ===== Benefits Over Ethernet =====
Line 24: Line 27:
   * Longer runs - CFLink can run for over 1km without the need for repeaters.   * Longer runs - CFLink can run for over 1km without the need for repeaters.
   * Multiple wiring topologies - CFLink can be daisy chained, home run, star, or any combination of topologies.   * Multiple wiring topologies - CFLink can be daisy chained, home run, star, or any combination of topologies.
-  * Less overheads costs - Expensive networking hardware such as ethernet switches are not required. +  * Less overheads costs - Expensive networking hardware such as ethernet switches are not required, which is a significant cost in larger automation networks. 
-  * Simplified setup maintenance - A network administrator is not required to handle IP address ranges, conflicts, etc. ID conflicts can be automatically resolved via CFLink.+  * Fewer points of failure - The CFLink bus is not reliant on a single device to handle communication routing (see Peer to Peer details below), unlike Ethernet which can have many points of failure at routers, switches, etc
 +  * Simplified setup maintenance - A network administrator is not required to handle IP address ranges, conflicts, etc. CFLink ​ID conflicts can be automatically resolved via System Commander software. 
 +  * Separated from corporate networks - access to tightly controlled corporate networks is not required, meeting requirements for data security in corporate environments. 
 +  * Lower unit price - The final cost to customers is significantly reduced by removing the need for Ethernet stacks physically from the product and from firmware R&D costs. 
 +  * Can use [[hardware:​cflink:​cflink-wiring-examples|any 5 core or higher cable]], including CAT5/6, making it more install-friendly. Only 3 cores are required for data when local power is used at each end of the cable run.
  
 ===== Peer to Peer Benefits ===== ===== Peer to Peer Benefits =====
Line 38: Line 45:
   * The burden of processing all messages is not placed on a single device. All devices are smart enough to communicate with each other directly.   * The burden of processing all messages is not placed on a single device. All devices are smart enough to communicate with each other directly.
   * The devices are more affordable due to lower processing requirements of distributed intelligence.   * The devices are more affordable due to lower processing requirements of distributed intelligence.
 +
 +===== Why Choose CFLink? =====
 +[[http://​www.commandfusion.com/​blog/​2013/​10/​03/​an-overview-of-our-cflink-bus-why-choose-cflink|Read this blog post to learn more about why we chose CFLink.]]
hardware/cflink/cflink-bus.1352258048.txt.gz · Last modified: 2012/11/07 03:14 by jarrod