F12: Smart Bulb - Revision history

Stephanie: /* Testing & Technical Challenges */

2012-12-20T20:28:18Z

‎Testing & Technical Challenges

Stephanie: /* References Used */

2012-12-20T18:55:11Z

‎References Used

Stephanie: /* Appendix */

2012-12-20T18:54:58Z

‎Appendix

Stephanie: /* References Used */

2012-12-20T18:54:27Z

‎References Used

Stephanie: /* Implementation of PCB Software */

2012-12-20T18:53:46Z

‎Implementation of PCB Software

Stephanie: /* System Components */

2012-12-20T18:35:39Z

‎System Components

Stephanie: /* Shared-Intelligence Network Manager (siNetworkMgr) */

2012-12-20T18:35:10Z

‎Shared-Intelligence Network Manager (siNetworkMgr)

Stephanie: /* Shared-Intelligence Network Manager (siNetworkMgr) */

2012-12-20T18:34:57Z

‎Shared-Intelligence Network Manager (siNetworkMgr)

Stephanie: /* Light Sampling via Color Sensor */

2012-12-20T18:27:00Z

‎Light Sampling via Color Sensor

Stephanie: /* Implementation of PCB Software */

2012-12-20T18:25:04Z

‎Implementation of PCB Software

@@ Line 908: / Line 908: @@
 ** To find shorts, we would use a multimeter to perform a continuity test and verification on the pins. We would also look at the processor chip (it was prone to shorts from the solder drag) under a magnifying glass/microscope
 ** Board shorting was a particularly difficult challenge we faced, and we would suggest very carefully assembling the board and paying attention to the components which are difficult to solder -- it costed us a lot of time and frustration when a hardware problem was confused with a software issue
 == Conclusion ==

