Received: by 10.224.117.143 with SMTP id r15mr7795676qaq.1.1349456294194; Fri, 05 Oct 2012 09:58:14 -0700 (PDT) X-BeenThere: nycresistormicrocontrollers@googlegroups.com Received: by 10.229.106.89 with SMTP id w25ls825218qco.0.gmail; Fri, 05 Oct 2012 09:58:04 -0700 (PDT) Received: by 10.224.183.13 with SMTP id ce13mr7803047qab.4.1349456284723; Fri, 05 Oct 2012 09:58:04 -0700 (PDT) Received: by 10.224.183.13 with SMTP id ce13mr7803045qab.4.1349456284702; Fri, 05 Oct 2012 09:58:04 -0700 (PDT) Return-Path: Received: from mail-qc0-f175.google.com (mail-qc0-f175.google.com [209.85.216.175]) by gmr-mx.google.com with ESMTPS id a27si2243929qck.3.2012.10.05.09.58.04 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Oct 2012 09:58:04 -0700 (PDT) Received-SPF: pass (google.com: domain of liminastu...@gmail.com designates 209.85.216.175 as permitted sender) client-ip=209.85.216.175; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of liminastu...@gmail.com designates 209.85.216.175 as permitted sender) smtp.mail=liminastu...@gmail.com; dkim=pass header...@gmail.com Received: by mail-qc0-f175.google.com with SMTP id j3so1304288qcs.20 for ; Fri, 05 Oct 2012 09:58:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer; bh=lk/PYyTq/7h79z6S0DMxpaGLI8fNk+eJd7a3u+Qsh+U=; b=pmmD0H55UvE6PKvuSW7m8mws9c5coeYy7eDuN2kb8qBBgQusVgTmcB3d21+ihzCU74 4+F8Ab7l4sD1YDTyarEDQVLn+tAx7wUjTXG8PfpkcdQ1w3VJvyRJWGg6314eBfjIePtK whDELGQ4gaSrP0pOWAXedpI2y5qJM38u5M2yjTg70K7nC+jPMSf2+RbpgWAixHlaEnbx C23eC5Tp2ffz2dea906FiIQWUmMnm2Ru9bKLfwkggoHW2KEs7vKyNKKo4LaJujjSexuH qwzydMggF8PcJVsPfb27SD4fnYcWy9e/bV/cdfBX0yqgDowzyoULcsz7XWDeGraGBHxZ Tj1w== Received: by 10.224.217.136 with SMTP id hm8mr1228292qab.81.1349456284488; Fri, 05 Oct 2012 09:58:04 -0700 (PDT) Return-Path: Received: from [10.2.99.128] ([204.145.81.110]) by mx.google.com with ESMTPS id a8sm10512445qew.11.2012.10.05.09.58.01 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Oct 2012 09:58:03 -0700 (PDT) From: "Ted Hayes | Limina.Studio" Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: multipart/alternative; boundary="Apple-Mail=_09B5B280-C7B8-4738-9602-0DD7D963A8FC" Subject: Re: [NYCR:Microcontrollers] zigbee + UART jpeg cam Date: Fri, 5 Oct 2012 12:58:05 -0400 In-Reply-To: To: nycresistormicrocontrollers@googlegroups.com References: <84DDA1B3-24BE-4A56-AB72-2B3FC76BF...@gmail.com> Message-Id: <852A76AB-C902-4BB1-B97F-36A9B11A5...@gmail.com> X-Mailer: Apple Mail (2.1283) --Apple-Mail=_09B5B280-C7B8-4738-9602-0DD7D963A8FC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 > Now I'm confused: I thought zigbee used 802.15.4 and added an = abstraction layer for meshing. =20 That's correct. ZigBee is mesh, "bare" 802.15.4 is not. The "S1" XBee = modules (formerly known as "Series 1") are just 802.15.4. (Comparison = chart: http://www.digi.com/pdf/chart_xbee_rf_features.pdf) Mesh networking adds lots of overhead since it has to maintain routes = between nodes. The downside is throughput. =97t3db0t On Oct 5, 2012, at 12:49 PM, Michael Cooper wrote: > Now I'm confused: I thought zigbee used 802.15.4 and added an = abstraction layer for meshing. =20 >=20 > I suppose I could use a 802.15.4 device without the zigbee layer, but = what is the downside to using zigbee here since it is (supposed to be) = easy to set up? =20 >=20 > On Friday, October 5, 2012 10:33:50 AM UTC-4, Tedb0t wrote: > Agreed. >=20 > Generally speaking, the only time you want to use zigbee is if you = *need* a mesh network. Point-to-point applications are better off using = 802.15.4 or bluetooth or some other radio link. >=20 > =97t3db0t >=20 > On Oct 4, 2012, at 4:59 PM, Michael Cooper wrote: >=20 >> Greetings Resistors, >>=20 >> 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: >>=20 >> 2 x zigbee units, one wired to the cam, 1 wired to the PC=20 >> 1 x camera with UART interface=20 >>=20 >> Steps: >>=20 >> - 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? >>=20 >> - Connect the other zigbee to USB port on the pc (easy) >>=20 >> - make the zigbees talk to each other (per zigbee unit documentation) >>=20 >> - 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) >>=20 >> I would have to write a custom parsing script for this in Processing, = correct? >>=20 >> - 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. >>=20 >> Is this generally the right way to think about this? =20 >>=20 >> Thanks very much for any help, advice, suggestions. >>=20 >> - Michael >>=20 >> --=20 >> You received this message because you are subscribed to the Google = Groups "NYCResistor:Microcontrollers" group. >> To view this discussion on the web visit = https://groups.google.com/d/msg/nycresistormicrocontrollers/-/6RqzhasaP-QJ= . >> To post to this group, send email to = nycresistormi...@googlegroups.com. >> To unsubscribe from this group, send email to = nycresistormicrocontrollers+unsubscribe@googlegroups.com. >> For more options, visit this group at = http://groups.google.com/group/nycresistormicrocontrollers?hl=3Den. >=20 >=20 > --=20 > You received this message because you are subscribed to the Google = Groups "NYCResistor:Microcontrollers" group. > To view this discussion on the web visit = https://groups.google.com/d/msg/nycresistormicrocontrollers/-/s3jKc2VPECAJ= . > To post to this group, send email to = nycresistormicrocontrollers@googlegroups.com. > To unsubscribe from this group, send email to = nycresistormicrocontrollers+unsubscribe@googlegroups.com. > For more options, visit this group at = http://groups.google.com/group/nycresistormicrocontrollers?hl=3Den. --Apple-Mail=_09B5B280-C7B8-4738-9602-0DD7D963A8FC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Now I'm confused: I thought zigbee used = 802.15.4 and added an abstraction layer for meshing. =  

That's correct. ZigBee is mesh, = "bare" 802.15.4 is not.  The "S1" XBee modules (formerly known as = "Series 1") are just 802.15.4. (Comparison chart: http://www.dig= i.com/pdf/chart_xbee_rf_features.pdf)

Mesh = networking adds lots of overhead since it has to maintain routes between = nodes.  The downside is = throughput.

=97t3db0t

On = Oct 5, 2012, at 12:49 PM, Michael Cooper wrote:

Now I'm = confused: I thought zigbee used 802.15.4 and added an abstraction layer = for meshing.  

I suppose I could use a 802.15.4 = device without the zigbee layer, but what is the downside to using = zigbee here since it is (supposed to be) easy to set up? =   

On Friday, October 5, 2012 10:33:50 AM UTC-4, = Tedb0t wrote:
Agreed.

Generally = speaking, the only time you want to use zigbee is if you *need* a mesh = network.  Point-to-point applications are better off using 802.15.4 = or bluetooth or some other radio = link.

=97t3db0t

On Oct = 4, 2012, at 4:59 PM, Michael Cooper 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?  

Thanks very = much for any help, advice, suggestions.

- = Michael

--
You received this message because you are subscribed to the Google = Groups "NYCResistor:Microcontrollers" group.
To view this discussion on the web visit https://groups.google.com/d/msg/nycresistormic= rocontrollers/-/6RqzhasaP-QJ.
=20 To post to this group, send email to nycresistormi...@googlegroups.= com.
To unsubscribe from this group, send email to nycresistormicrocontrollers+un= subscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nycresistormicr= ocontrollers?hl=3Den.


--
You received this message because you are subscribed to the Google = Groups "NYCResistor:Microcontrollers" group.
To view this discussion on the web visit https://groups.google.com/d/msg/nycresistormicrocontrollers/-/s3= jKc2VPECAJ.
=20 To post to this group, send email to nycresistormi= crocontrollers@googlegroups.com.
To unsubscribe from this group, send email to n= ycresistormicrocontrollers+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nycresistormicrocontrollers?hl=3Den.<= br>

= --Apple-Mail=_09B5B280-C7B8-4738-9602-0DD7D963A8FC--