Virtually unlimited. There is no limit on the number of sensors in one iQunet sensor network. You can also combine different sensor types in one network. The central node is the base station. All data gathered by the sensors is stored on the iQunet server attached to the base station.
The range of a sensor is a few hundreds of meters in free field. In industrial plants the range is less due to interference and reflections. If the sensor is mounted according to our instructions you can reach up to 50m in a rather open plant. In a very dense plant with metal constructions all over, the range will be up to 30m. If a sensor or the base station is put in a metal cabinet, the range will drop to less than 10m. You can always check the RSSI symbol in the dashboard to find out if the sensor is able to connect to the base station. Due to limitations in the free frequency bands, we are not allowed by governmental rules to increase broadcasting power – although we could.
Yes, you can! Use an iQunet repeater to extend the range of the sensor network. You can add an unlimited number of repeaters in the range of the base station. Each repeater can serve also an unlimited number of sensors. Nevertheless, each sensor might not see more than one repeater between sensor and base station. More repeater hops in the network will drastically increase the uptime of the radio transmitters in the sensors. By avoiding this, we can guarantee a long battery life.
This depends on the adjustable settings made on the sensor via the sensor dashboard. But as a comparison: the batteries of the vibration sensor, measuring 8192 vibration points every day, will last up to 5 years. With one important remark: the batteries should be installed clean! The sensor electronics are extremely low power. E.g. touching the CR2032 coin cell batteries will leave some grease on the batteries and this will allow leakage current to run over the battery poles, resulting in a reduced sensor life time up to 50%!
Yes, you can. Sensors like the standard vibration sensor are not sensitive to magnets. This allows you to mount the sensor on a magnetic base and start online measuring in no time. Other sensors like the proximity sensors measure the magnetic field, and it is obvious that mounting such a sensor on a magnetic base makes little sense.
The vibration sensor contains an acceleration MEMS chip. Even when on the table, the sensor measures gravity. Depending on how it lays on the table you will find +1g or -1g on the axis that is in line with gravity. You can set the high pass filter in the sensor dashboard to filter out the gravity measurement in the graphs.
You can set a threshold level for the vibration sensor which avoids creating not usable data. When the measured RMS on a few samples is higher than the threshold, the full measurement is processed and stored in the OPC database. Otherwise this sample measurement is dropped.
We are working on a system which digitizes analog sensor values and stores them in the OPC database with a time stamp. This way you will be able to combine existing monitoring sensors and wireless iQunet sensors and store the values in one database for further processing. We keep you updated via our website.
No, you don’t need to install any software but your browser to address the iQunet sensor dashboard. Neither is there any license fee to be paid. By purchasing the product, you have paid for both the hardware and installed software. We advise a Chrome browser, but any browser webRTC ready will do fine (check http://iswebrtcreadyyet.com/legacy.html to see if your browser supports this open source development). Try to browse the dashboard on a WebRTC ready browser on any device like your smartphone, tablet, etc. It will work fine too.
The sensor measurements are stored on the iQunet Unix Server you buy with the sensors and network components. This server runs several processes and contains a database. (We compute “in the edge – not in the cloud”) The OPC UA server allows you to access the data free of charge from any OPC UA client. There is no lock-in, nor are there any fees to be paid. It is the vision of iQunet that data collected by the customer belongs to the customer without fees. Of course, you will need stable network access to address the server and to visualize the data or to extract data using the OPC UA server communication.
As long as the servers (and repeaters) are connected to the mains, data collection and monitoring remains ongoing, even without internet/intranet connection. The iQunet sensor network stays up and running because we compute “in the edge”, not in the cloud. Data is stored nearby the sensor network. Only visualization (via browser) is done over the network.
All battery-operated sensors have a temperature sensor chip on board. This electronic sensor is situated on the PCB inside the sensor unit and measures the mass temperature from the wireless sensor. There will be some delay between the surface temperature of the sensor unit and the collected inside temperature.
This message will appear if your browser is not able to connect with the iQunet server via internet. Most likely, the network connection from the server is broken. In rare cases the company firewall setting will have to allow our relay server to connect to the iQunet Unix Server within the company network. Please contact us for further instructions.
The current IP address from the server in the network can easily been shown: click on the 3 bars below the iQunet logo in the browser. The left pane opens. Click “Ethernet-Wifi” and the information appears.
Yes, indeed. Connect to the iQunet server. Open the left pane in the iQunet dashboard by clicking the 3 bars below the iQunet logo. Click “Ethernet-Wifi” and change the setting from layer 3 in the network profile.
The iQunet vibration sensors are not calibrated because the calibration would only be valid for a specific frequency and temperature. Since these parameters cannot be kept stable in a real industrial environment and a calibration procedure per sensor is expensive, iQunet has chosen for a more practical solution.
Instead of (re)calibrating each sensor each year, iQunet keeps track of several trends, on top of the time signal, of the vibration signal (for example RMS). Based on these trends deviations can be detected automatically, where one-time measurements must work with prefixed threshold values. Since the sensor doesn’t need to be removed for calibration, it can remain mounted on an identical spot. This will lead to consistent trend tracking measurements. Since the iQunet sensors work completely wireless, there is also no risk of variable contact surface, modified measuring points, interference on the cabling or even an incorrectly performed measurement. Problems in the machine on the short term can thus be detected faster, even without calibration.
Since the sensor doesn’t need calibration, the maintenance costs per sensor are much lower and the sensor design is simpler which results in a lower current consumption and a longer battery life time.
Finally, the peak frequencies in the Fourier spectrum are dependent on the rotation speed. Even if the rotation speed is theoretically constant, there will be an unknown shift in the spectrum caused by the variable motor load, variations in the frequency control of the motor, etc. These shifts are however constant across the whole spectrum. Because of this, orders of the fundamental frequencies (1X, 2X, 3X, etc.) can be used in the spectrum. The same principle applies for a noncalibrated iQunet sensor.
Connect the iQunet server to the 230V mains and if available to the network.
If there is no network connection available, you can use the hotspot functionality of the iQunet server. Place the server within the WiFi range of your PC and look for the hotspot name (e.g. SERN- xxxxxxxxxxxx) in the network center of your computer. Your PC should be WiFi enabled. Select the hotspot and click Connect. The hotspot’s password is the Sensor Proxy ID (e.g. server-xxxxxxxx). This ID is written on your UNIX server. Once connected to the hotspot, you can connect to the server by browsing to 192.168.42.1:8000/dashboard/app. We recommend using the Chrome browser.
If there is a network connection available, you can either connect via the hotspot or via rtc.iqunet.be. The first time you connect via rtc.iqunet.be, you will be prompted to identify yourself with a Google account. This identification is to make sure you are not a web robot.
To logon to the iQunet sensor dashboard, you will be prompted for a Cloud API Key and a Sensor Proxy ID (API Key and Sensor Proxy ID are provided by iQunet). The Sensor Proxy ID is written on your UNIX server (e.g. server-xxxxxxxx).
You are now connected to the iQunet Unix server.
Once you are connected to the iQunet Unix server, you can adjust the settings of the sensors to your needs and start data acquisition.
For the vibration sensor for example you can change the sample rate, measurement axis, number of samples, etc. Start the data acquisition by either triggering manually (REC button in the ‘MEMS Vibration Setup’ section) or by enabling automatic measurements where you set the time interval in between two measurements (‘Auto Measurements’ section).
The recorded vibration data can be viewed in the iQunet sensor dashboard by opening the vibration lab pane. Click on the ‘vLab’ button in the ‘Vibration Download’ section to open this pane.
All recorded data can be extracted via the built-in OPC UA Server. The OPC UA Server always listens on port 4840 regardless if the connection is made via cable, hotspot or WiFi. If you use the hotspot connection, this will be 192.168.42.1:4840. If you use another connection type, you need to use the IP address of the iQunet Unix server (xxx.xxx.xx.xx:4840). The current IP address of the server in the network can easily been found by clicking the 3 bars below the iQunet logo in the sensor dashboard. Select “Ethernet-WiFi” in the left pane and the IP address will appear.
To extract data via OPC, you can use UAExpert for example.
Open UA Expert and click on Server –> Add.
Double click on “Double click to Add Server” and fill out the IP address behind opc.tcp://. Click OK.
Select the added server in the server list. All sensors connected to this server will appear in the Address Space.
Click on the macId of the sensor to see all possible attributes of the sensor.
Add a document to inspect for example the board temperature data (Document –> Add). Select ‘History Trend View’ as the document type and click ‘Add’.
Drag the boardTemperature attribute of the sensor to the configuration window.
Temperature read-out is possible via either a single update that extracts all data values in between two points of time at once or via a cyclic update that extracts all data over the set timespan every set time interval (update interval).
The accelerationPack attribute contains the raw vibration data. The accelerationPack format is as follows:
1/ numSamples: n = #samples
2/ accelArray: rawSample[0:n-1]
3/ sampleRate: e.g. 400 = 400Hz
4/ formatRange: e.g. 4 = +/-4g (hardware setting of the accelerometer IC)
5/ offset: unused, 0 (hardware offset of the accelerometer IC)
6/ encoded_axis: X = 0, Y = 1, Z = 2
7/ prescaler: unused (only used when no compression in debug mode)
8/ compression: unused (0 = no compression in debug mode, 1 = compression)
You will see that the first 7 samples of the accelArray (at the start of each measurement) show a transient response due to the start-up behavior of the compression algorithm. Since a Hanning window is used for the calculation of the DFT and RMS, this behavior will be automatically suppressed and has thus no further impact.
The conversion of the accelArray to g units is as follows:
Conversion of rawSample[0:n-1] to [g]:
gSample = rawSample[0:n-1]/512.0*formatRange [g]
gTimes = [0:n-1]/sampleRate [sec]