Unable to download Embedded MotionApps Lite v4.1

By alvaro_canivell , 17 February 2012

Sorry guys,

I'm trying to download Embedded MotionApps Lite v4.1 but each time e click the download icon I get forwarded to the login page. I logon with my "developer corners" account, I go to the download section and again when I click the download icon I get forwarded back to the login page?

What's wrong?
Do I have to have a different kind of privileges?

Thanks for any suggestion.
Paolo.

alvaro_canivell

14 years 1 month ago

Thanks, now it is working.

I have seen that there is no more "Embedded MotionApps Lite v4.1" download.
Why?

At the moment I'm experimenting with SDK board, but in future I plan to develop custom applications using MPU-9150, do you plan to release "Embedded MotionApps Lite v4.1" in near future?

Thanks.
Paolo.

phpbb Post ID
19239

jian_yuan

14 years 1 month ago

I have downloaded the "MotionFit SDK v 4.1" package but most of the Embedded MotionApps source code appears to be missing. I only have several header files which belong to Embedded MotionApps but except for main.c there are no other c-files.

phpbb Post ID
19242

marcello_rubino2

14 years ago

Are you seriously saying that your highly publicized MotionApps which is arguably the biggest reason for getting your platform is not available anymore???
What's the point of getting an mpu60x0 without that library???

phpbb Post ID
19248

guy_mcilroy

14 years ago

Are you referring to MotionApps 5.0 that you mentioned in another thread as the highly publicized library that is not available anymore?

Embedded MotionApps Lite 4.1 is and has always been available on the Developers Corner.

phpbb Post ID
19251

marcello_rubino2

14 years ago

@sectionsbest wrote:

Are you referring to MotionApps 5.0 that you mentioned in another thread as the highly publicized library that is not available anymore?

Embedded MotionApps Lite 4.1 is and has always been available on the Developers Corner.


There are two packages available in the devcorner download section.
One is the MotionFit Wireless SDK which doesn't have any source code related to the MotionApps as you surely know. The real library is precompiled for the TI430, that means nobody can do anything with it unless using the TI430.

The other package is the AVR UC3 SDK which has the full source code... of version 2!
And that has no 9DOF fusion as everybody on this forum has discovered by himself. Because nobody can obtain neighter the correct information from Invensense on how to program the DMP to get 9DOF fusion, and neighter the AK source from AK itself.

Also I may point out the following phrase extracted from V2 source file
compass_supervisor_lite_callbacks.c

/* Lite Fusion Compass Supervisor Delegates.
* Take compass_supervisor's compass_obj_t, and populate the
* inv_obj->mag data structure with the results.
* (Admittedly, lite_fusion is a little bit of a misnomer.)
*/


And the fact that the source require
compass_debug.h
compass_legacy.h

which are not included.

So you tell me: where is a FUNCTIONAL - that's to say able to provide 9DOF fusion - software package for the 6050 EVB you sell?


What is the point of marketing when what is marketed is not available?
Lure people into buying (and thus spending money) thing they'd have otherwise disregarded.
phpbb Post ID
19254

rrsgdtac

14 years ago

Dear Erupter,

Embedded MotionApps Lite (MotionFitSDK) is intended to be used with the wireless SDK board that will be available from InvenSense webstore shortly. Like you point out it can also be used with MSP430.

The Embedded MotionApps 2.0 is a 6-axis solution only. Making it work for 9-axis will require the user to get the akm library files and rights directly from AKM. InvenSense does not have the resources to support AKM library and hence we consciously decided to keep it 6-axis only.

Please let me know if this needs more clarification.

Thank you.

regards,
InvenSense team

phpbb Post ID
19257

marcello_rubino2

14 years ago

@tech_marketing wrote:

Dear Erupter,

Like you point out it can also be used with MSP430.

The Embedded MotionApps 2.0 is a 6-axis solution only.

Please let me know if this needs more clarification.

Thank you.

regards,
InvenSense team


1st) it's not "also with" it's "only with" as you precompiled the library. Thus any attempt at using the same package with other devices will fail.

2nd) Nice that you aknowledge that, now as a customer I want to know: how do I get 9-axis sensor fusion with your chip? I want the answer to this question. I'm developing a product and being able to fuse means putting your chip onboard or not. I want to know the steps beyond buying and soldering the chip.
The mpu6000 is advertised as a 9-dof fusion. How do I get it?

