AMS TIM CERN , July 2003

1
AMS TIM _at_CERN , July 2003
Tests with TReK and GoAhead
Alexei Klimentov Alexei.Klimentov_at_cern.ch
MIT
2
Agenda

• A.Lebedev AMS-02 Commanding
• P.Dennett TReKGate concept
• A.Klimentov Tests _at_ CERN
• K.Scholberg Tests _at_ MIT
• G.Carosi
• Action items for meeting _at_ MSFC

3
TReK/GoAhead Tests

• TReK Q1020v, Windows 2000 Professional and MS
  SW. TReK V2 SP 2 and GoAhead
• Linux PII 450MHz RH Linux 7.3, kernel 2.4.18
• Both connected to 100 Mbit/s CERN ethernet (the
  same segment, no routers/switches in between)

4
(No Transcript)
5
TReK/GoAhead Tests (telemetry)

• TReK
• telemetry simulator generates data
  and writes on disk
• C program
• checks new files and prepare catalogues
• catalogues can be viewed via Web (thanks to
  GoAhead)
• get telemetry
  statistics from TReK
• Linux
• Perl script (http Perl lib) checks
  catalogues and if new
• files available, copies files to local
  disk.

Run for 24h, minor bug in TReK with automatic
files closing (fixed in new release)
6
TReK/GoAhead Tests (commands)

• TReK
• TReK command simulator
• GoAhead linked with TReK API libs
• functions to send commands and
  get replies
• commands defined as GoAhead goform
• Linux
• Perl/cgi script (http Perl lib) to send
  commands from shell
• prompt or Web
• C program (subs from P.D.) to send commands

If commands generated as fast as C program can,
the commands order received/sent by GoAhead is
correct, about 10 of commands are swapped in
TReK command simulator
7
TReK/GoAhead Tests (remarks)

• TReK improved since 2001
• TReK helpdesk replies immediately and patches
  are provided
• There is no way to monitor TReK status from
  remote machine
• If TReK dies all programs compiled with TReK
  APIs must be resubmitted
• TReK source code is under US regulations and
  cannot be provided to AMS.

8
Meeting _at_ MSFC

• AMS GSC_at_MSFC, access to POIC
• AMS-02 GSC architecture
• AMS-01 HRDL system during AMS-02 shuttle
  phase
• Access to AMS science and telemetry data at
  POIC (UDP packets in format specified in PGUIDD
  ?), data buffering, RTDS/GSC connection
• The role of extracted telemetry interfaces is
  unclear (SSP 50304 Rev A, section 5.5)
• TReK , TReK enhancements and TReKGate concept
  
• TReK/TReKGate commanding during AMS-02
  shuttle phase
• Tests
• Group A and B