Re: "duty cycle" records

[Gerrit Kühn via Tech-talk <tech-talk at aps.anl.gov>]

Am Wed, 22 Nov 2023 16:23:29 +0100
schrieb Gerrit Kühn via Tech-talk <tech-talk at aps.anl.gov>:

> > You need to put PP at the end of your OUT link to force the second
> > record to process.  

> Yes, that was the mssing bit. Thanks to both of you for pointing this out
> to me.

Last question for today (hopefully). I have these records now:

---
record (calcout, "$(CHAN)_DUTY_CYC") {
  field (DESC, "duty cycled output")
  field (VAL,  "10") # 1st cycle time
  field (INPA, "10") # cycle time
  field (CALC, "VAL-1")
  field (OUT, "$(CHAN)_DUTY_RESET PP")
  field (OOPT, "Transition To Zero")
  field (SCAN, "1 second")
}

record (calcout, "$(CHAN)_DUTY_RESET") {
  field (DESC, "reset cycle counter")
  field (VAL, "11")
  field (INPA, "$(CHAN)_DUTY_CYC.INPA")
  field (CALC, "A")
  field (OUT, "$(CHAN)_DUTY_CYC")
  field (SCAN, "Passive")
}
---

The second record gets processed when the counter in the first record
reaches zero. However, it only resets the counter as desired when the INPA
field in the second record is defined constant (i.e., INPA, "10" directly
in the second record).
My original idea as written above was to get the INPA field of the second
record from the INPA field of the first record. However, this does not
work. camonitor reports this as "LINK INVALID" although I can use caget on
the reported link just fine (and get the correct value). Again, this feels
like I'm missing a simple thing...


cu
  Gerrit

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