1. Introduction: Industrial Communication Protocols as the Backbone of Modern Automation Systems

The progressive transformation of industrial systems toward highly interconnected, cyber-physical production environments has positioned industrial communication protocols as a foundational technological pillar. Modern automation systems are no longer isolated entities composed of programmable logic controllers (PLCs) and field devices operating independently. Instead, they are complex, distributed ecosystems in which machines, robots, sensors, enterprise software, simulation tools, and cloud-based analytics platforms exchange data continuously and deterministically.

Important it’s to clear some definitions: while ‘Industry 4.0‘ prioritizes digitalization, automation, and interconnectivity to optimize industrial efficiency through Cyber-Physical Systems, ‘Industry 5.0‘ introduces a human-centric paradigm [17]. It emphasizes the synergy between human creativity and robotic precision, integrating sustainability and resilience as core pillars to ensure technology benefits both society and the environment.

Now in the contemporary landscape of Industry 5.0, the manufacturing environment has evolved into a highly integrated ecosystem characterized by the seamless convergence of Information Technology (IT) and Operational Technology (OT) [15]. This ‘interconnectedness’ is driven by the deployment of the Industrial Internet of Things (IIoT), where a diverse array of hardware—ranging from mobile devices like industrial tablets and wearables to high-capacity servers—operates within a unified network. Operators equipped with wearables and mobile interfaces can now access real-time telemetry directly from robotic cell servers, allowing for untethered supervision and immediate intervention on the shop floor.
This bidirectional data flow ensures that information generated by robotic actuators is simultaneously processed by local edge servers and synchronized with office-based management systems. Such a framework facilitates the creation of Cyber-Physical Systems (CPS), where the physical production process is mirrored by a digital twin accessible across all levels of the enterprise hierarchy [16]. By harmonizing mobile human-machine interfaces with centralized server infrastructures, modern plants achieve unprecedented levels of agility, predictive maintenance, and decentralized decision-making, effectively transforming the factory into a responsive, data-driven organism.

Scientific literature consistently identifies industrial communication technologies as one of the key enablers of Industry 4.0, Smart Manufacturing, and Cyber-Physical Production Systems (CPPS) [1]. Standards such as Modbus, EtherCAT, OPC UA, PROFINET, RESTful industrial APIs, and many other protocols provide the technical infrastructure required to ensure interoperability, real-time performance, scalability, and security across heterogeneous industrial assets [2].

From an academic perspective, industrial communication protocols are studied not only as data transmission mechanisms but as integral components of control theory, distributed systems, and industrial informatics [3]. From a practical standpoint, they enable real-world applications such as machine-to-machine (M2M) communication, human–machine interfaces (HMI), supervisory control and data acquisition (SCADA), digital twins, predictive maintenance, and closed-loop optimization.

SD Companies operates at the intersection of these domains, combining deep theoretical understanding with applied engineering expertise to design, integrate, and optimize industrial communication architectures across production plants, robotic cells, sensor networks, and enterprise-level information systems. Its experience culminated in developing a robust Data Hub system that seamlessly integrates diverse machines, legacy systems, and modern software in a complex ecosystem. By bridging varying interconnection capabilities, it enables unified data flow, real-time collaboration, and efficient communication across all components. Contact SD Companies to know more about this efficient solution.

1.1 Scientific Foundations and Authoritative References

The scientific investigation of industrial communication protocols has evolved over several decades. Early fieldbus systems were designed primarily for robustness and simplicity, while modern Ethernet-based and service-oriented architectures emphasize bandwidth, determinism, semantic interoperability, and cybersecurity [4].

Key contributions in the literature analyze protocol performance under real-time constraints, fault tolerance, synchronization accuracy, and interoperability across vendors [5]. OPC Unified Architecture (OPC UA), for example, has been extensively studied for its information modeling capabilities and platform independence [6], while EtherCAT is widely recognized for its ultra-low latency and precise synchronization mechanisms [7].

