1 / 9

PACS OBSW Simulation/Test

PACS OBSW Simulation/Test. A.Mazy (CSL), S.Pezzuto (IFSI), A.N.Belbachir (TUVIE), H. Feuchtgruber (MPE). Virtuoso Emulator under Windows. Virtuoso kernel services are mapped onto windows services Services currently implemented : Tasks Semaphores Resources Events FIFOs Timers

talib
Download Presentation

PACS OBSW Simulation/Test

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. PACS OBSW Simulation/Test A.Mazy (CSL), S.Pezzuto (IFSI), A.N.Belbachir (TUVIE), H. Feuchtgruber (MPE) OBSW Simulation

  2. Virtuoso Emulator under Windows • Virtuoso kernel services are mapped onto windows services • Services currently implemented : • Tasks • Semaphores • Resources • Events • FIFOs • Timers • Link 1355 (mapped onto TCP/IP connection or using PCI-Spacewire board) OBSW Simulation

  3. Pros 95 % of OBS code is reused for simulator Powerful Windows tools available for debug Run on any desktop PC Can be connected to real HW Cons Scheduling behavior is different from Virtuoso Assembly code can not be simulated OBS Simulators on Virtuoso Emulator • Perfect tool to test the functionality of the OBSW, but not the performance. OBSW Simulation

  4. PACS OBSW Tests (1) • “Test Day” at CSL 6-Feb-2002 • Simulators of DPU, DMC, SPU-SWL and SPU-LWL OBSW running on 3 PCs • Certain “bypasses” are implemented due to the simulator environment (1553 interface to DPU) • Visualization of results is implemented as “printf” statements to screens or files • Major parts of the different individual OBSW pieces of DPU, DMC, SPU-SWL and SPU-LWL are already implemented. No compression/reduction running at this point yet. OBSW Simulation

  5. Test Set-up OBSW Simulation

  6. OBSW Simulation

  7. PACS OBSW Test (2) • Major debugging on sub-system protocol issues done  online updates • Emulator debugging  online update • Inspection of error handling between sub-systems  online updates • HK packet transfer from sub-units to DPU verified • TC+Acknowledge path DPU - DMC verified • TC+Acknowledge path DPU - SPU-SWL and DPU – SPU-LWL verified OBSW Simulation

  8. PACS OBSW Test (3) • Science packet transmission from DMC – SPU verified (blue and red, photometry and spectroscopy) • 1 OBCP has been executed including a DMC sequence (staring photometry) • Science packets of “SPU-simulated” data have been received by DPU but still some communication problems left, but identified. • Diagnostic data collection not yet verified due to failures  debugging done after the test • Entire Science TM path from DMC-SPU-DPU not yet tested due to lack of time. OBSW Simulation

  9. Conclusion • The emulator+simulator exercise has demonstrated its usefulness and value for PACS OBSW development and debugging • Continue efforts on the simulators • Update software to resolve identified problems • Update involved documentation • Next “Test day” at CSL: 6/7-Mar-2002 OBSW Simulation

More Related