LITHUANIAN CANSAT (CS), MISSILE AND UNMANNED AIR VEHICLES (UAV) CONTEST 2013 R U L E S I. GENERAL

Transcription

1 APPROVED by Vidmantas Tomkus Director Lithuanian Space Association January 28 th, 2013 LITHUANIAN CANSAT (CS), MISSILE AND UNMANNED AIR VEHICLES (UAV) CONTEST 2013 R U L E S I. GENERAL 1. Terms and definitions used in the Rules are defined in 3 Annex. 2. Cause and organisers of the Contest: 2.1. Lithuanian CanSat (CS), missile and Unmanned Air Vehicles (UAV) competition is held according to the Resolution No Concerning Approvement of the Means in Commemoration in 2013 of the Year of Steponas Darius and Stasys Girėnas Flight over Atlantic of Government of Republic of Lithuania on October 3 rd, The means to hold a contest of educational CanSat (CS), missiles and Unmanned Air Vehicles (UAV) devoted in commemoration of 80 th anniversary of S.Darius and S.Girėnas flight over Atlantic. Both contests will take part simultaneously Means holders (organisers) (1) Lithuanian Space Association, (2) Pakilimo takas UAB, (3) Space Science and Technology Institute; (4) Lithuanian Museum of Ethnocosmology. 3. Schedule of the Contest: 3.1. Selective stage: January 28, 2013: Competition rules announced; January 28 February 16, 2013: submission of commands applications; February 17 March 8, 2013: introductory workshops, screening talks with teams; Starting March 9: signing of participants agreements and delivery of equipment; 3.2. March 9, 2013 Test starts: manufacturing of CS and UAV, preparation of documentation; 3.3. Test starts. (detailed information in Test starts rulebook); 3.4. Test starts final stage: design improvement, preparation of presentation on project and its documentation; 3.5. Final stage. (detailed information in Final starts rulebook). 4. During starts and at the place Competition is governed by Competition Director, appointed by the organisers. His orders concerning safety and other organizational questions are compulsory to all contestants, spectators and other persons at the start s location. 5. Žilvinas Pukys (director, Liepiškės Technology Park) is appointed the Competition Director. 6. Competition date can be postponed or starts delayed due to bad meteorological conditions.

2 7. Contestants: 7.1. Team composition: Team consists of 2-4 members older than 14 as of February 10, 2013 and a team leader older than 18 as of February 10, All team members must be insured against accidents and present a copy of policy to organisers Minor team members must have written consent from parents (foster-parents) to take part in the Competition Teams from same community, taking part both in CS and UAV competitions, can be led by the same leader. Other members can take part in one team only Team leader is responsible for team members labour and health safety during all the period of project preparation and selective and final starts Persons from institutions and organisations engaged in commercial construction of aircrafts, missiles or satellites cannot be in a team or lead it Team leader signs and agreement with organizers concerning parties rights, duties, and responsibility Each team is responsible for provisioning their own: Transportation to the start place and back home Mobile computer and external USB storage device List of additional equipment will be published later Number of teams Test starts and final starts will accept up to 20 CS competition and up to 20 UAV competition teams Organizers can additionally invite up to 5 teams from abroad to the final starts. 8. Equipment for the contestants. Organizers will supply local teams with designing packages. 9. Requirements for competing CS and UAV are presented in 1 Annex. 10. Competition jury: Jury on the selective stage will be composed of organizer representatives. Its composition will be announced before the final starts To the jury on final stage will be invited representatives from: (1) Ministry of Economics, (2) Ministry of Education and Science, (3) Ministry of Transportation, (4) Air Force, (5) Agency for Science, Innovation and Technology, (6) A.Gustaitis aviation institute, VGTU, (7) Lithuanian Aeroclub, (8) Lithuanian Space Association, (9) Space Science and Technology Institute, (10) Oro navigacija VĮ. Jury can be appended with organizers representatives as well. Its final composition will be announced before the final starts. 11. This Rules and other related information will be published on the website Before test and final starts teams will be presented with the Rules of Conduct. Teams or contestants breaching those rules will be disqualified from the Contest. 2/9

3 II. EDUCATIONAL CANSAT MISSILE FLIGHT COMPETITION 13. Qualifications requirements for educational CS are presented in 1 Annex. Not complying CS will not start. 14. CS will be transported by an aircraft during test starts and by the missile during final starts. Missile will take 2 CS at once up to 1500 m high. Transporters in both cases will be provided by organizers. 15. Start sequence will be determined by a draw before starts. 16. Flight tasks are compulsory (C-PR) and additional (C-PA). Compulsory tasks are to be fulfilled during test and final starts. Additional tasks are to be fulfilled during final starts. 17. Team failed in fulfilling compulsory tasks or gaining less than minimum score is disqualified. 18. Compulsory CS tasks: C-PR-1. C-PR-2. C-PR-3. C-PR-4. C-PR Additional CS tasks: C-PA-1. C-PA-2. C-PA-3. C-PA-4. C-PA-5. C-PA-6. C-PA-7. C-PA-8. Project documentation. Teams must describe process of decision making, design and manufacturing of CS and present a short design description before the start. Guidelines are presented in 2 Annex. This task will only be assessed during the final starts. Soft landing. CS once separated from transport must deploy a parachute and land softly with maximum speed of 5 m/s at the moment of contact with the surface. Flight information record. CS must record flight altitude versus time. CS recovery. Team must find landed CS and bring it back. Processing of recorded information. After the flight recorded data must be moved to a computer and a graph of flight altitude dependence against time presented. Recording of additional flight data. Record additional data: coordinates, speed, direction, acceleration, rotation speed during flight. Move collected data to a computer and present their dependence against time graphs. Transfer of flight data. Transfer flight data (telemetry): altitude coordinates, speed, direction, acceleration, rotation speed via radio link. Record data into a computer. Eye view. Record with one or more cameras during the flight. After flight move data into a computer. Flight video transmission. Transmit the images from camera(s) during the flight. Store data on a computer. EggSat. Before start put a raw chicken egg into CS. Egg (with mass g) will be supplied by organizers. Egg must stay intact after flight. Mechanical design quality. Mechanical CS design and assembly quality is assessed. Quality of electronic part. Quality of assembly of electronic parts of CS is assessed. Final project presentation. Team prepares presentation (up to 10 slides) of work done and flight results gained and gives a short report on them. 20. Radio communication shall be in the 433 MHz range. Communication channels will be distributed to teams before starts. Team can use radio communication only during their flight. 21. Tasks will be assessed in the 0 to 10 points scale. 3/9

4 III. UNMANNED AIR VEHICLES (UAV) COMPETITION 22. Qualifications requirements for Unmanned Air Vehicles (UAV) are presented in 1 Annex. Not complying CS will not start. 23. Start sequence will be determined by a draw before starts. 24. UAV flight must be provided in heights between 20 m (66 ft.) and 1000 m (3281 ft.) above surface. Flight duration must be up to 15 minutes during test starts and up to 25 minutes during final starts. 25. Manual piloting of UAV is permitted only for take-off and landing. After the take-off the governing of UAV is passed (with permission of Flight Director) to autonomous system which guides it accordingly to pre-set parameters (coordinates). At the flight end pilot (with permission of Flight Director) takes over piloting and lands UAV. 26. Flight tasks are compulsory (B-PR) and additional (B-PA). Compulsory tasks are to be fulfilled during selective and final starts. Additional tasks are to be fulfilled during final starts. 27. Team failed in fulfilling compulsory tasks or gaining less than minimum score is disqualified. 28. Compulsory BPO tasks: B-PR-1. B-PR-2. B-PR-3. B-PR-4. B-PR-5. B-PR Additional UAV tasks: B-PA-1. B-PA-2. B-PA-3. Project documentation. Teams must describe process of decision making, design and manufacturing of UAV and present a short design description before the start. Guidelines are presented in 2 Annex. This task will only be assessed during the final starts. Horizontal target of known location. To find a target (horizontal, on surface) with known coordinates. Scan target s information. Vertical target of known location. To find a target (vertical, 1,5 2 m above surface) with known coordinates. Scan target s information. Horizontal target of known area. To find a horizontal target placed in defined area. Scan target s information and record its coordinates. Flight data recording. To record UAV flight data: time, altitude, direction, speed and coordinates. Flight data processing. After flight move data into a computer and present flight graphs and targets information. Immediate horizontal target. Transmit target coordinates to UAV in flight by radio. Find the target and scan its information. Transfer flight data (telemetry) by radio. Transmit data on UAV flight time, altitude, direction, speed and coordinates. Flight video. Transmit flight picture forwards and down or one of these. Record and save transmitted data. B-PA-4. Radio target. Find horizontal target marked with radio beacon (433 MHz range, 100 mw power) and scan visual information. Exact frequency will be presented later. B-PA-5. B-PA-6. Mechanical design quality. Mechanical UAV design and assembly quality is assessed. Quality of electronic part. Quality of assembly of electronic parts of UAV is assessed. 4/9

