Ya, I got it working. CLI/PWM in/out/DCM.ect... ... ...  I have been busy with GIT tortoise////turtle or what ever. I will finish it up and test, soon.

Hope to see the servo response time. 

I'm glad to hear there's some process on this. I'm still waiting on my ArduIMU+ V3 to arrive so I can test as well. I'll post when I get it and do some testing myself.

Cliff, the issue is you have to choose the right board. You have it set for the older APM board which has an mega 1280 but the IMU V3 board is a atmega 328P.

"warning- not a 1280

 

Cliff, sorry my bad,

Mission planner is throwing an error, the command line states a warning something along the lines of "warning- not a 1280"

You cannot load that code to an IMU V3 via mission planner!! Depending on the file format, you need to be using either Arduino if it's a PDE file or if it's a HEX, then avrdude (same thing mission planner is using but you must specify the chip type and the GUI of mission planner won't let you do that. I use AVR-Burn-O-Mat as agui for avrdude and it makes you life much easier.

Vernon,

Thanks very much for the help. However, I am new to AVR and the hex files, so working my way through it. I have winAVR and AVR8 burno matic installed, and now not quite sure about writing the gimbal.cpp.hex file as Flash or Eeprom? I am probably out of my league here, but still trying to give it a try, and judging by several other posts I am not the only one running into problems testing this out. Thanks again for any help.

First, you must configure the AVR-Burn-O-Mat to point to the location of acrdude and the config file.

Then ensure you have the right serial port and further the correct programmer chosen "STK500 V2"

Then you must close and reopen Burn-O-Mat.

Then at the top choose the right chip atemega328P.

Then you can select the hex file in "Flash"

Then hit "write"

You may have to hit the reset button on the IMU V3 right after you hit "write"

typo avrdude.exe  and avrdude.conf