My original blog post offering a bounty on software for the ArduIMU v3 to make it into a very good standalone camera gimbal stabilizer attracted alot of criticism and at the same time alot more support. There are many people who have joined my cause, and pledged to either match my bounty or contribute towards the bounty. So many pledges that it has become hard to track. One member suggested using Kickstarter. However as a non-US resident I was not able to create a project on Kickstarter so one has been created on IndieGoGo.
http://www.indiegogo.com/ArduIMU-Camera-Gimbal-Stabilizer?a=489994
Don't forget that whilst the $10 contribution is appreciated, and you contribute as much as you like, matching my $100 bounty is even more appreciated. And for $225 I'll get a ArduIMU and solder the connectors and flash the firmware for you.
[EDIT: The 30 March deadline has now been extended until 11 May or until the bounty is claimed, which ever comes first.
It looks like this is getting pretty big with a number of contenders and backers, ie. more than just my $100 reward. Whilst my offer for a $100 reward plus bonus still stands for the FIRST person to deliver code that meets the specification; I would like to propose that the contributions/backers/funders on IndieGoGo vote at the end of the project (11 May) who should receive the funds raise on IndieGoGo (less the 9% fee that IndieGoGo charge).
So essentially there will be the $100 plus bonuses from me for the FIRST app, and the IndieGoGo pool for the BEST app.
]
Comments
Andreas
When changing to BITS_FS_250DPS was that a Drifting issue that you found?
To anyone testing this. After reading anther post about imu 3 v1.9 giving bad data, it hit me. I have a very early version of the board. In fact it didn't have a bootloader installed.
I have updated my gimbal controler to auto detect the hard ware version from the mpu6000 and set the accelerometer scaling. I got it from Arduplane 2.4 and ported it to the V1.9 gimbal controller.
Get the latest version here. I should have known of this problem, but both my board are version C the older ones. It will now switch to C or D automatically on start up.
OK Torg heres a picture. I guess I can make one. I was hoping you would do it for me. I all ready did the hard part after all :)
@ Torq, Don't use those power connections. Thats the input to the onboard regulator, and you can't use that to power servos. Since you all ready need a 5 BEC you can use that to power the board. The power connections to the servos you need to do your self with perf board and a row of two or three pin connectors. Like this.
In the meantime I also tried the code version from Michael Oborne and it worked out of the box for me. Though I got hyroglyphs in the terminal window the stabilization itself worked very well. From what I saw some of the code might be from here: https://code.google.com/p/gentlenav/source/browse/branches/MatrixPi...
Having a 2g accel calibration scale is very good for what I want but does anybody know the correct calibration registers for a gyro scale of 250 deg/sec. The ones used in the code are for 2000 deg/sec:
void MPU6000_set_gyro_calibration()
{
byte regs[4];
regs[0]=0x4C;
regs[1]=0xCD;
regs[2]=0x6C;
MPU6000_set_mpu_memory(0x03, 0x7B, 0x03, regs); //FCFG_1 inv_set_gyro_calibration
regs[0]=0x36;
regs[1]=0x56;
regs[2]=0x76;
MPU6000_set_mpu_memory(0x03, 0xAB, 0x03, regs); //FCFG_3 inv_set_gyro_calibration
regs[0]=0x02;
regs[1]=0xCB;
regs[2]=0x47;
regs[3]=0xA2;
MPU6000_set_mpu_memory(0x00, 0x68, 0x04, regs); //D_0_104 inv_set_gyro_calibration
regs[0]=0x00;
regs[1]=0x05;
regs[2]=0x8B;
regs[3]=0xC1;
MPU6000_set_mpu_memory(0x02, 0x18, 0x04, regs); //D_0_24 inv_set_gyro_calibration
}
Simply trying to change MPU6000_SPI_write(MPUREG_GYRO_CONFIG,BITS_FS_2000DPS); to BITS_FS_250DPS compiles but leads to a trifting servo output...
Thanks,
Andreas
To any potential testers!!!!!!!!!!!!!!! Check the wiki again. I had the pitch and poll pins revesed. Thanks to Torg's graphic it has been sorted out. Go by the wiki.
Torg, OMG the pitch and roll are reversed. I followed your graphic instead of my notes, just to check. You drawing is right to my wrong wiki. Many thanks, reverse pitch and roll on yours and it will be correct. I will do the same on the wiki. And also put the bec 5V to the GND and 5V lines on the top side of the board. I am not using the regulator, and especially not on the servos. I would like to put it in the wiki.
To all. If any one tries it, please comment here!
Going to fix the wiki now, thanks Torg.
Oh Torg>>>>>>
PPM in and PPM out are only used if you change the user parameters. The default is normal RC channels. Just don't use them if you don't know what it is. PPM is 9 channels of RC on one line, like it goes to the radio. It is 'Pulse Position Modulation'
Greg can you please take a look at your DIYDRONES inbox ?
New gimbal code for the imu3 here. I have a wiki on how to set servo limits. It's easy. It takes rc input(ppm/pwm) and has 3 pwm outputs. It can output ppm too as it was born from my head tracker that I wrote for this board. Try the cli. Set the ardu serial monitor to 38400 and type "set up".
btw, the pic you uploaded of teh back of the arduimu is correct.
rc inputs are on a0 to a3, so there is room for "switch" expansion
-
1
-
2
-
3
-
4
of 4 Next