                                                                                                                                                                                                                                                                
Received-SPF: pass (google.com: domain of playas...@gmail.com designates 209.85.217.180 as permitted sender) client-ip=209.85.217.180;
MIME-Version: 1.0
In-Reply-To: <d6a034f3-ac8f-419c-8d52-c9ae6a91c791@googlegroups.com>
References: <d6a034f3-ac8f-419c-8d52-c9ae6a91c791@googlegroups.com>
Date: Thu, 4 Oct 2012 19:45:25 -0400
Message-ID: <CAEVTcgXfz7UAY9c3=6RzU83dqP3Jh0vptUcFrsFUmZc=vC+...@mail.gmail.com>
Subject: Re: [NYCR:Microcontrollers] zigbee + UART jpeg cam
From: Glen Duncan <playas...@gmail.com>
To: nycresistormicrocontrollers@googlegroups.com
Content-Type: multipart/alternative; boundary=f46d040167f36a4a2704cb445953

--f46d040167f36a4a2704cb445953
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Oct 4, 2012 at 4:59 PM, Michael Cooper <mbcoope...@gmail.com> wrote:

> Greetings Resistors,
>
> I am scoping out a small project and I am in need of a reality-check on
> basic framework.  The project is a remote camera transmitting over zigbee
> to a pc-based receiver.  After some research, I think this is what I need:
>
> 2 x zigbee units, one wired to the cam, 1 wired to the PC
> 1 x camera with UART interface
>
> Steps:
>
> - wire up the cam to the zigbee -- this is simply a matter of connecting
> the UART out of the cam into the UART input on the zigbee, correct?
>
> - Connect the other zigbee to USB port on the pc (easy)
>
> - make the zigbees talk to each other (per zigbee unit documentation)
>
> - use Processing's "Serial" library to parse the info from the camera
> coming based on the camera's specs for the data structure for its visual
> frame output (the camera I am looking at outputs jpeg-encoded frames)
>
> I would have to write a custom parsing script for this in Processing,
> correct?
>
> - theoretically, the result from that should be an image in jpeg format,
> so at that point I am thinking that I could output the parsed data from
> Processing as a file, slap a "jpg" extension on it, and then I am in known
> territory.
>
> Is this generally the right way to think about this?
>

I've looked at just about every type of consumer, security, and machine
vision camera out there, and don't recall seeing any that have a serial
interface. Firewire, ethernet, USB, or cameralink are your available
options.

Also, zigbee tops out at 256Kbps. A single raw 640x480 truecolor frame will
tale 3.6 seconds to transfer. With JPEG compression expect 1/10 of that.
You won't be pushing any meaningful video over zigbee any time soon.

I'd say your best bet would be to find an inexpensive network security
camera and a wireless bridge/client, and focus on the application side.

-spec

--f46d040167f36a4a2704cb445953
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Thu, Oct 4, 2012 at 4:59 PM, Michael =
Cooper <span dir=3D"ltr">&lt;<a href=3D"mailto:mbcoope...@gmail.com" target=
=3D"_blank">mbcoope...@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
Greetings Resistors,<div><br></div><div>I am scoping out a small project an=
d I am in need of a reality-check on basic framework. =A0The project is a r=
emote camera transmitting over zigbee to a pc-based receiver. =A0After some=
 research, I think this is what I need:</div>
<div><br></div><div>2 x zigbee units, one wired to the cam, 1 wired to the =
PC=A0</div><div>1 x camera with UART interface=A0</div><div><br></div><div>=
Steps:</div><div><br></div><div>- wire up the cam to the zigbee -- this is =
simply a matter of connecting the UART out of the cam into the UART input o=
n the zigbee, correct?</div>
<div><br></div><div>- Connect the other zigbee to USB port on the pc (easy)=
<br></div><div><br></div><div>- make the zigbees talk to each other (per zi=
gbee unit documentation)</div><div><br></div><div>- use Processing&#39;s &q=
uot;Serial&quot; library to parse the info from the camera coming based on =
the camera&#39;s specs for the data structure for its visual frame output (=
the camera I am looking at outputs jpeg-encoded frames)</div>
<div><br></div><div>I would have to write a custom parsing script for this =
in Processing, correct?<br></div><div><br></div><div>- theoretically, the r=
esult from that should be an image in jpeg format, so at that point I am th=
inking that I could output the parsed data from Processing as a file, slap =
a &quot;jpg&quot; extension on it, and then I am in known territory.</div>
<div><br></div><div>Is this generally the right way to think about this? =
=A0</div></blockquote><div><br></div><div>I&#39;ve looked at just about eve=
ry type of consumer, security, and machine vision camera out there, and don=
&#39;t recall seeing any that have a serial interface. Firewire, ethernet, =
USB, or cameralink are your available options.</div>
<div><br></div><div>Also, zigbee tops out at 256Kbps. A single raw 640x480 =
truecolor frame will tale 3.6 seconds to transfer. With JPEG compression ex=
pect 1/10 of that. You won&#39;t be pushing any meaningful video over zigbe=
e any time soon.</div>
<div><br></div><div>I&#39;d say your best bet would be to find an inexpensi=
ve network security camera and a wireless bridge/client, and focus on the=
=A0application=A0side.</div><div><br></div><div>-spec</div></div>

--f46d040167f36a4a2704cb445953--