首页>
外国专利>
Running method of SECS driver for SECS message exchanging between equipement server part and interface part
Running method of SECS driver for SECS message exchanging between equipement server part and interface part
展开▼
机译:设备服务器部分和接口部分之间进行SECS消息交换的SECS驱动程序的运行方法
展开▼
页面导航
摘要
著录项
相似文献
摘要
PURPOSE: A method of driving an automation communication driver for exchange of message between an equipment server and an interface for process automation is provided which changes a property value while a process proceeds when the property value is required to be varied due to a processor error to allow the process to be performed without having a time delay. CONSTITUTION: An operator forms library data(D101) and loads the library file(D102). Transaction data is loaded according to a virtual scenario(D103), and it is judged if primary data is transmitted or not(D104). The primary data is sent to an automation communication driver(D105) when the data is required to be transmitted, and it is judged if the primary data is received or not(D106) when the data is not required to be sent. When the primary data is required to be received, the automation communication driver transmits the primary data through an application program with reference to the library file(D107). The primary data is received from the driver according to the data transmission(D108). When there is no need to receive the primary data, it is judged if secondary data is transmitted or not(D109). The secondary data is transmitted to the driver(D110) when the data is required to be transmitted, and the driver transmits the secondary through the application program with reference to the library file(D111) when the data is not needed to be transmitted. The driver receives the secondary data(D112). The accuracy of a response message is judged(D113). When the proper response message was not received, message data is corrected(D114). It is judged if the library data is required to be corrected(D115). When the proper response message was received, it is judged if the virtual scenario has been completed(D116). When the virtual scenario has not been completed, the next transaction data on the virtual scenario is read(D117).
展开▼