Skip to content

Commit 224d00c

Browse files
AnnaMHuffAnnaMHuff
authored
Merge pull request #271834 from timlt/update-RTOS-refs
Bulk rebrand Azure RTOS to Eclipse ThreadX and update links
2 parents a41976b + e3c7bfc commit 224d00c

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

48 files changed

+79
-105
lines changed

‎articles/azure-maps/tutorial-iot-hub-maps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -275,7 +275,7 @@ To learn more about how to send device-to-cloud telemetry, and the other way aro
275275
[Get Search Address Reverse]: /rest/api/maps/search/getsearchaddressreverse?view=rest-maps-1.0&preserve-view=true
276276
[How to create data registry]: how-to-create-data-registries.md
277277
[IoT Hub message routing]: ../iot-hub/iot-hub-devguide-routing-query-syntax.md
278-
[IoT Plug and Play]: ../iot-develop/index.yml
278+
[IoT Plug and Play]: ../iot/overview-iot-plug-and-play.md
279279
[geofence JSON data file]: https://raw.githubusercontent.com/Azure-Samples/iothub-to-azure-maps-geofencing/master/src/Data/geofence.json?token=AKD25BYJYKDJBJ55PT62N4C5LRNN4
280280
[Plug and Play schema for geospatial data]: https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v1-preview/schemas/geospatial.md
281281
[Postman]: https://www.postman.com/

‎articles/index.yml

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -173,13 +173,6 @@ productDirectory:
173173
- ai-machine-learning
174174
url: open-datasets/index.yml
175175
# Card
176-
- title: Azure RTOS
177-
summary: Making embedded IoT development and connectivity easy
178-
imageSrc: ./media/index/rtos.svg
179-
azureCategories:
180-
- iot
181-
url: /azure/rtos/
182-
# Card
183176
- title: Azure Communication Services
184177
summary: Build rich communication experiences with the same secure platform used by Microsoft Teams
185178
imageSrc: ./media/index/communication-services.svg

‎articles/iot-central/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -272,8 +272,6 @@
272272
href: ../azure-maps/index.yml
273273
- name: Time Series Insights
274274
href: ../time-series-insights/index.yml
275-
- name: IoT device developer
276-
href: ../iot-develop/index.yml
277275
- name: Azure IoT SDKs
278276
items:
279277
- name: IoT Service SDKs

‎articles/iot-central/core/concepts-architecture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ IoT Central can also control devices by calling commands on the device. For exam
6262

