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: GUI Control System Options |
From: | "Chen, Xihui" <[email protected]> |
To: | Jeremy Iken <[email protected]>, "[email protected]" <[email protected]> |
Date: | Mon, 17 Jun 2013 12:26:42 -0400 |
Hi Jeremy, There is no existing code for creating a standalone BOY product, but it should be not that hard to create your own RCP product that only has BOY included. Someone from Hawaii Keck has done this before. We primarily use WebOPI for monitoring or non-critical controls. It mostly works smooth in a local area network on desktops or even tablets for small number of users, but we may need to reboot it once a month or two months. To use it for mobile over internet (for example, 3G network) , we only use it for small overview screens so users can know the overall status of the system. Thanks, Xihui From: Jeremy Iken [mailto:[email protected]] Hey, I am new to EPICS, and my company is starting to explore control systems for a proton shooting machine, and we are strongly considering EPICS and CSS (Control System Studio) for its BOY GUI, and especially its webOPI browser abilities. However, we wish there was some way to create a standalone BOY product instead of needing to go through Eclipse each time. We are also wondering if the webOPI is reliable, as there seems to be flickering that does not inspire confidence. So basically: Is the best GUI control system through CSS, or should I look to MEDM? Is webOPI the best for mobile/tablets? Is it strong enough? Thanks, Jeremy |