2. Technical Principles, Algorithms, and Infrastructure of Industrial Protocols

2.1 RESTful APIs and HTTP-Based Industrial Communication

Although originally conceived for web applications, RESTful APIs based on HTTP/HTTPS have become increasingly relevant in industrial automation, particularly for vertical integration between shop-floor systems and enterprise or cloud-level platforms.

From a technical standpoint, RESTful communication relies on a stateless client-server model, resource-oriented addressing (URI), and standardized HTTP methods (GET, POST, PUT, DELETE). In industrial contexts, REST APIs are typically used for:

• Interfacing Manufacturing Execution Systems (MES) with ERP platforms
• Exchanging production and quality data with analytics engines
• Connecting digital twins and simulation environments

RESTful APIs usually operate over Ethernet using TCP/IP, with standard RJ45 connectors and Cat5e/Cat6 cables. Typical transmission distances are up to 100 meters per Ethernet segment, extendable via switches and fiber optics. Bandwidth depends on the Ethernet standard (100 Mbps to multiple Gbps), while latency is non-deterministic, making REST unsuitable for hard real-time control but ideal for supervisory and information-level communication [8].
The adoption of RESTful APIs acts as a critical catalyst for the broader implementation of the Industrial Internet of Things (IIoT) within smart factories. By leveraging these web-standard protocols, industrial assets are no longer isolated entities but become active nodes in a ubiquitous data network. This integration facilitates the seamless exchange of information across heterogeneous architectural layers, bridging the gap between local control and global cloud services.
Consequently, the IIoT framework empowers organizations to harness big data analytics and edge computing, fostering a more agile production environment. According to Boyes et al. [18], the IIoT paradigm fundamentally redefines industrial operations by integrating sensing and processing capabilities through standardized, interoperable communication interfaces.

Practical Notes for Automation Engineering

In practice, REST APIs are not used to control actuators directly. Instead, they act as a bridge between control systems and higher-level software, allowing engineers to expose machine states, alarms, KPIs, and production metrics to external systems in a standardized way.

2.2 Modbus: Legacy Simplicity and Enduring Industrial Relevance

Modbus is one of the oldest and most widely adopted industrial communication protocols [19]. Originally developed for serial communication (Modbus RTU and ASCII), it later evolved into Modbus TCP/IP to leverage Ethernet infrastructure [20]. Developed by Modicon in 1979, Modbus is a foundational messaging protocol that has become a de facto standard in industrial automation. Currently maintained by the Modbus Organization, it is an open-source protocol defined by specifications that ensure interoperability across diverse hardware. Functionally, Modbus operates on a client-server architecture (formerly master-slave), where a client initiates requests to server nodes using unique IDs and function codes. These commands allow the reading and writing of data stored in a simple memory map consisting of 16-bit registers and discrete coils. Practically, it supports both serial communication (RTU/ASCII via RS-485) and Ethernet-based networks (TCP/IP), making it a versatile choice for connecting PLCs with sensors and actuators in SCADA systems.

Modbus follows a master-slave (client-server) architecture, where a master device initiates all communication requests. The protocol operates on a simple register-based data model, making it easy to implement and understand.

Typical physical layers include:

• RS-485 for Modbus RTU (2 or 4 wires, up to 1200 meters)
• Ethernet for Modbus TCP (RJ45 connectors, 100 m per segment)

Data rates vary from a few kbps in serial implementations to 100 Mbps or more in Ethernet-based systems. However, Modbus lacks intrinsic security features and deterministic timing guarantees, which limits its applicability in advanced real-time control scenarios [9].

2.3 EtherCAT: Deterministic Real-Time Ethernet

