Experimental Physics and Industrial Control System
> At first I wanted to suggest you check with the latest stable
sequencer version
> (2.0.12) but this now really looks like CA (or your setup of it) is at
fault.
> The fact that you have the -c option for caput means the client side
uses
> EPICS base 3.14.12, right? What EPICS version runs on the IOC?
At first, we observed the problem with the following configuration.
The sncseq-2.0.12 was executed on a PowerPC (MPC8347E)-based IOC cross-
compiled by a 32-bit linux-x86 host architecture (CentOS 4.6). Base-3.14.
9
was used for the IOC.
The other IOC which held the soft record was PowerPC 440-based (Virtex5)
cross-compiled by a 32-bit linux-x86 architecture (WindRiver Workbech 2.
0).
Base-3.14.9 was used for the IOC.
Then, I found the "values shortened to a multiple of 256"-problem when
SYNC/
ASYNC-option was specified. I guessed that the cause was in miss-match
of
versions between sequencer and the base. So, I down-graded the sequencer
from
sncseq-2.0.12 to snc-2.0.11. But the result was the same.
Next, I executed seq-2.0.11 with base-3.14.9 on a linux-x86-based IOC
self-
compiled by CentOS 4.6. The soft record was placed on the PowerPC (
MPC8347E)-
based IOC running base-3.14.9. Then, I found that only a value of zero
can be
put to the soft record when SYNC-potion was specified.
> Values shortened to a multiple of 256, this sounds like a byte order
problem.
> Knowing the exact type and version of the OS used on both client and
server
> side might help to solve this.
I think it is the most probable cause of the problem. I'll investigate
the
problem keeping your suggestions in mind.
Thanks a lot for your advice.
Jun-ichi
----- Original Message -----
> Am Freitag 25 Februar 2011, um 15:01:32 schrieben Sie:
> > Now, I have to bring up a problem I'm facing on pvPut.
> >
> > The attached files are a simple .stt program that repeatedly puts
> > a value into a PV, and a .db file including the PV (a soft longout
> > record with its all fields initialized with their default values).
> >
> > If the .stt progrm runs on an IOC where the soft record resides,
> > it works just fine for all of the following three cases:
> >
> > 1. pvPut(var)
> > 2. pvPut(var, SYNC)
> > 3. pvPut(var, ASYNC).
> >
> > However, if the .stt program runs on an IOC to put a value into
> > the soft record placed on another IOC, only pvPut(var) works fine.
> >
> > pvPut(var, SYNC) and pvPut(var, ASYNC) behave strangely. It's very
> > hard to explain in short sentences since it varies from case to
> > case.
> >
> > For example, the value actually put into the record is shortened
> > to a multiple of 256 that is mostly close to the value the .stt
> > program tried to put... or ... always zero...
> >
> > At any rate, pvPut(var, SYNC) and pvPut(var, ASYNC) shows exactly
> > the same strange befavior in the situation.
> >
> > I found that "caput -c" also does not work in that situation. So,
> > I guess this problem might be related with Channel Access as the
> > underlying message system.
>
> At first I wanted to suggest you check with the latest stable
sequencer version
> (2.0.12) but this now really looks like CA (or your setup of it) is at
fault.
> The fact that you have the -c option for caput means the client side
uses
> EPICS base 3.14.12, right? What EPICS version runs on the IOC?
>
> Values shortened to a multiple of 256, this sounds like a byte order
problem.
> Knowing the exact type and version of the OS used on both client and
server
> side might help to solve this.
>
> Cheers
> Ben
>
> ________________________________
>
> Helmholtz-Zentrum Berlin für Materialien und Energie GmbH
>
> Mitglied der Hermann von Helmholtz-Gemeinschaft Deutscher
Forschungszentren e.V
>
> Aufsichtsrat: Vorsitzender Prof. Dr. Dr. h.c. mult. Joachim Treusch,
stv. Vorsitzende Dr. Beatrix Vierkorn- Rudolph
> Geschäftsführer: Prof. Dr. Anke Rita Kaysser-Pyzalla, Prof. Dr. Dr. h.
c. Wolfgang Eberhardt, Dr. Ulrich Breuer
>
> Sitz Berlin, AG Charlottenburg, 89 HRB 5583
>
> Postadresse:
> Hahn-Meitner-Platz 1
> D-14109 Berlin
>
> http://www.helmholtz-berlin.de
>
- References:
- About pvPut dafault behavior jun-ichi.odagiri
- Re: About pvPut dafault behavior Benjamin Franksen
- Re: About pvPut dafault behavior jun-ichi.odagiri
- Re: About pvPut dafault behavior benjamin . franksen
- Navigate by Date:
- Prev:
Re: About pvPut dafault behavior jun-ichi.odagiri
- Next:
Re: About pvPut dafault behavior jun-ichi.odagiri
- 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: About pvPut dafault behavior jun-ichi.odagiri
- Next:
Re: About pvPut dafault behavior jun-ichi.odagiri
- 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