Experimental Physics and
Industrial Control System

[email protected] (Rozelle Wright) · Thu, 16 Feb 95 07:34:55 MST

> From [email protected] Wed Feb 15 15:40:07 1995
> Return-Path: <[email protected]>
> Date: Wed, 15 Feb 1995 14:38:50 -0800
> Subject: EPICS 3.12 questions
> To: [email protected]
> Reply-To: [email protected]
> X-Envelope-To: [email protected]
> Content-Transfer-Encoding: 7BIT
> Content-Length: 1739
> X-Lines: 45
> 
> I'm trying to upgrade my EPICS 3.11.1 applications to run under 3.12.0.  In
> building the database, I made a short report under 3.11 dct and created a new
> database using v1.15 dct under 3.12.  Then I modified from text file with the
> short report I made.  Then I sf2db to generate a .db file which is loaded by
> dbLoadRecords after default.dctsdr is loaded by dbLoad.  The dbLoadRecords
> results in:
> Cannot set field TEVL to a
> Cannot set field ELVL to b
> Cannot set field TVVL to c
> Cannot set field TTVL to d
> Cannot set field FTVL to e
> Cannot set field FFVL to f
> Cannot set field TEVL to a
> Cannot set field ELVL to b
> Cannot set field TVVL to c
> Cannot set field TTVL to d
> Cannot set field FTVL to e
> Cannot set field FFVL to f
> Cannot set field TEVL to a
> Cannot set field ELVL to b
> Cannot set field TVVL to c
> Cannot set field TTVL to d
> Cannot set field FTVL to e
> Cannot set field FFVL to f
> Cannot set field TEVL to a
> Cannot set field ELVL to b
> Cannot set field TVVL to c
> Cannot set field TTVL to d
> Cannot set field FTVL to e
> Cannot set field FFVL to f
> It turns out that these are my mbbi records and it appears that hex values are
> no longer allowed for these fields, even though dct now shows a 0x in front of
> each value and allows you to enter these values.  However, dct won't let me put 
> in leading zeros to try and solve this problem.  If somebody's got a fix, could
> we please have it?
> 
> Secondly, perhaps I've missed it somewhere (in which case please point me in
> the right direction), but I haven't seen a translation tool to convert OPIs,
> either .dl or .adl files from 1.16 edd/dm to 2.0 edd/dm.  What do I need to do
> to bring up my old displays?  I really hope I don't have to redraw them.
> 
> Any help is greatly appreciated!
> 
> 	Thanks,
> 		Ric
> 

The 3.11 dct put out a short report with no 0x in front of
the hex values for mbbi's and mbbo's.

The new dct in 3.12 will read the old style reports and
will report the new style ones with 0x in front.

I would use the batch processing capabilities of dct.
If you type 
dct help
it will tell you what these are.

For example, if your short report were named junk.sr and you wanted to
produce a database called junk.database, you could use the 3.12 dct and
type
dct -c junk
dct -m junk -i junk.sr
dct -r junk -o newjunk.sr

This would create a a new database called junk.database.
Modify it with your short report and then report it out again to newjunk.sr.

newjunk.sr will have the proper 0x in front of all hex values.

We had this same problem using atdb under 3.11 and I modified dct to prefix 
hex values with 0x before we had 3.12 available.
Rozelle Wright

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System