site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com I have a problem with a BLE peripheral and iOS. It’s unclear who is to blame, but one (or both) are doing something bogus. Let’s assume I only want to do WriteWithResponse in order to have better diagnostics (delegate being called after transmit). When I ask iOS for the WriteWithResponse MTU, it returns 512. Sending packets up to 247 data bytes works fine (which, by the way, is what iOS reports for WriteWithoutResponse), but once I exceed this, iOS sends a PREPARE WRITE to my peripheral, which ­– due to that peripheral not implementing queued writes ­– is not answered and the whole transfer stalls. Unfortunately it is an off-the-shelf BLE device (OBDLink CX OBD2 adapter), where I don’t have any control over the stack it’s using. Could anyone share some light on this? Let’s start by the question why iOS claims 512 to be an OK MTU for that peripheral? Best regards, Mickey. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com