Experimental Physics and
Industrial Control System

"Dudley, David" <[email protected]> · Wed, 3 Dec 2014 14:26:58 +0000

BTW: Referring to chapter 6 of the AppDevGuide.

One of the things I've had to change on a couple of the records was right before I changed them, it seems.
Page 102: pp_value - shows the allowed values are NO/YES, yet the dbdExpand program aborts if the field isn't set to TRUE/FALSE.

Later-  

David Dudley
Controls Engineer III
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824, USA
Tel. 517-908-7133
Email: [email protected]

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Johnson
Sent: Tuesday, December 02, 2014 6:39 PM
To: [email protected]
Subject: Re: EPICS 3.15.1

Hi David,

On 12/02/2014 03:22 PM, Dudley, David wrote:
> Downloaded and compiled fine.
> 
> Most of the modules we're using just needed some minor 'tweaking' to 
> get working fine (actually, only about 3-4 needed changes, rest worked 
> with no problems).

Thanks for the feedback there. We don't expect 3.15 to be a simple drop-in replacement for 3.14.12, so you should thoroughly test your IOCs after upgrading since there have been behaviour changes to several of the record types which could affect application functionality.

> I'm having problems with the dbdExpand.pl program.  It keeps telling 
> me that I have duplicated records when I try to build my IOCS, with a 
> record name of blank.

Can you post a copy/paste showing the output from make with both the commands being executed and the error messages you're getting. Also show us the content of your configure/RELEASE file so we can see which modules and the versions you're trying to build.

The new dbdExpand.pl script in 3.15 is stricter than the 3.14 dbExpand program was about what it will accept, so you will probably have to adjust the DBD files in your modules to get them to work with 3.15.

The errors you're seeing must be duplicate recordtype (not record
instance) definitions, which are no longer allowed. This means that a device support generally shouldn't have any 'include "xRecord.dbd"'
statements inside its published DBD files, but it is allowed to use empty record type declarations instead of including the record definition if all it's doing is defining device support layers:

myDevice.dbd:
    recordtype(ai) {}    # optional declaration
    device(ai, INST_IO, myAiDset, "My device")

When it comes to an IOC's DBD file though, the full recordtype definition must be included before any empty recordtype declarations are seen.

This stuff is not terribly well documented yet, I'm still working on that...

- Andrew
--
People everywhere confuse what they read in newspapers with news.
-- A. J. Liebling

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System