BlueCluster+ Features
- fast
- simple configuration
- automatic network establishment
- fail-proof
Bluetooth nodes in extensive installations can work together to establish a multi-hop network, which is designed in the form of a tree structure. Communications between the central Bluetooth device and the external stations can be effected using several hops. The central Bluetooth device requires only a single Bluetooth connection using the Serial Port profile (SPP), a standard Bluetooth profile. This means almost any commercially available Bluetooth device can function as the central Bluetooth device. The “intelligence” required for establishing the network and communicating within the network is implemented within the Bluetooth nodes of the external station.
The BlueCluster+ network is established automatically as soon as the central device is started. It is quasi-static in nature, and all communications links between the external stations exist permanently. This means that the transfer of data can be effected without any delays being caused by establishing the requisite data links, and energy-saving modes of the central link can also be invoked.
No configuration efforts are required for installing an external system; specifically, it is not necessary to define the topology of the network. The multi-hop network permits access even to nodes that are not “visible” to the central Bluetooth device. Any changes in network topology (selection of a node, installation of new nodes) are recognized automatically, resulting in a fully automated reconfiguration of the network.
This solution can be used anywhere data are to be transmitted to a central data collection system over greater distances or via “invisible” terminal devices. A cluster can include up to a maximum of 250 devices.
Technical specifications BlueCluster+ network
| Range | Several kilometers across multiple nodes |
| New node search interval | Configurable, typically 1 minute |
| Linking to additional nodes | Typically 1:30 minutes in case of 1 minute search intervals |
| Linking timeout in case of malfunction | Configurable, typically 20 seconds |
| Network recovery | Typically 1:30 minutes |
| Time required to build network, 30-50 subscribers | Typically 2 to 3 minutes |
| Network recovery after External Control Unit (ECU) connection | < 10 seconds |
| Transmission latency per node | Typically 50 ms |
| Number of ECUs | Maximum of 4 |
| Number of nodes | Typically 30 to 40, maximum of 250 |
| Number of parallel networks | Maximum of 63 (with own network IDs) |
| ECU platforms | Windows (PC, CE), Linux, PDA, cell phone |