Introduced by Beckhoff Automation in 2003, EtherCAT (Ethernet for Control Automation Technology) [21] is an open, high-performance industrial Ethernet protocol standardized under IEC 61158 and IEC 61784. Managed by the EtherCAT Technology Group (ETG), its primary innovation lies in the “processing on the fly” mechanism. Unlike traditional Ethernet protocols where each node must receive, decode, and copy data before passing it on, EtherCAT nodes read data addressed to them and insert new data into the frame as it moves through the device at hardware speed. This approach maximizes bandwidth utilization and eliminates the need for complex switches [22].

From a practical standpoint, EtherCAT operates at 100 Mbps using standard Cat5e cabling and RJ45 or M12 connectors. It achieves exceptional real-time performance with cycle times below 100 microseconds and nearly negligible jitter, thanks to its Distributed Clocks (DC) mechanism, which synchronizes nodes with sub-microsecond precision. The infrastructure is highly versatile, supporting diverse topologies—such as line, tree, star, or ring for redundancy—without performance degradation. This makes EtherCAT the gold standard for demanding applications in high-speed motion control and complex robotic cells.. EtherCAT (Ethernet for Control Automation Technology) represents a paradigm shift in industrial communication by enabling hard real-time performance over standard Ethernet hardware. Unlike traditional Ethernet protocols, EtherCAT processes data on-the-fly as frames pass through each node, significantly reducing latency.

EtherCAT typically uses standard Ethernet cables (Cat5e or higher) with RJ45 connectors, although fiber-optic variants exist for long distances and harsh environments. The protocol is extensively analyzed in the literature for motion control, robotics, and high-speed automation [7].

2.4 OPC UA: Semantic Interoperability and Information Modeling

Released in 2008 by the OPC Foundation as the successor to OPC Classic, OPC Unified Architecture (OPC UA) is a platform-independent, service-oriented architecture standardized under IEC 62541 [23]. Unlike its predecessor, which relied on Microsoft’s COM/DCOM technology, OPC UA is designed to operate across diverse operating systems and hardware. Its primary innovation is a sophisticated Information Model that allows devices to exchange not just raw data, but metadata and structural information, creating a semantic self-description of the system [24].

In practice, OPC UA operates on a client-server or publisher-subscriber (Pub/Sub) model. While it typically runs over TCP/IP (using port 4840) with binary encoding for performance, it also supports JSON over WebSockets for cloud integration. Transmission speeds are highly dependent on the underlying infrastructure (typically 100 Mbps to 1 Gbps Ethernet) and the complexity of the address space; however, it is generally optimized for supervisory control and vertical integration rather than high-speed motion control. For those transitioning from protocols like Modbus or EtherCAT, it is crucial to understand that OPC UA is object-oriented: instead of mapping simple 16-bit registers, you will interact with “Nodes” that contain attributes, variables, and methods. A practical first step is to use an OPC UA Client (e.g., UA Expert) to browse the server’s address space, which reveals the hierarchy and data types automatically, eliminating the need for manual register lists [6].

2.4 Many other protocols

The landscape of industrial automation is characterized by an extensive and heterogeneous array of communication protocols, each engineered to address specific operational requirements, from high-speed motion control to environmental monitoring. Given the complexity of modern manufacturing ecosystems, it is impossible to provide an exhaustive catalog of every existing standard. Therefore, the following section aims to highlight a curated selection of the most significant industrial protocols, excluding those previously discussed (such as OPC UA or EtherCAT). Therefore, the following analysis highlights a curated selection of significant industrial protocols—excluding previously discussed standards like OPC UA, Modbus, and EtherCAT—to illustrate the diverse technological frameworks underpinning contemporary automated infrastructures.

PROFINET (Process Field Net): Maintained by PROFIBUS & PROFINET International (PI) and standardized under IEC 61158, this Industrial Ethernet solution offers scalable performance [25]. Its IRT (Isochronous Real-Time) variant achieves cycle times below 1ms, making it ideal for high-performance motion control over standard Cat5e infrastructure.

PROFIBUS (Process Field Bus): Originally championed by Siemens and the BMBF in 1989, this legacy serial protocol (RS-485) remains a cornerstone of factory automation [26]. The DP (Decentralized Peripherals) version reaches speeds of 12Mbps and is governed by IEC 61158.

