Vijeo citect V7.0 R3 / OFS V3.31 Patch A

Hi Mohamed,

Any unusual entries in the I/O Server's syslog or in the OFS diagnostics window?
I would suggest upgrading to a newer OFS if possible (v3.63 is current) as older versions are known for instability.
Also, what Citect driver (protocol) do you use? OFSOPC or normal OPC? And which version?

Best regards,
Patrick

Hi Patrick,

The used protocol is OFSOPC.

is the newer OFS v3.63 compatible with with Vijeo citect V7.0 R3 and compatible with Windows XP Professional ? if yes, we can do this exercise.

There is no unusual entries in the I/O Server's syslog or in the OFS diagnostics window.

Best regards,
Mohamed

Is there any reason to run today Windowx XP and 7.0?
I think it is time to upgrade.

You definitely need to upgrade to a supported OS at a minimum. Even Windows 7 end of extended support occurred on 14th January 2020.
Like others mentioned, there are lots of bug fixes and issues addressed in newer OFS (currently 3.63 is latest). Also OFSOPC driver has had many updates over the years to make communications more stable. Latest version can be downloaded from Connectivity Hub (https://softwaresupportsp.aveva.com/#/connectivityhub).
Lastly, that version of Vijeo Citect is also long out of support. Best to upgrade to the latest, Plant SCADA 2020 R2 will be released in a months time.

This is correct Oliver,
The issue i face that while upgrading the VJC7.0r3 to Citect2016 or citect2018, the complie process failed with the following error

"function is obsolete and cannot be used anymore(E2101)"

This is Error related to Alarm_CSV

any suggestion ? advice ?

Yes; that function is obsolete, and you'll need to replace it. Every system that migrates has to deal with this issue. Obsolete function codes need to be re-engineered unfortunately.

To be fair, this is a very old configuration, and you should upgrade as soon as you can.
I even had to look up if Citect 7.0 supports MultiProcess mode, and it does. This may have to do with your problem, I think.

Does Citect run in multiprocess mode in your setup? If it does then the Runtime Manager shows seperate entries for Client, Alarm Server, Trend Server, I/O Server and Report Server. It can be enabled/disabled in the Computer Setup Wizard.

If your setup does not run in multiprocess mode, then any function in your Citect system can temporarily suspend I/O processing or handling alarms, etc. Examples of blocking functions are: cicode FOR or WHILE loops with no SleepMs statements in them, reading to/writing from files; executing external programs; calling DLL-functions or executing badly designed cicode or VBA functions.

In Multiprocess mode, only the process that executes one of these blocking function will be suspended, but not the other processes.
Howerver, switching Multiprocess mode on for a project was not engineered for this mode may lead to unexpected behaviour: Local Variables and GLOBAL or MODULE cicode variables are local to the Citect process instead of the whole computer and some system functions only work in a server process (like some I/O Device functions) or a client process (like animation and display functions).

So fixing your problems and/or upgrading to a newer version will involve some (re-)engineering.

Best regards,
Patrick