Hello,
I met next situatuion with export from ASCII Manager.
At first I added to _AlertClass some new DP and then made export via ASCII the _AlertClass with select _AlertClass as DPT.
After that in _AlertClass I deleted several DP among them that was added early and made export via ASCII the again with rewrite existing file.
In my case I see in rewrited file that DP not presents, but configs of deleted DP still included in this file.
For experiment I also made export via ASCII the to the new file and check it. New file havnt incude deleted DP and their configs.
Please check this scenario: export from ASCII Manager after deleted some DP to existing file with rewriting it.
Potential bug with export from ASCII Manager WINCC OA 3.15 P006
- rxs
- Posts:10
- Joined: Fri Sep 01, 2017 1:29 pm
Potential bug with export from ASCII Manager WINCC OA 3.15 P006
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Potential bug with export from ASCII Manager WINCC OA 3.15 P006
I've tested it but I could not reproduce it.
If a datapoint is deleted no config information is included in the ASCII file.
Have you started the ASCII manager directly at the server or on a remote machine?
Please note that the ASCII export only works when it is made at the server as it is reading data directly from the database (file access).
Best Regards
Leopold Knipp
Senior Support Specialist
If a datapoint is deleted no config information is included in the ASCII file.
Have you started the ASCII manager directly at the server or on a remote machine?
Please note that the ASCII export only works when it is made at the server as it is reading data directly from the database (file access).
Best Regards
Leopold Knipp
Senior Support Specialist