Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.apo.nmsu.edu/Telescopes/eng.papers/milt/telescopecontrol.html
Дата изменения: Mon Dec 13 18:50:17 1993
Дата индексирования: Sun Apr 10 02:22:57 2016
Кодировка:

Поисковые слова: space station
Telescope Control System

Telescope Control System

Requirements

System requirements which apply directly to control system design are listed in Section 1-6. A sub-budget which breaks the tracking line item down into structure and control system components is given in Section 3.1.

Pointing and Control System Design

Control System Configuration

All telescope control is via commands passed to the telescope control computer (TCC) via a user at a keyboard, or from another computer.

Several peripheral microcomputers implement control functions locally near the telescope. The microcomputers effectively relieve the TCC from a large amount of real time control and create convenient modularity of system hardware functions.

Figure 4.1 shows the interconnection of the components of the telescope control system. The system is hierarchical with the telescope control computer (TCC) at the top.

The TCC is connected to the azimuth controller (AzC), the altitude controller (AltC), the secondary controller (SC), tertiary controller (TC), the bright star camera controller (BSCC), the two instrument changer controllers (ICC1 and ICC2), the weather monitor controller (WMC), and the wind screen controller (WSC).

The AzC and AltC are identical hardware and run essentially identical software except for the values of a few constants. Each implements the digital state variable control system for that axis. The SC controls the tilt and piston of the secondary. The TC controls the position angle of the tertiary, field rotation for the two Nasmyth field cameras, and instrument selection in the two instrument changers.

ICC1 and ICC2 each control field de-rotation for one instrument changer for those instruments which require this service. The BSCC locates and centroids the brightest star in its field and returns this value to the TCC upon request. The WMC supplies the TCC with real time weather data including temperature, pressure, and humidity. The WSC controls the position of the wind screens.

The TCC and BSCC are located in the telescope control room in the main building. The WMC is mounted along with its transducers on top of a tower near the telescope enclosure. The other controllers are mounted in the telescope enclosure in close proximity to the device(s) they control.

The datalink between the controllers and the TCC is a hierarchical bus which uses the RS-232 protocol for asynchronous serial data communication. The long link between the control room and the telescope will be a fiber optic which will fan out into a fiber optic star configuration at each end thereby providing the necessary ports.

The TCC will be the bus controller and the other devices will send data only when requested by the TCC. This will prevent collisions and allow the TCC to schedule time critical tasks first when necessary.

Software design

A detailed software development methodology has been adopted to insure the timely completion of this critical project component. The definition of software requirements is being done at the present time using the data as the viewpoint. A data dictionary will be assembled in conjunction with the high level software design phase. This will be done in close coordination with the data acquisition and analysis software design which is the primary responsibility of The University of Chicago, thus insuring software compatability at the design level. At this point software components will be checked against the requirements to verify that they are met. After the high level design phase is complete it will be turned over to the programmers who will do a detailed design in pseudocode. We will use the stuctured walk through technique as part of the verification of the detailed design. The detailed design phase will be followed by the actual coding of the software. This will be completed in a timely manner leaving sufficient time for software testing and verification.

Encoding Strategy

Under ideal operating conditions encoder resolution will determine entirely the axis servo contributions to telescope pointing error. The somewhat novel encoding design we propose is low cost (Appendix), has a quantization error of 0.025 arc sec tracking, 0.025 arc sec offset over 10 degrees, and <0.5 arc sec rms over the visible sky.

25-bit Virtual Encoder

Each axis will be coupled to two encoders, a low resolution (9-bit) absolute encoder on axis and a high resolution (65535 count) incremental encoder friction coupled to a virgin portion of the drive disk tire not contacted by the drive roller.

Electrical code transition angles for the absolute encoder repeat to about 1arc sec. The coupling ratio for the incremental encoder is determined so that each increment corresponds to 0.04 arc sec of telescope axis rotation.

