BLE_RSCS and BLE_RSCS client

[estatiokvit]

Hello, is it possible to receive and transmit RSCS characteristic on only one nRF51 DK ? If merging rscs_example and rscs_c_example into 1 project is a good idea ?

[Joakim Jakobsen]

Hi.

is it possible to receive and transmit RSCS characteristic on only one nRF51 DK ?

I assume you aren't trying to receive a packet on the same board as you used to send it?

Could you elaborate a little bit on what you are trying to acheive here?

Do you want an application that acts like a relay, being able to receive values and then pass the on, i.e acting as both a central and a periperal?

I suggest that you take a look at the Experimental: BLE Relay Example:
"This example application demonstrates a simple relay that receives values and passes them on. The application combines a collector part on one end and a sensor part on the other to show how the SoftDevice can be used to make a device simultaneously function as central and peripheral device."

Is that something similar to what you are looking for?

Best regards,
Joakim

[estatiokvit]

I want to have 2 way communication (just like nus and nus_c example) for hrs or rscs service is it possible or maybe peripheral cannot receive anything ?

[estatiokvit]

Yes, but in my understanding this example is more like gateway.

It collects from peripheral and passes to client.

PERIPH ---> RELAY ---> CLIENT

I want to collect from peripheral and pass response to the same peripheral from which I received data.

PERIPH <---> CLIENT

Is it possible ?

[Joakim Jakobsen]

Hi again.

Sorry for the confusion here, but I'm still not sure what you are actually trying to acheive here.

What is the reason that you would like to send something from the peripheral to the central, and then send it back to the peripheral?

Best regards

[Joakim Jakobsen]

I think I may understand what you are trying to acheive here..

estatiokvit said:

I want to have 2 way communication (just like nus and nus_c example)

You don't want to send the same packet as the rscs peripheral sent to the client back to the peripheral again?
You want the central to send something else back to the peripheral, unrelated to rscs?

If so, I suggest looking at the ble_app_uart examples. Merging them with the rscs examples, and use NUS to send whatever else you want to send from the central to the peripheral.
Is that what you are looking for?

Best regards,
Joakim

[estatiokvit]

Thanks for answer again. So to be more precise:

PERIPH <---> CLIENT

1. PERIPH advertise RSCS

2. CLIENT search for RSCS and connect to PERIPH  to receive data

3. On user action CLIENT has to send configuration data to the PERIPH 

4. PERIPH should receive the configuration data from CLIENT and store them in non-volatile memory

1 and 2 is currently done and works fine. I'm wondering how to deal with 3 and 4.

[Joakim Jakobsen]

Thanks for clearing that up. Sorry about the confusion.
Did you look at my last answer?

You shouldn't use only the RSCS to do this.
However, if you implement something like NUS aswell, you can send some other data from your client to the peripheral.

You can read more about rscs here:
Running Speed and Cadence Service / Running Speed and Cadence Service Client

Best regards,
Joakim