rxAndroidBle 得到长写响应

Question

我正在对 BLE 进行长时间写入以进行 OTA 更新，但我需要等待 BLE 设备的写入响应以发送更多数据，但我不知道如何捕获设备写入响应，我正在使用带有 android 7 的三星 Galaxy Tab s2 和 Kotlin 作为我的代码

override fun otaDataWrite(data:ByteArray) {
    manager.connection?.flatMap { rxBleConnection: RxBleConnection? -> rxBleConnection?.createNewLongWriteBuilder()
            ?.setCharacteristicUuid(OTACharacteristics.OTA_DATA.uuid)
            ?.setBytes(data)
            ?.setMaxBatchSize(totalPackages)
            ?.build()
    }?.subscribe({ t: ByteArray? ->
        Log.i("arrive", "data ${converter.bytesToHex(t)}")
        manageOtaWrite()
    }, { t: Throwable? -> t?.printStackTrace() })

每次我编写特征时，订阅都会立即用写入的数据响应我，我需要捕获特征的响应，以发送更多数据

Answer 1

嗯，经过大量的测试，我终于开发了一个独立的类，用于使用android BLE API进行OTA更新，并将它与我所有的RxBle方法一起使用，我不知道我是硬件问题还是其他的，但我解决了这个问题，非常感谢。

Answer 2

您正在写关于特征的响应——我假设您所指的特征是带有UUID=OTA_DATA 的特征。长写入由内部的小写入（所谓的批处理）组成。

你可能想要达到的目标是：

fun otaDataWrite(data: ByteArray) {
    manager.connection!!.setupNotification(OTA_DATA) // first we need to get the notification on to get the response
            .flatMap { responseNotificationObservable -> // when the notification is ready we create the long write
                connection.createNewLongWriteBuilder()
                        .setCharacteristicUuid(OTA_DATA)
                        .setBytes(data)
//                        .setMaxBatchSize() // -> if omitted will default to the MTU (20 bytes if MTU was not changed). Should be used only if a single write should be less than MTU in size
                        .setWriteOperationAckStrategy { writeCompletedObservable -> // we need to postpone writing of the next batch of data till we get the response notification
                            Observable.zip( // so we zip the response notification
                                    responseNotificationObservable,
                                    writeCompletedObservable, // with the acknowledgement of the written batch
                                    { _, writeCompletedBoolean -> writeCompletedBoolean } // when both are available the next batch will be written
                            )
                        }
                        .build()
            }
            .take(1) // with this line the notification that was set above will be discarded after the long write will finish
            .subscribe(
                    { byteArray ->
                        Log.i("arrive", "data ${converter.bytesToHex(byteArray)}")
                        manageOtaWrite()
                    },
                    { it.printStackTrace() }
            )
}