I'm trying to figure out what, when I connect to a device to read Modbus data over TCP/IP, Moscan64 always shuts down.
It's been a while since I connected to a PLC via MODSCAN64 via TCP/IP, but as I remember when using MODSCAN32, I would first Identify the IP address of the PLC, and set my laptop to the same network:
PLC IP Address: 192.168.2.10
PC Address: 192.168.2.1
I've confirmed that I can PING 192.168.2.10 from my laptop
For some reason this causes MODSCAN64 to shut down...Am I using the wrong IP address on my laptop?.
Regards,
DM
"Real world Knowledge isn't dropped from a parachute in the sky but rather acquired in tiny increments from a variety of sources including panic and curiosity."
It's been a while since I connected to a PLC via MODSCAN64 via TCP/IP, but as I remember when using MODSCAN32, I would first Identify the IP address of the PLC, and set my laptop to the same network:
PLC IP Address: 192.168.2.10
PC Address: 192.168.2.1
I've confirmed that I can PING 192.168.2.10 from my laptop
For some reason this causes MODSCAN64 to shut down...Am I using the wrong IP address on my laptop?.
Regards,
DM
"Real world Knowledge isn't dropped from a parachute in the sky but rather acquired in tiny increments from a variety of sources including panic and curiosity."