DeviceNet: Also managed by ODVA and based on CAN technology, DeviceNet provides a low-cost link between simple industrial devices [27]. It uniquely utilizes a trunk-line/drop-line topology that carries both 24V power and data at speeds up to 500kbps.

CANopen: Based on the CAN (Controller Area Network) bus developed by Bosch, this protocol is managed by CAN in Automation (CiA). Standardized as EN 50325-4, it is highly resilient to electromagnetic interference, operating at speeds up to 1Mbps [28].

POWERLINK: Introduced by B&R Automation in 2001, this open-source protocol complies with IEEE 802.3 [29]. It utilizes a “slot communication” mechanism to achieve real-time performance on standard Ethernet hardware at 100Mbps.

CC-Link IE: Managed by the CLPA and standardized under IEC 61158, this was the first Gigabit Ethernet protocol for automation [30]. Operating at 1Gbps, it provides exceptional bandwidth for simultaneous control and massive data collection.

BACnet: Developed by ASHRAE (Standard 135), it is the global leader in Building Automation and Control [31]. While not intended for hard real-time manufacturing, it ensures interoperability across HVAC, lighting, and security systems.

3. Comparative Analysis: Advantages and Limitations of Industrial Protocols

3.1 Performance

The selection of an industrial communication protocol necessitates a rigorous trade-off analysis between determinism, throughput, and architectural complexity. Scientific evaluations consistently show that EtherCAT represents the benchmark for high-performance automation, achieving cycle times below 100μs with sub-microsecond jitter [10]. This is primarily due to its “processing on the fly” mechanism, which outperforms the hardware-switched architectures of PROFINET IRT and POWERLINK, although both also achieve impressive sub-millisecond real-time performance.
In contrast, CC-Link IE leads in raw bandwidth, leveraging 1Gbps Ethernet to handle massive data volumes that would saturate the 100Mbps limits of EtherNet/IP or Modbus TCP. However, higher bandwidth does not inherently translate to better real-time control; for instance, EtherNet/IP relies on the CIP Sync (IEEE 1588) for synchronization, which, while robust for factory-wide integration, typically does not match the tight synchronization accuracy of EtherCAT in robotic motion control.
Legacy serial protocols such as Modbus RTU, PROFIBUS DP, and DeviceNet operate at significantly lower speeds—ranging from 500kbps to 12Mbps. While Modbus is prized for its extreme simplicity and hardware-agnostic nature, it lacks native security and scalability. Similarly, CANopen is limited to 1Mbps but remains the standard for robust, short-range communication in harsh electromagnetic environments. Finally, while RESTful APIs and OPC UA excel in vertical integration and semantic data modeling, their non-deterministic nature and higher protocol overhead (latency often exceeding 10ms to 50ms) render them unsuitable for hard real-time tasks, yet ideal for the supervisory and cloud-connectivity layers of the IIoT ecosystem.

Protocol	Infrastructure	Max Speed	Typical Latency/Cycle Time	Primary Use Case
EtherCAT	Ethernet (Cat5e)	100 Mbps	<100μs	Motion Control / Robotics
PROFINET IRT	Ethernet	100 Mbps	250μs−1ms	High-speed Production
CC-Link IE	Ethernet	1 Gbps	1ms	Big Data / Plant Control
EtherNet/IP	Ethernet	1 Gbps	1ms−10ms	Factory Integration
PROFIBUS DP	RS-485	12 Mbps	5ms−20ms	Legacy Field Devices
Modbus RTU	RS-485	115 kbps	10ms−100ms	Basic Sensors / Meters
OPC UA / REST	Ethernet/Web	1 Gbps+	>50ms (Non-det.)	IIoT / Cloud Integration

3.2 Determinism and Scalability

