WEBVTT

1
00:00:00.050 --> 00:00:11.050
This prepared Enterprise lab contains a PLC, an Industrial Edge device, a broker, and Linux clients for the protocol checks.

2
00:00:15.800 --> 00:00:25.800
Open IoT Operations, then PLC tags, to inspect each tag’s value, quality, unit, and protocol mapping.

3
00:00:36.000 --> 00:00:46.000
Use the Linux client to browse the PLC’s OPC UA address space, then read the conveyor’s Boolean value.

4
00:00:47.850 --> 00:00:56.350
Use a bounded subscription to observe this Boolean node while a second client changes it.

5
00:01:04.750 --> 00:01:13.250
A second client writes false to the same node while the first client observes it.

6
00:01:13.600 --> 00:01:21.600
The observer reports the changed value, completes its observation, and returns to the prompt.

7
00:01:23.550 --> 00:01:31.050
Press Control C to interrupt a longer observation and return to the prompt.

8
00:01:34.150 --> 00:01:42.200
A Boolean node rejects an invalid value, leaving the last accepted value unchanged.

9
00:01:49.600 --> 00:01:58.100
Return to PLC tags to confirm the same Boolean value and the unchanged temperature reading.

10
00:02:05.950 --> 00:02:13.950
Writing one to the mapped Modbus coil restores the same PLC tag to true.

11
00:02:14.950 --> 00:02:23.950
Read input register two: the value two hundred and fifty represents twenty-five degrees in this mapping.

12
00:02:25.650 --> 00:02:32.650
An unmapped register is refused, while the valid temperature reading remains available.

13
00:02:34.700 --> 00:02:43.700
Use the separate Modbus server for a writable holding register, then read back the value forty-two.

14
00:02:46.200 --> 00:02:54.200
On the CoAP server, POST creates a temperature resource with the starting value twenty.

15
00:02:57.250 --> 00:03:04.250
GET reads that resource, and PUT updates it to twenty-six point five.

16
00:03:07.150 --> 00:03:15.050
Updating an unknown resource returns not found and leaves the existing resource unchanged.

17
00:03:29.750 --> 00:03:38.750
Open Edge connectors and set the broker, group, and edge-node identifiers used in the forwarded topics.

18
00:03:57.000 --> 00:04:06.500
Edit the PLC connector to read the temperature node and publish it as a metric named temperature.

19
00:04:08.750 --> 00:04:16.750
Saving a mapping leaves it stopped, so you decide when polling and forwarding begin.

20
00:04:23.850 --> 00:04:31.350
Start the connector, then inspect the exact metric delivered to Broker1 in Topics.

21
00:04:54.500 --> 00:05:04.000
Add a second connector for the Modbus coil, then confirm its Boolean metric at the same broker.

22
00:05:16.350 --> 00:05:24.350
An unavailable destination is refused without changing the saved broker or clearing your draft.

23
00:05:34.500 --> 00:05:41.500
Stop both connectors and confirm that their data-topic counters no longer increase.

24
00:05:41.700 --> 00:05:49.700
Reopen the lab to check the saved mappings, destination, and stopped states before continuing.

25
00:05:49.800 --> 00:05:58.350
You have read and changed PLC tags, checked three industrial protocols, and controlled edge forwarding.