What is Control System or Framework General purpose

What is “Control System” or “Framework”? General purpose of control system – need to control a lot of equipment from remote

What is “Control System” or “Framework”? We need a “Network” to connect instruments and controller

Small system In case the number of target instruments are limited, simple program can do everything. This is true for small laboratory.

Control Framework We need a control framework in case many instruments, programs, developers, operators, . . Tight communication and organic linkage between components are required.

If we want to add a “New” instument Need same “Language” and “Communication Protocol” with existing environment.

In reality Commercial product does not support EPICS or Tango framework in many cases. We need to develop support them.

In case of EPICS IOC (Input/Output Controller) manage hardware – IOC: VME, PC, PLC, software, etc. . . – Need special code depends on each device Field Busses Target PC RS 232 C GPIB, etc Device ADC DAC DIO IOC CPU Device VME, c. PCI CAMAC, etc Device PLC Device

EPICS : Communication Need to communicate with standard protocol between presentation layer and IOC layer. – Presentation Layer : Server process, Archiver, GUI, etc – Independent from each device Presentation Server Operator Console Archive Network Field Bus Target Dev. PC RS 232 C GPIB, etc Device ADC DAC DIO IOC CPU Device VME, c. PCI CAMAC, etc Device PLC Device

EPICS : Communication Protocol Channel Access protocol (PV, Process Variable)のやりとりをする – Network transparent. Distributed system. – CA protocol is used between IOCs Presentation Server Operator Console Archiver CA Ethernet Field Busses Target Dev. CPU PC RS 232 C GPIB, etc Device ADC DAC DIO IOC CA Device VME, c. PCI CAMAC, etc Device PLC Device

When you buy an instrument on the market If the device has an embedded ioc, we have nothing to do! CA Ethernet EPICS IOC embedded Device Just power on, plug to the network, and the instruments speak/listen CA protocol In reality, very few instuments understand EPICS or Tango. Accelerator research is very small field on the market.

for example : RS 232 C device Media converter (RS 232 C Ethernet) are often used – Need to put media converter near to the device – Distance between IOC and Device can be very long CA Ethernet Socket IOC Media Converter Ethernet Device USB RS 232, RS 422, RS 485, etc Socket protocol are used between IOC and M. C. “Steam Device”

Example commercial product • Serial-Ethernet Converter (Media Converter) Socket RS 232 M. C. Device RS 485 M. C. Device PC/IOC Ethernet M. C. Device Device Many company produces similar product. So many variety of the price and functionality. 2, 4, 8, 16 port, etc. Photo from http: //japan. moxa. com/

EPICS + Media Converter soft IOC on the server computer. – IOC is a kind of “Protocol Converter” Logical Description Physical Description Software IOC CA Client CA Ethernet Channel Access DB Access IOC Database Stream Device Socket I/O Socket Ethernet IOC Linux Server Channel Access DB Access IOC Database Stream Device Socket I/O CA Client CA Socket Ethernet Serial-Ether Conv. RS 232 C Device

Disadvantage of the media converter • Tend to increase network traffic • You need to mange a session between IOC and media converter. – For example: Initialize Socket protocol, reconnect, etc – You don’t need to care for CA protocol. (already defined) Software IOC Linux Server Channel Access DB Access IOC Database Stream Device Socket I/O Socket Session Management (depends on the device) Serial-Ether変換 RS 232 C Device CA Client CA Traffic Ethernet not a problem for slow serial.

not an ideal solution, but better than media converter We want a “small” device server attached to the device CA Ethernet Device Server Device USB RS 232, etc

Comparison of configuration A) Client B) Client C) D) Client EPICS IOC embedded Device CA Ethernet IOC IOC Device Server Socket Media Ethernet. Converter Socket Ethernet Device USB RS 232, etc Device

wait. . . Is there any differences between Linux PC and Device Server? – – Basically no difference Price, Size, Power consumption, TCO (Total cost of ownership), etc Hardware support for long time Consider these requirement to select the base hardware CA CA Ethernet Device Server Linux PC RS 232, USB, etc RS 232, USB, PCI board etc Device Ethernet Device

Candidates Credit-Card size board Arduino Raspberry Pi (model B) Beagle. Bone Black Raspberry Pi (model B+)

Candidates (1) [Ras. Pi 3 is not listed in this table] Beagle. Bone Black(Rev. C) Raspberry Pi (Model. B) Arduino Uno CPU TI AM 3359 (ARM Cortex-A 8) Broadcom BCM 2835 (ARM 11) Atmel ATMega 328 Speed 1 GHz 700 MHz 16 MHz RAM 512 MB DDR 3 L@400 MHz 512 MB SDRAM@400 MHz 2 KB Storage Onboard e. MMC 4 GB micro. SD slot 32 KB Flash I/O(GPIO) 65 8 20 ADC 7 n/a 8 Ethernet 10/100 x 1 n/a OS Debian(default) Angstrome Linux Fedora etc Raspbian(Debian) Pidora(Fedora) ARCH linux etc n/a Size [mm] 86. 4 x 53. 3 85. 6 x 54 75 x 53. 3 Price 6, 500 3, 940 3, 024