Experimental Physics and
Industrial Control System

Steven M Beard <[email protected]> · Fri, 23 Jul 1999 11:03:17 +0100 (BST)

I have come across an interesting problem with EPICS records that allow
you to specify a user-defined function. Suppose, for the sake of this
example, you take a genSub record with an integer output

     +--------+
     | genSub |
     |        +-OUTA-
     |        |
     +--------+
     FTVA: LONG
     SNAM: myFunction

and your user defined function writes to its VALA field like this

     long myFunction( struct genSubRecord *pgensub )
     {
         *(long *)pgensub->vala = value;
         return 0;
     }

You can connect the OUTA link to a field in another record and that field
will be set to your value when the genSub processes. This works ok, but
now suppose you have arranged your database with multiple copies of the
genSub record all writing to the same database field, like this

     +--------+
     | genSub |
     |        +-OUTA-------+
     |        |            |
     +--------+            |
     FTVA: LONG            |
     SNAM: myFunction      |
                           |
     +--------+            |              +--------+
     | genSub |            |              | longin |
     |        +-OUTA-------+----------VAL-+        |
     |        |            |              +--------+
     +--------+            |
     FTVA: LONG            |
     SNAM: myFunction      |
                           |
     +--------+            |
     | genSub |            |
     |        +-OUTA-------+
     |        |
     +--------+
     FTVA: LONG
     SNAM: myFunction

Now all of a sudden you have three copies of myFunction all sharing the
same resource, and if the genSub records happen to process at the same
time there can be a clash. I had a database like this and saw some very
strange behaviour (a different record generating an "illegal choice"
message when I tried to write a valid value to one of its inputs) until I
explicitly protected pgensub->vala with a mutex semaphore. I have the
following questions: 

1) How can myFunction tell that the output field it is writing to is
   connected to a shared resource? This depends on how the database has
   been connected up.

2) Can EPICS handle such resource sharing transparently? It would be a lot
   easier to deal with if shared links like this are recognised and
   protected with a mutex semaphore automatically.

   I am using EPICS 3.12.2. Is the behaviour different in EPICS 3.13?

3) Am I missing something? Is there a technique I should be following
   to protect the shared resource automatically (e.g. using the PHAS field
   or something similar)?

Any advice gratefully received.

Steven

==============================================================================
Steven Beard
UK Astronomy Technology Centre
Royal Observatory                  Tel.   : +44 (0)131 668 8253 (direct)
Blackford Hill                              +44 (0)131 668 8100 (switchboard)
Edinburgh EH9 3HJ                  Fax.   : +44 (0)131 668 1130
UK                                 E-mail : [email protected]       (Internet) 
                                   WWW    : http://www.roe.ac.uk/smbwww/

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System