second approach, better fitting what was agreed upon so far.
- pv_names are local to SEC-node, so not exporting via json and marking
them 'private'
- 2 devices for 2 temperature control loops, not one 'monster' device
which handles everything.
- read_status implemented
- write_target also updates the status (may be sensible to go to the core?)
- provide working stubs in case epics is not installed (-> testing possible)
- tested with the stubs.
- tests with real epics.
found problems:
in EpicsTempCtrl(EpicsDriveable) the read/write_<paramname> methods from
EpicsDriveable needed to be reimplemented. This should not be needed!
Change-Id: I9e4eeaff83114131d117c8f04fba758dfe22237b
+ make parameter-properties configurable
+ better derivation of automatic properties
+ implement 'group' properties (how to display in gui???
+ clean up descriptive data by omitting unset and live properties
Change-Id: Icd2b6e91e09037e9d4a8d6ad88483f8509a2cf5f
- unify (encoded) Errormessages. They now always contain the offeding request.
- adopt keywords to current spec
- fixed formatting of timestamp in WriteReply
- minor bugfixing + polishing
Change-Id: I0ab8836756551399643bdce3d062eedd345509f1