Each encoder is interfaced to a real time microprocessor controller. Using the incremental encoder as an interpolator between absolute encoder transitions, the system software synthesizes in effect a virtual absolute encoder with 25 bit resolution, 1 arc sec accuracy over large angles and high relative accuracy over smaller angles.

User-Transparent Offset Pointing

An improvement in pointing accuracy can be achieved by offsetting from standard star positions. This will be done entirely by the control system in a manner transparent to the user.

The Smithsonian Astrophysical Observatory (SAO) catalog is readily available in machine readable form. In a 3.5 meter telescope all 260,000 SAO stars are bright enough for real time acquisition using an inexpensive unenhanced CCD surveillance camera operating at the focus to encode a small patch of sky and serve as a 'crosshair'. Since they are so inexpensive, it may be desirable to provide one at each Nasmyth focus devoted entirely to the offsetting function and fed by retractable pickoff mirrors.

Accumulating Coupling Errors

One might say we are using 'analog gears' rather than 'digital gears' and must therefore expect real errors to accumulate over all motion scales. Fortunately there are simple ways to estimate such errors.

We have conducted controlled tests of our own in the UW Physics machine shop where several machine tools utilize retrofitted friction wheel micrometers to encode tool motions over distances of 0.5 to 1 meter.

These devices reproduce position readings to no worse than 1 micron (the dial reading limit) after many arm-tiring manual cycles of motion. At the edge of a 4 meter disk, 1 micron over 0.5 meter corresponds to about 0.1 arc sec over 14 degrees.

This suggests tracking with less than about 1 arc sec accumulated error may be possible over the entire sky (180 degrees). Existing telescopes with friction encoders do not currently perform this well all night. Thermal gradient drive disk distortion is surely a factor here as well as contact microslip. Our conservative encoder system design does not depend on the incremental encoder to do offsets over angles greater than about 40 arc min, the angle between two absolute encoder transitions.

The incremental encoder will be used for movements over all angles for which accumulated errors are smaller than the absolute encoder accuracy (1 arc sec rms).

The very familiar alternative of star-tracked offset guiding of course will not be excluded.

Daylight Observing

Daylight infrared observing is not to be precluded. Daytime solar radiation is likely to cause larger thermal gradients in the telescope structure. Since IR detectors have large pixel sizes compared with optical arrays, the pointing and tracking requirements are correspondingly relaxed.

There are of course offset stars available during the day, and observable using the CCD encoding camera. The smaller number of stars available will correspondingly degrade offsetting precision.

Axis Controllers

Control System Design

During active pointing of the telescope, each axis will be commanded to specific pointing angles and tracking rates by the TCC and will be controlled to acquire the commanded angles and rates by a feedback control system using the encoder and motor tachometer outputs. Figure 4.2 shows the components of the control loop for the axis controller. Such a feedback mechanization serves to attenuate pointing errors that would arise from varying characteristics of controller components and from external disturbances (e.g. wind loading). However, the existence of a feedback path alters the dynamic response of the system and imposes additional requirements in terms of stability, transient response to commands, and steady-state tracking errors. Meeting these requirements, and thus achieving the desired pointing accuracy, is accomplished by the design of the control algorithm which is implemented in the axis controller microprocessor. That design is developed by analysis of the dynamic characteristics of the system as indicated in the subsequent paragraphs.

Dynamic Models

For each axis of telescope pointing, the dynamic response of the system to pointing commands can be modeled as consisting of two coupled elements, namely the DC electric motor response and the structural response of the telescope inertia and drive train compliance. Structural vibration of the telescope tube structure can be ignored because the stiffness of that structure causes its vibration frequencies to be well above practical control bandwidths. However, this is not the case with compliance in the elements of the friction drive, which produces a vibration mode commonly referred to as the locked-rotor resonance frequency (LRRF).

