Hi:
The issue was simply a custom-build archive engine that didn't include the PVManager support for EPICS.
The ArchiveEngine.product lists these dependencies, amongst others: pvmanager, pvmanager.epics, pvmanager.sim, …
If you build an archive engine without pvmanager.epics, in fact no data sources at all, you get the error message
> …. uses the default data source but one was never set.
-Kay
On Sep 17, 2013, at 1:00 AM, "Konrad, Martin" <[email protected]> wrote:
> Hi,
>> java.lang.IllegalArgumentException: Channel emcvme100_fanspd1 uses
>> the default data source but one was never set.
> Try using "epics://pvname" instead of "pvname". Maybe one of the CSS
> developers can give you a hint why epics is not the default (it usually
> should be).
>
> Martin
>
- References:
- Re: RDB archive engine warning messages Konrad, Martin
- Navigate by Date:
- Prev:
RE: A little bit of history: Life before and after EPICS... Paul.gibbons
- Next:
RE: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime Mark Rivers
- 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: RDB archive engine warning messages Konrad, Martin
- Next:
A little bit of history: Life before and after EPICS... Emmanuel Mayssat
- 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·