Sir, you are a gentleman and a scholar. Thank you for this video.

Every thing else he talks other than modbus rtu is BS

That was right to the point. Great!

100% made in USA and all factory in china 😂

what file type does it download automatically to USB, CSV?

Are you going to be demoing this at Automation Fair next week?

Dont suppose you have an templates for Unitronics Vision series PLC's?

Clear explanations, Thanks

Can someone share the link of him explain TCP/IP modbus

6919 Allie Dam

Amen.

MQTT is also platform independent and certificates for security MQTT‘s versions is not an issue，the higher versions all have backward compability

Dear John, it's amazing how easy to understand you give us your knowledge, many thanks in 2024, peace

Get well John. Thanks for the courage and the unforgettable teaching you've left in the heart of many. God keep you safe! How are you doing now?

I’m using this module extensively with RS232 to pull data from Modicon 984s into AB controllers to get their data into our SCADA system. It’s been running for years with zero problems.

Preach

Agree with you John. Custom machines with networks that change constantly is not the place for rigid semi fancy silliness.

So Sorry You are a great person

Not sure where this guy gets his information from, but he's misinformed and plain wrong on most of what he says here. Just because that's how it was done 30 years ago, doesn't mean that's how it should continue today. Ask Tesla or any other majorly automated manufacturer and almost all or going to some sort of IT/OT convergence.

Thank you 👍

Thank for having spirit

Thank you very much

You only illustrated that you are a dinosaur

One thing I didnt follow in the discussion was the comments made around OPC not having a tag naming conventions. As was rightly pointed out there is no global standard for naming equipment tags. I don't understand why that's a opc specific problem. Surely it applies to other protocols as well, such as mqtt or spark plug. The advantage over modbus TCP is that you know the tag name from the object or the topic and you don't just create your own. Do people really want standardized tag names? Do they see that as a limitation of communication protocols?

Wow - just occurred to me how many people I recognized in this one. It's refreshing for me to hear an account of OPC without an obvious chip on the shoulder. Great video

hope you are doing great! My mom is just diagnosed as cancer, I am worrying about her and have the same feeling with you. Best wishes to you，John! Keep the optimistic attitude and follow the instructions of doctors, then everything will be fine!

The link in the description is wrong. It leads to your past book.

but, why nothing about voltage used in RS232 and RS485? It is very important.

Good stuff; a question or remark! Addressing: in OT we cant say that addresses can be or are duplicated as well. They differ either by PLC address or by function codes or final Labels distinguish them from each other.

Video was ruined for me because he thinks Lake Michigan is bigger than Superior.

I would like to see a video discussing offsets. I have a device that has a read value at register 9. I have to use address 30010. Weird

All I need to know, eh? Really? This video has almost no information. E.g., how do slaves get their IDs? Is the data LSB or MSB? Will the bus require some kind of termination? What's the right way to calculate the CRC that you mentioned? What's the baud rate? Some other timing considerations? Etc. etc.

So I come from the audio industry, and I'm happy to see what other uses TSN has besides audio. I agree with some of your points, that in industrial automation, there might be cases that will not have a benefit from the added complexity that TSN brings, but also TSN has so *many* uses (eg realtime audio and video) that it won't be going away, it's going to be a fact of life. also IEEE802.1CB specifies redundancy, ring networks are supported, multiple paths are supported

IT is not whenever! DoD and Government applications have Real Time and Near Real Time requirements also.

thank you so much, very clear from you

thank you alot

Well explained. Clear, precise, and straight to the point

Very nice overview. Subscribed and bought the blue book 5 minutes into the video 🙂

Ignore the haters? haha. I didn't see any haters...I see many people pointing out that he is very wrong about Vlans. Honestly...these type of videos are what create greater gaps between IT and OT departments....its the same network....OT people have a few different requirements but they have to work together. If you have a guy like this telling IT why their network is different and he is incorrect...well that just shows you why IT people don't trust OT people and are usually the bottle neck for OT projects.

is darth vader in your lecture?

Network segmentation / microsegmentation / zero trust are all (security) things on an 'IT' network. Maybe if you do an updated video you could talk about security / implicit trust.

Thanks a lot

Thank you for sharing your knowledge

Are your switches virtual or physical? Or it doesn’t matter?

I think these videos are a bit superficial, but that makes sense because they are introductory. And I admire anyone who uses ‘architect’ as a verb.

Interesting video. Good comments, too, if you ignore the haters. Thx.

Cheers

The most simple and open protocol to understand is modbus and comes built in scheineder electric device. U need only manipulate reading especially in floating point datas

The scheduler will be some AI like Bard in cooperation with quamtum computing; it´s beeing build, it just takes time! But yes, I agree in one point with you - linking IT to OT - I don´t see the reason why either to risk OT to hacker!

In the context of your good discussion, what is meant by cyclic message?