PTMAP provides the application interface to point data. Its function library provides the following services:
Manage Local Point Data |
Each point to be accessed by an application must be added to a local store of point data. |
Specify Requests |
Once a point is added to the local store, the application may make requests for that point data. For example, the application may request receipt of a point's data value every time the value changes. |
Group Requests |
Requests may be organized into Shopping Lists. A Shopping List represents a group of requests that the application makes at one time. The application can organize its requests in any number of Shopping Lists. |
Send Requests |
Once requests have been specified and grouped together, the application transmits that information to a PTMRP. The actual sending of the requests is handled by PTMAP. |
Wait for Responses |
After requests have been made, the application may wait for responses to be returned. The application may choose to wait for single responses to be returned or for complete sets of responses. |
Receive Responses |
Once responses have been received by PTMAP, the application is notified (either by explicitly waiting or by testing an event flag) that responses are available. The application may then access each response and the data that has been returned. |
Relative efficiency of Point Management requests. |
|
On-alarm requests. |
|
PTMAP error handling. |
|
Initialize and terminate PTMAP services. |
|
Manage local point data. |
|
Manage shopping lists. |
|
Modify request. |
|
Suspend and resume receipt of responses. |
|
Enable/disable requests. |
|
Cancel requests. |
|
Send requests to Point Management. |
|
Wait for Point Management responses. |
|
Get Point Management responses. |
|
Access point cinfiguration data. |
|
Point Management API subroutines. |
|
Point Management API general subroutines. |
|
About Point Management API. |