Writing device drivers¶
There are two ways a device driver can be written. Each has advantages/disadvantages, so you have to decide which is the most appropriate for your situation.
Native Erlang Driver¶
Native drivers should be used when the hardware is accessed over the network because it's very easy to do network communications using Erlang.
We also provide a C++ Driver API so drivers can be written in C++.
These are the various drivers that have been written for the framework. We encourage pure Erlang drivers, but there are cases where a C/C++ driver is necessary. In those cases, the
cdev API is used to interface with the Erlang framework.
- LXI Power Supply Driver
- Agilent Acquiris Digitizer
- Test Driver for Arrays
- Beam Trail Driver
- Bira 1253 Power Supply Driver
- CAMAC Driver
- Channel Access
- EPICS to ACNET Bridging Driver
- Galil 21x3 motion control
- IPG Laser Ethernet Controller
- Local Applications
- MODBUS Driver
- Multiwire Scanner
- picomotor Ethernet Controller 8752
- PLC Direct Driver
- TOMCO Power Supply Driver