【導讀】在下面的安裝過程中，假定接口程序的名字為，并且啟動腳本文件為。如果實際接口名為“Random”，那么在后面的安裝過程中必須用Random代替上述的ifc。比如，用戶可能分別用和接口程序1,和。代表接口程序2，依次類推。如果一個接口程序作為服務運行，可執(zhí)行程序及啟。PIHOME目錄樹在文件的PIHOME鍵值里已經配置。ASCII文本文件，在系統(tǒng)WinNT目錄下。典型的包含以下幾行：。上述的第二行定義PIHOME為C:drive.OSI推薦使用\pipc作為根目錄。如果遵循上面的命名規(guī)則，建議把ifc1,ifc2,ifc3,分別放在下面的目錄中：。安裝程序會為你創(chuàng)建這些目錄，并為你更改和文件名。有些附件程序DLL來對特定的一些應用程序進行后處理。

　　

【正文】 me and port rem /MA=Y Should we try to add tags in large batches rather than singly ? rem /ts=a Where do we get timestamps ? (Y/N/A/U) rem /stopstat Should we write a status to PI tags when the OPC server goes away ? rem /f=00:00:01 scan classes. The first one is for Read On Change tags... XXXX 發(fā)電有限 責任公司 PI 系統(tǒng)用戶使用手冊資料 第 16 頁 共 20 頁 opcint ^ /ps=B ^ /eC=1 ^ /er=00:00:03 ^ /id=1 ^ /TF=ccyy/mn/dd hh:mm: ^ /SERVER=:: ^ /host=piserver:5450 ^ /MA=Y ^ /ts=Y ^ /VN=1 ^ /opcstopstat ^ /f=00:00:01 ^ /f=00:00:01 ^ /f=00:00:01 ^ /f=00:00:30 9． NCS 網控部分啟動腳本配置 rem rem Startup file for the OPC interface to PI rem The ^ marks are continuation characters, they allow rem you to have a mand be split between multiple lines. rem There must not be ANYTHING after the ^ on each line. rem This is only a sample of the options available, the user rem manual has the list and descriptions for them all. rem rem /ps=O The pointsource this should match the pointsource for your tags rem /ec=10 The event counter number for IORATES XXXX 發(fā)電有限 責任公司 PI 系統(tǒng)用戶使用手冊資料 第 17 頁 共 20 頁 rem /er=00:00:03 The requested update rate for event triggered tags rem /id=1 The identifier string used in the file for messages rem from this interface it must match Location1 on the tags. rem /SERVER= The OPC server name。 format hostname::servername or just rem servername if it39。s local rem /host=mabel:5450 The PI server name and port rem /MA=Y Should we try to add tags in large batches rather than singly ? rem /ts=a Where do we get timestamps ? (Y/N/A/U) rem /stopstat Should we write a status to PI tags when the OPC server goes away ? rem /f=00:00:01 scan classes. The first one is for Read On Change tags... opcint ^ /ps=N ^ /ec=10 ^ /er=00:00:03 ^ /id=1 ^ /TF=ccyy/mn/dd hh:mm: ^ /host=:5450 ^ /server=:: ^ /FT=10 ^ /MA=Y ^ /ts=Y ^ /IS=Y ^ /AF=Y ^ /opcstopstat ^ XXXX 發(fā)電有限 責任公司 PI 系統(tǒng)用戶使用手冊資料 第 18 頁 共 20 頁 /f=00:00:01 ^ /f=00:00:01 ^ /f=00:00:01 ^ /f=00:00:10 ^ 10． 輔機單耗部分啟動腳本配置 rem rem Startup file for the OPC interface to PI rem The ^ marks are continuation characters, they allow rem you to have a mand be split between multiple lines. rem There must not be ANYTHING after the ^ on each line. rem This is only a sample of the options available, the user rem manual has the list and descriptions for them all. rem rem /ps=O The pointsource this should match the pointsource for your tags rem /ec=10 The event counter number for IORATES rem /er=00:00:03 The requested update rate for event triggered tags rem /id=1 The identifier string used in the file for messages rem from this interface it must match Location1 on the tags. rem /SERVER= The OPC server name。 format hostname::servername or just rem servername if it39。s local rem /host=mabel:5450 The PI server name and port rem /MA=Y Should we try to add tags in large batches rather than singly ? rem /ts=a Where do we get timestamps ? (Y/N/A/U) rem /stopstat Should we write a status to PI tags when the OPC server XXXX 發(fā)電有限 責任公司 PI 系統(tǒng)用戶使用手冊資料 第 19 頁 共 20 頁 goes away ? rem /f=00:00:01 scan classes. The first one is for Read On Change tags... opcint ^ /ps=F ^ /ec=2 ^ /er=00:00:03 ^ /id=1 ^ /TF=ccyy/mn/dd hh:mm: ^ /host=:5450 ^ /server=:: ^ /FT=10 ^ /MA=Y ^ /ts=n ^ /VN=2 ^ /opcstopstat ^ /f=00:00:01 ^ /f=00:00:30 ^ /f=00:00:01 ^ /f=00:00:30 ^