DAQ
3 System Upgrade Status
April
23, 2002
VME
systems Configuration
Currently
operating with vxWorks Tornado 2.0.2
Compiler: gcc 2.7.2
Orbix/E 2.0
Embedded C++
Status:
All subsystem servers ( dcm, gl1 , timing )
have been rebuilt in this operating environment.
System tests have been conducted to varying
degrees, the based on the conversions of the application programs. More details later.
All servers were converted to use the OMG
nameserver, although each is also functional with the previous nameserver.
Observations:
Stricter compiler standards resulted in more
than a few code changes to compile and run successfully.
Effort
was made to fix warnings, however, many still remain as the main function was
to identify major issues and have an operational system in place.
Code
modifications were made to correct for changed CORBA standards.
Orbix/E
concurrency model requires thread safe operation on shared code as multiple
clients operate in separate threads.
Desireable
to migrate to gcc 2.9.6 compiler due to lack of desireable C++ features which
restrict certain IDL constructs.
Wind
River is scheduled to support this version compiler this June/July.
Currently
arranging for a beta version.
Of those tested, only one function failed to
operate successfully so far.
SUBSYSTEM MIGRATION STATUS
DCM
Map
updated for T2.0.2
Dcm
server and utility functions built.
Standalone
dcm application successfully executes dcm download and
Initialization
functions.
Dcm CORBA server was upgraded and built.
Registers with OMG nameserver
TODO:
Finish
conversion of run control to test dcm
functions
GTM STATUS:
VxWorks server converted and
running under T2.0.2
Gtmcommand application built
and run with new server
GTMgui built with JDK 1.4 and
run with new tm server.
- not extensively tested
Test program results by JH
produces
JH ran multiple client instances of gtmcommand
Errors in memory address
when running multiple clients
TODO:
Make tm server thread safe
GL1
GL1 server built and running
under T2.0.2
Most functions successfully
tested
-
problem
with GL1_I::LV1_rdmonfifo
-
possible
memory limitation - currently under
investigation
Operating environment
Solaris:
Orbix2000
CC 5.1 C++
compiler
Upgrading
compiler to C++ 5.2
JDK 1.4
Java environment
Jdk 1.4
Idlj compiler
Linux:
Orbacus
4.1.0b1
Built
Orbacus 4.1.0
Currently
upgrading to this version
Requires
code rebuild only so far.
NT
Orbix 2000
Visual C++
6.0
( Is there a
desire to move to gcc? )
Build Environment
VxWorks kernels are located in
/export/software/lic/wind/Tornado2.0.2_ppc
Source /export/software/lic/wind/setupT2020env.csh
for Tornado 2.0.2 environment variables.
Currently building in private area
Propose creating R4.0.0 version for installation
Issues:
Current vxWorks compiler
lacks feature needed by JDK 1.4 IDL compiler.
Results in an Object ID
difference.
Option:
Workarounds available to make references compatible.
Will test beta vxWorks compiler soon.
Use Orbix2000 jidl compiler ( JDK 1.3 compatible )
Built CorbaUtility C++
libraries
Built Java CorbaUtility
packages
Status:
C++ libraries are being used
by test and online applications
Java jar libraries are being used by built online Java applications
GL1 APPLICATIONS:
Application |
Status |
gl1gui |
Built most functions
tested |
Bbcgui |
Built , run but not tested |
genll1gui |
Built , run but not tested |
GL1rc |
Built , run some functions
tested |
Built server with IIOP
protocol and libraries.
Status:
Not yet tested.
Code was added to migrate
server to Linux
Status:
Not yet built under Linux.
Needs Linux ARCNET drivers.
Will build server on Linux ASAP.
General Utility functions:
Nameserver manager , browser
Currently being ported.
PARTITION SERVER
Currently migrating server
application
RUN CONTROL
Need to convert to use
common utility libraries.
Currently migrating server
and Java gui
EVENT
BUILDER
Design
goal is to provide parallel server startup and initialization within 1 minute.
Will
build prototype servers for
demonstration of start, initialization
and restart operations with new system
servers.
PHENIX
MESSAGE SYSTEM
Is
implemented with OMG Event Service
Previous
message generators and Message consumer/ display application was ported to work
with Event Service
Existing
Message Structures work with Event Service.
Applications
sending / receiving messages have been running for over a month.
Will
test further for failure modes as time allows.