Skip to content

IoTize Studio

Installation procedure

  1. Download from this address (  (takes about 2 mins)
  2. Open the zip file and double-click on the IoTizeStudio_nnnn (nnn = version number)
  3. Allow this app from an unknown publisher to modify your PC
  4. Confirm you want to extract and launch the installation
  5. Click View Readme for additional explanations (optional)
  6. Click Install IoTize Studio
  7. If needed, change the installation directory (C:\Program Files (x86)\IoTize\IoTizeStudio by default)
  8. Click Start install
  9. Click "I agree" in the End-User License Agreement
  10. Click Finish when the installation is complete
  11. Check IoTize Studio is accessible in your Windows start menu  
  12. View the directories in the installation directory:
    • Bin and Drivers should never be modified
    • Doc (PDF format of the current on-line documentation)
    • The Examples directory contains:
      • The Sensor Demo which is used in the getting started documents :
        • The project file (senso_demo.iotz) contains the settings used by the demo, which can be edited with IoTize Studio
        • A generic TapNLink serial number: IoTzPr004100000000
        • All other configuration variables (bundles, variables, …) are identical to the configuration file stored in your Tap.
      • DemoClock and Mems examples illustrate more specific and advanced features of TapNLink
      • Terminal and *Sepam" examples more specific and advanced features of TapNPass (including access to target system via ModBus)


IoTize Studio is a PC-based configuration software which allows you to:

  • Edit, test and transfer configuration data used by the TapNLink module (also referred to as the Tap)
  • Automatically generate a Web App to monitor your target system
  • Set options used to connect your Taps (TapNLink or TapNPass) to IOT platforms (IoTize Primer Cloud Platform in the case of the Primer)

Before exploring the detailed options of IoTize Studio, we strongly advise you to:

This user manual covers both TapNLink and TapNPass product lines.

  • When no precision is given, the feature is relevant to both product lines
  • When an option is relevant only for one product line, it is indicated
  • A dedicated section at the end of this reference manual recaps the options relevant for TapNPass
  • We strongly advise you to set the type of target at the very beginning:
    • expand the menu IoTized Application (on the upper left)
    • click on Tap
    • set the Type of target option : 'MCU(TapNLink)' for TapNLink or 'System(TapNpass)' for TapNPass

IoTize project structure

The core concept for IoTize Studio is the notion of project (.iotz extension).

  • A project can be seen as "master configuration file", which configures the different components of the IoTize solution: Tap, Smartphone monitoring application, connectivity modes to IOT platform
  • Project examples (for both TapNLink and TapNPass) like Sensor_Demo are in the installation directory
  • Project information is split into:

    • Tap configuration

      • stored in a dedicated file (.xml or .izsc)
      • can be read from a Tap by IoTize Studio (menu Configuration > Read from Tap)
      • can be written to a Tap by IoTize Studio (menu Configuration > Write to Tap, or button Configure)
      • covers all settings used by your Tap to perform:
        • monitoring: IDs and address of variables to read or write, security information, pairing
        • data logging: bundles to log and related frequency
    • Cloud services configuration

      • stored in a dedicated configuration file (.cloud) which is sent to the cloud platform by IoTize Studio (via the button Publish)
      • mainly covers
        • data logging settings (choice of bundles to log in, frequency)
        • visualization settings used by the IOT platform (IoTize Primer Cloud Platform for Primers)
        • for the TapNLink Primer, these options are automatically managed based on the IoTize end-to-end architecture (which includes a MQTT broker and IoTize Primer cloud services).
        • for the standard TapNLink, you need to implement your own architecture. Refer to the Application note "Implementing your own IOT Platform".
    • Mobile App settings

      • type of application: Iotize 'Tap Manager' HTML Web Pages / Generated App/ Other. Refer to Mobile Development for more information about these different choices.
      • options related to the location and deployment (publishing) of your mobile Web App
    • IoTize Studio settings

      • options related to the connection of your Tap with IoTize Studio
      • log options (verbose level, log file)

IoTize Studio GUI

IoTize Studio GUI has several windows which can be undocked, moved, resized, overlapped and closed. Their visibility is controlled from View > Toolbars and Docking Windows. The only exception is the Web Viewer which occupies free space left by the other windows and cannot be closed.


IOTZ Explorer displays:

  • 1a. Configuration pane

    • IoTized Application contains 4 branches: Target, Tap, Mobile app, and Cloud
    • Studio contains general information about the project name and the tap connection
    • Bundles contains information about the resources to be accessed on the target
    • Profiles contains the profiles (pre-defined and custom)
  • 1b. Properties pane: properties of the element selected above

  • 1c. Contextual help of the property selected above

  • 2a. Resources View pane:

    • Symbols refer to addresses in your target application, and can be:
      • retrieved from your ELF file (defined in your C or Assembler source file)
      • retrieved from the SVD file (System View Description) provided by MCU vendor
        • complies with CMSIS/ARM specification
        • can be obtained from ARM website after (free) registration
        • allows to select MCU registers as variables
      • defined directly by the user in IoTize Studio
      • from an XML file (.svd compliant) for ModBus target protocol
    • Features provide complementary ways to access Target resources
      • like symbols, they can be attached to bundles and profiles
      • the built-in Web App Generator is NOT relevant for features
      • example : direct SWD can be used to re-program your target application or remote debugging, for example from RIDE (the Raisonance development environment)
  • 2b. Properties pane: properties of the resource (symbol or feature) selected above

  • 2c. Contextual help of the object selected above

  • 3. Web Viewer (used by the built-in Web App generator)

    • displays the current HTML page when a profile is selected. This display only applies if:
      • you set the option App Type = IoTize Type Manager app in IoTized Application > Mobile App
      • you set the option Automatic Web site generation = Yes in Studio
    • refer to Mobile Development for a detailed description of the built-in Web App generator
  • 4. Output View: displays messages such as configuration errors, inconsistent element detection, tap successfully configured (you can adjust the verbose level)

  • 5. Online help

You can adjust the default display from View Menu and Help menu in the upper bar menu.

Steps to iotize your target application

Create a project

To modify an existing project, open the corresponding project file (.iotz extension)

To create a new project use the menu File > New.

  • Enter the IoTize Tap Configuration File Name and Location
  • Enter your target application firmware’s Elf file (in the field Firmware)
  • Define (approximatively) the number of Bundles and Profiles
    • this creates generic Bundles (Bundle0, bundle1, …) and Profiles
    • you can complete, rename, remove these profiles and bundles, and add new ones later on
  • Create the project 


Define general settings

Modify the settings as required for:

In IOTZ Explorer pane, expand the IoTized Application.

Target options


  • Options for the Type of Target:

    • Select 'MCU (TapNLink)' for TapNLlink or TapNLink-Primer
    • Select 'System (TapNPass)' for TapNPass
  • Target protocol options

    • For TapNLink, the available options are:
      • 'SWD'
        • ideal to make POCs but limited to CORTEX-M MCUs
        • requires that port is enabled
        • does require any adaptation of the target application
      • 'S3P'
        • Serial Software Secure Protocol,
        • mMre secure but requires that SWD a "code object" is added in your target app. See S3P application note for further details)
      • 'Modbus':
        • as SWD and S3P, this mode allows to work with "mapped variables" and relaed features: bundles, Access rights, automatic generation of monitoring App)
      • 'Serial':
        • contrary to the previous modes, 'Serial' does not allow to manage variables in IoTize Studio, nor to use the build-in Web app generator
        • this mode only allows to implement a serial channel between your Tap and your target system
        • as for S3P, it requires an adaptation of your target app
        • the only way to implement it is to to attach the feature 'Serial' to one or several bundles and to build a 'Custom app', using the API (see Technologies/Mobile developement for further details
      • 'DirectIO'
        • can be used in complement of other modes (MCU variables)
        • contact us for other details
    • For TapNPass, the options are (see TapNPass pages for details):
      • 'Serial'
      • 'Modbus'

Tap options


  • 'Development Tap Serial number'
  • Host protocol (protocol between the Tap and smartphone)
    • leave the defaut value ('ALL') except if you want communication to start with an NFC pairing, for security reasons, for example
  • NFC Pairing Mandatory
    • 'Yes' means that pairing will only be performed using NFC, BLE/Wi-Fi protocols will be initiated after pairing.
    • 'Pairing+Login' means that pairing and Login must be done in NFC (BLE/Wi-Fi protocols will be initiated after login).
  • Low Power Optimization Level
    • Set to 'High' if you want the Tap to go to sleep mode when inactive
  • Security

Mobile App options


  • App Type
    • set to 'Iotize 'Tap Manager' HTML Web Pages' if you want to develop a Web App and take advantage of the built-in Web App Generator (refer to Technologies > Mobile development for details)
    • set to 'Generated App' if you want to use the mobile app generator coming with IoTize CLI(refer to Technologies > Mobile development for details).
    • set to 'Other' if you want to developp you own app (native or hybrid), using the APIs.

Options dedicated to the "Web app" mode

  • Name

    • the Web app name is displayed in Tap Manager
    • it is alos dislayed in the BLE / Wi-Fi device lists when scanning for BLE / WiFi devices
    • by default the app name is the projet name
  • Location of your Web App:

    • 'Primer Development Server' ( is only relevant for TapNLink Primer (and sometimes for Taps which have been provisionned in IoTize cloud servers)
    • 'Internal storage of your smartphone'
    • 'SD card'
    • User defined location
  • URI
    • corresponds to the home page for the automatically generated Web app
    • this page is automatically retreived by Tap Manager and executed in its built in viewer)
    • by default, the value is *'SerialNumber/SerialNumber.HTML'
    • it can be a URL if you are using a server

Options dedicated to the "custom app" mode (using the APIs)

  • Name : used in
  • Tap NFC tag block :
    • contains the reference of app in the respective stores (Apple Store or Google Play)
    • this reference is stored in the NFC tag of your Tap, so as to lannch automatically you app when you tap your TapNlink (or TapNPass)

Cloud options


  • Cloud service availability
    • set to 'No' if you are not interested in the 'cloud features' (related to data logging)
    • set to 'Yes' if you want to use a cloud platform to recover and display the data logged in the tap
      • for TapNLink Primers (or more generally for taps provisionned in the IoTize cloud servers), an implementation is proposed, which implies the following components:
      • option Send config to IoTize platform (for the Primer)
        • 'Yes': the config will be uploaded to the IoTize Primer cloud service whenever you publish the Web App, which means you previous data will be erased
      • option Minimal period for cloud transmission
        • this option is used by Tap Manager to retreive and send the data to IoTize cloud services (through the MQTT broker)
        • '0' : no MQTT transmission (no relay, the logged data is not uploaded)
        • 'n' (> 0) : number of seconds between 2 uploads

Studio (environment) options


Block 'Website Developement and monitoring Test'

  • These options are only relevant when the option Mobile App / Type from the Mobile App main menu is set to 'IoTize Tap Manager App' (Web app mode)
  • Automatic Website generation option
    • 'No' :
      • displays the web app defined in the option Website Path for Monitoring (see hereafter)
      • this allows for example to access to a "customized Web app", developped from the web app previously generated by IoTize Studio
      • a "customized Web app" can include logos, gauges an is developped using CSS and HTML tools
    • 'Yes' :
      • displays the HTML pages dynamically generated by the built-in Web App generator.
      • these pages are automatically updated when you apply changes such as adding/removing variables, access rights, labels of variables or units, formatting options...
      • the location of this web app is defined in the Studio / Website developement and monitoring test/ Generation subfolder option (the folder corresponding to the name of your project, for example Sensor demo)
      • it is important to understand the naming convention of the HTML pages, so as to define the home page option
      • the HTML page number is nnnnnnnnnn.profileID.html where:
        • 'nnnnnn' is the serial number of you tap
        • 'profile ID' is the ID of the profile
          • for exmaple 65535 is for admin , 0 for annymous
          • the profile ID can be recovered from the menu Profile/ Profile name
  • Website Path for Monitoring option
    • this option contains the url of the Web App you want to test from IoTize Studio (using the monitoring command)
    • this option can refer to:
      • a directory of your PC or your entreprise network (for example 'C:\Program Files (x86)\IoTize\IoTize Studio\Examples\Sensors_STM32_Demo\index.HTML' )
      • the "deployment location" of you app on a cloud server (in the case of the primer, it could be for exemple '')

Block 'Project'

  • Autoincrement version:
    • if 'No' is set, the new version overwrites the saved config file

Block 'Connection to Tap '

  • Protocol option
    • this options refers to the connection channel between the Tap and the PC.
    • implemented protocols in the current version of IoTize Studio are:
      • 'BLE':
        • To use direct BLE communication you need to have a BLE enabled PC with Windows 10 build 10586 or newer).
        • refer to this link for further details.
      • 'Socket relay' and 'MQTT Relay':
        • for BLE Taps, this requires to use the smartphone as a relay.
        • refer to this link for further details.
      • 'UART' (used for production and 'mass configuration").

Define profiles

Expand IOTZ Explorer > Profiles


The profile defines a group of users that have the same access rights (these rights are defined in the bundles). When a profile is selected the Web View shows the HTML page associated with this profile (with the bundles it can access).

There are 3 predefined profiles:

  • admin has full rights (read/writes) on all bundle. It is the only profile authorized to execute a “Factory Reset” or reconfigure the .iotz file. There is no method to recover this password yet, so keep it in a secure place.
  • supervisor can modify logins and passwords (except the administrator password)
  • anonymous provides the initial login screen. It does not require login. Everyone has anonymous rights as a minimum, so if you associate it with a bundle, everyone can access this bundle.

You can create additional profiles to meet your specific requirements. For example, you can add a profile "Maintenance" or "Technician", as in the Sensor Demo example.

  • Add profile: right-click Profiles, select New Profile and provide an initial password
  • Modify profile: click Profile and modify the properties pane:

    • Description: kept in the .iotz file on the PC
    • LifeTime: duration before timeout (mins)
    • Window Color: used in the WebView pane (enables to distinguish each profile’s HTML page)
    • Login: your choice
    • Password: your choice
  • Rename/Delete: right-click Profile and select Rename/Remove

  • A profile name can be up to 16 characters
  • Items in blue can be modified

Define users

Users are just aliases of profiles and are not really individuals, their access rights are inherited from the parent profile.

This mechanism is simple to implement and avoids sharing passwords between individuals.

  • Add User: click on a Profile and select New User. Add the Name, Description, Type of Login (user name and password, or Security Key) and Password
  • Rename/Delete: right-click User and select Rename/Remove

Our cloud-based user and token management systems (planned for Q2 2019) could be interesting if you envisage:

  • High numbers of users
  • Frequently changing users
  • Limited user rights (in time or number of sessions) Ask us directly for further information. 

Define bundles

A bundle contains several variables, and has profiles attached to it, with read or write access to all the variables in a bundle.

When a bundle is selected, it appears as an Active Bundle in the menu bar of the window.

  • Add Bundle: right-click Bundles, select New Bundle. Provide a name and description in the properties pane.
  • The bundle stays red until a profile has been added, to remind you to add a profile.
  • Rename/Remove: right-click Bundles and select Rename/Remove.


Add profiles and users to bundles

You can add several profiles to a bundle, and give them different access rights (as we did with the profile Count_Control in the Sensor Demo example).

Each users access right applies to all the variables in the bundle.

  • To link a Profile/User to a Bundle (to give a user access to this bundle):

    1. Select the Bundle (check it appears as the Active Bundle).
    2. Select the Profile/User that you want to add.
    3. Drag the Profile/User to the Bundle.
  • To set the access rights of Profile for a Bundle:

    1. Expand the Bundle and click on the Profile name.
    2. Set the Access rights corresponding to this combination Bundle + Profile in the Properties pane. Access rights can be read or write or both.

Add resources to bundles


Add variables

  • To add a Resource to a Bundle:

    1. Select the Bundle.
    2. Right-click the Symbol (or the Feature) in the Resource View.
    3. Select Add to current bundle.
  • To add an array element to a Bundle:

    1. Select the Bundle.
    2. Expand the array in Symbols View.
    3. Right-click the array element and Add to current bundle.


There are 3 types of symbol:

  • Embedded application symbols (purple icon), defined in the ELF file. It is NOT recommended to use large elements, it is better to add just a sub-element to a bundle.
  • MCU registers of the microcontroller (blue icon), defined in the SVD file from the microcontroller manufacturer (can be downloaded from the ARM website after free registration). The size of registers is limited to a word (32-bit register).
  • Custom symbols (green icon). You can define your own symbols and related properties in the following cases:
    • you can create customized symbols based on information in the MAP file, if you have no access to the ELF file
    • you can add specific addresses that are not mapped as variables in the ELF file
  • Note that after a symbol is attached to a bundle, it is referred to as a variable (in the configuration and in the Web App generator).

Add features

  • In addition (or as an alternative to variables), you can attach Features to bundles
  • There are 3 Features which enable you to access "resources" in your target application via APIs (refer to the Application development center for details)

  • 'Serial':

    • cover both the Send and Get functions
    • in this case, the TapNLink is used create a simple serial communication channel between the mobile device and the target
  • 'Modbus Direct':
    • can address any Modbus register
    • address has to be passed as a parameter
  • 'SWD Direct':
    • allows to access any address in the memory of a Cortex device.
    • this feature is generally used to debug or program the target system.
    • it must be handled with care (secutiry issue) and attached to a dedicated profile (with restrited population)
  • Complementary notes:
    • the built-in Web App generator is not relevant when a Feature is attached to a bundle (you have to use the APIs to developp your monioring app)
    • it is possible to mix access controls based on variables (for certain profiles) with access controls based on Featuress (for other profiles)
    • the Feature 'TapNPass control' does not apply to the current version

IoTize built-in Web App generator

IoTize Studio has an embedded Chromium browser that provides the infrastructure for HTML rendering and JavaScript execution. The embedded JavaScript execution context exposes the same 'IoTize JavaScript API' as Tap Manager App, therefore you can conveniently build and test your HTML+JavaScript pages. You can even access the built-in Chrome DevTools to further debug your HTML pages. Refer to Chrome DevTools documentation to learn more about the debugging capabilities of Chrome browser. See Getting started for examples.

  • Set the option Automatic Website Generation in Studio (in the IOTZ Explorer pane) to Yes
  • Observe the Web Viewer
    • expand Profiles and select a profile. You can see the corresponding page in the Web Viewer
    • the pages take into account the read/write access rights for each bundle
    • you can define the window background color for each page
  • Change some variables and observe the HTML page is dynamically updated. Click on a variable in a bundle (for example Period in the bundle Count_Control) and change the detailed settings:

    • Display in HTML (Y/N): Show this in the auto-generated HTML pages
    • Propose Submit (Y/N): Permit modification of this value from the HTML pages
    • attach an Alias to the variable
    • define the number of digits (for float variables)
    • set an Expression to change the displayed value. For example, you could use this formula $/1000.0 to display V instead of mV, where $ stands for original value.
  • The monitor button toggles monitoring On and Off

  • Refer to Technologies/Mobile development for a description of the underlying mechanisms (javascript code generation, IoTize APIs...)

Configure data logging

Data is collected by stored in an EEPROM of the Tap () and can then be uploaded in a cloud server. This mechanism is preconfigured for TapNLink Primer and is based on the IoTize Cloud Prime
See Getting started for examples.

  1. Select a bundle.
  2. Set the DataLog Period (Set to 0 to disable data logging).


Connect your Tap to IoTize Studio

  • Open the menu 'Studio' on the top left pane and view the detailed settings underneath.
  • The option to set is 'Connection to Tap / Protcool'

    • BLE if you PC is BLE enabled and you have Windows 10 installed on your PC.
    • Other Acceptable values are 'MQTT'(requires a MQTT broker) and Socket (your smartphone is used as a relay, with Tap Manager app)
    • 'UART' is reserved for (mass) deployment
  • Refer to the detailed procedure to set up a relay (for both MQTT and socket modes)

Configure your Tap

  1. Make sure IoTize Studio is relayed to your Tap.
  2. Click on the Configure button to send the configuration settings from IoTize Studio to your Tap (or use the menu Configuration > Write to Tap).
  3. Check in the output window that the publishing process is OK.

This covers only a subset of the settings managed by IoTize Studio (stored in <projectname>.izsc file). The writing of the configuration is done by a script mechanism (with a series of commands and answers) and but this is transparent for the developer.

Configuration version management

The version number applies to all configuration subsets: the Tap configuration, the cloud file configuration and the HTML. This allows to check that the HTML file and the Tap configuration are the same versions.

The config version number structure is XX.YY.ZZ

  • The XX and YY part of the version must be managed manually
  • If you set Auto-increment to Yes, the ZZ part is incremented whenever you save the project
  • When you configure, the project is automatically saved (and the ZZ part of the configuration number is updated if the Auto-increment option is Yes)
  • You must take care of the consistency between
    • your Tap configuration (related to the configure command)
    • the HTML pages and cloud versions (related to the publish command)

Test the Web App from IoTize Studio

From IoTize Studio:

  • Use menu Test > Monitor (or the Monitor button)
  • View the logs in the Output window
  • The HTML page for anonymous will be displayed first: check the consistency of values retrieved from the target application
  • Login using another profile to test other pages. If relevant, modify variables from the pages
  • Stop monitoring by clicking Disconnect. At this stage, the Web App is only located on your PC

Configure deployment settings and deploy your Web App

This step consists of 3 operations:

  1. Define Web App storage settings
  2. Define cloud configuration
  3. Publish Web App

See Getting Started for examples.

Define Web App storage settings


The Web App location is defined in Mobile App > Location, it is either:

  • Other Location: user defined URL
    • the entire Web App should be copied manually into a user defined location. The transfer can be done by ftp, MQTT ...
    • Mobile App > URI should contain the Pathname of the Web App (example for Sensor Demo).
    • note: the Web App (HTML pages) is retrieved by the smartphone using HTTP protocol so you must install an HTTP server
  • SD card storage: the files should be copied to the smartphone SDcard as '{SD-ROOT}/IoTize/relative_pathname' (Androids only).
  • Android internal storage: the files should be copied to the smartphone as '{ROOT}/IoTize/relative_pathname
  • Primers Development Server (on IoTize server) 
    • this is the simplest method, implemented for TapNLink Primer
    • pages are deployed automatically (using the Publish button)
    • deployment is done through MQTT, using an IoTize "cloud broker" (settings are listed hereafter)
    • TapNLink Primer also uses this broker for:
      • IoTize Studio, to send the cloud config file to the IOT platform
      • Tap Manager, to send the data packet (for data logging) to the IOT platform (or IoTize Primer Cloud platform for the Primer)

Define cloud configuration


For TapNLink Standard

  • You must replace IoTize cloud broker by your own broker
  • If you want to use IoTize cloud broker or if you need assistance on this subject, contact us.

Publish your Web App

  • If you use a TapNLink Primer and you kept the default cloud location for your Web App (IoTize Primer Development server =, you can use the Publish button, accessible from the top menu bar
  • Check in the output window that publication of the Web App and the cloud configuration were successful
  • If data logging is enabled, it will also transfer the cloud configuration file
  • For TapNLink Primer, the upload of a new configuration automatically deletes previous data and configuration (in IoTize Primer Cloud services)
  • If you chose to publish in Other location you must publish manually

Test your Web App from a smartphone

Tap your smartphone on your Tap or launch Tap Manager app manually and select your Tap (if your smartphone is not fitted with an NFC reader).

The Web App opens on the smartphone and displays the view that you created in IoTize Studio.

You can now control the target application from your smartphone.

Customize your Web App

You can customize your Web App by creating your own .css and .html pages and / or build a native application (refer to the Tap Manager).

Note that before (re)publishing your Web App, it is preferable to test it from IoTize Studio using your smartphone as a relay.

Settings for TapNPass

  • This last section summarizes the options dedicated to TapNpass
  • Refer to serial mode example and modbus example to view practical implementations and screen shots (in the document Getting Started/ TapNPass)
  • You can also load the 'SEPAM example' (accessible from the directory 'IoTizeStudio/Examples/Sepam10/sepam10.iotz'), which is a real industrial MobBus implementation.

Target Settings for TapNPass

  • These settings accessible from the Menu IoTized Application / Target on the top left pane (the detailed options are displayed in the pane underneath)
  • These settings determine the way TapNPass communicates with the target system
  • Type of Target: set this option 'System (TapNPass)' for TapNPass.
  • Target protocol: 'Serial Standard' or 'Modbus'.

    • 'Modbus': TapNPass and the target communicate using Modbus communication protocol. In this mode, TapNPass is Modbus Master and the target is Modbus Slave.

      • TapNPass can access to 'modbus registers'
      • these registers can be attached to Bundles, in a similar way as Variables in case of TapNLink
      • the access can be restricted (read and/or write) for each combination profile / bundle,
      • you can use the Access Control mechanisms to restrict the access to the target's registers.
      • IoTize Studio built-in Web app generator can automatically generate HTML pages, providing access to these Modbus registers
      • data logging apply to "modbus registers' attached to a bundle (in a similar way as variables for TapNLink)
      • the APIs handling "variables" also apply to 'Modbus registers'
    • 'Serial Standard':

      • TapNPass becomes a simple means of data transmission between the target system and the mobile application.
      • protocol layers must be handled at the application level.
    • The options Identification with LEDs and Enable LEDs can be ignored in the last version of IoTize Studio.

Additional settings for serial mode

  • Serial port:

    • TapNPass features 3 hardware ports: RS-232, RS-485 and USB.
    • Only one can be enabled and the corresponding configuration ('RS-232', 'RS-485' and 'USB') specifies the default value of the serial port.
    • 'AUTO' means USB if a USB device is connected, RS-232 otherwise.
  • Baudrate: communication speed in bps. You can select Custom to specify your desired value greater than 300bps and less than 300kbps.

  • Parity: check bit for error detection.

  • Length: the number of data bits.

  • Stop bits: end of frame bits.

  • Handshake: synchronization handshaking.

You can modify these options dynamically:

  • from your mobile app, using the relevant APIs
  • from the IoTize Terminal app
    • Your TapNPass is by default pre-configured with IoTize Terminal app (the NFC tag contains its AAR)
    • This simple app transmits character strings to your target system and displays the answer
    • It can alsobe used to test communication
  • Installation of IoTize Terminal on your mobile device:
    • If your mobile device is NFC-enabled, tap it on your TapNPass to automatically retrieve the app
    • Otherwise, install IoTize Terminal from Google Play Store

Modbus Additional Settings

When the Target protocol is set to Modbus, TapNPass and the target system communicate in Modbus.

  • Slave Address: If the Modbus communication is between one Master (TapNPass) and one Slave(Target system), you can provide here the Slave unit address to be used as the default address for commands.

  • Timeout: Response timeout (unit = 1/10 s).