Abstract
1. Introduction
With the progress of industrial modernization a large number of sensors and indicators need to be monitored in order to achieve the optimal production efficiency and product quality. Data is gathered either automatically over wired data acquisition systems [1] or in modern factories by wireless using wireless sensor networks and/or mobile robots for data collection [2–4].
When installing new sensors or troubleshooting existing sensors, engineers often need special measuring tools, such as oscilloscopes or more sophisticated sensor signal conditioning equipment, in order to check the correct operation of the industrial sensors. Such measuring equipment is often expensive and inflexible and can be used only for a specific type or brand of industrial sensors [5]. Moreover, most measuring tools have wired connection to the sensors; meaning each time the measurement must be carried out, the cables must be connected [6]. Each measuring tool has its own user-interface, which is often awkward and tool-specific. Such a measuring tool is used, for example, in the field of industrial signal conditioning of hydraulic systems and is shown in Figure 1. [7]

HYDAC HMG 3000 – mobile measurement device
In today's most sophisticated automation systems, such as manipulators, robots and mobile robots, there are numerous sensors, which are responsible for their correct operation. The causes of faults in such systems are hard to detect and isolate, especially if the error appears only during operation. Therefore, advanced algorithms are being developed for FDI (Fault Detection and Isolation) [8, 9]. Such algorithms often provide the operator with general error descriptions, for example ‘clamp error’ and do not provide the exact fault location within the subsystem. Maintenance personnel often use trial and error approaches to find out which component has failed. Such methods can be time consuming.
All the problems mentioned before can be dealt with by using a universal Bluetooth platform that can be connected to any industrial sensor without interfering with its normal operation; in other words, converting it to a wireless sensor. Data can then be collected wirelessly by any Bluetooth enabled smart device. This will enable maintenance personnel to detect the cause of the fault and isolate or fix it. Such a tool would come in especially handy for those machines with no automatic FDI mechanisms.
This paper presents and evaluates the Bluetooth platform and is organized as follows: Section 2 comprises a brief review of related works and the most commonly used wireless technologies. The first part of Section 3 presents the basic concept of the Bluetooth platform for wireless measurements and the second part deals with hardware, firmware and software implementations of the Bluetooth platform. The Bluetooth platform is tested in terms of range and throughput. The results and measurements are presented in Section 4, which is followed by a conclusion.
2. Related works
Wireless sensors have been extensively studied in literature over the last two decades. Most of the generally available sensors use one of the standard wireless communication protocols – Bluetooth (IEEE 802.15.1), ZigBee (IEEE 802.15.4) or Wi-Fi (IEEE 802.11) [10, 11]. There are numerous specific wireless sensor solutions available for different application areas. Most wireless sensor solutions have a built in transducer, signal conditioner and wireless radio. For examples see [12–16]. There are few solutions either for converting existing sensors to wireless, in such a way that we can still use them when wired as before [17, 18], or for making wireless data available to smart devices.
2.1 Brief overview of the most commonly used wireless communication standards
As mentioned before the most commonly used wireless communication protocols in the field of wireless sensor technology are Bluetooth, ZigBee and Wi-Fi. Each of them offers different advantages and also disadvantages. A comparison of the communication protocols is shown in Table 1.
Comparison of the wireless communication protocols [20]
ZigBee also uses 868 MHz band (1 channel) available in Europe only and 10 channels in 915 MHz band in North America only.
2.1.1 Wi-Fi
Wi-Fi uses a CSMA/CA (carrier sense multiple access with collision avoidance) access scheme, meaning that every Wi-Fi device should listen to the medium before transmitting. Transmission is allowed only if the medium is sensed to be idle. Wi-Fi networks operate over one of the 14 22 MHz wide channels defined for the 2.4 GHz ISM (industrial scientific and medical) band, meaning that no more than three networks can be simultaneously operated within the same area without interference [21].
2.1.2 ZigBee
Similarly to Wi-Fi, ZigBee devices use a CSMA/CA channel access algorithm and a 2.4 GHZ ISM band. The difference between the two is that ZigBee's channels are a lot narrower (just 2 MHz) and therefore do not overlap, meaning that 16 ZigBee networks can coexist within the same area. [21]
2.1.3 Bluetooth
Bluetooth is designed for cable replacement and connection-oriented services with low power consumption and short range operations. The output power and range depend on the device class (see Table 2).
Bluetooth device classes and theoretical range
Bluetooth uses 79 1 MHz wide channels within the 2402–2480 MHz frequency range. To reduce interference FHSS (frequency hopping spread spectrum) and AFH (adaptive frequency hopping) – since v1.2 – are used to spread the signal across all 79 channels. More Bluetooth networks can coexist within the same area by employing different hopping patterns. The Bluetooth channel access scheme is based on TDD (time division duplex). The master may start transmitting at even numbered slots and the slave at odd.
The low channel width and FHSS technique are fairly ineffective in contrast to Wi-Fi interference (one Wi-Fi channel pollutes 22 Bluetooth channels), resulting in a drastic Bluetooth signal degradation of up to 68%. [21]
3. Bluetooth platform for wireless measurements
Most modern smart devices have Bluetooth and Wi-Fi built-in and therefore no additional hardware is required for these two wireless protocols. This fact rules out ZigBee, which would need a special, device specific hardware or a Bluetooth or Wi-Fi to ZigBee converter. Such a converter would increase the complexity and latency of the connection and probably introduce some compatibility issues. Although Bluetooth is slower and has a smaller number of cell nodes compared to Wi-Fi, Bluetooth has been chosen as the appropriate protocol for wireless measurements. This is due to a practical reason. If a user wanted to measure sensor signals and browse the internet or log data to a remote server at the same time, the smart device would have to switch between a router with internet access and an AD-HOC wireless sensor network, which is unacceptable in such applications.
3.1 Basic concept
The basic idea of the platform is to add wireless access to existing industrial sensors so that data can be read wirelessly when needed, with no effect on the existing sensor connection. Figure 2 shows the basic idea of using the platform: 1. disconnect connected sensor, 2. add connector module and 3. connect sensor back via the connector module.