These elements and their coupling can be represented by linear, ordinary differential equations, thus providing a state space representation of the system (Kuo 1982 and Electrocraft Corp. 1980). For the selected motor and drive characteristics this model will be 4th order for each axis. From this representation, transfer functions can be derived to permit frequency response analysis and the application of classical linear control theory. A major concern in the derivation of these models will be to specify the range of variation of parameters in the models (e.g. inertia) so that controllers of sufficient robustness (i.e. with sufficient margins) can be designed to assure stability and good performance under all operating conditions.

Compensator Design

The need for compensation in the feedback control loops arises from the nature of the dynamic models, in order to provide stability and pointing accuracy. The derivation of state space models for the system and the presence of multiple sensors suggests the use of multivariable control theory for the design. However, since there are only two inputs and a single output for each axis, the resulting multivariable compensators should not differ greatly in characteristics from those that would result from a more classical design, as has been done for the MMT (Ulich 1982).

Characteristics to be expected in the design will include: 1) some form of notch filter to improve damping of LRRF while providing a relatively wide bandwidth (e.g. 5-10 Hz) to counter turbulent wind loading, and 2) sufficient integral control to permit following a varying rate command without significant pointing error. The use of a digital microprocessor to implement the compensation, and the inherent discrete character of the encoder output, suggests a direct digital design for the compensators.

Computer tools exist at UW to perform both multivariable and classical single loop analysis and design for digital control systems. Thus, compensator design is expected to proceed in a straightforward manner.

Performance Assessment

The pointing control loops will be designed to achieve desired tracking accuracy, in the presence of anticipated disturbances due to turbulent winds, based upon linear models of the system dynamic response. But this design analysis will not be sufficient to predict performance of the control system due to presence of unmodeled nonlinearities. These effects will become important when efforts are made to squeeze the best possible performance from the system.

Among the types of effects that will need to be assessed are the following:

  1. limiters on rate (and possibly acceleration) which serve to remove active damping provided by the compensation

  2. nonlinear effects within the DC motor and the amplifier which which drives it

  3. quantization effects in the digital elements of the loop

  4. friction effects in the bearings, particularly one noticed in the MMT azimuth bearing which appears to be due to the transition from static to (lubricated) rolling friction and produces a negative damping effect at typical tracking rates (Davison and Ulich 1982).

To assess fully the impact on performance of these effects, a detailed computer simulation of the system will be needed. Such a simulation can be used in a variety of ways, including assessing performance of controller designs in the presence of the above nonlinearities, verifying control algorithm software before it is implemented in the telescope computers, and aiding in the assessment of performance anomalies once the telescope is in operation. A trade study on the approach to development of this simulation capability will need to be carried out.

Control System Components

The two axis controllers are identical. Position information comes from an incremental encoder which is friction coupled to the axis drive disk. The encoder output consists of two pulse trains differing in phase by 90 degrees. This goes to a decoder/buffer where it is buffered by a 16 bit up/down counter which stores the axis position in units of the encoder resolution modulo 65536. A larger amount of buffering is not necessary since the processor will read the counter frequently enough to prevent ambiguity.

The output of the encoder buffer goes into a 16 bit parallel processor port. The output of the absolute position encoder goes into another processor parallel port. The absolute encoder is used to implement software limits to motion by the axis controller and is sent on demand to the telescope control computer which uses it as part of its determination of the zero point for the coordinate system defined by the incremental encoders.

The velocity of the motor shaft is sensed by a tachometer integrated with the motor. This signal is digitized by an A/D converter. Information from both the motor shaft and the telescope drive disk allows the control system to calculate the amount of wind up in the drive train and to correct for this effect.

The processor implements the digital state variable control system. This sampled data system operates at approximately one hundred cycles per second; well above the bandwidth of the servo loop. Each cycle the processor estimates the current state of the system based on the transducer outputs. It calculates the desired state of the system based on commands from the telescope control computer. Then it generates an output to achieve that state.

