Micro800™ controllers for Industrial Internet of Things (IIoT) applications

แชร์
ฝัง
  • เผยแพร่เมื่อ 30 ก.ย. 2020
  • This video demonstrates how you can configure a Micro800™ controller in Connected Components Workbench™ software version 12 to send data within the Industrial Internet of Things (IIoT) via Message Queuing Telemetry Transport protocol (MQTT protocol).
    Learn more about Connected Components Workbench software and how it helps reduce initial machine development time and cost at rok.auto/ccw
  • วิทยาศาสตร์และเทคโนโลยี

ความคิดเห็น • 3

  • @espenhalvorsen1780
    @espenhalvorsen1780 3 ปีที่แล้ว +1

    The sample code is NOT marked as "preferred", which according to the FAQ is not supported by Rockwell. The same applies to the Logix MQTT-code.

  • @nkt20880
    @nkt20880 2 ปีที่แล้ว +1

    What is the router recommended for the iot connection to micro820 to mqtt broker

  • @michaelbriggs1713
    @michaelbriggs1713 ปีที่แล้ว +4

    Your tutorial videos kind of suck. First, putting text on the bottom instead of having someone talk is annoying - if I read the text, I can't watch what is being shown, and by the time I'm done it's moved on to something else. So I have to keep pausing the video every time new text comes up.
    Second, and perhaps most importantly, they often seem like they are made by somebody who doesn't actually know how to implement these things. There are soooo many things not explained in this video - and the few that are are the obvious things (like setting the IP address). If the sample code had some useful comments in it, that would be helpful - but of course there are almost none. It's not explained what the various variables are. Some of them are obvious - and in fact the only ones that have comments are the obvious ones (locserver.Port and locserver.IPaddress).
    Overall, the video is borderline useless. It says the obvious stuff, but doesn't explain how things work. Like saying "trigger these rungs (2 and 3) to subscribe or unsubscribe to a topic". The "subscribe" and "ubsubscribe" pulse contacts make it obvious that those rungs are involved in that - but what is the "uniquSublden" variable that is having 1 added to it at the start of each of those rungs, and why? And whether subscribing or unsubscribing, subTopicName has topicName_input assigned to it. Why? It never seems to change what subTopicName is, so why assign that each time you subscribe or unsubscribe? And then the video text says the next rung is used for subscribing and unsubscribing (basically exactly what it said about the previous two rungs), but doesn't discuss how the UDFB works at all.
    Please hire somebody who can actually explain things. And put useful comments in your sample code.