Experimental Physics and Industrial Control System
|
Title: Re: Breakpoint Tables
I added the tables (I have 3 for the 3 flowmeters in the prototype installation right now). I named them flow1, flow2, flow3 (real original, I know..... I was in a hurry). I added those tables to the menuConvert.dbd file, and rebuilt my IOC.
After adjusting my *.db file to assign LINR on those flowmeters to the appropriate table name, and reloading the IOC, if I do a dbpr on the flowmeter record, it shows that LINR is set to “NO Conversion”. The tables are 15, 16, and 17, and if inside the IOC I set the LINR value to one of those numbers, it returns status that it’s assigned to the right table.
Was I supposed to adjust the indexes of the menu or something to generate those numbers for the load? I don’t get an error when I load the db, but it seems that the symbol sets the LINR value to 0.
I’m almost there... Just one more thing or so... (famous last words ;-).
David
On 12/17/10 1:13 PM, "Dalesio, Leo" <[email protected]> wrote:
It was originally written to create breakpoints from a table of values for each bit pattern. The thermocouple manufacturers used to provide these. mkbkpt allowed people to create a table that was as precise as they needed.
-----Original Message-----
From: [email protected] on behalf of Andrew Johnson
Sent: Fri 12/17/2010 11:22 AM
To: [email protected]
Subject: Re: Breakpoint Tables
Hi David,
On Thursday 16 December 2010 21:06:06 David Dudley wrote:
>
> So....
> The big format in the bpt*.data files, as specified in section 6.17 isn't
> required? And I don't have to run the 'makeBpt' command and the stuff
> that's listed in that section?
You don't have to do that if you have your own way of generating the
breaktable(name){raw, eng, ...} that the IOC can load (see 6.11, although I
suspect you have an older copy of the AppDevGuide with different numbering).
Note that you can load a .dbd file containing break-point table data using
either dbLoadDatabase or dbLoadRecords, and the table data values can be space
or comma-separated.
The makeBpt program described in 6.15 is useful if the calibration data you
have needs to be re-sampled to provide conversions with an acceptable error,
bearing in mind that the IOC code gives you values taken from a straight line
drawn between adjacent data points. You wouldn't need to run makeBpt manually
since that's all taken care of by the build system when you tell it
BPTS += bptXxx.dbd
and give it the data table as described in a file named bptXxx.data.
- Andrew
--
If a man is offered a fact which goes against his instincts, he will
scrutinize it closely, and unless the evidence is overwhelming, he will
refuse to believe it. If, on the other hand, he is offered something
which affords a reason for acting in accordance to his instincts, he
will accept it even on the slightest evidence. -- Bertrand Russell
David
--
"... The Crossbow Project. There's No Defense Like a Good Offense. " - Real Genius (1985)
Don't think it exists? Google the Air Force X-37B project.
- References:
- RE: Breakpoint Tables Dalesio, Leo
- Navigate by Date:
- Prev:
Patch for EDM Crashes on x86_64 Sebastian Marsching
- Next:
RE: Build EPICS 3.14.12 in windows 7 by MS VC++ 2010 Express Wang Xiaoqiang
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Breakpoint Tables Dalesio, Leo
- Next:
Epics driver for Agilent E4980A precision LCR meter Wang Xiaoqiang
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 12 Sep 2012 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|