<!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 - Card Reading</title>

   <link rel="start" href="" title="Home" />
   <link rel="prev" href="http://doublecounter.com/doubledown/2006_02_dealing_an_entire_game.html" title="Project Proposal - Dealing an Entire Game" />
   <link rel="next" href="http://doublecounter.com/doubledown/2006_02_main_control.html" title="Project Proposal - Main Control" />

   <!--
<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_card_reading.html"
    trackback:ping="http://thespork.net/mt-tb.cgi/1055"
    dc:title="Project Proposal - Card Reading"
    dc:identifier="http://doublecounter.com/doubledown/2006_02_card_reading.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.2 Card Reading The card reading layer will be necessary for determining what cards are dealt what..."
    dc:creator="John"
    dc:date="2006-02-10T01:17:56-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_dealing_an_entire_game.html">&laquo; Project Proposal - Dealing an Entire Game</a> |
                        <a href="index.html">Main</a>
                        | <a href="http://doublecounter.com/doubledown/2006_02_main_control.html">Project Proposal - Main Control &raquo;</a>
                     </p>

                     <a id="a001055"></a>
                     <div class="entry" id="entry-1055">
                        <h3 class="entry-header">Project Proposal - Card Reading</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/dealing_an_entire_game.html">here</a>.</p>

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

<blockquote><b>3.2 Card Reading</b>

<p>The card reading layer will be necessary for determining what cards are dealt what players.  This has many uses, but is primarily necessary if our dealer will know how to play blackjack.  This module will only talk with the single-card-dealer to minimize communication points and so that the single-card-dealer can trigger its flip process.  Once the card-reader has determined what the present card is, it will pass a six-bit value to the single-card-dealer.  The single-card-dealer can then flip the card and then pass the six-bit value back to the dealing-cart.  The dealing cart can then pass this back to the control to signalize that the entire process has finished dealing to the appropriate position.  Depending on the game being played or the card being dealt, the control can decide whether to keep or trash the card-value that was read.</p>

<p>The actual card reading computation will depend on if we implement barcode-reading using one sensor per player (2 total), or two sensors per player (4-total).  The first option is to use real barcode printers/readers.  This might be easiest if the commercial barcode readers can simply read off 1-52 depending on the card and pass that as a binary signal.  The next option is to have two photo-reflective sensors that read two tracks of black marks.  One track for clock cycle, the other track for actual information.  Using one photo-reflective sensor either means placing the sensor inbetween tracks to read variable amounts of light and convert that to information, or to simply feedback card position from the dealing-belt and transform the time information to position information.  This might make things more complicated not only in computation, but in removing some of the transparency between the card-reading layer and the card-dealing layer.</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:17 AM</span> <span class="separator">|</span> <a class="permalink" href="http://doublecounter.com/doubledown/2006_02_card_reading.html">Permalink</a>
                        </p>
                     </div>

                                          <div class="trackbacks">
                        <h3 id="trackback" class="trackbacks-header">TrackBack</h3>
                        <div id="trackbacks-info">
                           
                        </div>
                        <div class="trackbacks-content">
                                                                                 <p>Listed below are links to weblogs that reference <a href="http://doublecounter.com/doubledown/2006_02_card_reading.html" rel="nofollow">Project Proposal - Card Reading</a>:</p>
                           
                           <a id="p260"></a>
                           <div class="trackback" id="ping-260">
                              <div class="trackback-content">
                                 <p>
                                    &raquo; <a href="http://doublecounter.com/doubledown/2006/02/main_control.html" rel="nofollow nofollow">Main Control</a> from Double Down<br />
                                    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... <a href="http://doublecounter.com/doubledown/2006/02/main_control.html" rel="nofollow nofollow">[Read More]</a>
                                 </p>
                              </div>
                              <p class="trackback-footer">
                                 Tracked on <a href="#ping-260" rel="nofollow">February 10, 2006 01:10 PM</a>
                              </p>
                           </div>
                           
                        </div>
                     </div>
                     

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

