What has to be considered before doing an ASCII import / export?

  • The ASCII manager exports the database of the current project (the last project in the proj_path list of the project). Therefore, the ASCII output should be executed on the machine where the data and event managers are running.
     
  • An ASCII- export can only be realized when the data-manager is running in multi-use mode. On startup of a WinCC OA project the data-manager is first started in single user mode. The mode is switched to multi-user automatically as soon as the DataBG is started. If an ASCII export is started during this single user phase, the database cannot be opened. In this case, an error message is shown saying that a WinCC OA project is just starting and an ASCII export cannot be realized.
     
  • When importing an ASCII file with driver configs (_address/_distrib-configs), the driver (or a SIM) must run with the number specified by the distributor config otherwise the configs may not be imported and stored in the database.
     
  • When impoting ASCII file with alarm-configs, the command line option -inactivateAlert resp. the option "Input data with alarm handling" in the ASCII-manager panel must be activated. After completing the input, the setting of the attribute _active in the input file determines whether the alert handling is activated again (when the value is 1) or remains deactivated (when the value is 0).
     
  • When importing ASCII file with original values of datapoints having activated driver ouput address-configs, then these values will be sent again from the driver to the periphical devices. To avoid this the config-entry "ignoreManager" may be used to make the driver ignores the hotlinks of value changes from the ascii-manager.
     
  • the maximum length of characters in a string value to be imported via the ASCII import is limited to 1 MB.
     
  • a delay of few seconds between an ASCII ouput and an ASCII input should be respected, when executing this from a control-script.
  • Changing configs with the ASCII-Manager is only possible, when during the ASCII-import these configs are not locked in the database. Locking a config is possible via control script or is done automatically when opeining the associated config-panel in the PARA-module.
  • In a redundant project, imported data from an ASCII-manager that is connected only to the passive-Event-manager are ignored.
  • the ASCII-manager option -in, -out and -get may not be combined in one command line.
  • When you use the ASCII manager, Kerberos and SSO, enter the user by using the manager option and the dollar parameter user: PVSS00ascii -user $USER. $USER will be replaced by the current OS user.

    Further information about the ASCII-manager are available in the WinCC OA OnlineHelp, in chapter "ASCII Manager".
     

 

Date added:
Last revised:
Hits:
12.173
Version:
3.8, 3.9, 3.10, 3.11, ALL Versions
Platform:
Windows,Linux,Solaris
Rating:
  • Current rating is 3.2 out of 5
Rating: 3.2. 61 vote(s).
61 anonymous votes No rating done at all.
Your vote was '' (0 of 5) You are an anonymous user.
You may log on to do personalized votings
 Click the rating bar to rate this item Please log on to do ratings

  • Notification

    FE user cannot be identified! (1403201096)

Tags:
Engineering, Installation / Configuration, PVSS, WinCC Open Architecture
 go back