Basic concept of the Bluetooth platform for wireless measurements
The connector module only fits sensors with a certain type of connector, for example sensors with a DIN EN 175301-803 (former DIN 43650) from connector A. Other more commonly used industrial sensor connectors are shown in Figure 3.

More commonly used industrial sensor connectors
The connector module has a built in EEPROM, which stores all the sensor properties including name, description, measured quantity range, output signal range (e.g., 4 − 20 mA), etc. All the properties are defined on the first data acquisition. The main purpose of the connector module, along with sensor properties storage, is to enable hot-swap for the main module, meaning that the main module can be added or removed whilst the sensor is operating. Moreover, such a configuration is ideal for factories with a lot of sensors that need to be accessed wirelessly only when performing maintenance on a specific machine. On such a machine each sensor has its own connector module and the main module is added only to those sensors where wireless access is needed (Figure 4). This minimizes the cost by reducing the number of main modules needed.

Sensors with connector module installed – one with and one without the main module
If data from a specific sensor needs to be measured, the main module is connected to the connector module. Now wireless access to the sensor is available and data can be read using a smart device with built in Bluetooth and the appropriate application installed.
3.2 Hardware configuration
As described before there are two parts: the connector module and the main module.
3.2.1 The connector module
The connector module consists of three connectors; first one is used to connect the connector module to the sensor. Then the second connector of the opposite gender is used to connect the connector module with the signal cable. The third one is a DE-15 connector used for connection with the main module. Besides the two connectors, the connector module has a built in electronic signal routing between the three connectors and an EEPROM chip with I2C (Inter-Integrated Circuit) bus. The schematic outline of the connector module is shown in Figure 5.

Schematic outline of the connector module
There are several different types of connector modules: analogue connector modules, RS232 connector modules, digital input/output (DIO) connector modules, etc. The signal routing circuit differs from connector to connector. The signal routing circuit links the signal lines to the appropriate pin on the main module and contains a current sense resistor (analogue connector module) or RS232 to UART voltage level shifter (RS232 connector module) or transistors (DIO connector module). The connector module type is chosen depending on the sensor type and connector.
3.2.2 The main module
Configuration of the main module is a bit more complicated than the connector module. Its block diagram is shown in Figure 6. The main parts of the main module are the DC/DC converter (for efficient supply of power), the microcontroller unit (MCU), the Bluetooth module and the ADC (Analogue-Digital Converter).