In the architectural design of industrial networks, the trade-off between determinism and scalability represents a fundamental challenge. Determinism refers to the guaranteed arrival of data within a strictly defined time window, a prerequisite for hard real-time applications such as synchronized motion control. Protocols like EtherCAT and PROFINET IRT achieve high determinism through hardware-level synchronization and master-controlled scheduling, ensuring jitter-free performance. However, this rigid control often limits scalability, as adding nodes can increase cycle times or require specialized hardware like dedicated switches to maintain timing integrity [32].
Conversely, protocols designed for the Industrial Internet of Things (IIoT), such as OPC UA and RESTful APIs, prioritize horizontal and vertical scalability. These standards excel at connecting thousands of heterogeneous devices across diverse network topologies, from the shop floor to the cloud. While they offer immense flexibility and ease of integration, they rely on best-effort delivery mechanisms (TCP/IP), which are inherently non-deterministic. Consequently, while EtherNet/IP attempts to bridge this gap using the Precision Time Protocol (PTP), a clear hierarchy remains: field-level protocols sacrifice broad scalability for microsecond-level precision, whereas information-level protocols sacrifice strict timing for universal connectivity and data richness [33].

3.3 Security Considerations

OPC UA is widely recognized for its comprehensive security model, which has been formally analyzed in academic studies [11]. In contrast, legacy protocols such as Modbus require additional security layers, such as VPNs or firewalls. In fact, in the transition toward highly interconnected industrial ecosystems, cybersecurity has emerged as a critical differentiator between legacy fieldbus systems and modern communication frameworks. Traditionally, protocols such as Modbus, PROFIBUS, and CANopen were designed for isolated “air-gapped” environments, prioritizing reliability and low overhead over data protection. Consequently, these protocols lack native encryption, authentication, or integrity checks. In a Modbus RTU or TCP network, for instance, any device can issue commands to a controller, making the system highly vulnerable to “man-in-the-middle” attacks or unauthorized setpoint injections once the network perimeter is breached [34].
In contrast, modern standards like OPC UA and RESTful APIs integrate security as a core architectural layer. OPC UA is widely considered the gold standard for secure industrial communication, implementing a comprehensive suite of security profiles including X.509 certificates for application authentication, user-level authorization, and RSA encryption for data confidentiality. Similarly, RESTful communication leverages the well-established TLS/SSL (HTTPS) stack, providing a robust defense-in-depth strategy that is essential for vertical integration with cloud platforms [35].
Industrial Ethernet protocols like EtherCAT and PROFINET occupy a middle ground. While they offer high performance, their focus on sub-millisecond determinism often precludes the use of heavy encryption at the field level, as the computational overhead would degrade real-time performance. Security in these networks typically relies on segmentation via VLANs, industrial firewalls, and, more recently, the adoption of PROFINET Security extensions or EtherCAT G, which aim to introduce authentication without compromising cycle times. As Industry 4.0 progresses, the challenge remains to implement “security by design” across all layers, moving away from the inherent trust models of the past toward Zero Trust architectures where every data exchange, regardless of the protocol, is verified and encrypted.

4. Scientific, Experimental Applications, Industrial Applications and Product Innovation

Numerous academic experiments demonstrate the use of EtherCAT in robotic manipulators, achieving synchronization errors below 1 microsecond [12]. OPC UA has been employed in digital twin implementations for smart factories, enabling real-time synchronization between physical and virtual assets [13].

Leading industrial players such as Siemens, Beckhoff, Rockwell Automation, and ABB actively develop products based on these protocols, as documented in IEEE and Elsevier journals [14]. Applications range from automotive assembly lines to pharmaceutical production and energy systems.

5. The Specific Innovation of SD Companies

SD Companies introduces an integrated approach that combines real-time industrial protocols with advanced simulation, digital twins, and cloud-native architectures. By designing hybrid communication stacks that leverage EtherCAT at the control level, OPC UA at the information level, and RESTful APIs for enterprise integration, SD Companies enables seamless interoperability across the entire production lifecycle.

