1 / 9

An approach to HLA Gateway/Middleware Development

An approach to HLA Gateway/Middleware Development. Naval Air Warfare Center Training Systems Division [ Daniel J. Paterson, Eric Anschuetz, Mark Biddle Dave Kotick, Thai Nguyen ] Orlando, FL. dan_paterson@ntsc.navy.mil. Research Agenda. 3 Phases of Research Pre-Implementation

noma
Download Presentation

An approach to HLA Gateway/Middleware Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An approach to HLA Gateway/Middleware Development Naval Air Warfare Center Training Systems Division [Daniel J. Paterson, Eric Anschuetz, Mark Biddle Dave Kotick, Thai Nguyen] Orlando, FL dan_paterson@ntsc.navy.mil

  2. Research Agenda • 3 Phases of Research • Pre-Implementation • Implementation • Results/Lessons Learned • 4 Focus Areas: • HLA Rules of Usage • HLA Interface Specification • OMT (SOM & FOM) • HLA Gateway • HLA Gateway • separate 6.2 effort • translator approach • scaleable DIS research • Simulation Middleware • Object Classes (SMOC) • NAWCTSD HLA Effort: • I/ITSEC HLA Demo

  3. Approach/Goals • Approach taken based on Lessons Learned from first implementation and looking at future needs of our community. • Reused code from first implementation, but focused on O-O design approach. • Tried to implement higher degree of reusability, flexibility, and scaleability

  4. What did we get? • Object Oriented/Modular Interface • Realtime Platform Reference Federation Object Model (RPR-FOM) used with extensions for Voice. • DIS and HLA interface in a single box • Developed for Windows 95/NT, HP-UX, Solaris, and IRIX. • RTI 1.0 and HLA Tools all supported

  5. ArchMgr API ProtoMgr - sendDISPDUTo() - tick() - recvUpdates() EnttyMgr ... DISMgr RPRMgr XXXMgr - updateEntityTable() FEDERATION EXECUTION RTI EXECUTION RTI DIS HLA SMOC Architecture

  6. Federation Object Model • Different FOMs supported • Architecture data file supports the idea • Requires development of new object class for each FOM type (RPR-FOM already implemented) • Software “Knows” through polymorphism which instance to choose • No existing lines of code get changed • Supports exercise scaling as user can specify which channels data is sent/received on

  7. SMOC Demonstrations USS THE SULLIVANS - Mayport MARRIOTT - Orlando BFTT Experimental DIS VTC System BFTT VTC VME UNIX System PC NT SMOC Gateway SMOC Gateway DIS PDUs RTI RTI T1 Line WAN

  8. SMOC Demonstrations ARC Dome - Booth 302 I/ITSEC NAWC Booth 536 I/ITSEC F-18 SMOC PC-NT F-14 SMOC PC-NT Heads Down PC-NT Flight Model RTI Heads Down Display Flight Model RTI/Fedex RTI RTI HLA Network DIS ONYX2 VISUAL BFTT Digital VOICE BFTT Digital VOICE DIS DEC-ALFA IOS SIM-MAN AAR SGI-O2 IOS SIM-MAN AAR SGI-O2 Visual

  9. Summary • Quick solution for a DIS-HLA migration (Gateway mode) • Solution for interoperability (Use of RPR-FOM) • Solution for existing trainers (No DIS) with middleware mode • Solution for running DIS and /or HLA exercises without recompiling code or using a gateway • Solution for Multiple FOM interoperability • Solution for multiple RTIs

More Related