Love the subtle dig at AWS with the tshirt. Not sure if Shane got it in the moment, but well played :)
@olivierbloch1256
2 жыл бұрын
😎
@ucquach7177
2 жыл бұрын
Wonderful ... Thanks for this
@UncleF115
2 жыл бұрын
I'm learning Azure IOT and finished az220. all the episode are informative but how can i go though 172 videos, any index avail? or grouping of the videos based on topic so i can take a reference and and go through in a logical order.
@olivierbloch1256
2 жыл бұрын
Hi! That's not something we have yet as the concept of the show is to publish as topics come. But I can see how an index and better way to navigate could help in a learning journey. I'll try and find the best solution for this. In the meantime, you can navigate the playlists that allow watching content (IoT Show episodes and IoT demos) for each service. Stay tuned for updates on this
@arseniysleptsov9217
Жыл бұрын
I think I can address my questions here (at least something related to what I was doing): 1. what is the difference between IoT edge device with IoT device? I decided to connect my plc via node-red installed in the container on IoT edge device (raspberry pi) instead connecting it through node-red directly to IoT device because I thought that IoT edge device may store some data in a queue while IoT device will lose in case of no network. Am I right? 2. IoT edge device modules disappear when the PLC turned off and back again (`sudo iotedge list` gives no outputs). The PLC is connected to the Raspberry Pi via ethernet cable. I need to fix every time the raspi nameserver configuration. How can I solve the problem?
@MicrosoftIoTDevelopers
Жыл бұрын
Hi Arseniy Let me try to answer: 1. IoT Edge is a runtime based on Docker, allowing to run workloads in containers (called "modules") offering some sort of app model on the device with local orchestration and message routing, while an IoT Device is a device running one of our SDKs (or an MQTT library) to connect directly to IoT Hub and in which you need to code any sort of logic yourself. IoT Edge does indeed offer offline capabilities that you can configure (learn.microsoft.com/en-us/azure/iot-edge/offline-capabilities?view=iotedge-1.4), while the device SDK don't natively offer such capability; if coding using one of our device SDK you would need to implement your own offline logic with retention, buffering in storage and so on. Note that IoT Edge HW requirements are way higher than running our device SDK as you need a hardware that can run Docker. 2. It seems your IoT Edge runtime manifest is not persisted on your device
Пікірлер: 9