Hello,
I'm just curious how to make this work better.
We have some variable drives with multiple 'things' on it. Since both the names of any 'thing' and the position of them can change, it's helpful to expose these fields to expert users and autosave them. Currently we're doing
this with a combination of mbbo and calcout records.
Example: a variable drive with stripping foils at various positions
record(mbbo, "REA_BTS41:STRIP_D1391:POS_SEL"){
field(ZRST, "N/A")
field(ONST, "DLC 500 nm")
field(TWST, "DLC 2750 nm")
field(THST, "DLC 3500 nm")
field(FRST, "DLC 4000 nm")
info(autosaveFields, "ZRST ONST TWST THST FRST")
info(autosaveFields_pass0, "VAL")
}
record(calcout, "_REA_BTS41:STRIP_D1391:POS_calc"){
field(INPA, "REA_BTS41:STRIP_D1391:POS_SEL CP NMS")
field(INPB, "90")
field(INPC, "-11")
field(INPD, "-44")
field(INPE, "-77")
field(INPF, "-110")
field(CALC, "A==1?C:A==2?D:A==3?E:A==4?F:B")
field(OUT, "REA_BTS41:STRIP_D1391:POS_CSET PP")
info(autosaveFields, "B C D E F")
}
I'm open to any suggestions people may have, if they think there's a better way to handle it, but my two main questions are:
1. How can I keep these PVs and their fields from loading up as [INVALID - LINK_ALARM] on ioc reboot? I tried PINI, "YES", but that didn't seem to do the trick.
2. The calcout input fields don't appear to be autosaving, I've tried editing the db code to just the letter--i.e. field(B, "90")--and I've tried listing autosave values like "INPB INPC" etc..
I'm sure I'm missing something simple.
Thanks!
-Dan