Hi luc, MTU is indeed the max transmission size for a single packet. However, the APIs allow you pass us the whole buffer, and we will do the work of chopping up the whole buffer for you, and then transmitting it in pieces that fit into the MTU, until it is finished. Thus, you don't really need to be aware of what value the MTU is to send data. jason

Hi everyone,

I see in the Bluetooth spec that the channel MTU is the max packet size

that we can write (as a single bunch) into an L2CAP or RFCOMM channel.

When I call

NSLog(@"channel MTU = %i", ((int)[mChannel getMTU]));

then the answer is 666, which I think means that I cannot write more

than 666 bytes at once.

But when I call

exchangeDataStatus = [RfCommChannel writeSync:dataPointer

length:length];

or

exchangeDataStatus = [RfCommChannel writeAsync:dataPointer

length:length refcon:nil];

with a 4000 bytes long message, the complete message appears in the

remote device.

Does anyone knows if the Bluetooth methods implementation has change

without changing the API (handling the long message), or if I am just

lucky that the message is carried over and that one day it could crash?

Thanks a lot.

luc bergevin

_______________________________________________

bluetooth-dev mailing list | bluetooth-dev@lists.apple.com

Help/Unsubscribe/Archives:

http://www.lists.apple.com/mailman/listinfo/bluetooth-dev

Do not post admin requests to the list. They will be ignored.

_______________________________________________ bluetooth-dev mailing list | bluetooth-dev@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.