1 / 20

GSEOS V Ground Support Equipment Operating System

INSTITUT FÜR DATENTECHNIK UND KOMMUNIKATIONS-NETZE. Technische Universität Braunschweig. GSEOS V Ground Support Equipment Operating System. July 2006. Kai Stoeckner. Introduction (1). During development sophisticated test equipment is needed

tnicky
Download Presentation

GSEOS V Ground Support Equipment Operating System

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. INSTITUT FÜR DATENTECHNIK UND KOMMUNIKATIONS-NETZE Technische Universität Braunschweig GSEOS VGround Support Equipment Operating System July 2006 Kai Stoeckner

  2. Introduction (1) • During development sophisticated test equipment is needed • Similar test equipment requirements for different projects: • Operate the instrument in its various operational modes • Format the data from the instrument to an easily interpretable extract

  3. Introduction (2) • Typically 3 phases during instrument development: • Bench test (Assembly Level) • Spacecraft integration (System Level) • Flight operation (Mission Level) • The use of a common checkout system saves cost and time •  software package GSEOS V

  4. Bench Test (Assembly Level)

  5. Spacecraft Integration (System Level)

  6. Flight Operation (Mission Level)

  7. GSEOS Overview • Highly configurable software package • Configuration Language based on “C” • Interactive configuration on the running system assisted by a graphical editor • Contains tools for: • Command processing • Data decoder • Data display • Logging • Recording/Playback • Printing • Command batch files • External program calls • External DLL interface • Network • Serial port • Special hardware support (e.g. S/C interface simulator)

  8. System Architecture

  9. Main Features (1) • Real time data acquisition • H/W I/Fs with FIFOs (SDRAMs) and PCI Bus Master DMA • 32 Bit, 33 MHz PCI bus 133 MByte/s, < 10 µs • 64 Bit, 66 MHz PCI bus 528 MByte/s, < 10 µs • Near real time data handling • Prioritized and threaded task scheduling for: • Time-critical tasks • H/W interface handling 528 MByte/s • Data decoding 100 MByte/s, < 5 ms • Data recording 70 MByte/s • Commanding 100 MByte/s • Non-critical tasks • Data playback 70 MByte/s • Data display 10 MByte/s • Graphical online configuration Dual processor PC system, 2 x XEON 3 Ghz, SCSI 320 RAID 0 Array

  10. Main Features (2) • Platform: x86-based Workstations, Windows 2000/XP/VISTA • Windows NT 4.0 support for currently running projects • No more support for 16-bit Windows 95/98/ME • Full multiprocessing support through multiple thread programming • No polling • Data driven concept with several queues and task priorities to gain high data throughput without loss of data

  11. Configuration Language • Built-in compiler • Mostly “C”-like syntax, except: • Data driven decode on (rawScienceData) {...} • More bit precisely int(4,3) ArrayName[512]; • Motorola byte order motorola int Counter; • Array arithmetic a[5..8] = b[7..10] * c; • New data types bitmap 16 [1024,1024] rawCCDImage; • Direct DLL I/F dll “MilDriver.dll” long MilBusOpen (...); • Enhanced Runtime Library functions (dialog boxes, network, etc.) • No pointers, but references (like C++) void NetSend (UCHAR &a[]); • No dynamic memory management functions • No goto statement

  12. Language Inherent Safety Features • No pointers, no dynamic memory management • Enforced structured programming (no goto statement) • Data type checking during compilation • Array size checking during compilation and runtime • Exception handler for mathematic errors • Division by zero • Floating point overflow/underflow/not-a-number • Parameter checking for Runtime Library functions • Ensure zero termination of strings • Check all return buffer sizes • Check length of user input in dialog boxes • etc.

  13. Graphical Interface (1) • Interactive configuration on the running system assisted by a graphical editor • Numerous graphic controls for data visualization: • Static text • Static pictures • Group boxes • Command buttons • Scalar numeric items • Field numeric items (arrays) • Text references (lock-up table, cast numeric item into a string) • Strings (zero terminated character arrays) • Bitmaps with different color depth (1, 4, 8, 16, 24, 32 bits) • Bargraphs (histogram) • x/n, y/x plots

  14. Graphical Interface (2)  Static Text  Group Box  Button  Scalar  Array  Text- Reference  Bitmap  Bargraph  x/n Plot         

  15. Heritage (1) PC-based EGSEs under GSEOS supported more than 40 space instruments, e.g: Previous GSEOS Versions: • ACE: S3DPU, SEPICA, SWICS, SWIMS, ULEIS, EPAM • CLUSTER: RAPID, SSR • CLUSTER II: RAPID, SSR • GALLILEO: LRD, EPI • GEOTAIL: EPIC • PALASIM: ESTEC study • SOHO: CELIAS, SUMER • Spaceshuttle: MAS GSEOS V: • Chandrayaan: SIR-2 • CASSINI: DISR, MAG • CHAMP: OBDH Memory Module • CRYOSAT: MMFU • ENVISAT: SSR • GRACE: OBDH Memory Module • HCMB: ESTEC study • Mars Express: SSMM, Aspera • MSRS: DSU • Rosetta: ROSINA, OSIRIS, OSIRIS MMB • RTMC-3: IDA Radiation Test Equipment for High Capacity Memory • SMART-1: SIR • STEREO: IMPACT/SIT • Sunrise: a balloon-borne Solar telescope • TerraSAR: SSMM, DEU, Instrument EGSE • Venus Express: VNC, SSMM, Aspera-4

  16. Heritage (2) • The software package OCL (Onboard Command Language) is based on GSEOS built-in configuration language compiler and virtual machine • OCL is used in 6 projects: Instruments: • Rosetta: OSIRIS (Virtuoso, Temic 21020) • Venus Express: VMC (RTEMS, LEON) • Dawn: Framing Camera (RTEMS, LEON) Satellite Platform: • GOCE (RTEMS, ERC32) • Herschel (RTEMS, ERC32) • Planck (RTEMS, ERC32)

  17. GSEOS 3.3 vs. GSEOS V (1)

  18. GSEOS 3.3 vs. GSEOS V (2)

  19. GSEOS 3.3 vs. GSEOS V (3)

  20. Summary • GSEOS software package provides a flexible and powerful tool for typical EGSE tasks • Instrument operation • Data decoding and visualization • Easily adaptable to specific instrument requirements • Enhanced C-like configuration language • Graphical editor • Usable for all project stages from bench test up to flight data display • Documentation: http://www.gseos.de

More Related