Description
IoT Long Range Wireless Acceleration and Impact Detection Sensor
Our long range wireless enterprise series sensors are an easy to use and reliable start to any data aggregation application. This video will demonstrate how they work, what they do, and how to use them.
IoT Long Range Wireless Acceleration and Impact Detection Sensor
Introducing NCD’s Long Range IoT Wireless Impact Detection Sensor, boasting up to a 2 Mile range using a wireless mesh networking architecture. This device incorporates a precision acceleration sensor for measuring acceleration changes. Utilizing the interrupt feature of this sensor, it is able to minimize power consumption by waiting for the interrupt from the sensor.
Configure the Impact Detection condition (interrupt settings) using configuration mode. This impact detector offers many configuration parameters, including acceleration range, data rate, interrupt duration, and interrupt threshold. Interrupt duration is dependent upon data rate. It is the duration for which an interrupt condition has to hold to generate a system interrupt and initiate data transmission to a nearby receiver. Interrupt threshold is dependent upon acceleration range, and is the acceleration in g which (if exceeded) causes the interrupt to fire. Note the absolute value of actual g reading is compared, therefore it works for both positive and negative acceleration exceeding threshold.
Interrupts are fired only when the acceleration (absolute value) read form the sensor exceeds the threshold in the positive direction. All interrupts are combined with an OR gate. This allows impact detection (system interrupt) if an interrupt occurs for any axis (OR condition). User can also configure a delay time in seconds which disables the interrupt for that amount of time after a successful interrupt. This enables the user to make sure that the sensor does not drain its battery (with continuous transmissions) if an interrupt condition persists or a wrong condition is accidentally programmed. This time is also used to send a periodic packet to a receiver with latest available data.
The device also sends two extra samples with the sample which caused interrupt. This enables the user to have a history of acceleration data prior and after the interrupt. In a normal scenario, it will send 1 sample (n-1) prior to the interrupt sample (n) and 1 sample after the interrupt (n+1). However, if the data rate is too slow, the sensor does not wait for n+1 packet to arrive so as to save battery and instead sends 2 old samples (n-2, n-1) along with the third sample (n) which fired interrupt. It may happen that the duration and sleep delay combination is such that no old sample was saved after the last interrupt and at the time of interrupt the device may contain only 1 sample. In that case it sends 2 old samples from the last transmission along with third sample (n) being the interrupt sample. In case it has 1 old sample (n-1) and 1 interrupt sample (n), it will send the first sample (n-2) from the previously transmitted data.
Powered by just 2 AA batteries and an operational lifetime of 300,000 wireless transmissions, a 10 years battery life can be expected depending on environmental conditions and the data transmission interval. Optionally, this sensor may be externally powered.
We take IoT security very seriously, which is why we encrypt every IoT sensor, gateway, modem, and device in the NCD Enterprise product line. Encryption is much easier to manage than you might expect, as the encryption does not get in the way of using the device. We include a standard 128-Bit AES Encryption key with every device or we can help you integrate a new encryption key into all of your devices. All hardware devices must use the same encryption key. Once the keys are set, the hardware manages the rest for you, 100% in the background.
NCD long-range wireless IoT sensors use the DigiMesh® protocol from Digi.com. DigiMesh® was designed by THE industrial leader in secure wireless communications for industrial applications. DigiMesh® automatically hops data from gateway to gateway until it arrives at the desired destination. NCD IoT sensors are capable of a 2-Mile line-of-site communication distance with the included antennas and up to 28-mile range when using high-gain antennas.
Your data belongs to YOU and it’s up to you to decide where you want your IoT sensor data to arrive. Don’t be bogged down by the limitations of proprietary cloud solutions, post the data where you need it most. We offer an open communications protocol so you can integrate NCD wireless transmitters into your own software. This allows integration of NCD IoT sensors into any control system or gateway you could ever imagine. Send data to a PC, Mac, or Linux computer, or a Raspberry Pi using NCD modems. Send data to popular cloud platforms such as Microsoft® Azure® IoT, Losant, and MQTT using NCD Micro Gateways. We can also help get data from NCD wireless IoT sensors to embedded platforms such as Arduino. We also offer sample code for Microsoft® Visual Studio, Node-RED, LabVIEW®, and Python. Our documentation fully breaks down the packet structure, so integration into other languages is possible. We may even be able to help, so please feel free to contact us if you are working with a platform not mentioned here.
The long range, price, accuracy, battery life and security features of Wireless Impact Detection Sensor makes it an affordable choice which exceeds the requirements for most of the industrial as well as consumer market applications.
NOTE: The current version of this sensor does not support the inbuilt temperature sensor.
Transmission Interval
This device sends data when input thresholds exceed user-defined preset limits.
IoT Sensor Data Transmission
NCD IoT Sensors send a lot more than just sensor data. For instance, a unique serial number is sent so you can always identify a particular sensor on the network. A Node ID is also included, which a single byte of data that you can use for anything, such as the floor of a building or to help identify which group a sensor belongs to. Also included in the data packet is a firmware version, battery level, and sensor type. This allows your software to positively identify and manage the health of NCD IoT wireless sensors. While signal strength data is also available, it is handled in a different way, and is not included in the sensor data packet (but rest assured, signal strength data for each sensor is available). Please see the Resources tab to see detailed information on the data structure of this device.
NCD wireless sensors transmit data and require a receiver. There are many options available for receiving data from NCD IoT devices, please see below for a in-depth description of destinations available for NCD sensors. We highly recommend using our USB Modem (available during purchase) so you can monitor this device and use our LabVIEW® software for changing device settings. Some sensors have advanced settings that can help send alerts when problems are detected while other settings can be used to adjust communication interval, which will directly affect battery life.
How Long will the Batteries Really Last?
Most NCD IoT Sensors are rated for 300,000 to 500,000 transmissions until the batteries become so weak they are unreliable. You could spread these transmissions out over a 10 year period and send 50,000 transmissions per year. This would allow up to 136 transmissions per day, or about 5 transmissions per hour (for a 500K sensor, or 3 per hour for 300K sensor). If you only need the batteries to last 3 years, you could send 166,666 transmissions per year, or about 456 transmissions per day (about 19 transmissions per hour for a 500K sensor). As you can see, battery life is really up to you. By altering advanced settings in the NCD IoT sensor, you have control over longevity. Please note the 500,000 transmission rating is for premium alkaline batteries. NCD ships all sensors with premium Lithium batteries, which include a ultra-wide temperature range that typically lasts in excess of 600,000 transmissions for some sensor types. These batteries weigh less than half of alkalines, and they work in the freezer! A word of caution though, putting a sensor in configuration mode will drain the batteries very quickly. It’s important to configure your sensors and exit configuration mode as soon as possible or use a external power supply during configuration (if supported by the sensor). The table below indicates how many Transmissions Per Hour (TPH) your can expect from different sensors over a lifespan of up to 10 years.
| Life in Years: | 1 Year | 2 Years | 3 Years | 5 Years | 10 Years |
| 300K Sensor | 34 TPH | 17 TPH | 11 TPH | 6 TPH | 3 TPH |
| 400K Sensor | 45 TPH | 22 TPH | 15 TPH | 9 TPH | 4 TPH |
| 500K Sensor | 57 TPH | 28 TPH | 19 TPH | 11 TPH | 5 TPH |
| 600K Sensor | 68 TPH | 34 TPH | 22 TPH | 13 TPH | 6 TPH |
| TPH = Transmissions per Hour |
How Do I Change Settings and Examine Raw Sensor Data?
Using our long-range USB wireless modem, users can expect easy operation over a virtual COM port at 115.2K baud. Simply open the virtual COM port of the USB modem and watch data stream in. Optionally, we offer a Wireless receiver that operates over Ethernet. Data from NCD sensors will appear over TCP/IP on port 2101. Simply open a TCP/IP socket, port 2101, to the IP address of the Ethernet modem and see your data stream in to your local area network. We have developed LabVIEW® software for each sensor to change advance sensor settings using both Ethernet and USB modems. Alpha Station also allows display of sensor readings as well as limited configuration (this feature is still in development). Of course gateways are also available for sending data to popular cloud platforms such as Amazon® AWS® IoT, Microsoft® Azure® IoT, and Losant (more information below). We take software samples seriously, so be sure to to check out the “Resources” tab to see code samples for Raspberry Pi, Visual Studio, LabVIEW®, Arduino, Python, and more.
What Frequency Do I Need?
During purchase, you will see three frequency options. Not all options are legal for use in all areas, so it’s important to make the right selection during purchase. We will build your product and accessories based on the options chosen. Here, we will explain these options in much greater detail, but please check your local laws BEFORE purchase.
900MHz for North America (U.S., Canada, and Mexico) | |
| If you are located in North America, the 900MHz Option will provide the longest range currently supported with the best penetration through walls, buildings, industrial equipment, and trees. This option is also the best choice for long range applications. The official Line of Sight rating for this option is 2 Miles with included antennas or 28 Miles with high-gain antennas. We suggest contacting Digi.com for a high-gain antenna recommendation if required. Please check your local laws before choosing this option. | |
868MHz for Europe Only | |
| If you are located in Europe, the 868MHz Option is the only legal choice available at this time. This option offers better penetration through walls, builds, trees, and industrial equipment that 2.4GHz. The official line of site rating for this option is 14.5km using 2.1dBi antennas. Please check your local laws before choosing this option. | |
2.4GHz for Worldwide Use (Except Europe) | |
| The 2.4GHz option should be chosen if 900MHz and 868MHz are not legal for use in your country. Please note this particular module is NOT LEGAL for use in Europe, as it has a higher transmission power than is legally allowed at 2.4GHz. This option is certified for use in the United States, Japan, Australia, Brazil, and South Korea. Please check your local laws before choosing this option. |
LabVIEW® software is used to graph impact events and temperature over time. This software is also used to custom configure advanced detection features.
Applications
- Wireless Impact Detection
- Machine Health Monitoring
- Ideal Component for Predicative Maintenance
- Abnormal Vibration Detection
- Acceleration and Impact Monitoring for AWS® and Azure®
Full Node-RED Support
Use the power of Node-RED to quickly create complex logic flows and temperature alerts without a single line of code!
Where do I send my IoT Sensor Data?
IoT Sensor Data can be sent anywhere you need it. Whether you need IoT sensor data on a desktop computer, an IoT cloud platform, or an embedded platform, we have you covered. NCD IoT sensors broadcast data, so data handling is very easy, expandable, and versatile. Send IoT sensor data to Gateways when you want to talk directly to IoT cloud platforms. Send IoT Sensor data to Modems when you want to talk to local computers. Of course you can always send data to both gateways and modems simultaneously, so you always have access to your sensor data locally and remotely. Use multiple Gateways when you need data redundancy or if you need to send sensor data to multiple IoT cloud platforms.
IoT Sensor Clusters are also possible. You can build a cluster of IoT sensors on every floor of a high-rise building, sending data to gateways and modems on each floor. Clustering makes it possible to keep your IoT sensor data separated for easier management. Each Gateway and Modem can be configured to listen to a different cluster of IoT sensors. Because NCD devices support thousands of clusters, expanding your IoT sensor network is virtually limitless.
Send IoT Sensor Data to Microsoft® Azure® IoT
Collect IoT Sensor Data up to Two Miles Away and send your data to Microsoft® Azure® using the NCD Micro Gateway.
The Micro Gateway for Microsoft® Azure® reports all incoming IoT sensor telemetry, as real-world values, to Microsoft® Azure® through the connected Device Twin, and/or Device to Cloud Messages.
Setup could not be easier. The NCD Micro Gateway uses SoftAP and includes embedded web pages for configuration. Simply connect your WiFi capable computer to the NCD Micro Gateway Access Point and the Configuration Pages will appear. All you need is an Azure® Device Connection String to register this device to your Azure® account and a WiFi network with internet connectivity.
Send IoT Sensor Data to Losant
Collect IoT Sensor Data up to Two Miles Away and send your data to Losant using the NCD Micro Gateway. Leverage the power of the Losant Flow Builder to build a stunning dashboard that displays graphs of sensor telemetry over time.
The NCD Micro Gateway for Losant automatically provisions the gateway on the Losant Cloud and registers all IoT sensors as children of the gateway. Watch IoT Sensor data arrive on the Losant cloud with minimal setup time.
Setup could not be easier. The NCD Micro Gateway uses SoftAP and includes embedded web pages for configuration. Simply connect your WiFi capable computer to the NCD Micro Gateway Access Point and the Configuration Pages will appear. All you need are Losant connection credentials (Application ID and Application Token) and a WiFi network with internet connectivity.
Learn More about the NCD Micro Gateway for Losant Here
Losant is an Official Partner of National Control Devices, Learn More about Losant Here.
Send IoT Sensor Data to Amazon® AWS® IoT
Collect IoT Sensor Data up to Two Miles Away and send your data to Amazon® AWS® IoT using the NCD Micro Gateway. Leverage the power of the Amazon® AWS® IoT to connect to the complete ecosystem of NCD IoT Wireless Sensors. The NCD Micro Gateway for Amazon® AWS® automatically provisions the gateway on the Amazon® AWS® Cloud and registers all IoT sensors as children of the gateway. Watch IoT Sensor data arrive on the Amazon® AWS® cloud with minimal setup time.
Setup could not be easier. The NCD Micro Gateway uses SoftAP and includes embedded web pages for configuration. Simply connect your WiFi capable computer to the NCD Micro Gateway Access Point and the Configuration Pages will appear. All you need are Amazon® AWS® connection credentials and a WiFi network with internet connectivity.
Send IoT Sensor Data to your MQTT Broker
Collect IoT Sensor Data up to Two Miles Away and send your data to your own MQTT broker using the NCD Micro Gateway. Build your own cloud using the complete ecosystem of NCD IoT Wireless Sensors. The NCD Micro Gateway for MQTT sends JSON strings in human-readable values for easy integration into your own dedicated cloud applications.
Setup could not be easier. The NCD Micro Gateway uses SoftAP and includes embedded web pages for configuration. Simply connect your WiFi capable computer to the NCD Micro Gateway Access Point and the Configuration Pages will appear. All you need are MQTT credentials and a WiFi network with internet connectivity.
Send IoT Sensor Data to Visual Studio
We Developed Alpha Station using Visual Studio to demonstrate how IoT sensor data can be received and converted to real-world values. Alpha Station allows you to view and set basic configuration settings of remote sensors up to 2 miles away. Alpha Station supports our Wireless USB Modem and our Wireless Ethernet Modem. The source code and run-time application is available for download on our web site at https://ncd.io/alpha.
Send IoT Sensor Data to Node-RED
NCD Node-RED Libraries are always expanding, you can read about how to integrate our sensor into Node-RED Here.
We Developed a complete set of Drivers for Node-RED, so you can build your own flows and dashboards to help get you connected. Send NCD IoT sensor data to Node-RED and use flows to build logic operations to send alerts or turn things on or off. Combining Node-RED with NCD IoT sensors gives you limitless power to monitor, control, and visualize data locally and remotely.
The Node-RED Flow Builder is powerful, allowing you to build complex graphs and dashboards in minutes. Node-RED may also be used for advanced Gateway applications, so you easily send data to your favorite IoT Cloud service such as Losant, or Azure®, or Amazon® AWS®. Since Node-RED runs on a local computer, you should use one of the Modems below for communication to NCD sensors up to 2 Miles away.
Send IoT Sensor Data to LabVIEW®
Configure & Test IoT Sensors with LabVIEW®
We Developed a complete set of tutorials for working with NCD IoT Sensors using LabVIEW®. Use LabVIEW® to configure advanced sensor settings or to graph incoming sensor data. Monitor the battery level of remote sensors and watch sensor data flow over time. We will be adding source code for LabVIEW® in the future, please contact us if you have a urgent need for LabVIEW® source code. Since LabVIEW® runs on a local computer, a USB Modem or Ethernet Modem is required.
Data Logging
Using our LabView software, data logging from a single sensor is also possible. Simply run the software and watch the graph fill with data over time. Export the data into comma delimited tables for use in Excel or into other data analysis tools. Logging data from multiple sensors simultaneously is not supported at this time in our software, but can easily be accomplished using Losant or Azure web services.
Please check the “Resources” tab above for resources relevant to this product or Click Here to see all of our LabVIEW® resources.
IoT Security and Transparency Statement
All IoT Device Manufacturers should commit to IoT Security and Transparency. As a consumer, you have the right to a IoT Security and Transparency Statement BEFORE purchase, and we encourage all customers to demand this information from all IoT Manufacturers and Vendors. In an effort to be fully transparent with our customers, we will always disclose the most important security related information at the bottom of each product page for all IoT Devices. Under no circumstances does NCD use IoT devices to collect customer data, sensor readings, or other information without full disclosure. As a matter of NCD IoT Security Policy, any IoT device that collects any form of data must be disclosed in the IoT Security and Transparency Statement. Relevant Security Information pertaining to this particular device is Indicated Below:
- This Device does not directly communicate to the internet
- This Device requires a Gateway for communication to the internet
- This Device Uses 128-Bit AES Encrypted Wireless Communications (Minimum)
- This Device is Equipped with a Default AES Encryption Key Common to All NCD Wireless Sensors at the Time of Shipping
- Users Have the Ability to Change the Default AES Encryption Key
- This Device Requires Physical Access to Change the AES Encryption Key
- This Device Does Not Have the Ability to Communicate to NCD Servers
- Firmware Upgrades Require Physical Access to this Device by NCD Engineers ONLY
900HP-S3B Industrial Wireless Mesh
Long-Range Wireless Mesh networking is our favorite of all wireless communication technologies. This is the ONLY communications technology NCD recommends on the factory floor, operating at a safe 900MHz. Mesh technology will hop data from one location to another to reach its intended destination, users do not need to do anything other than make sure wireless modules stay within hopping range of each other. We use the Digi 900HP-S3B module in many of our products, as this is the best industry has to offer. With a 2 mile range between modules and up to 8 hops, it is possible to cover 16 miles of wireless territory using this technology. Using high-gain antennas, this module is capable of communicating to a remote module up to 28 miles away. Please note that data hopping only works between live devices. Data will not hop between sleeping sensors. Data will hop from sensors to gateways and modems. Data will also hop between gateways and modems.
