As the communicator class needed for a module can be specified,
in the configuration we do not need to specifiy it explicitly.
A new configurator function IO() is introduced for this, defining
names and uri only.
- update also configuration reference and a tutorial example
- update get_class function to accept attributes of classes like
'frappy_demo.lakshore.TemperatureSensor.ioClass' and import from
modules other than frappy... like 'test.test_iocfg.Mod'.
- add ioClass to the example class for the temperature controller
tutorial
Change-Id: I3115371d612f14024e43bc6d38b642e1d27b314d
Reviewed-on: https://forge.frm2.tum.de/review/c/secop/frappy/+/38071
Tested-by: Jenkins Automated Tests <pedersen+jenkins@frm2.tum.de>
Reviewed-by: Markus Zolliker <markus.zolliker@psi.ch>
- remove the auto detect from replies
- improve readability
- add not implemented attributes in AHBase to avoid pylint
complaints
Change-Id: I20aabe6c5cfaad94845cdfff22b889fb7ff7e257
For devices sending messages asynchronously, a simple
readline method is added. Waiting for characters is not
blocking writeline - only the actual reading is using
a lock.
This needs also some rework of frappy.lib.asynconn.
improve the mechanism which avoids duplicated error messages
in the log file:
- extend to errors in doPoll
- trigger error messages every day, so that they appear in every
logfile
+ add missing space in some error message
Change-Id: Icfaa06b43ee53f477483bab1f84def832fd0b977
Reviewed-on: https://forge.frm2.tum.de/review/c/secop/frappy/+/37432
Reviewed-by: Markus Zolliker <markus.zolliker@psi.ch>
Tested-by: Jenkins Automated Tests <pedersen+jenkins@frm2.tum.de>
- configuration errors on startup are no longer collected in the
'errors' attribute, but logged immediately and counted in a new
'logError' method.
- generalConfig may be configured to raise the errors immediately
instead
- Raise immediately on unhandled errors. Some of them were catched
before which may lead to strange follow up errors.
- do not start poller thread, when the error count is non-zero
- as before, simple connection failures are not preventing startup,
but now more severe errors (bad uri) will stop the server
Change-Id: I4f84ee8e86cf2925108c0fe92eaab796bb731091
Reviewed-on: https://forge.frm2.tum.de/review/c/secop/frappy/+/37776
Tested-by: Jenkins Automated Tests <pedersen+jenkins@frm2.tum.de>
Reviewed-by: Markus Zolliker <markus.zolliker@psi.ch>