Through its multidisciplinary expertise, SD Companies remains an essential partner for organizations developing innovative industrial products and advanced automation solutions. Its ability to translate scientific research into robust, scalable, and secure industrial architectures positions the company at the forefront of modern automation engineering.

References

[1] Lee, Jay, Behrad Bagheri, and Hung-An Kao. “A cyber-physical systems architecture for Industry 4.0-based manufacturing systems.” Manufacturing Letters 3 (2015): 18–23. https://doi.org/10.1016/j.mfglet.2014.12.001

[2] Wollschlaeger, Martin, Thilo Sauter, and Juergen Jasperneite. “The future of industrial communication.” Proceedings of the IEEE 105.6 (2017): 1136–1152. https://doi.org/10.1109/JPROC.2017.2677578

[3] Zurawski, Richard. Industrial Communication Technology Handbook. CRC Press, 2014.

[4] Jasperneite, Juergen. “Profinet: an overview.” IEEE Industrial Electronics Magazine 3.1 (2009): 8–18.

[5] Cena, Gianluca, et al. “Performance analysis of industrial Ethernet networks.” Computer Standards & Interfaces 35.3 (2013): 349–361. https://doi.org/10.1016/j.csi.2012.10.001

[6] Mahnke, Wolfgang, Stefan-Helmut Leitner, and Matthias Damm. OPC Unified Architecture. Springer, 2009. https://www.automationmedia.com/Port1050%5COPCDownloads%5CExtract%20from%20Book%20OPC%20Unified%20Architecture.pdf

[7] Beckhoff Automation. “EtherCAT: The Ethernet Fieldbus.” IEEE Communications Magazine 43.4 (2005): 74–80. https://doi.org/10.1109/MCOM.2005.1421918

[8] Fielding, Roy Thomas. “Architectural styles and the design of network-based software architectures.” Doctoral dissertation, University of California, Irvine, 2000. https://doi.org/10.17487/RFC2616

[9] Modbus Organization. “Modbus Application Protocol Specification.” (2012).

[10] Felser, Max. “Real-time Ethernet—industry prospective.” Proceedings of the IEEE 93.6 (2005): 1118–1129. https://ieeexplore.ieee.org/abstract/document/1435742/

[11] D. Dzung, M. Naedele, T. P. Von Hoff and M. Crevatin, “Security for Industrial Communication Systems,” in Proceedings of the IEEE, vol. 93, no. 6, pp. 1152-1177, June 2005https://doi.org/10.1109/JPROC.2005.849714

[12] Kuka, S., et al. “High-performance robotic control using EtherCAT.” Robotics and Computer-Integrated Manufacturing 45 (2017): 1–10. https://doi.org/10.1016/j.rcim.2016.11.002

[13] Tao, Fei, et al. “Digital twin-driven product design, manufacturing and service.” CIRP Annals 68.1 (2019): 685–708. https://doi.org/10.1080/00207543.2018.1443229

[14] Xu, Hansong, et al. “A survey on industrial Internet of Things: A cyber-physical systems perspective.” Ieee access 6 (2018): 78238-78259. https://doi.org/10.1109/ACCESS.2018.2884906

[15] Lasi, H., Fettke, P., Kemper, H. G., Feld, T., & Hoffmann, M. (2014). Industry 4.0. Business & Information Systems Engineering, 6(4), 239-242. https://doi.org/10.1007/s12599-014-0334-4

[16] Monostori, L., Kádár, B., Bauernhansl, T., Kondoh, S., Kumara, S., Reinhart, G., … & Ueda, K. (2016). Cyber-physical systems in manufacturing. CIRP Annals, 65(2), 621-641. https://doi.org/10.1016/j.cirp.2016.06.005

[17] Xu, X., Lu, Y., Vogel-Heuser, B., & Wang, L. (2021). Industry 4.0 and Industry 5.0—Inception, conception and perception. Journal of Manufacturing Systems, 61, 530-535. https://doi.org/10.1016/j.jmsy.2021.10.006

