NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Main > TWikiUsers > MelindaMello

Users | Groups | Offices | Changes | Index | Contents | Notify | Search | Jump to Topic:

• Name: melinda mello
• Login Name: mmello
• Email: mmello@nrao.edu
• Phone: 456-2143
• Department: sdd
• Location: GreenBankWV
• Comment:

Workspace

Modification Request #???? (C03 2008)

• • OCU replacement
• 1. Introduction
• 2. Background
• 3. Requirements
  • 3.X CCU to OCU Interface
    • 3.x.1 Secure Interface
    • 3.x.2 Protocol -maybe needs to be moved into design section
    • 3.x.3 Control Commands
    • 3.x.3.x Control Modes
    • 3.x.4 Status Mechanisms
• 3.x Heartbeat
• 4. Design
• 5. Add Any More Sections That Are Appropriate
• 6. Deployment Checklist
• 7. Test Plan
  • 7.2 Sponsor Testing
• Signatures
• CCC Discussion Area
• Config tool wish list
• Gbtstatus wish list
• Other

OCU replacement

1. Introduction

2. Background

3. Requirements

3.X CCU to OCU Interface

3.x.1 Secure Interface

3.x.2 Protocol -maybe needs to be moved into design section

3.x.3 Control Commands

• TBD range checking, done here or at CCU level...if here, it would be done twice, not such a great idea
• AllStop
• AEPreset - Presets will allow the operator to optionally set a maximum rate (excluding 'ramp-up'). The system will support the following presets. System will provide the ability to add presets as operational requirements dictate.:
  • Access
  • BirdBath
  • Survival
  • SnowDump
• AEStow - Only Elevation should be effected by this command. All stow commands will put the pin in. The stow alignment positions are Snow Dump (@ 5.131 degrees), Survival (@ 60.105 degrees), Bird Bath (@ 65.864 degrees, Access (@ 77.850 degrees, 90 degrees (@90.052 degrees).
• AEUnstow - Only elevation stow pin should be affected by this command
• SRStop
• SRStow
• SRPreset -
  • stow
  • home
  • max Yn
  • max Xn
• PFStop - NOTE: only one operator used this functionality, the other operators performed an ALLStop instead.
• PFPreset
  • Additional functionality: multiple preset positions (at a minimum PF1 and PF2) are required.
• TUStop
• TUPreset
  • There must be two turret presets for each turret position corresponding with the locked and removal positions.
  • Each Turret preset position should be label with a text label similar, if not exact, to the current labeling system e.g.: K_BAND_230.
• BoomPosition
• Boomstop
• Control - Please refer to section 2.2.4 for control arbitration state diagram.
• AZ En/Dis
• El En/Dis
• Az Drive Enable
• El Drive Enable
• PF Drive Enable? TBF asked for clarification in section 3 of general spec
• SR Enable? TBF asked for clarification in section 3 of general spec

The following commands will be rejected if the AZ or Elrequire a separate enable command.

• AEPosition - The current functionality should be implemented which includes an optional cablewrap input. The nomenclature for the cablewrap should be changed to "CW" for clockwise and "CCW" for counter clock wise. No commands will be accepted unless the axis is enabled.
• PFPosition - No commands will be accepted unless the axis is enabled.
• SRPosition - No commands will be accepted unless the axis is enabled. Command shall be accepted in astronomic (X,Y,Z,Xt,Yt,Zt) or engineering (X1,X2,Y1,Y2,Y3,Z1) coordinates.

3.x.3.x Control Modes

• The Operator must be able to take control from the M&C system at any time.
• The Operator may NOT take control from the Manual Control when it is active.
• The Operator must be able to stop an Auto-stow situation that is triggered by loss of power.
• The Operator must be able to release control to another system. This will be supported with a general release mechanism allowing any of the follwing systems to take control:
  • M&C
  • Manual Control Unit
  • A remote OCU -(TBF - arbitration may be at a different level, perhaps vnc)

3.x.4 Status Mechanisms

• Status information will be supplied to the OCU no matter which application or manual unit is in control
• latching faults
• text messages with time stamps - IDEAS: xml that can be read without rebooting, so that "new messages" for kernel upgrades can be handled? Is this to flexible?
  • list messages from existing OCU that will be duplicated or at least functionaility will be duplicated.
  • levels
• ladder like fault tree,
• position, rate and command displays
  • Primary Axis
    • Display of the commanded and indicated positions (in degrees)
    • Display an indicator of the position with respect to the cablewrap
    • A status field
      • "Fault" in the status field indicates a fault in the system.
      • When no faults exist in the system, the status field will be blank.
  • Secondary Axis
    • SubReflector? (change to display in mm or inches)
      • X, Y, Z, Xt, Yt, Zt
      • Y1, Y2, Y3, X1, X2, Z1
    • Turret
    • Prime Focus
      • Pol
      • X
      • Focus

3.x Heartbeat

4. Design

5. Add Any More Sections That Are Appropriate

6. Deployment Checklist

What has to get done to integrate this completely into the system. This checklist must be completed before Cycle Integration Testing begins.

7. Test Plan

-

7.2 Sponsor Testing

Signatures

APPROVED: I acknowledge that to the best of my knowledge, my request is fully contained in this MR.

ACCEPTED: I acknowledge that I have validated the completed code according to the acceptance tests, and I am happy with the results.

Written	- MelindaMello -
Checked
Approved by Sponsor
Approved by CCC
Accepted/Delivered by Sponsor	symbol - name - date

Symbols:

• Use %X% if MR is not complete (will display )
• Use %Y% if MR is complete (will display )

CCC Discussion Area

-- MelindaMello - 18 Apr 2008

Config tool wish list

• add config tool to gbt.ygor module
  • modularize common dictionaries that other apps and apis can use--such as receiver pol switch parameters, backend IFs, receiver sidebands
• Make a dependency tree for all frequency calculations and update documentation
• Make a dependecy tree for all parameters and update documentation
• Change spectrometer, spectralprocess etc. ifpath to receiver code and remove the recever FEEDS_AND_BEAMS dictionary
• re-design config tool as api (originally designed as app)

Gbtstatus wish list

• pretty up the wx status screen
• add user designated parameters and samplers

Other

• Move from prototype balancing api to a complete package
• Write an ygor manager for the penn array that removes our dependency on IRC.
• Get involved with E-E
  • Observation Scheduler
    • investigate observation parameters..meta data needed
    • particapate in design and implemetation
  • ?

Personal Preferences (details in TWikiVariables)

• Horizontal size of text edit box:
  • Set EDITBOXWIDTH = 35
• Vertical size of text edit box:
  • Set EDITBOXHEIGHT = 25
• Style of text edit box. width: 99% for full window width (default), width: auto to disable.
  • Set EDITBOXSTYLE = width: 99%
• Optionally write protect your home page: (set it to your WikiName)
  • Set ALLOWTOPICCHANGE = MelindaMello?
• • RELEASEEDITLOCKCHECKBOX = "checked"

Related topics

• TWikiPreferences has site-level preferences of GB.
• WebPreferences has preferences of the GB.Main web.
• TWikiUsers has a list of other TWiki users.