On 9/21/12 9:33 AM, Wesley Moore wrote:
> Jeff and Dirk - thanks for getting back to me.
>
> I'm familiar with some of the issues that you guys pointed out, they can definitely bite you. While double-checking your suggestions I found that one of the channels that was being monitored came from another vxWorks IOC (mistake on my part). Surprise, surprise...it never has any disconnect issues. Following that lead, I found that the problems seem to be centered around a dynamically assigned pv in one of my two sequencers. When I hard-coded that pv assignment the problems went away. This remains consistent. What's confusing me a bit is that I use dynamic assignment in the working sequencer, I just don't do any reassignments.
>
> Ben - Any known issues with dynamic assignment/reassignment? Perhaps specific to RTEMS?
Hi, Wesley.
There have been a number of bug fixes related to pvAssign. You
can find these in the release notes (just search in the page for
"pvAssign"):
http://www-csr.bessy.de/control/SoftDist/sequencer/Notes.html
What version of the sequencer are you using?
Lewis
- Replies:
- Re: CAC problem between RTEMS and vxWorks Wesley Moore
- References:
- Re: CAC problem between RTEMS and vxWorks Wesley Moore
- Navigate by Date:
- Prev:
Re: CAC problem between RTEMS and vxWorks Wesley Moore
- Next:
Re: CAC problem between RTEMS and vxWorks Wesley Moore
- 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: CAC problem between RTEMS and vxWorks Wesley Moore
- Next:
Re: CAC problem between RTEMS and vxWorks Wesley Moore
- 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
|