Richard Parker's blog

Part 2a: The Sensor Bar (Arduino Gas Meter project)

Posted in Arduino, Projects by Richard on February 18, 2009

Ok, so here we are a few days later than expected. I’ve been a bit too busy to tinker lately, but I’ve made some interesting progress. I’ll keep this post brief…

Firstly, the phototransistor I ordered from Maplin turned out to be of limited use since it’s ‘detection range’ is a little bit too small to work with the gas meter properly. Also, due to the siting of the gas meter within my property (in a cupboard, with a chair in front of it!), I needed the sensor to be remote to the Arduino. So I ordered a Fairchild Photoreflector from Active Robots. On the surface, it’s everything I need (a photoreflector with wires already attached). Very inexpensive.

Fairchild Photoreflector

Simply dropped this right in place of the existing photoreflector and it works a treat.

Experiments with mounting the sensor to the gas meter

So far, having attempted to mount the sensor on a little bracket in front of the meter, I can’t get an accurate reflection (annoyingly there is a clear plastic cover over the reflective disc which is at a 45 degree angle – sort of – and curved). Having run out of Blu-tac on a previous tinkering experiment, I’ll have to go get some more tomorrow in order to experiment with that.

Reading the meter

I just got my hands on a Nuelectronics LCD Shield so I’ll be setting that up soon to display the meter value.

More to follow soon…

Reading a gas meter with an Arduino, Part 2

Posted in Arduino, Projects by Richard on February 10, 2009

In Part 1 of Reading a Gas Meter with an Arduino, I outlined in brief what I wanted to achieve and how I thought I might go about it.

In this second article, I detail my experiences using the photo-reflector purchased from Maplin. Since I haven’t yet created any circuits more complicated than some basic traffic lights, this would be my first real experience using this type of sensor in a circuit. I had a feeling when starting that I’d be needing to use the pull-down resistor type set-up on one of the sensor pins, and it turns out I was right – special thanks to everyone on the Arduino Forums for assisting.

It turns out, with a little help from the Arduino forums, it was pretty easy (it always is when you know how!). Having first connected the sensor to a digital input, and reading the value from the digital pin in the loop() method, it quickly became clear that trying to count one pass of the reflective disc on the gas meter in this manner wouldn’t work. Adding delay statements wouldn’t work either – I might miss the disc moving past the sensor as the speed it rotates is variable (depending on the amount of gas being consumed). If you’re not sure why this won’t work, think of the Arduino and photo-reflector as a high-speed camera: taking many frames per second the second a reflection is detected. You might receive – for argument’s sake – 1,000 ‘frames’ while the gas meter disc is passing under the sensor, but how do you know – in code – which one to ‘act’ upon and which to ignore? Clearly, you can’t send a thousand ‘pulses’ to your data logger, because your data will all be wrong. This dilemma only came up because in my limited knowledge of the Arduino and the C++ implementation it uses meant that I was trying to stuff all this “detection logic” into the loop() statement.

Enter the Hardware Interrupt… the simplest answer to the problem

In my traditional .NET coding, I’d simply use an ‘event’ to achieve what I wanted, and then write some minimal state-checking code. On the Arduino, however, I have learned that the hardware interrupt is basically very similar (but a bit cooler, actually!). What’s even better is that I don’t even need to bother with any complex code to determine whether or not the sensor is still sensing the same revolution of the disc: when you initialise the interrupt, you state whether you want it to be triggered when a certain condition is met, i.e. any state change, from low to high, from high to low etc. This really nifty feature is exactly what I needed.

Refer to line 7 of the sketch sample below to see how easy it is to register the interrupt. In this example, I simply use the interrupt to turn on an LED whenever the photo-reflector is LOW, i.e. it is detecting a reflection. In later articles, I’ll be changing this to do some logging. The reason for this, is simply that this hardware interrupt is fired only ONCE – and not again until the state changes.

Finding out what’s going on under the hood