5 B-PA-7. Final project presentation. Team prepares presentation (up to 10 slides) of work done and flight results gained and gives a short report on them. 30. Targets: several white shapes 600 x 600 mm. 31. Radio communication shall be in the 433 MHz range. Communication channels will be distributed to teams before starts. Team can use radio communication only during their flight. 32. Tasks will be assessed in the 0 to 10 points scale. IV. ANNEXES 1 ANNEX. REQUIREMENTS FOR COMPETING CANSATS AND UAVS 1. Requirements for competing CanSats (CS): 1.1. CS must be manufactured by the team members Measurements of CS together with folded parachute must be: height 115 mm, diameter 70 mm. Mass with parachute 350±15 g In case of additional EggSat task, measurements of CS together with folded parachute must be: height 230 mm, diameter 70 mm. Mass together with parachute and egg 700±25 g Manufacturing costs of finished CS must not exceed 2000 LTL ( 579,24). Cost calculation must be presented to the jury together with project documentation. 2. Requirements for competing Unmanned Air Vehicles (UAV): 2.1. UAV must be manufactured by the team members Full mass of UAV must not exceed 5 kg Manufacturing costs of finished UAV must not exceed 3000 LTL ( 868,86). Cost calculation must be presented to the jury together with project documentation. 2 ANNEX. DOCUMENTATION GUIDELINES According to: NPR A NASA Systems Engineering Processes and Requirements w/change 1 (11/04/09). Preliminary Design Review Entrance Criteria 1. Successful completion of the SDR or MDR and responses made to all SDR or MDR RFAs and RIDs, or a timely closure plan exists for those remaining open. 2. A preliminary PDR agenda, success criteria, and charge to the board have been agreed to by the technical team, project manager, and review chair prior to the PDR. Success Criteria 1. The top-level requirements including mission success criteria, TPMs, and any sponsor-impose constraints are agreed upon, finalized, stated clearly, and consistent with the preliminary design. 2. The flow down of verifiable requirements is complete and proper or, if not, an ade- 5/9

6 3. PDR technical products listed below for both hardware and software system elements have been made available to the cognizant participants prior to the review: a) Updated baselined documentation, as required. b) Preliminary subsystem design specifications for each configuration item (hardware and software), with supporting trade-off analyses and data, as required. The preliminary software design specification should include a completed definition of the software architecture and a preliminary database design description, as applicable. c) Updated technology development maturity assessment plan. d) Updated risk assessment and mitigation. e) Updated cost and schedule data. f) Updated logistics documentation, as required. g) Applicable technical plans (e.g., technical performance measurement plan, contamination control plan, parts management plan, environments control plan, EMI/EMC control plan, payload-to-carrier integration plan, producibility / manufacturability program plan, reliability program plan, quality assurance plan). h) Applicable standards. i) Safety analyses and plans. j) Engineering drawing tree. k) Interface control documents. l) Verification/validation plan. m) Plans to respond to regulatory requirements (e.g., Environmental Impact Statement), as required. n) Disposal plan. o) Technical resource utilization estimates and margins. p) System-level safety analysis. q) Preliminary limited life items list (LLIL). quate plan exists for timely resolution of open items. Requirements are traceable to mission goals and objectives The preliminary design is expected to meet the requirements at an acceptable level of risk. 4. Definition of the technical interfaces is consistent with the overall technical maturity and provides an acceptable level of risk. 5. Adequate technical interfaces are consistent with the overall technical maturity and provide an acceptable level of risk. 6. Adequate technical margins exist with respect to TPMs. 7. Any required new technology has been developed to an adequate state of readiness, or back-up options exist and are supported to make them a viable alternative. 8. The project risks are understood and have been credibly assessed, and plans, a process, and resources exist to effectively manage them. 9. Safety and mission assurance (e.g., safety, reliability, maintainability, quality, and EEE parts) have been adequately addressed in preliminary designs and any applicable S&MA products (e.g., PRA, system safety analysis, and failure modes and effects analysis) have been approved. 10. The operational concept is technically sound, includes (where appropriate) human factors, and includes the flow down of requirements for its execution. Critical Design Review Entrance Criteria 1. Successful completion of the PDR and responses made to all PDR RFAs and RIDs, or a timely closure plan exists for those remaining open. 2. A preliminary CDR agenda, success criteria, and charge to the board have been agreed to by the technical team, project manager, and review chair prior to the CDR. 3. CDR technical work products listed below for both hardware and Success criteria 1. The detailed design is expected to meet the requirements with adequate margins at an acceptable level of risk. 2. Interface control documents are sufficiently matured to proceed with fabrication, assembly, integration, and test, and plans are in 6/9

