EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Which version are you using Re: group PV question
From: Timo Korhonen <[email protected]>
To: "Kasemir, Kay" <[email protected]>, EPICS Core Talk <[email protected]>
Date: Mon, 29 Oct 2018 17:23:27 +0000
I took the circle.db from a (much) earlier release and have been editing
it stepwise for my own understanding.
I attach the current state which I used. Please do not consider this as a
fully developed example.

Timo



On 29/10/18 16:57, "[email protected] on behalf of Kasemir,
Kay via Core-talk" <[email protected] on behalf of
[email protected]> wrote:

>Hello:
>
>Related to Timo's group PV question, I'm looking that the circle.db
>that's generated with EPICS base 7.0.1.1 when running makeBaseApp.pl -t
>example.
>
>The structure looks like this, i.e. different from Timo's message:
>
>$ pvinfo training:circle
>CHANNEL  : training:circle
>STATE    : CONNECTED
>ADDRESS  : 160.91.233.125:5075
>structure
>    structure record
>        structure _options
>            uint queueSize
>            boolean atomic
>    epics:nt/NTScalar:1.0 angle
>        double value
>        alarm_t alarm
>            int severity
>            int status
>            string message
>        time_t timeStamp
>            long secondsPastEpoch
>            int nanoseconds
>            int userTag
>        display_t display
>            double limitLow
>            double limitHigh
>            string description
>            string format
>            string units
>        control_t control
>            double limitLow
>            double limitHigh
>            double minStep
>        valueAlarm_t valueAlarm
>            boolean active
>            double lowAlarmLimit
>            double lowWarningLimit
>            double highWarningLimit
>            double highAlarmLimit
>            int lowAlarmSeverity
>            int lowWarningSeverity
>            int highWarningSeverity
>            int highAlarmSeverity
>            double hysteresis
>    epics:nt/NTScalar:1.0 x
>        double value
>        alarm_t alarm
>            int severity
>            int status
>            string message
>        time_t timeStamp
>            long secondsPastEpoch
>            int nanoseconds
>            int userTag
>        display_t display
>            double limitLow
>            double limitHigh
>            string description
>            string format
>            string units
>        control_t control
>            double limitLow
>            double limitHigh
>            double minStep
>        valueAlarm_t valueAlarm
>            boolean active
>            double lowAlarmLimit
>            double lowWarningLimit
>            double highWarningLimit
>            double highAlarmLimit
>            int lowAlarmSeverity
>            int lowWarningSeverity
>            int highWarningSeverity
>            int highAlarmSeverity
>            double hysteresis
>    epics:nt/NTScalar:1.0 y
>        double value
>        alarm_t alarm
>            int severity
>            int status
>            string message
>        time_t timeStamp
>            long secondsPastEpoch
>            int nanoseconds
>            int userTag
>        display_t display
>            double limitLow
>            double limitHigh
>            string description
>            string format
>            string units
>        control_t control
>            double limitLow
>            double limitHigh
>            double minStep
>        valueAlarm_t valueAlarm
>            boolean active
>            double lowAlarmLimit
>            double lowWarningLimit
>            double highWarningLimit
>            double highAlarmLimit
>            int lowAlarmSeverity
>            int lowWarningSeverity
>            int highWarningSeverity
>            int highAlarmSeverity
>            double hysteresis
>
>
>
>The structure basically contains the complete circle:x, circle:y,
>circle:angle record data, while Timo had a much more compact example:
>
>From: [email protected] <[email protected]> on
>behalf of Timo Korhonen <[email protected]>
>Sent: Friday, October 26, 2018 6:45 AM
>Subject: group PV question
>...
>$ pvget circle
>circle
>epics:nt/NTTable:1.0
>    structure record
>        structure _options
>            uint queueSize 0
>            boolean atomic true
>    double angle 279
>    alarm_t alarm NO_ALARM NO_STATUS NO_ALARM
>    time_t timeStamp 2018-10-26T12:35:48.132 0
>    structure value
>        double X 0.156434
>        double Y -0.987688
> 
>
>
>Timo, what are you using to create this?  EPICS base 7.0.1.1? git master?
>Or some older version?
>
>Thanks,
>Kay

Attachment: circle.db
Description: circle.db


References:
group PV question Timo Korhonen
Which version are you using Re: group PV question Kasemir, Kay via Core-talk

Navigate by Date:
Prev: Jenkins build became unstable: epics-7.0 » linux32 #73 APS Jenkins via Core-talk
Next: Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Which version are you using Re: group PV question Michael Davidsaver
Next: pvget -m timeout after first value Kasemir, Kay via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
ANJ, 29 Oct 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·