We are using OPC Mirror in order to map National Instruments OPC server to DeltaV’s.
3 types of pressure, flow and temperature transmitters (Both wireless and wired HART signals) together with 2 types of On/Off and flow valves are going to map OPC servers. We tried mapping pipes one by one and validated those. The system is working properly until mapping of one device which could be any of explained. Then whole system collapses and we have to reinstal the OPC mirror in order to continue same procedures of mapping pipes. We have tried different order of mapping and validating instruments. We have even tried to add pipes into two different modules and OPC mirror is still hanging at once we map a device of any kind.? We have observed system-crash sometimes after mapping 15 and sometimes after mapping 18 or 22 devices. By the way, we can’t see the system tree at the upper left field of OPC mirrors configuration window.
We are assuming following critiria to be met:
- Quantity of pipes
- Quantity of OPC server licences (How do we check our licences quantity?)
- Incompatibility of OPC-Mirror with a mixed wireless and wired HART (Our wireless Gateway is connected to DeltaV through a serial card and not via ethernet – Gateway is an older type which is not directly connectable)
- Combination of transmitters and valves
Does anyone have any idea what could be wrong?
What version of DeltaV are you running?
What version of OPC Mirror? Where is it installed (DeltaV Application Server)?
In the Mirror Configuration tool, choose HELP - ABOUT, and the pop up will show you the license and number of servers.
When you say "the whole system collapses", what exactly are the symptoms? Can you just restart the mirror client?
When you say you "don't see the tree", does it give you the error when you create the PIPE (i.e. "Unable to browse server...)?
In reply to Travis Neale:
I have been using OPC mirror version 5.1.1 under license VE2211 (for 2 servers) for data transfer between DeltaV and Provox. I have set up two pipes (one pipe for DeltaV to Provox data and another pipe for Provox to DeltaV data). The OPC mirror is installed on DeltaV application Server. I have not seen any problems with data transfer in either direction (Provox to DeltaV or DeltaV to Provox).
Since OPC mirror does not care about the status of data, you may have to handle status issues by using watch dog timers or some other techniques. I have similar questions as Travis Neale has (what exactly are the symptoms)?