miro
Edge Sphere
miro Edge Sphere
2. Sphere SDK
Download and install the Sphere SDK. For configuring the gateway (see next point), only the SDK is needed, the other development tools are NOT needed (CMake, Ninja, VS code, etc.).
3. Configuration
To configure the gateway (region, frequencies, LoRaWAN network server (LNS) URL, etc.), download the "Sphere Image Package" from here.
Follow the instructions in the README file to create an image package with the desired configuration.
The image package can be deployed remotely via the Sphere CLI (see Azure Sphere documentation). Alternatively, qiio provides a web-based graphical interface to deploy the image package and manage your gateway fleet (qiio Sphere Studio®).
The gateway does not need to be connected to your computer, it can be claimed and deployed remotely.
4. Registration
The default image is configured to connect to eu1.loriot.io. To register the gateway, follow these steps:
-
On the Loriot dashboard, navigate to “Networks→your_application”
-
Click “Add gateway”
-
Select “Packet Forwarder STM” as gateway type (NOT miro Edge)
-
Under “eth0 MAC address” enter the EUI from the back of the gateway without FFFF
-
Click “Register Packet Forwarder STM gateway”
The Semtech packet forwarder can also be configured to use other LNS (see configuration above).
5. Installation
-
For optimal performance, install the gateway far away from metal objects or concrete
-
Attach both labeled antennas (LTE and 868 MHz LoRa®)
-
Use the provided USB power supply and cable
-
Wait until the WWAN and LoRa® LEDs are on
To power the gateway via USB, the USB cable must be connected to a USB port with a minimum of 1.5A. A standard USB port on a laptop or PC is not enough. |
6. Azure Sphere documentation
For information about tenants, devices, device groups, deployments, see Azure Sphere documentation
7. FAQ
-
Q: I connected the gateway to my computer via USB, but the gateway does not show up in the Azure Sphere CLI. I cannot claim the device. What can I do?
A: Runazsphere device rescan-attached
first. It should now show up when runningazsphere device list-attached
and can be claimed. (make sure the USB hub port supports a minimum current of 1.5A). NOTE: The gateway does not need to be connected to your computer to be claimed and deployed. It can be claimed and deployed remotely via the Azure Sphere CLI or qiio Sphere Studio®. -
Q: What is Sphere used for in the gateway?
A: Microsoft Azure Sphere provides automatic security updates on all gateways. It also allows to securely configure the gateway and to deploy new packet forwarder versions. Only crytographically signed software for your tenant can be deployed to gateways claimed to your tenant. This prevents unauthorized software from being deployed to your gateways (botnets, etc.). -
Q: How does the deploying images / fleet management work via Sphere?
A: See the Azure Sphere documentation for management via the command line and Sphere SDK. Alternatively, contact qiio for a web-based interface to deploy the image package and manage your gateway fleet. -
Q: How do I access the configuration web GUI of the gateway?
A: For security reasons, the gateways does not have a web GUI. All settings are part of the Azure Sphere application image package that is deployed securely via Azure Sphere (see "Configuration" above). -
Q: What is the EUI?
A: When registering your gateway with your LoRaWAN network server (e.g. Loriot), use the EUI from the back of the gateway. You might need to replace the middle part depending on the LNS (e.g. FFFF or FFFE). NOTE: It is different from the ethernet MAC address of the gateway. -
Q: I want to use a different LoRaWAN network server (LNS). What should I do?
A: To use a different LNS, an image package configured for that LNS must be created and deployed via your Sphere tenant to the gateways. See "Configuration" above. -
Q: Can I use Azure IoT Hub?
A: Using Azure IoT Hub is entirely optional. The gateway directly connects to your configured LoRaWAN network server (LNS). Most LNS have an integration for IoT Hub and can forward the data.