Help on Omniflow Computer and Citect SCADA

That's an ancient protocol. I could only find this:
https://softwareforums.aveva.com/citect_community/driverweb_forum_archived_content/citect_drivers_-_other/omni/f/1335/t/26305
It's seems pretty outdated. I doubt that this will run under a new OS, but you can give it a try. Maybe you have to check if there is an Omniflow OPC Server and switch the protocol to OPC.

Thanks for the swift reply, but I think this OMNI driver is different right? Because when I tried then compile it gives an error "Bad IO Device variable".

Normally, if a driver doesn't come with Citect, you can go to the Connectivity Hub page of the Aveva Support site and download the driver separately or find out how to get it (if it requires a license). I don't see this driver anywhere. Also, it did not come with Citect 6.10. This may be a custom Citect driver written by Omni or a 3rd party.

Check if your old server has a driver installer file for OMNIFLOB saved somewhere. Try installing it on the new PC. The other option is to manually install it:

• Copy OMNIFLOB.dll and OMNIFLOB.dbf files from the Citect 6.10 Bin folder to the new Citect Bin folder
• Open the Bin\protdir.dbf file in Excel or LibreOffice and find the entries for OMNIFLOB. Copy those entries to the new Citect's Bin\protdir.dbf. Note: the columns may not be in the same order
• Optionally, do the same editing for proterr.dbf
• Copy the new protdir.dbf and proterr.dbf to the Bin folder on any client computers (they don't need the other files)

Now, you should see the new protocol in the new Citect and should be able to compile the project. Try running Citect and see if it can run the driver. If it won't run, you may have to use Dependency Walker to open OMNIFLOB.DLL and find what other DLLs it depends on, then copy those files from the old PC.

Hi Rominaldo,

It might be a custom driver that was built specifically for that protocol. Is there a chance that you have the installer for it somewhere archived? Not all custom drivers have installers though.

If not, you could copy the driver files from the old to the new system (should be called something like OMNIFLOB.dll and OMNIFLOB.dbf; look in the BIN folder). You should then manually add a record for the protocol to PROTDIR.DBF (again, look at the existing system how the fields should be filled; look for a record that contains OMNIFLOB).

Please try it first on a test system to check if the driver is compatible with the new OS and/or Citect version.

Regards,
Patrick

Haha, Eric beat me to it

Very nice you nailed it Sir, thanks to all your support I will try that procedure. Thanks to all. :)