Hi,
S112/S113 is currently the only supported SoftDevice on nRF52805 and doesn't support Central (Only Peripheral). Is there a plan to enable S132, SoftDevice Central are suited for end products.? If yes by when can we expect?
Regards,
Ramki
Hi,
S112/S113 is currently the only supported SoftDevice on nRF52805 and doesn't support Central (Only Peripheral). Is there a plan to enable S132, SoftDevice Central are suited for end products.? If yes by when can we expect?
Regards,
Ramki
the S40 soft device is 150kB in size so it would fit into 192kB flash memory of nRF52805, even though the remaining size for the app is very small.
is there any other reason why there is no central role support?
Also there are some posts on internet which showed that modified versions of softdevice S132v5.1 managed to achieve multiple roles .
the S40 soft device is 150kB in size so it would fit into 192kB flash memory of nRF52805, even though the remaining size for the app is very small.
is there any other reason why there is no central role support?
Also there are some posts on internet which showed that modified versions of softdevice S132v5.1 managed to achieve multiple roles .
fionut said:the S40 soft device is 150kB in size so it would fit into 192kB flash memory of nRF52805, even though the remaining size for the app is very small.
Sure, but there are also other requirements - running a central also requires more RAM, which the nRF52805 only has 24 kB of.
fionut said:is there any other reason why there is no central role support?
I have not been involved with the development of these SoftDevices, so I do not really have a lot of information about the design choices here, but if I had to take a guess I would say that this likely is one of the main reasons, yes.
The nRF52805 is a subset of the other nRF52 series devices - it is made specifically as a smaller device perfect for specific peripheral type devices.
As mentioned in my previous comment we do not discuss roadmaps and/or future releases here on DevZone, so if you have questions about this you will have to inquire your Regional Sales Manager (RSM) directly. Send me a direct message with your location if you do not know who your RSM is, so I may provide you their contact information.
fionut said:Also there are some posts on internet which showed that modified versions of softdevice S132v5.1 managed to achieve multiple roles .
Please be specific about which posts you are referring to here so I could take a look.
Best regards,
Karl
Ok, I understand that RAM may be a constraint.
And that for specific use cases which need a small simple device, with few functions, peripheral role is enough.
We want to build a such small simple device with few functions, but with central role (bassically a button over BLE, battery powered)
https://jimmywongiot.com/2021/08/19/multiple-role-on-the-nordic-nrf52805/
fionut said:We want to build a such small simple device with few functions, but with central role (bassically a button over BLE, battery powered)
Could you elaborate why you want / need such a simple device to have the central role?
Could you not achieve this functionality through a device in a peripheral role?
fionut said:jimmywongiot.com/.../quote]Thank you for specifying.
This blog indeed seems to use the S132 v5.1 - which is compatible with the nRF52810, but incompatible with the nRF52805.
The S132 supports both central and peripheral role, while the S112 and S113 only supports peripheral and broadcaster roles.
Best regards,
Karl
The BLE button will send infrormation to a BLE relay which is peripheral.
The BLE button I think it will save more power if it is central and sends data over BLE only when the buton is pushed ; this way also the response time is shorter. comparing to the case when the buton is peripheral
fionut said:The BLE button I think it will save more power if it is central and sends data over BLE only when the buton is pushed ;
No, I do not think that this is correct. This would mean that you would wake up the device when the button is pressed to start scanning, and you would have to scan until you found the advertisements of the peripheral device. Scanning has a higher power consumption than advertising since scanning uses the radio continuously during the scanning window, compared to advertisements which is contained to a short period. If the central does not immediately find the peripheral device it might go on to scan for a relatively long time (active radio time compared to advertising), which will consume more power.
If you instead wake the device to do spaced out advertising upon the button press (or starting out with fast advertisings, then moving to spaced out ones) should give you a lower over all power consumption.
fionut said:this way also the response time is shorter. comparing to the case when the buton is peripheral
The timing difference between the peripheral's first reception of a central data payload packet and the central's first reception of a peripheral data payload packet is neglectable - it depends on the connection configuration, but it will be in the 100 of µs range. Additionally, the SoftDevice will not give back control of the CPU to the application before it is finished with the entire exchange, which is why I would call this difference in first data packet reception time neglectable.
You could take a look at how the different parameters and exchanges will look in the Online Power Profiler.
Best regards,
Karl
