DOCSLIB.ORG

Operating System Linux As Developing and Runtime Platform for Control System of Particle Accelerator

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

OPERATING SYSTEM LINUX AS DEVELOPING AND RUNTIME PLATFORM FOR CONTROL SYSTEM OF PARTICLE ACCELERATOR A.S. Chepurnov, Institute of Nuclear Physics, Moscow State University, 119899, Moscow, Russia F.N. Nedeoglo, D.V. Komissarov, Department of Physics, Moscow State University, 119899, Moscow, Russia Abstract To upgrade old fashion control system of a race track microtron (RTM) injector we have used Linux for the first What operating system to choose is a common problem time in 1996 [1,2]. Single PC under Linux replaced five necessary to solve during development of control system old-styled LSI-11 minicomputers. We ensured that Linux for particle accelerator. It would be very attractive to use is a stable and reliable OS and it could be used in the the same operating system as for development of software control systems more widely after two years of successful components of control system as for runtime both for real- exploitation of the system. So, the Linux was chosen as time and non real-time applications. Remote boot-loading uniform developing and runtime platform for our new capabilities, mature software development tools, and other control system of “industrial style” which is under final advantages of Linux make it very useful for development development now together with newly designed high of software components of modern control system for beam current electron continuous wave linac [3]. particle accelerators. Our experience lets us to propose application of Linux operating system as for non real-time 2 LINUX BASED CONTROL SYSTEM high levels as for real-time middle level of control system. Real-time extension of Linux - RTLinux is used for real- 2.1 General layout of control system. time applications. This choice allowed us to utilize effectively performance of x86 compatible computers, to The control system for the linac consists of two have uniform hardware and software environment. Linux classical levels (Figure. 1) - non-real-time top level and operating system have been used on different levels of real-time front-end level. Both levels use Intel-compatible control system of electron linacs as for gradual upgrading computers. of the old control system as for development of new control system for newly designed compact accelerator. Software drivers for CAN-bus adapters together with DeviceNet library have been developed under Linux. 1 INTRODUCTION Linux operating system (OS) has become more and more popular as dynamically developing modern Unix- like OS. Many of famous hardware and software manufacturers such as IBM, SGI, Oracle, National Instruments and others have support this OS. Linux brings an attractive alternative to operating systems traditionally used in the field of accelerators control. The basic advantages of Linux OS against traditional operating systems are the open developing model and free of charge. There are thousands of developers and testers that take part in the developing of the OS. Open source availability allows anyone to Figure 1. Layout of the control system. implement new features and new applications not from scratch but based on the existing code. Front-end level supports fast control algorithms, Wide spectrum of compilers, high-level programming hardware locking, fast feedback loops, and signal languages, cross-platform libraries, developing tools and conditioning hardware. The basic functions of top level real-time extensions allow to use Linux at all the levels of are bootloading of front-end computers, supporting of the control system as development platform as runtime man-machine interface and providing necessary database environment. capabilities. 1832 Proceedings of EPAC 2000, Vienna, Austria Top level and front-end PCs communicate via Ethernet of writing and reading messages to or from special fibre optic link, to provide galvanic isolation between character device file. The driver can handle up to four levels of control system. CAN-bus-ISA adapters simultaneously. CAN-bus fieldbus is the second key component of our The DeviceNet compliant protocol stack provides Slave control system. DeviceNet was selected as well-defined capabilities for various types of front-end controllers and and consistent version of CAN application layer (CAL). Master capabilities for host personal computer (PC) The CAN-bus-ISA adapter is installed into PC to provide running under Linux OS. computer access to CAN-bus network. Home designed To support the protocol stack for different hardware CAN-bus-ISA adapter for PC is based on Philips SJA1000 platform it was developed in the form of software library CAN-bus controller and provides fast access to the CAN (Figure2) and consists of the following components: controller by direct memory mapping. • the library kernel, • the module with system dependent functions, 2.2 Top level. • the module with interface to CAN-bus. PC compatible computer runs under Linux 2.2.x at the top level of control system. To improve interaction Library API (interface to user code) between operator and accelerator we use knobs-type Library Kernel modules and plan to use touch screen. The module Kernel mechanisms constructed around single-chip micro-controller consists Candrv: interface to CAN of encoder, two lines of high brightness LCD, and four Sysdrv: system specific bus (setup, read_msg, functions (timers, LED) keys with corresponding LEDs. The modules (up to four write_msg) in our case) could be assigned dynamically with any adjustable or controllable parameter of accelerator. The Figure 2. The structure of the DeviceNet library. modules communicate with top level PC via CAN-bus. 2.3 Front-end level. This partitioning scheme ensures portability of our software to platforms with poor resources (micro- At the front-end level the diskless PC runs under Linux controllers) as well as platforms with rich resources such 2.2.x with RTLinux 2.2a (real-time extension of Linux). as PCs. The library kernel contains the protocol stack only Diskless PC boots operating system via BOOTP protocol and interface to the application program. All dependencies from the top-level PC. Then root file system is mounted to particular environments are located in the two other with the help of NFS protocol. parts of the library. So if ones kernel module has been CAN-bus-ISA adapter installed in front-end PC debugged and tested under Linux, it can be used in controls embedded controllers that belonged to a family of DeviceNet compliant devices, developed for other “Smart Devices”--intelligent controllers which support platforms. To port the library to a new platform it is functions of real-time digital feedback control, data necessary to modify system dependent functions (module acquisition and processing [4]. called Sysdrv) and interface to CAN-bus (called Candrv). Various versions of DeviceNet library have been tested 3 SOFTWARE DESIGN ISSUES including Intel-compatible PC under Linux, single-chip micro-controllers from Microchip (PIC16C7x/87x) and Control system software was developed with the GNU DSP from TI (TMS320C2xx ). development tools only under the Linux OS. The GNU C compiler (GCC) with standard GNU C library (GNU LIBC), GNU Debugger (GDB) and Concurrent Version 3.2 Software support of real-time. Control system (CVS) were used. Real-time extension of Linux OS - RTLinux allows 3.1 Software support of CAN-bus. developing software components, which have got hard real-time capability [7]. The real-time processes are CAN-bus is used at both levels of control system. To implemented in RTLinux as lightweight threads and run in ensure high level of compatibility and ability to use as the kernel memory space. RTLinux coexists with Linux home made as “off the shelf” components DeviceNet high OS and Linux kernel operates as separate real-time level protocol for CAN-bus was used [5]. We did not find process with the lowest priority using a virtual machine neither appropriate support of CAN-bus nor DeviceNet layer in RTLinux. software stack under Linux. So, DeviceNet compliant RTLinux version 2 consists of core component and protocol stack and different CAN-bus device drivers were several optional components. The core component is developed [6]. distributed as Linux kernel patch. The core component To support CAN-bus-ISA adapters under the Linux allows registering low interrupt handlers that cannot be kernel a Linux kernel mode driver has been developed. Application software interfaces with the driver by means Proceedings of EPAC 2000, Vienna, Austria 1833 preempted by Linux itself. The optional components Modules of application software watch and control an provide: accelerator through a segment of DSM. Mirroring • pure priority based scheduler, mechanism of DSM segments lied hidden from • set of functions to work with system clock and application software. Software components accessing the timers, segment of DSM, and not responsible for mirroring, might • support for POSIX IO interface know nothing about inter-level communication (read/write/open/close) for real-time device construction and were not concerned with the appearance drivers, of data. This approach ensured rather clear application • real-time FIFOs, that connect a real-time process program interface, which simplified work of programmers and Linux user space process through a special and made possible, the independent development of parts character device file so the Linux process can of application software as mirroring algorithm for read/write to real-time component, different types of hardware. • shared memory between real-time components and Linux processes. 4 CONCLUSION RTLinux uses the loadable kernel module mechanism The newest features of last RTLinux versions such as implemented in Linux OS to load as real-time processes POSIX compatible interfaces appeared since our last as optional components into the memory [8]. publication [3] and our last experience has strengthened Figure 3. Interaction of RTLinux components in control the belief that RTLinux is usable for accelerator control. system software. During the last three years the new control system has Linux User Linux Application Memory Space been developed as a result of our efforts in the fields of Linux OS and CAN-bus applications.
Recommended publications
  • Some Video Games Require a Operating System

    Some Video Games Require a Operating System

    Some Video Games Require A Operating System Playing and woven Hiro never bail his trouncing! Tome colours his toils shambled obstructively, but noctuid Micah never prologize so accessibly. Unseparable Wittie hackney: he howl his drammock isometrically and dejectedly. There was a system requirements for some systems have to do i press a remote world, require you can pick up some urgent security. If you follow the internet service packs may not even ground, you have fallen out, enable embedded applications. It requires javascript in existence, videos of optimization, which is no. Are some systems? Vram do operating system. Sgi needed to some maintainers look around at different processes can. Your pc gamer, require some video games function checks for. Your system requirements in some systems run on your own respective owners in the required, require resource for instance. Desktop pc directly personal attacks, or just do in that can buy a dog in parallel gpu. Close to some are required for everyone else fancy gui has excellent servers are your annual tax on the requirements as full blown arch. Scroll on console or installation in your pc in beautiful places of. We will learn more, some time and capturing tools for bigger game? For residential clients, which disappeared from. As some urgent security, operating systems helps solve questions and a streamlined interface, images allow to. Api for server by default, it are done in more modern operating system? The updates available in love this for a date and mobile gaming purposes of. Fragmentation and secure a member only. Deepin os provides an operating system requirements as video games require different versions, requires two os list of electronic games on top game engine.
  • NESO LT Core Block Diagram NESO LT CPU Type I.MX 257 Core Class ARM 926

    NESO LT Core Block Diagram NESO LT CPU Type I.MX 257 Core Class ARM 926

    TECHNICAL SPECIFICATION SOLUTIONS THAT COMPLETE! NESO LT Single Board Computer CPU RS-485 CAN NESO LT core Block Diagram NESO LT CPU Type i.MX 257 Core Class ARM 926 ARM 9 Single Board Computer Driver Core Clock 400 MHz 24V/Digital Out i.MX25 4-pole Molex Features 16 KB for Instruktion and data caches Step Down Converter RTC Accuracy: +/- 30 ppm at 25°C GPIO2 DISP0 DAT0 Display RGB Memory 40-pole FFC PMIC Power TSC NAND Flash 256MByte NAND Flash RAM Standard 128 MByte DDR-SDRAM PWM-1 Backlight Battery GPIO-2 Driver Micro SD Card Slot 4 bit MicroSD (HC) CR1220 Operating Systems Battery Supported OS Windows CE 6.0, Linux Yocto PCT Interface RTC RC 1 I2C-3 6-pole FFC Communication Interfaces Digital I/O 1x Digital Out (0.7 A) RS-232 UART-1 Transceiver USBPHY1 Internal USB Network 1x 10/100 Mbit/s Ethernet (RJ-45) 5-pole STL RS-232/RS-485 RS-485 / CAN Fieldbus 1x RS-485 (Half 1x CAN (ISO/DIS 12-pole Molex RS-485 UART-3 duplex) 11898) Transceiver USB-OTG USBPHY1 RS-232 1x RS-232 (RX/TX/CTS/RTS) Flex Type AB CAN CAN Synchronous SPI (10 MBit/s) up to 12 chip selects; I²C, Keypad Keypad USB Serial Interfaces Matrix keypad up to 8 x 8 USBPHY2 20-pole JST Port Type A High-Speed USB 2.0 1x 12 Mbit/s Full Speed Host Micro-SD-Card 1x 480 Mbit/s High Speed OTG ESDHC2 Internal Audio Connector 10-pole Molex Audio Speaker output 1x speaker (connector), 1.0 W RMS (8Ω) UART-4 Audio I2C-2 S/PDIF AUDMUX Expansion Audio Internal 1x speaker connectors parallel to external Codec SPI1 30-pole FFC ESDHC2 output, Line In, Line Out, MIC In owire_LINE Display and Touch Line Out Display Interface TTL up to 24 bit (RGB) Audio EIM SDRAM Touch Interface 4-wire analog resistive; PCAP I²C 2x Speaker Amplifier 2-pole JST NAND Backlight Interface 42.5 mA Backlight drives EMI NANDF Flash Device Dimensions RJ-45 Ethernet W x H x D 113.8 x 18.0 x 47.3 mm FEC Jack Phy Weight 51g Power Supply Supply Voltage Nom.
  • Allgemeines Abkürzungsverzeichnis

    Allgemeines Abkürzungsverzeichnis

    Allgemeines Abkürzungsverzeichnis L.
  • IO-Link Instead of Fieldbus

    IO-Link Instead of Fieldbus

    APPLICATIONS SENSOR TECHNOLOGY IO-Link Instead of Fieldbus Laempe Mössner Sinto GmbH uses IO-Link in a new core shooter machine and achieves shorter cycle times with Turck’s QR24-IOL IO-Link encoder “When I first read about it, I thought: please don’t add the few manufacturers of core shooters worldwide. The another fieldbus system. Today I know that IO-Link isn’t machines produce sand cores for metal casting. If, for a fieldbus but quite the opposite. In many areas, example, the casting of an engine block is required, IO-Link means for us the end of bus systems because it cores are placed inside the casting mold to later makes communication simple once again,” explains produce the cavities of the engine. The cores are “shot” Tobias Lipsdorf, controller programmer at foundry from a binder sand mixture with compressed air into a machinery manufacturer Laempe Mössner Sinto mold – the core box – at a high speed between 0.3 and GmbH. When the engineer talks about the IO-Link 0.5 seconds. The mold mixture is then hardened in the intelligent communication standard, you get a sense of closed core box using process gas or heat and can then genuine enthusiasm – so too with his colleague Andre be removed. After casting, the binder loses its hard- Klavehn, who is responsible for the electrical planning. ness due to the heat from the filled melt. The cores The two of them jointly redesigned the electrical disintegrate, the sand can be removed from the cast, planning of the new machine generation and imple- leaving behind the required internal contour.
  • An Introduction to Integrated Process and Power Automation

    An Introduction to Integrated Process and Power Automation

    Power Up Your Plant An introduction to integrated process and power automation Jeffrey Vasel ABB, Inc. June 30, 2010 Rev 1 Abstract This paper discusses how a single integrated system can increase energy efficiency, improve plant uptime, and lower life cycle costs. Often referred to as Electrical Integration, Integrated Process and Power Automation is a new system integration architecture and power strategy that addresses the needs of the process and power generation industries. The architecture is based on Industrial Ethernet standards such as IEC 61850 and Profinet as well as Fieldbus technologies. Emphasis is placed on tying the IEC 61850 substation automation standard with the process control system. The energy efficiency gains from integration are discussed in a power generation use case. In this use case, energy efficiency is explored with integrated variable frequency drives, improved visibility into power consumption, and energy efficiency through faster plant startup times. Demonstrated capital expenditure (CAPEX) savings is discussed in a cost avoidance section where a real world example of wiring savings is described. Lastly, a power management success story from a major oil and gas company, Petrobras, is discussed. In this case, Petrobras utilized integrated process and power automation to lower CAPEX, operational expenditure (OPEX), and explore future energy saving opportunities. Executive Summary Document ID: 3BUS095060 Page 1 Date: 6/30/2010 © Copyright 2010 ABB. All rights reserved. Pictures, schematics and other graphics contained herein are published for illustration purposes only and do not represent product configurations or functionality. Executive Summary Document ID: 3BUS095060 Page 2 Date: 6/30/2010 © Copyright 2010 ABB.
  • Android Operating System

    Android Operating System

    Software Engineering ISSN: 2229-4007 & ISSN: 2229-4015, Volume 3, Issue 1, 2012, pp.-10-13. Available online at http://www.bioinfo.in/contents.php?id=76 ANDROID OPERATING SYSTEM NIMODIA C. AND DESHMUKH H.R. Babasaheb Naik College of Engineering, Pusad, MS, India. *Corresponding Author: Email- [email protected], [email protected] Received: February 21, 2012; Accepted: March 15, 2012 Abstract- Android is a software stack for mobile devices that includes an operating system, middleware and key applications. Android, an open source mobile device platform based on the Linux operating system. It has application Framework,enhanced graphics, integrated web browser, relational database, media support, LibWebCore web browser, wide variety of connectivity and much more applications. Android relies on Linux version 2.6 for core system services such as security, memory management, process management, network stack, and driver model. Architecture of Android consist of Applications. Linux kernel, libraries, application framework, Android Runtime. All applications are written using the Java programming language. Android mobile phone platform is going to be more secure than Apple’s iPhone or any other device in the long run. Keywords- 3G, Dalvik Virtual Machine, EGPRS, LiMo, Open Handset Alliance, SQLite, WCDMA/HSUPA Citation: Nimodia C. and Deshmukh H.R. (2012) Android Operating System. Software Engineering, ISSN: 2229-4007 & ISSN: 2229-4015, Volume 3, Issue 1, pp.-10-13. Copyright: Copyright©2012 Nimodia C. and Deshmukh H.R. This is an open-access article distributed under the terms of the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.
  • Chapter 1: Introduction

    Chapter 1: Introduction

    Chapter 1: Introduction Operating System Concepts Silberschatz, Galvin and Gagn Objectives To provide a grand tour of the major operating systems components To provide coverage of basic computer system organization Operating System Concepts 1.2 Silberschatz, Galvin and Gagne What is an Operating System? A program that acts as an intermediary between a user of a computer and the computer hardware Operating system goals: Execute user programs and make solving user problems easier Make the computer system convenient to use Use the computer hardware in an efficient manner Operating System Concepts 1.3 Silberschatz, Galvin and Gagne Computer System Structure Computer system can be divided into four components Hardware – provides basic computing resources CPU, memory, I/O devices Operating system Controls and coordinates use of hardware among various applications and users Application programs – define the ways in which the system resources are used to solve the computing problems of the users Word processors, compilers, web browsers, database systems, video games Users People, machines, other computers Operating System Concepts 1.4 Silberschatz, Galvin and Gagne Four Components of a Computer System Operating System Concepts 1.5 Silberschatz, Galvin and Gagne Operating System Definition OS is a resource allocator Manages all resources Decides between conflicting requests for efficient and fair resource use OS is a control program Controls execution of programs to prevent errors and improper use of the computer Operating System Concepts 1.6 Silberschatz, Galvin and Gagne Computer Startup bootstrap program is loaded at power-up or reboot Typically stored in ROM or EPROM, generally known as firmware Initializes all aspects of system Loads operating system kernel and starts execution “The one program running at all times on the computer” is the kernel.
  • Kbox Tech Spac Sheet

    Kbox Tech Spac Sheet

    KBox Family IOT GATEWAYS/ EMBEDDED BOX PC About Kontron – Member of the S&T Group IOT GATEWAYS/EMBEDDED BOX PC The KBox A-series is designed for a variety of applications in The KBox B-Series is based on Kontron’s mini-ITX mother- Kontron’s KBox C-Series is designed for the industrial control The KBox E-Series provides rugged, fanless, sealed and the industrial environment. It comprises intelligent IoT gate- cabinet environment. Based on COMe modules the KBox compact design for easy embedded into a custom housing or Kontron is a global leader in IoT/Embedded Computing Technology ways for edge analytics or remote monitoring as well as CPUs. Kontron’s KBox B-Series can be used for various C-Series is highly scalable and ensures simple upgrades as a stand-alone device, to fulfill requirements for fog portfolio of secure hardware, middleware and services for Internet of systems for control and process optimization. All systems applications such as medical, gaming, process control, - computing, edge analytics and real time control in a variety of Things (IoT) and Industry 4.0 applications. With its standard products feature a fanless design which ensures a significantly pro- wherever high performance is needed. tions guarantees mounting even when space is limited. industrial applications. and tailor-made solutions based on highly reliable state-of-the-art . embedded technologies, Kontron provides secure and innovative d e ; z i e t longed lifespan and high system availability. With its broad range of interfaces, various storage capabili- n a g applications for a variety of industries.
  • Mac OS X: an Introduction for Support Providers

    Mac OS X: an Introduction for Support Providers

    Mac OS X: An Introduction for Support Providers Course Information Purpose of Course Mac OS X is the next-generation Macintosh operating system, utilizing a highly robust UNIX core with a brand new simplified user experience. It is the first successful attempt to provide a fully-functional graphical user experience in such an implementation without requiring the user to know or understand UNIX. This course is designed to provide a theoretical foundation for support providers seeking to provide user support for Mac OS X. It assumes the student has performed this role for Mac OS 9, and seeks to ground the student in Mac OS X using Mac OS 9 terms and concepts. Author: Robert Dorsett, manager, AppleCare Product Training & Readiness. Module Length: 2 hours Audience: Phone support, Apple Solutions Experts, Service Providers. Prerequisites: Experience supporting Mac OS 9 Course map: Operating Systems 101 Mac OS 9 and Cooperative Multitasking Mac OS X: Pre-emptive Multitasking and Protected Memory. Mac OS X: Symmetric Multiprocessing Components of Mac OS X The Layered Approach Darwin Core Services Graphics Services Application Environments Aqua Useful Mac OS X Jargon Bundles Frameworks Umbrella Frameworks Mac OS X Installation Initialization Options Installation Options Version 1.0 Copyright © 2001 by Apple Computer, Inc. All Rights Reserved. 1 Startup Keys Mac OS X Setup Assistant Mac OS 9 and Classic Standard Directory Names Quick Answers: Where do my __________ go? More Directory Names A Word on Paths Security UNIX and security Multiple user implementation Root Old Stuff in New Terms INITs in Mac OS X Fonts FKEYs Printing from Mac OS X Disk First Aid and Drive Setup Startup Items Mac OS 9 Control Panels and Functionality mapped to Mac OS X New Stuff to Check Out Review Questions Review Answers Further Reading Change history: 3/19/01: Removed comment about UFS volumes not being selectable by Startup Disk.
  • Foundation Fieldbus Overview

    Foundation Fieldbus Overview

    FOUNDATIONTM Fieldbus Overview Foundation Fieldbus Overview January 2014 370729D-01 Support Worldwide Technical Support and Product Information ni.com Worldwide Offices Visit ni.com/niglobal to access the branch office Web sites, which provide up-to-date contact information, support phone numbers, email addresses, and current events. National Instruments Corporate Headquarters 11500 North Mopac Expressway Austin, Texas 78759-3504 USA Tel: 512 683 0100 For further support information, refer to the Technical Support and Professional Services appendix. To comment on National Instruments documentation, refer to the National Instruments website at ni.com/info and enter the Info Code feedback. © 2003–2014 National Instruments. All rights reserved. Legal Information Warranty NI devices are warranted against defects in materials and workmanship for a period of one year from the invoice date, as evidenced by receipts or other documentation. National Instruments will, at its option, repair or replace equipment that proves to be defective during the warranty period. This warranty includes parts and labor. The media on which you receive National Instruments software are warranted not to fail to execute programming instructions, due to defects in materials and workmanship, for a period of 90 days from the invoice date, as evidenced by receipts or other documentation. National Instruments will, at its option, repair or replace software media that do not execute programming instructions if National Instruments receives notice of such defects during the warranty period. National Instruments does not warrant that the operation of the software shall be uninterrupted or error free. A Return Material Authorization (RMA) number must be obtained from the factory and clearly marked on the outside of the package before any equipment will be accepted for warranty work.
  • Hacking the Industrial Network

    Hacking the Industrial Network

    Hacking the industrial network A White Paper presented by: Phoenix Contact P.O. Box 4100 Harrisburg, PA 17111-0100 Phone: 717-944-1300 Fax: 717-944-1625 Website: www.phoenixcontact.com © PHOENIX CONTACT 1 Hacking the Industrial Network Is Your Production Line or Process Management System at Risk? The Problem Malicious code, a Trojan program deliberately inserted into SCADA system software, manipulated valve positions and compressor outputs to cause a massive natural gas explosion along the Trans-Siberian pipeline, according to 2005 testimony before a U.S. House of Representatives subcommittee by a Director from Sandia National Laboratories.1 According to the Washington Post, the resulting fireball yielded “the most monumental non-nuclear explosion and fire ever seen from space.”2 The explosion was subsequently estimated at the equivalent of 3 kilotons.3 (In comparison, the 9/11 explosions at the World Trade Center were roughly 0.1 kiloton.) According to Internet blogs and reports, hackers have begun to discover that SCADA (Supervisory Control and Data Acquisition) and DCS (Distributed Control Systems) are “cool” to hack.4 The interest of hackers has increased since reports of successful attacks began to emerge after 2001. A security consultant interviewed by the in-depth news program, PBS Frontline, told them “Penetrating a SCADA system that is running a Microsoft operating system takes less than two minutes.”5 DCS, SCADA, PLCs (Programmable Logic Controllers) and other legacy control systems have been used for decades in power plants and grids, oil and gas refineries, air traffic and railroad management, pipeline pumping stations, pharmaceutical plants, chemical plants, automated food and beverage lines, industrial processes, automotive assembly lines, and water treatment plants.
  • FOUNDATION Fieldbus Design Considerations Reference Manual

    FOUNDATION Fieldbus Design Considerations Reference Manual

    Reference Manual PlantPAx Process Automation System: FOUNDATION Fieldbus Design Considerations Catalog Numbers 1757-FFLDx, 1757-FFLDCx Important User Information Solid-state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://www.rockwellautomation.com/literature/) describes some important differences between solid-state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid-state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable. In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment. The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams. No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual. Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited. Throughout this manual, when necessary, we use notes to make you aware of safety considerations. WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.