DaisyDriver.github.io/operation.html at master · DaisyDriver/DaisyDriver.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
<!DOCTYPE html>
<html lang="en">

<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">

    <link rel="stylesheet" type="text/css" href="css/default.css" />
    <link rel="stylesheet" type="text/css" href="css/responsive_sm.css" />
    <link rel="stylesheet" type="text/css" href="css/responsive_md.css" />

    <script src="js/utility.js"></script>

    <title>DaisyDriver - Graphical User Interface</title>
</head>

<body>

    <div class="main-container">
    <header>
        <img src="assets/daisydrivertext.png">
        <nav role="navigation">
            <div id="dd-imgcontainer">
                <img src="assets/reorder-three.svg" / id="dd-img">
            </div>
            <div id="dd-content">
                <a href="index.html">Home</a
                ><a href="assembly.html">Assembly</a
                ><a href="operation.html" class="current">Operating</a
                ><a href="serial.html">Serial Interface</a
                ><a href="gui.html">GUI</a
                ><a href="programming.html">Programming</a>
            </div>
        </nav>
    </header>

    <section>
        <h1 class="postheading">Operating Instructions</h1>

        <p>
            Before operating the DaisyDriver, it is important to familiarise
            yourself with the locations of the important features on the module.
            These are shown below, and numbered when mentioned in the text.
        </p>

        <img id="boardlayout" src="assets/board_CAD_numbered_features.png">

        <h3>List of Main Components Corresponding to Image Numbers:</h3>
        <ol>
            <li>USB micro B connector</li>
            <li>ISP 6 header</li>
            <li>Status LED</li>
            <li>SPI header</li>
            <li>Motor connector</li>
            <li>OUT chain connector</li>
            <li>IN chain connector</li>
            <li>Power connector</li>
        </ol>

        <hr>

        <p>
            DaisyDriver is composed of modular units, each of which can operate separately
            or as part of a chain, connected by cables. Chained operation is useful to extend
            the number of axes that can be operated simultaneously. <b>When operating modules in
            a chain, it is essential that the chain is not broken or added to whilst the chain
            is powered on, otherwise damage can result to the modules</b>.
        </p>

        <p>
            When adding motors to an existing setup, first site the modules at each group of
            motors. Once the modules are secured in place, they can be connected with cables.
            <b>It is important that modules are joined in order, i.e. cables always run from
            the OUT port (6) of one module to the IN port (7) of another.</b> Once the modules
            have been connected in a chain, the start of the chain (the module at one end of
            the chain which outputs to the remainder of the chain) can be connected to a
            computer using a USB A to Micro B cable (1). The power cable can be plugged into
            any of the units (8), though it is often convenient to connect it to the start of
            the chain.
        </p>

        <p>
            When power is applied, all the units in the chain should blink their status
            indicator LED (3) in the sequence Red-Green-Blue. Each unit will then momentarily
            turn its status indicator Red to indicate that it is waiting to be initialised,
            before blinking Green a number of times corresponding to the module's physical
            position in the chain, which is also its logical address.
        </p>

        <p>
            Once the chain has been powered on successfully, it is ready to be controlled.
        </p>

        <p>
            DaisyDriver can be controlled in one of two modes: <b>Serial Command</b> or <b>GUI</b>.
        </p>

        <p>
            <b>Serial Command</b> offers control of a chain of DaisyDrivers through a command
            line interface. More detail is available on the
            <a href="serial.html">Serial Command page.</a>
        </p>

        <p>
        The <b>DaisyDriver GUI</b> is a specialised graphic interface for using the DaisyDriver
        with a <a href="https://gitlab.com/openflexure/openflexure-microscope/">WaterScope (Openflexure
        Microscope)</a> for time lapse microscopy. More detail is available on the
        <a href="gui.html">GUI page.</a>
        </p>
    </section>
    </div>

    <footer>
        <p>Site code by Jonathan Louis Kaplan and Fergus Riche under MIT License unless otherwise stated.</p>
    </footer>

</body>

</html>