I want to run Embedded MotionApps on a PIC mcu and am using the MPU6050. I'm not sure where to start; the knowledge center and download page aren't too clear...
The knowledge center has links with the following names:
-For Implementation of Embedded MotionApps Software on Atmel AVR UC3 Platform
-For Implementation of Embedded MotionApps Software on your platform
-For Implementation of E-MAP on MSP430
All three links lead to the same download page. In the download page, I see a file for the implementation of Embedded MotionApps on Atmel AVR, but I see no files for any of the other two bullet points above. Furthermore, the file name of the Atmel AVR MotionApps implementation has a "MPU3050" in it (is that compatible with MPU-60x0?).
1) What do I need to get to use Embedded MotionApps on a PIC mcu? In other words, what download corresponds to "For Implementation of Embedded MotionApps Software on your platform"?
2) What is the minimum set of files needed to run Embedded MotionApps?
3) The Embedded MotionApps Release UserGuide v2.0 says its intended to be used alongside the "Embedded MotionApps Platform Reference Manual". Where can I get this document?
thanks!
- Log in to post comments
phpbb Topic ID
14205
Re: Re: MotionApps Download Clarification
E-MAP on MSP430 refers to the MotionFit Wireless SDK download.
Embedded MotionApps on Atmel AVR UC3 refers to the Atmel AVR UC3 download. This can be ported to another platform and is compatible with MPU-6050 for 6 axis sensor fusion.
Embedded MotionApps on your platform refers to the Embedded MotionApps Lite 4.1 which is inside the MotionFit Wireless SDK download. We briefly had it as a stand alone on the download page but took it down since it was already a part of the MotionFit Wireless SDK package which is capable of 9 axis sensor fusion.
We have not validated the porting of Embedded MotionApps Lite 4.1 to other platforms.
We will get back to you with regards to your other questions shortly.
Re: Re: MotionApps Download Clarification
@sectionsbest wrote:
Actually there is no general purpose MotionApps download anywhere.
And your Marketing has gone all around the world telling that "MotionApps 5 is now available".
@sectionsbest wrote:
Do you mean months?
Also in the MotionFit zip there is a RAR, inside this rar there is an AVR project which includes the MotionApps.
But there is no source for the MotionApps!
Only headers.
So how should we do?
Re: Re: MotionApps Download Clarification
@erupter wrote:
Look, we all know there's an icecube's chance in hell of getting anything sensible from InvenSense. As far as I can tell, there is no promise left unbroken by them. What they delivered was bad, and now it's all gone. There is no download for Embedded MotionApps, the wireless SDK has the lure of source but no source.
We all know the bottom line, but InvenSense would simply like to make more promises to you. Come mid-April, something might be here. But, really, who knows?
Re: Re: MotionApps Download Clarification
Hi Erupter and paul_l_curtis
MotionFit SDK is a 9-axis solution in a compiled library format and intended for use with the wireless SDK only. If your intention is to re target it for a difference MCU, then this library is not the right choice for you. A 9-axis solution in source code is out of the scope of this release.
Thank you.
regards
InvenSense Team
Re: Re: MotionApps Download Clarification
All I really want to do for now is to read info from the DMP. I'm currently using the umpl folder from the Atmel AVR project. The Embedded MotionApps user guide claims that only a small part of the source is platform dependent. Although this may be true, I can't get it working on a PIC18 for the following reasons:
1) The code uses non-standard elements such as inline functions, which are not part of ANSI C. My compiler doesn't support inline functions so I can't compile the code without making changes. My compiler also doesn't seem to support __func__.
Another example is the INT_SOURCE enum in mldl.h: it has a comma after the last item , which is detected as a syntax error by my compiler.
2) I'm having a hard time modifying the umpl code to work with my compiler since the code is so convoluted and overly complex. I'm at a point where any change I make just adds to the list of compiler errors.
The concept behind your product is absolutely fantastic. The issue is that getting it to work on other MCUs isn't as straight forward as it should be.
What would be very helpful, not just for me but for other developers as well, is a simplified version of the umpl that is ANSI C and can compile on a variety of platforms. I don't need a complex and feature rich API, I just want to be able to get quaternion input with ease. At the very least, can you please provide example projects for popular MCUs, such as PIC18?
Has anyone else tried to get quaternion output from an MPU-60x0 using a PIC18?
Re: Re: MotionApps Download Clarification
This library can be ported to virtually any MCU. Concerns have been raised about the size and complexity of the library as you have mentioned. Porting it is possible but for reasons on certian MCU's may be difficult. This is a concern we are reviewing internally for potential changes.
Thank you for your input
In regards to umpl that is ANSI C, this is something that we have yet to make available to the public.
Re: Re: MotionApps Download Clarification
Are you guys planning on releasing a simple and lightweight version of the SDK that can easily be ported to other MCUs? If so, when?
Re: Re: MotionApps Download Clarification
There is a planned release of a new simple and lightweight solution, however it is not a version of the SDK. A scheduled release date has not beenn determined.
Re: Re: MotionApps Download Clarification
What I see is that there is low support for hobbyist which is sad to see since I am trying to get my project working with the MPU-6050 :( so far I have found this:
http://www.i2cdevlib.com/devices/mpu6050#source
I'll keep posted when I find something and try to sort out how their API works.
Re: Re: MotionApps Download Clarification
Motion Driver will be posted by the end of this week. Thank you all for your patience, it has been a long time coming.