The digital output is converted to an analog output by a D/A converter. The low level analog output command is amplified by the motor controller and used to drive the motor. The motor is coupled to the telescope axis by azero backlash speed reducer which turns the drive roller. This roller is pressed against the axis drive disk with a contact force sufficient to insure that slippage will not occur.

Telescope Control Computer

The telescope control computer (TCC) is the overall master of the telescope except for the instruments mounted on the telescope. The TCC has a number of functions besides telescope pointing and tracking, including secondary focus and tilt, tertiary rotation, field camera control, instrument selection, and field rotation. Each of these functions will be implemented with its own intelligence on the telescope and the system will be designed with a very conservative value for TCC operating system and bus latency. This can be accomplished by queuing commands in some of the controllers when necessary.

The TCC will be largely insulated from the real time requirements of the task by the controller components of the system. The TCC provides the user interface between the astronomer and the telescope or between the astronomer's computer and the telescope. As such it will accept high level pointing and tracking commands. The SAO catalog will be read accessible to the users and utilities will be provided which will allow the users to create and edit their private catalogs of objects which they wish to observe. We expect that most observers will wish to grant read access to their program object files but file protection will be available. The telescope will point to objects specified by their coordinates in arbitrary epoch or will search in the designated files for the coordinates of objects specified by name.

The SAO catalog is readily available in machine readable form and is a compilation of objects from other catalogs. Because of this its overall precision is nonuniform, but on the average is better than about 0.5 arc sec; estimated position errors, proper motion and the estimated error in the proper motion is included with each entry. The SAO catalog contains more than 250000 stars and nearly every point on the sky is within 0.5 degree of a star in the SAO catalog.

The TCC will provide a status display indicating where the telescope is pointed in right ascension and declination and galactic coordinates, the number of air masses in the optical path, the current time, etc.

Primary Modes of Operation

The TCC plays an essential role in the telescope pointing control system. To slew to a new field the TCC will send new position and tracking commands to the axis controllers which will check the commands for errors and if legal will determine appropriate velocity ramp up and ramp down profiles and the necessary slewing time. The new location commanded by the TCC will be updated during the slew using the commanded tracking velocity for the new position thus accounting for the slew time.

During aquisition of a new object the TCC will periodically reset the zero points of the alt-az coordinate system by pointing the telescope at a SAO catalog position reference star and requesting the field camera controller for the position of the star centroid in the field. Alternatively it can request the axis controllers for data from the absolute encoders which in turn can be used to reset the zero points.

During tracking the TCC sends the axis controllers the velocity commands necessary to track a celestial object. It takes into account the alt-az RA-dec coordinate transformation, telescope flexure, atmospheric refraction, mechanical telescope misalignments, etc. The TCC will perform closed loop tracking control by periodically requesting the telescope position from the axis controllers and sending correction commands as required.

Secondary Modes of Operation

Startup and Encoder Calibration

Attention will be paid to secondary modes of operation during the design of the telescope control system. These include start-up, power-up after a power failure, shut-down, power failure, maintenance and component failure. Start-up and power-up will be handled identically. Power will be applied to the motors only after self diagnostics have verified the proper operation of the components. Similarly during shut-down and power failure power will immediately be removed from the motors. The TCC will provide the reset function for the telescope function controllers.

There will be three levels of encoder calibration: At installation time, when initial setup parameters for the telescope are determined; after occasional power failures; and every time a slew occurs to a new object.

Calibration at installation - once and for all

At telescope installation time one full turn of the azimuth axis is performed by the computer to determine the number of encoder increments between two successive detections of the same absolute encoder angle and to map the absolute encoder in incremental encoder space. A similar operation (TBD) is performed for the altitude axis. This information is saved on non-volatile storage.

