This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Are nRF52810 device able to operate with reliability over 8 hours of continue connection?

In my application I'd like to use nRF52810 due different reasons. Since we're still in evaluating phase, without even choose a brand and related EVK, I've some basic questions about this device.

Probably, all of my question may be possible, but a confirmation would be good to correctly choose the right product.

- Are two nRF52810 able to be connected together for regular data polling or regular data transmitting?

I should be able to connect a Master and a single (for now) Slave between them, both nRF52810 product. It's something "easy" to setup and stable like a regular App-nRF52 Device?
Data transmitting will be done every 250ms, a very small packet with an ADC value. About this I'd like to ask also if it's possible to reduce consumption to minimum keeping connection active to optimize battery usage (BLE application) between each packet.

- Are nRF52810 device able to operate with reliability over 8 hours of continue connection?

I'll have a critical device that should be operative and constantly transmit above described packet. This mean no packet losses, no connection losses and no system crashes/loops. This is a kind of device able to do this if correctly configured? Is there some kind of re connection if this is lost or a watchdog if MCU is in crash/loop able to reset it?

- Are two nRF52810 able to be unique connected together?

In this application I've a Master that, at start of the system, should always try to connect to the associated slave when it's also on. If another device tries to connect to the Slave, and it's not an nRF52810 Master, this shouldn't be possible. If a device tries to connect to Master should be allowed only in particular case, if disconnects Master should automatically reconnect to Slave or refuse non nRF52810 device connection.


I hope that I've explained what I mean, something like a Sensor that sends critical data to a System and a System that gather data from a single(or multiple) registered sensor.
In reality is not that critical, but since the communication is between two devices without any interface (like reset buttons or displays), they should be able to connect between them when they find each other and self debug if connection is lost.

About my questions I ask only feasibility and not a technical answer.

About how to match two device, do you think possible during manufacturing to insert inside memory (using NFC interface) two unique IDs of Master and Slave to create this association?

Parents
  • Do a bit more research: In Bluetooth low Energy, there are Central and Peripherial devices. Slavery was abolished. ;-)

    Unfortunately the S112 Stack can only be Peripherial, and the S132 is VERY BIG on flash consumtion. So you really want an nRF52832 or nRF52840 as the Central device.

    You cannot connect 2 NRF-based devices with NFC, as the chip can only implement the "passive" or "tag" side - and  the other side is powering the RF field.

    Are two nRF52810 able to be unique connected together

    Yes. Look at how the BLE examples use peer manager and whitelisting.

Reply
  • Do a bit more research: In Bluetooth low Energy, there are Central and Peripherial devices. Slavery was abolished. ;-)

    Unfortunately the S112 Stack can only be Peripherial, and the S132 is VERY BIG on flash consumtion. So you really want an nRF52832 or nRF52840 as the Central device.

    You cannot connect 2 NRF-based devices with NFC, as the chip can only implement the "passive" or "tag" side - and  the other side is powering the RF field.

    Are two nRF52810 able to be unique connected together

    Yes. Look at how the BLE examples use peer manager and whitelisting.

Children
No Data
Related