I'm glad we switched to RTEMS. These issues are history...
In about 4-5 (wo)man-months a BSP can be developed (includes
'learning by doing' RTEMS training). If several projects/labs
could decide on sharing BPSs, money could be saved. Plus,
you have control over the source code.
-- Till
Jeff Hill wrote:
I am in the process of renewing our vxWorks maintenance.
Unfortunately, WRS
still does not have a two tier licensing scheme for users of Tornado GUI
tool verses folks that are just building and installing executables with
scripts (i.e. typical EPICS application developers). It occurs to me that
there is a potential to significantly reduce the cost of Tornado
ownership
at EPICS installations. It seems that if someone were to modify the SNL
compiler so that it produced byte code which is interpreted at run time
(similar to JAVA) and there was an option to create an alternative IOC
configuration where dependence on the target symbol table by vxWorks
compiled iocCore was removed (we already have this working on other OS
with
R3.14), then the application developer wouldn't need to use a Tornado
seat.
Sites might need to buy Tornado seats for building EPICS base and for
developing drivers, but not for developing EPICS function block
databases or
to develop SNL based logic.
I was just curious if there was any general level of interest in that
approach?
P.S.
I just heard that there is a new 8k US $ per year per seat licensing
model
from WRS which allows unlimited use of any hostArch / targetArch /
project
permutation by one user.
Jeff
__________________________________________________________
Jeffrey O. Hill Mail [email protected]
LANL MS H820 Voice 505 665 1831
Los Alamos NM 87545 USA Fax 505 665 5107