Can I import items from the CAENHVOPCServer2.2 to DSC ?

[Stefania_Spagnolo]

I'm just starting to test DSC. I see I can import channels defined on NI DAQ (PCI) into the configuration file of the tag engine just using the configuration Wizard. On the other hand, I've installed on the same PC the CAEN HVOPCserver2.2 whose items are visible through the configuration wizard, but Labview (6.i) get stack when tryint to add channel dependent items to the conf. file.
I've also updated NI Logos to ver. 4.4 but this doesn't help.
Did anyone experienced (or solved) these problems ?
Thanks.

[Roli]

Hi Stefania,

Did you try to connect from another OPC Client to the CEAN HVOPCserver?

A good link is our troubleshooting page for OPC and DSC: Tools for Troubleshooting OPC Interface Problems

If LV DSC isn't the only OPC client to have trouble, than we would know that there is something wrong in the OPC Server implementation. I suspect that other OPC clients will as well, since LV DSC OPC client works with other OPC servers.

When the TCE uses the server, it creates a group and adds items to it, and validates the items. It never activates the items. Then, we remove the items and remove the group. Some time right after we release the group, th
e server could cause a crash in our code. Possibly it's calling into our group after it's been deleted? Or something similar?

Given that our OPC client works with dozens of other OPC servers without exhibiting such behavior, it is maybe a server bug.

We have seen similar behaviors with other various OPC servers.
E.g. The server is deliting an object that provides the interface "IEnumOPCItemAttributes" when we still have a reference to it. This violates the IUnknown interface contract.
We can avoid their bug by releasing our interface prior to informing the server that we're done with the group.

This change is encountered in the LabVIEW DSC 6.1 Release.
A patch that avoids this bug in the Servers is attached for LV DSC 6.0.2.

Could you try the attached DLL with your OPC server? If this does not help you might contact the OPC server company for the latest version or/and you contact National Instruments support directly, thus the Applications Engineer can reproduce the beha
vior.

Hope this helps
Roland
National Instruments
PS: the file belongs to \vi.lib\system"