Next a bright star is boresighted onto the CCD camera frame. Initially this will require operator participation. Noting the time and the pixels on which the star image falls, the computer, using the known star position, now calibrates telescope coordinates. In this context the CCD pixels serve the function of a crosshair. At this time the fiducial positions in alt and az space (referred to the TV frame) are determined once and for all. These values are also stored on non-volatile storage and the telescope system is now ready to perform a power up cold start at any time.

The scale of incremental encoder tick per telescope axis rotation and the relative positions of absolute encoder transitions in practice will fail to repeat at some level. Frequent re-determination of these values is expected to be a routine engineering function of the TCC software.

Power up Initialization

If an orderly power fail shutdown was performed then no recalibration will be necessary at power up. If telescope position was lost however then the following steps are performed automatically.

At a cold start, the telescope computer first rotates the telescope until an absolute encoder CHANGE is detected. The incremental encoder buffer register is initialized at this position. The 25-bit virtual absolute encoder is now initialized 1 arc sec rms accuracy.

Initialization on each new object

Each time a slew to a new object is commanded by the observer, the telescope computer finds the SAO star nearest the destination object. A slew to the standard star then occurs; arrival will be within a few arc seconds using the incremental encoders. The bright star camera controller locates the star image and calculates the position of its centroid in the field. This information is used to reset the zero points of the axes coordinate systems if necessary. Then the slew to the observers object is made, a distance of not more than about 1 degree. The time required for the telescope to execute this procedure is negligible and appears transparent to the user.

Maintenance

During maintenance test software will be available to allow thorough verification of the system. Also a positive method of locking the drives will be provided to safeguard personnel working on the telescope.

Failure

Frequently in computer controlled telescopes inadequate fail safe operation has been provided, leading to runaway conditions where the telescope takes off at slew rates and stops only when it reaches one of the horizon limits.

We propose to largely avoid this problem by incorporating software in the axis controllers which will check commands from the TCC for possible errors before execution. The axis controllers will also check for consistency between the telescope position and rate transducers since the position signal can be differentiated to give a rate. The axis controllers will assume that an error in position which cannot be corrected in a reasonable time is due to a fault such as D/A or amplifier failure or an external obstruction or load and will cut power to the motors and set brakes.

A watch dog circuit will be implemented for each controller. In normal operation the controller software will reset the watch dog every 100 milliseconds. If the controller fails to reset the watch dog for any reason (e.g. if the program bombs) this circuit will cut power to the drive motors. The TCC will provide high level monitoring of the axis controllers for faults.

The philosophy in the control system design is to detect all single point failures and stop the telescope before any damage or injuries occur and to identify the failed module to facilitate rapid repair or replacement.

Implementation

Components are described in this section in some detail in order to give a specific example of the design described in Section 4-2. It is likely that most if not all of the numbers given below will change as our design becomes more complete.

Motors

The axis motors will be DC servo motors rated at 2000 rpm and 5 N m. Each motor will have an integral tachometer with a sensitivity of 10 V/krpm. The moment of inertia of the telescope seen by the azimuth motor through the drive train is 0.10 kg m^2. The value for the altitude axis is 0.036 kg m^2. Motors with rotor moments of inertia small compared to these values are readily available. Electrical time constants of 5 milliseconds are readily available; the system pole due to motor inductance can be ignored.

Amplifiers

Each motor controller (power amplifier) is rated at 12 amps at 150 volts DC and are readily available from several sources. Circuit protection features are standard and include current limiting and fusing.

Drive Train

The coupling between the motors and the axes is yet to be determined. The required total reduction ratio is 1000:1 of which 30:1 is due to diameter ratio of the drive roller to the driven disk. The rest of the reduction will accomplished using commercial components if ones of adequate stiffness which are backlash free can be located. Otherwise we will design an additional stage of friction roller reduction.

Other alternatives include using a pair of spur gear reducers driven by two separate motors with a DC offset so that one is preloaded against the other. The extra complication of this design is to be avoided if possible. Another possibility is that the drive roller could be driven directly with a150 N m torque motor. A trade study will be done to choose between these alternatives.