Main module layout and block diagram
The heart of the main module is a MCU. The MCU is a Microchip dsPIC, running at 3.3 V and 20 MHz. The clock is provided by a crystal (XTAL) oscillator. The MCU features peripheral pin select technology, built in hardware ADCs, DACs (Digital-Analogue Converter), UART (Universal Asynchronous Receiver/Transmitter, I2C and SPI (Serial Peripheral Interface). The UART is used for communication with the Bluetooth module (red) and I2C (green) for communication with EEPROM and an external 16 bit ADC. 3 digital pins are used to drive LED indicators, which enable visualization of the main module status.
The most important part is the Bluetooth module. A Roving Networks RN-41 Class 1 Bluetooth module was chosen for this application. This is mostly because it is capable of connecting with all the smart devices available on the market, including Apple devices, which require an external authentication coprocessor. Moreover, the RN-41 automatically handles communication with an authentication coprocessor on a separate I2C bus (orange). RN-41 is connected to the MCU via the UART configured to a baud rate of 115200 Bd/s with RTS/CTS (Request to Send/Clear to Send) flow control, no parity and 1 stop bit (
The external ADC offers accurate 16 bit wide conversion with data rates of up to 7 kS/s, with built in averaging including voltage, current and power calculation. The gain error of the ADC is less than 0.1% and the ADC does not need any external voltage references. Moreover, the ADC is factory calibrated and therefore provides accurate voltage and current readings.
A DC/DC converter was preferred over a linear voltage regulator mainly due to better efficiency and wider input range. The power losses on the ideal linear voltage regulator (eq. 3) would be bigger than 1 W when being powered from 24 V line and transmitting (50 mA).
3.3 Firmware
Custom firmware has been developed for the platform. The firmware is written in C programming language using Microchip's Integrated Development Environment (IDE) called MplabX. The Mcrochip C30 compiler was used to compile the code and circuit debugger ICD3 was used to debug it. Firmware that is running on the MCU consists of initialization procedures for all the peripheral devices, an UART command parser/handler and a data acquisition timer. Both the UART command parser and the data acquisition timer are interrupt-driven, which reduces the number of checks that should be carried-out at each iteration of the main loop. A simplified flowchart of the firmware program is shown in Figure 7, where synchronous tasks are presented in blue and asynchronous (interrupt driven tasks) in orange. Interrupt Service Routine (ISR) gets called at the specified hardware event.

Firmware program flowchart
3.3.1 Communication protocol
A special protocol has been developed, which is used for communication between the main module and the software on the smart device. The protocol is a master/slave type, where the smart device acts as a master and the main module as a slave. This means that the main module may transmit only when the master wants it to. Available commands are divided into three groups: GET commands, SET commands and ACTION commands. Using the GET commands the software requests particular data from the main module, for example, the name of the sensor. SET commands are used to send data to the main module. ACTION commands are special commands that, for example, initiate data acquisition with a specific data rate.
The protocol uses the Bluetooth Serial Port Profile (SPP), which is based on the Bluetooth Core Protocol and RFCOMM protocol. Bluetooth Core Protocol is divided into four parts: The first part is Baseband Protocol (BP), which is used to control the Bluetooth radio. Link Management Protocol (LMP) is used to establish the link between Bluetooth devices. The third and one of the more important parts is the Logical Link Control and Adaptation protocol (L2CAP), which provides segmentation and the reassembly of on-air packets. The last part of the Bluetooth Core Protocol is the Service Discovery Protocol (SDP), which allows a device to discover services supported by other devices. Services are identified by a Universally Unique Identifier (UUID). In our case SDP discovers whether the SPP service is available. The RFCOMM protocol is used for serial cable emulation. Figure 8 shows the described protocol stack used in our Bluetooth measurement platform [22].

The Bluetooth platform protocol stack
3.3.2 Communication example
As soon as the main module and the smart device are connected the communication begins with a HELLO command sent by the smart device, which is always replied to with hello, which means that the main module is ready and the connector module is already configured properly. After that some information about the sensor and the connector module is read from the EEPROM of the connector module with the GCT (Get Connector Type), GNAME (Get NAME) and GDSC (Get DeSCription). Later on more values specific to each connector type are read. For an analogue connector module: GUNIT (Get UNIT), GLSB (Get Least Significant Bit), GK (Get slope (K)), GN (Get y-intercept (N)) and GST (Get Sample Time). All those values are required for correct calculation of the measured value. If we want to change the sample time (ST), the ST variable can be set using a SST command. As soon as the module is set to our needs, the measurement may be initiated by sending the START command. After the START command the module replies with 2 bytes (16 bits) of data each x ms as defined in ST variable. The measured value is calculated using slope and y-intercept values (which differ with sensor range) and the least significant bit (which differs with voltage or current measurement) (eq. 4).
The measurement is stopped using the STOP command. The communication example described above is shown in Figure 9.

Communication example between the Smart Device (SD) and the Main Module (MM)
3.4 Software
Good software is one that makes the hardware useful. Along with the basic functionality, the graphical user interface is the most important aspect of user satisfaction. The user interface should therefore be transparent, easy to navigate and use pleasing graphics. The whole concept of the user interface must be very intuitive. [23]
The used software is a custom made program that implements the described communication protocol. It is written in Java using Xcode IDE provided by Apple Inc. The Xcode features programming compiling, debugging and the simulation of the code and has a lot of built in objects and libraries, which simplify the development process.
Used software consists of the following segments:
Settings.
Cockpit (shown in Figure 10) - the area that shows all the data. Users can freely organize the cockpit and determine how the data will appear.
Event Manager - a place where all previous events (measurements) can be accessed. Measurements are organized by client, project and events.
Calculator - calculate all main industrial quantities (electrical, hydraulic, pneumatic …). • Reporter – report generation tool.

Software - Cockpit running on Apple iPad.
4. Test results
The range and throughput of the Bluetooth measurement platform was tested in order to prove its usability for industrial measurements and maintenance.
4.1 Range measurements
Range measurements were performed using the main module and a 3G version of Apple iPad 2. The maximum range is a range where iPad can still connect to the main module to send and receive data (the module responds properly to START and STOP commands). The delays and jitter were not measured. Range measurement results are presented in Table 3.
Range measurement results
Measurement 1 was taken in open space with line of sight (LoS) of the device through a window. Measurements 2 and 3 were taken in laboratory environments through different obstacles. A laboratory environment means that there are computers operating nearby and the area is polluted with at least one Wi-Fi computer network. Last of all an industrial environment measurement (4) was performed through the same walls as in measurement 3, with an 18 kW motor running on a frequency inverter between the main module and the iPad. Measurement 4 showed no range decrease compared to the office environment.
4.2 Throughput measurements
Throughput measurements were performed using the main module and a 3G version of Apple iPad 2. The measurement examined whether all the data had arrived from the main module to the iPad. The main module sampled the voltage signal with 16 bit accuracy and sent data over Bluetooth to the iPad. Four different sample rates were chosen for the test. Various obstacles had almost no effect on the throughput. The test was performed using the same commands as shown in Figure 9. The only difference was the sample rate, which was different for each measurement.
Table 4 shows the results of the throughput measurements. It was noticed that on sample rates greater than 500 S/s data loss was detected. For some reason the CTS signal of RN-41 had become high and disabled the transmission, which caused the UART TX FIFO buffer in the MCU to overflow. This might have happened because the RN-41 was unable to transmit all the data in time or the iPad was unable to receive all the data due to a bug in the benchmarking application.
Throughput measurement results
5. Conclusion
The main objective of this work was to develop a user friendly platform for wireless measurements based on Bluetooth wireless protocol that can be used with existing sensors. Such a system has many advantages, especially when maintaining and troubleshooting existing industrial machinery including robots. For most measurement systems the jitter, delays and communication breakdown are not a problem, as long as no data loss occurs and all the data can be read by the smart device. On the other hand, in safety critical or closed loop control applications, the delays or communication breakdowns would cause a problem and therefore such wireless systems cannot replace wired ones.
The measurement results have proved that the developed Bluetooth platform can be used for reliable industrial measurements with sample rates of up to 500 S/s. Therefore the platform could be a replacement for sophisticated sensor signal conditioning equipment in the near future, replacing the brand-specific equipment with the universal measurement system for all industrial sensors.
Some useful applications using the developed Bluetooth platform in robotics are briefly described and referenced below:
Such a platform can enable existing sensors to acquire data in remote places with no database access. Acquired data is collected using mobile robots in specific intervals [24, 25].
Enables robot interaction with sensors in close proximity. For example on nearby machines or other instruments. This is a need for maintenance robots, whether teleoperated, under supervisory control, or autonomous, especially if they are working in hazardous environments [26].
Enables fast and simple robotic tool change - no connection/disconnection of sensor cables [27].
Provides a wireless interface for all sensors in the field of factory automation including robots, resulting in simplified installation, reduced engineering efforts and eliminated cable wear and tear factors [28].
6. Further work
Future research plans are to perform a detailed measurement of the platform's performance within an industrial environment, including latency and jitter measurements [29]. If the measurements were to provide give satisfactory results, the time synchronizations of different channels would be implemented [30]. Moreover, the platform would firstly be tested using controlling actuators and later for closed loop control. If the platform is used for control, jitter, communication breakdown and security issues would have to be taken into account. For example, what to do if there is no data or there is large jitter from a closed control loop sensor; should the loop be stopped or continue running using the last received value? A lot of effort will be put into such intelligent fault detection and isolation systems in the future. Moreover, any existing security holes should be found and fixed to prevent unauthorized access via the main module to control loop properties and actuators. To ease the firmware update procedure, a bootloader on the MCU is planned. A bootloader would enable ‘over the air’ firmware updating on the main modules.
More connectors are also planned – for strain gauges, piezoelectric and CANbus sensors. Moreover, we want to add the possibility of powering the sensor and main module from a battery or solar cell, which would enable using any sensor as an autonomous wireless sensor.
