Skip to content

Getting Started

At IoTize we have three main hardware product lines, connectivity Modules (TapNLink) and ready to use products (Tapioca and TapNPass). This getting started page is focus on the TapNLink Primer, our evaluation board. If you have a Tapioca or a TapNPass please see below.

The TapNLink modules can be used for several purposes:

  1. as an inferface between a mobile application and a device (target) that you want to modify/monitor.

  2. as an inferface between a remote application (on the 'Cloud') and this target device.

  3. as a processor board that manages sensors/actuators.

At a first step, we will focus on the first functionality (interface between a mobile App and a mobile application).

We recommend that you start by looking at our demonstration which uses the Primer kit's Target board instead of your own device:

  1. Open the Demonstration interface. This page will show you how to connect your tap and how to use it.
  2. If you have an Apple device checkout how its behaviour differs from Androids when using IoTize products.
  3. Then follow the discovery path for your Tap, described in dedicated sections below.

Once the software required by the discovery path is installed/setup, app creation takes literally 2 minutes !

The manuals, "How to" guides and demo videos will be useful later to customize your app. In particular this video explains how to modify/monitor your own device.

NBW

NB

NFC

  • NFC (TnL-FIT20x)

There is no specific 'Primer Kit' including the TnL-FIT20x module. The NFC only TapNLink discovery path is the same as that of the NFC/WiFi or the NFC/BLE TapNLink (above), with these specific features.

Note: The TapNLink API is unique, whatever the wireless incoming protocol selected. Therefore, a mobile App developed for a specific module should work with another module (with the limitation of the wireless protocols availability).

TapNPass

The TapNPass wireless adapters embed a TapNLink module. Therefore, the 'Getting Started' guides are generally relevant except the imported variables are issued from ELF files for a standard TapNLink and generally from a CSV file (when Modbus is used) for TapNPass:

  1. Flyer & Quick start TnP-NSR103 (Nomad) or Quick start TnP-FSR103 (Fixed) for an optional overview.
  2. Get Started: Run Toolbox App using Serial or Modbus, and modify the configuration

Tapioca-xxx

There are several Tapioca models that depend on the type of the target (wire) connection. When TapNPass supports "USB (host mode) and RS485 and RS232", Tapioca supports only one of these wire connections (and only 'device mode' for USB). Typically, there is one model Tapioca-232 and another Tapioca-485. The first contains an unique RS232 driver, and the second an unique RS485 driver.
Therefore, for the user's point of view, TapNPass and Tapioca-xxx are quite similar. However, if we look at the structure, Tapioca is closer to TapNLink because it does not embed any other microcontroller, but the TapNLink module with a simple serial transceiver. Firmware for TapNLink and Tapioca are common and 100% compatible whilst the TapNPass requires two firmware packages: one for the embedded TapNLink module and one for the wire-communication board.

When you create a new project in Studio, you can specify the product you will use. For Tapioca, you will have to select the exact reference of your model. In general, the impact on the configuration is not so important (except for the ethernet version).

Due to its similarities to both the TapNLink and TapNPass, the 'Getting Started' guides are also generally relevant for the Tapioca.

However, here is a specific guide on how to use the Tapioca's capability to act as a Modbus slave device:

  1. Get Started: Configure the Tapioca as a Modbus Slave device

Going further

After playing with the demo project, you should be interested by designing your own application. We recommend to read first the following sections:

Title Description
Target protocols To decide how to connect your electronic (the 'target') to a TapNLink module.
Different protocols and different topologies are available.
RF Incoming protocols To decide which module to use in your specific case.
Java in case you don't have a MCU on your board, or if you wish to send alarms/data to the Cloud.
IoTize Studio to make your own configuration from scratch.
App generator To generate your branded mobile Apps.