Leading Analog & Mixed Signal Products

Notice:
Dear user,
Semtech will be phasing out support for new registrations and development on the existing LoRaWAN network server and associated websites hosted by Semtech (including http://iot.semtech.com/ ; http://us01-iot.semtech.com/). A transition plan to an alternate server to support prototype evaluation is being drafted and will be communicated in the next few weeks. Until then, existing users may continue to use the services offered here as they have been previously. Semtech remains committed to our vision of enabling LPWAN applications with LoRa technology and providing open and easily accessible means to develop products. Please contact your local Semtech representative if you have additional questions on the network server.
Regards,
Your Semtech Team

Site Help

This website provides a globally accessible hub for your LoRa trials. Once your LoRa packet forwarder is pointing here you will be able to do the following things (depending on the type of LoRaMote you’re using):

  • Commission motes;
  • Control their basic functions;
  • Track their location;
  • Create new applications to group your motes;
  • Plot & download performance statistics and application data

To get started you must have an official LoRa starter kit or other LoRa-enabled equipment with a packet forwarder capable of pointing to this site.

More Help

If you have any trouble using this website or your LoRa hardware, please get in touch with your Semtech contact or visit the LoRa Community. For technical problems with the website please send an e-mail to iot.web@semtech.com.

Topics

  1. Getting Your Motes on the Site
  2. Motes
  3. Gateways
  4. Network Map
  5. Applications
  6. Limitations

Getting Your Motes on the Site

Once you have an account on the site you will need to direct your packet forwarders (gateways) to here. The method to do this varies with gateway, but the common details are as follows:

Host:
us01-iot.semtech.com
Port:
1780

For the basic packet forwarder included with the LoRa starter kit, you will need to modify the file local_conf.json (or global_conf.json if that doesn’t exist) to include the following lines:

"server_address": "us01-iot.semtech.com",
"serv_port_up": 1780,
"serv_port_down": 1780

Be sure to restart your packet forwarder for any changes to take effect.

Every mote must be registered on the site before it will appear on the network. Registering a mote can be done from the main motes page; the details you need to supply depend on whether the device is configured for personalised or over-the-air activation. In either case you can add the mote to the default application 00-00-00-00-00-00-00-00 (‘defaultApp’) or to a private application which you can create as part of the mote registration. Go to the main motes page and enter the details under the heading ‘Add a Mote’.

Once a mote has been registered with the site you will have 24 hours to power on the mote and have it picked up by the network. If it has not been detected within this time then the registration will be cancelled and you will have to enter the mote details a second time. A table of pending motes and their remaining time before cancellation can be seen under the heading ‘Pending Motes’ above the main list of active motes. Once a mote has been detected it will remain registered with the network until you remove it.

Note: All motes on the default application will be visible to everyone and can be controlled by anyone who is logged in.

Personalised Motes

Your mote has a default application session key, network session key and device address (four bytes). If your mote is a demonstration LoRaMote supplied by Semtech and the session keys are unchanged then adding the mote is as simple as entering the device’s address and selecting which application you’d like it to appear on. Go to the main motes page and at the top under the heading ‘Add a Mote’ type in the mote’s 4-byte address and select the application from the drop-down on the right. Click Add. It will then be listed with the programmed device address and an EUI (eight bytes) equal to the device addresses padded with zeros.

If you have changed the mote’s session keys or the mote is not a demonstration LoRaMote then then you will need to expand the heading ‘More mote options’ and fill in the fields Application session key and Network session key in addition to Address.

Over-the-Air Motes

Motes can join the network via over-the-air protocol. In this case your mote is programmed with a device EUI (eight bytes) and an application key, and also the EUI of its application. Go to the main motes page and at the top under the heading ‘Add a Mote’ expand the heading ‘More mote options’. Select Activation: Over-the-air and fill in the fields EUI and Application key. Select the mote’s application from the drop-down on the right. If the application’s EUI cannot be seen in the list then you will have to add it: select New from the drop-down and fill in the fields that appear below it.

When you activate your mote and have it picked up by your gateway, the mote will be registered with the website on the application you specified, and will have a device address (four bytes) dynamically assigned to it.

Motes

The main motes page lists the motes which are active on the network and those which have been active in the past. Here it is possible to view the last gateway on which each mote was detected, and what the most recent frame was, including its raw data as a hexadecimal string. The table can be sorted by many of its columns, so you can view by date or by mote EUI for example.

Clicking on a mote’s EUI will bring up the mote summary page. Depending on the type of mote, several statistics and parameters will be visible. LoRaMotes shipped with the LoRa starter kit and configured for GPS demo mode will report back their location and environment, and this can be seen on the details page. There is also a graph of these factors over the last 24 hours.

If you have added some motes to the site and they are not appearing in the list, first make sure you are logged in; if you have added your motes to a private application then you will only be able to see them if you are logged in. If they still will not appear after you have logged in, check your gateway’s logs to make sure it is forwarding frames from the motes, and ensure the gateway can communicate with the us01-iot.semtech.com server on port 1780.

Obtaining Mote Data

The data received from the mote can be viewed on the website. To access it go to the mote’s details page and look for the application name in the summary box. Clicking the table icon (Table icon) will take you to the data received from the mote on its current application. You can expand the drop-down ‘Previous applications’ to see the mote’s previous applications and view their data instead. Alternatively, if you own the mote, you can click the link ‘View all mote data’ to view everything the mote has transmitted.

If you own the mote you can download the data in CSV format by expanding the Download Data heading by clicking on it, then entering either a date range over which to download data or the number of most recent records you want. You can optionally enter the EUI of a gateway by which you wish to filter. Click Download to receive the file.

The downloaded data will be ordered by descending time starting with the most recent frame.

Gateways

The gateways page lists the gateways that have forwarded frames from motes on the network. Gateways that are live but have not received anything from any motes are not listed. You can view details of a gateway (including its location and a table of recent activity) by clicking on its EUI.

Private Gateways

By default a gateway that forwards traffic to us01-iot.semtech.com is publicly listed, and any publicly visible data (i.e. data on application 00-00-00-00-00-00-00-00) that is forwarded by it is shown to visitors as having come from that gateway. A gateway can be declared private, however, whereupon its details will be hidden from the user along with any performance data pertaining to frames forwarded by it. The payloads forwarded by private gateways will still be visible.

To declare a gateway private go to the Gateways page and under the heading Private Gateways enter the EUI of the gateway you’d like to hide from the public. A gateway can only be made private if it has not forwarded frames from motes that do not belong to you.

Network Map

The network map shows the location of gateways and motes worldwide. On the left of the page are two tabs: Motes and Gateways. Each tab displays a list of the items in question, and the Gateway tab also includes a form to retrieve the historical data of one or all motes in a given time window and plot this on the map.

Only LoRaMotes configured for GPS demo mode and returning valid GPS data are displayed on the map. All gateways will appear on the map, but they may not have known GPS co-ordinates. If a gateway is yours and you know its location, you may enter the latitude and longitude for it in its box on the left. These settings are not persistent and will reset after you close your browser.

Applications

Private applications can be created and configured by registered users. When you’re logged in you will see a link in the Demonstration area to the applications list. Once there, you will see a list of your existing applications and the number of motes that have been configured on them. Click on an application’s name to go to its summary page, where you can see a table of recent mote activity and a link to all data received from the motes. Click on the number in the Configured Motes column to go to the mote configuration page where you can prepare the network to accept frames from motes.

Creating Applications

Creating a private application can be done at the same time as adding a mote (see ‘Getting Your Motes on the Site’, above) or as a separate task from the main applications page. Simply enter a name and owner for the application along with an EUI. This EUI must be globally unique; upon pressing the Add button and submitting the form, you will be informed if the EUI has already been used. The owner column can be used to supply a label to help you group associated applications. Neither the application name nor owner can contain any spaces.

Obtaining Application Data

The data received from the motes on a private application can be viewed on the website. To access it go to the application’s details page and click ‘View data from all motes’. Alternatively, you can view the data received from individual motes by clicking the table icon (Table icon) next to their EUI.

You can download the data in CSV format by expanding the Download Data heading by clicking on it, then entering either a date range over which to download data or the number of most recent records you want. You can optionally enter the EUI of a gateway by which you wish to filter. Click Download to receive the file.

The downloaded data will be ordered by descending time starting with the most recent frame.

Public applications cannot have their entire data viewed; you may only view the data from individual motes. Furthermore you may only download the data from motes you own.

Limitations

We are always striving to keep this test platform up-to-date with the latest features and behaviours documented in the LoRaWAN Specification. Nevertheless you should be aware that the website and attached LoRa network are subject to several limitations.

Specification Version

This test platform conforms to version 1.01 of the LoRaWAN Specification.

Region Support

us01-iot.semtech.com supports the following regions only:

  • US 902-928MHz
  • EU 863-870MHz

While this test platform does support the European region above, the servers are located in the United States and therefore might not be appropriate for trials conducted in Europe expecting downlink communication due to the increased response time. The sister website iot.semtech.com is provided for European trials.

Mote Classes

Class A:
Supported.
Class B:
Partially supported and subject to change. Class B is experimental in the LoRaWAN Specification.
Class C:
Supported (not tested).

Inline Logs