Experimental Physics and
Industrial Control System

Kristi Luchini <[email protected]> · Wed, 25 Apr 2001 15:22:52 -0700

Hi, 

Tim Mooney wrote:
> 
> re...,
> 
> > gdct lives!
> 
> Yay!
> 
> > ...
> >
> > Use of ivtools fixes a long-standing bug in editing text fields under
> > gdct.  ...
> 
> The most irritating bug in gdct for us has been its tendency to replace
> record_name.<field_name> with record_name.VAL in links.  (The graphical
> link continues to point to the correct field, but the .db file doesn't
> agree.)  I have never determined the circumstances under which this
> occurs, because the replacement in not apparent until you try to run
> the .db file.  Have you guys run into this problem?
> 
Yes, I've come across this bug recently. In my case it seems to occur
when connecting a db link (DBF_INLINK) field of a pv to an External
Link. In particular, when
the external link name uses a macro at the end of the pv name. For
example

 An external link with the name specified as 
    TR01:CAENV265:C$(M):ARY$(CH)         (special record with fields
ARY0-ARY7)
               or
    TR01:CAENV265:C$(M):VAL$(CH)         (special record..with fields
VAL0-VAL7)       

http://www.slac.stanford.edu/grp/cd/soft/nlcdev/tarf/images/fast_adc.gif

You need to make sure that after a connection is drawn to an external
link
that you check the db link (DBF_INLINK) field and/or the .db file after
a save, but before
exiting gdct.

      - Regards,
         Kristi Luchini

> Tim Mooney ([email protected]) (630)252-5417
> Beamline Controls & Data Acquisition Group
> Advanced Photon Source, Argonne National Lab

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System