Hi all,
I'm currently trying to develop a new widget for WinCC OA. I'm quite newbie with Qt creator and I would like to know if it is possible to test the widget directly in Qt creator without having to start a WinCC OA UI.
My problem is that if I start an UI, I cannot replace the widget after each compilation as it is locked by UI process...
Is there any way to do efficient testing during dev? I really wish to see easily how my widget behave graphically in a quick and efficient way
Thanks
Test an EWO without starting an UI
- fmulder
- Posts:330
- Joined: Wed Feb 03, 2010 9:46 am
Re: Test an EWO without starting an UI
Yes, there is a simple solution ! Don't develop a widget.
Some years ago I developed the Gis viewer as an ActiveX. (because I had no knowledge of Qt). I was then asked to port it. What I did was:
1) use QtCreator to start a standalone application where you implement the graphics of your 'shape'. Lets say that your class doing the actual drawing is called 'MyDrawingClass'
2) Then start a widget using the WinCC Oa Api. Include the source files of CMyDrawingClass
You now have a standalone application that allows you to develop fast and convenient. Set breakpoints and debug directly in QtCreator. The widget should just be the 'envelope' calling methods of your MyDrawingClass
when you gave your widget then you can of course directly debug the widget.
1) Configure C:\\Siemens\\Automation\\WinCC_OA\\3.15\\bin\\Wccoaui.exe as the executable
2) Add command line options '-proj MYPROJECT -m gedi -p MyWidgetTestPanel.pnl'
3) Now a 'new' Gedi is started everytime you start to debug the widget. When you stop the widget (from your editor) it will also stop the UI
Hope this helps
share the fun
Frenk Mulder
Some years ago I developed the Gis viewer as an ActiveX. (because I had no knowledge of Qt). I was then asked to port it. What I did was:
1) use QtCreator to start a standalone application where you implement the graphics of your 'shape'. Lets say that your class doing the actual drawing is called 'MyDrawingClass'
2) Then start a widget using the WinCC Oa Api. Include the source files of CMyDrawingClass
You now have a standalone application that allows you to develop fast and convenient. Set breakpoints and debug directly in QtCreator. The widget should just be the 'envelope' calling methods of your MyDrawingClass
when you gave your widget then you can of course directly debug the widget.
1) Configure C:\\Siemens\\Automation\\WinCC_OA\\3.15\\bin\\Wccoaui.exe as the executable
2) Add command line options '-proj MYPROJECT -m gedi -p MyWidgetTestPanel.pnl'
3) Now a 'new' Gedi is started everytime you start to debug the widget. When you stop the widget (from your editor) it will also stop the UI
Hope this helps
share the fun
Frenk Mulder
- imyrvold
- Posts:1
- Joined: Wed May 29, 2019 10:29 am
Re: Test an EWO without starting an UI
This sounds interesting. But I have understood the documentation that you need to create a dll, and rename it to the .ewo extension, to be able to use it in a WinCC OA panel. How do you get that from a standalone Qt application?
- adaneau
- Posts:310
- Joined: Tue Feb 21, 2012 9:49 am
Re: Test an EWO without starting an UI
Hi,
Actually you shouldnt use a full application but just the widget you need. As explained by Frenk above, create your object independantly from WinCC OA template and then either include it in usual main from qt or inside template. Main is for testing, template is for using in WinCC OA. This is really straightforward. If you need more I can send you a small example.
BR
Alexandre
Actually you shouldnt use a full application but just the widget you need. As explained by Frenk above, create your object independantly from WinCC OA template and then either include it in usual main from qt or inside template. Main is for testing, template is for using in WinCC OA. This is really straightforward. If you need more I can send you a small example.
BR
Alexandre