Experimental Physics and
Industrial Control System

Gerrit Kühn via Tech-talk <tech-talk at aps.anl.gov> · Tue, 5 Dec 2023 08:20:05 +0100

Hello,

I have a device continuously sending data that I parse via StreamDevice
into the following records:

---
record (ai, "$(CHAN)_CT_03") {
  field (DESC, "PM count greater 0.3µm")
  field (DTYP, "stream")
  field (INP, "@particulatematter.proto getCount($(U),$(CHAN)) $(CBPCT)")
  field (SCAN, "I/O Intr")
}
record (ai, "$(CHAN)_CT_05") {
  field (DESC, "PM count greater 0.5µm")
}
record (ai, "$(CHAN)_CT_10") {
  field (DESC, "PM count greater 1.0µm")
}
record (ai, "$(CHAN)_CT_25") {
  field (DESC, "PM count greater 2.5µm")
}
record (ai, "$(CHAN)_CT_50") {
  field (DESC, "PM count greater 5.0µm")
}
record (ai, "$(CHAN)_CT_100") {
  field (DESC, "PM count greater 10.0µm")
}
---

In the protocol, the first record is parsed directly, the others are
populated using record redirection:

---
in
"greater03um=%i\tgreater05um=%(\$2_CT_05)i\tgreater10um=%(\$2_CT_10)i\tgreater25um=%(\$2_CT_25)i\tgreater50um=%(\$2_CT_50)i\tgreater100um=%(\$2_CT_100)i";
---

This all works fine except for one thing:
Sometimes I need to reset these channels, e.g., using caput on the
commandline. This works as expected for all channels except for the first
one that is using I/O Intr scanning. For this, caput is able to change the
value, a following caget reports the new value. However, camonitor does
not recognise the change. I do get the new value when restarting
camonitor, though. This also leads to the new value not being recognised by
the archiver appliance.

As this works fine with all other records, it looks to me like the
scanning field (I/O Intr), maybe in combination with StreamDevice, is
causing my trouble here. Is this expected behaviour? How can I achieve
that caput changes are recognised by camonitor on I/O Intr records?

cu
  Gerrit

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System