1. A snapshot of the Sensor Demo project config
This page presents the different panes available in the IoTize Studio Graphic User Interface.
If the Sensor Demo project isn't open, use File / Open C:\Program Files (x86)\IoTize\IoTize Studio\Examples\Sensors_STM32_Demo\Sensor_demo.iotz
Studio
These settings determine how Studio connects to the Tap and where the Webview is stored. By default IoTize Studio generates the HTML pages in a subfolder of the project file.
Note: Unlike the other options, the 'Studio' settings concern only the development environment and are not uploaded to the Tap.
Target System
Expand the IoTized Application, and observe the Target System settings. They specify the target board (if any) and the type of connection between TapNLink and the target board.
Tap
Development Tap SN is the Serial Number of your TapNLink (the generic serial number (IoTzPr004100000000) becomes your Taps serial number when you connect to it). The other options determine the general behaviour of your Tap regarding the security, low power modes,...
Incoming communication (Wireless)
These settings define which radio protocol will be used between the Tap and the mobile device. They also detail the modes for each protocol.
Mobile App
These settings specify the type and the contents of the mobile application.
IoT Platform
These settings specify whether an IoT platform should be used; either to control the Tap remotely, or to store information, for example datalogging.
Resources (variables)
List of the available resources for the bundle contents. Bold resources are already linked with a bundle.
Click on a resource to see more information about it. The Id number is unique and can be used by software to access the resource.
Bundles
Below, 'sensor demo' has 3 bundles with associated users. Click on the users to see their read/write permissions.
Profiles and Users
A Profile can be linked to bundles with specific rights. A User just inherits the rights of the parent profile. A User has a specific password.
The Tech profile has 2 users: user and Paul. Passwords can be given to them and to the parent profile.