I use the Serial library to output ‘debug’ information to help me figure out what’s happening inside the Arduino. It’s not necessary for reading values from the photo-reflector, and at a later stage in this project I’ll probably remove the debug information as I’ll need to be sending the information that is read from the gas meter back to the PC somehow.

The Sketch


int ledPin = 13;                     // select the pin for the LED
volatile int state = LOW;            // remember the current state

void setup() {
  pinMode(ledPin, OUTPUT);            // declare the ledPin as an OUTPUT
  Serial.begin(9600);
  attachInterrupt(0, check, CHANGE);  // attach an interrupt (interrupt 0 = digital pin 2)
}

void loop() {
  digitalWrite(ledPin, state);
}

void check() {    // Checks for feedback from the phototransistor
  state = !state;
  Serial.print("State changed to: ");
  Serial.print(state);
  Serial.print(".\n");
}

Photograph

Schematic

I have attempted to re-create the above in schematic form, using Fritzing. As mentioned in earlier posts, Fritzing is a beta tool and it doesn’t currently have symbols for all the electrical components one might use. Having searched the web for a suitable circuit symbol for my photoreflector, I can’t find one. I suspect that because, although the photo-reflector is an ‘all-in-one’ design, it is actually just comprised of an LED and a photosensitive transistor:

Arduino schematic showing placement of maplin photo-reflector

Next Steps…

Now that I have figured out how to interpret a value from a photo-reflector within the Arduino, what I need to do is build a prototype sensor ‘bar’ that I can mount to the gas meter. The next post on this subject will probably be just that – how I made (or am making!) the sensor bar. One point I’ll be bearing in mind is that I’d like to site the Arduino remotely from the sensor arm, and I’d like to be able to collect data from other sensors attached to the same board. Thinking ‘out loud’ as I go really, but I promise to write a proper ‘How-To’ article when I’m on the other side of the learning curve!

Reading a gas meter with an Arduino, Part 1

Posted in Arduino, Projects by Richard on February 9, 2009

Ok, since I received my Arduino, I have been playing around with some simple projects in an effort to understand more about the way the Arduino board works, and to gather some of the basic electronic skills necessary to work with it. So now, I want to turn my attention to something a little more in tune with my reasons for actually buying the Arduino in the first place: home automation.

After a trip to the gas meter cupboard, unfortunately my gas meter is not the type that outputs a digital ‘pulse’ at regular intervals: it’s an odometer type. However, usefully, I did discover that it has a little reflective disc between the digit ’6′ and ’7′, which could presumably be read with some kind of reflection sensor. I did some digging around to see who else on the web has built their own gas-meter readers, and found BWired.nl. This is an awesome site – certainly way beyond what most of us mere mortals could aspire to for our home automation setups! Anyway, on this page, the owner describes using a ‘CNY70 Reflective Optical Sensor with Transistor Output’. After some digging around, I found that Maplin has something which (I think) might be similar here - it’s called “Photoreflector SY-CR102″ and it costs £0.79! This neat little device includes a photo-emitting diode and a phototransistor, which should do the trick.

I’ll go down to the store and pickup the Photoreflector later today, and have a go at playing with it over the coming days. Essentially what I need to do is figure out how the sensor responds whenever the reflective disk of the gas meter passes the sensor aperture. In theory then, at least, it’s then going to be a case of simply counting the ‘pulses’ from the sensor. Once I can do that, given that the dial will rotate once a known quantity of gas has been consumed, I should be able to create a very accurate sensor device that is synchronous with the gas meter itself.

Here’s how I imagine the project to unfold:

I’m quite excited about this – it’s such a steep learning curve though! :)

/Rich

Arduino Traffic Lights – Take Two

Posted in Arduino, Projects by Richard on February 9, 2009

Ok, so after starting my first project (yesterday: Arduino timer-based traffic lights), I decided to expand upon the concept today. In keeping with the traffic light theme (it seemed like a good idea!), I added a few extra LEDs and a digital switch so that someone can ‘cross the road’ by pressing the button to change the lights to red.

Scenario: traffic and crossing lights

