LabVIEW
tcp/ip help communication
Solved!
@Mark_Yedinak wrote:
They are both IP protocols but TCP/IP is only TCP.
NO!
"The Internet protocol suite, commonly known as TCP/IP, is the set of communication protocols used in the Internet and similar computer networks. The current foundational protocols in the suite are the Transmission Control Protocol (TCP) and the Internet Protocol (IP), as well as the User Datagram Protocol (UDP). "
@bleite wrote:
It's better if I post/attache here a video of the functionality of this system?
No!!!! It is a million times better to attach your VI instead. It is completely silly to show us truncated code pictures of gigantic rigid diagrams.
It would take us 2 minutes to rewrite so the code is scalable and fits on a postage stamp while doing exactly the same, but better. For example, if you currently want to change the displayed text, you would need to rewrite the entire thing!
Currently, this is just a gigantic, inflexible, unmaintainable mess!
@altenbach wrote:
@Mark_Yedinak wrote:
They are both IP protocols but TCP/IP is only TCP.NO!
"The Internet protocol suite, commonly known as TCP/IP, is the set of communication protocols used in the Internet and similar computer networks. The current foundational protocols in the suite are the Transmission Control Protocol (TCP) and the Internet Protocol (IP), as well as the User Datagram Protocol (UDP). "
No! I side with Mark on this one. Both UDP and TCP are build on top of IP. The use of TCP/IP to refer to any internet protocol is technically wrong although quite common under non-technical people. But until recently HTTP was a pure TCP based protocol and most others like FTP, SMTP, and POP3 also use TCP as underlaying transport layer so in this sense it’s not entirely wrong. But UDP definitely doesn’t fit into the TCP/IP protocol designation.
@rolfk wrote:
But UDP definitely doesn’t fit into the TCP/IP protocol designation.
With that logic, a walrus only eats walnuts. 😄
Quote from a casual google search:
A couple of years ago, I had the pleasure of attending a talk by Vint Cerf. Maybe we could ask him 😄
Over 20 years ago, I wrote a full set of VIs to parse the raw packet headers to analyze network traffic. Worked great. One of the first home routers (Zyxel prestige 310 running their zynos) had a hidden mode to send a raw copy of all packets processed to a designated IP address on the LAN. My listening LabVIEW program was able to do basically the same as wireshark and was able to identify bugs in the firmware where certain ftp traffic was handled incorrectly. I still have the device, but with a 10Mbps WAN port it's pretty useless. Worked fine on my blazing (at the time!) 1.5Mbps Lancity cable modem (pre-docsis!), though.
@bleite wrote:
VI Atacched
(We really don't need the modbus libraries, just your VI!!!)
My Portuguese is not good enough to understand the details of the manual and you still need to figure out how to calculate the checksum and from what parts, but here's a quick draft that should get you started. I am sure it is full of bugs, but you should be able to figure out the general idea....
