CommandFusion Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== CFLink Bus Physical Specs ======
CFLink is an RS485, 5-wire bus, used to interconnect CommandFusion hardware to create a CFLink network.\\
It is a peer-to-peer bus, where all devices can talk directly to each other. There is no master-slave devices, all devices are equal priority.

===== Wiring =====
CFLink uses 5 wires as follows:

  - Isolated Ground
  - Data +
  - Data -
  - Power (9-30V DC)
  - Ground

The reason there are two grounds is to reduce noise interference and ground loops by isolating all data communication from the power supply.\\
The CFLink data is isolated even at board level to ensure high quality data integrity.\\
\\
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 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.\\

==== 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 =====

  * 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.
  * Less overheads costs - Expensive networking hardware such as ethernet switches are not required.
  * 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.

===== Peer to Peer Benefits =====

CFLink is a peer-to-peer (P2P) bus, which means every device on the network can communicate to any other device.\\
Whereas a master-slave bus requires a master device to handle all communication to slave devices.\\

P2P is beneficial in automation for the following reasons:

  * The system is not dependant on a single device to operate. In master-slave, if the master device fails for some reason, then the whole network goes down.
  * P2P bus on the other hand will continue to operate if any device fails.
  * 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.
CommandFusion Wiki

User Tools

Site Tools

Page Tools