Regards
disheartened customer
phpbb Post ID
19260

rrsgdtac

14 years ago

Dear Erupter,

One way to use the Embedded MotionApps 2.0 code for 9-axis is by taking the 6-axis sensor fusion data from the MPU and performing the compass data integration by writing required code for compass data integration on the MCU. Does this approach work for you ?

Agree that the 4.1 library is targeted for use with MSP430 MCU only. I was merely trying to say is that you can either use our wireless SDK board or any other MSP430 MCU based EVB.


Thank you.

cheers,
regards,
InvenSense Team

phpbb Post ID
19263

marcello_rubino2

14 years ago

@tech_marketing wrote:

Dear Erupter,

One way to use the Embedded MotionApps 2.0 code for 9-axis is by taking the 6-axis sensor fusion data from the MPU and performing the compass data integration by writing required code for compass data integration on the MCU. Does this approach work for you ?


It could work if I could find detailed instructions about the required code.
Can you share some details about this?

Regards
phpbb Post ID
19266

marcello_rubino2

14 years ago

@erupter wrote:

@tech_marketing wrote:
Dear Erupter,

One way to use the Embedded MotionApps 2.0 code for 9-axis is by taking the 6-axis sensor fusion data from the MPU and performing the compass data integration by writing required code for compass data integration on the MCU. Does this approach work for you ?


It could work if I could find detailed instructions about the required code.
Can you share some details about this?

Regards



After a week without answer I think I can ask for one?
phpbb Post ID
19269

hernan_angel

14 years ago

@erupter wrote:

@erupter wrote:
@tech_marketing wrote:
Dear Erupter,

One way to use the Embedded MotionApps 2.0 code for 9-axis is by taking the 6-axis sensor fusion data from the MPU and performing the compass data integration by writing required code for compass data integration on the MCU. Does this approach work for you ?


It could work if I could find detailed instructions about the required code.
Can you share some details about this?

Regards


After a week without answer I think I can ask for one?


After a week, you know that you won't get an answer. I've been trying for a year--what makes you so special that you think you can get one is just a week? :-)
phpbb Post ID
19272

rrsgdtac

14 years ago

Dear Erupter, Paul_I_curtis:

I was trying to suggest that if you can use the 2.0 release off the web, which puts out 6-axis calibrated sensor fusion data. Tie the compass to the main MCU (of your choice) and do the integration yourself. The register spec for the MPU-6050 is available on the web (https://invensense.tdk.com/mems/gyro/documents/RM-MPU-6000A.pdf) that will give you the details of configuring the MPU as needed.

The software that performs 9-axis sensor fusion (based of the 2.0 code base) is not available for public release since it would require developers getting both the library and support directly from AKM. Since we dont have the bandwidth to support AKM library we have decided not to make this available as a general release.

In an effort to enable system developers access to 9-axis sensor fusion we released the MotionFit SDK with our own compass calibration library. Since it has IP from InvenSense we decided to release it as a library for MSP430 only. The MSP430 MCU is still pretty low cost and we see it affordable for the system developers. Can you share which MCU you are targeting for your design ?

As you can see we are continuing to make progress in supporting developers. In the future we may find ways to make it more accessible but we are not a point where we can share specific schedules on when such a solution be available.

Thank you
regards
InvenSense team

phpbb Post ID
19275

alvaro_canivell

14 years ago

Dear InvenSense,

I agree with you if we are talking about protecting IP.
It is also true that this must not be a limitation and it must not force developer to use MSP430. Changing the CPU in project is a major task to accomplish.

I'm developing for PIC32MX340F512H, could you please provide me - and all who is using this processor - a precompiled library for 9-DOF data fusion?

Sure you can. ;)
Thanks.
Paolo.

phpbb Post ID
19278

marcello_rubino2

14 years ago

I'm targeting a PIC32 too, although different from Paolo: 695F512H.
It could be worth looking into if a library could be precompiled in a way that makes it compatible with a whole range of MCUs instead of just a specific model.
That would be useful regardless of the make and model of MCU we're talking about.

