Electrical output

From OLPC
Revision as of 17:12, 11 August 2007 by Homunq (talk | contribs) (Initial page to unite ideas from wiki and developer list)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Just as the Measure activity allows direct input for sensors, it is useful to have a direct electrical output for robotics, LED's, and other purposes.

Possibilities:

  • Audio port: This would theoretically support a highly gradated, relatively precise, d/a output, at low currents. No word on whether this works.
  • You can blink LEDs by connecting them to modem control signals. Advantages: the relevant connector (phone cord) is widely available and cheap (or even scavengable)
  • USB to serial adapters are readily available. They work fine for simple things, but aren't great for microsecond level timings. A quick search finds prices under $20.
  • ntp uses one of the modem signals to catch the PPS (pulse per second) timing. Many kernels have a hack to grab the time when a modem signal changes state. USB adds a lot of jitter. (this is actually input, not output.)
  • USB to printer port adapters are also available. I've never played with one. Prices are under $40. Advantages: number of parallel outputs (how many?)
  • OLCP just had a summer intern, Arjun Sarwal, who worked on the Measure/oscilliscope activity. We also talked about an OLPC digital gadget prototyping dongle with a USB-equipped microcontroller like those available from, for example, Atmel. Those chips cost a dollar or two and Arjun can get all the other parts really inexpensively in India where he lives.