Processors

The axis controllers will be CMOS processors thereby reducing the heat dissipated at the telescope to negligible values. The state variable control system is implemented digitally by performing matrix multiplications and additions. By the time that the components are specified, components with the required processing capability will be readily available; adequate components are currently available.

One constraint which has not been investigated in detail at this time is the operating temperature range specification. Since we require operation down to -20 C we require better temperature specs than standard consumer specs. The effect of this requirement on cost and availability has not yet been determined; it can be avoided by providing temperature controlled enclosures for the electronics. Since the enclosures would be small they could be insulated very well and would require very small amounts of heat to meet temperature specs of consumer parts. Still the simplest solution is to buy electronics which will run at the ambient temperature.

The software for the axis controllers will be written in FORTH, a language which is unexcelled for real time control applications. FORTH executes rapidly; time critical functions can easily be recoded in assembly language when necessary.

The TCC will be a 68000 class microcomputer interfaced to a hard disk drive with approximately 20 megabytes capacity. The TCC will be connected to the data aquisition and analysis computer and its disk and tape drives most likely via Ethernet. The TCC software will be written in a high level language such as Pascal or C under a standard operating system such as UNIX.

Tach A/D

The tachometer analog to digital converter will be at least 12 bits (16 will be used if readily available and inexpensive at component specification time). Full scale will be set to give good resolution at slow speeds; at high speeds the incremental encoder information can be differentiated to give accurate rate information. Also at high speeds the accuracy requirement of the control system is relaxed (either a slew is in progress or the telescope is pointed near the zenith where pointing is relatively insensitive to azimuth angle). The control loop execution rate will be about one hundred Hz. This sets the requirement on the A/D speed and is very modest. Fifty-microsecond 12 bit A/Ds are readily available and are inexpensive.

Amplifier Drive D/A

The requirements for the D/A which sends output commands to the motor controller are mild. 12 bits of resolution are certainly sufficient and the conversion speed requirement of a few hundred microseconds will be met by almost any D/A converter currently available. A word of elaboration is appropriate here. The effect of the D/A is to command a torque to be applied to the system. This is because the electrical time constants involved are so small that they can be neglected. This is in contrast to the digital portion of the MMT control system which sends a velocity command to the analog inner loop. In our case the quantization error in our control torque corresponds to 1/2 the least significant bit of the encoder or 1 part in 4000 of full scale for a 12 bit D/A. This error has the same effect on the system as a wind induced torque of the same magnitude. Using reasonable numbers this corresponds to a 0.6 m/s (1.4 mph) wind which is clearly a negligable disturbance to the system.

Encoders

Absolute encoder

An actual encoder candidate is the BEI Model 5V682A used in the Space Shuttle remote manipulator. A relatively unappreciated property of this encoder (and perhaps others like it) is the very high angular repeatability of electrical code pattern transitions.

Figure 4.3, provided by the encoder's designer Paul Johnson of BEI shows the results of high precision optical autocollimation measures of 32 code transition angles for the 5V682A both before and after a rugged environmental test. The mean of before-after residuals is 0.44 arc sec with arange of 2.5 arc sec peak to peak.

The cost is $3800 for the 16-bit version. A newer less expensive 16-bit encoder, model M25 ($2200) is also available. It is equally repeatable and more rugged. These prices represent upper limits to our cost as we do not anticipate the need for the 16-bit version.

Coupling
Figure 4.4 shows a proposed method of coupling the absolute encoder directly on axis. The telescope azimuth load bearing is mounted with inner race fixed and outer race rotating. This leads to a convenient encoder coupling topology since a stationary on axis encoder base is provided on the exposed end of the bearing inner race stub axle.

After azimuth axis installation, a fixture is bolted concentrically to the stub providing complete load isolation between the driveshaft and the encoder. The hollow tubular driveshaft is suspended at its ends by lash free flex-disk universals. The flex di