On 10/26/23 04:02, Jörn Dreyer via Tech-talk wrote:
Hello,
while converting an application from pva to pvxs I ran into a strange problem that I could not solve.
I added pvxs to an IOC and observed a strange error from pvxput telling that the requested PV is seen on two ports of the host running my IOC: at 5075 and something > 30000.
After some fighting with the startup script, I figured out that I still had pva (qsrv) in my IOC included. After removing it, the error disapeared,
Were you only seeing the warning message, or were you seeing differences in behavior?
fyi. so far I have ensured that both QSRV versions can coexist with only this warning.
However, I am considering ending this after PVA links are added to QSRV2.
but still I get an error that I can not write the variable.
Error St13runtime_error: Unable to assign value from "0"
when using pvxput pv:name 0. It perfectly works with pvput! Realy strange. I have no clue whats going wrong.
pvxput is not yet a replacement for pvput. I am recommending that end users continue
with pvput for the time being.
When pvxput gets an equivalent level of "polish", I will add an build option to
install it also with the "pvput" name.
- References:
- pvxs configuration problem Jörn Dreyer via Tech-talk
- Navigate by Date:
- Prev:
RE: Display Builder Web Runtime HTML pages CAOUEN Loïc via Tech-talk
- Next:
workQPanic-Kernel work queue overflow while attempting async communication and thereafter initializing tyGSOctalModule with vxWorks Mrinal Bera via Tech-talk
- 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:
pvxs configuration problem Jörn Dreyer via Tech-talk
- Next:
Display Builder Web Runtime HTML pages Hasan SANSAR via Tech-talk
- 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
|