I'm a newb to DIY Drones but have been an Arduino tinkerer for a while. I received my new V3 in the mail yesterday; soldered it up and loaded the code with no issues.
Upon first power up it returned a solid red light (sensors saturated). I booted the windows test program and although the IMU does return information, it appears that the accelerometers are way out of wack. I reloaded the code multiple times... altered the scalars of the accelerometer data by orders of magnatude... can't get that damn light to turn off!
Has anyone else had this problem?
I got the same, I received my V3 board early this week and didn't get a chance on getting this red led out...
here's my latest investigation :
in the arduimu.pde file, it is stated that the gravity value of the mpu is set to 4096 to match the 4g range
But sensitivity scale factor for AFS_SEL=1 is 8192 and not 4096. would it be an error? could it be that that makes the sensor saturated?
Any help would be much appreciated as I wouldn't get stuck too long on this glitch
Actually, it is a range of + and - 4g for a full scale of 8192.
0g is usually set a half scale ( at 4096 ) so for a 1g value in the Z vector the output should be
4096 / 4 = 1024 for the normal gravity
4096 (0g) + 1024 (normal gravity) = 5120
does this make any sens at all?
In addition to that, the voltage reference for the AD converter must be set between 2.375V and 3.46V.
What is the voltage supply to the mpu6000 when we power the board through the FTDI cable?
Hi Chris! Maybe a little bit off topic, but is the unmodified 1.9 code not giving correct measurements? Does it matter if I power it on the FTDI-pins or not?
I uploaded the 1.9 code "as is" and it gave the red led "on" meaning tha the gyro were saturated. As I didn't connect the Arduimu to anything and I powerd it only through the FTDI cable, I don't know if this setup is really adapted to give correct mesurement.
I sent a message to Jordi Muños to tell him that the wiki about the Arduimu project was outdated
The new board has quite a few new feature not mentioned in these pages but I didn't get an answer yet.
Hope that it'll help
I had the same problem and I'm finally getting closer to correct readings. Since I'm testing the board by itself with an FTDI cable, I disable this parameter in the "user parameter" of the arduimu.pde file that I openened with Arduino 0023
"#define SPEEDFILT 2" changed to "#define SPEEDFILT 0"
It cancels the speed filter for yaw drift and when I set it to "0" the red led stays OUT.
The readings of the accelerometer still seem a bit off and I keep looking but at least this red led is OUT!!
I have the same problem, any updates on how to troubleshoot this?
I wound up returning my IMU to 3drobotics and they have fixed it. I should be receiving it in the mail tomorrow. They did find a problem with my accelerometers, however they did also tell me that they've seen some firmware work properly while the red light is on anyway.
Once I get my repaired board working I'll let you know!
Hi kyle. I got the V3 by mail last week. I'm totally new to IMUs. I don't know how to get started. I believe the first step after unboxing is to solder the 6 pin header on to the FTDI slots right? Could you post pictures of your assembly please?
i cant tell but is both the red and blue light on or just the blue light on the v3