I have some trouble to get thingy's motion sensor.

[wanna]

Hi.

I applied https://github.com/crfosse/Thingy-52-to-nRF52xx project to get thing'y motion sensor by nRF52840 DK.

When I init DK, it discovered only 7 UUID so euler, rotation matrix, heading, gravity service couldn't use.

Also Quaternion, step counter, raw data service had same handle.

How can I get to thingy's motion data?

Thank you for reading.

uint32_t ble_thingy_tms_c_init(ble_thingy_tms_c_t * p_ble_thingy_tms_c, ble_thingy_tms_c_init_t * p_ble_thingy_tms_c_init)
{
    uint32_t      err_code;
    ble_uuid_t    thingy_tms_uuid;
    ble_uuid128_t thingy_tms_base_uuid = {THINGY_UUID_BASE};

    VERIFY_PARAM_NOT_NULL(p_ble_thingy_tms_c);
    VERIFY_PARAM_NOT_NULL(p_ble_thingy_tms_c_init);
    VERIFY_PARAM_NOT_NULL(p_ble_thingy_tms_c_init->evt_handler);
    
    
    p_ble_thingy_tms_c->peer_thingy_tms_db.euler_cccd_handle    = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.euler_handle         = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.heading_cccd_handle  = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.heading_handle       = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.orient_cccd_handle   = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.orient_handle        = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.pedometer_cccd_handle = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.pedometer_handle     = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.quat_cccd_handle     = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.quat_handle          = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.raw_cccd_handle      = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.raw_handle           = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.rot_cccd_hanlde      = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.rot_hanlde           = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.tap_cccd_handle      = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.tap_handle           = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.gravity_cccd_handle  = BLE_GATT_HANDLE_INVALID;
    p_ble_thingy_tms_c->peer_thingy_tms_db.gravity_handle       = BLE_GATT_HANDLE_INVALID;



    p_ble_thingy_tms_c->conn_handle                    = BLE_CONN_HANDLE_INVALID;
    p_ble_thingy_tms_c->evt_handler                    = p_ble_thingy_tms_c_init->evt_handler;
    
    
    err_code = sd_ble_uuid_vs_add(&thingy_tms_base_uuid, &p_ble_thingy_tms_c->uuid_type);
    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }
    VERIFY_SUCCESS(err_code);

    thingy_tms_uuid.type = p_ble_thingy_tms_c->uuid_type;
    thingy_tms_uuid.uuid = THINGY_TMS_UUID_SERVICE;

    return ble_db_discovery_evt_register(&thingy_tms_uuid);
}

[Bjørn Kvaale]

Sorry for the delayed response. Are you getting any compile errors? Have you tried seeing the log output via UART using Tera Term for example? Have you updated the UUIDs in ble_tes_c.h for the Thingy motion services instead of the services that are handled in the example?

I would also consider reading & trying this custom service tutorial so that you understand how custom services are added to the softdevice. Last but not least, this case could be useful for understanding error handling in our SDK.

[wanna]

I have no compile errors and i updated the motion service uuid on header file. But It still discovered only 6 Services and handle is not delivered for event. What can I have to do? Is it different  from the getting environment data?

[Bjørn Kvaale]

Did you enable logging on the 52840 dev kit? Did you get the github example working with the temperature service on the 52840 before you started updating the code? It should be the same thing to get motion data to the dev kit as with the temperature service. Also, could you please update your question here to include the information from this devzone case: https://devzone.nordicsemi.com/f/nordic-q-a/37344/is-getting-motion-data-different-from-environment-data

Then, we can keep this conversation on this case. Thanks!

[wanna]

Hi, Bjørn.

I did enable logging on dev kit, and I got temperature data before updating.

So I followed the example.Thingy sending data successfully.

Is there any wrong code to init? https://devzone.nordicsemi.com/f/nordic-q-a/37344/is-getting-motion-data-different-from-environment-data

I think It is right to init motion service. But It still discover 6 Service..

After init, handle values were not discovered.

Thank you for your help.

[Bjørn Kvaale]

Sorry for the delayed response. Transferring motion service data over BLE should be very similar to transferring temperature data. 

Referring to the code posted here: https://devzone.nordicsemi.com/f/nordic-q-a/37344/is-getting-motion-data-different-from-environment-data

It looks like you did everything correctly from comparing your code to the code posted on Github. 

You said before that 7 UUIDs were discovered, but in your last comment you mention 6 UUIDs. Did you change something in the code? How many UUIDs do you want to discover?

Some small syntax tips: I would change all of the TES in THINGY_TES_UUID_* to TMS (i.e. THINGY_UUID_TMS_EULER_CHAR). By this, I mean giving the UUID values the same name as given in ble_tms.c in the Thingy SDK.

I would also recommend changing thingy_tes_init() to thingy_tms_init() because you are initializing the Thingy Motion Service, not the Thingy Environment Service.