Everyone a great god, c # and mitsubishi PLC (without Kepware) direct communication, I look at the net is introduced, such as call MXComponent components and CPU built-in Ethernet interface and the Ethernet communication module built-in Ethernet support MC protocol and sockets, want to ask next: 1000 data read and write 100 data, which way is better? Please comment ~

CodePudding user response:

MC agreement, directly to the PLC internal register, do whatever you want,

CodePudding user response:

reference 1/f, youth wind response:

,

MC agreement directly on the PLC internal register, do whatever you want,

someone says MC agreement with socket go? Is that so? MC agreement and the socket is not built-in Ethernet communication mode? Please instruct,

CodePudding user response:

Let PLC developers and you directly set a TCP communication protocol is one of the best
Directly read register feels a bit stupid, a result is all events trigger you cycle to read, but not trigger after the initiative to give you a message
Both to the target PC with very large MX component

CodePudding user response:

reference stherix reply: 3/f

let developers of PLC and direct you to book the TCP communication protocol is one of the best
Directly read register feels a bit stupid, a result is all events trigger you cycle to read, but not trigger after the initiative to give you a message
Both to the target PC with very large MX component

great god, and this can define your own TCP protocol? I just learning, the second MX time than with the MC will be more? Please comment,