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

MTU PI Gatttool Connection interval

hi i m using nrf52 with a pi and the gatttool. pi as master and nrf52 as slave. i want to change the mtu but i got no answer from the nrf52 as you see in the log! do i have to enable it? Mtu_request.pcapng

if i notify on uart the data rate are to slow for my use case. you can see in the log it only use every 3th message to send data! is this normal? notification.pcapng How can i easy improve the data throughput? Where can i change the connection interval on the pi or can i change it from the slave the nrf52?

If i described something bad please feel free to ask me;)

Update: S132 Nrf52832 qfa ab0 I want to transfer more data per second. so i want to change the mtu or the connection interval. my problem is i m using the pi and in the most connection libs you only can change the mtu but the nordic ignore it! My other idea was too change the settings from the nordic site but i m not shure if this is possible. Perhaps you have an other idea to change the data transmission rate?

Update: the FW was built on the uart-ble example from nordic!

Parents
  • Hi Marc,

    You are speaking about nRF52 but that's just HW description (and even that is vague as Nordic has released new member of nRF52 earlier this week, you should be saying "nRF52832 Rev1" or something along these lines;) but ATT_MTU exchange procedure is managed by software stack (and to make it even more complicated it is managed by "lower" stack - implemented inside Nordic's SoftDevice if you use that - but it can get callback up to APPlication layer). So you should be more clear bout what exactly you are using and why you expect that ATT layer on GAP Peripheral device (running on nRF52) should handle MTU Change procedure...

    Cheers Jan

Reply
  • Hi Marc,

    You are speaking about nRF52 but that's just HW description (and even that is vague as Nordic has released new member of nRF52 earlier this week, you should be saying "nRF52832 Rev1" or something along these lines;) but ATT_MTU exchange procedure is managed by software stack (and to make it even more complicated it is managed by "lower" stack - implemented inside Nordic's SoftDevice if you use that - but it can get callback up to APPlication layer). So you should be more clear bout what exactly you are using and why you expect that ATT layer on GAP Peripheral device (running on nRF52) should handle MTU Change procedure...

    Cheers Jan

Children
No Data
Related