Things used in this project


Introducing NCD’s Long Range IoT Industrial wireless vibration and temperature sensor, boasting up to a 2-mile range the use of a wireless mesh networking structure. Incorporating a precision 16-bit vibration and temperature sensor, this device transmits incredibly accurate vibration and temperature records at consumer-described duration.

For the duration of Power-Up, this vibration sensor learns “normal” base-line vibration from the monitored device. This base-line vibration is subtracted from regular sampled vibration readings to improve applicable vibration data. Preferably, the monitored device must be off even as the sensor is mastering. Once the sensor stabilizes and starts sending information, the device/equipment being monitored can be powered on. This business IoT wireless vibration sensor samples 3-axis of vibration data for 100ms after which calculate RMS, maximum, and minimal vibration readings. This sensor combines these records with temperature data in a data packet and transmits the result to modems and gateways in the wi-fi variety. Once the transmission is complete, the vibration sensor is going lower back to sleep, therefore minimizing power consumption.

Powered by using just 2 AA batteries and operational life of 500,000 wireless transmissions, a ten years battery life can be expected relying on environmental conditions and the data transmission interval. Optionally, this sensor may be externally powered, making it a perfect choice for wireless vibration monitoring device for industrial equipment. With an open communication protocol, this sensor transmits hardware-encrypted data that may be included with just about any control system or gateway. Data can be transmitted to a laptop, a raspberry pi, to Losant IoT cloud, microsoft® azure® IoT, and an embedded gadget all at the equal time. Sensor parameters and wireless transmission settings can be modified using labview® tracking software on a computer pc.

Long-Range Wireless Mesh Modem with USB Interface

Resources Required

Setting up XAMPP

XAMPP is most prevailing, free an open-source cross-platform which is one solution to run your web services. XAMPP is developed by ApacheFriends which released in May 2002. XAMPP Stands for Cross-Platform(X), Apache(A), MySQL(M) also Sometimes (M) refers to MariaDB, PHP(P) and Pearl(P).

xampp allows you to work on a local server and test local copies of websites using PHP code and MySQL databases. Once xampp is active, you can access your local copy with a browser using an URL like http://localhost/ or

Downloading and Installing XAMPP

Go to XAMPP web site and download the installer based on your operating system. Installation should be similar to a normal software installation you do in your operating system.

When installing, there would be an option to select whether you want to run Apache and MySQL as services. If you chose it, Apache and MySQL will start at system boot-up which may not need if your computer is tight with memory resources or if you are not doing PHP development frequently. You can change these settings after installation.

Starting Apache and MySQL

That’s all with the setting up of XAMPP.

Setting up Node-Red.

The sensor and Zigmo/Router come pre-programmed and work out of the box. In this section, we will set up a sensor and Zigmo link and start receiving data on our PC

Steps to install NODE-RED

Now that you have sensors running, we need a way to do something useful with that data.

Setting up the nodes

Assuming at this point you’ve started up Node-RED, you should be able to open a browser and navigate to http://localhost:1880, this will open up the flow builder that is the heart of the Node-RED experience.

Steps to build the flow

Finding your wireless sensors

Once you’ve added the node you’ll be able to view the info tab, which contains information about the node’s functionality, this tab is well-populated for most node-red packages and contains valuable information, many times you will not need to view any other documentation outside of the info tab, so keep it in mind while you are building your flows if you have a question about how a node works. The next thing we need to do is configure the node, when you first add it you’ll notice that there is a small triangle on the top right corner next to a blue dot, the triangle indicates that the node needs additional configuration, the blue dot indicates that the node has not yet been deployed as part of the flow.

Working with the data

Now out of your wireless sensors data is gathered and it is output to the “debug” tab, this “debug tab” is placed within the right sidebar subsequent to the information tab. To see the information are available in to hit the reset button. In node-red records is surpassed among nodes in a JSON packet. When the msg object comes into the debug tab you may make bigger it to view the overall list of information that comes with it. This is extraordinarily useful in case you need to quickly see which sensors are checking in. The other issue this node gives is an easy way to interchange your router to the network identity that devices in configuration mode document on, simply hit the button on the left of the node and the tool will switch to the configuration network, hit it once more to return it to listening mode. Once we get the wireless device nodes set up, they may be set to routinely configure a sensor whilst it enters configuration mode, so it’s always available to maintain such gateway nodes present at the flow for speedy configuring a device.

Adding the wireless sensors

we need to separate wireless sensor records domestically in order that we are able to display it, we could use a switch node to split out the messages from the gateway based totally on the mac address with or sensor type, but as I referred to, the wireless nodes truly incorporate extra functionality for configuring the sensors, so we’ll start with them to give you an extra entire image of how those structures can work. In case you haven’t already seen packets coming in from both of your sensors, cross in advance and hit the reset button on the only that hasn’t stated. While a sensor assessment in thru any serial device configuration node, the mac address and kind of sensor is cached in a pool so we are able to quickly find it for the duration of this next step.

You’ll notice this automatically sets the sensor type for you, you can also give it a name to make it easier to identify. As noted in the info tab, the Serial Device for Config field is optional, and we won’t worry about it right now. The node you have just added effectively works as a filter on incoming sensor data, only passing through data for the mac address, or sensor type if no mac address is present.

