Table of Contents
Advertisement
CHAPTER 11: TIPS AND TRICKS
NOTE: The previous information needs to be read like approximately 25 physical and virtual sensors counted
together plus the actions. For example, 5 actions, 5 physical sensors, and 15 virtual sensors. Using your own
database or a centralized redundant database for many units changes these calculations dramatically depending on
the power of your database server.
11.1.10 DATA STORAGE
The size of the provided SD card is 64GB. Since aging is, by default, one month, historical data and logs with entries older
than 30 days are purged. You may change that value in the top left menu Settings. You may decide to store certain
values and not to store other values by clicking on the Edit option for virtual sensors or datapoints.
11.1.11 IP CAMERA LIVE FEEDS
A Dashbox can be of Type IP Camera for live feeding pictures onto the dashboard and into that Dashbox. Since this
feature needs web browser capabilities, not all URLs from your IP camera may work. However, many cameras have an
URL that provides an image as a snapshot. Since Dashboxes are actualized every second this may work for you as well.
Dashboxes with IP Camera Live Feeds can never be interactive. See below.
11.1.12 CLOCK DASHBOX
A Dashbox can be of Type Clock. You can visualize the clock as an analog or digital clock. For the digital clock, it can use
either EU 24 hour format or US 12 hour AM/PM format. You can also define an offset to visualize time in other time zones.
Dashboxes with Clocks can never be interactive. See below.
11.1.13 HISTORICAL DATA AND ASSIGNMENT TO DEVICE ADDRESSES
In the LoRaWAN
universe physical sensors being joined are identified by a network-wide, unique Device Address.
®
That is a 32-bit field where the upper bits are for defining the network. If AW3000 tells you it is Device Address 32, the
hexadecimal equivalent with network identifier would be "BB000020."
NOTE: Since Device Addresses need to be unique, a physical sensor gets a new Device Address after every new join
process. Historical data, however, is assigned to Device Addresses.
As a result, you may encounter this situation: You join a sensor which gets Device Address (leaving out the network
identifier part) of 32. You collect historial data for one week. Then someone, by chance, hits the reset button of that
sensor, and a new join process happens. Since the Appkey never changes for a physical LoRaWAN sensor unless you
change it, you have new datapoints for Device Address 33 not ,connected to the historial data of Device Address 32.
For that case, there is that button MV in the sensors page. That allows you to assign the historical data behind that
datapoint to another Device Address.
Since there are many variations of LoRaWAN sensors, this is the best solution in this circumstance. Also consider that
some sensors do not remember having joined a network when unplugging the battery.
The alternative is to enable Automatic Rejoin in Settings. (See "Settings" in this manual.)
11.1.14 MISSING REMOVE BUTTON
Once you joined a sensor, you can't remove it. If you remove datapoints for this sensor and if that sensor is still active, with
next data transmission the removed datapoints return. Removing a datapoint mainly deletes historical data.
If a sensor is joined, but is no longer transmitting for more than one hour, the Remove Button is shown again. By
removing that sensor, all information about the join process and established encryption keys is lost. Removing the sensor,
however, does not automatically remove the datapoints.
11.1.15 UNLOCK CODE
The unlock code is provided to you by a Black Box tech support team member. The Black Box tech support team
member needs to know the EUI64 ID of your unit. You can view that on the start screen or in settings.
42
1.877.877.2269
BLACKBOX.COM
NEED HELP?
LEAVE THE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
Advertisement
Table of Contents
