Profinet Stack for QNX

Profinet Stack for QNX

Profinet stack for QNX Master’s Thesis in Computational Engineering submitted by Valianos Stelica born 15.07.1990 in Macin Written at Lehrstühl für Informatik 10 Friedrich-Alexander-Universität Erlangen-Nurnberg. Advisor: Prof. Dr. Harald Köstler, Dipl. Inf. Nicol Vogler Started: 01.04.2020 Finished: 20.10.2020 i Ich versichere, dass ich die Arbeit ohne fremde Hilfe und ohne Benutzung anderer als der angegebenen Quellen angefertigt habe und dass die Arbeit in gleicher oder ähnlicher Form noch keiner anderen Prufungsbehörde vorgelegen hat und von dieser als Teil einer Prüfungsleistung angenommen wurde. Alle Ausfuhrungen, die wörtlich oder sinngemaß übernommen würden, sind als solche gekennzeichnet. Die Richtlinien des Lehrstuhls für Studien- und Diplomarbeiten habe ich gelesen und an-erkannt, insbesondere die Regelung des Nutzungsrechts. Erlangen, den 20. Oktober 2020 ii iii Übersicht Der Erfolg von QNX Neutrino RTOS ist, dass es in den eingebetteten Systemen für den medizinischen Markt häufig verwendet wird, aufgrund der Zertifizierungen und Sicherheitsmerkmale, deshalb wird die Nutzung von QNX Neutrino RTOS in die Angiographiesystemen sinnvoll. Trotzdem Linux RTOS wird kostenlos angeboten und wird gut dokumentiert und unterstützt in der Softwareentwickler-Gemeinschaft. In dieser Arbeit wird die QNX RTOS Alternative zu dem Linux RTOS getestet und wir untersuchen die Unterschiede der Gesamtkosten, Programmsicherheit, Zuverlässigkeit und Informationssicherheit. Die präsentierte Implementierung von QNX RTOS wurde vor Ort auf die Siemensgeräte CCOM und FCPU geprüft und evaluiert. Wir haben eine zeitliche Verkürzung durch QNX RTOS bemerkt, dass einen frühren Markteintritt des Produktes produziert und erzeugt größere Einnahmen im Gegensatz zur Benutzung von dem kostenlosen Linux RTOS. Darüberhinaus QNX ist stabiler, sicherer und zuverlässiger somit wird der Entwicklungsprozess abhängig von der medizinische Gerätezertfizierung verkürzt. Aufgrund der vorgestellten Eigenschaften und Vorteilen, das QNX RTOS wird für alle CCOMs und FCPUs Geräte in den neuen Siemens Systemen benutzt. Abstract The great success of QNX Neutrino RTOS in the embedded systems for the medical market, due to its certifications and safety characteristics, makes it desirable for Angyography systems. However, Linux RTOS is offered for free and is well documented and supported in the software development community. In this work, we propose the QNX RTOS alternative to the Linux RTOS, and we will examine the differences in the total ownership cost, security, reliability and safety. The presented implementation of QNX RTOS was field tested and evaluated on Siemens’ devices- CCOM and FCPU. We notice a reduction in the time to market for the final product, resulting in a bigger total revenue than using free Linux RTOS variant. Furthermore, QNX is more stable, secure and reliable, thus reducing the process of development related to medical devices certifications. Due to its features and advantages presented, QNX RTOS is used for all CCOMs and FCPUs, in the new Siemens systems. iv v Contents 1 Introduction ….……………………………………………………………………….. 1 1.1 Motivation…………………………………………………………………………. 1 1.2 Objective of the Thesis………………………………………………………….. 2 2 Theoretical Background…………………………………………………………….. 3 2.1 Introduction to operating systems……………………………………………… 3 2.2 Common operating systems……………………………………………………. 5 2.2.1 Unix OS and its importance………………………………………….. 5 2.2.2 Linux OS……………………………………………………………….. 6 2.2.3 QNX OS………………………………………………………………… 7 2.3 Total ownership costs: QNX vs Linux………………………..……………….. 10 3 Profinet…………………………………………………………………………………. 16 3.1 Profinet standard for communication………………………………………….. 16 3.2 Profinet Conformance Classes…………………………………………………. 19 3.3 Profinet Communication Layer………………………………………………….. 22 4 Network sockets……………………………………………………………………… 25 4.1 Introduction to Network Sockets……………………………………………….. 25 4.2 Linux Sockets…………………………………………………………………….. 28 4.3 FreeBSD Sockets………………………………………………………………... 29 4.4 BPF Filter…………………………………………………………………………. 29 5 Porting from Linux to QNX…………………………………………………………… 34 5.1 System overview and high-level porting instructions…………………………. 34 5.2 Low-level layer implementation of Ethernet Driver for Standard MAC……... 46 5.3 QNX vs Linux RTOS in medical devices………………………………………. 54 5.4 Resulted advantages from the porting process...…………………………….. 58 5.5 Testing the Profinet communication……………………………………………. 60 6 Conclusion and Outlook…………………………………………………………….. 64 List of Figures 65 List of Tables 65 Bibliography 66 Appendix 69 vi CONTENTS vii Abbreviations API Application Program Interface CLI Command Line Interface CPU Central Processing Unit CT Computerized Tomography FCPU Fail-safe Central Processing Unit HDMI High-Definition Multimedia Interface GUI Graphic User Interface MRI Magnetic Resonance Imaging PCIE Peripherial Component Interconnect Express OS Operating System RTOS Real-Time Operating System UI User Interface USB Universal Serial Bus SMP Symmetric multiprocessing FIFO First-In First-Out POSIX Portable operating System Interface IT Information Technology EMF Embedded Market Forecaster GPL General Public License viii IEC International Electrotechnical Commission Profinet Process Field Network TCP/IP Transmission Control Protocol/Internet Protocol XML Extensible Markup Language PLC Programmable Logic Controller IO Input-Output PD Programmable Device PC Personal Computer HMI Human-Machine Interface WLAN Wireless Local Area Network DAP Device Access Point GSD General Station Description AR Application Relation CR Communication Relation RT Real-time MAC Media Access Control LLDP-MIB Link-Layer Discovery Protocol- Management Information Base SNMP Simple Network Management Protocol PA Process Automation DR Dynamic Reconfiguration PTP Precision Time Protocol DFP Dynamic Frame Packing IRT Isochronous Real-Time IPv6 Internet protocol versions 6 VLAN Virtual Local Area Network TAS Time-Aware Shaper OSI Open Systems Interconnection RPC Remote Procedure Call ix TDMA Time Division Multiple Access-Collision Detection OPC UA Open Platform Communication United Architecture CSMA/CD Carrier-sense multiple access with collision detector ARP Adress Resolution Protocol DCP Discovery and Configuration Protocol BPF Berckeley Packet Filters ICMP Internet Control Message Protocol NIC Network Interface Controller CAN Controller Area Network EKG Electrocardiogram IDE Integrated Development Environment EPS Embedded Profinet System PnDriver Profinet Driver LD Logical Device HD Hardware Device LED Light Emitting Diode PN Profinet PSI Profinet System Integration EDDS Ethernet Device Driver for “Standard MAC” MDR European Medical Device Regulation OTA Over-The-Air PKI Public Key Infrastructure NVD National Vulnerability Database SOUP Software of Unknown Provenience PNIO Stack Profinet Input-Output Stack x Chapter 1 Introduction 1.1 Motivation With the growing number of the population world-wide and the need for fast treatment of the diseases, new technologies and equipment to cure, diagnose or support the patients are in demand. The number of people affected by different diseases increases with the age of the patients. It is expected that by the year 2050, more than 1.5 billion people worldwide will live over the age of 65 [Wor11]. The medical industry is one of the fastest growing segment in the world. New medical technologies help the medical personnel in treating fast and accurate the diseases, in long term support of the patient with chronic disease but also in the diagnosis process. From common medical supplies(e.g.syringes, bandages) to complex instruments(e.g.robotic surgery, 3D printing of artificial organs, CT, MRI, heart valves), there are over 190.000 different devices manufactured by more than 18.000 firms worldwide[MD18]. Because many modern devices are used outside a controlled hospital environment, they should be reliable, safe and secure. Chronic diseases have caused most elderly deaths(e.g.chronic lower respiratory disease), and the treatment of these diseases requires long therm use of medical devices. An orthopedic surgeon implants a hip prosthesis in an elderly patient and expects the device to withstand the stress loads reliably, in order to restore normal mobility. An anesthesiologist uses a pulse oximeter during surgery to monitor the physiologic status of the patient, and expects the readings to be reliable. An insulin pump must calculate and adjust the insulin dose properly in order to support the life of the patient. As we can expect, for medical devices failure is not an option[EXP10][QVP]. Furthermore, the people affected by diseases, have problems in accepting devices that will further process patient related information in order to monitor the disease, because of the possibility of data misuse. In principle, having a robust real-time operating system to support your 1 API, will help in the design of a reliable and safe medical device that is in conformance with the international regulations with respect to medical devices[MD18]. Therefore, this work addresses the efficient use of QNX RTOS instead of Linux RTOS for the medical devices, and highlights the advantages offered by QNX in improving the overall quality of the final product. 1.2 Objective of the thesis Our goal is to implement a Profinet Stack for a QNX real-time operating system(RTOS) medical device, porting the previous Linux RTOS system. The QNX RTOS, for the field of medical devices, must ensure the stability, safety and reliability of the system. As medical devices

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    92 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us