{"id":25,"date":"2015-09-16T18:41:14","date_gmt":"2015-09-16T22:41:14","guid":{"rendered":"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/?page_id=25"},"modified":"2016-04-01T12:53:13","modified_gmt":"2016-04-01T16:53:13","slug":"systems-design","status":"publish","type":"page","link":"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/systems-design\/","title":{"rendered":"Systems Design"},"content":{"rendered":"<p><strong>a. System requirements<\/strong><\/p>\n<p><strong>Functional Requirements<\/strong><\/p>\n<ul>\n<li>The system shall\n<ul>\n<li><span style=\"line-height: 1.5\">F1. Have two major components: quadcopter and moving docking platform<\/span><\/li>\n<li>F2. Detect and communicate when docking and undocking is not possible<\/li>\n<\/ul>\n<\/li>\n<li>The docking platform shall\n<ul>\n<li>MF1.1 Be moving until the quadcopter has been docked<\/li>\n<li>MF1.2 Withstand the weight of the quadcopter once it has been docked<\/li>\n<\/ul>\n<\/li>\n<li>The quadcopter shall &#8211;\n<ul>\n<li>F2.1 Localize itself w.r.t. the platform<\/li>\n<li>F2.2 (MOVED TO DESIREABLE)<\/li>\n<li>F2.3 Navigate to the platform<\/li>\n<li>F2.4 Dock to the platform without any collision<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><strong>Non Functional Requirements<\/strong><\/p>\n<ul>\n<li>The system shall:\n<ul>\n<li>MNF1.1 Function in a GPS degraded environment<\/li>\n<li><span style=\"line-height: 1.5\">MNF1.2 Provide a user interface with DOCK command and provide status<\/span><\/li>\n<\/ul>\n<\/li>\n<li>The quadcopter shall:\n<ul>\n<li>MF2.1 Have a payload capacity of &gt; 500g<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><strong>Performance Requirements<\/strong><\/p>\n<p>Mandatory Requirements<\/p>\n<ul>\n<li>The docking platform will-\n<ul>\n<li>MP1.1. Have 1 degree of freedom along Z-direction<\/li>\n<li>MP1.2. Oscillate in harmonic motion with dominant frequency &lt; 0.3Hz<\/li>\n<li>MP1.3. Have oscillations\u2019 span \u00b1200mm<\/li>\n<li>MP1.4. Have a locking mechanism which supports weight of 5kg<\/li>\n<\/ul>\n<\/li>\n<li>The quadcopter will \u2013\n<ul>\n<li>MP2.1. Localize w.r.t. platform within \u00b150cm<\/li>\n<li>MP2.2. Navigate to the platform within 10 minutes<\/li>\n<li>MP2.3. Dock to the platform autonomously and without colliding within 10 minutes<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Desirable Requirements<\/p>\n<ul>\n<li>The docking platform will-\n<ul>\n<li>DP1.1. Have 3 degrees of freedom along X, Y and Z-direction<\/li>\n<li>DP1.2. Have random movements in 3D space<\/li>\n<\/ul>\n<\/li>\n<li>The quadcopter will &#8211;\n<ul>\n<li>DP2.1. Localize w.r.t. platform within 30cm accuracy<\/li>\n<li>DP2.2. Navigate to the platform within 5 minutes<\/li>\n<li>DP2.3 Plan a path to the docking platform<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>b. Functional architecture<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p><a href=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/functional2.png\" rel=\"attachment wp-att-274\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-350 size-full\" src=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/functional2.png\" alt=\"\" width=\"1100\" height=\"450\" srcset=\"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/functional2.png 1100w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/functional2-300x123.png 300w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/functional2-768x314.png 768w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/functional2-1024x419.png 1024w\" sizes=\"auto, (max-width: 1100px) 100vw, 1100px\" \/><\/a><\/p>\n<p style=\"text-align: center\">Figure 1 &#8211; Functional Architecture of the Docking mechanism<\/p>\n<p>The system\u2019s input is the user\u2019s decision to dock and the output is the successful dock. The architecture is divided into two parts &#8211; the quadcopter and the platform. The quadcopter and platform are working together to plan the approach to the docking platform and dock at an opportune moment. There are three phases in the whole docking process. The platform and the quadcopter relay periodic updates to the user about their individual statuses and poses. (Figure 1)<\/p>\n<ul>\n<li>\u00a0Decision Phase<br \/>\nOnce the user requests the docking to initiate, the platform receives the request, analyzes its movement, and sends the request to dock to the quadcopter. If possible, the quadcopter and platform move on in the docking procedure. If docking isn\u2019t possible (maybe the quadcopter is too far away or the platform\u2019s movement is too erratic), then the user is notified aptly.\u00a0 During this phase, the quadcopter centers itself on the dock and hovers at a set distance from the lowest point of the platform&#8217;s motion.<\/li>\n<li>\u00a0Navigation Phase<br \/>\nIn the navigation phase, the dock&#8217;s Palantir subsystem informs the quadcopter of the time, velocity, and location it must reach to dock.<\/li>\n<li>Docking Phase<br \/>\nIn this phase, the quadcopter moves in the manner the dock has specified and makes contact with the docking face, activating the onboard electropermanent magnet and completing dock.\u00a0 This is done to minimize changes in velocity and dangers to the quadcopter.<\/li>\n<\/ul>\n<p style=\"text-align: center\"><a href=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/quadstates.jpg\" rel=\"attachment wp-att-374\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-374 aligncenter\" src=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/quadstates.jpg\" alt=\"quadstates\" width=\"487\" height=\"403\" srcset=\"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/quadstates.jpg 487w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/quadstates-300x248.jpg 300w\" sizes=\"auto, (max-width: 487px) 100vw, 487px\" \/><\/a>Figure 2 &#8211; Docking Activity Flow<\/p>\n<p>&nbsp;<\/p>\n<p><strong>c. Cyberphysical architecture<\/strong><\/p>\n<p>Our cyberphysical architecture can be broken up along its major subsystems and those subsystems&#8217; supporting subsystems.<\/p>\n<p><a href=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberoverview-1.png\" rel=\"attachment wp-att-416\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-416\" src=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberoverview-1.png\" alt=\"cyberoverview\" width=\"756\" height=\"605\" srcset=\"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberoverview-1.png 756w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberoverview-1-300x240.png 300w\" sizes=\"auto, (max-width: 756px) 100vw, 756px\" \/><\/a><\/p>\n<p style=\"text-align: center\">Figure 3 &#8211; Cyberphysical Architecture Overview<\/p>\n<p style=\"text-align: left\">The dock and quadcopter have their own cyberphyiscal architecture, broken up into power, data, and code.<\/p>\n<p style=\"text-align: left\">\u00a0\u00a0\u00a0 <a href=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquadcode2.png\" rel=\"attachment wp-att-355\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-355\" src=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquadcode2.png\" alt=\"cyberquadcode2\" width=\"200\" height=\"149\" srcset=\"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquadcode2.png 835w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquadcode2-300x223.png 300w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquadcode2-768x571.png 768w\" sizes=\"auto, (max-width: 200px) 100vw, 200px\" \/><\/a> <a href=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquaddata2.jpg\" rel=\"attachment wp-att-357\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-357\" src=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquaddata2.jpg\" alt=\"cyberquaddata2\" width=\"200\" height=\"151\" srcset=\"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquaddata2.jpg 835w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquaddata2-300x227.jpg 300w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquaddata2-768x580.jpg 768w\" sizes=\"auto, (max-width: 200px) 100vw, 200px\" \/><\/a> <a href=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquadpower2.png\" rel=\"attachment wp-att-358\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-358\" src=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquadpower2.png\" alt=\"cyberquadpower2\" width=\"200\" height=\"151\" srcset=\"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquadpower2.png 835w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquadpower2-300x227.png 300w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/cyberquadpower2-768x580.png 768w\" sizes=\"auto, (max-width: 200px) 100vw, 200px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: center\">Figures 4-6 &#8211; Quadcopter\u00a0Cyberphysical Architecture : Code, Data, Power<\/p>\n<p><a href=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/functional2-1.png\" rel=\"attachment wp-att-354\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-354\" src=\"http:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/functional2-1.png\" alt=\"functional2\" width=\"1023\" height=\"598\" srcset=\"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/functional2-1.png 1023w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/functional2-1-300x175.png 300w, https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-content\/uploads\/sites\/6\/2015\/09\/functional2-1-768x449.png 768w\" sizes=\"auto, (max-width: 1023px) 100vw, 1023px\" \/><\/a><\/p>\n<p style=\"text-align: center\">Figures 7 &#8211; Dock\u00a0Cyberphysical Architecture<\/p>\n<p><strong>d. System design description\/depiction(s)<\/strong><\/p>\n<p>The architecture, shown in Figure 2\u00a0is divided into three abstractions for the docking platform and the quadcopter. The software abstraction encompasses the algorithms used to accomplish the functions depicted in the functional architecture. The electronic abstraction shows the different electrical equipment and their connection to run the algorithms from the software abstraction. The lines from the software abstraction show which processor runs the processes. Lastly, the mechanical abstraction holds the mechanisms that allow the software algorithms to manifest into the physical realm. The most substantial mechanical feature is the docking mechanism that will lock the quadcopter onto the platform.<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>a. System requirements Functional Requirements The system shall F1. Have two major components: quadcopter and moving docking platform F2. Detect and communicate when docking and undocking is not possible The docking platform shall MF1.1 Be moving until the quadcopter has been docked MF1.2 Withstand the weight of the quadcopter once it has been docked The<br \/><a class=\"moretag\" href=\"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/systems-design\/\">+ Read More<\/a><\/p>\n","protected":false},"author":31,"featured_media":0,"parent":0,"menu_order":2,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-25","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-json\/wp\/v2\/pages\/25","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-json\/wp\/v2\/users\/31"}],"replies":[{"embeddable":true,"href":"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-json\/wp\/v2\/comments?post=25"}],"version-history":[{"count":34,"href":"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-json\/wp\/v2\/pages\/25\/revisions"}],"predecessor-version":[{"id":417,"href":"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-json\/wp\/v2\/pages\/25\/revisions\/417"}],"wp:attachment":[{"href":"https:\/\/mrsdprojects.ri.cmu.edu\/2015teame\/wp-json\/wp\/v2\/media?parent=25"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}