Instead of having the lights cycle from red – amber – green infinitely as in the previous project, this time I wanted the lights to go through a fake initialise sequence (i.e. turn on the Arduino board, have the red LED blink 5 times, then have all three traffic lights switch on, as an example) then to step to amber, then green. To make things a little more interesting, I also added two new LEDs: a ‘Green Man’ and a ‘Red Man’ light – to help our little pedestrians figure out when it’s safe to cross the road. :)

The traffic lights should remain on green until a ‘pedestrian’ presses the crossing button, at which point we should go to amber, then red. We should wait a little bit for the pedestrian to cross, blink the green man light a few times to indicate that the pedestrian needs to get out of the road, followed by blinking the Amber light a few times to alert the traffic to get ready, then go back to a green traffic light and a red man light.

The lights and crossing should obey the following rules:

  • When a red traffic light is displayed, the green man light should be on
  • When a green traffic light is displayed, the red man light should be on

Common sense really! :)

So our sequence of events needs to resemble the following:

  • Initialise the lights (blink red LED 5 times, then turn on all three traffic lights)
  • Show amber traffic light
  • Show green traffic light and wait on green
    • When the crossing button is pressed:
      • Show the amber traffic light
      • Show the red traffic light
      • Show the green man
      • Wait a preset amount of time to let the pedestrians cross
      • Blink the green man light a few times
      • Blink the amber traffic light a few times
      • Extinguish the green man light and turn on the red man light
    • Resume green traffic light
    • Repeat!

After about a half hour tinkering, I’d stripped the breadboard and added a digital switch and two new LEDs (for the crossing indicators). The Arduino sketch was modified to include controls for the crossing LEDs, and the continuous alternating traffic light sequence was replaced with a solid green LED (which remains green until the switch is pressed).

A quick observation: the digital switch and pull-down resistors

My switch is connected to a digital input. Initially, this resulted in an intermittent switch: picking up HIGH or LOW sometimes worked, and sometimes didn’t. I figured out after a little bit of Googling that I actually needed to connect the switch in a mini ‘pull-down resistor circuit’ which now works brilliantly. I will admit, I have yet to fully understand the principles behind why this works, but that’s something I will continue to look into (besides wanting to just have fun with the Arduino, one of my goals is to learn more about the basic electrical principles regarding physical computing).

The board setup:

Pedestrian Crossing with Traffic Lights

And the wiring diagram:

Now then! The lovely Fritzing program I used to create the above diagram (which I absolutely love), is so new, that it doesn’t (yet) have a switch symbol for the type of switch I have used. Hence, with my very limited knowledge of electrical schematics, I’ve used the standard switch symbol and tried to represent how I’ve actually wired the switch up. Here’s a close-up photograph of what I’ve actually done, in the hopes that someone can correct me:

Switch Detail

I found this technique here.

Video:

The Sketch

This is a bit messy at the moment, but I’ll clean it up tomorrow (I’ve used generic on/off methods to set light states instead of just using a ‘setRed’ or ‘setGreen’ method, which encapsulates the code to extinguish lights that aren’t used by that mode, for instance) and also remove some of the ‘debugging’ serial code I wrote:

// Configure the light pins
int redLed = 2;
int yelLed = 3;
int grnLed = 4;
int redManLed = 8;
int grnManLed = 7;

// Program variables
int lightState = 0;
int crossingRequestSwitchPin = 13;            // The pin our crossing button is connected to
int switchStatePin = 6;

// Traffic Light Variables
int timerDelayTime = 3000;                    // The ms between each light change when running in timer mode
int crossingTime = 5000;

// Setup
void setup() {
  pinMode(redLed, OUTPUT);
  pinMode(yelLed, OUTPUT);
  pinMode(grnLed, OUTPUT);
  pinMode(switchStatePin, OUTPUT);
  pinMode(grnManLed, OUTPUT);
  pinMode(redManLed, OUTPUT);
  pinMode(crossingRequestSwitchPin, INPUT);
  Serial.begin(9600);                        // Initialise the serial port for debugging
  changeLightState(-1);                      // Set the light state to "initialise".
}

