1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 <2014> 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 <2014> 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: New standards for small and medium sized astronomical observatories |
From: | "Johnson, Andrew N." <[email protected]> |
To: | "<[email protected]>" <[email protected]> |
Cc: | Grzegorz Lech <[email protected]>, Rafał Konrad Pawłaszek <[email protected]>, "[email protected]" <[email protected]> |
Date: | Wed, 9 Jul 2014 15:09:16 +0000 |
Hi Piotr,
Some secondary questions of yours that we haven't answered yet were these:
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.
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
|