Hi Piotr,
Some secondary questions of yours that we haven't answered yet were these:
Could you point me to some example of embedded device with low resources (10K-100KB of memory, 8-bit processor, preferably bare metal distribution), that supports the EPICS? I know that I am pushing the limits, but
the optimization (low power consumption) is an important factor for us.
EPICS is not designed to run on such small systems, the smallest IOCs would need to run RTEMS or VxWorks (or be ported to something similar) and have 8-12MB of RAM, 16MB recommended. Anything smaller would need to run custom code and communicate with a
real IOC (which may be remote) over a network, serial or field bus connection. This architecture can protect the small system from being overloaded by communications requests from other devices, and help keep your power consumption low.
And what about communication security, is it possible to authenticate EPICS agents with certificates?
The EPICS Channel Access protocol is not suitable for use on open networks, it does not implement cryptographic authentication or encryption of data streams at all. There are plans and designs to be able to use them in the replacement V4 protocol PVAccess,
but that aspect of the work has not proven sufficiently important to the V4 users to have been implemented yet.
- Andrew
--
Sent from my iPad
|