Re: [EXTERNAL] lso record

[Heinz Junkes via Tech-talk <tech-talk at aps.anl.gov>]

Thanks Steve,
Yes, that works. However, in my opinion, none of this is well explained in our documentation. Examples are also missing.
I'll try to write something about this in the next few days, including the DCT field.

Unfortunately, we make it infinitely difficult for beginners to get to grips with Epics. And even I couldn't figure it out today :-(

And if I set the Epics record as described by you


record(lso, "$(user):zone0")
{
    field(SIZV, "64")
    field(DOL, {const:"/sys/devices/virtual/thermal/thermal_zone0/temp”})
    field(PINI, "YES")
}

the result with caget/pvget looks like this (truncated):

pvget ares:zone0
ares:zone0 <undefined>              /sys/devices/virtual/thermal/thermal_zo INVALID DRIVER UDF

epics@ares:~$ pvget ares:zone0
ares:zone0 2024-09-09 19:52:41.690  /sys/devices/virtual/thermal/thermal_zo

epics@ares:~$ caget ares:zone0
ares:zone0                     /sys/devices/virtual/thermal/thermal_zo

I know about VAL$ (is this documented anywhere?):

epics@ares:~$ pvget ares:zone0.VAL$
ares:zone0.VAL$ 2024-09-09 19:52:41.690  [47,115,121,115,47,100,101,118,105,99,101,115,47,118,105,114,116,117,97,108,47,116,104,101,114,109,97,108,47,116,104,101,114,109,97,108,95,122,111,110,101,48,47,116,101,109,112,0]

epics@ares:~$ caget ares:zone0.VAL$
ares:zone0.VAL$ 64 47 115 121 115 47 100 101 118 105 99 101 115 47 118 105 114 116 117 97 108 47 116 104 101 114 109 97 108 47 116 104 101 114 109 97 108 95 122 111 110 101 48 47 116 101 109 112 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Now I'm curious if I want to use this PV as the INPA of an aSubRecord. I'm already worried about ‘cutting it off’ …

Heinz


------------------------------------------------------------------------------
Fritz-Haber-Institut    | Phone:         (+49 30) 8413-4270
Heinz Junkes             | Fax (G3+G4):   (+49 30) 8413-5900
Faradayweg 4-6        | VC: https://zoom.fhi.berlin/junkes
D - 14195 Berlin        | E-Mail:        junkes at fhi-berlin.mpg.de
------------------------------------------------------------------------------

> On 9. Sep 2024, at 18:27, Hartman, Steven <hartmansm at ornl.gov> wrote:
>
> This works . . .
>
> record(lso, "myLSO")
> {
>    field(DOL, {const:"foo"})
> }
>
>
> --
> Steven Hartman
> hartmansm at ornl.gov
>
>
>
>> On Sep 9, 2024, at 11:44 AM, Heinz Junkes via Tech-talk <tech-talk at aps.anl.gov> wrote:
>>
>> Good evening,
>>
>> I have a problem with the lso (long string out) record.
>>
>> When I use it as a replacement for stringout (limited to 41 char),
>>
>> according to the Record reference Manual : "To initialize a string output record it is simplest to set the VAL field directly"
>>
>> record(lso, "$(user):zone0")
>> {
>>    field(VAL, 'blabberblabberblub')
>> }
>>
>>
>> I get the following message:
>>
>>
>> dbLoadRecords "db/tempLinuxExample.db", "user=ares"
>> Can't set "ares:zone0.VAL" to "blabberblabberblub"  : Bad Field value
>> ERROR:  at or before ')' in file "db/tempLinuxExample.db" line 7
>>
>> 7 |     field(VAL, 'blabberblabberblub')
>>
>> ERROR failed to load 'db/tempLinuxExample.db’
>>
>> We then tried the contradictory definitions of the description:
>> "DOL can also be a constant instead of a link, in which case VAL is initialized to the constant value.”
>>
>> record(lso, "$(user):zone0")
>> {
>>    field(DOL, 'blabberblabberblub')
>> }
>>
>>
>> epics@ares:~$ caget -s ares:zone0.VAL$
>> ares:zone0.VAL$ 41 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>>
>> But I don't quite understand this:
>>
>> "The first field that determines where the desired output originates is the output mode select (OMSL) field, which can have two possible values: closed_loop or supervisory. If closed_loop is specified, the VAL field's value is fetched from the address specified in the Desired Output Link field (DOL) which can be either a database link or a channel access link. If supervisory is specified, DOL is ignored, “
>>
>> record(lso, "$(user):zone0")
>> {
>>    field(OMSL, "closed_loop")
>>    field(DOL, 'blabberblabberblub')
>> }
>>
>> The same output :
>>
>> epics@ares:~$ caget -s ares:zone0.VAL$
>> ares:zone0.VAL$ 41 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>>
>>
>>
>> Danke Heinz
>>
>

Attachment: smime.p7s
Description: S/MIME cryptographic signature