Subject: [IGSMAIL-2441] Turbo Rogue Tracking Status
From: Miranda Chin/NGS CORS Data Management Team
Date: Sun, 22 Aug 1999 15:48:02 PDT

******************************************************************************
IGS Electronic Mail      Sun Aug 22 15:48:02 PDT 1999      Message Number 2441
******************************************************************************

Author: Miranda Chin/NGS CORS Data Management Team
Subject: Turbo Rogue Tracking Status

Subject: Turbo Rogue Tracking, Data Download, and Rinex Status

This is a preliminary summary derived from 12 Turbo Rogue tracking
stations. The tracking status was recorded on Sunday (August 22) 
morning; data download tests were using 'offload' command; and
Rinex data sets were translated using 'Teqc'.

Firmware 3.2.32.9 were installed before August 22:

 - 8 stations were tracking fine.
 - USNO's receiver reverted back to version 3.2.32.4; and the
   GPS time was set to Jan. 1980.
 - TMGO's receiver reverted back to version 3.2.32.8
 - After 'bang'ed the USNO and TMGO receivers, firmware 3.2.32.9
   reappeared. 
 - In the 'offload' command, GPS week is 1024.
 - Both Conan Binary and Turbo Binary offloads are fine.
 - '99o' and '99n' files are seems OK. '1024' is in the '99n' files.

Firmware 3.2.32.8:

 - BRMU, KELY, and FORT receivers still have this version.
 - BRMU and KELY trackings are fine. Not able to get hold of FORT.
 - In the 'offload' command, GPS week is 0.
 - Conan Binary offload seems fine at KELY. BRMU communication was
   interrupted after the initial contact.
 - NO '99n' file from KELY. '99o' seems OK.

The latest 'ACT' receiver at AMC2:

 - Tracking seems OK. 
 - In the 'offload' command, GPS week is 0.
 - Downloaded Turbo Binary. File size is larger than normal.
 - Produced both '99o' and '99n' files. '1024' is in the '99n' file.

We hope to get BRMU upgraded to 3.2.32.9 on Monday and KELY this week.
FORT will be a couple of weeks later.

Any suggestions or advices will be appreciated.

[Mailed From: [email-masked]]