• State Verified Answer
  • +8 person also asked this people also asked this
  • Replies 36 replies
  • Subscribers 74 subscribers
  • Views 21097 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 129801
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

change phy in mesh

kassianson

I'm working with the nRF52840 PDK and I'm wondering how to change the PHY (preferably to CODED) in a Mesh. Has that been implemented yet? Or when can we expect this feature?

Parents
  • 0

    Although this is not yet added to the standard or supported from Nordic, I think this possibility add many new use cases where Bluetooth Mesh can be used (industrial, smart city etc).

    Would be interesting yo know if anyone tried this out? We will for sure test it as soon as possible!

    Additional comment:

    We have a real smart city use case where we are going to test mesh. The idea is exactly as you say David, we intent to start with coverage test using non coded PHY but I would be good to have the long range option at hand if needed (and I see risk for it in this case).

    BTW, nice to meet with you again, David. Been a while since we worked on Automation IO ...!

  • 0 in reply to matsublox

    @Jeff I would typically expect a PHY that has a shorter on air time like a 2Mbit/s to work out of the box. I would also expect that the change to a PHY that has a longer on air time like LE Coded PHY will be more work, as the time needed for the TimeSlot API to run will be more for the coded PHY and that has to be adjusted for. If you are using a 125 Kbit/sec then the on air time will be atleast 8 times more and since the LE coded PHY is used you need to also allow for the FEC in the packet so the on-air time is larger.

Reply
  • 0 in reply to matsublox

    @Jeff I would typically expect a PHY that has a shorter on air time like a 2Mbit/s to work out of the box. I would also expect that the change to a PHY that has a longer on air time like LE Coded PHY will be more work, as the time needed for the TimeSlot API to run will be more for the coded PHY and that has to be adjusted for. If you are using a 125 Kbit/sec then the on air time will be atleast 8 times more and since the LE coded PHY is used you need to also allow for the FEC in the packet so the on-air time is larger.

Children
No Data
Related