Actility’s ThingPark Community Portal (TPCP) provides access to its ThingPark Enterprise (TPE) platform, which allows developers to experience the ThingPark platform which is already used by many networks around the world, from large nationwide public networks to small private networks. Anyone can connect up-to three gateways and 50 devices to TPCP free of charge for non-commercial use.
The platform is always kept up-to-date with the latest ThingPark release, as soon as automated QA testing has been completed from R&D. It is used as a first field-test platform as part of the release cycle. Therefore, it may be stopped or upgraded at any time, with a prior notification of 48 hours. There is no service level agreement for this platform.
To create an account on the TPCP, please visit community.thingpark.org and click the Sign Up button. The account you create can be used for accessing both the portal and the platform, which is accessible at community.thingpark.io/tpe.
Execute the following steps so that your gateway can access the internet to reach the TPCP.
- Plug in your gateway to a power source.
- Connect your gateway to an Ethernet network where it can get an automatic IP address from a DHCP server and access the Internet. If your gateway is behind a corporate firewall, make sure the firewall does not block the following ports towards the Internet:
- FTP (TCP port 21)
- NTP (UDP port 123)
- IPsec (UDP ports 4500 and 500)
All gateway connections are in the gateway-to-Cloud direction and support NAT traversal, and therefore no port forwarding is required.
- Go to TPCP UI
- In the main menu (on the left), under Base Stations, select Create
- Select the gateway vendor (e.g., “UfiSpace”)
- Complete the form:
Figure 22: Creating a Gateway: Form #1
- Select the Model (e.g., “Pico/Enterprise V1.5”).
Figure 23: Pico Gateway
Figure 24: Enterprise Gateway
- Use the Name field to assign a name to your gateway.
- Enter your gateway’s universally-unique ID in the LRR UUID field. Your gateway’s LRR UUID (e.g. 001558-46584254C0001BF9) will have been emailed to you. You have received the LRR UUID prior to continuing.
- Select your RF Region. Also select the number of channels your gateway supports (e.g., “EU 863-870MHz (8 channels)”).
- Select the Enabled option for IPsec (X.509) for base station to TPE connection.
- Feel free to add any notes to the Additional Information field that you may want to associate with your gateway.
- Enter your gateway’s Public key (see example below). You must have received the public key of your gateway in an email. Copy the public key from your email (with or without the BEGIN/END lines) and paste into the Public key field on the TPCP UI.
Public Key Example:
—–BEGIN PUBLIC KEY—–
9JDPF1v0EnQ6Xluiz6Mc3hlsWzM303HQA3dAgRfSWDy7kHcAS8631uQIDAQAB—–END PUBLIC KEY—–
- For setting the gateway location, select Manual and enter the coordinates using latitude (Lat) and longitude (Long) or by clicking on the map.
- Click Save
Wait for approximately five minutes for your gateway to complete the Initialization procedure and become “Active”.
Note: If the gateway status shows Radio Error before becoming “Active”, ignore the error.
Figure 25: Gateway Status
Now your gateway is ready to send the uplink frames it demodulates to your TPCP account and to accept the downlink frames sent from any application server or cloud via TPCP to be transmitted over the air. You can see it listed when you click on List under Base Stations in the main menu.
- At the main menu, under Applications, select Create
- Select Generic Application
- Complete the form:
Figure 26: Creating a Gateway: Form #2
- Use the Name field to assign a name to your application
- Set the URL field to:
Note: The actual value of the TEMP-AUTHORIZATION will be assigned by Tago.IO once the application is created on that end. Use this temporary value for now, and we will guide you to come back and replace it with the actual value later.
- For Content Type, select JSON
- Copy the randomly-generated Tunnel Interface Authentication Key to use with your TagoIO account in the subsequent steps.
- Feel free to add any notes to the Additional Information field that you may want to associate with your application
- Click Save
Figure 27: Application Status
The TagoIO application is now ready to send and receive application payloads via the TPCP for the trackers you will be creating. You can see the application listed when you click List under Applications in the main menu.
Now create your tracker as a device based on the LoRaWAN protocol on your TPCP account.
- At the main menu, under Devices, select Create
- Select Generic as the device manufacturer
- Complete the form:
Figure 28: Create a Device - Form #1
- For the Model, select LoRaWAN 1.0.3 revA - Class A (LORA/GenericA.1.0.3a_XX)). The trailing letters (XX) should be “ETSI” for an EU868 device, “FCC” for a US915 device, or “AS923” for an AS923 device.
- Use the Name field to assign a name to your device.
- Set the DevEUI field to the 8-byte globally-unique value that will be used to identify your tracker. This value, provided to you along with the tracker, is represented in hexadecimal format (i.e., 16 characters, such as A1B2C3D4E5F6A7B8).
- Select Over-the-Air Activation (OTAA) with external Join Server as the Activation mode, since the tracker is using the Semtech join server connected to TPCP via ThingPark Exchange.
- Set the JoinEUI (AppEUI) field to the 8-byte globally-unique value to be used to identify the join server associated with your tracker. This value is represented in hexadecimal format (i.e., 16 characters, such as F1E2D3C4B5A6F7E8) and was provided to you along with the tracker.
- Feel free to add any notes to the Additional Information field that you may want to associate with your tracker.
- Select the application you created above (under Create the TagoIO Application) and click the plus sign (+) to set the application for your tracker.
- For Mode, select No location, since this will not be using a ThingPark-based location service.
- Click Save.
Figure 29: Device Status
Now your tracker is ready to be used. You can see it listed when you click on the “List” under “Devices” in the main menu.
From a web browser, go to https://admin.tago.io and create your free account.
Figure 30: TagoIO Sign up
Once you have created your account and confirmed your email, you will be redirected to the TagoIO Admin page. From there you can see your account usage information. One important area to watch is the Usage Statistics section. This section shows you with how many services you are using in your applications.
Figure 31: TagoIO Usage Statistics
Among other things, the Usage Statistics show how much data your devices are sending by the hour (Data Input), and how much data you can have stored at TagoIO (Data Registers). You will receive notifications if you get close to or surpass the limits, so be aware of that if you happen to stop receiving your data at TagoIO.
Next, set up ThingPark Community Platform to redirect your sensor data to TagoIO, and to enable your TagoIO account to accept this data.
- Log in to your TagoIO account and select your Devices page on the sidebar.
- On the Devices page, click the Authorization button on the top right corner (https://admin.tago.io/devices/authorization).
- Enter a name for your Service Authorization, and click the blue Generate button.
Figure 32: Naming the Service Authorization
- Click the Copy button to copy your authorization token.
- Go to your ThingPark Community Platform account and find the application you had created earlier by going to Applications > List > your application’s name.
- Enter the editing mode on the URL field by clicking on the pencil icon next to it. Copy and paste the following link, replacing the authorization by the one generated at TagoIO, and click on confirm:
- Copy the Application ID from the application you just created.
- Go back to your Authorization page at TagoIO and edit your previously-created authorization by clicking the pencil icon. Then, paste the Tunnel Interface Authentication Key generated by Actility,.
If you forgot to get a copy of the Tunnel Interface Authentication Key at the time of ThingPark Community Platform setup, you can create a new one:
- Go back to your application page on the ThingPark Community Platform
- Click on the regenerate button next to the Tunnel Interface Authentication Key
- Copy the key
- Press confirm button to save the key
Once you have created your account and created a link between the Actility and TagoIO services, you will not need to repeat them again. Now, you need to create your device at TagoIO. If you have more than one device, repeat this step for each of them.
- Go to your Devices page at TagoIO (https://admin.tago.io/devices).
- Click Add Device.
- Select LoRaWAN Actility in the network sidebar.
- Search for the “LoRa Edge Tracker” or “Semtech” and click on the connector found.
- Complete the following fields accordingly:
- Name: Give a name for your device.
- Device EUI: Your device EUI.
- DAS Token: Copy your LoRa Cloud Device & Application Services token (https://www.loracloud.com/portal/device_management/tokens).
- Click Create Device.
- You will be prompted to install the dashboard template. Click on the link to open the installation page, and then click Install.
- Select your sensor for the dashboard.
After creating your device, a new dashboard will be available in the sidebar:
Figure 33: Location of the Sidebar on the TagoIO Dashboard View
Once the gateway and tracking devices are turned on and the device and tokens been added to the TagoIO port, you will be able to add the device to the Dashboard. First press the pen in the upper-right corner of the Dashboard to edit it, then the “Edit” form will be visible and shown below.
Figure 34: Devices and Gateway Reporting Example
This will bring up a window to add the device to the Dashboard. Select the new device and “location” and click Save.
Figure 35: Add Device to Dashboard View
The Dashboard for the LR1110 Tracker has four modes: 1) Main; 2) Data traffic history; 3) GNSS; and 4) Wi-Fi. The “Main” screen is the map and device information. The “Data traffic history” shows the latest traffic to and from the Device & Application Services showing status messages on the service. The “GNSS” page shows the latest GNSS solutions and statistics. The “Wi-Fi” page shows the latest Wi-Fi location history and its statistics.
Figure 36: Dashboard modes