Control

Monitor Pro 7.6 Modbus TCP Communication Problem

  • Thread starter Ayhan Buyuksemerci
  • Start date
A

Thread Starter

Ayhan Buyuksemerci

We have 3 Premium PLCs running under Monitor Pro 7.6 via Ethernet with Modbus TCP. Each PLC has more than one dataset definitions. Under these datasets total 3500 I/O Tags defined. If communication to a PLC fails for a short time there is no problem to continue to communicate. However, if it fails for a few minutes, Modbus TCP Driver Process never tries to open connection to any of the PLCs. It neeeds to be restarted.
Does anybody have an idea on what causes this problem and on how to solve it?

If it helps, here are our
Modbus TCP/IP Protocol Driver Settings.

MODBUS TCP/IP Driver Device Definition

DEVICE NAME IP NETWORK ADDRESS INDEX VARIABLE
EGO_AT_MBUSTCP 192.168.0.33 1
EGO_TAT1_MBUSTCP 192.168.0.34 1
EGO_TAT2_MBUSTCP 192.168.0.35 1

STATUS TAG



Ioxlator Mailbox Definition

Ioxlator Mailbox Tag Max MSG in IOX
EGO_MODTIOXMbx 100

Modbus TCP/IP Driver Mailbox Definition

Protocol Deriver Mailbox Tag
EGO_MODTDrvMbx


Thanks.
 
R

Ruslan

Hi,

You can use "Reconnect column" and set value 'YES
or enter tagname with default value 1.

Ruslan
 
You must log in or register to reply here.
Thread starter Similar threads Forum Replies Date
F How to monitor values inside addresses in PLC using Unity Pro S? Programmable Logic Controller - PLC 0
S Monitor Pro FactoryLink DDE Communication Human Machine Interface - HMI 3
O Monitor Pro and Modbus TCP/IP Modbus 0
E Monitor Pro 7.6 Modbus TCP Problem Modbus 1
A Write data to Monitor Pro from Momentum ME1 via Modbus TCP/IP Modbus 1
Similar threads
How to monitor values inside addresses in PLC using Unity Pro S?
Monitor Pro FactoryLink DDE Communication
Monitor Pro and Modbus TCP/IP
Monitor Pro 7.6 Modbus TCP Problem
Write data to Monitor Pro from Momentum ME1 via Modbus TCP/IP

You May Also Like

Top