I’m actually creating a support module rather than an IOC, so I don’t have much control over what kind of IOC will use the module. I’m more interested in why/how things behave the way they do, and if I’m
doing something wrong or not.
The support module is an intermediary between PV’s and data in caching servers like Redis. So I’m doing some mapping between many of the EPICS DB types and Redis types.
Am I repeating any existing work? I did some searching and didn’t find any such project, but since we’re here, does anyone know of anything like this already done?
From:
Kasemir, Kay <kasemirk at ornl.gov>
Date: Wednesday, July 31, 2024 at 9:41 AM
To: Dave Bracey <dbracey at fnal.gov>, Jure Varlec <jure.varlec at cosylab.com>, tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: Truncated LSO
[EXTERNAL] – This message is from an external sender
Build PVXS from
https://github.com/epics-base/pvxs
As a result you’ll have the new C++ PVXS library, command line tools pvxget, pvxmonitor, … and the softIocPVX mentioned by Jure
From:
Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Dave Bracey via Tech-talk <tech-talk at aps.anl.gov>
Date: Wednesday, July 31, 2024 at 10:36 AM
To: Jure Varlec <jure.varlec at cosylab.com>, tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: [EXTERNAL] Re: Truncated LSO
Thank you Jure.
Can anyone point to any examples of this in github, etc?
From:
Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Jure Varlec via Tech-talk <tech-talk at aps.anl.gov>
Date: Wednesday, July 31, 2024 at 1:07 AM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: Truncated LSO
[EXTERNAL] – This message is from an external sender
Hi,
You need to build your IOC with a recent version of PVXS. This will serve records over PVAccess using the newer QSRV2, which handles the lsi record the way one would expect. For a quick test, use softIocPVX that comes with the PVXS module.
Best,
Jure
On 7/31/24 03:09, Di Wang via Tech-talk wrote:
> Caution: This email originated from outside of Cosylab.
>
>
> Hi Dave,
>
> You can try "Long String Field Modifier $" for your purpose.
> Doc:
https://urldefense.proofpoint.com/v2/url?u=https-3A__urldefense.us_v3_-5F-5Fhttps-3A__epics.anl.gov_base_R7-2D0_8-2Ddocs_doxygen_filters.html-5F-5F-3B-21-21G-5FuCfscf7eWS-21cnuappWtgqPWAx1TPmDXqDhMvigKvWKoFp2iYWd5Q8WjhwPeqNIiUSy188XGNI75gNbTE1TS62BgbrFUQfin8Q-24&d=DwIFaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=-F5ElEx0xTIzUkth_6VDnd86lqN2rUgF0GIN-S3DMY4&m=Xn75GgSD2-0TaZTBSx7cTI_D6Y97mxBbdtDKRTxRKIgpIPFC92DM9cKU25y7iPGi&s=t96MOnUvNpcx3RU-Fh_W450kiz2TYdznvXX2pzN7D74&e=
>
> $ caput -S plain.VAL$ "this is a string longer than forty characters"
> Old : plain.VAL$
> New : plain.VAL$ this is a string longer than forty characters
>
> $ caget -S plain.VAL$
> plain.VAL$ this is a string longer than forty characters
>
> I am also curious about how to do it through PV Access though...
>
> Cheers,
> Di
>
>> Date: Tue, 30 Jul 2024 17:53:23 +0000
>> From: Dave Bracey <dbracey at fnal.gov>
>> To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
>> Subject: Truncated LSO
>>
>> I'm using an lso record and my string gets truncated to 40 chars:
>>
>> record(lso, "plain_lso")
>> {
>> field(SIZV, 256)
>> }
>> $ pvput plain_lso "This is a string longer than forty characters"
>> Old : <undefined> INVALID DRIVER UDF
>> New : 2024-07-30 12:45:33.238 "This is a string longer than forty char"
>> $ pvget plain_lso
>> plain_lso 2024-07-30 12:45:33.238 "This is a string longer than forty char"
>>
>> What am I doing wrong here?
>
|
