Is there any way to determine if the BT write stream and the buffer have finished processing the previous data transmitted?

 In other words... when streaming a large block of data to a bluetooth printer, the printers buffer gets garbaged because some commands get mixed up because the stream from the device is much faster than what the device can handle.

I have seen this issue before when using fransons searial.net, i then switched to princece tools from fieldsoftware and that seems to work when writing to the serial port on the bt device over bt...

Well, as I understand it, the remote Bluetooth device should have correct flow-control to signal to the local Bluetooth device that its buffers are filling up and that stops the local device from sending so the overflow never happens.  If the remote device isn't signalling in that way then it seems difficult to avoid that apart from sending the data more slowly.

Anyone else know if that's how it's meant to work...

Alan