(Ab)using CurrentCost dev boards - code

This is something that I've been meaning to do for a while. I put together a "framework" to deal with the common tasks with the CurrentCost digital development boards, such as transmitting and pairing. I've also provided an example of handling a DHT22 temperature and humidity sensor.

(Ab)using CurrentCost dev boards part 4

Last time around, I'd managed to get as far as starting and stopping the transmitter. I also alluded to the fact that it was slightly more difficult than I'd expected! I also needed to tap the receiver in order to see what's going on! First thing, in order to be able to see that we've transmitted valid data, we need to be able to receive. The CurrentCost EnviR base is already set up correctly for receiving, which should make life easier. So, we need to take the receiver apart and see what we can find.

(Ab)using CurrentCost dev boards part 3

In the previous parts, I looked at how things were connected and how the RF transmitter was configured. This time around, I want to see if I can actually transmit something! The PIC16F689 is the microcontroller in use, and Microchip have made the IDE (MPLabX) and a compiler freely available for those running Windows, Mac or Linux.

(Ab)using CurrentCost dev boards part 2.5

In parts 1 and 2, I flew over the board, how the things were connected and the data that was sent over the SPI bus. I didn't really cover how I got that data out of the device, and Billy picked me up on that. So I thought I should write something to rectify this situation.

If you remember previously, I'd posted a picture that had the pins marked on it. This is really handy reference, as it makes connections plain. From reading the datasheet, there's three pins that are "interesting" at this point. What's really handy is that they're next to each other!

(Ab)using CurrentCost dev boards part 2

In part 1 of this series, I went over what the CurrentCost digital dev board was, and what was on it. In this part, I'm looking a bit more in depth at the components, and trying to figure out how it works.

(Ab)using CurrentCost dev boards part 1

Once upon a time, I purchase a CurrentCost power monitoring device and base station. The monitoring device watches the output of my electricity meter, and the base station displays the information and sends an XML stream over a serial port. It works. However CurrentCost also produce some digital development boards and I picked up three, as it seemed a good idea at the time. Sadly, what I didn't realise (although, it was documented...) is that the boards send a signal indicating 500W consumption when you short the input channel, and a signal indicating 0W consumption when you leave the input channel open. Now, for some people, that's great, but I wasn't happy with it what seemed to be pretty basic operation. I thought to myself, "I'm sure we can get this thing to do a lot more!", so I set about trying to do just that.


If you haven't come across the Currentcost digital development boards before, they look like this: