On page 227, there is an error in the schematic.  IT shows the RX of the FTDI serial-to-USB adaptor connected to TXen of the XBee.  IT should be connected to the TX of the XBee instead.

Lantronix UDP Device Query

 Chapter 7, Processing  Comments Off on Lantronix UDP Device Query
Oct 072007
 
/*
  Lantronix UDP Device Query
  Language: Processing

  Sends out a UDP broadcast packet to query a subnet for Lantronix 
  serial-to-ethernet devices.

  Lantronix devices are programmed to respond to UDP messages 
  received on port 30718.  If a Lantronix device receives the 
  string 0x00 0x00 0x00 0xF6, it responds with a UDP packet 
  containing the status message on port 30718.
  
  When the program starts, press any key on the keyboard and 
  watch the message pane for responses. 
  See the Lantronix integration guide from www.lantronix.com 
  for the details.

  This program uses the Hypermedia UDP library available at  
  hypermedia.loeil.org/processing/
*/

Continue reading »

Toxic Report

 Chapter 7, PHP  Comments Off on Toxic Report
Oct 072007
 
/*
toxic report
Language: PHP

This program opens a socket connection to an Xport and reads bytes from the socket. 
It then sorts the bytes into packets, interprets the packets, reports the results, 
and saves them  to a data log file.

*/

Continue reading »

Lantronix UDP Tester

 Chapter 7, Processing  Comments Off on Lantronix UDP Tester
Oct 072007
 
/*
Lantronix UDP Tester
Language: Processing
Sends and receives UDP messages from  Lantronix serial-to-ethernet devices.
Sends a serial message to a Lantronix device connected to the serial 
port when you type "s". Sends a UDP message to the Lantronix device 
when you type "u". Listens for both UDP and serial messages and 
prints them out.
*/

Continue reading »

XBee Packet Reader and Graphing Program

 Chapter 7, Processing  Comments Off on XBee Packet Reader and Graphing Program
Oct 072007
 
/*
  XBee Packet Reader and Graphing Program
  Language: Processing 
  Reads a packet from an XBee radio via UDP and parses it. 
  Graphs the results over time. The packet should be 22 bytes long, 
  made up of the following:
     byte 1:     0x7E, the start byte value
     byte 2-3:   packet size, a 2-byte value  (not used here)
     byte 4:     API identifier value, a code that says what this response is (not used here)
     byte 5-6:   Sender's address
     byte 7:     RSSI, Received Signal Strength Indicator (not used here)
     byte 8:     Broadcast options (not used here)
     byte 9:     Number of samples to follow
     byte 10-11: Active channels indicator (not used here)
     byte 12-21: 5 10-bit values, each ADC samples from the sender 
*/

Continue reading »

© 2012 Making Things Talk Suffusion theme by Sayontan Sinha