Hello, good morning. I'm not sure if this section would be the recommended one to this question, so I'm sorry if not (if possible, some moderator could move it to the right place please?).
Well, we have a MOCCA software (Honeywell) that is our Alarm Management tool. It basically reads many Delta V control modules parameters (such as HI_ALM.CV, HI_ALM.OPSUP, engineering units and range, etc), catalogue everything, and we use it also as a tool for alarm rationalization. The problem is that we are not being able to read the MODULE/DESC.CV parameter for some reason. If you check the OPC branches on the OPCWATCHIT, we can't find this parameter there, but if you type it directly to "Type Path", it reads perfectly.
We contacted Honeywell support many many times, but they are unable to solve this issue. Do you guys have any idea about how to fix it? Is there any other path to read the control module description? Why it doesn't appear in the OPC branches? Please see an example below:
The module description is not stored as a parameter within control modules, and as such is not exposed to the OPC Server Browser. However, the path is available via the OPC server. Using the OPCWatchit tool on the DeltaV system, the browser does not show the /DESC parameter. But manually typing the path will return the module's description, as you have shown abofe.
The browser functionality of an OPC DA Server is actually an optional feature of the OPC Server, and client applications can only browse what the OPC Server has exposed. A client application would not be able to overcome this, except by providing an independent method to derive and expose the description parameter.
Andre Dicaire
In reply to Andre Dicaire:
In reply to Rafael Rebouças de Araujo:
Leo
In reply to Leo Paradis:
In reply to Youssef.El-Bahtimy: