Driver allocation of _address config through CTRL

[giorgiob]

Hi all,

I need to set the _address config of a datapoint through a CTRL script with dpSet function.

It works properly, but when I open the datapoint from PARA I see that Driver Number = 1, while I want to allocate it to Driver Number 2.

When I create the _address config with PARA and set Driver Number 2, I can see that a _distrib config is created too.

Exporting _adderss and _distrib created from PARA with Ascii Manager, it results:

# DistributionInfo
Manager/User ElementName TypeName _distrib.._type _distrib.._driver
UI (1)/0 AQL_AI1.VALORE AQL_AI 56 \\2

# PeriphAddrMain
Manager/User ElementName TypeName _address.._type _address.._reference _address.._poll_group _address.._connection _address.._offset _address.._subindex _address.._direction _address.._internal _address.._lowlevel _address.._active _address.._start _address.._interval _address.._reply _address.._datatype _address.._drv_ident
UI (1)/0 AQL_AI1.VALORE AQL_AI 16 "36.0.1.0.0.6" 0 0 \\2 0 0 1 01.01.1970 00:00:00.000 01.01.1970 00:00:00.000 01.01.1970 00:00:00.000 526 "IEC"

So do I need to set also a _distrib config through CTRL script?
I tried this:

dpSetWait(dpname + ":_distrib.._type", DPCONFIG_DISTRIBUTION_INFO, dpname + ":_distrib.._driver", '\\2');

but it doesn't work.
Can you help me?
Thanks.

PS: my WinCC-OA version is 3.14 patch 22.

[leoknipp]

In my scripts I have defined the value for _distrib.._driver as integer, e.g. dpname + ":_distrib.._driver", 2)
Can you please check if it works then.

Best Regards
Leopold Knipp
Senior Support Specialist

[giorgiob]

Thank you Leopold for your support.

I already tried the way you wrote, but it doesn't work.

I call dpSet for _distrib config after the one for _address config: the _address config disappears and the _distrib config, from PARA, looklikes empty, even if exporting it results correct:

It seems it doesn't find driver number 2, but I can see it running in my console.

[leoknipp]

You have to configure the _distrib config before the configuration for the _address config is made.
The driver/simulation driver with number 2 must be started to be able to configure addresses for this driver.

Best Regards
Leopold Knipp
Senior Support Specialist

[giorgiob]

Thank you Leopold... now it works!!!