<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xml:lang="en" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">Sensors</journal-id>
<journal-title>Sensors</journal-title>
<issn pub-type="epub">1424-8220</issn>
<publisher>
<publisher-name>Molecular Diversity Preservation International (MDPI)</publisher-name></publisher></journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.3390/s120810014</article-id>
<article-id pub-id-type="publisher-id">sensors-12-10014</article-id>
<article-categories>
<subj-group>
<subject>Article</subject></subj-group></article-categories>
<title-group>
<article-title>A Wireless Interface for Replacing the Cables in Bridge-Sensor Applications</article-title></title-group>
<contrib-group>
<contrib contrib-type="author">
<name><surname>Pavlin</surname><given-names>Marko</given-names></name><xref ref-type="aff" rid="af1-sensors-12-10014"><sup>1</sup></xref><xref ref-type="corresp" rid="c1-sensors-12-10014"><sup>*</sup></xref></contrib>
<contrib contrib-type="author">
<name><surname>Novak</surname><given-names>Franc</given-names></name><xref ref-type="aff" rid="af2-sensors-12-10014"><sup>2</sup></xref></contrib></contrib-group>
<aff id="af1-sensors-12-10014">
<label>1</label> In.Medica d.o.o., Levicnikova 34, 8310 Sentjernej, Slovenia</aff>
<aff id="af2-sensors-12-10014">
<label>2</label> Jozef Stefan Institute, Jamova 39, 1000 Ljubljana, Slovenia; E-Mail: <email>franc.novak@ijs.si</email></aff>
<author-notes>
<corresp id="c1-sensors-12-10014">
<label>*</label>Author to whom correspondence should be addressed; E-Mail: <email>marko.pavlin@inmedica.si</email>; Tel.: +386-7393-4959; Fax: +386-7393-4849.</corresp></author-notes>
<pub-date pub-type="collection">
<year>2012</year></pub-date>
<pub-date pub-type="epub">
<day>25</day>
<month>07</month>
<year>2012</year></pub-date>
<volume>12</volume>
<issue>8</issue>
<fpage>10014</fpage>
<lpage>10033</lpage>
<history>
<date date-type="received">
<day>18</day>
<month>06</month>
<year>2012</year></date>
<date date-type="rev-recd">
<day>13</day>
<month>07</month>
<year>2012</year></date>
<date date-type="accepted">
<day>16</day>
<month>07</month>
<year>2012</year></date></history>
<permissions>
<copyright-statement>© 2012 by the authors; licensee MDPI, Basel, Switzerland.</copyright-statement>
<copyright-year>2012</copyright-year>
<license>
<p>This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution license (http://creativecommons.org/licenses/by/3.0/).</p></license></permissions>
<abstract>
<p>This paper presents a solution in which a wireless interface is employed to replace the cables in bridge-sensor measurement applications. The most noticeable feature of the presented approach is the fact that the wireless interface simply replaces the cables without any additional hardware modification to the existing system. In this approach, the concept of reciprocal topology is employed, where the transmitter side acquires signals with its own transfer function and the receiver side reconstructs them with the transfer function reciprocal to the transmitter transfer function. In this paper the principle of data acquisition and reconstruction is described together with the implementation details of the signal transfer from the sensor to the signal-monitoring equipment. The wireless data communication was investigated and proprietary data-reduction methods were developed. The proposed methods and algorithms were implemented using two different wireless technologies. The performance was evaluated with a dedicated data-acquisition system and finally, the test results were analyzed. The two different sets of results indicated the high level of amplitude and the temporal accuracy of the wirelessly transferred sensor signals.</p></abstract>
<kwd-group>
<kwd>bridge-sensor measurements</kwd>
<kwd>wireless interface</kwd>
<kwd>reciprocal topology</kwd>
<kwd>sensor data integrity and reduction</kwd>
<kwd>comparative test methods</kwd>
<kwd>signal stream delay testing</kwd></kwd-group></article-meta></front>
<body>
<sec sec-type="intro">
<label>1.</label>
<title>Introduction</title>
<p>Cable connections can lead to difficulties in many sensor applications [<xref ref-type="bibr" rid="b1-sensors-12-10014">1</xref>–<xref ref-type="bibr" rid="b3-sensors-12-10014">3</xref>]. The key advantage of using wireless technologies in industrial, medical, environmental and other sensor applications is that they can significantly improve the flexibility and lower the costs associated with installing, maintaining, and upgrading wired systems [<xref ref-type="bibr" rid="b4-sensors-12-10014">4</xref>,<xref ref-type="bibr" rid="b5-sensors-12-10014">5</xref>]. The commercial promise of such solutions has been proved by the vast number of installed applications [<xref ref-type="bibr" rid="b6-sensors-12-10014">6</xref>] based on new standards, like IEEE802.15.4 [<xref ref-type="bibr" rid="b7-sensors-12-10014">7</xref>], and industrial collaborations, like the Zigbee Alliance [<xref ref-type="bibr" rid="b8-sensors-12-10014">8</xref>]. All these new installations and wireless sensor applications, which are often very application specific, require a new infrastructure or at least some degree of adaptation to implement the wireless sensor technology in industrial or other environments. Any adaptations or new installations may result in significant investments. Some specific environments are very sensitive with regard to the investments, and the costs of going wireless are not always justified [<xref ref-type="bibr" rid="b9-sensors-12-10014">9</xref>,<xref ref-type="bibr" rid="b10-sensors-12-10014">10</xref>]. A good example is hospitals, where sensors are used in intensive care. All those sensors, placed on or near the patient, are traditionally connected with wires to the monitoring equipment [<xref ref-type="bibr" rid="b11-sensors-12-10014">11</xref>]. However, monitors, even modern ones, have no standard wireless interfaces to connect to the sensors and the introduction of wireless sensors would require the replacement of the monitors [<xref ref-type="bibr" rid="b12-sensors-12-10014">12</xref>,<xref ref-type="bibr" rid="b13-sensors-12-10014">13</xref>].</p>
<p>In this paper we propose a solution in which a wireless sensor interface is employed to replace the cable connection of an existing measurement system. The salient feature of the proposed approach is that no adaptation or change to the sensor or to the measuring-equipment site is required. We developed reciprocal transmitter and receiver architecture which enables simultaneous multiple monitoring of a sensor signal. In a running system, only the data at the receiver are available, and the delay cannot be estimated. To solve this problem, a dynamic time-adaptation algorithm was developed. In the following we outline the advantages of the proposed topology and the requirements for its real life applications. In the second part of the paper we describe implemented prototypes and their operation in practice. The developed dynamic time-adaptation algorithm is demonstrated in the description of the signal time delay test evaluation.</p>
<p>While the presented solution can be applied to different passive bridge-sensor implementations and does not depend on a target application, we illustrate the advantage of the proposed approach on a case study of a blood-pressure monitor as a typical medical application. Test results were collected during clinical evaluation, which proved the commercial system based on presented concepts met the requirements of IEC-60601-1-2:34 {ed. 2.0} and base of the usability's requirements of the IEC 60601-1-6_2010 ed.3 and IEC 62366_2007 ed.1. The clinical trial was conducted under identifier NCT01373996.</p></sec>
<sec>
<label>2.</label>
<title>Bridge-Sensor Connections</title>
<p>Bridge resistors are primarily sensitive to the primary measured parameter (e.g., the pressure). The output signal, however, is also influenced by other parameters (e.g., the temperature), generating an error in the differential output voltage, which can be minimized by a compensation circuit or an algorithm. There are different implementations of bridge sensors. Amplifiers or even a complete microcontroller with temperature compensation and calibration can be integrated within a sensor. In this paper we focus on a Wheatstone-bridge configuration, which is common in many sensors operating on a resistance-change principle. They are (but not limited to) the following: piezoresistive pressure sensors, strain-gauge sensors, temperature bridge sensors, and many more.</p>
<p>A conventional bridge sensor is connected to the monitoring or measuring equipment with a minimum of a four-lead cable, as shown in <xref ref-type="fig" rid="f1-sensors-12-10014">Figure 1</xref>. The cables that are placed between the sensor and the process-automation equipment are sometimes difficult to install. Another limitation is the case when one process requires more than one measuring channel per sensing parameter. Such a case would require connecting one sensor to two instruments, which is not feasible with passive bridge sensors. The supply lines are either in short circuit, or the sensor bridge is not supplied by the correct instrument, which results in an incorrect readout. The above problems can be solved by replacing the cable with a wireless communication, as described in the following sections.</p>
<p>In most cases the equipment is a part of an existing infrastructure that is already installed, or there is a need to upgrade the system with some standard, additional instrumentation. Both cases have one common feature: the only accessible points are the external connections of the bridge sensors and the measurement instruments. Usually, there is no possibility to adapt the internal structure of the instruments to directly implement the use of any kind of wireless technology. The proposed wireless resistive-bridge sensor interface is suitable for a cable replacement in the existing systems and requires no modification of the measurement infrastructure.</p></sec>
<sec>
<label>3.</label>
<title>Wireless Cable-Replacement Interface for Bridge Sensors</title>
<p>The wireless resistive-bridge sensor interface integrated in an industrial or medical sensor system consists of transmitter and receiver units connected with a secure RF link within the unlicensed Industrial, Scientific and Medical (ISM) frequency band at 2.4 GHz (<xref ref-type="fig" rid="f2-sensors-12-10014">Figure 2</xref>).</p>
<p>A bridge-sensor element has a low differential voltage output. One typical example is a ceramic pressure sensor [<xref ref-type="bibr" rid="b14-sensors-12-10014">14</xref>]. Its sensitivity is in the range of mV/V at a full-scale input (ratio 1:1,000) [<xref ref-type="bibr" rid="b15-sensors-12-10014">15</xref>,<xref ref-type="bibr" rid="b16-sensors-12-10014">16</xref>]. Such low-level voltages introduce two issues that are specific to a wireless system.</p>
<p>First, at the transmitter side, the mV range from the sensor bridge is too low for the Analog-to-Digital Converter (ADC), which requires higher input-voltage levels, which means an amplifier with a gain G<sub>IA</sub> needs to be placed at the ADC converter input. The digital output stream from the transmitter is thus proportional to the amplified voltage, not to the mV output from the sensor bridge. In the subsequent discussion, however, let us denote the ratio between the transmitter output and the low-level sensor signal as the transmitter gain G<sub>TX</sub>.</p>
<p>The second issue is related to the receiver side. The Digital-to-Analog Converter (DAC) has an output voltage range from −V<sub>REF</sub> to +V<sub>REF</sub>. The reference voltage V<sub>REF</sub> has its lower limit, usually in the 1 V range. The received digital stream is fed to the DAC in the receiver unit. The transmitter ADC and the receiver DAC have the same resolution and operating range. Their digital ports are linked via the wireless interface. Ideally, the DAC will generate an output voltage, which is equal to the ADC input voltage (with equal reference voltages). To reconstruct the low voltage level at the receiver output, which is equal to the sensor-bridge output voltage, the receiver must have an attenuation that is reciprocal to the transmitter gain. If the receiver gain is represented by G<sub>RX</sub>, then the following condition must be met: G<sub>TX</sub> = (G<sub>RX</sub>)<sup>−1</sup>.</p>
<p>As shown in <xref ref-type="fig" rid="f2-sensors-12-10014">Figure 2</xref>, the wireless interface requires an additional signal-acquisition module with a sensor-bridge supply, two RF link modules and a signal-reconstruction module. The excitation voltage for the resistive sensor bridge is supplied by the transmitter unit. The sensor differential output voltage is amplified by an instrumentation amplifier (G<sub>IA</sub>), digitized by an ADC and processed by a microcontroller (μC). The wireless link is based on a standard wireless technology (Bluetooth, IEEE 802.15.4) with standard or proprietary protocols. The processed readouts are transmitted to the receiver side, which is connected to the measuring instruments or process automation equipment. The receiver RF link passes the received readouts to the microcontroller. The receiver unit mimics the sensor bridge with a multiplying DAC. The output voltage from the multiplying DAC is proportional to the digital word multiplied by the reference voltage. It operates in all four quadrants with negative or positive DC or AC reference voltages.</p>
<p>The described wireless interface provides an efficient solution to the problems mentioned above. It does not require any modification within the internals of the process equipment. Furthermore, one sensor can be connected to several measurement channels because there is only one sensor excitation. The operation of the proposed wireless sensor interface is described in the following sections.</p>
<sec sec-type="methods">
<label>3.1.</label>
<title>Transmitter Data Acquisition</title>
<p>The transmitter side of the wireless interface is connected to the resistive sensor bridge. The interface also provides an excitation voltage for the pressure transducers (<xref ref-type="fig" rid="f3-sensors-12-10014">Figure 3</xref>). Let the sensor-transfer characteristics be represented by the transfer function <italic>f(p)</italic>. The sensor bridge has a differential output voltage in the mV range, ratiometric to the supply voltage V<sub>CC</sub> (<xref rid="FD1" ref-type="disp-formula">Equation (1)</xref>):
<disp-formula id="FD1">
<label>(1)</label>
<mml:math id="mm1" display="block">
<mml:semantics id="sm1">
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mi>P</mml:mi></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:mi>P</mml:mi>
<mml:mn>1</mml:mn></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:mi>N</mml:mi>
<mml:mn>1</mml:mn></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>C</mml:mi>
<mml:mi>C</mml:mi></mml:mrow></mml:msub>
<mml:mi>f</mml:mi>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>p</mml:mi>
<mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>The output voltage <italic>V<sub>OUT</sub></italic> from the instrumentation amplifier is the sum of the amplified differential input voltage <italic>V<sub>P</sub></italic>, multiplied by the instrumentation amplifier gain <italic>G<sub>IA</sub></italic>, and the offset voltage <italic>V<sub>OFS</sub></italic>:
<disp-formula id="FD2">
<label>(2)</label>
<mml:math id="mm2" display="block">
<mml:semantics id="sm2">
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OUT</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>G</mml:mi>
<mml:mrow>
<mml:mi>I</mml:mi>
<mml:mi>A</mml:mi></mml:mrow></mml:msub>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mi>P</mml:mi></mml:msub>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>The instrumentation amplifier gain <italic>G<sub>IA</sub></italic> is determined and fixed by the resistor <italic>R<sub>G</sub></italic>. The offset voltage is proportional to the supply voltage and defined by the resistor divider <italic>R<sub>OFS1</sub></italic> and <italic>R<sub>OFS2</sub></italic> (<xref ref-type="fig" rid="f3-sensors-12-10014">Figure 3</xref>).
<disp-formula id="FD3">
<label>(3)</label>
<mml:math id="mm3" display="block">
<mml:semantics id="sm3">
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext>
<mml:mn>1</mml:mn></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>C</mml:mi>
<mml:mi>C</mml:mi></mml:mrow></mml:msub>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext>
<mml:mn>2</mml:mn></mml:mrow></mml:msub></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext>
<mml:mn>1</mml:mn></mml:mrow></mml:msub>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext>
<mml:mn>2</mml:mn></mml:mrow></mml:msub></mml:mrow></mml:mfrac></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>The amplifier output voltage is connected to the ADC. The reference voltage <italic>V<sub>REF</sub></italic> is derived from the supply voltage by the resistor divider <italic>R<sub>OFS1</sub></italic> and <italic>R<sub>OFS2</sub></italic> and is equal to the offset voltage <italic>V<sub>OFS</sub></italic>:
<disp-formula id="FD4">
<label>(4)</label>
<mml:math id="mm4" display="block">
<mml:semantics id="sm4">
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">REF</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>C</mml:mi>
<mml:mi>C</mml:mi></mml:mrow></mml:msub>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext>
<mml:mn>2</mml:mn></mml:mrow></mml:msub></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext>
<mml:mn>1</mml:mn></mml:mrow></mml:msub>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext>
<mml:mn>2</mml:mn></mml:mrow></mml:msub></mml:mrow></mml:mfrac></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>The 16-bit digital output value from the ADC is proportional to the ratio of the ADC input voltage and the reference voltage (<xref ref-type="fig" rid="f4-sensors-12-10014">Figure 4</xref>):
<disp-formula id="FD5">
<label>(5)</label>
<mml:math id="mm5" display="block">
<mml:semantics id="sm5">
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">ADC</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msup>
<mml:mn>2</mml:mn>
<mml:mrow>
<mml:mn>16</mml:mn></mml:mrow></mml:msup>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">INADC</mml:mtext></mml:mrow></mml:msub></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">REF</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:mfrac></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>Replacing <italic>V<sub>INADC</sub></italic> = <italic>V<sub>OUT</sub></italic> we obtain:
<disp-formula id="FD6">
<label>(6)</label>
<mml:math id="mm6" display="block">
<mml:semantics id="sm6">
<mml:mtable columnalign="left">
<mml:mtr>
<mml:mtd>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">ADC</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msup>
<mml:mn>2</mml:mn>
<mml:mrow>
<mml:mn>16</mml:mn></mml:mrow></mml:msup>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>G</mml:mi>
<mml:mrow>
<mml:mi>I</mml:mi>
<mml:mi>A</mml:mi></mml:mrow></mml:msub>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mi>P</mml:mi></mml:msub>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext></mml:mrow></mml:msub></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">REF</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:mfrac>
<mml:mo>=</mml:mo></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">ADC</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msup>
<mml:mn>2</mml:mn>
<mml:mrow>
<mml:mn>16</mml:mn></mml:mrow></mml:msup>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>G</mml:mi>
<mml:mrow>
<mml:mi>I</mml:mi>
<mml:mi>A</mml:mi></mml:mrow></mml:msub>
<mml:mi>f</mml:mi>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>p</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>+</mml:mo>
<mml:mi>α</mml:mi></mml:mrow>
<mml:mi>α</mml:mi></mml:mfrac></mml:mtd></mml:mtr></mml:mtable></mml:semantics></mml:math></disp-formula>where:
<disp-formula id="FD7">
<label>(7)</label>
<mml:math id="mm7" display="block">
<mml:semantics id="sm7">
<mml:mrow>
<mml:mi>α</mml:mi>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext>
<mml:mn>2</mml:mn></mml:mrow></mml:msub></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext>
<mml:mn>1</mml:mn></mml:mrow></mml:msub>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OFS</mml:mtext>
<mml:mn>2</mml:mn></mml:mrow></mml:msub></mml:mrow></mml:mfrac></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p><xref rid="FD6" ref-type="disp-formula">Equation (6)</xref> has no reference voltage, which means the ADC reference voltage could be an arbitrary value as long as it is within the ADC specification required by the ADC. This is true only when the sensor-bridge excitation and the ADC reference voltage are proportional or equal (<xref rid="FD4" ref-type="disp-formula">Equation (4)</xref>). Finally, the digital readouts <italic>N<sub>ADC</sub></italic> are buffered and transmitted via a wireless link (<xref ref-type="fig" rid="f4-sensors-12-10014">Figure 4</xref>).</p></sec>
<sec sec-type="methods">
<label>3.2.</label>
<title>Receiver Data Reconstruction</title>
<p>Digital readouts are transmitted to the receiver. The raw digital data <italic>N<sub>DAC</sub></italic> feeds the digital-to-analog converter with the same sampling rate as the ADC converter in the transmitter. The applied external reference input voltage <italic>V<sub>ref</sub></italic> determines the full-scale output voltage of the DAC converter:
<disp-formula id="FD8">
<label>(8)</label>
<mml:math id="mm8" display="block">
<mml:semantics id="sm8">
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">DAC</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">DAC</mml:mtext></mml:mrow></mml:msub></mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mn>2</mml:mn>
<mml:mi>M</mml:mi></mml:msup></mml:mrow></mml:mfrac>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">REF</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:semantics></mml:math></disp-formula>
<disp-formula id="FD9">
<label>(9)</label>
<mml:math id="mm9" display="block">
<mml:semantics id="sm9">
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">REF</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>C</mml:mi>
<mml:mi>C</mml:mi></mml:mrow></mml:msub>
<mml:mfrac>
<mml:mi>R</mml:mi>
<mml:mrow>
<mml:mi>β</mml:mi>
<mml:mi>R</mml:mi>
<mml:mo>+</mml:mo>
<mml:mo stretchy="false">(</mml:mo>
<mml:mn>1</mml:mn>
<mml:mo>−</mml:mo>
<mml:mi>β</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
<mml:mi>R</mml:mi></mml:mrow></mml:mfrac>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mn>1</mml:mn>
<mml:mn>2</mml:mn></mml:mfrac>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>C</mml:mi>
<mml:mi>C</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:semantics></mml:math></disp-formula>where 2<sup>M</sup> refers to the DAC resolution. The reference voltage is set to one half of the bridge supply voltage (V<sub>CC</sub>/2). The DAC output is connected to a fully differential amplifier. It has a differential input and a differential output (<xref ref-type="fig" rid="f5-sensors-12-10014">Figure 5</xref>).</p>
<p>The differential output voltage is generated by the differential driver with a rail-to-rail output. Its internal common-mode feedback architecture allows its output common-mode voltage to be controlled by the voltage applied to <italic>V<sub>M</sub></italic>. To implement the fully differential configuration the feedback resistors and attenuator resistors must match perfectly. One option is to select the resistors and sort them into several bins, which creates many problems when it comes to mass production. Another option is to use high-precision resistors, which raises the cost of the implementation. An optimal trade-off between the costs, the mass-production requirements and the performance could be implemented with a thick-film hybrid-circuit technology providing the ultimate match of the feedback network consisting of four resistors that determine the amplifier's closed-loop gain. The amplifier's differential output voltage (<xref ref-type="fig" rid="f5-sensors-12-10014">Figure 5</xref>) is defined as:
<disp-formula id="FD10">
<label>(10)</label>
<mml:math id="mm10" display="block">
<mml:semantics id="sm10">
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">ODIF</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>O</mml:mi>
<mml:mi>P</mml:mi></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>O</mml:mi>
<mml:mi>N</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>The common-mode output voltage is the average of the two voltages and is defined as:
<disp-formula id="FD11">
<label>(11)</label>
<mml:math id="mm11" display="block">
<mml:semantics id="sm11">
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">OCM</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>O</mml:mi>
<mml:mi>P</mml:mi></mml:mrow></mml:msub>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>O</mml:mi>
<mml:mi>N</mml:mi></mml:mrow></mml:msub></mml:mrow>
<mml:mn>2</mml:mn></mml:mfrac></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>The voltage gain of the single-ended-to-differential output topology can be derived from the signal definitions shown in <xref ref-type="fig" rid="f3-sensors-12-10014">Figure 3</xref>. The setting <italic>V<sub>OFS2</sub></italic> = 0 can be written as:
<disp-formula id="FD12">
<label>(12)</label>
<mml:math id="mm12" display="block">
<mml:semantics id="sm12">
<mml:mrow>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">DAC</mml:mtext></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>A</mml:mi>
<mml:mi>P</mml:mi></mml:mrow></mml:msub></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mi>G</mml:mi></mml:msub></mml:mrow></mml:mfrac>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>A</mml:mi>
<mml:mi>P</mml:mi></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>O</mml:mi>
<mml:mi>N</mml:mi></mml:mrow></mml:msub></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mi>F</mml:mi></mml:msub></mml:mrow></mml:mfrac>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>A</mml:mi>
<mml:mi>N</mml:mi></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>A</mml:mi>
<mml:mi>P</mml:mi></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>O</mml:mi>
<mml:mi>P</mml:mi></mml:mrow></mml:msub>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mrow>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mi>G</mml:mi></mml:msub></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mi>F</mml:mi></mml:msub>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mi>G</mml:mi></mml:msub></mml:mrow></mml:mfrac></mml:mrow>
<mml:mo>)</mml:mo></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>Solving the above <xref rid="FD10" ref-type="disp-formula">Equation (10)</xref> gives the gain relationship for <italic>V<sub>ODIF</sub>/V<sub>DAC</sub></italic>:
<disp-formula id="FD13">
<label>(13)</label>
<mml:math id="mm13" display="block">
<mml:semantics id="sm13">
<mml:mrow>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>O</mml:mi>
<mml:mi>P</mml:mi></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mi>O</mml:mi>
<mml:mi>N</mml:mi></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">ODIF</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>V</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">DAC</mml:mtext></mml:mrow></mml:msub>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mrow>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mi>F</mml:mi></mml:msub></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mi>G</mml:mi></mml:msub></mml:mrow></mml:mfrac></mml:mrow>
<mml:mo>)</mml:mo></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>An inverting configuration with the same gain magnitude can be implemented by simply applying the input signal to <italic>V<sub>OFS2</sub></italic> and setting <italic>V<sub>DAC</sub></italic> = 0. For a balanced differential input, the gain from <italic>V<sub>DAC</sub></italic> − <italic>V<sub>OFS2</sub></italic> to <italic>V<sub>ODIF</sub></italic> is also equal to <italic>R<sub>F</sub>/R<sub>G</sub></italic>.</p>
<p>The advantages of the proposed topology can be summarised as follows:
<list list-type="simple">
<list-item>
<label>-</label>
<p>there is no need for accurate (and costly) voltage references in the transmitter or receiver,</p></list-item>
<list-item>
<label>-</label>
<p>an additional receiver or transmitter calibration is not needed with a mindful circuit design,</p></list-item>
<list-item>
<label>-</label>
<p>the signal reconstruction operates equally as a Wheatstone bridge in all four quadrants.</p></list-item></list></p>
<p>A disadvantage of the presented solution is that it requires a highly matched resistor network. There are other types of amplifiers, which can be deployed in this circuit and are commonly used. One is differential amplifier implemented with singe operational amplifier. True instrumentation amplifiers with three or two operational amplifiers may be implemented. They all amplify differential signals with good rejection of common mode input voltages. The latter two are popular for discrete implementation having lower requirements on resistors. Since our amplifier circuit is implemented in a thick film hybrid circuit technology, the resistor matching is not an issue, because they are all precisely laser trimmed.</p></sec>
<sec sec-type="methods">
<label>3.3.</label>
<title>Data Reduction</title>
<p>The performance of a battery-operated wireless device depends on the energy efficiency. One of the main consumers of the energy in the battery is the RF link. The transmitter's power efficiency could be maximised by minimizing the RF link's active time. The active time starts with the transition from a low power state to the active state. This period is followed by a data-transmission interval. Finally, the RF link needs some time to switch from the active mode back to the sleep mode. The transition intervals are significantly shorter than the active transmission. The main focus in minimizing the RF link's power consumption should be during the active period. The easiest way to reduce the power consumption of the RF transmitter is to reduce the bandwidth of the RF link by sending less data without losing performance.</p>
<p>During the system design, it is necessary to define the required system resolution δ<sub>X</sub> and the operating range (<italic>x<sub>MAX</sub></italic>−<italic>x<sub>MIN</sub></italic>). Both parameters define the minimum number of bits required to store any value within the operating range:
<disp-formula id="FD14">
<label>(14)</label>
<mml:math id="mm14" display="block">
<mml:semantics id="sm14">
<mml:mrow>
<mml:msub>
<mml:mi>M</mml:mi>
<mml:mi>S</mml:mi></mml:msub>
<mml:mo>&gt;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mo>log</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msub>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>x</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">MAX</mml:mtext></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>x</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">MIN</mml:mtext></mml:mrow></mml:msub></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>δ</mml:mi>
<mml:mi>X</mml:mi></mml:msub></mml:mrow></mml:mfrac></mml:mrow></mml:semantics></mml:math></disp-formula>where <italic>M<sub>S</sub></italic> is the smallest number of bits.</p>
<p>Another possible solution to reduce the amount of data being transmitted is data compression. However, the lossless compression of a continuous data stream is a challenging task for a resource-limited embedded microcontroller. The compression method should conform to the restrictions imposed on the processing power and the memory resources. The best method to reduce data rate is to use a custom data format with a resolution equal to <italic>M<sub>S</sub></italic>. The data reduction is then implemented as simple bit-manipulation, where all the processing remains within the microcontroller register file. In our implementation we used half-precision 16-bit floating-point numbers using 1 sign bit, a 5-bit excess-15 exponent and 10 mantissa bits, in accordance with IEEE Std 754-2008 [<xref ref-type="bibr" rid="b17-sensors-12-10014">17</xref>].</p></sec>
<sec sec-type="methods">
<label>3.4.</label>
<title>Data Integrity</title>
<p>Replacing a cable with a wireless interface presents new challenges for the field of data integrity. It is not uncommon to be faced with issues relating to the integrity of readouts transmitted via a wireless interface. This wireless interface is usually small in size and has limited computing capabilities. With some safety-critical applications, like healthcare, data integrity ranks high in the core requirements. Wrong decisions caused by invalid data may harm someone's health or even result in the death of a patient. One such example is wireless blood-pressure monitoring. When used, e.g., in a critical-care unit, many decisions are based on instruments' readouts. If the blood pressure displayed by the patient's monitor is wrong, the patient could receive the wrong treatment, resulting in a critical state. In such cases, it is better not to transfer any data at all than present data that might be invalid. With this in mind, three levels of error detection were implemented: sequence-number checking, control-byte error checking and the checksum calculation. The whole data frame structure is shown in <xref ref-type="fig" rid="f6-sensors-12-10014">Figure 6</xref>.</p>
<p>At the upper level, a sequential freshness security service is employed. Sequential freshness maintains an ordered sequence of received frames. When a frame is received, the freshness value is compared with the last known freshness value. If the freshness value is newer than the last known value, the check has passed, and the freshness value is updated to the new value. If the freshness value is not newer than the last known freshness value, the check has failed. This service provides evidence that the received data are newer than the last data received by that device.</p>
<p>The frame control byte (FCB) represents the essential part of an application frame. The bit pattern within the FCB defines the type of payload or serves as a special command, like data-acknowledge, data-acquisition start and stop, <italic>etc.</italic> The FCB is divided in two 4-bit symbols. The FCB error detection is provided with 4-bit to 8-bit coding. There are only 16 valid byte codes for each 4 bit half of the FCB. Each symbol is coded with an 8-bit code. Finally, the check sum calculation is operated over the complete frame and added at the end of the frame. Each data frame has control structures with a data payload (<xref ref-type="fig" rid="f6-sensors-12-10014">Figure 6</xref>). Some special frames such as reception acknowledge or command strobes have no data payload.</p></sec></sec>
<sec>
<label>4.</label>
<title>System Evaluation</title>
<sec>
<label>4.1.</label>
<title>Implemented Prototypes</title>
<p>The wireless-sensor interface shown in <xref ref-type="fig" rid="f2-sensors-12-10014">Figure 2</xref> was implemented with two different wireless technologies. The first set was implemented on IEEE 802.15.4 transceivers based on the CC2400 from TI/Chipcon (<xref ref-type="fig" rid="f7-sensors-12-10014">Figure 7(a)</xref>). The second pair was implemented with standard Bluetooth WT12 modules from Bluegiga (<xref ref-type="fig" rid="f7-sensors-12-10014">Figure 7(b)</xref>).</p>
<p>The main reason for the implementation with two different wireless technologies was their evaluation for industrial and medical applications. They are both some of the most commonly used in a variety of applications. IEEE 802.15.4 is preferred in industrial applications, like ZigBee and similar protocols. Medical applications are more Bluetooth oriented.</p>
<p>The following table presents the main characteristics of the two wireless technologies that are relevant for the selection of a target application. The data gathered in <xref ref-type="table" rid="t1-sensors-12-10014">Table 1</xref> could be used as a guideline when selecting the optimum wireless technology. The final decision, however, also depends on other factors, like availability, legal and safety compliance with medical or industrial applications, <italic>etc.</italic></p></sec>
<sec>
<label>4.2.</label>
<title>Evaluation Procedure</title>
<p>In order to evaluate the performance of the developed wireless interface for replacing cables in bridge-sensor applications, a dedicated data-acquisition system was constructed. The clinical evaluation system (<xref ref-type="fig" rid="f8-sensors-12-10014">Figure 8</xref>) schematic is shown in <xref ref-type="fig" rid="f9-sensors-12-10014">Figure 9</xref>. The pressure was generated using a programmable pressure source for laboratory testing, while real live signals from different patients were taken during clinical trial. The calibrated pressure sensor S was used for the reference electrical signal. The output voltage from sensor S was connected to the transmitter unit and served as a reference signal <italic>p<sub>T</sub></italic>. The same signal was directly connected to the data-acquisition system. The transmitter output signal was wirelessly transmitted to several receiver units simultaneously. All the receiver signals <italic>p<sub>R1</sub>, p<sub>R2</sub> p<sub>RN</sub></italic> were measured with dedicated channels in the DAQ.</p>
<p>The purpose of the study was to determine whether the wireless transmission of pressure signals from the sensor to the data-acquisition system is feasible, safe and as accurate as a conventional cable connection. The analysis was made by comparing pressure-signal pairs <italic>p<sub>T</sub></italic> and <italic>p<sub>Ri</sub></italic> (<italic>i</italic> = <italic>1, …,N</italic>). Each signal was sampled and stored in files over a long period of time. The sampling frequency was twice the sampling frequency of the wireless interface, which resulted in huge data files. The gathered data was, therefore, analyzed offline.</p>
<p>As shown in <xref ref-type="fig" rid="f10-sensors-12-10014">Figure 10</xref>, the signal <italic>p<sub>R</sub></italic> is delayed after the signal <italic>p<sub>T</sub></italic>. The wireless-data connection is not ideal; it exhibits some error in the time and the amplitude. In addition, the delay time and the amplitude error between the signals may change over time [<xref ref-type="bibr" rid="b18-sensors-12-10014">18</xref>]. The main reason for the time-delay variability is the difference in the internal clocks between the transmitter and the receiver unit (<xref ref-type="fig" rid="f10-sensors-12-10014">Figure 10</xref>). The amplitude error is caused by component tolerances in the transmitter acquisition and receiver reconstruction circuits.</p></sec>
<sec>
<label>4.3.</label>
<title>Testing Method</title>
<p>The wireless interface was measured with the DAQ system over a one-day period. As mentioned above, the measurement resulted in an enormous amount of data that was stored in huge files. It was not possible to perform the evaluation on a sample-by-sample basis [<xref ref-type="bibr" rid="b19-sensors-12-10014">19</xref>]. To handle such long data records, it is necessary to split the long data record into segments of a manageable size. In order to evaluate the quality of the wireless data transmission a dedicated, multiple-step data-extraction and evaluation algorithm was developed. The principle of the algorithm is sketched in <xref ref-type="fig" rid="f11-sensors-12-10014">Figure 11</xref>.</p></sec>
<sec sec-type="methods">
<label>4.4.</label>
<title>Data-Extraction and Evaluation Algorithm</title>
<p>The acquired test-results file contains two sets of data: <italic>p<sub>T</sub></italic> from the transmitter side and <italic>p<sub>R</sub></italic> from the receiver side. Both signals were sampled simultaneously, although they are not correctly aligned due to the delay induced by the wireless system. The first step in the algorithm is the extraction of segments that are suitable for analysis. The segment size was determined in a preliminary analysis that considered two criteria. The first one was the trade-off between the number of segments and the computational speed: shorter segments require a shorter processing time. On the other hand, this would result in a larger number of segments, which is more difficult to handle. The second criterion was related to the duration time of the segmented data. The programmable pressure source generated a periodic signal. To keep the analysis consistent at least two input signal periods should be present in a single segment. Consequently, one whole period of the transmitter periodic signal <italic>p<sub>T</sub></italic> lies between the segment array indexes <italic>a</italic> and <italic>a</italic> + <italic>N</italic>, as shown in <xref ref-type="fig" rid="f11-sensors-12-10014">Figure 11</xref>.</p>
<p>The corresponding samples appear in the receiver signal <italic>p<sub>R</sub></italic> between indices <italic>b</italic> and <italic>b</italic> + <italic>N</italic> as an approximate and a delayed approximate of the signal <italic>p<sub>T</sub></italic>. In order to calculate the difference between the two signals, they must be aligned in time. This is done by shifting the output signal back until the shapes fit. In order to determine the actual error induced by the wireless system, the two signals must be perfectly aligned. The index <italic>b</italic>, which represents the start of the transmitted signal within the received array, is not known. The difference between the indices <italic>a</italic> and <italic>b</italic> (see <xref ref-type="fig" rid="f11-sensors-12-10014">Figure 11</xref>) characterizes the time delay and is determined by calculating the cross-correlation between the two signals.</p>
<p>Let the extracted segments of the signals <italic>p<sub>T</sub></italic> and <italic>p<sub>R</sub></italic> be represented by the arrays:
<disp-formula id="FD15">
<label>(15)</label>
<mml:math id="mm15" display="block">
<mml:semantics id="sm15">
<mml:mrow>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mi>T</mml:mi></mml:msub>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mo>=</mml:mo>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>T</mml:mi>
<mml:mi>a</mml:mi></mml:mrow></mml:msub>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>T</mml:mi>
<mml:mi>a</mml:mi>
<mml:mo>+</mml:mo>
<mml:mn>1</mml:mn></mml:mrow></mml:msub>
<mml:mo>,</mml:mo>
<mml:mo>…</mml:mo>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>T</mml:mi>
<mml:mi>a</mml:mi>
<mml:mo>+</mml:mo>
<mml:mi>N</mml:mi></mml:mrow></mml:msub></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula>and:
<disp-formula id="FD16">
<label>(16)</label>
<mml:math id="mm16" display="block">
<mml:semantics id="sm16">
<mml:mrow>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mi>R</mml:mi></mml:msub>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mi>j</mml:mi>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mo>=</mml:mo>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>R</mml:mi>
<mml:mi>b</mml:mi></mml:mrow></mml:msub>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>R</mml:mi>
<mml:mi>b</mml:mi>
<mml:mo>+</mml:mo>
<mml:mn>1</mml:mn></mml:mrow></mml:msub>
<mml:mo>,</mml:mo>
<mml:mo>…</mml:mo>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>R</mml:mi>
<mml:mi>b</mml:mi>
<mml:mo>+</mml:mo>
<mml:mi>N</mml:mi></mml:mrow></mml:msub></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula>where <italic>a</italic> is the starting index and <italic>N</italic> is the segment length limiting the transmitter-segment boundaries. The corresponding segment in the receiver signal is denoted by the index <italic>b</italic> and the equal length <italic>N</italic> (see <xref ref-type="fig" rid="f11-sensors-12-10014">Figure 11</xref>).</p>
<p>The array segment within the receiver signal array is shifted back in time:
<disp-formula id="FD17">
<label>(17)</label>
<mml:math id="mm17" display="block">
<mml:semantics id="sm17">
<mml:mrow>
<mml:msubsup>
<mml:mi>p</mml:mi>
<mml:mi>R</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mi>j</mml:mi>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mi>R</mml:mi></mml:msub>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mo>−</mml:mo>
<mml:mi>k</mml:mi></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula>where the array shift is denoted by the lag difference <italic>k</italic>. The maximum <italic>k</italic> is related to the buffering mechanism of the wireless system and is proportional to the buffer width. The signal delay is determined by calculating the normalized cross-correlation between the segments <italic>p<sub>T</sub></italic> and <italic>p</italic>′<italic><sub>R</sub></italic> at all the expected values of <italic>k</italic>. The normalized cross-correlation between the two arrays is defined as:
<disp-formula id="FD18">
<label>(18)</label>
<mml:math id="mm18" display="block">
<mml:semantics id="sm18">
<mml:mrow>
<mml:mi>ρ</mml:mi>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mi>T</mml:mi></mml:msub>
<mml:mo>⊗</mml:mo>
<mml:msubsup>
<mml:mi>p</mml:mi>
<mml:mi>R</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>The delay <italic>k</italic> = <italic>b</italic> − <italic>a</italic> is defined as the lag for which the normalized cross-correlation has the largest absolute value <italic>ρ<sub>MAX</sub></italic>. At this point, the two signals closely resemble each other. In reality, the wireless system adds some errors in amplitude. Some variation in the time delays of the individual segments is also apparent due to the dynamic clock handling of the internal buffering mechanism. The resulting small amplitude errors and time-delay deviations, however, provide sufficient correlation between the pair of the delayed signal, as shown in <xref ref-type="fig" rid="f12-sensors-12-10014">Figure 12</xref>.</p>
<p>The last step, shown in <xref ref-type="fig" rid="f11-sensors-12-10014">Figure 11</xref>, is the evaluation. The result of the evaluation process is a single value, calculated from the aligned signal segments for each evaluated parameter (<italic>i.e.</italic>, amplitude error, time delay).</p>
<p>The first evaluation stems from the mean difference between the signals. The difference array <italic>δ</italic>[<italic>i</italic>] is calculated by subtracting the corresponding elements from the aligned signal arrays:
<disp-formula id="FD19">
<label>(19)</label>
<mml:math id="mm19" display="block">
<mml:semantics id="sm19">
<mml:mrow>
<mml:mi>δ</mml:mi>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mo>=</mml:mo>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>R</mml:mi>
<mml:mi>c</mml:mi></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>T</mml:mi>
<mml:mi>a</mml:mi></mml:mrow></mml:msub>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>R</mml:mi>
<mml:mi>c</mml:mi>
<mml:mo>+</mml:mo>
<mml:mn>1</mml:mn></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>T</mml:mi>
<mml:mi>a</mml:mi>
<mml:mo>+</mml:mo>
<mml:mn>1</mml:mn></mml:mrow></mml:msub>
<mml:mo>,</mml:mo>
<mml:mo>…</mml:mo>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>R</mml:mi>
<mml:mi>d</mml:mi></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>p</mml:mi>
<mml:mrow>
<mml:mi>R</mml:mi>
<mml:mi>b</mml:mi></mml:mrow></mml:msub></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>The new array <italic>δ</italic>[<italic>i</italic>] is the source for the first evaluator <italic>δ̄</italic>. It is calculated as an average value of the array <italic>δ</italic>[<italic>i</italic>]:
<disp-formula id="FD20">
<label>(20)</label>
<mml:math id="mm20" display="block">
<mml:semantics id="sm20">
<mml:mrow>
<mml:mover accent="true">
<mml:mi>δ</mml:mi>
<mml:mo>¯</mml:mo></mml:mover>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mn>1</mml:mn>
<mml:mrow>
<mml:mi>b</mml:mi>
<mml:mo>−</mml:mo>
<mml:mi>a</mml:mi></mml:mrow></mml:mfrac>
<mml:munderover>
<mml:mo>∑</mml:mo>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mo>=</mml:mo>
<mml:mi>a</mml:mi></mml:mrow>
<mml:mi>b</mml:mi></mml:munderover>
<mml:mrow>
<mml:mi>δ</mml:mi>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mi>j</mml:mi>
<mml:mo>]</mml:mo></mml:mrow></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<p>The signal difference evinces a systematic amplitude error. Its value represents the actual quality of the wireless transmission system. This should be kept within acceptable limits, defined by the required system accuracy.</p>
<p>The second evaluator is the time delay. The difference between the indices <italic>a</italic> and <italic>b</italic> is transformed into time. The time between two samples within the signal array is defined by the sampling frequency <italic>f<sub>S</sub></italic>. The time delay <italic>D</italic> between the signals of the observed segments is calculated by:
<disp-formula id="FD21">
<label>(21)</label>
<mml:math id="mm21" display="block">
<mml:semantics id="sm21">
<mml:mrow>
<mml:mi>D</mml:mi>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mi>b</mml:mi>
<mml:mo>−</mml:mo>
<mml:mi>a</mml:mi></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>f</mml:mi>
<mml:mi>S</mml:mi></mml:msub></mml:mrow></mml:mfrac></mml:mrow></mml:semantics></mml:math></disp-formula></p>
<sec>
<title>Acceptance Criteria for the System Evaluation</title>
<p>The system requirements were based on the general requirements commonly seen in industrial applications. The overall accuracy of the wireless system was set to 1% full scale. In our case, the system operated at a full scale of ±400 kPa. Accordingly, the evaluator <italic>δ̄</italic> should remain within ±4 kPa. In order to detect any possible anomalies a verification run of 24 hours was planned.</p>
<p>As regards the time delay between the signals, the requirement was to keep it below 1 s. In addition, the time delay should not change rapidly to avoid signal distortion. A separate mechanism for detection of the rapid time-delay changes is not required since the deviation would result in a significant output-signal distortion. This would consequently scale the evaluator <italic>δ̄</italic> above an acceptable level. Therefore, only a time delay was observed during the 24 hour test. Both acceptance criteria are shown in <xref ref-type="table" rid="t2-sensors-12-10014">Table 2</xref>.</p></sec></sec>
<sec sec-type="results">
<label>4.5.</label>
<title>Test Results</title>
<sec>
<label>4.5.1.</label>
<title>Signal Time Delay</title>
<p>Three sensor pairs were used during the testing, marked as sensor pairs #1, #2 and #3. The first tested parameter was the signal time delay. One transmitter was connected to three receivers at the same time and the delay between the signals was measured.</p></sec>
<sec>
<label>4.5.2.</label>
<title>Signal Time-Delay Variation</title>
<p>The internal algorithms within the communication stack compensate the time deviations between the transmitter and each of the three receivers. The transmitter/receiver pair operates at slightly different frequencies. When sampling is not exactly synchronized, one of the devices will face buffer over- or under-flow, either in acquisition or reconstruction. To overcome this problem, a dynamic time-adaptation algorithm was implemented. Since there is only one transmitter in the system, its internal clock served as the reference to all the connected receivers. Each receiver has its own buffer under- and over-flow detection algorithm. When one of the receivers runs slower than the transmitter, its reconstruction buffer gets overflowed by the samples received from the transmitter. To detect the buffer overflow, the available buffer space is evaluated. When the available buffer space is lower than a predefined level, the receiver's internal reconstruction clock is accelerated until sufficient buffer space is available. A similar situation occurs when the receiver runs faster than the transmitter. Over some time, the receiver's reconstruction buffer will underflow (<italic>i.e.</italic>, the transmitter will not provide enough readouts for the reconstruction). When such a situation is detected, the receiver's internal reconstruction clock is adjusted to run slower than the transmitter until the buffer recovers.</p>
<p>A saw-tooth shape of the time delay (<xref ref-type="fig" rid="f13-sensors-12-10014">Figure 13</xref>) occurs as a result of the time-deviation compensation. Notice that the measured time delay is well within the required range given in <xref ref-type="table" rid="t2-sensors-12-10014">Table 2</xref>.</p></sec>
<sec>
<label>4.5.3.</label>
<title>System Accuracy</title>
<p>The average signal difference between the signals p<sub>T</sub> and p<sub>R</sub> (expression 20) was measured next. The results for the three sensor pairs are shown in <xref ref-type="fig" rid="f14-sensors-12-10014">Figure 14</xref>. The reference pressure was a periodic signal within the system's operating range. The experiment with the three receivers connected to one transmitter was running for 24 hours. Data was recorded during that time with a sampling frequency of 250 Hz. The analysis was carried out off-line. As shown in <xref ref-type="fig" rid="f14-sensors-12-10014">Figure 14</xref>, the requirement for the error band to be within ±4 kPa, which is ±1% of full scale, was met. The achieved statistics indicates a good system performance, even between ±1 kPa. Some sparse outliers have no impact on the target system application.</p></sec></sec></sec>
<sec sec-type="conclusions">
<label>5.</label>
<title>Conclusions</title>
<p>The main idea of this work was to investigate the possibility of implementing a wireless replacement for a sensor-bridge cable. We were able to prove the concept of an inverted topology. All the test results were obtained directly from theoretical calculations, without any additional calibration. The overall performance was within the requirements, despite a small systematic error, which was about a decade lower than the required tolerances. The concept was tested with the same results, using several receiver/transmitter pairs. This confirmed the idea of the inverted topology and validated it for mass production. The presented solution is currently integrated within a series production for a medical application.</p>
<p>Beyond the raw sensor-signal manipulation over the wireless link, we implemented additional mechanisms for sensor data integrity, compression and time synchronization. The data integrity mechanism keeps the transferred data valid, authentic and consistent with the process measurement. It was validated during testing. Any failure to bring consistent data via a wireless link would result in a measurable error, because the measurement system compared the received signals to the reference signals at the transmitter input. There was no error detected during 24 hours of operation, which sustained data integrity at a high level.</p>
<p>The data compression was based on a number-precision reduction. The internal data processing was standard double-precision floating point, while the wirelessly transmitted readouts were reduced in precision to maintain the required resolution. The advantage was a compressed data flow via a wireless link. It was tested with three simultaneous connections from a single transmitter to three receivers without any data loss.</p>
<p>The tolerances in the frequency of the time bases for the transmitter and the receiver resulted in asynchronous handling of the data buffers. To override any troubles with the buffer over- or under-run, we implemented a synchronization algorithm for the compensation in the time-base frequencies. The shape of the time-delay diagram follows exactly the activity of the time-synchronization algorithm. The implemented regulation model was linear. Some future investigation will be required to investigate the possibilities for implementing higher-order PID regulation or some fuzzy-logic algorithms, which could result in a smaller time-delay deviation.</p>
<p>The wireless technology employed was Bluetooth, which is not optimum for an agile communication administration. New and emerging wireless technologies [<xref ref-type="bibr" rid="b20-sensors-12-10014">20</xref>,<xref ref-type="bibr" rid="b21-sensors-12-10014">21</xref>] may provide more nimble solutions, bringing shorter delay times and lower power consumption, which will be the focus of our future work.</p></sec></body>
<back>
<ack>
<p>This work was partially supported by EC under contract RCSG/4301-14/2011-2011/2015-9895/9896-8E and the Slovenian Research Agency under grant P2-0098.</p></ack>
<ref-list>
<title>References</title>
<ref id="b1-sensors-12-10014"><label>1.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Gardner</surname><given-names>R.M.</given-names></name></person-group><article-title>Accuracy and reliability of disposable pressure transducers coupled with modern pressure monitors</article-title><source>Crit. Care. Med.</source><year>1996</year><volume>24</volume><fpage>879</fpage><lpage>882</lpage><pub-id pub-id-type="doi">10.1097/00003246-199605000-00025</pub-id><pub-id pub-id-type="pmid">8706469</pub-id></citation></ref>
<ref id="b2-sensors-12-10014"><label>2.</label><citation citation-type="journal"><article-title>Risk of electric shock from patient monitoring cables and electrode lead wires</article-title><source>Health Dev.</source><year>1993</year><volume>22</volume><fpage>301</fpage><lpage>303</lpage></citation></ref>
<ref id="b3-sensors-12-10014"><label>3.</label><citation citation-type="web"><person-group person-group-type="author"><name><surname>Ye</surname><given-names>M.</given-names></name></person-group><article-title>Cable, transducer and electrode, patient (including Connector)</article-title><comment>Available online: <ext-link xlink:href="http://www.accessdata.fda.gov/scripts/cdrh/devicesatfda/index.cfm?db=pmn&amp;id=K120010" ext-link-type="uri">http://www.accessdata.fda.gov/scripts/cdrh/devicesatfda/index.cfm?db=pmn&amp;id=K120010</ext-link> (accessed on 2 June 2012)</comment></citation></ref>
<ref id="b4-sensors-12-10014"><label>4.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Ligtenberg</surname><given-names>A.</given-names></name><name><surname>Lammert</surname><given-names>K.</given-names></name></person-group><article-title>Sensing a changing world</article-title><source>Sensors</source><year>2009</year><volume>9</volume><fpage>6819</fpage><lpage>6822</lpage><pub-id pub-id-type="doi">10.3390/s90906819</pub-id><pub-id pub-id-type="pmid">22423199</pub-id></citation></ref>
<ref id="b5-sensors-12-10014"><label>5.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Moor</surname><given-names>C.</given-names></name><name><surname>Braecklein</surname><given-names>M.</given-names></name><name><surname>Jorns</surname><given-names>N.</given-names></name></person-group><article-title>Current status of the development of wireless sensors for medical applications</article-title><source>Biomed. Tech.</source><year>2005</year><volume>50</volume><fpage>241</fpage><lpage>251</lpage><pub-id pub-id-type="doi">10.1515/BMT.2005.036</pub-id></citation></ref>
<ref id="b6-sensors-12-10014"><label>6.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Orwat</surname><given-names>C.</given-names></name><name><surname>Graefe</surname><given-names>A.</given-names></name><name><surname>Faulwasser</surname><given-names>T.</given-names></name></person-group><article-title>Towards pervasive computing in health care</article-title><source>BMC. Med. Inform. Decis. Mak.</source><year>2008</year><volume>8</volume><fpage>26</fpage><lpage>43</lpage><pub-id pub-id-type="doi">10.1186/1472-6947-8-26</pub-id><pub-id pub-id-type="pmid">18565221</pub-id></citation></ref>
<ref id="b7-sensors-12-10014"><label>7.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Buratti</surname><given-names>C.</given-names></name><name><surname>Conti</surname><given-names>A.</given-names></name><name><surname>Dardari</surname><given-names>D.</given-names></name><name><surname>Verdone</surname><given-names>R.</given-names></name></person-group><article-title>An overview on wireless sensor networks technology and evolution</article-title><source>Sensors</source><year>2009</year><volume>9</volume><fpage>6869</fpage><lpage>6896</lpage><pub-id pub-id-type="doi">10.3390/s90906869</pub-id><pub-id pub-id-type="pmid">22423202</pub-id></citation></ref>
<ref id="b8-sensors-12-10014"><label>8.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Cifuentes</surname><given-names>C.A.</given-names></name><name><surname>Gentiletti</surname><given-names>G.G.</given-names></name><name><surname>Suarez</surname><given-names>M.J.</given-names></name><name><surname>Rodriguez</surname><given-names>L.E.</given-names></name></person-group><article-title>Development of a Zigbee Platform for Bioinstrumentation. Engineering in Medicine and Biology Society (EMBC)</article-title><conf-name>Proceedings of 2010 Annual International Conference of the IEEE</conf-name><conf-loc>Buenos Aires, Argentina</conf-loc><conf-date>31 August–4 September 2010</conf-date><fpage>390</fpage><lpage>393</lpage></citation></ref>
<ref id="b9-sensors-12-10014"><label>9.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Rosenthal</surname><given-names>K.</given-names></name></person-group><article-title>New frequencies, new monitoring Technology</article-title><source>Nurs. Manag.</source><year>2003</year><volume>34</volume><fpage>49</fpage><lpage>51</lpage></citation></ref>
<ref id="b10-sensors-12-10014"><label>10.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Roth</surname><given-names>H.</given-names></name><name><surname>Schwaibold</surname><given-names>M.</given-names></name><name><surname>Moor</surname><given-names>C.</given-names></name><name><surname>Schochlin</surname><given-names>J.</given-names></name><name><surname>Bolz</surname><given-names>A.</given-names></name></person-group><article-title>Miniaturized module for the wireless transmission of mdpieasurements with Bluetooth</article-title><source>Biomed. Tech.</source><year>2002</year><volume>47</volume><fpage>854</fpage><lpage>856</lpage><pub-id pub-id-type="doi">10.1515/bmte.2002.47.s1b.854</pub-id></citation></ref>
<ref id="b11-sensors-12-10014"><label>11.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Imhoff</surname><given-names>M.</given-names></name></person-group><article-title>The spaghetti syndrome revisited</article-title><source>Anesth. Analg.</source><year>2004</year><volume>98</volume><fpage>566</fpage><lpage>567</lpage><pub-id pub-id-type="pmid">14980899</pub-id></citation></ref>
<ref id="b12-sensors-12-10014"><label>12.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Ng</surname><given-names>K.G.</given-names></name></person-group><article-title>Review of measurement methods and clinical validation studies of noninvasive blood pressure monitors: Accuracy requirements and protocol considerations for devices that require patient-specific calibration by a secondary method or device before use</article-title><source>Blood. Press. Monit.</source><year>2011</year><volume>16</volume><fpage>291</fpage><lpage>303</lpage><pub-id pub-id-type="doi">10.1097/MBP.0b013e32834e3c22</pub-id><pub-id pub-id-type="pmid">22064634</pub-id></citation></ref>
<ref id="b13-sensors-12-10014"><label>13.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Oyri</surname><given-names>K.</given-names></name><name><surname>Balasingham</surname><given-names>I.</given-names></name><name><surname>Samset</surname><given-names>E.</given-names></name><name><surname>Hogetveit</surname><given-names>J.O.</given-names></name><name><surname>Fosse</surname><given-names>E.</given-names></name></person-group><article-title>Wireless continuous arterial blood pressure monitoring during surgery: A pilot study</article-title><source>Anesth. Analg.</source><year>2006</year><volume>102</volume><fpage>478</fpage><lpage>483</lpage><pub-id pub-id-type="doi">10.1213/01.ane.0000195232.11264.46</pub-id><pub-id pub-id-type="pmid">16428546</pub-id></citation></ref>
<ref id="b14-sensors-12-10014"><label>14.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Belavic</surname><given-names>D.</given-names></name><name><surname>Zarnik</surname><given-names>S.M.</given-names></name><name><surname>Hrovat</surname><given-names>M.</given-names></name><name><surname>Macek</surname><given-names>S.</given-names></name><name><surname>Pavlin</surname><given-names>M.</given-names></name><name><surname>Jerlah</surname><given-names>M.</given-names></name><name><surname>Holc</surname><given-names>J.</given-names></name><name><surname>Drnovsek</surname><given-names>S.</given-names></name><name><surname>Cilensek</surname><given-names>J.</given-names></name><name><surname>Kosec</surname><given-names>M.</given-names></name></person-group><article-title>Benchmarking different types of thick-film pressure sensors</article-title><conf-name>Proceedings of the IMAPS/ACerS 2007, 3rd International Conference and Exhibition on Ceramic Interconnect and Ceramic Microsystems Technologies (CICMT)</conf-name><conf-loc>Denver, CO, USA</conf-loc><conf-date>23–26 April 2007</conf-date><fpage>278</fpage><lpage>285</lpage></citation></ref>
<ref id="b15-sensors-12-10014"><label>15.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Mozek</surname><given-names>M.</given-names></name><name><surname>Resnik</surname><given-names>D.</given-names></name><name><surname>Aljancic</surname><given-names>U.</given-names></name><name><surname>Vrtacnik</surname><given-names>D.</given-names></name><name><surname>Amon</surname><given-names>S.</given-names></name></person-group><article-title>Calibration procedures for smart measurement systems</article-title><conf-name>Proceedings of the 9th Electronic Devices and Systems Conference 2002 and Experimental Methods in Acoustic and Electromagnetic Emission International Workshop</conf-name><conf-loc>Brno, Czech Republic</conf-loc><conf-date>9–10 June 2002</conf-date><fpage>389</fpage><lpage>394</lpage></citation></ref>
<ref id="b16-sensors-12-10014"><label>16.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Marko</surname><given-names>P.</given-names></name><name><surname>Belavic</surname><given-names>D.</given-names></name><name><surname>Novak</surname><given-names>F.</given-names></name></person-group><article-title>Ceramic mems designed for wireless pressure monitoring in the industrial environment</article-title><source>Sensors</source><year>2011</year><volume>12</volume><fpage>320</fpage><lpage>333</lpage><pub-id pub-id-type="doi">10.3390/s120100320</pub-id><pub-id pub-id-type="pmid">22368471</pub-id></citation></ref>
<ref id="b17-sensors-12-10014"><label>17.</label><citation citation-type="book"><source>IEEE Standard for Floating-Point Arithmetic</source><comment>IEEE Standard 754-2008</comment><day>29</day><month>August</month><year>2008</year><publisher-name>IEEE Computer Society</publisher-name><publisher-loc>Washington, DC, USA</publisher-loc><fpage>1</fpage><lpage>58</lpage></citation></ref>
<ref id="b18-sensors-12-10014"><label>18.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Zarnik</surname><given-names>M.S.</given-names></name><name><surname>Belavic</surname><given-names>D.</given-names></name><name><surname>Macek</surname><given-names>S.</given-names></name></person-group><article-title>The warm-up and offset stability of a low-pressure piezoresistive ceramic pressure sensor</article-title><source>Sens. Actuators A. Phys.</source><year>2010</year><volume>158</volume><fpage>198</fpage><lpage>206</lpage><pub-id pub-id-type="doi">10.1016/j.sna.2009.12.035</pub-id></citation></ref>
<ref id="b19-sensors-12-10014"><label>19.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Bland</surname><given-names>J.M.</given-names></name><name><surname>Altman</surname><given-names>D.G.</given-names></name></person-group><article-title>Statistical methods for assessing agreement between two methods of clinical measurement</article-title><source>Lancet</source><year>1986</year><volume>1</volume><fpage>307</fpage><lpage>310</lpage><pub-id pub-id-type="pmid">2868172</pub-id></citation></ref>
<ref id="b20-sensors-12-10014"><label>20.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Jovanov</surname><given-names>E.</given-names></name><name><surname>Raskovic</surname><given-names>D.</given-names></name><name><surname>Price</surname><given-names>J.</given-names></name></person-group><article-title>Patient monitoring using personal area networks of wireless intelligent sensors</article-title><source>Biomed. Sci. Instrum.</source><year>2001</year><volume>37</volume><fpage>373</fpage><lpage>378</lpage><pub-id pub-id-type="pmid">11347420</pub-id></citation></ref>
<ref id="b21-sensors-12-10014"><label>21.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Jokerst</surname><given-names>N.M.</given-names></name><name><surname>Brooke</surname><given-names>M.A.</given-names></name><name><surname>Cho</surname><given-names>S.Y.</given-names></name><name><surname>Shang</surname><given-names>A.B.</given-names></name></person-group><article-title>Chip-scale sensor system integration for portable health monitoring</article-title><source>Anesth. Analg.</source><year>2007</year><volume>105</volume><fpage>42</fpage><lpage>47</lpage><pub-id pub-id-type="doi">10.1213/01.ane.0000278760.29572.3b</pub-id></citation></ref></ref-list>
<sec sec-type="display-objects">
<title>Figures and Tables</title>
<fig id="f1-sensors-12-10014" position="float">
<label>Figure 1.</label>
<caption>
<p>Passive sensor bridge connected to the process equipment.</p></caption>
<graphic xlink:href="sensors-12-10014f1.gif"/></fig>
<fig id="f2-sensors-12-10014" position="float">
<label>Figure 2.</label>
<caption>
<p>Wireless resistive-bridge sensor interface-block diagram.</p></caption>
<graphic xlink:href="sensors-12-10014f2.gif"/></fig>
<fig id="f3-sensors-12-10014" position="float">
<label>Figure 3.</label>
<caption>
<p>Analog input stage at the transmitter side.</p></caption>
<graphic xlink:href="sensors-12-10014f3.gif"/></fig>
<fig id="f4-sensors-12-10014" position="float">
<label>Figure 4.</label>
<caption>
<p>Analog-to-digital converter connection.</p></caption>
<graphic xlink:href="sensors-12-10014f4.gif"/></fig>
<fig id="f5-sensors-12-10014" position="float">
<label>Figure 5.</label>
<caption>
<p>Output stage of the sensor signal reconstruction unit: the main component is the fully differential amplifier.</p></caption>
<graphic xlink:href="sensors-12-10014f5.gif"/></fig>
<fig id="f6-sensors-12-10014" position="float">
<label>Figure 6.</label>
<caption>
<p>Data-integrity protection envelope.</p></caption>
<graphic xlink:href="sensors-12-10014f6.gif"/></fig>
<fig id="f7-sensors-12-10014" position="float">
<label>Figure 7.</label>
<caption>
<p>(<bold>a</bold>) Transmitter and receiver prototype implemented with CC2400 and (<bold>b</bold>) Transmitter and three receivers implemented with WT12 Bluetooth module.</p></caption>
<graphic xlink:href="sensors-12-10014f7.gif"/></fig>
<fig id="f8-sensors-12-10014" position="float">
<label>Figure 8.</label>
<caption>
<p>(<bold>a</bold>) Clinical evaluation setup under laboratory conditions and (<bold>b</bold>) during clinical trial in the hospital intensive care unit.</p></caption>
<graphic xlink:href="sensors-12-10014f8.gif"/></fig>
<fig id="f9-sensors-12-10014" position="float">
<label>Figure 9.</label>
<caption>
<p>Evaluation data-acquisition system.</p></caption>
<graphic xlink:href="sensors-12-10014f9.gif"/></fig>
<fig id="f10-sensors-12-10014" position="float">
<label>Figure 10.</label>
<caption>
<p>Signals captured at the lower level of the experiment.</p></caption>
<graphic xlink:href="sensors-12-10014f10.gif"/></fig>
<fig id="f11-sensors-12-10014" position="float">
<label>Figure 11.</label>
<caption>
<p>Data-extraction and evaluation algorithm.</p></caption>
<graphic xlink:href="sensors-12-10014f11.gif"/></fig>
<fig id="f12-sensors-12-10014" position="float">
<label>Figure 12.</label>
<caption>
<p>Cross-correlation between input signal and shifted output signal.</p></caption>
<graphic xlink:href="sensors-12-10014f12.gif"/></fig>
<fig id="f13-sensors-12-10014" position="float">
<label>Figure 13.</label>
<caption>
<p>Time-delay evaluator D between p<sub>T</sub> and p<sub>R</sub> for 24-hour pressure measurements.</p></caption>
<graphic xlink:href="sensors-12-10014f13.gif"/></fig>
<fig id="f14-sensors-12-10014" position="float">
<label>Figure 14.</label>
<caption>
<p>Results for evaluator δ(n) for 24-hour pressure measurements.</p></caption>
<graphic xlink:href="sensors-12-10014f14.gif"/></fig>
<table-wrap id="t1-sensors-12-10014" position="float">
<label>Table 1.</label>
<caption>
<p>Evaluation of the appropriateness of the wireless technologies for various applications.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="left" valign="top"><bold>Feature</bold></th>
<th align="left" valign="top"><bold>CC2400</bold> <xref ref-type="table-fn" rid="tfn2-sensors-12-10014"><sup>a</sup></xref></th>
<th align="left" valign="top"><bold>WT12</bold> <xref ref-type="table-fn" rid="tfn3-sensors-12-10014"><sup>b</sup></xref></th>
<th align="left" valign="top"><bold>Units</bold></th></tr></thead>
<tbody>
<tr>
<td align="left" valign="top">Data rate</td>
<td align="left" valign="top">250</td>
<td align="left" valign="top">723</td>
<td align="left" valign="top">kbps</td></tr>
<tr>
<td align="left" valign="top">Rx power consumption</td>
<td align="left" valign="top">165</td>
<td align="left" valign="top">231</td>
<td align="left" valign="top">mW</td></tr>
<tr>
<td align="left" valign="top">Tx power consumption</td>
<td align="left" valign="top">148.5</td>
<td align="left" valign="top">231</td>
<td align="left" valign="top">mW</td></tr>
<tr>
<td align="left" valign="top">CE, FCC qualified</td>
<td align="left" valign="top">Yes</td>
<td align="left" valign="top">Yes</td>
<td align="left" valign="top"/></tr>
<tr>
<td align="left" valign="top">Indoor/Urban Range</td>
<td align="left" valign="top">30</td>
<td align="left" valign="top">10</td>
<td align="left" valign="top">m</td></tr>
<tr>
<td align="left" valign="top">Outdoor RF line-of-sight Range</td>
<td align="left" valign="top">100</td>
<td align="left" valign="top">(X)</td>
<td align="left" valign="top">m</td></tr>
<tr>
<td align="left" valign="top">Supported Network Topologies</td>
<td align="left" valign="top">Point-to-point,<break/>Point-to-multipoint,<break/>Peer-to-peer &amp; Mesh</td>
<td align="left" valign="top">Point-to-point,<break/>Point-to-multipoint</td>
<td align="left" valign="top"/></tr>
<tr>
<td align="left" valign="top">Self-routing option</td>
<td align="left" valign="top">Yes</td>
<td align="left" valign="top">(X)</td>
<td align="left" valign="top"/></tr>
<tr>
<td align="left" valign="top">Self-healing network</td>
<td align="left" valign="top">Yes</td>
<td align="left" valign="top">(X)</td>
<td align="left" valign="top"/></tr>
<tr>
<td align="left" valign="top">Fault-tolerant mesh network</td>
<td align="left" valign="top">Yes</td>
<td align="left" valign="top">(X)</td>
<td align="left" valign="top"/></tr>
<tr>
<td align="left" valign="top">Supply voltage</td>
<td align="left" valign="top">3.3</td>
<td align="left" valign="top">3.3</td>
<td align="left" valign="top">V</td></tr>
<tr>
<td align="left" valign="top">UART interface</td>
<td align="left" valign="top">No</td>
<td align="left" valign="top">Yes</td>
<td align="left" valign="top"/></tr>
<tr>
<td align="left" valign="top">SPI interface</td>
<td align="left" valign="top">Yes</td>
<td align="left" valign="top">No</td>
<td align="left" valign="top"/></tr>
<tr>
<td align="left" valign="top">Encryption</td>
<td align="left" valign="top">128</td>
<td align="left" valign="top">128</td>
<td align="left" valign="top">bit</td></tr>
<tr>
<td align="left" valign="top">RSSI indication</td>
<td align="left" valign="top">Yes</td>
<td align="left" valign="top">Yes</td>
<td align="left" valign="top"/></tr>
<tr>
<td align="left" valign="top">Time to connect</td>
<td align="left" valign="top">&lt;0.05</td>
<td align="left" valign="top">&gt;5</td>
<td align="left" valign="top">s</td></tr>
<tr>
<td align="left" valign="top">Form factor</td>
<td align="left" valign="top">24 × 27 × 2.3</td>
<td align="left" valign="top">26 × 14 × 2.3</td>
<td align="left" valign="top">mm</td></tr>
<tr>
<td align="left" valign="top">Integrated antenna</td>
<td align="left" valign="top">Y</td>
<td align="left" valign="top">Y</td>
<td align="left" valign="top"/></tr>
<tr>
<td align="left" valign="top">External antenna</td>
<td align="left" valign="top">Y</td>
<td align="left" valign="top">N</td>
<td align="left" valign="top"/></tr>
<tr>
<td align="left" valign="top">Price per 1k units</td>
<td align="left" valign="top">10.89</td>
<td align="left" valign="top">&gt;20.00</td>
<td align="left" valign="top">€</td></tr>
<tr>
<td align="left" valign="top">Coexistence with other wireless technologies</td>
<td align="left" valign="top">Limited</td>
<td align="left" valign="top">Possible</td>
<td align="left" valign="top"/></tr></tbody></table>
<table-wrap-foot><fn id="tfn1-sensors-12-10014">
<p>Notes:</p></fn><fn id="tfn2-sensors-12-10014">
<label>a</label>
<p>Source: Ti CC2400 documentation and measurements on evaluation modules;</p></fn><fn id="tfn3-sensors-12-10014">
<label>b</label>
<p>Source: Bluegiga WT12 documentation; X: Information not given by datasheet or user's manual.</p></fn></table-wrap-foot></table-wrap>
<table-wrap id="t2-sensors-12-10014" position="float">
<label>Table 2.</label>
<caption>
<p>Wireless-system requirements.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="center" valign="top"><bold>Evaluator</bold></th>
<th align="center" valign="top"><bold>Min</bold></th>
<th align="center" valign="top"><bold>Typ</bold></th>
<th align="center" valign="top"><bold>Max</bold></th>
<th align="left" valign="top"><bold>units</bold></th></tr></thead>
<tbody>
<tr>
<td align="center" valign="top">Amplitude error (<italic>δ̄</italic>)</td>
<td align="center" valign="top">−4</td>
<td align="center" valign="top">0</td>
<td align="center" valign="top">4</td>
<td align="left" valign="top">kPa</td></tr>
<tr>
<td align="center" valign="top">Time delay (<italic>D</italic>)</td>
<td align="center" valign="top">0</td>
<td align="center" valign="top"/>
<td align="center" valign="top">1</td>
<td align="left" valign="top">s</td></tr></tbody></table></table-wrap></sec></back></article>