So in essence you don't have the resources to support a certain kind of application. Still it would be nice if you could provide the means without explicit support. Or support in best-effort mode.
Every manufacturer offers something that it doesn't fully support, or for which a full customer support chain is not provided. Still it is offered because it gives higher value to the product being sold.

And yet the marketing Invensense pushes on for the MPU6000 still targets its 9-dof capability. Also the dev board being sold by invensense has an AKM magnetometer on it.

So I think there is a problem here: you market a product with some features, you go as far as *selling* (thus making money out of a promise of a range of features and capabilities) a dev-board that theoretically offers those features, but then refuse to provide the software to use those features.
I'm not well educated in the US Law system, but I suppose there could be the grounds for a fraud case here.

What does a small company have to do to get the advertised features?
Sign NDAs? Some other kind of contract? Pay some kind of special support?
What do you ask of us to get what you advertise?

I strongly underline the fact that you are still marketing your own product as capable of doing something you are later actively refusing to provide in the form of information and software needed. Thus you are actively and consciously negating a feature that is part of the product. Moreover it is and remains in the capability of the product as we have acquired and payed it, you are just refraining from giving the necessary details (information and/or software) to get access to it. Isn't this a breach of contract between who buys your product and the manufacturer?

phpbb Post ID
19281

rrsgdtac

14 years ago

We never advertised a 9dof library that can be ported to any MCU. If you bought the chips directly through InvenSense and cannot use our chip the way you intended to use them, please follow the RMA (Return Merchandise Authorization) process by contacting sales@ invensense.com

Thank you.
InvenSense Team

phpbb Post ID
19284

hernan_angel

13 years 12 months ago

@tech_marketing wrote:

We never advertised a 9dof library that can be ported to any MCU. If you bought the chips directly through InvenSense and cannot use our chip the way you intended to use them, please follow the RMA (Return Merchandise Authorization) process by contacting sales@ invensense.com

Thank you.
InvenSense Team


You advertised Embedded MotionApps in a press release:

https://invensense.tdk.com/mems/gyro/documents/articles/050211-INVENSENSE-INTRODUCES-THE-WORLDS-FIRST-MOTIONAPPS-PLATFORM-FOR-EMBEDDED-SYSTEM-DEVELOPERS.html

This says the 6DOF software is optimized for 8-bit systems. Like the AVR, for instance. So, is this true or false? Is it available?

From your own advertising:

"The devices combine a 3-axis gyroscope and a 3-axis accelerometer on the same silicon die together with an onboard Digital Motion Processorâ„¢ (DMPâ„¢) capable of processing complex 9-axis MotionFusion algorithms.
The parts’ integrated 9-axis MotionFusion algorithms access external magnetometers or other sensors through an auxiliary master I²C bus, allowing the devices to gather a full set of sensor data without intervention from the system processor"

So, if the fusion algorithms are all internal, then there's no external code necessary. But this isn't true.

What I take this to mean is that there isn't really anything that will do what most customers want to do: have a single I2C device that knows how to talk to a magnetometer (in the case of the MPU-6000 series) and put out quaternions over I2C. It needs a bunch of intelligence on the host, a bunch of software on the host, and a whole load of time to make it all work.

If InvenSense had made clear their expectations from the start, then perhaps many of us would not feel so let down. What has been delivered does not match what is marketed, as far as I can tell. Certainly not for us who are purchasing devices in the 200-unit quantities, anyway.

I have now coded my own software to do 9DOF fusion without using the DMP, and I at least have control of my own software and can port it. Fixed-point quaternions are great; the code runs like a train and the MPU-6050 is used as a dumb collection device only. Oh well....
phpbb Post ID
19287

rrsgdtac

13 years 12 months ago

Dear Erupter,

The part of the press release is referring to the secondary I2C bus on the MPU that would allow interfacing to an external magnetometer. So the raw data processing is offloaded, and sensor fusion can be run on the DMP, so in that sense it offloads some processing from the MCU. But you are right that the calibration algorithms run on the MCU.

We do have a library for 8-bit micros like the 8051 and Atmega MCUs. Since we have very minimal resources to support it and hence been released to select customers only.

Thank you
Cheers,
InvenSense Team.

phpbb Post ID
19290
phpbb Topic ID
14148