hi,all
S110 NRF51822 SDK8.0.0 server
i want to increase the througout speed,the SDK8.0.0 support changing MTU size?
MTU Can be in 4.0 protocol is modified?
if SDK8.0.0 support it,have exmaple?
hi,all
S110 NRF51822 SDK8.0.0 server
i want to increase the througout speed,the SDK8.0.0 support changing MTU size?
MTU Can be in 4.0 protocol is modified?
if SDK8.0.0 support it,have exmaple?
Edit: sorry, my bad, none of nRF51 SoftDevices support ATT_MTU change procedure, all are capable of default size (23B) only. Note that using BT SIG specification version for feature list is pretty confusing, none of them demands ATT_MTU exchange procedure as mandatory features so you can have BLE stacks (like several Nordic Soft Device types/versions) which are certified as v4.1 or v4.2 but don't support that. It's similar with other features (like PDU extension), always reed detailed spec/feature list not just BT SIG version mentioned in certification documents.
Yes, under some condition you can achieve higher effective bandwidth on top of GATT with non-default ATT_MTU size, however again this is very application-dependent. Don't get confused by some simulated numbers, it's important if your application is half duplex/full-duplex, what are typical packet sizes on top of (G)ATT MTU, if the protocol is completely asynchronous or if it is command-response pair etc. I'd recommend to grab few Dev Kits and simulate it, there is nothing better then proper feasibility study...
Yes, under some condition you can achieve higher effective bandwidth on top of GATT with non-default ATT_MTU size, however again this is very application-dependent. Don't get confused by some simulated numbers, it's important if your application is half duplex/full-duplex, what are typical packet sizes on top of (G)ATT MTU, if the protocol is completely asynchronous or if it is command-response pair etc. I'd recommend to grab few Dev Kits and simulate it, there is nothing better then proper feasibility study...