2005
DOI: 10.1016/j.csi.2004.05.001
|View full text |Cite
|
Sign up to set email alerts
|

Real-time performance evaluation of urgent aperiodic messages in FF communication and its improvement

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2007
2007
2022
2022

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 10 publications
(2 citation statements)
references
References 13 publications
0
2
0
Order By: Relevance
“…Analyzing, for example, the Modbus specification as well as other non-standard extensions [27], we can argue that only Modbus RTU is suitable for real-time communications. Modbus ASCII allows a maximum of 6 seconds between characters, which is unacceptable for any real-time application [28], and Modbus TCP/IP uses the TCP/IP stack, which is of the best-effort type.…”
Section: Figure 5 the Time Period Between Two Requests Sent By The Cl...mentioning
confidence: 99%
“…Analyzing, for example, the Modbus specification as well as other non-standard extensions [27], we can argue that only Modbus RTU is suitable for real-time communications. Modbus ASCII allows a maximum of 6 seconds between characters, which is unacceptable for any real-time application [28], and Modbus TCP/IP uses the TCP/IP stack, which is of the best-effort type.…”
Section: Figure 5 the Time Period Between Two Requests Sent By The Cl...mentioning
confidence: 99%
“…These function blocks will be executed only after the required inputs are scheduled to be available. To address the case, where a device providing an input becomes unavailable, the user can configure the number of consecutive communications that may be lost before the input status of the receiving device is set to the bad state and consequently the actual mode of the block using this input switches to manual [10,11].…”
Section: Basics Of Fb Implementationmentioning
confidence: 99%