Skip to content

Commit a2d672d

Browse files
committed
practice exercises
1 parent cc82193 commit a2d672d

File tree

1 file changed

+15
-2
lines changed

1 file changed

+15
-2
lines changed

docs/network-iot/learn/build-a-device.mdx

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -73,5 +73,18 @@ If uplinks are shown in the logger above, the device is successfully sending dat
7373
Network!
7474

7575
With the payloads received, the next step would be to send them to an application. LNSs typically
76-
support a number of integrations like HTTP, MQTT, or bespoke integrations with platforms like AWS
77-
IoT or Azure IoT.
76+
support several integrations like HTTP, MQTT, or bespoke integrations with platforms like AWS IoT or
77+
Azure IoT.
78+
79+
## Practice
80+
81+
Now that data is being sent to the Helium Network, experiment with the device.
82+
83+
1. Try changing the data being sent by the device. How would you send the payload, "Hello, World!"?
84+
The current payload is being sent in hexadecimal format. Tools like
85+
[asciitohex.com](https://www.asciitohex.com/) can help convert data types.
86+
1. LoRaWAN provides the 'port' field which helps separate data types. For instance, multiple sensors
87+
can run on the same device under different ports or status updates like battery level can be sent
88+
on a different port than sensor data.
89+
1. The device is currently sending data every 30 seconds. Try changing the interval to 10 seconds.
90+
How would this affect the battery life of the device?

0 commit comments

Comments
 (0)