Topic Name Conflict (MBENET)

P

Thread Starter

Parag

Topic Name Conflict in TFDCS:

We are doing a project which includes Modicon Quantum PLC and InTouch SCADA.

Facing a problem regarding transfer of Discrete Signals through MBENET IO server.

In TFDCS (Area) under Discrete Signals there are two Categories:
1. Discrete Signals which SCADA is reading from TankFarm Quantum PLC. (Alarms and Status of Valves, Pumps etc.)
2. Discrete Signals which SCADA is writing to TankFarm Quantum PLC. (Start and Stop for Pumps and MOVs)

Transfer of signals between InTouch SCADA and Quantum PLC is carried through MBENET i/o Server.

In MBENET:
For these two categories two different Topic Names are being created.
1.PLC81_DISCRETE for reading signals from PLC.
2.PLC81_DISCWRITE for writing Signals to PLC.

Problem:

The Signals which are transferred through PLC81_DISCWRITE Topic Name are taking about 7 to 8 Seconds delay. While signals transferred through PLC81_DISCRETE topic name are getting reflected in SCADA immediately after status change in PLC.

But if one signal which is transferred through PLC81_DISCWRITE is transferred through PLC81_DISCRETE then it gets reflected in PLC immediately after command is given from SCADA.

SCADA is writing 669 signals through PLC81_DISCWRITE Topic Name. Address range used in Quantum PLC is 4001 to 4952 and 1665 to 1939. Does Address range have any effect on polling of signals?

And SCADA is reading about 3000 signals through PLC81_DISCRETE Topic Name.

In MBENET one can define about 16 Topic Names for one PLC (i.e. 1 IP address)

In our application we have defined only four topic names.

If anyone knows about it do reply quickly pls.

Thanks
Parag
 
Top