NimbeLink Asset Tracker

NimbeLink’s family of Asset Tracking devices are ruggedized, function both indoors and out, and deliver exceptional battery life. With up to 14 years on a single set of batteries, each device is globally capable, highly configurable and designed to seamlessly connect. From simple tracking to fully featured monitoring, NimbeLink Asset Trackers are designed to fit the broadest array of use cases, business models and budgets. Whatever you want to track, and wherever you want to track it, there’s a NimbeLink solution that’s right for you.

Online resources

You can learn more about the NimbeLink Asset Tracker product from the manufacturer’s product page here

Using with Atmosphere IoT

Registering devices

You will need to get into contact with sales at Atmosphere IoT Corp. or your NimbeLink sales representative to have you on boarded into Atmosphere IoT’s solution. Once your devices are connect to Atmosphere IoT they will be placed into your IoT central organization.

Device Settings

The NimbeLink Asset tracker has configuration parameters that can be set by the user that can change the reporting time, and types of notifications that you will receive from the device.

Check-in rate

This controls how often the Asset Tracker will report it’s sensor data to the cloud. You can set this value from 15 minutes to 10080 minutes. Changing the frequency of the device’s check-in rate can greatly effect the battery life.

Note that if your check-in rate is longer than your other sample rates you will still only receive all the sampled data points during the check-in event.

Location sample rate

This controls how often the sensor attempts to get a location sample and report at the next check-in. You can set this value from 5 minutes to 1440 minutes.

Temperature sample rate

This controls how often the sensor will make a temperature reading as well as humidity if available and report at the next check-in. You can set this from 5 minutes to 1440 minutes.

Accelerometer sample rate

This controls how often the accelerometer will take a reading and report at the next check-in. You can set this from 5 minutes to 1440 minutes.

WiFi Location Enable

This will control if the device should attempt to scan for WiFi APs when a location reading is taken.

Cell Location Enable

This will control if the device should attempt to scan for cell towers when a location reading is taken.

GPS Enable

This will control if the device should get a GPS fix when a location reading is taken.

Temp Enable

This will control if the device should make any temperature readings. This also controls reading humidity on models that support it.

Accelerometer Enable

This will control if the device should use it’s accelerometer at all.

Accelerometer Mode

The asset tracker supports several modes for it’s accelerometer.

  • 0: Disabled mode is the same as disabling the accelerometer. No accelerometer readings are ever made

  • 1: After movement is completed, locate the device. No raw X, Y, Z accelerations are recorded in this mode.

  • 2: During movement, locate the device. No raw X, Y, Z accelerations are recorded in this mode.

  • 3: Measure accelerometer periodically. This mode will simply periodically sample the accelerometer and send the raw data up to the cloud

  • 4: Tilt detection. This mode will periodically check the device’s tilt orientation and generate an event if it’s changed.

Geo-fence Enabled

This will enable the use of a geo-fence on the device.

Users will receive notifications from the Asset Tracker when the geo-fence is either exited or entered.

Geo-fence center point

This selects the center point of the circular geo-fence

Geo-fence radius

In meters the radius of the geo-fence circular perimeter from the center point.

Geo-fence buffer

In meters this will create an extended “grace” area around the geo-fence.

For example if your device was 20 meters from the center of the geo-fence and the geo-fence radius is 10 meters. If the buffer is 5 meters and the error on the GPS is 5 meters then the device is still inside the fence because the distance from the center of the fence was not greater than the radius of the fence plus the buffer and the error in the GPS reading.