FeatureAcceleration do not respond when FeatureMemsSensorFusion is enabled

[janakact]

When both FeatureAcceleration and FeatureMemsSensorFusion is enabled only MemsSensor 's listener get responses .

        mAccelerometer = node.getFeature(FeatureAcceleration.class);
        mGyroscope = node.getFeature(FeatureGyroscope.class);
        mSensorFusion = node.getFeature(FeatureMemsSensorFusion.class);

once I removed the Fusion Feature the Accelerometer and Gyroscope listeners get data. Otherwise it doesn't. Does Sensor Fusion disable other two features?

[GiovanniVisentiniST]

Hi Janakact the SDK permit you to enable acceleration and sensor fusion at the same time. It could be a BLE a bandwidth problem, are you sending the notification with an high frequency? You should see some error in the board console when the BLE connection is congested. Could you use the SensorFusionCompact? in this way 3 quaternions at the time are sent, reducing the BLE pressure.. I'm trying the example app with the FP-SNS-MOTENV1 v3 and I don't have problems.

Are you using the SensiBLE? in that case happen also to me. Using the example app. But it seams an fw problem/decision, becsuse looking to the log cat I see that the app enables correctly the characteristics, and,as you can see, it doesn't disable it, but the acceleration data arrive only after the sensorfusion is disabled:

//click sensor fusion line -> enable sensor fusion
08-22 15:21:53.840 15591-15591/com.st.BlueSTSDK.Example D/BluetoothGatt: setCharacteristicNotification() - uuid: 00000080-0001-11e1-ac36-0002a5d5c51b enable: true
//click accelerometer line -> enable accelerometer (not receiving acc data)
08-22 15:22:24.550 15591-15591/com.st.BlueSTSDK.Example D/BluetoothGatt: setCharacteristicNotification() - uuid: 00e00000-0001-11e1-ac36-0002a5d5c51b enable: true
//click sensor fusion line -> disable sensor fusion (start receving acc data)
08-22 15:22:39.200 15591-15591/com.st.BlueSTSDK.Example D/BluetoothGatt: setCharacteristicNotification() - uuid: 00000080-0001-11e1-ac36-0002a5d5c51b enable: false

in that case I can't do anything since we don't develop the SensiBLE fw.

Best Regards Giovanni