You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<spanclass="images"><span>Gateway details: The Things Network uses the gateway location to create coverage maps, so make sure the location is set correctly.</span></span>
131
-
132
-
1. If you use the Kerlink Wirnet station:
133
-
- Tick **I'm using the legacy packet forwarder**.
134
-
- Under **Gateway EUI**, enter the EUI of the gateway (printed on the box).
135
-
136
-
1. If you use the Raspberry Pi:
137
-
- Tick **I'm using the legacy packet forwarder**.
138
-
- Under **Gateway EUI**, enter the EUI that printed when you called `install.sh` in step 2.1.
139
-
140
-
1. Click **Register gateway**.
126
+
1. Click **Create gateway**.
141
127
1. You have created the gateway.
142
128
143
-
If you use the MultiTech conduit, you need the 'Gateway key' to authenticate the gateway to the network. Copy it.
129
+
If you use the MultiTech conduit, you need the 'Gateway key' to authenticate the gateway to the network. Click on **API Keys** and **Add API Key**
1. If your device has an EUI printed on it, enter this in **Device EUI**.
226
209
227
210
<span class="images"><span>The device EUI is often printed on the module or on the box.</span></span>
228
211
229
-
1. If your device does not have an EUI printed on it, press the **generate** button to allocate an EUI from a block owned by The Things Network. Do **not** make an EUI up; it must be globally unique.
1. Fill in the rest of the details, and click **Register end device**.
237
213
1. The device page opens. It contains the keys that your device uses when authenticating with the network. Click the `<>` button to get the keys as a byte array. This makes it easy to copy the keys into code.
@@ -305,7 +281,7 @@ Now you can verify whether the setup works by flashing this application to your
305
281
306
282
1. When compilation succeeds, the compiler sends a file to your computer.
307
283
1. Plug your development board into the computer (over micro-USB) to mount it as a USB mass storage device.
308
-
1. Once the device mounts, drag the compiled file onto the board. This causes the device to boot. You can then see the device joining and then sending messages in the The Things Network console, under the **Data** tab:
284
+
1. Once the device mounts, drag the compiled file onto the board. This causes the device to boot. You can then see the device joining and then sending messages in the The Things Network console, under the **Live data** tab:
@@ -356,7 +332,7 @@ You can toggle the LED on your development board over LoRa. In the Online Compil
356
332
<span class="notes">**Note:** On some development boards, writing `0` to the LED turns them on. On others, writing `1` does this. It depends on the wiring of the board.</span>
357
333
358
334
1. Compile, and flash the application.
359
-
1. When the device is back online, use the The Things Network console to queue a message. Go to your device page, and under **Downlink**, select port **21** and data `01`. Then press **Send**.
335
+
1. When the device is back online, use the The Things Network console to queue a message. Go to your device page, and under **Messaging**, select **Downlink** and add port **21** and data `01`. Then press **Schedule downlink**.
360
336
361
337
<spanclass="images"><span>Queuing a downlink message over port 21</span></span>
362
338
@@ -377,7 +353,7 @@ To build this application, first grab an access key from The Things Network:
0 commit comments