October 2016 Release of the daq.io Platform

Adds Tokens and other Improvements

Hello everyone,

We’re proud to release the October 2016 update for daq.io. If features the addition of Tokens to the platform.

The update was rolled out to the servers automatically. Find the updated LabVIEW client ( on our web site for download.


What Tokens are good for
Imagine a typical IIoT scenario: You developed a smart edge device with NI hardware and would like to roll it out to various sites. You are the main developer and you implemented the daq.io access for those embedded systems. At some point you will deploy those systems and will only have limited access to them. You should never have to share your credentials with other users simply to enable them to upload data. Instead you can use Tokens, that are unique IDs you can assign to each data logger. It will allow typical operations such as pushing time series data, event data and waveforms. However, a user that only holds a Token will not have access to the daq.io web interface and will not be able to change any settings for systems and other users. This means, you can easily send out Tokens to end-users which will allow them to upload data. At the same time, this will not compromise your platform security as you do not share any credentials and you can disable Tokens from your account.

How to use Tokens
Tokens really make sense in an embedded datalogging settings. That’s why we added a new example to the updated LabVIEW library, called “daq.io Embedded Machine Example with Token”. It demonstrates what the Tokens can do.

Use a Token, step-by-step:
1. Create a Token from your user profile page (click your user name top-right). Click the green “+” button on the Tokens field to add a new Token.

2. Select an existing device, edit to assign a token. Save it. (If the token is unassigned and no device exists with the client name, the LabVIEW example can generate a new device, too)

3. Find the LabVIEW example.

4. Enter your Token and run.


Other improvements include higher overall stability, improved user rights management, improved on-device buffering and bug fixes in the LabVIEW client and the API.

Let us know how you like it!

-Peter (daq.io)