Dear Madam/Sir,
Thank you for your interest in our products.
You can use our QuickOPC product (most likely, QuickOPC Standard Edition) to provide OPC client functionality inside your application. QuickOPC itself, however, is simply a means of providing the communication to the OPC servers. As such, it will greatly relieve from the need to write the communication code, but developing the HMI functionalities described below remains onto you.
To the specifics:
We are planning to create an HMI application on .NET platform. The application will have following features:
1. User authenticated login
This is an application functionality, generally outside the QuickOPC scope. If user credentials need to be passed to the target OPC servers, OPC Unified Architecture does allow this, and QuickOPC support passing the credentials as needed.
2. HMI designer studio - Here the designer will be allowed to create various screens. Add controls to the screens and bind tags with the controls.
We have a “Live Binding” functionality in QuickOPC that allow to bind OPC data to controls on Windows Forms. The binding is done in Visual Studio. If you aim at having your own designer app, the QuickOPC can provide the data binding, but you need to develop the HMI designer yourself.
3. HMI operator bench - Here the operator will run the application in operator mode and see the results during run time along with alarms. Start/Stop the execution of the controllers.
The answer is similar to the above. If the screens were designed in Visual Studio with QuickOPC Live Binding, you would build your app and run it, with the controls on forms bound to OPC server items. If you create your own designer app, you will probably also need to create a runtime environment (where, again, QuickOPC would facilitate the OPC data transfer).
Let me know should you have any additional questions.
Yours sincerely,
