Xb24-aci-001 pdf

Unfortunately the current received is lower than required to run the Xbee and as a result a large capacitor is used to account for the current needed. The C1 and C2 is to provide a constant voltage to the 3. The voltage divisor is used to decrease the sensors inputs received from the Kill-A-Watt at 5V to 3.

The last resistor is used to power the LED. In this demonstration we did not create our own circuit board but instead used one that was meant for the receiver. Creating your own transmitter circuit board will greatly increase the speed and simplicity of putting this together.

You must change these options within the program:. I decided to use the PCB board created for the XBee host controller by adafruit this saved some time in creating a new PCB board and also using just a breadboard.

It can twitter the energy usage and also upload your data into a spreadsheet in google docs. I will not be covering how to use this program here. You are able to use any almost any programming language to communicate with the Xbee unit. Most popular programming languages have third party APIs for the Xbee. I am going to be using the open source language python python , as the code is readily available, free and will save time.

I added support for two meters to adafruit's original code [3] and Brian Naughton's modification for pachube [4]. The modification will average the data received from both power meters into two separate variables and upload it to pachube. Without the modification the program would combine the average into one variable which I feel provides less useful information.

In the following steps I will demonstrate how to modify the code for your own power meter. Most of the design was straight forward but I did come across several problems when adding multiple Kill-A-Watts also the new Kill-A-Watt revision did not make things easy either.

One of the problems I encountered with the software was to find a good website to host the data. Google powermeter was my first choice but it did not allow me to share the data publicly. Instead it required every person who wanted to see the data to be invited. The next website I found was Pachube [5] , it was a very straight forward website and allowed me to publicly share the data. Problems did arise when multiple power meters were added.

The original program was written for only one power meter. The modification above was necessary to account for this challenge.

The new Kill-A-Watt revision did not allow a simple way to route the wiring around to the other side. A notch was needed to be made on the PCB which was risky as a wrong move could break a connection.

Another problem that I came across was calibration. It appeared that the Kill-a-Watt's ampdata reference numbers were drifting with time.

I came to the conclusion that it was due to the wiring onto the Op-Amp and it was creating a connection with something it shouldn't of. Please enable JavaScript to pass antispam protection! Antispam by CleanTalk. Views by admins and bots are not counted. Multiple views during the same session are counted as one. Retrieved January 13, Loading map Solder on LED and its respective resistor to reduce the current.

The voltage regulator regulates the voltage to 3. The 10k resistors are soldered onto analog input pin AD0 and AD4 and to ground. Solder on two 4. Finish soldering the 4. Now for the uF capacitor. Solder the diode make sure the diode is pointing to the capacitor to the positive lead of the capacitor and then connect it to the XBee's power source through the voltage regulator. Then solder the negative lead to it's respective ground.

Solder on a wire to the positive and negative lead, make sure you use a heat shrink to cover the leads once you are done. This will be used to connect to the Kill-A-Watt's power source. This step can be different for everyone depending on what revision of the Kill-A-Watt you received.

But it's functionality is still the same. The Op-Amp is circled in the picture. This step is optional depending on revision. Make a hole on the PCB board in this case we did to the left of the Op-Amp in order to feed through the wires to the other side.

The modules require minimal power and provide reliable delivery of data between devices. The modules Through its serial port, the module can communicate with any logic and voltage com- patible UART; or through a level translator to When operating in this mode, the modules act as a serial line replacement - all UART data received through the DI pin is queued up for RF transmission. The establishment of membership is useful in scenarios that require a central unit Coordinator to relay messages to or gather data from several remote units End The Energy Scan selects one channel and scans for energy on that channel.

The duration of the scan The RF module conforms to the A unique The module shifts into the other modes of operation under the following Also, a Coordinator using indirect transmissions will revert to direct transmission if it knows the destination module In order to enter Sleep Mode, one of the following conditions must be met in addition to the module having a When waking the module, the pin must be de-asserted at least two 'byte times' after CTS goes low.

This assures that there is time for the data to enter the DI buffer. This API frame can be used to send commands to a remote module to Write parameter values to non-volatile memory so that parameter modifications persist through subsequent power-up or reset.

Enables node discover self-response on the module. Resolves an NI Node Identifier string to a physical address. The following events occur Read errors with the last association request: 0x00 - Successful Completion - Coordinator successfully started or End Device association complete 0x01 - Active Scan Timeout 0x02 - Active CCA Threshold. Prior to Serial BD Interfacing Request non-standard baud rates with D5 v1. Read hardware version of the RF module. Received Signal Strength. Absolute value