Hello,
I have been using epics and python for quite some time now.
Just recently I moved to the excellent pyepics.
The only issue... long type PVs!
I am about to upgrade to the latest version (pyepics 3,0,8) since I am using an older one (3.0.1)
But here is what I see:
epics2@cr1com1 $ caget DMC2183:1:AEncdrPstnLI
DMC2183:1:AEncdrPstnLI -1833
in python:
-------> print(pv.info)
== DMC2183:1:AEncdrPstnLI (long) ==
value = 4294965463
char_value = 4294965463
count = 1
type = long
units = Steps
host = cls1ir-eth0:5064
access = read/write
status = 0
severity = 0
timestamp = 1285131880.264 (2010-09-21 22:04:40.263942)
upper_ctrl_limit = 0
lower_ctrl_limit = 0
upper_disp_limit = 0
lower_disp_limit = 0
upper_alarm_limit = 0
lower_alarm_limit = 0
upper_warning_limit = -7872675053568
lower_warning_limit = 0
PV is internally monitored, with 0 user-defined callbacks:
=============================
Notice the reported value as ...
value = 4294965463
It seems there is an issue with bit ordering.
It works well for double records though.s ;-)
Based on the pdf doc, the maintainer is Matthew Newville at U Chicago.
Is he on the mailing list? Anyone knows how to contact him?
I should have contacted him a long time ago....
Best,
--
Emmanuel
-
Emmanuel
- Replies:
- Re: pyepics bug (need fix asap!) + Matthew Newville? Matt Newville
- Navigate by Date:
- Prev:
Re: vlinac and point release Eric Norum
- Next:
Re: pyepics bug (need fix asap!) + Matthew Newville? Matt Newville
- 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:
Register at http://www.bnl.gov/guv/gis.asp Dalesio, Leo
- Next:
Re: pyepics bug (need fix asap!) + Matthew Newville? Matt Newville
- 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
|