Hi,

Thanks for the update.

I have a query regarding subscription based one.

What I am doing is sending group of events for subscription using below code, As mentioned in ExamplesCOM. And waiting for item changed events, Here I am getting single item changed event at a time, I suppose to get event for all group of items I subscribed, but I am not.

I get single item and convert into JSON and upload to cloud, it leaks to much memory for each item if I do. Therefore, I am looking for a way, where I can get group of items get changed at a time where I subscribed group of items only.

Please do let me know your inputs.


for (int i = 0; i < noOftags; i++)
{
_EasyDAItemSubscriptionArgumentsPtr ItemSubscriptionArgumentsPtr(_uuidof(EasyDAItemSubscriptionArguments));
ItemSubscriptionArgumentsPtr->ServerDescriptor->UrlString = urlString.m_str;
ItemSubscriptionArgumentsPtr->ItemDescriptor->ItemId = itemIds.m_str;
ItemSubscriptionArgumentsPtr->GroupParameters->RequestedUpdateRate = 1;
arguments.SetAt(i, _variant_t((IDispatch*)ItemSubscriptionArgumentsPtr));
}

LPSAFEARRAY pArguments = arguments.Detach();
CComSafeArray<VARIANT> handles(ClientPtr->SubscribeMultipleItems(&pArguments));
arguments.Attach(pArguments);

Okay, I have done same thing for connection status, Sending first 2 tags to check connection status than I am starting actual tags execution, In that case am I doing right I guess.

The CPU and Memory usages are more in QuickOPC Libraries, Please help me to solve this CPU n Memory issues or any lead which will help me.

Hi,

1. How do I check server status? whether its running, disconnected and etc? Is there any QuickOPC API for this, as per as I searched I could not find one.

2. My application taking around 50MB of RAM consistently, In that around 17MB is my application(private working set) and 42MB is shared working set. In that case quickOPc assemblies are taking 42MB?

PLease clarify above questions.

There are 130+ events. I have put sleep for 1 min so that event is having 1 min time to deliver.

I just checked by commenting this loop for sometime, is there any-other way to wait continuously without this loop?

Inside I put Sleep(60000);

while (1) {
Sleep(60000);
}