CPC CMW

CMW WinCC OA client address format

In WinCC OA UNICOS requires following format for CMW client dpe:  TYPE|TRANSFORMATION_TYPE|POLL_GROUP|ADDRESS_CONFIG|FILTER_NAME|FILTER_VALUE|LLC

TYPE:
  2 - DPATTR_ADDR_MODE_INPUT_SPONT - default (TODO: ?) mode
  3 - DPATTR_ADDR_MODE_INPUT_SQUERY -
  4 - DPATTR_ADDR_MODE_INPUT_POLL - requires poll group
  5 - DPATTR_ADDR_MODE_OUTPUT_SINGLE - output (not used in cpc!) TODO: set up an example

TRANSFORMATION_TYPE
  should be the one that's used for published data in cmw server

DPE type Data Size CMW type Data Size
Data types matching
char 1 char 1
uint 4 long 4
int 4 long 4
float 8 double 8
bool 1b bool 1
string - string -

 

  Data types encoding:        
Data types encoding
CMW_LONGLONG_TYPE 1002
CMW_LONG_TYPE 1003
CMW_SHORT_TYPE 1004
CMW_DOUBLE_TYPE 1005
CMW_FLOAT_TYPE 1006
CMW_BOOL_TYPE 1007
CMW_STRING_TYPE 1008
CMW_CHAR_TYPE 1009

 POLL_GROUP - format: [group_name,polling_interval]

    make sence only for DPATTR_ADDR_MODE_INPUT_POLL

    TODO: should it be per property or per device? or per project?

FILTER_NAME|FILTER_VALUE

    TODO: where's documentation?
    In FESA server (but not in PVSS CMW server) it is possible to hold several values per Server$Device$Property$Value.
    The values in this case are marked with keys (FILTER_VALUE) in different namespaces (FILTER_NAME)
    TODO: what is the usecase?

 LLC

    if true than timestamp would be changed only if new data is changed from old one
    makes sence only for DPATTR_ADDR_MODE_INPUT_SPONT
    TODO: what's recommended mode? compare to PLC?

You are here