PASSKEY

[katyon]

 I’ve downloaded     nRF5_SDK_11.0.0_89a8197 and starting with examples from \examples\ble_peripheral\???\pca10040\s132\arm5_no_packs\

 I would like the other device to request a passkey (constant) at pairing (the passkey on my side is constant - no display needed)

After   gap_params_init();I’ve added the following code:

 

{

 static ble_opt_t optS;

   static uint8_t passw[]="123456";           

 optS.gap_opt.passkey.p_passkey=passw;

   err_code =sd_ble_opt_set(BLE_GAP_OPT_PASSKEY, &optS);

}

 

err_code returned :  0  

 

Still the module will pair and communicate without requesting a passkey.

I've tried to find an answer in Q&A . in some answers there was a reference to fields : io_caps,mitm. cant make out what does it mean. 

(these fields belong to structs relevant to services, not pairing)

 

Thanks for any help

   Yona

[Vidar Berg]

Hi,

It sounds like you're doing it correctly.  sys_evt=2 means  NRF_EVT_FLASH_OPERATION_SUCCESS, so it should have worked. Did you make sure to read out the flash content after the NRF_EVT_FLASH_OPERATION_SUCCESS event?  

[katyon]

sorry sorry sorry.

my mistake was somewhere else.

thanks again for your patience.

YONA

[Vidar Berg]

No worries, thanks for letting me know. 

Vidar

[katyon]

Hi again.

new issue:

the guys writing the application on the cell phone are bringing this up.

I might have 1-20 BLE devices in a given location. all of them would be seen by the cellphone application.

each of my BLE devices has a different TYPE (say up to 10 types ).

the TYPE of a given device might change (not very often)  .

the application "would like" to search all devices ,sort only my devices, show a list of them, each with an icon. the icon is the TYPE of the device.

my suggestion was to use appearance.

so every time my TYPE changed- I'll use sd_ble_gap_appearance_set to change it.

their complaint is that in order for them to know all TYPES, they need to READ the appearance characteristic for each of my devices, and that would take them too long.

their suggestion is to have a service that its uuid will be a function of the device's TYPE.

in that way- I'll will have one (an empty) service that its uuid will a function of the TYPE. 

in that way- all that's needed from them is to scan services , sort those that belong to me , and understand (from the uuid ) there TYPES.AVOIDING the need to actually preform  a READ into these services (characteristics).

the thing is- I don't see a function for service delete,characteristic delete, change of uuid.

How can I solve this? what would you do?

thanks

yona

[Vidar Berg]

Hi,

It's not possible to update Services and characteristics on the fly. You need to disable then enable the softdevice and re-initialize the new BLE services. However, you can update your advertisement payload using ble_advdata_set() regardless of what services/characteristics you have. Also, the appearance may be included in the advertisement packet: ble_advdata_t::include_appearance