| 1 |
From [email protected] Tue Jan 13 03:19:47 1998 |
| 2 |
Received: from aleve.media.mit.edu by hub.media.mit.edu; (5.65v3.2/1.1/06Jun95-8.2MPM) |
| 3 |
id AA08834; Tue, 13 Jan 1998 03:19:47 -0500 |
| 4 |
Received: from splat.securepipe.com (splat.securepipe.com [169.207.51.74]) |
| 5 |
by aleve.media.mit.edu (8.8.7/ML970927) with SMTP id CAA00703 |
| 6 |
for <[email protected]>; Tue, 13 Jan 1998 02:15:36 -0500 (EST) |
| 7 |
Message-Id: <[email protected]> |
| 8 |
Received: (qmail 7615 invoked from network); 13 Jan 1998 07:23:07 -0000 |
| 9 |
Received: from jack.securepipe.com ([email protected]) |
| 10 |
by splat.securepipe.com with SMTP; 13 Jan 1998 07:23:07 -0000 |
| 11 |
X-Mailer: exmh version 2.0zeta 7/24/97 |
| 12 |
From: Joshua Heling <[email protected]> |
| 13 |
To: [email protected] |
| 14 |
Subject: questions re: unix version of IC |
| 15 |
Reply-To: Joshua Heling <[email protected]> |
| 16 |
Mime-Version: 1.0 |
| 17 |
Content-Type: text/plain; charset=us-ascii |
| 18 |
Date: Tue, 13 Jan 1998 01:23:12 -0600 |
| 19 |
Sender: [email protected] |
| 20 |
|
| 21 |
Hi - |
| 22 |
|
| 23 |
I'm a handy-board/ic newbie, so please excuse this question if it's answers |
| 24 |
seem obvious. After two weeks of writing code in DOS/Windows (yuck), I |
| 25 |
downloaded the ic-2.860beta source code, which compiled without significant |
| 26 |
trouble in linux (redhat 5). The version is, of course, a bit different from |
| 27 |
that which came with the handy-board (from Gleason Rsch, was version 2.851). |
| 28 |
|
| 29 |
My question is, can I just copy the library files that came from Gleason Rsch. |
| 30 |
into the lib directory on the unix ic installation (it seems that I can, I |
| 31 |
just want to be sure)? Are there any other issues I should be aware of |
| 32 |
(w.r.t. the beta, or using ic from unix, end-of-line conventions on library |
| 33 |
files, etc.). I'm not particularly concerned with being able to download the |
| 34 |
pcode in unix - I do have DOS easily available... |
| 35 |
|
| 36 |
BTW, thanks to all that have contributed to this really neat project - this is |
| 37 |
my first exposure to robotics, and it's been great fun so far. |
| 38 |
|
| 39 |
----- Begin Included Message ----- |
| 40 |
|
| 41 |
From [email protected] Thu May 1 09:58:06 1997 |
| 42 |
X-Authentication-Warning: ns1.qsl.net: majordom set sender to [email protected] using -f |
| 43 |
From: "Guy Hamblen" <[email protected]> |
| 44 |
To: "Laser" <[email protected]> |
| 45 |
Subject: [LASER] Which Circuit for OPT210? |
| 46 |
Date: Thu, 1 May 1997 12:53:29 -0400 |
| 47 |
X-Msmail-Priority: Normal |
| 48 |
X-Priority: 3 |
| 49 |
X-Mailer: Microsoft Internet Mail 4.70.1155 |
| 50 |
Mime-Version: 1.0 |
| 51 |
Content-Type: text/plain; charset=ISO-8859-1 |
| 52 |
Content-Transfer-Encoding: 7bit |
| 53 |
Sender: [email protected] |
| 54 |
Reply-To: "Guy Hamblen" <[email protected]> |
| 55 |
Content-Length: 1037 |
| 56 |
|
| 57 |
Thanks everyone for sourcing information on this device. I've got several |
| 58 |
in hand, feedback resistors are in the mail. Now can I get existing |
| 59 |
OPT1210 user experience re: the following questions: |
| 60 |
|
| 61 |
1) I assume (dangerous I know...) that the easiest circuit (per the |
| 62 |
Burr-Brown App Notes) is the Fig. 3 "Single Power Supply Operation"? |
| 63 |
2) Is 12v operation recommended? |
| 64 |
3) If 12v operation, did you use a 5.6v zener or lower value? |
| 65 |
4) Did you use electrolytics to bypass to ground pins 1 & 8? |
| 66 |
5) Did you build this circuit in a shielded box? |
| 67 |
6) Does the on-board opamp provide sufficient output to drive a set of |
| 68 |
headphones or did you add another opamp gain circuit? If so what low noise |
| 69 |
device? Any highpass filter circuits? Is there any need for a bandpass |
| 70 |
filter circuit to get rid of audio highs? |
| 71 |
|
| 72 |
I am using a 3" PVC with a focusing lens (f/4") - - how did you |
| 73 |
mechanically place the OPT210 so the focused light source falls on the |
| 74 |
photodiode? My approach would be trial-versus-error.... |
| 75 |
|
| 76 |
Thanks in advance....Guy N7UN/2 |
| 77 |
|
| 78 |
----- End Included Message ----- |
| 79 |
|
| 80 |
|
| 81 |
- Joshua |
| 82 |
|
| 83 |
-------- |
| 84 |
Joshua Heling [email protected] |
| 85 |
SecurePipe Communications, Inc. |
| 86 |
|
| 87 |
|
| 88 |
|
| 89 |
From [email protected] Tue Jan 13 10:41:57 1998 |
| 90 |
Received: from aleve.media.mit.edu by hub.media.mit.edu; (5.65v3.2/1.1/06Jun95-8.2MPM) |
| 91 |
id AA21129; Tue, 13 Jan 1998 10:41:57 -0500 |
| 92 |
Received: from ml.media.mit.edu (ml.media.mit.edu [18.85.13.107]) |
| 93 |
by aleve.media.mit.edu (8.8.7/ML970927) with ESMTP id JAA22423 |
| 94 |
for <[email protected]>; Tue, 13 Jan 1998 09:10:43 -0500 (EST) |
| 95 |
Received: from localhost (localhost [127.0.0.1]) |
| 96 |
by ml.media.mit.edu (8.8.7/8.8.7) with SMTP id JAA26699; |
| 97 |
Tue, 13 Jan 1998 09:10:37 -0500 (EST) |
| 98 |
Message-Id: <[email protected]> |
| 99 |
X-Authentication-Warning: ml.media.mit.edu: localhost [127.0.0.1] didn't use HELO protocol |
| 100 |
To: Joshua Heling <[email protected]> |
| 101 |
Cc: [email protected] |
| 102 |
Subject: Re: questions re: unix version of IC |
| 103 |
In-Reply-To: Your message of "Tue, 13 Jan 98 01:23:12 CST." |
| 104 |
<[email protected]> |
| 105 |
Date: Tue, 13 Jan 98 09:10:37 -0500 |
| 106 |
From: "Fred G. Martin" <[email protected]> |
| 107 |
X-Mts: smtp |
| 108 |
|
| 109 |
Joshua - |
| 110 |
|
| 111 |
There should be no problems using the Gleason Research libraries (or |
| 112 |
any of the libraries that are on the web site). There are no differences |
| 113 |
between version 2.851 and 2.860 from the point of view of the |
| 114 |
libraries. |
| 115 |
|
| 116 |
There is a pre-compiled version for Linux. See |
| 117 |
|
| 118 |
ftp://cher.media.mit.edu/pub/projects/interactive-c/unix/ |
| 119 |
|
| 120 |
Fred |
| 121 |
|
| 122 |
|
| 123 |
In your message you said: |
| 124 |
> Hi - |
| 125 |
> |
| 126 |
> I'm a handy-board/ic newbie, so please excuse this question if it's answers |
| 127 |
> seem obvious. After two weeks of writing code in DOS/Windows (yuck), I |
| 128 |
> downloaded the ic-2.860beta source code, which compiled without significant |
| 129 |
> trouble in linux (redhat 5). The version is, of course, a bit different from |
| 130 |
|
| 131 |
> that which came with the handy-board (from Gleason Rsch, was version 2.851). |
| 132 |
> |
| 133 |
> My question is, can I just copy the library files that came from Gleason Rsch |
| 134 |
. |
| 135 |
> into the lib directory on the unix ic installation (it seems that I can, I |
| 136 |
> just want to be sure)? Are there any other issues I should be aware of |
| 137 |
> (w.r.t. the beta, or using ic from unix, end-of-line conventions on library |
| 138 |
> files, etc.). I'm not particularly concerned with being able to download the |
| 139 |
|
| 140 |
> pcode in unix - I do have DOS easily available... |
| 141 |
> |
| 142 |
> BTW, thanks to all that have contributed to this really neat project - this i |
| 143 |
s |
| 144 |
> my first exposure to robotics, and it's been great fun so far. |
| 145 |
> |
| 146 |
> |
| 147 |
> - Joshua |
| 148 |
> |
| 149 |
> -------- |
| 150 |
> Joshua Heling [email protected] |
| 151 |
> SecurePipe Communications, Inc. |
| 152 |
> |
| 153 |
> |
| 154 |
> |
| 155 |
|
| 156 |
From [email protected] Thu Jan 1 05:56:53 1998 |
| 157 |
Received: from aleve.media.mit.edu by hub.media.mit.edu; (5.65v3.2/1.1/06Jun95-8.2MPM) |
| 158 |
id AA29720; Thu, 1 Jan 1998 05:56:53 -0500 |
| 159 |
Received: from kott.my.domain ([email protected] [198.110.144.127]) |
| 160 |
by aleve.media.mit.edu (8.8.7/ML970927) with ESMTP id FAA31795 |
| 161 |
for <[email protected]>; Thu, 1 Jan 1998 05:06:14 -0500 (EST) |
| 162 |
Received: from kott.my.domain ([email protected] [192.168.0.1]) |
| 163 |
by kott.my.domain (8.8.8/8.8.5) with SMTP id FAA01072 |
| 164 |
for <[email protected]>; Thu, 1 Jan 1998 05:06:33 -0500 (EST) |
| 165 |
Date: Thu, 1 Jan 1998 05:06:32 -0500 (EST) |
| 166 |
From: David Kott <[email protected]> |
| 167 |
Sender: [email protected] |
| 168 |
To: [email protected] |
| 169 |
Subject: Re: Digital outputs. |
| 170 |
In-Reply-To: <[email protected]> |
| 171 |
Message-Id: <[email protected]> |
| 172 |
Mime-Version: 1.0 |
| 173 |
Content-Type: TEXT/PLAIN; charset=US-ASCII |
| 174 |
|
| 175 |
On Wed, 31 Dec 1997, Tom Brusehaver wrote: |
| 176 |
|
| 177 |
<snip> |
| 178 |
> |
| 179 |
> G> Wich are the options to have 3 digital outputs in the handyboard? |
| 180 |
> G> No matter if i have to do little modifications to the Hardware. I |
| 181 |
> G> already know how to conect the keypad if you can tell me how |
| 182 |
> G> obtain 3 outputs.. :) |
| 183 |
> |
| 184 |
> |
| 185 |
> The SPI port is sitting there. I think you can get at 3 outputs from |
| 186 |
> those pins (SD/RD/CLK). |
| 187 |
> |
| 188 |
</snip> |
| 189 |
|
| 190 |
yet ANOTHER idea, if you are suitably masochistic, is to use the SPI port |
| 191 |
for a much more extensible I/O system. As you know, SPI uses 4 basic |
| 192 |
control signals, MOSI, MISO, CLK and SS... Ok, what we used to do in |
| 193 |
Embedded Controllers class is hook up a Serial In/Parallel Out |
| 194 |
(hereforward referred to as a SIPO) shift register. You must have at |
| 195 |
least ONE output available, so, this pretty much eliminates a L293 or, if |
| 196 |
you are bold enough, obtain additional outputs using a '138 as outlined in |
| 197 |
the HandyBoard FAQ. A SIPO you might use is the 8 bit 74164. |
| 198 |
|
| 199 |
Hook the DATA IN on the SIPO to the MOSI pin on the SPI. Hook the |
| 200 |
SPI's CLK output to the SIPO's clock pin. Use a transparent latch to |
| 201 |
update and hold the data on the outputs of the SIPO and update it with the |
| 202 |
one output pin, perhaps a 74373. |
| 203 |
|
| 204 |
To update the new 8 bits of data appearing at your latch's output, you load |
| 205 |
the SPI's data register with the byte value that you want to have across |
| 206 |
your new outputs. This data will be shifted out during the next 8 E-clock |
| 207 |
cycles. After the SPI's data register is empty indicating that the SIPO |
| 208 |
has the output byte on it's parallel outputs, pulse the single control |
| 209 |
output to update the latch's outputs. |
| 210 |
|
| 211 |
With this arrangement, you could, in theory, have many, many SIPO shift |
| 212 |
register/Latch pairs; the Serial Data In of the next stage connected to |
| 213 |
the last Parallel Output on the previous adjacent stage. |
| 214 |
|
| 215 |
One would just have to make sure that you coordinated the number of stages |
| 216 |
with the number of bytes outshifted by the SPI data register (naturally). |
| 217 |
The downside to this arrangement is the time it takes to update a digital |
| 218 |
output. The entire train (8 bits, 16 bits, 24 bits... more?) Need to be |
| 219 |
loaded and shifted out to change just ONE output. The upside is, the data |
| 220 |
will shift at 2 Mhz, which makes for a (250 ns * [8+2] ) 2.5 ms update |
| 221 |
time. Not suitable for time critical applications, (PWM, Communication) |
| 222 |
but not bad for bulk outputs. |
| 223 |
|
| 224 |
I don't think I have explained my little circuit here very well.. perhaps |
| 225 |
an ASCII graphic? |
| 226 |
|
| 227 |
Output originally going to an L293D |
| 228 |
+---------------------------------------+ |
| 229 |
|Or added via a '138 from the | |
| 230 |
|expansion buss. | |
| 231 |
| +--+----+ |
| 232 |
+----+---------+ +---------+ | LE | |
| 233 |
| | SPI CLK |'164 PO0|----| '373 |---- |
| 234 |
| +-----------+ CP PO1|----| |---- |
| 235 |
| 68HC11 | SPI MOSI | PO2|----| |---- |
| 236 |
| +-----------+ Data PO3|----| |---- New |
| 237 |
| | | PO4|----| |---- Digital |
| 238 |
+--------------+ | PO5|----| |---- Outputs |
| 239 |
| PO6|----| |---- |
| 240 |
| PO7|----| |---- |
| 241 |
+---------+ +-------+ |
| 242 |
|
| 243 |
|
| 244 |
Where: |
| 245 |
PO# is a "Parallel Output" on a SIPO |
| 246 |
Data is the "Serial Data Input" on a SIPO |
| 247 |
CP is the SIPO's clock |
| 248 |
|
| 249 |
|
| 250 |
-d |
| 251 |
|
| 252 |
|
| 253 |
Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to |
| 254 |
an 8 bit operating system originally coded for a 4 bit microprocessor, |
| 255 |
written by a 2 bit company that can't stand 1 bit of competition. -UGU |
| 256 |
|
| 257 |
|
| 258 |
|
| 259 |
From [email protected] Thu Jan 1 10:20:57 1998 |
| 260 |
Received: from aleve.media.mit.edu by hub.media.mit.edu; (5.65v3.2/1.1/06Jun95-8.2MPM) |
| 261 |
id AA28944; Thu, 1 Jan 1998 10:20:57 -0500 |
| 262 |
Received: from ml.media.mit.edu (ml.media.mit.edu [18.85.13.107]) |
| 263 |
by aleve.media.mit.edu (8.8.7/ML970927) with ESMTP id JAA23720 |
| 264 |
for <[email protected]>; Thu, 1 Jan 1998 09:41:01 -0500 (EST) |
| 265 |
Received: (from fredm@localhost) |
| 266 |
by ml.media.mit.edu (8.8.7/8.8.7) id JAA32741 |
| 267 |
for handyboard; Thu, 1 Jan 1998 09:41:01 -0500 (EST) |
| 268 |
From: Fred G Martin <[email protected]> |
| 269 |
Message-Id: <[email protected]> |
| 270 |
To: [email protected] |
| 271 |
Subject: Re: Digital outputs. |
| 272 |
|
| 273 |
Thanks David for a nice explanation of how to add I/O using shift |
| 274 |
registers. |
| 275 |
|
| 276 |
Let us not all forget that the HB does have two uncommitted digital |
| 277 |
output ASIDE from the four SPI pins: PA7 (a bidirectional pin which |
| 278 |
is marked as digital input #9) and PA5 (a timer output pin which is |
| 279 |
marked as TO3 on the expansion header). |
| 280 |
|
| 281 |
It would seem silly to disconnect a motor driver signal when these |
| 282 |
two signals are available. |
| 283 |
|
| 284 |
Fred |
| 285 |
|