Download CIMPLICITY HMI Tracking Operation Manual
Transcript
Application Subroutines The following application subroutines are available for your use. prt_api_init - Initialize The PRT_API Interface Name: prt_api_init Description: The PRT_API initialization routine is responsible for initializing the interface between an application process and the PRT_API utilities. prt_api_init must be called by an application before any other PRT_API functions. If an application process wishes to be an interested process to PRT it must instead call one of the PRT interested process initialization routines prt_api_register_intproc or prt_api_register_dyn_intproc. If an application process wants to access the standard PRT_API routines as well as sign up as an interested PRT process it must call both PRT_API initialization routines. Syntax: int prt_api_init (event_flag, rcv_req_flag, prt_system, cimp_sys, retstat) COR_U4 event_flag; COR_BOOLEAN rcv_req_flag; Char *prt_system; Char *cimp_sys; COR_STATUS *retstat; Data Structures: None Input Arguments: event_flag Message receipt event flag; not used if rcv_req_flag is FALSE rcv_req_flag Receive requests flag; if TRUE, this indicates the application will receive requests from PRT Data Collector processes for item tracking data and serialized item hold information. prt_system Name of the PRT data server to connect to. This parameter allows you to connect to different Production Tracking systems with the same API. You may also specify the prefix of all the data servers you wish to connect to. This allows the API to connect to multiple servers. cimp_sys Name of the project or node where the PRT data collector(s) reside. Output Arguments: *retstat GFK-1216F Pointer to COR_STATUS structure Production Tracking Application Interface 5-3