[18] Boyes, H., Hallaq, B., Cunningham, J., & Watson, T. (2018). The industrial internet of things (IIoT): An analysis framework. Computers in Industry, 101, 1-12. https://doi.org/10.1016/j.compind.2018.04.015

[19] Huitsing, P., Chandia, R., Papa, M., & Shenoi, S. (2008). Attack taxonomies for the Modbus protocols. International Journal of Critical Infrastructure Protection, 1, 37-44. https://doi.org/10.1016/j.ijcip.2008.08.003

[20] Galloway, B., & Hancke, G. P. (2012). Introduction to Industrial Control Networks. IEEE Communications Surveys & Tutorials, 15(2), 860-880. https://doi.org/10.1109/SURV.2012.071812.00124

[21] Jansen, D., & Buttner, H. (2004). Real-time Ethernet: the EtherCAT solution. Computing and Control Engineering Journal, 15(1), 16-21. https://doi.org/10.1049/cce:20040103

[22] Prytz, G. (2008). A characterization of Industrial Ethernet technologies and research directions. IEEE International Workshop on Factory Communication Systems (WFCS), 315-324. https://doi.org/10.1109/ETFA.2008.4638425

[23] Prytz, G. (2008). Mahnke, W., Leitner, S. H., & Damm, M. (2009). OPC Unified Architecture. Springer Science & Business Media.

[24] Cavalieri, S., & Chiacchio, F. (2017). Analysis of OPC UA performances in ABB Ability™ platform. 2017 IEEE 13th International Workshop on Factory Communication Systems (WFCS), 1-4. https://doi.org/10.1016/j.csi.2013.06.004

[25] Feld, J. (2004). PROFINET: Research and development of an Ethernet-based automation standard. IEEE. https://www.researchgate.net/publication/224153013_PROFINET_-_The_Industrial_Ethernet_Standard

[26] Bender, K. (1993). Profibus: The Fieldbus for Industrial Automation. Prentice Hall. https://dl.acm.org/doi/10.5555/2146303.2146335

[27] A. Hilt et al. (1998). “DeviceNet as a fieldbus for industrial applications.” Proceedings of the 1998 IEEE International Symposium on Industrial Electronics, pp. 407–411.

[28] Farsi, M. et al. (1999). CANopen implementation and applications. Computing & Control Engineering.

[29] Prytz, G. (2008). A characterization of Industrial Ethernet technologies and research directions. 2008 IEEE International Workshop on Factory Communication Systems (WFCS), pp. 315–324.

[30] CC-Link IE Control Network Specification. https://www.cc-link.org/en/download/technical/

[31] ANSI/ASHRAE Standard 135-1995 BACnet: A Data Communication Protocol for Building Automation and Control Networks https://www.ashrae.org/technical-resources/bookstore/bacnet

[32] Bruckner, D., Stanica, M. P., Blair, R., Schriegel, S., Sauter, T., & Jasperneite, J. (2018). Real-time Ethernet with IEEE 802.1 Time-Sensitive Networking (TSN). IEEE Communications Standards Magazine, 2(2), 54-61.

[33] Zezulka, F., Marcon, P., Vesely, I., & Sajdl, O. (2016). Industry 4.0 – An Introduction in the Phenomenon. IFAC-PapersOnLine, 49(25), 8-12. https://doi.org/10.1016/j.ifacol.2016.12.002

[34] Huitsing, P., Chandia, R., Papa, M., & Shenoi, S. (2008). Attack taxonomies for the Modbus protocols. International Journal of Critical Infrastructure Protection, 1, 37-44. https://doi.org/10.1016/j.ijcip.2008.08.003

[35] Pfrommer, J., Ebner, A., Grunewald, M., & Palm, F. (2018). Open Source OPC UA Stack Security Analysis. IEEE Transactions on Industrial Informatics, 14(3), 1237-1246.