void loop() {
 if (lightState == -1) {
   doBeginSequence();
   changeLightState(0);                      // Now our "initialise" phase is done, increment the light state
 }
 if (lightState == 0) {
   lightOn(redLed);
   lightOn(yelLed);
   lightOn(grnLed);
   delay(1500);
   startLightsOnTimer();
 }
}

void doBeginSequence() {                    // Handles the lighting sequence for lights that have just been started.
  Serial.println("Begin sequence was requested.");
  blinkLed(redLed, 5, 500);
}

void startLightsOnTimer() {

  Serial.println("Starting timed-sequence.");
  allLightsOff();                          // Turn all lights off

  while ( lightState == 0 ) {    

    lightOn(grnLed);
    lightOn(redManLed);

    /*lightOn(redLed);
    delay(timerDelayTime);
    lightOn(yelLed);
    delay(timerDelayTime);
    lightOff(redLed);
    lightOff(yelLed);
    lightOn(grnLed);
    */

    // When the light is green, allow anyone to signal for a crossing request
    int request = checkForCrossingRequest();
    if (request > 0) {
      Serial.println("Beginning crossing sequence...\n");
      beginCrossing();
    }

  }

}

// Switch lights to red for a crossing sequence
void beginCrossing() {

   changeLightState(1);                 // Indicate that we're beginning a crossing sequence

   // Goto Amber...
   allLightsOff();
   lightOn(yelLed);
   delay(timerDelayTime);

   // Goto Red, and wait for crossingTime milliseconds before continuing...
   lightOff(redManLed);
   lightOff(yelLed);
   lightOn(redLed);
   lightOn(grnManLed);
   delay(crossingTime);
   blinkLed(grnManLed, 5, 500);

   // Blink the Yellow Led...
   lightOff(redLed);
   blinkLed(yelLed, 5, 500);            // Blink the Yellow LED 5 times to signal to drivers to proceed if the way is clear
   lightOn(grnLed);
   lightOff(grnManLed);
   changeLightState(0);                 // Change back to timer mode lighting

}

// Check for crossing button push
int checkForCrossingRequest() {
  int val = digitalRead(crossingRequestSwitchPin);
  if (val == HIGH) {
    Serial.println("*** Crossing Request Received ***\n");
    return 1;      // Crossing requested
  } else {
    return 0;
  }
}

// Helper functions
void lightOn(int pin) {      // Turn an LED on
   digitalWrite(pin, HIGH);
   Serial.print("Set pin ");
   Serial.print(pin);
   Serial.print(" to HIGH.\n");
}

void allLightsOff() {       // Turns all LEDs off
  digitalWrite(redLed, LOW);
  digitalWrite(yelLed, LOW);
  digitalWrite(grnLed, LOW);
  Serial.println("All lights turned OFF.\n");
}

void lightOff(int pin) {    // Turn an LED off
  digitalWrite(pin, LOW);
  Serial.print("Set pin ");
  Serial.print(pin);
  Serial.print(" to LOW.\n");
}

void blinkLed(int pin, int timesToBlink, int blinkIntervalMs) {  // Blinks the LED pin the set number of times
  Serial.print("Beginning blink sequence... Pin ");
  Serial.print(pin);
  Serial.print(", ");
  Serial.print(timesToBlink);
  Serial.print(" times with a ");
  Serial.print(blinkIntervalMs);
  Serial.println("ms interval between each blink.\n");

  for (int i=0; i <= timesToBlink; i++) {
    digitalWrite(pin, HIGH);
    delay(blinkIntervalMs);
    digitalWrite(pin, LOW);
    delay(blinkIntervalMs);
  }
}

void changeLightState(int newLightState) { // Changes the current lightState
  Serial.print("Light state changed from ");
  Serial.print(lightState);
  Serial.print(" to ");
  Serial.print(newLightState);
  Serial.println(".\n");
  lightState = newLightState;
}

So! There you have it… My second Arduino project… or, rather an extension of the first! Thanks for reading!

/Rich