escott (Customer) asked a question.
Trying to connect to an LS-XMC-E16A plc, not having much luck. I realize that there is no specific protocol for the LS PLC's but I was trying to use the more generic Modicon profile. LS PLC returns errors when trying to establish SOCKET_TCPCONNECT. If anyone has anything that might help I'm all ears. If not I'll have to hunt down a LS HMI :(
You should start here
https://www.automationdirect.com/support/question-answer?techId=5928
I did exactly as that post suggests. I was able to get that far by manual reading. But I could not get the two to actually connect and recognize each other. As in the first post, when trying to use SOCKET_TCPCONNECT, which is the first step in the process, there are errors that I cannot make go away, and I feel that I have followed all the directions correctly. I've ordered an LS HMI at this point.
"when trying to use SOCKET_TCPCONNECT, which is the first step in the process, ..."
SOCKET_TCPCONNECT is used when the LS is the client. When connecting to a CM5, it will be the server, so I'm not sure what you mean by that.
I have only found documentation that the CM5 is a server, not a client. Therefore the LS cannot be the server. So I'm not sure what you mean by that. From the help file on the Cmore "The following information applies for Modicon Modbus TCP/IP PLC compatible with C-more panels.
The C-more panel is the master when communicating with this device."
Regardless I have fixed the issue by ordering the LS screen.
"The C-more panel is the master when communicating with this device. "
master = client
I realize you have decided to move forward with an LS panel but wanted to add some info in case others, looking further details, may happen upon this thread.
When used with a Cmore, the PLC will be the server and the Cmore will be the client.
Here is a link detailing setup for the Modbus server in the XEM CPU
Set up the Modbus Server Mode on XEM CPU
A key piece of information here is the Server Mode must be changed from "XGT server" to "Modbus Server"
Here is a link to a video demonstrating Modbus server configuration.
https://youtu.be/GaC1pulM4-k?si=8eDgPXwMtib2VRSD
As a self-taught programmer, one headache I find is vendors using terms interchangeably: Master = Client. Huh? I don't see the similarities.
Anyway, I don't remember who the manufacturer was, but their way of describing comms that made sense was "parent" and "child".
I know AD is not going to change an industry's terms, but I think placing "parent" and "child" in parentheses in help files will assist people like myself in understanding the roles of the HMI, PLC, and other networked devices.
Server=Slave Therefore Client=Master is how I have to pause and think about it when they switch terms.
Words are violence now ;) LMAO. "Male" and "female" along with Master and Slave will be frowned upon by the modern indoorsmen this perpetually offended world is producing. A related topic:
https://www.plctalk.net/forums/threads/ot-connector-terminology.135192/#post-932710
"The C-more panel is the master when communicating with this device. "
master = client
I realize you have decided to move forward with an LS panel but wanted to add some info in case others, looking further details, may happen upon this thread.
When used with a Cmore, the PLC will be the server and the Cmore will be the client.
Here is a link detailing setup for the Modbus server in the XEM CPU
Set up the Modbus Server Mode on XEM CPU
A key piece of information here is the Server Mode must be changed from "XGT server" to "Modbus Server"
Here is a link to a video demonstrating Modbus server configuration.
https://youtu.be/GaC1pulM4-k?si=8eDgPXwMtib2VRSD