Sitting down to get my 2.0 out and 2.5 in :-)
I'm trying to sort out where the Optical flow sensor gets landed now? I have been looking at the Eagle files trying to get a grip, but there are new components in the chain and I just can't get my head around where I pull MISO, MOSI, SCLK, ect...
If someone could help me out I'd be grateful.
I followed the suggestion you have given and also I read the pages you've suggested. Now my optical floe sensor is working good and I'm able to grab the images using python test script. I need one help that can you please tell me what are the PID values for OF_LOITER? I'm using APM2.5 with arducopter 2.9.1b firmware along with 3drobotics optical flow sensors for my f450 quad-copter.
I tried to compile the code from master, but even this one also not compiling on my PC, can you please tell me about the check list to compile the code given in the master. Actually its showing error at Base_Bin, but after removing Base it is not showing any error at that particular line but after its giving an error at "flowSensor.print_pixel_data();" so please help me to compile this code successfully.
Thanks in Advance.
Thanks in advance.
hi who can you send me the APM 2.5 hardware. firstname.lastname@example.org
I cann't open the file withe eagle software: http://stuff.storediydrones.com/Main_V25.zip
Problem solved for APM2.5 OPTICAL FLOW wiring
So I got it working although it needs more testing and vetting by some of the others on the dev + testing team before it gets into a release. My guess is it won't make 2.7.4 which will probably be out in a week but the one after that.
I've updated the wiki as well with the new instructions. It's easier than with the APM2 although switching the little MISOLVL jumper from 5v to 3.3v is a bit tricky.
The software changes were a bit tricky..there was a small bug in the restore/backup spi settings (we use different settings for different devices so we need to constantly save/restore settings depending on what device is talking at the time...on top of that I needed to make it auto-detect which SPI bus the sensor was on. So now it first tries the regular SPI bus, then it tries the secondary one.
If you're confortable with git, you can find it in the rmackay999-wip2 clone in the optflow25 branch.
Would you mind give me a copy of EAGLE Files of APM2.5
The bummer IMHO, is that there has been no response at all good, bad, or otherwise from 3DR at this point...
Here is a screen snippet of my log of the OF sensor just doing some hovering a round the front of the house... Haven't tried much to actually use the OF_Loiter or adjust the PID's, but figured one of you may know whether or not these are good numbers?
By all means try the jumper :-)
(posting in dual threads at this point, here and the Wiki...)
I did try landing the OF on the 3.3v side of the level shifter on the MPU-6000 side. It's a no go, as soon as you touch the SCLK line it all goes haywire. Just look at the horizon in the MP and watch what happens when you touch the SCLK with a test lead (not even hooked to the meter), the gyro drifts off and flips the horizon :-/
But, please look into it as I am certainly no expert in microprocessors or SPI :-)
Hi, I'm having the same problem. It looks like on the APM1 that you used the 2560's ISP headers. But I read that on the APM2 there was some conflict with using those pins so you had to connect to the pins on the GPS shield. (Those connected to PJ0-2)
I opened up Eagle too, to see where those pins go on the APM2.5 and they are entirely too small to solder anything to. I guess that means we need to connect it somewhere else. I'm hoping that the conflict that existed on the APM2 has been resolved and we can just hook into the ISP pins again. But then, I thought the 2 and the 2.5 were software identical, maybe that's not the case.
Anyway, I really need to figure this out too!