Experimental Physics and Industrial Control System
hi, Jeff, medm is built with that 2003-03-12 base cvs snapshot. And there is no such kind of problems using caEventRate <PV>.
I find what result in this problem. When I build medm with baseR3.14.0beta2 and baseR3.14.1, there will be no this problem.
So I think it's the base3.14 cvs snapshot 2003-03-12 that causes this problem. But unfortunately, when I use the last two base3.14 cvs snapshots(20030323 and 20030326), they cann't be compiled or run correctly, respectively. (By the way, my target architecture is i386-rtems. ) So I'm not sure whether you've fixed this unknown reason which are causing this medm problem untill now. I make sure that it is NOT my configuration or settings in base3.14-cvs-snapshot-20030312 which result in this medm problem.
And it seems to me that there are another serious problem in all current version of baseR3.14* when using i386-rtems. To be more clear, I will describe this problem in another seperate email.
regards,
Shao Ming-chao
----- Original Message -----
From: "Jeff Hill" <[email protected]>
> Is your MEDM compiled and linked with this 2003-03-12 base
> snapshot? Do you see this problem when the "caEventRate <PV
> name>" is run from the 2003-03-12 base snapshot?
>
> Jeff
- References:
- RE: medm unable to contact CA repeater after 50 tries Jeff Hill
- Navigate by Date:
- Prev:
"assert (!plink->value.pv_link.pvt)" failed Feng, Shuchen
- Next:
ca client cannot connect server M.C.Shao
- 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: medm unable to contact CA repeater after 50 tries Jeff Hill
- Next:
problem with SNC/SEQ Version 1.9.2.Beta12 Oleg Makarov
- 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