Greetings!
I’ve got some problems with implementing *.ewo-file. Whenever I try to add test EWO (example included in WinCC OA), I’ve take that error:
Module: Gedi_1
Panel: C:\\WORK\\SomeProj\\SomeProj\\panels\\objects\\SomePanel.pnl []
Object: 0 named: "" of type: TestEWO_ewo
, Could not load ExternalWidgetObject "widgets/TestEWO.ewo"
WCCOAui1:VarAttrElem "pixmap" isAttribute(): type not implemented:QVARIANT_VAR
WCCOAui1:VarAttrElem "pixmap" isAttribute(): type not implemented:QVARIANT_VAR
e.t.c... (summary repeated 9 times)
I use WinCC OA 3.13; QT 5.3.2 (qmake.exe NewEWO.pro -r -spec win32-msvs2013; jom.exe -> nmake.exe); Visual Studio 2013.
In QT compiler is MV C++ Compiler 12.0 (amd64), qmake (path: ...\\QT\\Qt5.3.2.2\\5.3\\msvc2013_64\\bin\\qmake), cmake (path ...\\VS2013\\VS\\bin\\nmake.exe)
Compiled without error. I’ve copy my TestEWO.dll (48 kb) from Release folder and rename it to TestEWO.ewo then I’m trying add it into my panel and get that error.
How could I fix it?
EWO implementation problem
- mkoller
- Posts:741
- Joined: Fri Sep 17, 2010 9:03 am
Re: EWO implementation problem
Into which folder did you copy the TestEWO.ewo file ? It should be in your project/bin/widgets
Is there any error message immediately BEFORE the "Could not load..." message ?
(The VarAttrElem "pixmap" messages are not related to not being able to load the ewo)
Is there any error message immediately BEFORE the "Could not load..." message ?
(The VarAttrElem "pixmap" messages are not related to not being able to load the ewo)
- AGorbatykh
- Posts:59
- Joined: Thu Dec 17, 2015 1:01 pm
Re: EWO implementation problem
I copy it into project/bin. But path project/bin/widget neither helps me.Into which folder did you copy the TestEWO.ewo file ? It should be in your project/bin/widgets
Just this few lines:Is there any error message immediately BEFORE the "Could not load..." message ?
Code: Select all
WCCOAui (1), 2016.04.13 11:11:35.872, SYS, WARNING, 16/uim,
Module: Gedi_1
Panel: C:\\WORK\\Some1\\Some1\\panels\\objects\\TestPanel.pnl []
Object: 0 named: "" of type: NewEWO_ewoStrange. So I can attach whole log-file from opening project (EWO_log.txt in attach file). And here is log from opening Using Interface (gedi):(The VarAttrElem "pixmap" messages are not related to not being able to load the ewo)
Code: Select all
WCCILpmon (1), 2016.04.13 11:37:13.153, SYS, INFO, 24/pmon, Got START command from ::1, starting the manager WCCOAui(1) at index 12
WCCILpmon (1), 2016.04.13 11:37:13.157, SYS, INFO, 1, Manager Start, C:\\Siemens\\Automation\\WinCC_OA\\3.13\\bin\\WCCOAui.exe -PROJ Some1 -pmonIndex 12 -m gedi
WCCOAui (0), 2016.04.13 11:37:13.362, SYS, INFO, 1, Manager Start, PROJ, Some1, V 3.13 - 3.13 platform Windows AMD64 linked at Jul 22 2015 21:25:40
WCCOAui (0), 2016.04.13 11:37:14.607, SYS, INFO, 3, Trying to connect to (SYS: 0 Data -num 0 CONN: 1) @ localhost:4897
WCCOAui (0), 2016.04.13 11:37:14.613, SYS, INFO, 4, Connected to (SYS: 0 Data -num 0 CONN: 1) @ WIN-3CJV1OF4OCT (::1)
WCCILdata (0), 2016.04.13 11:37:14.645, SYS, INFO, 4, Connected to (SYS: 1 Ui -num 1 CONN: 1) @ WIN-3CJV1OF4OCT (::1)
WCCILdata (0), 2016.04.13 11:37:14.650, SYS, INFO, 0, , Manager (SYS: 1 Ui -num 1 CONN: 1) initialised
WCCOAui (1), 2016.04.13 11:37:14.651, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAui (1), 2016.04.13 11:37:14.653, SYS, INFO, 3, Trying to connect to (SYS: 1 Event -num 0 CONN: 1) @ localhost:4998
WCCOAui (1), 2016.04.13 11:37:14.655, SYS, INFO, 4, Connected to (SYS: 1 Event -num 0 CONN: 1) @ WIN-3CJV1OF4OCT (::1)
WCCILevent (0), 2016.04.13 11:37:14.691, SYS, INFO, 4, Connected to (SYS: 1 Ui -num 1 CONN: 1) @ WIN-3CJV1OF4OCT (::1)
WCCOAui (1), 2016.04.13 11:37:14.695, SYS, INFO, 102, Waiting for user names/passwords
WCCOAui (1), 2016.04.13 11:37:14.709, SYS, INFO, 103, User names/passwords initialized
WCCOAui (1), 2016.04.13 11:37:26.942, SYS, WARNING, 16/uim,
Module: Gedi_1
Panel: C:\\WORK\\Some1\\Some1\\panels\\objects\\TestPanel.pnl []
Object: 0 named: "" of type: NewEWO_ewo
, Could not load ExternalWidgetObject "widgets/NewEWO.ewo"
WCCOAui1:VarAttrElem "pixmap" isAttribute(): type not implemented:QVARIANT_VAR
WCCOAui1:VarAttrElem "pixmap" isAttribute(): type not implemented:QVARIANT_VAR
WCCOAui1:VarAttrElem "pixmap" isAttribute(): type not implemented:QVARIANT_VAR
WCCOAui1:VarAttrElem "pixmap" isAttribute(): type not implemented:QVARIANT_VAR
WCCOAui1:VarAttrElem "pixmap" isAttribute(): type not implemented:QVARIANT_VAR
WCCOAui1:VarAttrElem "pixmap" isAttribute(): type not implemented:QVARIANT_VAR
WCCOAui1:VarAttrElem "pixmap" isAttribute(): type not implemented:QVARIANT_VAR
WCCOAui1:VarAttrElem "pixmap" isAttribute(): type not implemented:QVARIANT_VAR
WCCOAui1:VarAttrElem "pixmap" isAttribute(): type not implemented:QVARIANT_VARP.S.: I'm using Qt Createor 3.2.1 (opensource) based on Qt 5.3.2 (MSVC 2010, 32 bit). But all compilers and e.t.c. are x64 bit.
By the way I create fake-file (create new *.txt) and renamed it to *.ewo and I got same errors excluding the number of it lines.
https://www.winccoa.com/fileadmin/image ... WO_log.txt
- Attachments
-
- EWO_log.txt
- (22.89 KiB) Downloaded 230 times
- agruber
- Posts:147
- Joined: Tue Sep 07, 2010 2:52 pm
Re: EWO implementation problem
Hi,
The logs give no clue about the reason, you can always take a look at known to work sources like here:
Video Player EWO
The team of the product support can be reached via the following link:
http://www.siemens.com/industry/supportrequest
BR,
Andreas Gruber
The logs give no clue about the reason, you can always take a look at known to work sources like here:
Video Player EWO
The team of the product support can be reached via the following link:
http://www.siemens.com/industry/supportrequest
BR,
Andreas Gruber
- AGorbatykh
- Posts:59
- Joined: Thu Dec 17, 2015 1:01 pm
Re: EWO implementation problem
Thanks, Martin, you were right. The problem is in *.ewo path. I have tested with .../project/bin and .../project/bin/widget, but it must be in a .../project/bin/widgets/windows (or windows-64).
- AGorbatykh
- Posts:59
- Joined: Thu Dec 17, 2015 1:01 pm
Re: EWO implementation problem
By the way, if any wants create own EWO which include another DLL, you must copy that *.dll to ".../Siemens/Automation/WinCC_OA/****/bin/" not at ".../project/bin/" as it seems
- mkoller
- Posts:741
- Joined: Fri Sep 17, 2010 9:03 am
Re: EWO implementation problem
That is correct. The reason is, the operating system searches for the other libs, but does not know where the other library is located. So it uses the PATH env to look for it. But PATH does not contain your project path.
Note that in addition when you want to use this EWO on a client PC with the Webclient that you have to install that library beforehand, also in the install/bin path, since the Webclient does not know about the other libs and can not download it.
The simplest way to use external libs in an EWO is to statically link the lib, if possible. Then there is no need for the additional installation of the external lib.
Note that in addition when you want to use this EWO on a client PC with the Webclient that you have to install that library beforehand, also in the install/bin path, since the Webclient does not know about the other libs and can not download it.
The simplest way to use external libs in an EWO is to statically link the lib, if possible. Then there is no need for the additional installation of the external lib.