Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.arch.embedded > #27014

Camera I/F's

From Don Y <blockedofcourse@foo.invalid>
Newsgroups comp.arch.embedded
Subject Camera I/F's
Date 2017-07-08 11:05 -0700
Organization A noiseless patient Spider
Message-ID <ojr6lv$188$1@dont-email.me> (permalink)

Show all headers | View raw


I hacked together my "IP cameras" using some web cams for which I was
able to track down some FOSS i/f implementation documentation.  This
was OK for a proof of concept.  But, I now have to settle on "production"
hardware.

There seem to be a variety of i/f's for cameras:
- RS170 (requires hardware to digitize the signal; inflexible)
- parallel (video is digized, just needs to be captured at pixel rate)
- USB (digitized but packed in proprietary transport protocols over USB)
- CSI (digitized with specialty hardware required in host)
- IP (digitized but packed in protocols over IP)

The USB option is the easiest from the host's *hardware* point of view.
But, seems to limit the devices that could be supported as camera
vendors are loathe to publish details that only *their* driver implementers
should need.

RS170 is... "passe"

Parallel requires lots of signals to/from the host/camera.

CSI seems to be primarily supported on hosts intended to address the
mobile market.

As USB is essentially "free" (hardware-wise), adding support for it as
an *alternative* interface seems prudent.

Relying on CSI seems like it will restrict my choice of processor(s)
going forward (I'd like to standardize on *a* host platform and not
have to support a variety) -- though that's where the volume lies
(think camera in cell phones).  OTOH, it may make getting components
difficult (small fish, etc.)

IP seems to have more costs than USB with little/no gain.

Anyone been down this road who can share experiences?  Probably
only looking at 10K/yr...

Back to comp.arch.embedded | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Camera I/F's Don Y <blockedofcourse@foo.invalid> - 2017-07-08 11:05 -0700
  Re: Camera I/F's Dimiter_Popoff <dp@tgi-sci.com> - 2017-07-08 21:30 +0300
    Re: Camera I/F's Don Y <blockedofcourse@foo.invalid> - 2017-07-08 13:41 -0700
      Re: Camera I/F's Dimiter_Popoff <dp@tgi-sci.com> - 2017-07-09 01:53 +0300
        Re: Camera I/F's Don Y <blockedofcourse@foo.invalid> - 2017-07-09 09:21 -0700
  Re: Camera I/F's Joe Chisolm <jchisolm6@earthlink.net> - 2017-07-08 17:06 -0500
    Re: Camera I/F's Don Y <blockedofcourse@foo.invalid> - 2017-07-09 09:46 -0700
  Re: Camera I/F's Paul <paul@pcserviceselectronics.co.uk> - 2017-07-09 11:58 +0100
    Re: Camera I/F's Don Y <blockedofcourse@foo.invalid> - 2017-07-09 09:55 -0700
      Re: Camera I/F's Theo Markettos <theom+news@chiark.greenend.org.uk> - 2017-07-10 10:09 +0100
        Re: Camera I/F's Paul <paul@pcserviceselectronics.co.uk> - 2017-07-10 12:27 +0100
          Re: Camera I/F's Theo Markettos <theom+news@chiark.greenend.org.uk> - 2017-07-10 19:36 +0100
        Re: Camera I/F's Don Y <blockedofcourse@foo.invalid> - 2017-07-10 12:56 -0700

csiph-web