6363
The telemetry, properties, and commands that a device implements are collectively known as the device capabilities. You define these capabilities in a model that the device and the IoT Central application share. In IoT Central, this model is part of the device template that defines a specific type of device. To learn more, see [Assign a device to a device template](concepts-device-templates.md#assign-a-device-to-a-device-template).
6464

65-
The [device implementation](tutorial-connect-device.md) should follow the [IoT Plug and Play conventions](../../iot/concepts-convention.md) to ensure that it can communicate with IoT Central. For more information, see the various language [SDKs and samples](../../iot-develop/about-iot-sdks.md).
65+
The [device implementation](tutorial-connect-device.md) should follow the [IoT Plug and Play conventions](../../iot/concepts-convention.md) to ensure that it can communicate with IoT Central. For more information, see the various language [SDKs and samples](../../iot/iot-sdks.md).
6666

6767
Devices connect to IoT Central using one the supported protocols: [MQTT, AMQP, or HTTP](../../iot-hub/iot-hub-devguide-protocols.md).
6868

‎articles/iot-central/core/howto-manage-data-export-with-rest-api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -294,7 +294,7 @@ The following example shows how to use the `filter` field to export only message
294294
"displayName": "Enriched Export",
295295
"enabled": true,
296296
"source": "telemetry",
297-
"filter": "SELECT * FROM dtmi:azurertos:devkit:gsgmxchip;1 WHERE accelerometerX > 0",
297+
"filter": "SELECT * FROM dtmi:eclipsethreadx:devkit:gsgmxchip;1 WHERE accelerometerX > 0",
298298
"destinations": [
299299
{
300300
"id": "dest-001"
@@ -312,7 +312,7 @@ The following example shows how to use the `filter` field to export only message
312312
"displayName": "Enriched Export",
313313
"enabled": true,
314314
"source": "telemetry",
315-
"filter": "SELECT * FROM dtmi:azurertos:devkit:gsgmxchip;1 AS A, dtmi:contoso:Thermostat;1 WHERE A.temperature > targetTemperature",
315+
"filter": "SELECT * FROM dtmi:eclipsethreadx:devkit:gsgmxchip;1 AS A, dtmi:contoso:Thermostat;1 WHERE A.temperature > targetTemperature",
316316
"destinations": [
317317
{
318318
"id": "dest-001"

‎articles/iot-central/core/howto-manage-jobs-with-rest-api.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -361,7 +361,7 @@ The following example shows a request body that creates a scheduled job.
361361
"data": [
362362
{
363363
"type": "cloudProperty",
364-
"target": "dtmi:azurertos:devkit:hlby5jgib2o",
364+
"target": "dtmi:eclipsethreadx:devkit:hlby5jgib2o",
365365
"path": "Company",
366366
"value": "Contoso"
367367
}
@@ -388,7 +388,7 @@ The response to this request looks like the following example:
388388
"data": [
389389
{
390390
"type": "cloudProperty",
391-
"target": "dtmi:azurertos:devkit:hlby5jgib2o",
391+
"target": "dtmi:eclipsethreadx:devkit:hlby5jgib2o",
392392
"path": "Company",
393393
"value": "Contoso"
394394
}
@@ -426,7 +426,7 @@ The response to this request looks like the following example:
426426
"data": [
427427
{
428428
"type": "cloudProperty",
429-
"target": "dtmi:azurertos:devkit:hlby5jgib2o",
429+
"target": "dtmi:eclipsethreadx:devkit:hlby5jgib2o",
430430
"path": "Company",
431431
"value": "Contoso"
432432
}
@@ -462,7 +462,7 @@ The response to this request looks like the following example:
462462
"data": [
463463
{
464464
"type": "cloudProperty",
465-
"target": "dtmi:azurertos:devkit:hlby5jgib2o",
465+
"target": "dtmi:eclipsethreadx:devkit:hlby5jgib2o",
466466
"path": "Company",
467467
"value": "Contoso"
468468
}
@@ -529,7 +529,7 @@ The response to this request looks like the following example:
529529
"data": [
530530
{
531531
"type": "cloudProperty",
532-
"target": "dtmi:azurertos:devkit:hlby5jgib2o",
532+
"target": "dtmi:eclipsethreadx:devkit:hlby5jgib2o",
533533
"path": "Company",
534534
"value": "Contoso"
535535
}

‎articles/iot-central/core/howto-query-with-rest-api.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -44,11 +44,11 @@ The query is in the request body and looks like the following example:
4444

4545
```json
4646
{
47-
"query": "SELECT $id, $ts, temperature, humidity FROM dtmi:azurertos:devkit:hlby5jgib2o WHERE WITHIN_WINDOW(P1D)"
47+
"query": "SELECT $id, $ts, temperature, humidity FROM dtmi:eclipsethreadx:devkit:hlby5jgib2o WHERE WITHIN_WINDOW(P1D)"
4848
}
4949
```
5050

51-
The `dtmi:azurertos:devkit:hlby5jgib2o` value in the `FROM` clause is a *device template ID*. To find a device template ID, navigate to the **Devices** page in your IoT Central application and hover over a device that uses the template. The card includes the device template ID:
51+
The `dtmi:eclipsethreadx:devkit:hlby5jgib2o` value in the `FROM` clause is a *device template ID*. To find a device template ID, navigate to the **Devices** page in your IoT Central application and hover over a device that uses the template. The card includes the device template ID:
5252

5353
:::image type="content" source="media/howto-query-with-rest-api/show-device-template-id.png" alt-text="Screenshot that shows how to find the device template ID in the page URL.":::
5454

@@ -111,7 +111,7 @@ If your device template uses components, then you reference telemetry defined in
111111

112112
```json
113113
{
114-
"query": "SELECT ComponentName.TelemetryName FROM dtmi:azurertos:devkit:hlby5jgib2o"
114+
"query": "SELECT ComponentName.TelemetryName FROM dtmi:eclipsethreadx:devkit:hlby5jgib2o"
115115
}
116116
```
117117

@@ -131,7 +131,7 @@ Use the `AS` keyword to define an alias for an item in the `SELECT` clause. The
131131

132132
```json
133133
{
134-
"query": "SELECT $id as ID, $ts as timestamp, temperature as t, pressure as p FROM dtmi:azurertos:devkit:hlby5jgib2o WHERE WITHIN_WINDOW(P1D) AND t > 0 AND p > 50"
134+
"query": "SELECT $id as ID, $ts as timestamp, temperature as t, pressure as p FROM dtmi:eclipsethreadx:devkit:hlby5jgib2o WHERE WITHIN_WINDOW(P1D) AND t > 0 AND p > 50"
135135
}
136136
```
137137

@@ -165,7 +165,7 @@ Use the `TOP` to limit the number of results the query returns. For example, the
165165

166166
```json
167167
{
168-
"query": "SELECT TOP 10 $id as ID, $ts as timestamp, temperature, humidity FROM dtmi:azurertos:devkit:hlby5jgib2o"
168+
"query": "SELECT TOP 10 $id as ID, $ts as timestamp, temperature, humidity FROM dtmi:eclipsethreadx:devkit:hlby5jgib2o"
169169
}
170170
```
171171

@@ -193,7 +193,7 @@ To get telemetry received by your application within a specified time window, us
193193

194194
```json
195195
{
196-
"query": "SELECT $id, $ts, temperature, humidity FROM dtmi:azurertos:devkit:hlby5jgib2o WHERE WITHIN_WINDOW(P1D)"
196+
"query": "SELECT $id, $ts, temperature, humidity FROM dtmi:eclipsethreadx:devkit:hlby5jgib2o WHERE WITHIN_WINDOW(P1D)"
197197
}
198198
```
199199

@@ -214,7 +214,7 @@ You can get telemetry based on specific values. For example, the following query
214214

215215
```json
216216
{
217-
"query": "SELECT $id, $ts, temperature AS t, pressure AS p FROM dtmi:azurertos:devkit:hlby5jgib2o WHERE WITHIN_WINDOW(P1D) AND t > 0 AND p > 50 AND $id IN ['sample-002', 'sample-003']"
217+
"query": "SELECT $id, $ts, temperature AS t, pressure AS p FROM dtmi:eclipsethreadx:devkit:hlby5jgib2o WHERE WITHIN_WINDOW(P1D) AND t > 0 AND p > 50 AND $id IN ['sample-002', 'sample-003']"
218218
}
219219
```
220220

@@ -238,7 +238,7 @@ Aggregation functions let you calculate values such as average, maximum, and min
238238

239239
```json
240240
{
241-
"query": "SELECT AVG(temperature), AVG(pressure) FROM dtmi:azurertos:devkit:hlby5jgib2o WHERE WITHIN_WINDOW(P1D) AND $id='{{DEVICE_ID}}' GROUP BY WINDOW(PT10M)"
241+
"query": "SELECT AVG(temperature), AVG(pressure) FROM dtmi:eclipsethreadx:devkit:hlby5jgib2o WHERE WITHIN_WINDOW(P1D) AND $id='{{DEVICE_ID}}' GROUP BY WINDOW(PT10M)"
242242
}
243243
```
244244

@@ -279,7 +279,7 @@ The `ORDER BY` clause lets you sort the query results by a telemetry value, the
279279

280280
```json
281281
{
282-
"query": "SELECT $id as ID, $ts as timestamp, temperature, humidity FROM dtmi:azurertos:devkit:hlby5jgib2o ORDER BY timestamp DESC"
282+
"query": "SELECT $id as ID, $ts as timestamp, temperature, humidity FROM dtmi:eclipsethreadx:devkit:hlby5jgib2o ORDER BY timestamp DESC"
283283
}
284284
```
285285

‎articles/iot-dps/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -226,8 +226,6 @@ items:
226226
href: ../azure-maps/index.yml
227227
- name: Time Series Insights
228228
href: ../time-series-insights/index.yml
229-
- name: IoT device developer
230-
href: ../iot-develop/index.yml
231229
- name: Azure IoT samples
232230
items:
233231
- name: C# (.NET)

‎articles/iot-edge/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -316,8 +316,6 @@
316316
href: ../azure-maps/index.yml
317317
- name: Time Series Insights
318318
href: ../time-series-insights/index.yml
319-
- name: IoT device developer
320-
href: ../iot-develop/index.yml
321319
- name: Azure IoT SDKs
322320
items:
323321
- name: IoT Service SDKs

‎articles/iot-edge/how-to-connect-downstream-device.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ Typically applications use the Windows provided TLS stack called [Schannel](/win
128128

129129
## Use certificates with Azure IoT SDKs
130130

131-
[Azure IoT SDKs](../iot-develop/about-iot-sdks.md) connect to an IoT Edge device using simple sample applications. The samples' goal is to connect the device client and send telemetry messages to the gateway, then close the connection and exit.
131+
[Azure IoT SDKs](../iot/iot-sdks.md) connect to an IoT Edge device using simple sample applications. The samples' goal is to connect the device client and send telemetry messages to the gateway, then close the connection and exit.
132132

133133
Before using the application-level samples, obtain the following items:
134134

0 commit comments

Comments
 (0)