I have created a super simple web-based automation framework (yes, one of many). With AutoTalk, you can get started in just 10 minutes!

Check it out here ( * there are videos to help get you started * ):
http://andrewfrueh.com/autoTalk/

AutoTalk allows you to communicate with and control your Arduino from a web-dashboard. The focus of AutoTalk is to create a message protocol that is easy for beginners but powerful enough for more complex projects. Please give feedback if you use AutoTalk so I can work that into the next version.

Thanks,
Andrew

Have you tried the "servo knob" tutorial. It is very simple, and it would at least eliminate the possibility of problems in the code.

The tutorial is here:
http://arduino.cc/en/Tutorial/Knob

Yup, tone() is included as part of the language in 0018, so you won't need to include the Tone library. But be aware that the implementation changed a bit.

For example in 0017 it would be:

Code:

#include <Tone.h>  
const int audioPin = 7; // the pin you will use for the audio out

void setup() {
  toneGenerator.begin(audioPin); // attach the pin to the tone object
}

void loop() {
    toneGenerator.play(NOTE_A4);
}

While in 0018 it would be:

Code:

#include "tone_note_definitions.h" // this include is for the note names (optional, you will need to create this file -- they were built into the old library)
const int audioPin = 7; // the pin you will use for the audio out

void setup(){
  // we don't need anything here now
}

void loop(){
  tone(audioPin, NOTE_A4);
}

Oh no. Oh well.

Is it possible that you will be able to resolve the conflict between Tone and Servo in the future, or is this a limitation of the hardware?

Here is a video of what we are working on and why we have a need for Servo and Tone together.


There will be several of these birds, and I was hoping I would be able to run more than one with each Arduino board (as opposed to having to buy a separate board for each bird).

Hiya,

I am very excited to see the addition of tone() to the regular Arduino release. I was experiencing compiler errors when I used the servo() and tone() libraries together in the previous version (0017). This new version seems to have fixed the problems I was experiencing before.

However, I have a new problem. The new implementation of tone() does not allow you to create multiple instances (new objects) to have more than one tone playing at a time. Perhaps the previous object-based implementation could be re-introduced in the next version.

I hope this is an easy fix/addition because as it is now I will have to use a separate Arduino board for each audio channel I want which is, of course, very costly.

I just realized that I posted this thread to the wrong section. It really should be posted in the "software" section. I will re-post it there.

No problem. I was actually developing both parts of my project separately -- servo and tone in different scripts. I didn't realize there was a conflict between tone and servo until I merged the two scripts together -- big bummer.

I am hoping that it will be possible (easy/whatever) for the implementation to be object based in the next version. That way you create a new tone object for each sound channel you need.

Fingers crossed.

The problem is that when I use the servo and tone libraries together, I get compiler errors (I am running Arduino 0018 on WinXP).

If I "verify" this script in Arduino:

Code:

#include <Servo.h>
#include <Tone.h>

void setup(){}

void loop(){}

I get the following errors:

>>
[path to library]\Tone\Tone.cpp.o: In function `__vector_11':

[path to library]\Tone\Tone.cpp:438: multiple definition of `__vector_11'

[path to library]\Servo\Servo.cpp.o:[path to library]\Servo\Servo.cpp:103: first defined here
<<


and p.s. cr0sh, I think the synth shield is a great idea!

Hiya,

I am very excited to see the addition of tone() to the regular Arduino release. I was experiencing compiler errors when I used the servo() and tone() libraries together in the previous version (0017). This new version seems to have fixed the problems I was experiencing before.

However, I have a new problem. The new implementation of tone() does not allow you to create multiple instances (new objects) to have more than one tone playing at a time. Perhaps the previous object-based implementation could be re-introduced in the next version.

I hope this is an easy fix/addition because as it is now I will have to use a separate Arduino board for each audio channel I want which is, of course, very costly.

Sorry for any confusion.

AutoTalk allows you to set up a basic web-dashboard to control your Arduino board (no it does not need to be on the same machine, I just happen to use a local web server on my machine).

The current package comes with a script for your Arduino, and some files to run the web-dashboard side of it.

I tired to keep everything simple so it could be modified easily.

I am very interested in feedback, so if you decide to try it out, please let me know what you find.

I just created a project page for this framework I'm working on.

Go to the AutoTalk project page.

AutoTalk is a communication framework. It is both a language and some scripts for parsing/wrapping messages. The package for this version has an Arduino script and a web-based dashboard so you can control you project and receive data from it.

AutoTalk is the messaging system that will be used by the next version of GardenBot.

GWRedDragon,

I like your project and your focus on running on battery power. Looking forward to seeing what you come up with.

Heya

This is pretty exciting. Check out the article.

GardenBot was featured on Wired.com
http://www.wired.com/gadgetlab/2010/08/gardenbot-gardening/

nickvd,

I'm happy to explore other ways to pull that off. There are a couple of reasons for having the local circuit portion of the module -- and yeah, they are all electronics related.

The capacitor in the sensor local circuits is acting as a noise filter, and it needs to be located physically close to the Arduino to be effective.
The other thing is that by keeping the power line in the brain, you only need two wires out to the sensor (instead of three).

The idea is that the module contains all the pieces it needs to work. So one soil moisture sensor needs one local circuit -- the whole thing together makes it give you a signal you can use. If you want to add a sensor, you will need to duplicate the local circuit portion as well. And build it this way helps you understand why the sensor works so you can make adjustments.

I like the idea for a super easy interface. A note, I had trouble running the LCD display at the same time as the sensors -- a ton of noise! That's what pushed me to do the charting on the computer. But if you have interest, I say go ahead and start playing. And let me know what you find out.

Hey thanks nickvd for the compliment. Most of the work went into the site, so I'm glad it shows.

And madepablo, it looks like we do have different objectives, but I like your ArduDrop project. I will add a link to in on the GardenBot site (just let me know if this is not okay).

GardenBot is really focused on having simple, step-by-step instructions while being a flexible, extensible modular system so people can try out different setups. And I tried to make sure that charting the data would be easy (since I'm an artist, I like visual data) -- hence the CSV output and web-based charts.