Adding Function Nodes

The function node is used to run JavaScript code against the msg object. The function node accepts a msg object as input and can return 0 or more message objects as output. This message object must have a payload property (msg.payload) and usually has other properties depending on the proceeding nodes.

Here you have to write little javascript code to create a condition, so the data is sent to the MySQL database.

rms_x = msg.payload.rms_xrms_y = msg.payload.rms_yrms_z = msg.payload.rms_zmax_x = msg.payload.max_xmax_y = msg.payload.max_ymax_z = msg.payload.max_zmin_x = msg.payload.min_xmin_y = msg.payload.min_ymin_z = msg.payload.min_ztemperature = msg.payload.temperaturemsg.topic = "INSERT INTO vibration_temperature ( `rms_x`, `rms_y`, `rms_z`, `max_x`, `max_y`, `max_z`, `min_x`, `min_y`, `min_z`, `temperature`) VALUES ( "+ rms_x +", "+ rms_y +", "+ rms_z +", "+ max_x +", "+ max_y +", "+ max_z +", "+ min_x +", "+ min_y +", "+ min_z +", "+ temperature +");"return msg;

Once it's done, you’ll see “mysql” node is present in the palette.


Here you can visualize the data coming in.

Node-RED Flow

[{"id":"ab91f6eb.240f38","type":"tab","label":"Flow 9","disabled":false,"info":""},{"id":"5dd41f6d.915ab","type":"ncd-gateway-node","z":"ab91f6eb.240f38","name":"","connection":"8cca9788.ffe138","x":130,"y":80,"wires":[["12e691e.ab6976e"]]},{"id":"d22c7a49.01a578","type":"ncd-wireless-node","z":"ab91f6eb.240f38","name":"","connection":"1eb93cb8.033cb3","config_comm":"cb5cdf57.475f9","addr":"","sensor_type":"8","auto_config":"","node_id":0,"delay":300,"destination":"0000FFFF","power":4,"retries":10,"pan_id":"7FFF","change_enabled":"","change_pr":"0","change_interval":"0","cm_calibration":"60.6","bp_altitude":"0","bp_pressure":"0","bp_temp_prec":"0","bp_press_prec":"0","amgt_accel":"0","amgt_mag":"0","amgt_gyro":"0","impact_accel":"0","impact_data_rate":"4","impact_threshold":25,"impact_duration":1,"activ_interr_x":1,"activ_interr_y":2,"activ_interr_z":4,"activ_interr_op":8,"filtering":0,"data_rate":5,"time_series":0,"reading_type":1,"x":80,"y":240,"wires":[["6963b687.e08fd8","5ddf132d.818fbc"]]},{"id":"12e691e.ab6976e","type":"debug","z":"ab91f6eb.240f38","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":410,"y":80,"wires":[]},{"id":"6963b687.e08fd8","type":"debug","z":"ab91f6eb.240f38","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":260,"y":400,"wires":[]},{"id":"5ddf132d.818fbc","type":"function","z":"ab91f6eb.240f38","name":"MySQL Function","func":"rms_x = msg.payload.rms_x\nrms_y = msg.payload.rms_y\nrms_z = msg.payload.rms_z\nmax_x = msg.payload.max_x\nmax_y = msg.payload.max_y\nmax_z = msg.payload.max_z\nmin_x = msg.payload.min_x\nmin_y = msg.payload.min_y\nmin_z = msg.payload.min_z\ntemperature = msg.payload.temperature\nmsg.topic = \"INSERT INTO vibration_temperature ( `rms_x`, `rms_y`, `rms_z`, `max_x`, `max_y`, `max_z`, `min_x`, `min_y`, `min_z`, `temperature`) VALUES ( \"+ rms_x +\", \"+ rms_y +\", \"+ rms_z +\", \"+ max_x +\", \"+ max_y +\", \"+ max_z +\", \"+ min_x +\", \"+ min_y +\", \"+ min_z +\", \"+ temperature +\");\"\nreturn msg;","outputs":1,"noerr":0,"x":370,"y":240,"wires":[["4d7967a3.5510a8"]]},{"id":"4d7967a3.5510a8","type":"mysql","z":"ab91f6eb.240f38","mydb":"4bd6fc82.510b44","name":"MySQLDatabase","x":700,"y":240,"wires":[[]]},{"id":"8cca9788.ffe138","type":"ncd-gateway-config","z":"","name":"","comm_type":"serial","ip_address":"","tcp_port":"2101","port":"COM6","baudRate":"115200","pan_id":"7fff","rssi":false},{"id":"1eb93cb8.033cb3","type":"ncd-gateway-config","z":"","name":"","comm_type":"serial","ip_address":"","tcp_port":"2101","port":"COM6","baudRate":"115200","pan_id":"7fff","rssi":false},{"id":"cb5cdf57.475f9","type":"ncd-gateway-config","z":"","name":"","comm_type":"serial","ip_address":"","tcp_port":"2101","port":"COM6","baudRate":"115200","pan_id":"7fff","rssi":false},{"id":"4bd6fc82.510b44","type":"MySQLdatabase","z":"","host":"","port":"3306","db":"rjdatabase","tz":"GMT +5:30"}]