It does work yes. Just wondering if there was a more suitable
one. Thanks
On 14-04-2017 17:38, Arnold, Ned D.
wrote:
Why doesn't a ai, ao, or calc work for
this purpose? Making field(DTYP, "Soft") makes it not tied to
any hardware ...
Ned
Yes you are right. I was going to say that that would not
help me because i have the autosave and the PINI would
overwrite it, but that actually not true. I got this wrong
the first time I did it.
Thanks 4 the help.
By the way, what kind of record should i be using for a
decimal value that is not either a ai, ao or calc. I mean,
it is a value that is only changed by the user
manually.Like a setpoint or something similar.
On 14-04-2017 17:24, Arnold,
Ned D. wrote:
>The
problem is that i would not like it to be instantiated as
an
>undefined pv.
If I understand correctly, I think all you need is the
PINI field set true ...
record(stringin , "$(user):ExperienceString"){
info(autosaveFields, "VAL") #autosave
field(VAL, "no experience")
field(PINI,"YES")
field(DESC, "anotar estados da experiencia")
}
Ned
________________________________________
From:
[email protected] [[email protected]] on
behalf of Miguel [[email protected]]
Sent: Friday, April 14, 2017 11:18 AM
To:
[email protected]
Subject: Init pv properly
Hello,
I would like to create a Pv that at the epics start up
does not have any
specific value or one forced by me.
For example i would like to have a string that its initial
state is not
really important (no experience). Like:
record(stringin , "$(user):ExperienceString"){
info(autosaveFields, "VAL") #autosave
field(VAL, "no experience")
field(DESC, "anotar estados da experiencia")
}
Where ill change this afterwrds manually when it will be
important.
The problem is that i would not like it to be instantiated
as an
undefined pv.
Changing the VAL is the most appropriated method? I tought
about changin
UDF to 0 but did not work.
The same for a integer pv. Wich kind of pv should i use
and how should i
instantiate it?
Thanks a lot,
MiguelB
|