@@ Line 933: / Line 933: @@
 * [https://github.com/drslump/Protobuf-PHP DrSlump's Protobuf-PHP library]
 * [http://koti.kapsi.fi/jpa/nanopb/ Nanopb - protocol buffers with small code size]
-* [https://github.com/paulhodge/EASTL - Clone of the EASTL library taken from http://gpl.ea.com/]
+* [https://github.com/paulhodge/EASTL Clone of the EASTL library taken from http://gpl.ea.com/]
 === Appendix ===

← Older revision		Revision as of 18:54, 20 December 2012
Line 942:		Line 942:
	* [http://www.parallax.com/Portals/0/Downloads/docs/prod/sens/555-28027-PIRSensor-v2.2.pdf Parallax PIR Motion Sensor Datasheet]		* [http://www.parallax.com/Portals/0/Downloads/docs/prod/sens/555-28027-PIRSensor-v2.2.pdf Parallax PIR Motion Sensor Datasheet]
	* [ftp://ftp1.digi.com/support/documentation/90000991_B.pdf XBee/XBee-PRO DigiMesh™ 2.4 RF Modules Product Sheet]		* [ftp://ftp1.digi.com/support/documentation/90000991_B.pdf XBee/XBee-PRO DigiMesh™ 2.4 RF Modules Product Sheet]
		+	* [http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2271.html EASTL -- Electronic Arts Standard Template Library]

@@ Line 933: / Line 933: @@
 * [https://github.com/drslump/Protobuf-PHP DrSlump's Protobuf-PHP library]
 * [http://koti.kapsi.fi/jpa/nanopb/ Nanopb - protocol buffers with small code size]
 === Appendix ===

@@ Line 697: / Line 697: @@
+	}
+}
 </pre>

← Older revision		Revision as of 18:35, 20 December 2012
Line 405:		Line 405:

	[[File:CmpE146_F12_T2_PWM_MatchRegDiag.png\|center\|frame\|x200px\|Match Register Diagram]]		[[File:CmpE146_F12_T2_PWM_MatchRegDiag.png\|center\|frame\|x200px\|Match Register Diagram]]
		+
		+	===== Protocol Buffers =====
		+	We utilized Google Protocol Buffers to exchange data among devices within the shared-intelligence network. Protocol buffers enable a single ''.proto'' file to be written, which dictates the fields of the message which will be exchanged. A single message can contain multiple levels of nested messages, along with integer values (32-bit and 64-bit), floating point values, booleans, arrays, and strings. The .proto file is compiled using a protocol buffer compiler, which then generates language-specific object-oriented implementation files. The fields within the message object are modified to contain the data to be sent, and the message is then serialized into an on-the-wire format which is machine-type independent. This enables messages to transverse between machines of different endianness (such as our x86 PHP server and our ARM-based SmartBulb) without additional work. When the message arrives at the destination, it is deserialized back into a message object, which can then be reviewed by the recipient.

	=== Web Interface Design ===		=== Web Interface Design ===

← Older revision		Revision as of 18:35, 20 December 2012
Line 339:		Line 339:

	===== Shared-Intelligence Network Manager (siNetworkMgr) =====		===== Shared-Intelligence Network Manager (siNetworkMgr) =====
−	We utilized Google Protocol Buffers to exchange data among devices within the shared-intelligence network. Protocol buffers enable a single ''.proto'' file to be written, which dictates the fields of the message which will be exchanged. A single message can contain multiple levels of nested messages, along with integer values (32-bit and 64-bit), floating point values, booleans, arrays, and strings. The .proto file is compiled using a protocol buffer compiler, which then generates language-specific object-oriented implementation files. The fields within the message object are modified to contain the data to be sent, and the message is then serialized into an on-the-wire format which is machine-type independent. This enables messages to transverse between machines of different endianness (such as our x86 PHP server and our ARM-based SmartBulb) without additional work. When the message arrives at the destination, it is deserialized back into a message object, which can then be reviewed by the recipient.
−
	The shared-intelligence network manager pulls for new encoded protocol buffer messages from the XBee API, and then passes received messages to the protobuffer library for decoding / deserializaton. Messages which are successfully decoded by the protobuffer library are then passed into the Bulb Logic task via an RTOS queue. In addition, the siNetworkMgr verifies that the bulb's unique identification address exists within the shared-intelligence network message's recipient field.		The shared-intelligence network manager pulls for new encoded protocol buffer messages from the XBee API, and then passes received messages to the protobuffer library for decoding / deserializaton. Messages which are successfully decoded by the protobuffer library are then passed into the Bulb Logic task via an RTOS queue. In addition, the siNetworkMgr verifies that the bulb's unique identification address exists within the shared-intelligence network message's recipient field.

@@ Line 339: / Line 339: @@
 ===== Shared-Intelligence Network Manager (siNetworkMgr) =====
-The shared-intelligence network manager pulls for new messages from the XBee API, and then passes received messages to the protobuffer library for decoding / deserializaton. Messages which are successfully decoded by the protobuffer library are then passed into the Bulb Logic task via an RTOS queue. In addition, the siNetworkMgr verifies that the bulb's unique identification address exists within the shared-intelligence network message's recipient field.
+We utilized Google Protocol Buffers to exchange data among devices within the shared-intelligence network. Protocol buffers enable a single ''.proto'' file to be written, which dictates the fields of the message which will be exchanged. A single message can contain multiple levels of nested messages, along with integer values (32-bit and 64-bit), floating point values, booleans, arrays, and strings. The .proto file is compiled using a protocol buffer compiler, which then generates language-specific object-oriented implementation files. The fields within the message object are modified to contain the data to be sent, and the message is then serialized into an on-the-wire format which is machine-type independent. This enables messages to transverse between machines of different endianness (such as our x86 PHP server and our ARM-based SmartBulb) without additional work. When the message arrives at the destination, it is deserialized back into a message object, which can then be reviewed by the recipient.
 This task is necessary, as Bulb Logic must be able to respond to both internal and external (network-based) events. To facilitate this requirement, the siNetworkMgr task sends external events to the Bulb Logic task processing queue, while other components, including interrupts and the ambient-light sampling task, send internal events to the processing queue.

@@ Line 700: / Line 700: @@
 ==== Light Sampling via Color Sensor ====
-Ambient light sensing was accomplished via a TAOS color sensor, which was communicated with via I<sup>'2'</sup>C. Setting up the sensor for simple operation is an easy task:
+Ambient light sensing was accomplished via a TAOS color sensor, which was communicated with via I<sup>'2'</sup>C. The sensor has four different channels (red, blue, green, clear) to measure light. Each of these channels is read to determine the composition of the current light sampled.
 # Initialize the I<sup>'2'</sup>C bus (if not already completed)
 # Write to the color sensor's control register to enable the ADC
 # Write to the color sensor's gain register to enable maximum gain
-# Periodically read from the 8 color registers (which have high and low bytes) to determine the current value of the light sampled
+# Periodically read from the 8 color registers (which have high and low bytes) to determine the composition of the current light sampled.
-'''Reading Data via TAOS Color Sensor:'''
+'''Pseudo-code for reading sampled color via TAOS Color Sensor:'''
 <pre>
 // constant values

@@ Line 693: / Line 693: @@
 		break;
+	}
+}
 </pre>