Customer Handoff & Final Project Documentation
Table of Contents
Team Vision for Final Demo and Handoff
Team Plans for Phase
Overall, our team planned to wrap up any outstanding issues with the project and ensure adequate preparation for Imagine RIT.
The EE team had a variety of plans to complete the project. The most important of those plans was to complete testing of the feedhorns, remote antenna switch, and low noise amplifier. The feedhorn and dipole boxes needed to be installed and their devices mounted internally. A method of powering the noise source in the receiver box needed to be determined. Another important item was to update the electrical schematic to include new wiring for the remote antenna switch and the observatory.
The ME team made several plans regarding the final installation in Ionia. Brendan planned to work with the EE team to mount the feedhorn and dipole boxes.
The CE team planned to finalize the motor calibration, implement the additional temperature sensor, and finalize the automation of the PC.
Team Accomplishments for Phase
Our team accomplished much of our goals, but we had to change our plans due to an alteration of Imagine RIT plans. Our customer notified us that we would be unable to move our project to the Ionia observatory as planned. Instead, we will retain the project here at RIT to present it at Imagine RIT instead of presenting it remotely.
Due to this change, Brendan was forced to scrap many of his installation plans. However, he still completed his goals of drilling and mounting components in the feedhorn and dipole boxes. He also mounted the feedhorn antenna using a trimmed block of wood. Brendan drilled holes in each box to fit grounding cables.
The EE team also accomplished many of their goals. Jeff S, with help from Jeff K, finalized the selection of a boost converter that would increase a 5V input to 17.5V to feed into the noise source. Jeff S and Jeff K also developed and implemented connections for the bias tees and the LNAs that would go into the dipole and feedhorn boxes. Jeff and Jeff also installed 10-foot cable extensions for the PC power boot button and the kill switch, so they could be fed through PVC pipe to the observatory. Jeff K also performed plenty of testing this phase, completing remote antenna switch testing and feedhorn testing with Adam's help. Adam finalized the schematic to include all changes, adding a wire legend and differentiating between USB cables, power cables, coaxial cables, and normal power wires. Adam also led an effort to begin documentation of the electrical schematic to ensure that any subsequent teams started on better footing than our team did.
During the phase, we encountered a variety of issues, one of which was a sensory problem with the linear actuator. Brendan helped calibrating the Hall sensor and rewired it along with Jeff S and Adam, solving a problem that we had encountered for many weeks where the linear actuator hadn't been providing complete positional information.
Zak continued motor testing and verified radio eyes can control the dish appropriately. He also implemented the RAS controls and the calibration process for the Callisto hardware. Nate accomplished his goal of automating the PC startup sequence, allowing the PC to start all required programs after a restart.
Test Results Summary
Remote Antenna Switch Testing
Smith ChartsTerk LOGTVO - Log Periodic: Unnamed Dipole (non-rectangular):
SWRTerk LOGTVO - Log Periodic: Unnamed Dipole (non-rectagular):
Risk and Problem Tracking
|Risk ID||Category||Risk Item||Effect||Cause||Likelihood, L (1-3) 3=most||Severity, S (1-3) 3=Worst||Importance, L*S (1-9) 9=most||Action to Minimize Risk||Owner|
|R1||Technical||Improper feedhorn installation||Feedhorn may have loose mounting or be unable to be assembled.||Heating or cooling during drilling.||0||0||0||Use heat sink and lubricant during feedhorn installation||Mechanical Engineer|
|R2||Technical||Unreliable internet connection to Zurich||Packets of information could be dropped||Severe thunder storms or overcast weather||3||1||3||Provide data backup until Zurich server confirms reception||Computer Engineer|
|R3||Technical||Dish may be too heavy for motors/actuators||Tracking functionality is lost, manual repairs required||Ice buildup, power depletion, errors in measurements||1||2||4||Provide flags and warnings to warn users of imminent disruption||Computer Engineer|
|R4||Technical||File transfer system error||Zurich server receives incomplete data||High frequency of power interrupts beyond design of UPS||0||0||0||Provide data backup until Zurich server confirms reception||Computer Engineer|
|R5||Technical||Auto-calibration error||Incorrect data analysis, manual repairs required||Drift of control systems over time||0||0||0||Provide recurring updates to autonomous calibration results||Computer Engineer|
|R6||Technical||TeamViewer software error||Remote operation made difficult or impossible||Incorrect data structures and / or program speed||0||0||0||Use cross-platform coding techniques||Computer Engineer|
|R8||Technical||RadioEyes/LabView incompatibility||Additional time required for integration solution||Incorrect data structures and / or program speed||0||0||0||Use cross-platform coding techniques||Computer Engineer|
|R9||Technical||Feedhorn selection may carry unexpected collaterals (integration)||RX levels may become inefficient for extraction from raw signal||Mismatching impedance and frequency response||0||0||0||Perform extensive testing on feed/dish assembly||Electrical Engineer|
|R10||Technical||eCallisto software error||Data may be corrupted or incorrect; Zurich may not recieve data at all||Improper program setup / unforeseen program error||0||0||0||Perform extensive software testing and provide data backup||Computer Engineer|
|R11||Technical||Internal EM interference within subsystems||May cause errors in computer operation or other subsystem operation||Improper magnetic shielding on power lines near vulnerable systems||0||0||0||Isolate magnetic interference, or place wiring more carefully||Electrical Engineer|
|R12||Technical||Improper power management||One or more subsystems failing due to internal power loss||Power delivery system insufficient to meet power needs||0||0||0||Perform extensive power system simulations||Electrical Engineer|
|R13||Technical||Internal subsystem overheating||Damage to one or more subsystems||Improper cooling systems or lack of temperature sensor||0||0||0||Place temperature sensors in overheat locations||Mechanical Engineer|
|R14||Resource||Scarcity of integration and/or testing facilities||Project receives unexpected delays waiting for facilities||Primary facilities are 1 hour away.||0||0||0||Establish carpools and overlap schedules to ensure effective use of lab||All|
|R15||Resource||Insufficient budget to meet all project requirements||May need to take performance hits to accommodate cheaper budget||Limited funds (~$500)||0||0||0||Design and build where possible||All|
|R16||Resource||Destruction of "Suntracker" project hardware||Loss of unique designed hardware, project delays||Incorrect assumptions about input levels and tolerances||0||0||0||Implement strict guidelines for interacting with unique hardware||All|
|R17||Resource||Inadequate space to assemble and test||Team may not be able to prove that the project works||Necessary space or devices not easily available||0||0||0||Ensure that proper space or devices are reserved well in advance||All|
|R18||Resource||Theft of system components||Irreplaceable components may be lost||Improper storage of materials||0||0||0||Lock physical project materials in a locker||All|
|R20||Resource||Critical team member or project sponsor becomes unavailable||Project will be more difficult to complete without assistance from team member or guidance from sponsor||Team member or sponsor is injured or unavailable||0||0||0||Obtain guidance from faculty advisors; Maintain team awareness||All|
|R21||Resource||Insufficient manufacturing tools available||One or more subsystem additions may not be able to be completed||Limited budget and/or resources of RIT or sponsors||0||0||0||Prioritize subsystems based on accessibility||All|
|R22||Safety||Team member injury during construction||Slowed rate of project work while team member recovers||Improper safety measures taken during construction and use||0||0||0||Observe proper safety rules during device construction and operation||All|
|R23||Environmental/Social||Other unwanted data could be intercepted||Zurich server recieves incorrect data||Improper selection of device reciever frequency||1||1||1||Filter unnecessary data||Computer Engineer|
|R24||Environmental/Social||Transmission of RF data could cause interference||Remote operation difficulty, conflict with TV/radio stations||Improper selection of device transmission frequency||0||0||0||Observe proper FCC rules and regulations||Computer Engineer|
|R25||Environmental/Social||Remote log-in to unit may pose security threat||Sensitive data may restrict remote login||Malicious actor obtaining password/login information||0||0||0||Ensure strict security in regard to username/ password information||All|