1 / 4

Application requirements of Manufacturing System

Application requirements of Manufacturing System. ITC Nse-bu Munaka and Ono Updated on 2008/01/11. Application Requirements. 15-08-0043-00-004e. Latency

lakeesha
Download Presentation

Application requirements of Manufacturing System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Application requirements of Manufacturing System ITC Nse-bu Munaka and Ono Updated on 2008/01/11

  2. Application Requirements 15-08-0043-00-004e • Latency • It is required for the network system to provide a certain mechanism or formula which enables a system designer to know accurately the maximum latency according to the system parameters, such as the number of slaves and the data size. • For example, under some network layer protocols for manufacturing system networks, latency is dominated by the number of slaves and the data size. • Latency : time required to notify an change of data in a slave to the master. • Reproducibility of the failure • To detect the failure, reproducibility is indispensable for the highly reliable system. • Failure detection and localization • Being able to know the current status of all slaves • Could be distinguished “active” and “non-active”. • Be able to accumulate error logs in a master • Slaves do not have a resource accumulating logs • There is not only a memory but a CPU on slaves. • It can not add some commands for failure detection into the system because it declines the performance. • We should add some data into the MAC frame for the failure detection. • Auto configuration support • Slaves can join the system any time. • Latency should be kept even if some slaves join the system.

  3. Precondition (restriction) • Slaves • There are many types of slaves. Their resource constraint such as CPU, memory and other resources are varied. • Software architecture • Programs running on the master may check the data mapped on the shared memory space periodically.

  4. Appendix. Example of a field network system Example of a field network system configuration Field network terminator master slave slave slave How it works 1. Master sends a polling frame to slaves sequentially. The order is defined in advance. 2. Each slave replies its own data frame to the master. Time schedule interval Polling Polling Polling Polling Polling Polling Master t Reply Reply Reply Reply Reply Reply slave Link scan time = delay time (or latency)

More Related