Subsystem Build & Test
Table of Contents
Your website should document your journey through MSD, so include work-in-progress as well as latest results. Use pdf's for display whenever possible so that information is easily viewable without the need to download files and open applications. (Your EDGE file repository should still contain original editable files).
All template text must be removed prior to your Subsystem-Level Build & Test Review
Team Vision for Subsystem Level Build & Test PhaseSummarize:
- Continue working on the Arduino controller code to control the dish.
- Come up with an error tracking algorithm using the LED stack light as the indicator
- Complete the user interface
Summarynote: put some picture on it i guess. Like the stack LED and a chart of the dish control limitation,.... Summarize test results and assess effectiveness of test plans to unambiguously demonstrate satisfaction of the engineering requirements
Dish controlDish Control:
- Arduino controller code works properly, and can be tested without application using the serial terminal PuTTy.
- Dish calibration gets forward and reverse limits of both Linear Actuator and Rotary.
- The 'home position' or 0 postion is the median value between the forward and reverse limits, it lies directly in between both limits.
- To test the SunTracker functionality to see if it works properly, the application initiates the motor controller by performing calibration, the Linear Actuator and Rotary values are given directly to us via a test window.
- Following if we have a successful operation, we will the begin to work on translating the Altitude/Azimuth coordinates to Linear Actuator/Rotary pulses, then will begin implementation.
- After translating the Altitude/Azimuth coordinates, we then will begin working on the Automatic Sun Tracking system.
Status lightStatus light:
- The P19571 Stack Light, created by Nicolas Law is a
Stack Light that has 3 sets of LEDs; Green, Yellow, and
Red. Each set has two LED lights, one on and one off.
- The Green Light indicates that all systems are nominal. The green light will begin to blink when the Dish is calibrating. When the dish is calibrating with the Arudino it sends power to the Linear Actuators which cause them to move. After moving the Linear Actuators send back pulses to the Arduino giving the location of each motor in which we can determine based off the pulse values.
- The Yellow Light indicates a Recoverable error or
- When the yellow light is blinking, this indicates that there is powerloss and is running on backup power.
- When the yellow light is blinking it could also indicate that there is no internet connection.
- When the yellow light is blinking, this could indicate that the Dipole Reciever is down.
- When the yellow light is solid this could indicate that the Zulrich server in which the program sends its raw data to, is down.
- When the yellow light is solid this could indicate that the we are in Manual Operation mode allowing us to manually move the dish.
- The Red light indicates that there is a critical
- The Sun radio frequency recievers are down.
- There is some sort of motor failure on the dish.
- The SunTracker, or Callisto software is not
- When there is mutiple critical failures the status light will blink red.
Radio Frequency switches (RF)
- Each radio frequency reciever is connected to a RF switch, the switches allow for us to calibrate the range that the RF recievers will get from the incoming RF data.
- Each switch has a 0% load, and a 100% load, as well
as the actual RF source taken from the sky.
- The 0% and 100% loards are used for calibrating what range of RF data is so that it can be mapped effectively.
- The Arduino controls which source is used, which is determined by the SunTracker program itself.
- The team needs to construct a voltage divider to bring the Arduino's 5V output down to 3.3V.
- We also need to construct an inverter which will allow us to power the RF switches with 3.3V and -3.3V voltage lines.
Outputs & Destination
- Test Results
- System integration
Risk and Problem Tracking
Plans for next phase
- As a team, where do you want to be in three weeks at your next demo?
- As an individual on the team, what are you doing to help your team achieve these goals? (Use the individual 3-week plan template for this)