<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   <meta name="generator" content="Movable Type 3.2" />

   <link rel="stylesheet" href="styles-site.css" type="text/css" />
   <link rel="alternate" type="application/atom+xml" title="Atom" href="atom.xml" />
   <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="index.xml" />

   <title>Double Down: Project Proposal - Main Control</title>

   <link rel="start" href="" title="Home" />
   <link rel="prev" href="http://doublecounter.com/doubledown/2006_02_card_reading.html" title="Project Proposal - Card Reading" />
   <link rel="next" href="http://doublecounter.com/doubledown/2006_03_motor_steady_check.html" title="Motor Steady Check" />

   <!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
         xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description
    rdf:about="http://doublecounter.com/doubledown/2006_02_main_control.html"
    trackback:ping="http://thespork.net/mt-tb.cgi/1056"
    dc:title="Project Proposal - Main Control"
    dc:identifier="http://doublecounter.com/doubledown/2006_02_main_control.html"
    dc:subject=""
    dc:description="This entry contains the continuation of our project propsal, found here, and continuing from here. The following is taken from our project proposal: 3.3 Main Control The main control will be a module in itself within Simulink, but have no..."
    dc:creator="John"
    dc:date="2006-02-10T01:19:15-06:00" />
</rdf:RDF>
-->


   

   <script type="text/javascript" src="http://doublecounter.com/doubledown/mt-site.js"></script>
</head>
<body class="layout-one-column" onload="individualArchivesOnLoad(commenter_name)">
   <div id="container">
      <div id="container-inner" class="pkg">

         <div id="banner">
            <div id="banner-inner" class="pkg">
               <h1 id="banner-header"><a href="index.html" accesskey="1">Double Down</a></h1>
               <h2 id="banner-description">An automated card-dealer</h2>
            </div>
         </div>

         <div id="pagebody">
            <div id="pagebody-inner" class="pkg">
               <div id="alpha">
                  <div id="alpha-inner" class="pkg">

                     <p class="content-nav">
                        <a href="http://doublecounter.com/doubledown/2006_02_card_reading.html">&laquo; Project Proposal - Card Reading</a> |
                        <a href="index.html">Main</a>
                        | <a href="http://doublecounter.com/doubledown/2006_03_motor_steady_check.html">Motor Steady Check &raquo;</a>
                     </p>

                     <a id="a001056"></a>
                     <div class="entry" id="entry-1056">
                        <h3 class="entry-header">Project Proposal - Main Control</h3>
                        <div class="entry-content">
                           <div class="entry-body">
                              <p>This entry contains the continuation of our project propsal, found <a href="http://doublecounter.com/doubledown/2006/02/introduction.html">here</a>, and continuing from <a href="http://doublecounter.com/doubledown/2006/02/card_reading.html">here</a>.</p>

<p>The following is taken from our project proposal:</p>

<blockquote><b>3.3 Main Control</b>

<p>The main control will be a module in itself within Simulink, but have no physical representation other than the xPC Target and/or Host.  Its functionality will be transparent to all other layers, and it will primarily communicate with the dealer-cart because the main control believes this to be the only thing it can control.  It will also communicate with a user interface, however that is implemented (either hard coded or through actual buttons).  Therefore, it will send whatever signals necessary for not only dealing whatever game it believes it is playing but for dealing cards to play the game.</p>

<p>For example, if playing blackjack, it would first deal the game: one card up and one down to the dealer, and two cards up to the user.  Then it starts playing, by waiting for the user to “hit” and then dealing the appropriate cards until they “stay.”  If the user “busts” the game is over, if not, it will hit until it either beats the player or busts.  The main control would have to send to the dealing-cart only the necessary cards to deal for this interaction, thus keeping the game completely transparent to the dealing-cart.</blockquote></p>
                           </div>
                           <div id="more" class="entry-more">
                              
                           </div>
                        </div>
                        <p class="entry-footer">
                           <span class="post-footers">Posted by John Hanauer on February 10, 2006 01:19 AM</span> <span class="separator">|</span> <a class="permalink" href="http://doublecounter.com/doubledown/2006_02_main_control.html">Permalink</a>
                        </p>
                     </div>

                     

                     
                  </div>
               </div>
            </div>
         </div>
      </div>
   </div>
</body>
</html>

