$ wget -O - http://panda-service.gsi.de/debian/repo-key.pub | apt-key add -
deb http://panda-service.gsi.de/debian wheezy main
deb http://panda-service.gsi.de/debian jessie main
deb http://panda-service.gsi.de/debian wheezy rpi
$ apt-get update && apt-get install <your-package-name>
In principal these packages should also work with Ubuntu, but this was not explicitly tested!
The Packages follow the Debian Packages Policy and File System Hierachy Standard. This means:
All packages still work exactly the same, as if build from source. When editing a configure/RELEASE file
just use the corresponding path in /etc/epics of the needed modules.
When creating a new IOC, the libraries and DBD files of the modules available in these repositories
will be used automatically, when their corresponding variables are defined in configure/RELEASE.
| Package | Version | Description | main | rpi | ||
|---|---|---|---|---|---|---|
| amd64 | i386 | armhf | armhf | |||
| activemq-cpp-library | ||||||
| libactivemq-cpp-dev | 3.8.3-2 | ActiveMQ C++ library CMS (stands for C++ Messaging Service) is a JMS-like API for C++ for interfacing with Message Brokers such as Apache ActiveMQ. CMS helps to make your C++ client code much neater and easier to follow. To get a better feel for CMS try the API Reference. ActiveMQ-CPP is a client only library, a message broker such as Apache ActiveMQ is still needed for your clients to communicate. This package contains the headers and tool needed for developing |
✓ | ✓ | ✗ | ✗ |
| libactivemq-cpp-doc | 3.8.3-2 | ActiveMQ C++ library CMS (stands for C++ Messaging Service) is a JMS-like API for C++ for interfacing with Message Brokers such as Apache ActiveMQ. CMS helps to make your C++ client code much neater and easier to follow. To get a better feel for CMS try the API Reference. ActiveMQ-CPP is a client only library, a message broker such as Apache ActiveMQ is still needed for your clients to communicate. Documentation for ActiveMQ C++ Library |
✓ | ✓ | ✓ | ✗ |
| libactivemq-cpp18 | 3.8.3-2 | ActiveMQ C++ library CMS (stands for C++ Messaging Service) is a JMS-like API for C++ for interfacing with Message Brokers such as Apache ActiveMQ. CMS helps to make your C++ client code much neater and easier to follow. To get a better feel for CMS try the API Reference. ActiveMQ-CPP is a client only library, a message broker such as Apache ActiveMQ is still needed for your clients to communicate. This package contains the shared libraries |
✓ | ✓ | ✗ | ✗ |
| libactivemq-cpp18-dbg | 3.8.3-2 | ActiveMQ C++ library CMS (stands for C++ Messaging Service) is a JMS-like API for C++ for interfacing with Message Brokers such as Apache ActiveMQ. CMS helps to make your C++ client code much neater and easier to follow. To get a better feel for CMS try the API Reference. ActiveMQ-CPP is a client only library, a message broker such as Apache ActiveMQ is still needed for your clients to communicate. Debug symbols for libactivemq-cpp |
✓ | ✓ | ✗ | ✗ |
| alarmnotifications | ||||||
| alarmnotifications | 1.0.1-1 | EPICS AlarmNotifications AlarmNotifications is a framework that listens to the Control System Studio Alarm Server calles BEAST via Java Message Service (JMS) and alerts the users in the lab, at the office desktop and via e-mail that something is wrong. This main package contains the configuration utility and readme files |
✓ | ✓ | ✗ | ✗ |
| alarmnotifications-doc | 1.0.1-1 | EPICS AlarmNotifications documentation AlarmNotifications is a framework that listens to the Control System Studio Alarm Server calles BEAST via Java Message Service (JMS) and alerts the users in the lab, at the office desktop and via e-mail that something is wrong. This package contains the code and configuration documentation created by Doxygen from the source code of the application. |
✓ | ✓ | ✓ | ✗ |
| an-daemon | 1.0.1-1 | EPICS AlarmNotifications AlarmNotifications is a framework that listens to the Control System Studio Alarm Server calles BEAST via Java Message Service (JMS) and alerts the users in the lab, at the office desktop and via e-mail that something is wrong. This package contains the daemon flavour that can draw the staff's attention to a problem by activating a flashlight in the laboratory and/or send e-mails to a mailing list. |
✓ | ✓ | ✗ | ✗ |
| an-desktop | 1.0.1-1 | EPICS AlarmNotifications AlarmNotifications is a framework that listens to the Control System Studio Alarm Server calles BEAST via Java Message Service (JMS) and alerts the users in the lab, at the office desktop and via e-mail that something is wrong. This package contains the legacy version of the desktop flavour that uses the QSystemTrayIcon interface to interact with the user. It should work on any desktop environment but provides less flexibility than the modern version an-desktop-kde4. |
✓ | ✓ | ✗ | ✗ |
| an-desktop-kde4 | 1.0.1-1 | EPICS AlarmNotifications AlarmNotifications is a framework that listens to the Control System Studio Alarm Server calles BEAST via Java Message Service (JMS) and alerts the users in the lab, at the office desktop and via e-mail that something is wrong. This package contains the modern version of the desktop flavour that uses the StatusNotifierItem API to interact with the user. As the name indicates it uses the implementation in the KDE4 Platform library of the StatusNotifierItem, but this does not mean that the user has to run KDE Plasma Workspaces, because other desktop environments also support the StatusNotifierItem API. |
✓ | ✓ | ✗ | ✗ |
| asyn | ||||||
| asyn-dev | 4.26-2~wheezy | Files needed to develop EPICS IOCs with ASYN support asynDriver is a general purpose facility for interfacing device specific code to low level communication drivers. A primary target for asynDriver is for EPICS IOC device support, but other than using the EPICS build system and libCom library, most of the code was designed so it can be used outside of an EPICS IOC. Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| asyn-doc | 4.26-2~wheezy | ASYN documentation asynDriver is a general purpose facility for interfacing device specific code to low level communication drivers. A primary target for asynDriver is for EPICS IOC device support, but other than using the EPICS build system and libCom library, most of the code was designed so it can be used outside of an EPICS IOC. Documentation for ASYN |
✓ | ✓ | ✓ | ✓ |
| libasyn4.26 | 4.26-2~wheezy | AsynDriver libraries for clients and servers asynDriver is a general purpose facility for interfacing device specific code to low level communication drivers. A primary target for asynDriver is for EPICS IOC device support, but other than using the EPICS build system and libCom library, most of the code was designed so it can be used outside of an EPICS IOC. This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libasyn4.26-dbg | 4.26-2~wheezy | Asyn debug symbols asynDriver is a general purpose facility for interfacing device specific code to low level communication drivers. A primary target for asynDriver is for EPICS IOC device support, but other than using the EPICS build system and libCom library, most of the code was designed so it can be used outside of an EPICS IOC. Debug symbols for EPICS ASYN shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| cagateway | ||||||
| cagateway | 2.0.6.0-2~wheezy | EPICS CA gateway deamon The Gateway is both a Channel Access Server and Channel Access Client that provides a means for many clients to access a process variable while making only one connection to the server that owns the process variable. It also provides additional access security beyond that on the server. It thus protects critical servers while providing possibly restricted access to needed process variables. The Gateway typically runs on a machine with multiple network cards, and the clients and the server may be on different subnets. CA gateway deamon |
✓ | ✓ | ✗ | ✗ |
| cagateway-doc | 2.0.6.0-2~wheezy | EPICS CA gateway documentation The Gateway is both a Channel Access Server and Channel Access Client that provides a means for many clients to access a process variable while making only one connection to the server that owns the process variable. It also provides additional access security beyond that on the server. It thus protects critical servers while providing possibly restricted access to needed process variables. The Gateway typically runs on a machine with multiple network cards, and the clients and the server may be on different subnets. Documentation for EPICS CA gateway |
✓ | ✓ | ✓ | ✗ |
| devgpio | ||||||
| devgpio-dev | 1.0.2-2~wheezy | Files needed to develop EPICS IOCs with devGpio support Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✗ | ✗ | ✓ | ✓ |
| devgpio-doc | 1.0.2-2~wheezy | devGpio documentation Documentation for devGpio |
✗ | ✗ | ✗ | ✓ |
| libdevgpio1 | 1.0.2-2~wheezy | EPICS dev support for GPIO This package contains host system shared libraries for clients and IOCs. |
✗ | ✗ | ✓ | ✓ |
| libdevgpio1-dbg | 1.0.2-2~wheezy | devGpio debug symbols Debug symbols for EPICS ASYN shared libraries and utilities. |
✗ | ✗ | ✓ | ✓ |
| devsnmp | ||||||
| devsnmp-dev | 1.0.9-1~wheezy | Files needed to develop EPICS IOCs with SNMP support Net-SNMP support for EPICS Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| devsnmp-doc | 1.0.9-1~wheezy | SNMP documentation Net-SNMP support for EPICS Documentation for SNMP |
✓ | ✓ | ✓ | ✓ |
| libdevsnmp1.0 | 1.0.9-1~wheezy | DevSNMP libraries for clients and servers Net-SNMP support for EPICS This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libdevsnmp1.0-dbg | 1.0.9-1~wheezy | DevSNMP libraries debug symbols Net-SNMP support for EPICS Debug symbols for EPICS SNMP shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| drvasyncan | ||||||
| drvasyncan-dev | 3.0.1-1~wheezy | Files needed to develop EPICS IOCs with drvAsynCan support EPICS device support for: ISEG EHS/EDS modules, Wiener VME crate remote control(via CANbus), Temperature and Humidity Monitoring board for PANDA (THMP), PANDA-EMC light pulser, TMCM142 1-axis stepper controller/driver(via CANbus) Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| libdrvasyncan3 | 3.0.1-1~wheezy | CANBus Support libraries for clients and servers EPICS device support for: ISEG EHS/EDS modules, Wiener VME crate remote control(via CANbus), Temperature and Humidity Monitoring board for PANDA (THMP), PANDA-EMC light pulser, TMCM142 1-axis stepper controller/driver(via CANbus) This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libdrvasyncan3-dbg | 3.0.1-1~wheezy | CANBus Support libraries debug symbols EPICS device support for: ISEG EHS/EDS modules, Wiener VME crate remote control(via CANbus), Temperature and Humidity Monitoring board for PANDA (THMP), PANDA-EMC light pulser, TMCM142 1-axis stepper controller/driver(via CANbus) Debug symbols for EPICS drvAsynCan shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| epics-base | ||||||
| epics-catools | 3.14.12.5-3~wheezy | Command line utilities for EPICS The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. EPICS utilities such as caget and caput as well as the caRepeater daemon. |
✓ | ✓ | ✓ | ✓ |
| epics-dev | 3.14.12.5-3~wheezy | Files needed to develop new EPICS applications The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| epics-doc | 3.14.12.5-3~wheezy | EPICS documentation The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. Documentation for EPICS Base |
✓ | ✓ | ✓ | ✓ |
| epics-perl | 3.14.12.5-3~wheezy | Perl bindings for EPICS The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. Perl bindings for EPICS |
✓ | ✓ | ✓ | ✓ |
| ioclogserver | 3.14.12.5-3~wheezy | Log recording daemon for EPICS IOCS The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. The IOC log server listens for network log messages sent from IOC. This is used by the caputlog support module to collect messages relating to PV value changes. |
✓ | ✓ | ✓ | ✓ |
| libepics3.14.12 | 3.14.12.5-3~wheezy | EPICS Base libraries for clients and servers The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libepics3.14.12-dbg | 3.14.12.5-3~wheezy | EPICS base libraries debug symbols The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. Debug symbols for EPICS shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| epics-ioc | ||||||
| epics-files | 1.0.5-2~wheezy | EPICS db and proto files Collection of database and protocol files for EPICS IOCs EPICS databases and protocol files. |
✓ | ✓ | ✓ | ✓ |
| iocpandadcs | 1.0.5-2~wheezy | Generic EPICS IOC for PANDA DCS This IOC uses every device support module in the PANDA Debian Repository. Additionally it provides dallas-1-wire support for the Raspberry Pi computer and the subroutines needed for the old calibration of the THMP. This package contains the executable and config file for the IOC. |
✓ | ✓ | ✓ | ✓ |
| isegioc | 1.0.5-2~wheezy | EPICS IOC for iseg HV modules This IOC uses the isegHAL to communicate with high voltage modules from iseg Spezialelektronik GmbH. This package contains the executable and config file for the IOC. |
✓ | ✓ | ✓ | ✓ |
| epics-modbus | ||||||
| epics-libmodbus2.7 | 2.7-3~wheezy | EPICS Modbus libraries for clients and servers MODBUS is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides client/server communication between devices connected on different types of buses or networks. It is typically used for communication with I/O systems, including Programmable Logic Controllers (PLCs). This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| epics-libmodbus2.7-dbg | 2.7-3~wheezy | EPICS Modbus libraries debug symbols MODBUS is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides client/server communication between devices connected on different types of buses or networks. It is typically used for communication with I/O systems, including Programmable Logic Controllers (PLCs). Debug symbols for EPICS Modbus shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| epics-modbus-dev | 2.7-3~wheezy | Files needed to develop EPICS IOCs with Modbus support MODBUS is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides client/server communication between devices connected on different types of buses or networks. It is typically used for communication with I/O systems, including Programmable Logic Controllers (PLCs). Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| epics-modbus-doc | 2.7-3~wheezy | EPICS ModBus documentation MODBUS is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides client/server communication between devices connected on different types of buses or networks. It is typically used for communication with I/O systems, including Programmable Logic Controllers (PLCs). Documentation for EPICS Modbus |
✓ | ✓ | ✓ | ✓ |
| iseghal | ||||||
| iseghalclientexample | 1.0.1.6-1~wheezy | isegHAL client example The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. Command line application to access isegHAL. |
✓ | ✓ | ✓ | ✓ |
| iseghalserver | 1.0.1.6-1~wheezy | isegHAL server The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. Daemon process collecting data from iseg HV modules. |
✓ | ✓ | ✓ | ✓ |
| libiseghal-client-dev | 1.0.1.6-1~wheezy | Files needed to develop clients for isegHAL The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. Libraries and headers needed to develop clients for isegHAL. |
✓ | ✓ | ✓ | ✓ |
| libiseghal-client1 | 1.0.1.6-1~wheezy | iseg HAL client library The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. This package contains host system shared libraries for clients. |
✓ | ✓ | ✓ | ✓ |
| libiseghal-client1-dbg | 1.0.1.6-1~wheezy | iseg HAL client lib debug symbols The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. This package contains host system shared libraries for clients. |
✓ | ✓ | ✓ | ✓ |
| libiseghal1 | 1.0.1.6-1~wheezy | iseg HAL library The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. This package contains host system shared libraries for the server. |
✓ | ✓ | ✓ | ✓ |
| libsocketcan | ||||||
| libsocketcan-dev | 0.0.10+git20140721-3~foo | library to control some basic functions in SocketCAN from userspace This package provides development files for libsocketcan. |
✓ | ✓ | ✓ | ✓ |
| libsocketcan-doc | 0.0.10+git20140721-3~foo | library to control some basic functions in SocketCAN from userspace This package provides documentation for libsocketcan. |
✓ | ✓ | ✓ | ✓ |
| libsocketcan2 | 0.0.10+git20140721-3~foo | library to control some basic functions in SocketCAN from userspace This userspace library allows one to do common configure/control tasks on SocketCAN interface. |
✓ | ✓ | ✓ | ✓ |
| seq | ||||||
| libseq2.2 | 2.2.2-1~wheezy | State Notation Language and Sequencer libraries The State Notation Language (SNL), is a domain specific programming language that smoothly integrates with and depends and builds on EPICS base. This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libseq2.2-dbg | 2.2.2-1~wheezy | State Notation Language and Sequencer libraries The State Notation Language (SNL), is a domain specific programming language that smoothly integrates with and depends and builds on EPICS base. Debug symbols for EPICS seq shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| seq-dev | 2.2.2-1~wheezy | Files needed to develop new EPICS state machines The State Notation Language (SNL), is a domain specific programming language that smoothly integrates with and depends and builds on EPICS base. Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| seq-doc | 2.2.2-1~wheezy | SEQ documentation The State Notation Language (SNL), is a domain specific programming language that smoothly integrates with and depends and builds on EPICS base. Documentation for SEQ |
✓ | ✓ | ✓ | ✓ |
| stream | ||||||
| libstream2.6 | 2.6-3~wheezy | StreamDevice libraries for clients and servers Generic EPICS device support for devices with "byte stream" based communication interfaces. Supports devices that can be controlled by sending and receiving strings including non-printable characters and even null-bytes This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libstream2.6-dbg | 2.6-3~wheezy | StreamDevice libraries debug symbols Generic EPICS device support for devices with "byte stream" based communication interfaces. Supports devices that can be controlled by sending and receiving strings including non-printable characters and even null-bytes Debug symbols for EPICS STREAM shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| stream-dev | 2.6-3~wheezy | Files needed to develop EPICS IOCs with STREAM support Generic EPICS device support for devices with "byte stream" based communication interfaces. Supports devices that can be controlled by sending and receiving strings including non-printable characters and even null-bytes Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| stream-doc | 2.6-3~wheezy | StreamDevice documentation Generic EPICS device support for devices with "byte stream" based communication interfaces. Supports devices that can be controlled by sending and receiving strings including non-printable characters and even null-bytes Documentation for StreamDevice |
✓ | ✓ | ✓ | ✓ |
| Package | Version | Description | main | rpi | ||
|---|---|---|---|---|---|---|
| amd64 | i386 | armhf | armhf | |||
| asyn | ||||||
| asyn-dev | 4.28-1+deb8u1 | Files needed to develop EPICS IOCs with ASYN support asynDriver is a general purpose facility for interfacing device specific code to low level communication drivers. A primary target for asynDriver is for EPICS IOC device support, but other than using the EPICS build system and libCom library, most of the code was designed so it can be used outside of an EPICS IOC. Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| asyn-doc | 4.28-1+deb8u1 | ASYN documentation asynDriver is a general purpose facility for interfacing device specific code to low level communication drivers. A primary target for asynDriver is for EPICS IOC device support, but other than using the EPICS build system and libCom library, most of the code was designed so it can be used outside of an EPICS IOC. Documentation for ASYN |
✓ | ✓ | ✓ | ✓ |
| libasyn4 | 4.28-1+deb8u1 | AsynDriver libraries for clients and servers asynDriver is a general purpose facility for interfacing device specific code to low level communication drivers. A primary target for asynDriver is for EPICS IOC device support, but other than using the EPICS build system and libCom library, most of the code was designed so it can be used outside of an EPICS IOC. This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libasyn4-dbg | 4.28-1+deb8u1 | Asyn debug symbols asynDriver is a general purpose facility for interfacing device specific code to low level communication drivers. A primary target for asynDriver is for EPICS IOC device support, but other than using the EPICS build system and libCom library, most of the code was designed so it can be used outside of an EPICS IOC. Debug symbols for EPICS ASYN shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| devgpio | ||||||
| devgpio-dev | 1.0.4-1+deb8u1 | Files needed to develop EPICS IOCs with devGpio support Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| devgpio-doc | 1.0.4-1+deb8u1 | devGpio documentation Documentation for devGpio |
✓ | ✓ | ✓ | ✓ |
| libdevgpio1 | 1.0.4-1+deb8u1 | EPICS dev support for GPIO This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libdevgpio1-dbg | 1.0.4-1+deb8u1 | devGpio debug symbols Debug symbols for EPICS ASYN shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| devsnmp | ||||||
| devsnmp-dev | 1.0.0.0-1+deb8u1 | Files needed to develop EPICS IOCs with SNMP support Net-SNMP support for EPICS Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| devsnmp-doc | 1.0.0.0-1+deb8u1 | SNMP documentation Net-SNMP support for EPICS Documentation for SNMP |
✓ | ✓ | ✓ | ✓ |
| libdevsnmp1 | 1.0.0.0-1+deb8u1 | DevSNMP libraries for clients and servers Net-SNMP support for EPICS This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libdevsnmp1-dbg | 1.0.0.0-1+deb8u1 | DevSNMP libraries debug symbols Net-SNMP support for EPICS Debug symbols for EPICS SNMP shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| drvasyncan | ||||||
| drvasyncan-dev | 3.1.1-1+deb8u2 | Files needed to develop EPICS IOCs with drvAsynCan support EPICS device support for: ISEG EHS/EDS modules, Wiener VME crate remote control(via CANbus), Temperature and Humidity Monitoring board for PANDA (THMP), PANDA-EMC light pulser, TMCM142 1-axis stepper controller/driver(via CANbus) Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| libdrvasyncan3 | 3.1.1-1+deb8u2 | CANBus Support libraries for clients and servers EPICS device support for: ISEG EHS/EDS modules, Wiener VME crate remote control(via CANbus), Temperature and Humidity Monitoring board for PANDA (THMP), PANDA-EMC light pulser, TMCM142 1-axis stepper controller/driver(via CANbus) This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libdrvasyncan3-dbg | 3.1.1-1+deb8u2 | CANBus Support libraries debug symbols EPICS device support for: ISEG EHS/EDS modules, Wiener VME crate remote control(via CANbus), Temperature and Humidity Monitoring board for PANDA (THMP), PANDA-EMC light pulser, TMCM142 1-axis stepper controller/driver(via CANbus) Debug symbols for EPICS drvAsynCan shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| drvasyni2c | ||||||
| drvasyni2c-dev | 1.0.0-1+deb8u1 | Files needed to develop EPICS IOCs with asynI2C support asynI2CDriver is a general purpose facility for interfacing an I2C bus. Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| drvasyni2c-doc | 1.0.0-1+deb8u1 | asynI2C documentation asynI2CDriver is a general purpose facility for interfacing an I2C bus. Documentation for asynI2C |
✓ | ✓ | ✓ | ✓ |
| libdrvasyni2c1 | 1.0.0-1+deb8u1 | AsynI2CDriver libraries for clients and servers asynI2CDriver is a general purpose facility for interfacing an I2C bus. This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libdrvasyni2c1-dbg | 1.0.0-1+deb8u1 | AsynI2C debug symbols asynI2CDriver is a general purpose facility for interfacing an I2C bus. Debug symbols for EPICS ASYN shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| epics-base | ||||||
| epics-catools | 3.14.12.5-4+deb8u2 | Command line utilities for EPICS The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. EPICS utilities such as caget and caput as well as the caRepeater daemon. |
✓ | ✓ | ✓ | ✓ |
| epics-dev | 3.14.12.5-4+deb8u2 | Files needed to develop new EPICS applications The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| epics-doc | 3.14.12.5-4+deb8u2 | EPICS documentation The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. Documentation for EPICS Base |
✓ | ✓ | ✓ | ✓ |
| epics-perl | 3.14.12.5-4+deb8u2 | Perl bindings for EPICS The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. Perl bindings for EPICS |
✓ | ✓ | ✓ | ✓ |
| ioclogserver | 3.14.12.5-4+deb8u2 | Log recording daemon for EPICS IOCS The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. The IOC log server listens for network log messages sent from IOC. This is used by the caputlog support module to collect messages relating to PV value changes. |
✓ | ✓ | ✓ | ✓ |
| libepics3.14.12 | 3.14.12.5-4+deb8u2 | EPICS Base libraries for clients and servers The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libepics3.14.12-dbg | 3.14.12.5-4+deb8u2 | EPICS base libraries debug symbols The Experimental Physics and Industrial Control System is a collection of tools, libraries and applications for creating a distributed soft real-time control systems. Debug symbols for EPICS shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| epics-ioc | ||||||
| epics-files | 1.0.7-1+deb8u2 | EPICS db and proto files Collection of database and protocol files for EPICS IOCs EPICS databases and protocol files. |
✓ | ✓ | ✓ | ✓ |
| iocpandadcs | 1.0.7-1+deb8u2 | Generic EPICS IOC for PANDA DCS This IOC uses every device support module in the PANDA Debian Repository. Additionally it provides dallas-1-wire support for the Raspberry Pi computer and the subroutines needed for the old calibration of the THMP. This package contains the executable and config file for the IOC. |
✓ | ✓ | ✓ | ✓ |
| isegioc | 1.0.7-1+deb8u2 | EPICS IOC for iseg HV modules This IOC uses the isegHAL to communicate with high voltage modules from iseg Spezialelektronik GmbH. This package contains the executable and config file for the IOC. |
✓ | ✓ | ✓ | ✓ |
| epics-modbus | ||||||
| epics-libmodbus2 | 2.7-4+deb8u1 | EPICS Modbus libraries for clients and servers MODBUS is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides client/server communication between devices connected on different types of buses or networks. It is typically used for communication with I/O systems, including Programmable Logic Controllers (PLCs). This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| epics-libmodbus2-dbg | 2.7-4+deb8u1 | EPICS Modbus libraries debug symbols MODBUS is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides client/server communication between devices connected on different types of buses or networks. It is typically used for communication with I/O systems, including Programmable Logic Controllers (PLCs). Debug symbols for EPICS Modbus shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| epics-modbus-dev | 2.7-4+deb8u1 | Files needed to develop EPICS IOCs with Modbus support MODBUS is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides client/server communication between devices connected on different types of buses or networks. It is typically used for communication with I/O systems, including Programmable Logic Controllers (PLCs). Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| epics-modbus-doc | 2.7-4+deb8u1 | EPICS ModBus documentation MODBUS is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides client/server communication between devices connected on different types of buses or networks. It is typically used for communication with I/O systems, including Programmable Logic Controllers (PLCs). Documentation for EPICS Modbus |
✓ | ✓ | ✓ | ✓ |
| iseghal | ||||||
| iseghalclientexample | 1.1.1.4-2+deb8u1 | isegHAL client example The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. Command line application to access isegHAL. |
✓ | ✓ | ✓ | ✓ |
| iseghalserver | 1.1.1.4-2+deb8u1 | isegHAL server The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. Daemon process collecting data from iseg HV modules. |
✓ | ✓ | ✓ | ✓ |
| libiseghal-client-dev | 1.1.1.4-2+deb8u1 | Files needed to develop clients for isegHAL The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. Libraries and headers needed to develop clients for isegHAL. |
✓ | ✓ | ✓ | ✓ |
| libiseghal-client1 | 1.1.1.4-2+deb8u1 | iseg HAL client library The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. This package contains host system shared libraries for clients. |
✓ | ✓ | ✓ | ✓ |
| libiseghal-client1-dbg | 1.1.1.4-2+deb8u1 | iseg HAL client lib debug symbols The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. This package contains host system shared libraries for clients. |
✓ | ✓ | ✓ | ✓ |
| libiseghal1 | 1.1.1.4-2+deb8u1 | iseg HAL library The iseg Hardware Abstraction Layer (isegHAL) offers a string based application interface - API. The data collection from the iseg high voltage modules is done in background. All communication hand shake is handledby the isegHAL. This package contains host system shared libraries for the server. |
✓ | ✓ | ✓ | ✓ |
| seq | ||||||
| libseq2 | 2.2.3-3+deb8u1 | State Notation Language and Sequencer libraries The State Notation Language (SNL), is a domain specific programming language that smoothly integrates with and depends and builds on EPICS base. This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libseq2-dbg | 2.2.3-3+deb8u1 | State Notation Language and Sequencer libraries The State Notation Language (SNL), is a domain specific programming language that smoothly integrates with and depends and builds on EPICS base. Debug symbols for EPICS seq shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| seq-dev | 2.2.3-3+deb8u1 | Files needed to develop new EPICS state machines The State Notation Language (SNL), is a domain specific programming language that smoothly integrates with and depends and builds on EPICS base. Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| seq-doc | 2.2.3-3+deb8u1 | SEQ documentation The State Notation Language (SNL), is a domain specific programming language that smoothly integrates with and depends and builds on EPICS base. Documentation for SEQ |
✓ | ✓ | ✓ | ✓ |
| stream | ||||||
| libstream2 | 2.6c-1+deb8u1 | StreamDevice libraries for clients and servers Generic EPICS device support for devices with "byte stream" based communication interfaces. Supports devices that can be controlled by sending and receiving strings including non-printable characters and even null-bytes This package contains host system shared libraries for clients and IOCs. |
✓ | ✓ | ✓ | ✓ |
| libstream2-dbg | 2.6c-1+deb8u1 | StreamDevice libraries debug symbols Generic EPICS device support for devices with "byte stream" based communication interfaces. Supports devices that can be controlled by sending and receiving strings including non-printable characters and even null-bytes Debug symbols for EPICS STREAM shared libraries and utilities. |
✓ | ✓ | ✓ | ✓ |
| stream-dev | 2.6c-1+deb8u1 | Files needed to develop EPICS IOCs with STREAM support Generic EPICS device support for devices with "byte stream" based communication interfaces. Supports devices that can be controlled by sending and receiving strings including non-printable characters and even null-bytes Libraries, headers, and utilities needed to develop applications targeted to the host system. |
✓ | ✓ | ✓ | ✓ |
| stream-doc | 2.6c-1+deb8u1 | StreamDevice documentation Generic EPICS device support for devices with "byte stream" based communication interfaces. Supports devices that can be controlled by sending and receiving strings including non-printable characters and even null-bytes Documentation for StreamDevice |
✓ | ✓ | ✓ | ✓ |