Hi,
I have a problem with an Single Point Signal (SPI, M_SP_TB_1) which was sent as a Double Point signal (DPI, M_DP_TB_1) incorrectly.
The address in WinCC OA is a SPI-address (30.0.35.9.43.173)!
The IEC-driver in PVSS 3.1 accepted this (wrong) telegram. Not the driver of WinCC OA version 3.12
The log of the wrong telegram - aceptet only by PVSS 3.1
WCCOAiec2: Buffer: 68 15 e2 0 4 0 1f 1 3 0 23 0 ad 2b 9 1 ca c7 1c 88 4 6 f
WCCOAiec2:WCCOAiec (2), 2015.06.04 08:28:51.204, WORK, IecPr104ConnItem::quitSendItem() for: "IEC_35_2" number 2
WCCOAiec2:OrgTime: Thu Jun 04 08:28:51 2015 092
WCCOAiec2:IecHWService::notifyData called for "IEC_35_2-31.0.35.9.43.173"
WCCOAiec2:Index: 37 S: IecState_Running E: IecEvent_I_Data A: IecAction_I_Data N: IecState_Running
The log of the correct telegram - accepted by both; PVSS 3.1 and WinCC OA 3.12
WCCOAiec2: Buffer: 68 15 d0 3 14 0 1e 1 3 0 23 0 ad 2b 9 1 4c 9e 2b 88 4 6 f
WCCOAiec2:WCCOAiec (2), 2015.06.04 08:43:43.120, WORK, IecPr104ConnItem::quitSendItem() for: "IEC_35_2" number a
WCCOAiec2:OrgTime: Thu Jun 04 08:43:40 2015 20c
WCCOAiec2:IecHWService::notifyData called for "IEC_35_2-30.0.35.9.43.173"
WCCOAiec2:WCCOAiec (2), 2015.06.04 08:43:43.121, WORK, "processData2Dp called: startix = 0; nofElements = 99 at 2015.06.04 08:43:43.121"
WCCOAiec2:WCCOAiec (2), 2015.06.04 08:43:43.122, WORK, "convert2Ing called for (Type: 215 Sys: 1 Dp: 35021 El: 112 : _address..)"
WCCOAiec2:Index: 37 S: IecState_Running E: IecEvent_I_Data A: IecAction_I_Data N: IecState_Running
WCCOAiec2:WCCOAiec (2), 2015.06.04 08:43:43.123, WORK, Now sending message(s) with 1 items.
Is there any way that the WinCC OA 3.12 driver does exactly as the PVSS 3.1 Driver?
config, datapoint or ... ?
Best regards
Uwe Heinrich
Department ELBAS, Section Studies and Development
SIGNON Germany GmbH, Dresden