{"title":"在Fuber IEC 61499运行时环境中使用的执行模型的定义","authors":"G. Cengic, K. Åkesson","doi":"10.1109/INDIN.2008.4618113","DOIUrl":null,"url":null,"abstract":"The buffered sequential execution model (BSENI) for IEC 61499 function block applications is presented. Before the execution of the application the composite function blocks are flattened. The resulting application containing the basic and service interface function blocks is executed. The basic function blocks are put in the ready queue in the same order that they receive the input events, hence the word ldquosequentialrdquo in the name. Each basic function block keeps a queue of incoming events with their associated data, hence the word ldquobufferedrdquo in the name. Scheduling policy of the blocks is in the scheduling function while the execution policy of the received events is in the function block instance. The extended finite automata models suitable for formal verification of the proposed execution modelpsilas behavior are presented. The model may be analyzed using a discrete event systems tool called Supremica. The presented execution model is implemented in the Fuber runtime environment.","PeriodicalId":112553,"journal":{"name":"2008 6th IEEE International Conference on Industrial Informatics","volume":"75 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2008-07-13","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"15","resultStr":"{\"title\":\"Definition of the execution model used in the Fuber IEC 61499 runtime environment\",\"authors\":\"G. Cengic, K. Åkesson\",\"doi\":\"10.1109/INDIN.2008.4618113\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The buffered sequential execution model (BSENI) for IEC 61499 function block applications is presented. Before the execution of the application the composite function blocks are flattened. The resulting application containing the basic and service interface function blocks is executed. The basic function blocks are put in the ready queue in the same order that they receive the input events, hence the word ldquosequentialrdquo in the name. Each basic function block keeps a queue of incoming events with their associated data, hence the word ldquobufferedrdquo in the name. Scheduling policy of the blocks is in the scheduling function while the execution policy of the received events is in the function block instance. The extended finite automata models suitable for formal verification of the proposed execution modelpsilas behavior are presented. The model may be analyzed using a discrete event systems tool called Supremica. The presented execution model is implemented in the Fuber runtime environment.\",\"PeriodicalId\":112553,\"journal\":{\"name\":\"2008 6th IEEE International Conference on Industrial Informatics\",\"volume\":\"75 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2008-07-13\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"15\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2008 6th IEEE International Conference on Industrial Informatics\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/INDIN.2008.4618113\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2008 6th IEEE International Conference on Industrial Informatics","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/INDIN.2008.4618113","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Definition of the execution model used in the Fuber IEC 61499 runtime environment
The buffered sequential execution model (BSENI) for IEC 61499 function block applications is presented. Before the execution of the application the composite function blocks are flattened. The resulting application containing the basic and service interface function blocks is executed. The basic function blocks are put in the ready queue in the same order that they receive the input events, hence the word ldquosequentialrdquo in the name. Each basic function block keeps a queue of incoming events with their associated data, hence the word ldquobufferedrdquo in the name. Scheduling policy of the blocks is in the scheduling function while the execution policy of the received events is in the function block instance. The extended finite automata models suitable for formal verification of the proposed execution modelpsilas behavior are presented. The model may be analyzed using a discrete event systems tool called Supremica. The presented execution model is implemented in the Fuber runtime environment.