Cockatoo NBIOT (Telstra) - Pulse Counter
Note : Due to the breadth of information related to the Cockatoo the release notes below should viewed in partnership with Cockatoo User Guide.
Overview
The Cockatoo is a flexible telemetry solution, and this variant is being released as:
NBIoT Cockatoo - pulse counter using with Alpha TOPS firmware
As at September 2023, our intention is to release up to 200 units, whilst we wait for the final release version of firmware ( in early 2024). After final firmware release devices will be locally updated via NFC onsite, or physically swapped out with a device using the final firmware. Once the new firmware is available, we will cease producing the Alpha firmware variant.
Table of Contents
- 1 Overview
- 2 Device Specifications
- 3 Released Variants
- 4 Taggle Operations
- 4.1 NBIoT Communications
- 4.1.1 Data Usage
- 4.1.2 NBIoT Identifiers
- 4.1.3 Jasper
- 4.1.3.1 Redash URL
- 4.1.3.2 Step 1 - using tag id to lookup IMEI
- 4.1.3.3 Step 2 - using IMEI to lookup ICCID
- 4.1.3.4 Step 3 - lookup ICCID in Jasper
- 4.1 NBIoT Communications
- 5 Tools and Aqualus
- 5.1.1 Example of Taggle Tools
- 5.1.2 Delivery Bundle and Delivery Methods
- 5.1.3 Data Delivery
- 5.1.4 Aqualus Water
- 5.2 Frequency Asked Questions
Device Specifications
Cockatoo Functional description
Radio - NBIoT - Band 28 NBIoT radio using Telstra for communications ( Quectel BC66 radio modem)
SIM card - this Telstra NBIoT SIM is provided and managed by Taggle
Sampling - default is 15 minutes net flow pulse counting samples ( with direction flag for monitoring reverse flow).
Transmissions - once per day (which is a rolling 24 hours since the last SWIPE of the Cockatoo)
i.e. If the SWIPE was at 4pm, then every 4pm there after will be the daily transmit time.
Battery - 2 x D-cells (optional special build is 4 x D-Cell )
Live Swipe - Radio connectivity check to IOT platform (note this is straight YES or NO). RSSI is not currently supported.
NFC - NFC enabled for commissioning and determining device status
Environmental protection - IP68 rated.
Bracket - Stainless Steel bracket with hose clamp restraint.
Protection Cap (Optional extra) - for locations at risk of vandalism or possible animal damage, the protection cap conceals the plugs and cables.
(Taggle Commentary - internal use )
Encryption - does not support encrypted communications in the Alpha firmware release
Firmware Over the Air (FOTA) - does not support updating firmware-over-the- air (FOTA) in the Alpha firmware release.
Commercial Firmware update - Taggle intends to either physically swap these devices once the commercial firmware is released, or locally update the firmware via NFC. The final plan is still to be determined.
NFC - When executing an NFC read the “Last Reading” field, which represents the pulse count will not update as pulse counts increment. Naturally the radio message will have the correct pulse counts. This will be fixed in the commercial release.
Inside the Cockatoo
User guide
The links are to the Cockatoo (all radio type) User Manual/ Quick start guide;
https://taggle.jira.com/wiki/spaces/PROD/pages/6841598016
Released Variants
The table below lists the main and expected high volume SKU and the second table representing the complete list with non-stocked but released SKU variants.
Main SKUs (Stock Keeping Units)
| Power | Antenna | Product Code | Product Description | |||
Variant | 2B | 4B | Ext. | Int. | Ext. |
|
|
Pulse Counter | Y |
|
| Y |
| CK2-C1-I-2B-0-0-PCA-AU | Cockatoo - NBIOT Band 28 radio with internal antenna and 2 x battery for pulse counting sensor, sampling once every 15 minutes and one transmission per day - Aust. version |
Pulse Counter | Y |
|
|
| Y | CK2-C1-C-2B-0-0-PCA-AU | Cockatoo - NBIOT Band 28 radio with external antenna and 2 x battery for pulse counting sensor, sampling once every 15 minutes and one transmission per day - Aust. version |
Special Build not held as stock
Highly unlikely we will produce any of these variants in the initial 200, but they will be offered in the final commercial released version.
| Power | Antenna | Product Code | Product Description | |||
Variant | 2B | 4B | Ext. | Int. | Ext. |
|
|
Pulse Counter |
| Y |
| Y |
| CK2-C1-I-4B-0-0-PCA-AU | Cockatoo - NBIOT Band 28 radio with internal antenna and 4 x battery for pulse counting sensor, sampling once every 15 minutes and one transmission per day - Aust. version |
Pulse Counter |
| Y |
|
| Y | CK2-C1-C-4B-0-0-PCA-AU | Cockatoo - NBIOT Band 28 radio with external antenna and 4 x battery for pulse counting sensor, sampling once every 15 minutes and one transmission per day - Aust. version |
Taggle Operations
NBIoT Communications
Taggle is using the Telstra NBIoT network for all our NBIoT products. We are initially sourcing these NBIoT services via a Telstra reseller, M2M One. The SIMs are removable plastic Nano SIMs in the Cockatoo, but are dedicated to the NBIoT network.
Data Usage
Each Cockatoo Pulse Counter is allocated 85kb per month data allowance. Using TOPS protocol the Cockatoo (based on our test devices and 2000 transmission days) is expected to consume between 40Kb to 55Kb per month in the data.
Substantiation for < 85Kb pm
Data usage analysis - for reference purposes
NBIoT Identifiers
Tag ID - The Taggle ID (Printed on the side of the Cockatoo)
ICCID - SIM card serial number, and used to interrogate Jasper
IMEI - the NBIOT radio modem serial number. (Printed on the side of the Cockatoo)
Jasper
Network connectivity validation should be done using Jasper and looking up the IMEI or ICCID using the Redash Query below;
Redash URL
Step 1 - using tag id to lookup IMEI
Step 2 - using IMEI to lookup ICCID
Step 3 - lookup ICCID in Jasper
URL - https://cc10.jasper.com/provision/jsp/login.jsp
ICCID Dashboard
Spotlight investigation
Tools and Aqualus
Example of Taggle Tools
Delivery Bundle and Delivery Methods
The NBIOT Cockatoo uses the same business-as-usual Byron type Delivery Methods and Delivery Bundles. Hence CSV data is delivered to Aqualus Water.
Data Delivery
As a result of the data delivery being a rolling 24 hours after the SWIPE Event.
Example - A 4pm swipe will mean all future daily data deliveries will occur at 4pm. This will mean the CSV file for a given day will be missing in this example, data from 4pm to 12pm (8 hours) when published to Aqualus Water overnight.
Customer expectation should be aligned to this operating model.
Aqualus Water default leak and data continuity reporting is not set to less than 24 hours, and hence this should not present an issue for customers. Customers just need to be aware the prior day’s data will be partially complete ( based on the original activation time), but the remaining data which is missing will be delivered during the next day’s data delivery.
Aqualus Water
The Aqualus Water Managed Models for all NBIOT Cockatoo variants will be loaded into each Aqualus customer instances by default. For examples purposes the CK2-C1-I-2B-0-0-PCA-AU is the image below.
Below is an NBIOT Cockatoo pulse counter, counting every 15minutes, and sending data at 4:15pm
Currently the IOT Platform does NOT support real time report updates for NBIOT devices.
Frequency Asked Questions
Main source is the Cockatoo User Guide (above)
How will the Alpha firmware differ from the commercial release version ?
The Alpha firmware behaves differently to planned commercial release version in the following ways;
NFC reading will NOT present the increments in the “Last Reading”, but will transmit the pulse counts via the radio transmission
Radio transmission are a rolling 24 hours after the SWIPE Event, hence a 4pm swipe will mean all future daily data deliveries will occur at 4pm.
No encrypted radio transmissions
No ability for remote firmware updates.
Does the device account for changes in day light saving time ?
No the firmware does not adjust the radio transmission for changes in Day Light Saving time.
Missing daily data?
If the tag is unable to have it’s message received by the NBIOT network, owing to obstructions or radio impediments, that day’s date will not retransmitted and essentially lost. This will be corrected in future firmware release, such the data needs confirmation of receipt.
What does the NFC read look like ?
The NFC screen below shows the device in FLIGHT MODE.
The NFC screen below shows the device in ACTIVATED mode, having exited FLIGHT MODE
Which Taggle Visualisation platforms support these Cockatoos?
Aqualus Water - MDMS : Supports the Cockatoo - Pulse Counter, in similar way to a standard SP3C or HP3D tag.
Aqualus Water - Field Operations App : Supports the Cockatoo - Pulse Counter, in similar way to a standard SP3C or HP3D tag.
The Cockatoo with it’s D-cell batteries of a Class( dangerous good and as result has a special product packaging box.