UniInt End User
filepath/exename_hostname_pointsource_id_ptcache.dat
Download 1.93 Mb.
|
PI BASemAPI
| filepath/exename_hostname_pointsource_id_ptcache.dat
Likewise, the digital cache file will have the form filepath/exename_hostname_pointsource_id_dgcache.dat For example, if the file path to the executable is “C:\Program Files\PIPC\Interfaces\Test”, with an executable name of “Test”, host name of “FreeBird”, point source of “abc”, and an id of “1”, the point cache and digital cache files created in the directory indicated by the path to the executable would have the following name: c:/program files/pipc/interfaces/test/test_freebird_abc_1_ptcache.dat c:/program files/pipc/interfaces/test/test_freebird_abc_1_dgcache.dat Part of the creation process includes storing Interface and PI Server versioning information in the each of the files to be used in the validation process. Therefore, a connection to the PI Server must be available during the initial creation process for the disconnected startup operation to be configured. Note: If either of the caching files fails to be created, an error message will be logged to the pipc.log file and the interface will fail to start. ValidationCAUTION: Users must not modify the caching files created by the interface. User modification of either of the caching files has the potential of invalidating the file and inducing a data loss situation. If a file has been modified by the user, it should be deleted to allow the interface to create valid files necessary for the Disconnected Startup configuration. Newly created files will require a connection to the PI Server to start the interface. An interface starting in the disconnected startup configuration requires the caching files be validated to determine their usability. The validation process ensures the point and digital set cache files are designated for a particular instance of the interface and the files are capable of receiving new data. If the cache files are validated, the process will then provide the interface with the stored PI Server versioning information necessary to start the interface. Finally, the validation process determines if the cache file has stored all point information needed to start the interface without a connection to the PI Server. If the validation process determines the cache file is not complete, the interface will wait for a connection to the PI Server to become available. The PI server connection is needed to finish initializing the necessary cache files. The status of the validation process is logged in the pipc.log file. A file which cannot be validated will be renamed and a new file will be created as described in the “Creation” section. Renamed files will contain an inserted numerical date‑time change string in the filename. If either of the point or digital set cache files cannot be found, the necessary file(s) will be created as previously described. The “Messages” section of this document contains a listing of typical messages, which includes the renaming of an invalid file, sent to the pipc.log file during the validation mode. Download 1.93 Mb. Share with your friends:
|