• State Not Answered
  • Replies 5 replies
  • Subscribers 62 subscribers
  • Views 2385 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 123428
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Thingy:52 node.js/Raspberry Pi demos PDK support

dansam

I would like to setup the just released RasPI demo using the Nordic-Thingy52-Nodejs repo I don't have a dongle, but 4 PDK 52840 boards and 2 Thingys.

Can I still use 1 PDK attached to the Pi instead of a dongle?

Parents
  • 0

    Hi,

    The Raspberry Pi has built-in Bluetooth. You don't need to connect a dongle or PDK to it. You can connect directly to the Thingy with Raspberry Pi.

  • 0 in reply to Sigurd

    None of the nodejs supported devices (e.g. Raspberry PI) support BLE5 long range so the connection between the gateway and the PDK would be on regular BLE 1Mbps mode.

    Note that one of the benefits with mesh is that you actually don’t need BLE5 long range. More Bluetooth devices can be connected to a mesh network, and together they will extend the range of every node in the network. A mesh network will increase the range because A communicates with D via B and C, when a direct connection between A and D would otherwise be out of range.

    Regarding BLE Mesh that will be released: the official Bluetooth Mesh is based on the Bluetooth low energy part of the Bluetooth 4.0 Specification and shares the lowest layers with this protocol. I.e. the official BLE Mesh will not support BLE5 long range.

    If official BLE mesh is the best option for you depends on how many nodes and gateways you are planning to use. If you are planning only a few nodes a long range (BLE 5) solution with your own "mesh/tree" system may be the preferred option.

    Also note that we will release a production ready IoT SDK in Q3 this year. It will be built on SoftDevice S132 v5.

Reply
  • 0 in reply to Sigurd

    None of the nodejs supported devices (e.g. Raspberry PI) support BLE5 long range so the connection between the gateway and the PDK would be on regular BLE 1Mbps mode.

    Note that one of the benefits with mesh is that you actually don’t need BLE5 long range. More Bluetooth devices can be connected to a mesh network, and together they will extend the range of every node in the network. A mesh network will increase the range because A communicates with D via B and C, when a direct connection between A and D would otherwise be out of range.

    Regarding BLE Mesh that will be released: the official Bluetooth Mesh is based on the Bluetooth low energy part of the Bluetooth 4.0 Specification and shares the lowest layers with this protocol. I.e. the official BLE Mesh will not support BLE5 long range.

    If official BLE mesh is the best option for you depends on how many nodes and gateways you are planning to use. If you are planning only a few nodes a long range (BLE 5) solution with your own "mesh/tree" system may be the preferred option.

    Also note that we will release a production ready IoT SDK in Q3 this year. It will be built on SoftDevice S132 v5.

Children
No Data
Related