Evaluation of Message Missing Failures in Flexray-Based Networks with Star Topology

Total Page:16

File Type:pdf, Size:1020Kb

Evaluation of Message Missing Failures in Flexray-Based Networks with Star Topology Evaluation of Message Missing Failures in FlexRay-based Networks with Star Topology Abstract FlexRay communication protocol [10]. The FlexRay allows the sharing of the bus among event-triggered This paper evaluates the error propagation and its and time-triggered messages, thus offering the effects in message missing in a FlexRay-based network advantages of both protocols. It is reported that the with star topology. The evaluation is based on about FlexRay will very likely become the de-facto standard 35680 bit-flip fault injections inside different parts of for in-vehicle communications [5] [11]. The FlexRay the FlexRay communication controller. To do this, a defines a communication cycle (bus cycle) as the FlexRay communication controller is modeled by combination of a time-triggered (or static) window, an Verilog HDL at the behavioral level and is exploited to event-triggered (or dynamic) window, a symbol setup a FlexRay-based network composed of four window and a network idle time (NIT) window. The nodes. The results of fault injection show that about time-triggered window is similar to TTP, and employs 39% of faults lead to the message missing failures. The a time-division multiple-access (TDMA) mechanism. clock synchronization process and the controller host The event-triggered window of the FlexRay protocol is interface of the FlexRay were the most sensitive to the similar to Byteflight protocol and uses a flexible message missing failure. The coding and decoding unit TDMA (FTDMA) bus access method. The symbol of the FlexRay was the least sensitive to this failure. window is a communication period in which a symbol can be transmitted on the network. The NIT window is a communication-free period that specifies the end of 1. Introduction each communication cycle. The importance of safety in critical distributed Safety in distributed systems such as automotive applications signals to pay specific attention to the systems and avionics is of decisive importance due to reliability of communication protocols. One way to system failures which may threat human life. In a evaluate the reliability of communication protocols is distributed system, each node consists of three parts by fault injection to assess the vulnerability of such [1]: 1) I/O part, 2) host part, and 3) communication protocols. The fault injection techniques can be controller. Among these three parts, the classified into two main categories [12]: 1) hardware- communication controller has a key role in the based fault injection [13], and 2) software-based fault distributed systems operation. injection [14]. The latter can in turn be divided into In general, communication activities can be triggered software-implemented fault injection (SWIFI) and either dynamically, in response to an event (event- simulation-based fault injection [14]. In simulation- triggered), or statically, at predetermined moments in based fault injection, faults are injected into the time (time-triggered). Examples of time-triggered simulation model of circuits using HDL languages [14] protocols are the SAFEbus [2], SPIDER [3], and Time- or other languages such as C++ [15]. Triggered Protocol (TTP) [4]. The main drawback of In [16], a simulation-based fault injection has been the time-triggered protocols is their lack of flexibility used for the assessment of message missings in the [5]. Examples of event-triggered protocols are the CAN protocol. Effects of masquerade failures have Byteflight [6] introduced by BMW Company for been investigated using a simulation-based fault automotive applications, CAN [7], LonWorks [8] and injection in the CAN protocol [17]. Evaluation of Profibus [9]. The main drawback of the event-triggered TTP/C communication controller by heavy-ion fault protocols is their lack of predictability. A large injection (hardware-based fault injection) has been consortium of automotive manufacturers and suppliers performed in [18]. The purpose of the experiments in has proposed a hybrid type of protocol, namely, the that paper was to validate the fail silence property of the TTP/C by injecting faults in a single node. The 2. FlexRay Protocol Structure relationship between the number of nodes in a cluster and the slightly-off-specification (SOS) failures has The FlexRay protocol controller consists of six been assessed using heavy-ion fault injection [19]. In parts: controller host interface (CHI), protocol [20], the TTP/C protocol with bus and star topologies operation control (POC), coding and decoding has been investigated using SWIFI fault injection. (CODEC), media access control (MAC), frame and Here, the effects of the SOS failures in the bus and star symbol processing (FSP) and clock synchronization topologies with respect to the start of frame process (CSP). transmission have been studied. In [21] [22], a generic The CHI manages data and control flow between tool was developed for monitoring and diagnosis of a the host processor and the FlexRay protocol engine FlexRay-based system as well as for a CAN-based within each node. The CHI contains two major system. This tool has been used by the FlexRay interface blocks: the protocol data interface and the consortium to perform extended fault injection for message data interface. The protocol data interface evaluating of the FlexRay communication protocol. manages all data exchange relevant to the protocol One important limitation of this tool is that faults operation and the message data interface manages all cannot be injected inside different parts of the FlexRay data exchange relevant to the exchange of messages. protocol. The protocol data interface manages the protocol This paper evaluates the error propagation and configuration data, the protocol control data, and the message missing failures in the FlexRay protocol with protocol status data. The message data interface star topology. It evaluates the conditions that faults in manages the message buffers, the message buffer the FlexRay protocol disturb the sending or receiving configuration data, the message buffer control data, of messages at a node and cause a message does not and the message buffer status data. In addition, the CHI send or receive. In this condition a message missing provides a set of services that define self-contained failure occurs. This evaluation is done by 35680 bit- functionality that is transparent to the operation of the flip fault injection inside different parts of the FlexRay protocol [10]. protocol. To do this, a FlexRay communication The core parts of the protocol are moded by POC. controller was modeled by Verilog HDL at the Proper protocol behavior can only occur if the mode behavioral level. A FlexRay-based network composed changes of the core parts are properly coordinated and of four nodes was established using this controller by synchronized. The purpose of the POC is to react to star topology. The evaluations are done in two phases, host commands and protocol conditions by triggering at the first phase the percentages of faults resulting in coherent changes to core parts in a synchronous three kinds of errors, namely, content errors, syntax manner, and to provide the host with the appropriate errors and boundary violation errors are characterized. status regarding these changes [10]. The most sensitive and the less sensitive points of the The CODEC contains two sections: coding section FlexRay protocol to faults are identified. Then in the and decoding section. Coding section is responsible for second phase, by considering the error propagation encoding the communication elements into a bit stream results, the message missing failures are evaluated. In and how the transmitting node represents this bit this phase the relationship between the error stream to the bus driver for communication onto the propagation and message missing failure results are physical media. Decoding section is responsible for analyzed. Also, the message missing failure rate that receiving communication elements, make bit streams occurs in time-triggered or event-triggered window of and investigate correctness of bit streams. the FlexRay communication cycle are assessed. The The MAC controls access to the bus. In the FlexRay dependencies of fault locations (FlexRay parts) to this protocol, media access control is based on a recurring failure are also assessed. communication cycle. Within one communication This paper is organized in six sections. Section 2, cycle, FlexRay offers the choice of two media access introduces the FlexRay protocol, and section 3 presents schemes. These are a TDMA scheme and a FTDMA the message missing failures and error models found in scheme. The communication cycle is the fundamental this protocol. The experimental organization is given in element of the media access scheme within FlexRay. It section 4, and the results are presented in section 5. contains the static segment, the dynamic segment, the The last section concludes the work. symbol window and the NIT [10]. The FSP is the main processing layer between CODEC and CHI. This part checks the correct timing of received frames and symbols with respect to the TDMA scheme, applies further syntactical tests to received frames, and checks the semantic correctness receiving the messages from communication of received frames [10]. controller. Meanwhile, the host generates the message Finally, the CSP uses a distributed clock exactly as many as the IDs that has been allocated to its synchronization mechanism in which each node controller. It means that the number of generated
Recommended publications
  • Benefits of a Standardized Diagnostic Framework
    Benefits of a standardized diagnostic framework Hareesh Prakash Development Engineer The copying, distribution and utilization of this document as well as the communication of its contents to other without expressed authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or ornamental design registration. Agenda DiagnosticsDiagnostics withwith standardsstandards –– Motivation Motivation ODXODX –– ODXplorer ODXplorer MCD-3MCD-3 ServerServer –– samMCD3 samMCD3 serverserver MVCI-D-PDU-APIMVCI-D-PDU-API –– HSX HSX samtecsamtec DiagnosticDiagnostic FrameworkFramework The copying, distribution and utilization of this document as well as the communication of its contents to other without expressed authorization is prohibited. ffenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or ornamental design registration. Diagnostics with Standards Motivation 2000 - 2009 New ACC Stop & Go ALC + Navigation Strategies, Heading Control Night Vision Process, AFS I + II X-AGS 1990 - 1999 Internet Tools, … Telematics Navigation system Online Services CD-Changer Bluetooth Bus system Car Office ACC Adaptive Cruise Control Complexity Local Hazard Warning Complexity 1980 - 1989 Airbags Integrated Safety Systems DSC Dynamic Stability Control Electronic Transmission control Break-By-Wire Adaptive Transmission Control Electronic air conditioning control Steer-By-Wire Anti-roll ASR i-Drive Xenon Lights ABS Fuel cells 1970 - 1979 BMW Assist Telephone LH RDS/TMC 2 Electronic Fuel Injection Seat heating Lane change ssistant Emergency calls Electronic Ignition … Personalization Servotronic Check Control Software Update … Idle speed regulator Force Feedback Pedal Central lock … Costs Source: [2] Hudi; [4] Reichert The copying, distribution and utilization of this document as well as the communication of its contents to other without expressed authorization is prohibited.
    [Show full text]
  • Smartwire-DT Gateways – Canopen and PROFIBUS-DP
    09/11 MN05013002Z-EN Manual replaces 06/09 AWB2723-1612en SmartWire-DT Gateways All brand and product names are trademarks or registered trademarks of the owner concerned. Emergency On Call Service Please call your local representative: http://www.eaton.com/moeller/aftersales or Hotline of the After Sales Service: +49 (0) 180 5 223822 (de, en) [email protected] Original Operating Instructions The German-language edition of this document is the original operating manual. Translation of the original operating manual ) All editions of this document other than those in German language are translations of 2 the original German manual. 1st edition 2009, edition date 02/09 2nd edition 2009, edition date 06/09 3rd edition 2010, edition date 03/10 4th edition 2010, edition date 06/10 5th edition 2011, edition date 03/11 6th edition 2011, edition date 09/11 See revision protocol in the “About this manual“ chapter © 2009 by Eaton Industries GmbH, 53105 Bonn Production: René Wiegand Translation: globaldocs GmbH All rights reserved, including those of the translation. Rückenbreite festlegen! (1 Blatt = 0,106 mm, gilt nur für XBS) g/m 80 bei Digitaldruck Eberwein für mm = 0,080 Blatt (1 No part of this manual may be reproduced in any form (printed, photocopy, microfilm or any other process) or processed, duplicated or distributed by means of electronic systems without written permission of Eaton Industries GmbH, Bonn. Subject to alteration without notice. Danger! Dangerous electrical voltage! Before commencing the installation • Disconnect the power supply of the • Suitable safety hardware and device. software measures should be • Ensure that devices cannot be implemented for the I/O interface accidentally restarted.
    [Show full text]
  • — PROFIBUS-Adapter
    — ABB MEASUREMENT & ANALYTICS | DATA SHEET PROFIBUS-Adapter — To find your local ABB contact visit: www.abb.com/contacts For more information visit: www.abb.com/measurement — We reserve the right to make technical changes or modify the contents of this document without prior notice. With regard to purchase orders, the agreed particulars shall prevail. ABB does not accept any responsibility whatsoever for potential errors or possible lack of information in this document. We reserve all rights in this document and in the subject matter and illustrations contained therein. Any reproduction, disclosure to third parties or utilization of its contents – in whole or in parts – is forbidden without prior written consent of ABB. © ABB 2019 3KXN631121R1001 10/63-6.31-EN Rev. G 05.2019 2 NDA121-NO PROFIBUS-ADAPTER | 10/63-6.31-EN REV. G NDA121-NO PROFIBUS-ADAPTER | 10/63-6.31-EN REV. G 7 — Measurement made easy — Profibus DP / PC Adapter • USB NDA121-NO PROFIBUS-ADAPTER | 10/63-6.31-EN REV. G 3 — NDA121-NO PROFIBUS DP / PC-USB adapter hange from one to two columns Adapter CommDTM Desktop PC’s as well as notebooks can be flexible connected The Device Type Manager CommDTM provides access to the in the field to a PROFIBUS® network via the adapter PROFIBUS® Master NDA121-NO. Within the FDT architecture, NDA121-NO. Thereby a parallel operation of up to 16 adapter the CommunicationDTM enables DeviceDTMs to connect to is possible. The adapter supports the Master functionality of their respective devices via PROFIBUS® DP/-V1. the PROFIBUS® Standards DP (class 1 and 2), DP-V1 (class 2).
    [Show full text]
  • Master Simulators
    Master simulators By using master simulators from HMS, you can set up and test slaves/adapters on PROFIBUS, PROFINET, CANopen, EtherNet/IP and DeviceNet without having a PLC in place. Simply connect to your computer and you have a very cost-efficient alternative to a PLC or PC-card. CANopen interface — powered by USB USB port on the PC RS-232 CANopen cable 9-pin D-Sub connector PROFIBUS interface Device under test Device under test DeviceNet interface USB (24V power supply required to connect and test a DeviceNet adapter —not included). DeviceNet cable with data and power lines Pluggable screw connector Ethernet cable with termination Device under test Device under test Available for: Test your device without an expensive PLC Key features Master simulators are ideal for test-wiring of inputs and ouputs • Easy-to-use test and diagnostics and reading and writing analog values. They are useful during tool. setup of slave/adapters in a network as well as during final • No programming required. inspection tests at the device manufacturer. • Auto-detects slaves/adapters Industrial Ethernet versions are software-only, while fieldbus (even when GSD/EDS file is not versions also include a converter interface which is used to available). connect the fieldbus cable to the PC. • Auto detection of I/O data size. No GSD/EDS files needed (not for EtherNet/IP) During setup and maintenance, there may not be GSD/EDS available making master simulators especially useful for this scenario. HMS provides a full 3 year product guarantee TECHNICAL SPECIFICATIONS Description Consists of a Windows-based Software only.
    [Show full text]
  • Efficiently Triggering, Debugging and Decoding Low-Speed Serial Buses
    Efficiently Triggering, Debugging and Decoding Low-Speed Serial Buses Hello, my name is Jerry Mark, I am a Product Marketing Engineer at Tektronix. The following presentation discusses aspects of embedded design techniques for “Efficiently Triggering, Debugging, and Decoding Low-Speed Serial Buses”. 1 Agenda Introduction – Parallel Interconnects – Transition from Parallel to Serial Buses – High-Speed versus Low-Speed Serial Data Buses Low-Speed Serial Data Buses – Challenges – Technology Reviews – Measurement Solutions Summary 2 In this presentation we will begin by taking a glance at the transition from parallel-to-serial data and the challenges this presents to engineers. Then we will briefly review some of the most widely used low-speed serial buses in industry today and some of their key characteristics. We will turn our attention to the key measurements on these buses. Subsequently, we will present by example how the low-speed serial solution from Tektronix addresses these challenges. 2 Parallel Interconnects Traditional way to connect digital devices used parallel buses Advantages – Simple point-to-point connections – All signals are transmitted in parallel, simultaneously – Easy to capture state of bus (if you have enough channels!) – Decoding the bus is relatively easy Disadvantages – Occupies a lot of circuit board space – All high-speed connections must be the same length – Many connections limit reliability – Connectors may be very large 3 Parallel buses present all of the bits in parallel, as shown in the logic analyzer display. A parallel connection between two ICs can be as simple as point-to-point circuit board traces for each of the data lines. If you can physically probe these lines, it is easy to display the bus state on a logic analyzer or mixed signal oscilloscope.
    [Show full text]
  • The Role of CAN in the Age of Ethernet and IOT
    iCC 2017 CAN in Automation The role of CAN in the age of Ethernet and IOT Christian Schlegel, HMS Industrial Networks CAN technology was developed in the 1980s and became available in 1987, just as other industrial fieldbus systems like PROFIBUS or INTERBUS entered the stage of industrial communication. Beside the fact that CAN is a success in the automotive industry and used in all types of cars today, it has also made its way in many other industrial areas. About 15 years ago, new technologies based on Ethernet started to emerge, with ap- pealing and sometimes outstanding features. Some six years ago Ethernet also started to find its way into automobiles. Today, other new communication technologies are showing up on the horizon driven by the omnipresent Industrial Internet of Things. But even now, 30 years after their introduction, these “classic” fieldbus technologies are still alive – with varying success. Since CAN was initially developed with a focus for use in automobiles, CAN has certain features that still make it the best choice for many applications in automobiles and industrial areas – even when compared to the newer technologies. This paper discusses why CAN is still a valid or even better choice for certain applica- tion areas than Ethernet-based technologies, not just focusing on the advanced fea- tures provided by the enhanced capabilities of CAN FD but also highlighting how these applications benefit from the features of “classic” CAN. Looking back into history … the requirement to transmit data between … when CAN was born these ECUs but also to connect sensors and actuators to them.
    [Show full text]
  • Fieldbus Communication: Industry Requirements and Future Projection
    MÄLARDALEN UNIVERSITY SCHOOL OF INNOVATION, DESIGN AND ENGINEERING VÄSTERÅS, SWEDEN Thesis for the Degree of Bachelor of Science in Engineering - Computer Network Engineering | 15.0 hp | DVA333 FIELDBUS COMMUNICATION: INDUSTRY REQUIREMENTS AND FUTURE PROJECTION Erik Viking Niklasson [email protected] Examiner: Mats Björkman Mälardalen University, Västerås, Sweden Supervisor: Elisabeth Uhlemann Mälardalen University, Västerås, Sweden 2019-09-04 Erik Viking Niklasson Fieldbus Communication: Industry Requirements and Future Projection Abstract Fieldbuses are defined as a family of communication media specified for industrial applications. They usually interconnect embedded systems. Embedded systems exist everywhere in the modern world, they are included in simple personal technology as well as the most advanced spaceships. They aid in producing a specific task, often with the purpose to generate a greater system functionality. These kinds of implementations put high demands on the communication media. For a medium to be applicable for use in embedded systems, it has to reach certain requirements. Systems in industry practice react on real-time events or depend on consistent timing. All kinds are time sensitive in their way. Failing to complete a task could lead to irritation in slow monitoring tasks, or catastrophic events in failing nuclear reactors. Fieldbuses are optimized for this usage. This thesis aims to research fieldbus theory and connect it to industry practice. Through interviews, requirements put on industry are explored and utilization of specific types of fieldbuses assessed. Based on the interviews, guidelines are put forward into what fieldbus techniques are relevant to study in preparation for future work in the field. A discussion is held, analysing trends in, and synergy between, state of the art and the state of practice.
    [Show full text]
  • CAN-To-Flexray Gateways and Configuration Tools
    CAN-to-Flexray gateways Device and confi guration tools lexray and CAN net- Listing bus data traffic toring channels it is possi- power management func- Fworks will coexists in (tracing) ble to compare timing rela- tionality offers configurable the next generation or pas- Graphic and text displays tionships and identify timing sleep, wake-up conditions, senger cars. Flexray orig- of signal values problems. and hold times. The data inally designed for x-by- Interactive sending of GTI has developed a manipulation functionality wire applications gains mar- pre-defined PDUs und gateway, which provides has been extended in or- ket acceptance particular- frames two CAN and two Flexray der to enable the user to ap- ly in driver assistance sys- Statistics on nodes and ports. It is based on the ply a specific manipulation tems. Nevertheless, Flexray messages with the Clus- MPC5554 micro-controller. function several times. Also applications need informa- ter Monitor The gateway is intended to available for TTXConnexion tion already available in ex- Logging messages for be used for diagnostic pur- is the PC tool TTXAnalyze, isting CAN in-vehicle net- later replay or offline poses, generating start-up/ which allows simultaneous works. Therefore, CAN-to- evaluation sync frames, and it can be viewing of traffic, carried on Flexray gateways are nec- Display of cycle multi- used with existing software the various bus systems. essary. Besides deeply em- plexing, in-cycle rep- tools. The Flexray/CAN bedded micro-controller etition and PDUs in the The TTXConnexion by gateway by Ixxat is a with CAN and Flexray inter- analysis windows TTControl is a gateway tool configurable PC application faces, there is also a need Agilent also provides an combining data manipula- allowing Flexray messag- for gateway devices as in- analyzing tool for Flexray tion, on-line viewing, and es and signals to be trans- terface modules for system and CAN.
    [Show full text]
  • Profibus and Modbus: a Comparison
    James Powell, P. Eng. Profibus and Modbus: a comparison We live in a multi-protocol In this article, we will provide an overview col that only Modicon could use. However, of both protocols and discuss their key it was later published royalty-free so that world – and this will likely strengths and applications. Comparing the anyone could use it. Finally, Modicon made not change anytime soon. two, we’ll see that both protocols have their it an open protocol. When it was published, own particular strengths. We’ll also discuss a number of companies started using it, Different protocols work which one works best in which applications creating different interpretations and modi- better in different applica- – although there is some overlap in what fi cations of the original specifi cation. As a each can do. What’s more, they can com- result, there are now quite a few variations tions. I have not come to plement each other in joint applications. in the fi eld. bury Modbus or Profibus, Introduction to Modbus The specifi cation document is fewer than nor to praise them, but 100 pages in length, which is a good indica- rather to add some per- Modbus is the “granddaddy” of industrial tion of the protocol’s low level of complex- communication protocols. It was originally ity. In comparison, Profi bus’ specifi cation spective and knowledge. designed in the mid-1970s by Modicon as document is thousands of pages long. a way to link intelligent devices with PLCs using a simple master/slave concept. The term “Modbus” typically refers to one of three related protocols: Modbus ASCII, “Simple” is a key descriptor for Modbus – Modbus RTU, or Modbus TCP/IP:1 and also its biggest strength.
    [Show full text]
  • Table of Contents
    Table of Contents Chapter 1 Bus Decode -------------------------------------------------------------- 1 Basic operation --------------------------------------------------------------------------------------------- 1 Add a Bus Decode ----------------------------------------------------------------------------------------------------- 1 Advance channel setting ---------------------------------------------------------------------------------------------- 2 Specially Bus Decode: ------------------------------------------------------------------------------------------------ 4 1-Wire ------------------------------------------------------------------------------------------------------------------- 7 3-Wire ------------------------------------------------------------------------------------------------------------------- 9 7-Segment -------------------------------------------------------------------------------------------------------------- 11 A/D Converter--------------------------------------------------------------------------------------------------------- 14 AcceleroMeter -------------------------------------------------------------------------------------------------------- 17 AD-Mux Flash -------------------------------------------------------------------------------------------------------- 19 Advanced Platform Management Link (APML) ---------------------------------------------------------------- 21 BiSS-C------------------------------------------------------------------------------------------------------------------ 23 BSD ---------------------------------------------------------------------------------------------------------------------
    [Show full text]
  • The Path to Robust Automotive Networking
    The Path to Robust Automotive Networking www.infineon.com/automotive-networking 2 Content Introduction 4 Products Overview 7 Automotive Transceivers 8 System Basis Chips (SBCs) 12 Infineon® Embedded Power ICs 18 Microcontrollers 25 Support Tools 28 System Basis Chips (SBCs) 28 Infineon® Embedded Power ICs 29 Microcontrollers 30 Packages Overview 32 3 Introduction Automotive Networking Automotive networking technology is evolving fast, driven World leader in automotive electronics for over 40 years, by a number of key trends. With an ever-increasing num- we actively engage with many industry, standardization ber of cars on the road and rising fuel costs, demands and research organizations to drive in-vehicle network- for energy efficiency are growing. Worldwide legislation ing innovations capable of meeting today’s demands for is establishing ever-stricter caps on CO2 emissions. The energy efficiency, safety, smooth interfacing and complex- spotlight is also on functional safety. With the ISO 26262 ity management. Our broad portfolio extends from stand- automotive standard increasingly moving into applications alone transceivers through system basis chips to embed- that were not typically safety-relevant, the bar is moving ded power solutions for CAN, LIN and FlexRay protocols. upwards and we are seeing increasingly granular system We also offer microcontrollers with enhanced communica- safety concepts. At the same time, complexity is on the tion capabilities to support multiple protocols. All of our increase. Growing consumer expectations are fuelling new products are designed to deliver the exceptional levels of comfort and safety features also in low-end segments, and ESD and EMC performance required in automotive environ- this, in turn, is placing pressure on semiconductor manu- ments.
    [Show full text]
  • Profinet Vs Profibus
    Profinet vs Profibus Pouya Aminaie1 and Poorya Aminaie2 1Department of ECE, Shiraz University, Shiraz, Iran 2 Department of ECE, Shahid Beheshti University, Tehran, Iran E-mail: [email protected] Abstract We present a step by step definition of Profinet and Profibus. We introduced different types of each of the two communication protocols. We then described the topology and performance of each one individually. Finally, the properties of them have been compared to show that which one has better performance in the industry. Keywords: Profinet, Profibus, Industrial Ethernet and Communication Networks 1. Introduction 1.1. Profinet Profinet is the abbreviation for Process Field Net, which refers to technical standards for data communication through Ethernet in the industry. These types of standards are used for gathering data and controlling industrial equipment. As can be seen from Fig.1, Profinet satisfies all the needs of industrial technologies. Fig.1 Requirement of automation technology [1] 1 The need for Profinet is felt in production automation and processing automation sections, where its use can resolve many of these needs. Profinet can be divided into two main categories, as follows: • Profinet IO • Profinet CBA 1.2. Profibus The word Profibus is taken from the phrase Process Field Bus. The scope of this protocol covers from the field level to the control level. The advantages of Profibus are as follows: 1. Low noise acceptance due to twisted pair cable being the transmission interface. 2. Appropriate bandwidth due to the use of an appropriate transmission method such as RS485. 3. Secure and non-interfering data exchange for using the token pass access method.
    [Show full text]