Experimental Physics and
Industrial Control System

Hi,

 

For developing modern age EPICS ‘driver support’ for something like the PI GPIO I would definitely suggest using the asyn module: http://www.aps.anl.gov/epics/modules/soft/asyn/

 

I find the easiest to get going quickly is to use the asynPortDriver C++ class – extend it with the PI GPIO C libraries and your driver can be implemented in just a single class with a few methods. Docs and examples are pretty good in asyn: http://www.aps.anl.gov/epics/modules/soft/asyn/R4-21/asynDriver.html#asynPortDriver

 

Cheers,

Ulrik

 

 

Hello all...

We are exploring the idea of using Raspberry Pi for basic digital IO tasks.  The idea is that we could avoid deploying other IOCs and possibly wasting many other IOC ports.  I have EPICS running on a Raspberry Pi with a test record DB (soft records only) and it is successfully communicating across the network.  I know how to directly access the GPIO pins while on the Pi (through C libraries etc.), but I do not know the first thing about how to get to those pins through EPICS.

Any advice or direction would be much appreciated.  I am relatively new to EPICS development but am experienced with with maintenance of EPICS records and the like.

Regards
Peter

Dr Peter Linardakis

Accelerator Research &Development Engineer

Nuclear Physics | Research School of Physics and Engineering

Australian National University

e: [email protected]

p: (02) 6125 2862

-- 

----------------------------------------

| Dr. Florian Feldbauer                |

|                                      |

| Helmholtz-Institut Mainz /           |

| Johannes Gutenberg-Universität Mainz |

| Johann-Joachim-Becher-Weg 45         |

| D-55128 Mainz                        |

|                                      |

| Office: 01/102                       |

| Phone:  (+49)6131 / 39-27373         |

----------------------------------------