Pi bailey Sem api interface Manual
Download 2.52 Mb.
|
PI BASemAPI, UniInt Interface User Manual
- Navigate this page:
- Stopping Interface Running as a Service
- Buffering
| blysem.exe –start
To start the interface service with PI ICU, use the button on the PI ICU toolbar. A message will inform the user of the the status of the interface service. Even if the message indicates that the service has started successfully, double check through the Services control panel applet. Services may terminate immediately after startup for a variety of reasons, and one typical reason is that the service is not able to find the command-line parameters in the associated .bat file. Verify that the root name of the .bat file and the .exe file are the same, and that the .bat file and the .exe file are in the same directory. Further troubleshooting of services might require consulting the pipc.log file, Windows Event Viewer, or other sources of log messages. See the section “Appendix A: Error and Informational Messages,” for additional information. Stopping Interface Running as a ServiceIf the interface was installed a service, it can be stopped at any time from PI ICU, the services control panel or with the command: blysem.exe –stop The service can be removed by: blysem.exe –remove To stop the interface service with PI ICU, use the button on the PI ICU toolbar. This section describes starting and stopping the interface once it has been installed as a service. See the UniInt Interface User Manual to run the interface interactively. BufferingFor complete information on buffering, please refer to the PI API Installation Instruction. PI Interface Node buffering consists of a buffering process which runs continuously on the local node, a PI API library whose calls can send data to this buffering process, and a utility program for examining the state of buffering and controlling the buffering process. Note: Change the Local Security Policy on Windows XP. 1. Open “Administrative Tools” from the control panel. 2. Open “Local Security Policy” from administrative tools. 3. Browse to “Security Options” under “Local Policies.” 4. Double click on “System Objects: Default owner for objects created by members of the Administrators group.” 5. Change the dropdown from “Object Creator” to “Administrators group.” The behavior of Bufserv should now be the same on Windows XP as it was for Windows and 2000. Download 2.52 Mb. Share with your friends:
|