Re: netDev "channels" record type problem

[Владимир Сергейчик via Tech-talk <tech-talk at aps.anl.gov>]

Hello Shuei,
I am using EPICS R7.0.7 and netDev-1.0.7 

Пн, 7 авг. 2023 г. в 9:32 PM, Shuei YAMADA <shuei.yamada at gmail.com>:

Hi Vlad,

First of all I have two questions:

Which version of netDev and EPICS base are you using?

Why don't you use ai records for IR:something:T1 (or T2) instead of ao records?

regards,
Shuei

p.s.
Currently I'm on vacation and I don't have access to our working
version of netDev. I'll look into it when I get back

2023年8月7日(月) 18:34 Владимир Сергейчик via Tech-talk <tech-talk at aps.anl.gov>:

>
> Hello everyone! I want to read out data from GM10 data logger, using netDev "channels" record type (it turns the set of PVs into an array). However, I have encountered some problem: I need to use "Passive" SCAN mode for the elements of that array, however, it would work only if I add .PROC CA to the FLNK line:
>
> field(FLNK,"IR:something:T1.") -> field(FLNK,"IR:something:T1.PROC CA")
>
> Only in this case it starts working properly. (By "working properly" I mean that while processing the data from datalogger both individual PV and the corresponding element of the array change simultaneously, while in other case the element of array changes whereas the value of a particular PV remains unchanged). Meanwhile, while looking at scripts of other users, they do not use .PROC CA addition and everything works OK.
>
> Could you explain why the field(FLNK,"IR:something:T1.") (without .PROC CA) doesn't work and how it can be fixed (because simple adding of .PROC CA doesn't seem to be a correct solution, otherwise other users would also add it).
>
> For better understanding of the context, I attach the example db-file. The first record is "channels" record type (which is array), and two others are scalar PV.
>
> Thanks,
> Vladimir



--
                 ----------------------------------------------------
                 Shuei Yamada,
                 High Energy Accelerator Research Organization (KEK)
                 mailto:shuei at post.kek.jp
                 ----------------------------------------------------