You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've one more question, about how does reading of Alarms work.
I see this: TestWaitForAlarmNotifications, wich uses WaitForNewS7plusReceived(waitTimeout);
How does this work. What about I want to use the same connection to read Tags and Alarms?
As I see the Lib could not be used with multiple Threads, as WaitForNewS7plusReceived does not wait for a specific answer, it only returns the next one.
Or does the protocol at all not support multiple actions at once?
The text was updated successfully, but these errors were encountered:
It's for now only a testfunction to analyze how it works. I think it would be clearer to do all alarm relevant communication on a separate connection. If I remember correctly, that's also the way Siemens handles this in their software. They use one connection for variable access, one for events, and start an optional 3rd for exploring. I don't think this is a "must", but if something major in the event task goes wrong, you can just restart this session and keep the variable flow working.
Hello Thomas,
I've one more question, about how does reading of Alarms work.
I see this: TestWaitForAlarmNotifications, wich uses WaitForNewS7plusReceived(waitTimeout);
How does this work. What about I want to use the same connection to read Tags and Alarms?
As I see the Lib could not be used with multiple Threads, as WaitForNewS7plusReceived does not wait for a specific answer, it only returns the next one.
Or does the protocol at all not support multiple actions at once?
The text was updated successfully, but these errors were encountered: