Add new datapoint element after ASCII import

[ange.ogawin]

Hi,

I have created a datapoint type and its master datapoint. Inside this datapoint type, i have also created a datapoint element.
This datapoint element contains different peripheral address using a driver with the parameter "driver number: 2".
Next i exported with ASCII manager this datapoint type and all the stuffs i created.
When i import this file on another computer, i am not able to add new datapoint element with my datapoint type imported.

How to fix this problem?

Precisions:
-I have already set up the project on the another PC with the driver launched with -num 2 in the console manager and the appropriate panels.
-The problem doesn't appear when i launch two instances of driver, with -num 1 and -num 2.
-The driver is working perfectly.

Thank you.

[leoknipp]

Please always use the correct naming for the data structures in WinCC OA.
The structure of nodes and elements is defined with a datapoint type. For a datapoint type you can create datapoints. A datapoint can consist of 1-n datapoint elements (defined by the datapoint type).
If the ASCII import does not work you should get an error. Please check the logfiles if an error was written during the import.

Best Regards
Leopold Knipp
Senior Support Specialist

[ange.ogawin]

Ok, so the question is rather how to add a new datapoint?
I got the following error(see attachment).
It shows that WinCC is trying to connect to driver -num 1 while the master datapoint use -num 2 for all drivers num of datapoints elements(in the peripheral addresses).

[leoknipp]

The log messages describe that the driver related configs cannot be added.
Even if the log message occurs the datapoint should be created.

Please start a driver/simulation driver with number 1 to avoid the problems when configuring driver related configs and check afterwards if it works.

Best Regards
Leopold Knipp
Senior Support Specialist

[ange.ogawin]

Yes, like i said, it's working when i start a driver with number 1. But i was thinking that it's not a normal behaviour.
But if it's the right way to do, i will proceed like that.

Thank you.

[leoknipp]

The log messages are written when the function defined in mp.ctl reads the configs defined at _mp_C200 in your case.
In the screenshots we cannot see if a _distrib-config is existing at _mp_C200 which refers to driver number 2.
Normally if the Event Manager knows that the dp element refers to driver 2 the dpGet() calls are send to driver number 2 and the log messages will not appear.

Best Regards
Leopold Knipp
Senior Support Specialist