NRAO Home  >  Green Bank  |  Wiki Topic:    GB > PTCS > InformationForProjectTeam > PTCSProjectPlan > ServoImprovements
   Changes | Index | Search | Statistics | Go

Servo Improvements

Introduction

The GBT servo system has served the GBT well throughout its early life. The currently implemented system was designed by the contractor to meet specifications NRAO provided that did not include the needs of the current GBT operating modes. The parameters of the telescope servo system were optimized for stepping and tracking sidereal sources, and for that it works well. However, our needs do not match the specifications in several ways:

Project Goals

The goals of the this project are to improve the GBT servo to support high frequency observations. Specifically, the long-term servo replacement should allow better control in windy conditions, and the short-term improvements should improve pointing in benign conditions. The goal of the PTCS is less than 1.2 arcsec of tracking error for good performance at 86 GHz. THis tracking error must be allocated among several sources of error, so the error budget for the servo is less than this, perhaps 0.5 arcsec. (N.B. I think this was in Kim's URSI presentation)

Project Charter

These issues have led us into attacking the servo system from a couple of fronts, short-term and long term. The first items are short-term improvements that work with the current system, and can be completed, with the proper staffing, by the end of the calendar year. The last item is a long-term (> 1 year from now) item.

Project Personnel

Project Charter Approval

Approval of the charter means that the program is authorized to proceed, and commit funds and labor hours to the project.

Symbols:

Project Scope

Scope of the project refers to the activities that will be pursued.

In Scope

The scope is defined by the Work Breakdown Structure and the project activities. These project activities are documented separately, and are referenced below.

Out of Scope

Several things that will specifically not be included in the scope of work for the servo improvements are:

Scope Management Plan

Changes in mission will be accepted only by the project manager in consultation with GBT Program Management (Currently K. O'Neil and R. Prestage), along with the project's team members. Increases in scope will not be accepted unless a clear source of additional resources to handle the increased scope is provided with the request.

Work Breakdown Structure (WBS)

The following will be provided by this program:

Project Activities

Project Schedule

The servo interlock upgrade and the friction compensator are currently being pursued. These other activities are on hold pending availability of additional effort, which is currently allocated to the pointing model and holography. We will start them approximately as follows:

Project Status Meeting Notes

Estimated Costs

Except for the New servo system, nearly all the costs are in personnel. The new servo system will require about $50k of consulting, and $50k of hardware costs. If it is decided that the 22-bit azimuth and elevation encoders should be replaced with better performing devices, then additional costs for hardware and software interface modifications will apply.

Program Plan Approvals

Current (January through March) Request for effort allocations

-- JohnFord - 19 Jan 2007

Attachment: sort Action: Size: Date: Who: Comment:
azvstime.pdf action 56958 08 Feb 2007 - 22:57 ToddHunter VLBI fast switching: Azimuth settling time = 20%
elvstime.pdf action 63774 08 Feb 2007 - 22:57 ToddHunter VLBI fast switching: Elevation settling time = 8%
servo_update.ppt action 3398656 05 Mar 2007 - 19:50 ToddHunter powerpoint presentation for 03/06/07 PTCS meeting
PTCSMeetingnotes080826.pdf action 19695 28 Aug 2008 - 21:01 MartyBloss PTCS Meeting 26-Aug-08

Topic ServoImprovements . { Edit | Attach | Ref-By | Printable | Diffs | r1.21 | > | r1.20 | > | r1.19 | More }
Revision r1.21 - 28 Aug 2008 - 21:03 GMT - MartyBloss
Parents: WebHome > InformationForProjectTeam > PTCSProjectPlan
Content copyright © 1999-2007 by the contributing authors.
All material on this collaboration platform is the property of the contributing authors.