Skip to content

Commit a5e02a5

Browse files
authored
Fixed typo and broken links (#38)
* Fixed typos and broken links The link to hardware.md was broken in majority of the files that I have read, I fixed it in addition to correcting some typos. * Update README.md * Update README.md * fixed typos and broken links * Completed chapter one review * Update README.md * Update app.py * Update virtual-device.md * worked on the request * fixed up the apps * Update README.md
1 parent cac3ccf commit a5e02a5

File tree

6 files changed

+14
-10
lines changed

6 files changed

+14
-10
lines changed

1-getting-started/lessons/1-introduction-to-iot/virtual-device.md

+1
Original file line numberDiff line numberDiff line change
@@ -119,6 +119,7 @@ Create a Python application to print `"Hello World"` to the console.
119119
```sh
120120
code .
121121
```
122+
> 💁 If your terminal returns `command not found` on macOS it means VS Code has not been added to PATH, you can [add VS Code to PATH](https://code.visualstudio.com/docs/setup/mac#_launching-from-the-command-line) and run the command afterwards. VS Code is installed to PATH by default on Windows and Linux.
122123
123124
1. When VS Code launches, it will activate the Python virtual environment. You will see this in the bottom status bar:
124125

1-getting-started/lessons/3-sensors-and-actuators/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ Actuators are the opposite of sensors - they convert an electrical signal from y
112112
Some common actuators include:
113113

114114
* LED - these emit light when turned on
115-
* Speaker - these emil sound based on the signal sent to them, from a basic buzzer to an audio speaker that can play music
115+
* Speaker - these emit sound based on the signal sent to them, from a basic buzzer to an audio speaker that can play music
116116
* Stepper motor - these convert a signal into a defined amount of rotation, such as turning a dial 90°
117117
* Relay - these are switches that can be turned on or off by an electrical signal. They allow a small voltage from an IoT device to turn on larger voltages.
118118
* Screens - these are more complex actuators and show information on a multi-segment display. Screens vary from simple LED displays to high-resolution video monitors.

1-getting-started/lessons/3-sensors-and-actuators/wio-terminal-actuator.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Connect the LED.
3434

3535
One of the legs of the LED is the positive pin, the other is the negative pin. The LED is not perfectly round, and is slightly flatter on one side. The side that is slightly flatter is the negative pin. When you connect the LED to the module, make sure the pin by the rounded side is connected to the socket marked **+** on the outside of the module, and the flatter side is connected to the socket closer to the middle of the module.
3636

37-
1. The LED module has a spin button that allows you to control the brightness. Turn this all the way up to start with byt rotating it anti-clockwise as far as it will go using a small Phillips head screwdriver.
37+
1. The LED module has a spin button that allows you to control the brightness. Turn this all the way up to start with by rotating it anti-clockwise as far as it will go using a small Phillips head screwdriver.
3838

3939
1. Insert one end of a Grove cable into the socket on the LED module. It will only go in one way round.
4040

1-getting-started/lessons/4-connect-internet/README.md

+9-7
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ Messages can be sent with a quality of service (QoS), which determines the guara
8686

8787
✅ What situations might require an assured delivery message over a fire and forget message?
8888

89-
Although the name is Message Queueing, it doesn't actually support message queues. This means that if a client is disconnected, then reconnects it won't receive messages sent during the disconnect except for those messages that it had already started to process using the QoS process. Messages can have a retained flag set on them. If this is set, the MQTT broker will store the last message sent on a topic with this flag, and send this to any clients who later subscribe to the topic. This way the clients will always get the latest message.
89+
Although the name is Message Queueing, it doesn't actually support message queues. This means that if a client disconnects, then reconnects it won't receive messages sent during the disconnection except for those messages that it had already started to process using the QoS process. Messages can have a retained flag set on them. If this is set, the MQTT broker will store the last message sent on a topic with this flag, and send this to any clients who later subscribe to the topic. This way the clients will always get the latest message.
9090

9191
MQTT also supports a keep alive function that checks to see if the connection is still alive during long gaps between messages.
9292

@@ -102,19 +102,19 @@ The word telemetry is derived from Greek roots meaning to measure remotely. Tele
102102

103103
> 💁 One of the earliest telemetry devices was invented in France in 1874 and sent real-time weather and snow depths from Mont Blanc to Paris. It used physical wires as wireless technologies were not available at the time.
104104
105-
Lets look back at the example of the smart thermostat from Lesson 1.
105+
Let's look back at the example of the smart thermostat from Lesson 1.
106106

107107
![An Internet connected thermostat using multiple room sensors](../../../images/telemetry.png)
108108

109109
***An Internet connected thermostat using multiple room sensors. Temperature by Vectors Market / Microcontroller by Template / dial by Jamie Dickinson / heater by Pascal Heß / mobile phone and Calendar by Alice-vector / Cloud by Debi Alpa Nugraha / smart sensor by Andrei Yushchenko / weather by Adrien Coquet - all from the [Noun Project](https://thenounproject.com)***
110110

111-
The thermostat has temperature sensors to gather telemetry. It would most likely have one temperature sensor built in, and it might connect to multiple external temperature sensors over a wireless protocol such as BLE.
111+
The thermostat has temperature sensors to gather telemetry. It would most likely have one temperature sensor built in, and it might connect to multiple external temperature sensors over a wireless protocol such as [Bluetooth Low Energy](https://wikipedia.org/wiki/Bluetooth_Low_Energy) (BLE).
112112

113113
An example of the telemetry data it would send could be:
114114

115115
| Name | Value | Description |
116116
| ---- | ----- | ----------- |
117-
| `thermostat_temperature` | 18°C | The temperature measured by the thermostat's built in temperature sensor |
117+
| `thermostat_temperature` | 18°C | The temperature measured by the thermostat's built-in temperature sensor |
118118
| `livingroom_temperature` | 19°C | The temperature measured by a remote temperature sensor that has been named `livingroom` to identify the room it is in |
119119
| `bedroom_temperature` | 21°C | The temperature measured by a remote temperature sensor that has been named `bedroom` to identify the room it is in |
120120

@@ -139,7 +139,7 @@ Follow the relevant step below to send telemetry from your device to the MQTT br
139139

140140
### Receive telemetry from the MQTT broker
141141

142-
There's no point in sending telemetry if there's nothing on the other end to listen for it. The light level telemetry needs something listening to it to process the data. This 'server' code is the kind of code you wold deploy to a cloud service as part of a larger IoT application, but here you are going to run this code locally on your computer (on on you Pi if you are coding directly on there). The server code consists of a Python app that listens to telemetry messages over MQTT with light levels. Later in this less you will make it reply with a command message with instructions to turn the LED on or off.
142+
There's no point in sending telemetry if there's nothing on the other end to listen for it. The light level telemetry needs something listening to it to process the data. This 'server' code is the kind of code you will deploy to a cloud service as part of a larger IoT application, but here you are going to run this code locally on your computer (or on your Pi if you are coding directly on there). The server code consists of a Python app that listens to telemetry messages over MQTT with light levels. Later in this lesson you will make it reply with a command message with instructions to turn the LED on or off.
143143

144144
✅ Do some research: What happens to MQTT messages if there is no listener?
145145

@@ -318,6 +318,8 @@ Write the server code.
318318
Message received: {'light': 0}
319319
Message received: {'light': 400}
320320
```
321+
322+
The app.py file in the nightlight virtual environment has to be running for the app.py file in the nightlight-server virtual environment to recieve the messages being sent.
321323
322324
> 💁 You can find this code in the [code-server/server](code-server/server) folder.
323325
@@ -357,7 +359,7 @@ A thermostat could receive a command from the cloud to turn the heating on. Base
357359
358360
### Send commands to the MQTT broker
359361
360-
The next step for our Internet controlled nightlight is for the server code to send a command back to the IoT device to control the light based off the light levels it senses.
362+
The next step for our Internet controlled nightlight is for the server code to send a command back to the IoT device to control the light based on the light levels it senses.
361363
362364
1. Open the server code in VS Code
363365
@@ -396,7 +398,7 @@ The next step for our Internet controlled nightlight is for the server code to s
396398
397399
### Handle commands on the IoT device
398400
399-
Now that commands are being sent from the server, you cna now add code to the IoT device to handle them and control the LED.
401+
Now that commands are being sent from the server, you can now add code to the IoT device to handle them and control the LED.
400402
401403
Follow the relevant step below to listen to commands from the MQTT broker:
402404

1-getting-started/lessons/4-connect-internet/code-commands/virtual-device/nightlight/app.py

+1
Original file line numberDiff line numberDiff line change
@@ -38,3 +38,4 @@ def handle_command(client, userdata, message):
3838
print('Light level:', light)
3939

4040
mqtt_client.publish(client_telemetry_topic, json.dumps({'light' : light}))
41+
time.sleep(5)

1-getting-started/lessons/4-connect-internet/single-board-computer-mqtt.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,6 @@ Write the device code.
7474
Light level: 0
7575
```
7676

77-
> 💁 You can find this code in the [code-mqtt/virtual-device](code/virtual-device) folder or the [code-mqtt/pi](code/pi) folder.
77+
> 💁 You can find this code in the [code-mqtt/virtual-device](code-mqtt/virtual-device) folder or the [code-mqtt/pi](code-mqtt/pi) folder.
7878

7979
😀 You have successfully connected your device to an MQTT broker.

0 commit comments

Comments
 (0)