7 software system elements have been made available to the cognizant participants prior to the review: a) updated baselined documents, as required; b) product build-to specifications for each hardware and software configuration item, along with supporting trade-off analyses and data; c) fabrication, assembly, integration, and test plans and procedures; d) technical data package (e.g., integrated schematics, spares provisioning list, interface control documents, engineering analyses, and specifications); e) operational limits and constraints; f) technical resource utilization estimates and margins; g) acceptance criteria; h) command and telemetry list; i) verification plan (including requirements and specification); j) validation plan; k) launch site operations plan; l) checkout and activation plan; m) disposal plan (including decommissioning or termination); n) updated Technology Development Maturity Assessment Plan; o) updated risk assessment and mitigation; p) updated reliability analyses and assessments; q) updated cost and schedule data; r) updated logistics documentation; s) software design document(s) (including interface design documents); t) updated LLIL; u) subsystem-level and preliminary operations safety analyses; v) systems and subsystem certification plans and requirements (as needed); and w) system safety analysis with associated verifications. place to manage any open items. 3. High confidence exists in the product baseline, and adequate documentation exists or will exist in a timely manner to allow proceeding with fabrication, assembly, integration, and test. 4. The product verification and product validation requirements and plans are complete. 5. The testing approach is comprehensive, and the planning for system assembly, integration, test, and launch site and mission operations is sufficient to progress into the next phase. 6. Adequate technical and programmatic margins and resources exist to complete the development within budget, schedule, and risk constraints. 7. Risks to mission success are understood and credibly assessed, and plans and resources exist to effectively manage them. 8. Safety and mission assurance (e.g., safety, reliability, maintainability, quality, and EEE parts) have been adequately addressed in system and operational designs, and any applicable S&MA products (e.g., PRA, system safety analysis and failure modes and effects analysis) have been approved. 3 ANNEX. TERMS AND DEFINITIONS 1. PDR Preliminary Design Review. The PDR demonstrates that the preliminary design meets all system requirements with acceptable risk and within the cost and schedule constraints and establishes the basis for proceeding with detailed design. It will show that the correct design options have been selected, interfaces have been identified, and verification methods have been described. 2. CDR Critical Design Review. The CDR demonstrates that the maturity of the design is appropriate to support proceeding with full-scale fabrication, assembly, integration, and test. CDR determines that the technical effort is on track to complete the flight and ground system 7/9

8 development and mission operations, meeting mission performance requirements within the identified cost and schedule constraints. 3. TPM Technical Performance Measure. TPM refer to key technical goals that needed to be met, where the technical goals were vital for the functioning of a system in its environment. 4. MDR Mission Definition Review. The MDR examines the proposed requirements, the mission architecture, and the flow down to all functional elements of the mission to ensure that the overall concept is complete, feasible, and consistent with available resources. 5. SDR System Definition Review. The SDR examines the proposed system architecture and design and the flow down to all functional elements of the system. 6. RFA Request for Action. 7. RID Review Item Discrepancy. 8. EEE electrical, elecronic and electromechanical. 9. S&MA Safety and Mission Assurance. 10. PRA Probabilistic Risk Assessment. 4 ANNEX. DESING PACKAGE One of possible design packages is shown lower: Item Approx. price, CS competitiotition UAV compe- LTL Dragonfly aircraft platform 105 Brushless motor 28 Speed controller (BEC) 35 Motor battery 105 Electronics battery 21 Servo (3 x) 72 Transmitter/receiver 155 Simulation cable 18 Battery charger 28 BEC for electronics 15 Full HD camera 340 Wire extensions 14 Autopilto APM MHz communication 300 Airspeed sensor 88 5 ANNEX. COMPETITION PLACE 8/9

9 Ignalina airfield Contest flight zone at Ignalina airfield (5,5 x 2,5 km), maximal height for UAV FT (2900 m), missiles FT ( m). the end 9/9