Yes it does. I have since connected it to a bus pirate, and it shows the two other chips (gyro and magnetometer) responding, but the accelerometer was not. So definitely a faulty part.

I emailed cool components and they said they would send me a replacement.

That is slightly reassuring. I'm using the RBBB (Really Bare-Bones Board) arduino. Here is a photo:



I really appreciate the help btw.

Also, I hooked it up to an oscilloscope. It seems like the address is sent, but the ACK bit isn't set by the ADXL345. Also note that it is 3.3V (vertical division is 2V).

Search for FreeIMU, and also don't make the mistake of connecting it to the arduino without disabling its internal pull-up resistors like I did, or you might fry the chips.

Thanks for the replies. Fabio, what makes you think they aren't dead, given that I connected them to the 5V pull-ups and the datasheet for the ADXL345 says SDA and SCL can't go above Vdd (3.3V) plus a tiny bit? And if they aren't dead, then I can't see why my code didn't work with the internal 5V pull-ups disabled (it seems the schematic shows 3.3V pull-ups built into the sensor board).

Dammit. So basically all I had to do was modify twi.cpp so it didn't use the 5V pull-ups, and it would have been fine, but now the chips are dead?

It seems pretty damn stupid that they'd have a voltage regulator so you can run Vcc off 5V, but then not even tell you that you'll damage it if you connect it straight to the 5V arduino. And whoever wrote twi.cpp deserves some significant blame too... Code shouldn't break hardware by default.

I thought you had to disable those... or do I need to disable the internal ones and add external ones to 3.3V? I don't even have a 3.3V source. :-/ And also if I previously ran it with the internal pull-ups enabled, will that have damaged the devices? If so that is pretty -ing annoying given that there is no warning about this anywhere on sparkfun, or the wire library, and that *really* shouldn't be the default.

Is there any way to bodge a 3.3V source, perhaps using a voltage divider? I'm not concerned about power usage.

Hi, I bought one of these: http://www.sparkfun.com/products/10183
which has an ADXL345 accelerometer that I am trying to communicate with over I2C. I wired it up to an Arduino like this:

+5V -> Vcc
0V -> Gnd
A4 -> SDA
A5 -> SCL

And my code so far is:

Code:

#include <Wire.h>

const int ACCEL_ADDRESS = 0x1D;
const int ACCEL_POWER_CTL = 0x2D;
const int ACCEL_DATAX0 = 0x32;
const int ACCEL_DATAX1 = 0x33;
const int ACCEL_DATAY0 = 0x34;
const int ACCEL_DATAY1 = 0x35;
const int ACCEL_DATAZ0 = 0x36;
const int ACCEL_DATAZ1 = 0x37;

const int MAGNO_ADDRESS = 0x1E;

const int GYRO_ADDRESS = 0x38;

void setup()
{
  Serial.begin(9600);
 
  Serial.println("Starting I2C.");
  Wire.begin();
  Serial.println("I2C started. Starting accelerometer.");
  Wire.beginTransmission(ACCEL_ADDRESS);
  Wire.send(ACCEL_POWER_CTL);
  Wire.send(0x08);
  Wire.endTransmission();
  Serial.println("Accelerometer starter. Looping.");
}


void loop()
{
  // X accel.
  Wire.beginTransmission(ACCEL_ADDRESS);
  Wire.send(ACCEL_POWER_CTL);
  Wire.endTransmission();
  Wire.requestFrom(ACCEL_ADDRESS, 1);
  while (!Wire.available());
  int highx = Wire.receive();
  Wire.beginTransmission(ACCEL_ADDRESS);
  Wire.send(ACCEL_DATAX1);
  Wire.endTransmission();
  Wire.requestFrom(ACCEL_ADDRESS, 1);
  while (!Wire.available());
  int lowx = Wire.receive();
  Serial.println((highx << 8) | lowx);
}

But I don't get any response from the device (it never gets past the first Wire.available() loop). Can anyone say what I am doing wrong? I read some mention of disabling pull-up resistors in twi.cpp which I also tried, but it made no difference, and I've also tried the driver from the FreeIMU library which didn't work either.

This is very annoying, especially as it cost about £60. Have I got a dud board? Any ideas?

Hi,

With the recent release of the Qt Creator source code (GPL) I though it would be awesome if someone (possibly me) could create an arduino version of it.

Don't take this the wrong way, but the text editor in the current IDE is shit. It also doesn't have awesome features like code completion and ... even anti-aliased text!

The Qt Creator IDE in contrast is simple, looks good and doesn't have too many features that would be overkill for arduino.

What do you think?

Ah misread - I was looking at the drawings (which have short pins) rather than the data sheets.

So presumably what I want is one of these:

http://www.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=SAM1125-32-ND

and select the SSA-132-W-T item number (and then I can cut the 32 pin up into four 8 pin headers).

£2 seems like a lot... Guess you don't need them much...

Thanks for the replies. The one I want is the one on adafruit, but I don't live in America and really don't feel like paying international shipping (&waiting) for a $2 item!

Anyone know where I can get them in the UK? Tried searching digikey again but it doesn't have the leg height as a field, which makes it impossible to search...

This is the image:



By the way, not only is this a stupid way of preventing spam, but the 'post' and 'preview' buttons become broken after you click them. This is really annoying because you do something like:

1. Write message
2. Be told you can't have links.
3. Go back to edit the post.
4. Try to click post - it doesn't work anymore. You now have to copy the text and go to the 'Create new topic' again.

Grr stupid forum software.

Hi, I'm trying to make a veroboard shield and need some of these pin things:

(See the next message, I can't post a link annoyingly.)

I bought some like that from maplin, but they are only just long enough, and I had to file down the solder on the bottom of the board for it to work at all. So, can I ask you fine folk:

1. What are those things called?
2. Could you perhaps provide a link to them on digikey?
3. Can you get the same thing but with sockets on the top so I can stack shields? What are those called and where do I get them on digikey? (The digikey website is definitely not for beginners!)

Many thanks,

Tim

PS: My first veroboard thing was successful - an optoisolated camera controller, but I accidently burnt out one of the optoisolators because the bottom of the veroboard contacted the +5V on the ICSP header! D'oh! It would be awesome if there are pins that raise the board slightly so it doesn't short to the ICSP pins...

Aha! It works with version 0011! :-) Is there a bug tracker somewhere?

It seems to randomly cut some of the timing short... It doesn't seem to be deterministic. You probably get a similar effect by replacing the

delay(3000)'s with

delay(rand() % 8 ? 3000 : 200); // Assuming rand() works like libc's.

I'm going to try manually making the PWM signal to see if that works. I'll hook it up to a scope too to see if that provides any more insight.

Oh and I've switched to using the Servo library that comes with the arduino IDE. Doesn't seem to have changed anything though.