The new example, NimBLE_Stream_Server, is incompatible with some NUS terminal software.

[LusterWong]

Thank you very much for providing the new example. I am currently looking for a similar method for sending and receiving data like the Arduino serial port. I think this example seems feasible.

Check out the NimBLE about Stream, and I find that it defines the Nordic UART SERVICE_UUID and CHARACTERISTIC_UUID. However, the standard should include two feature codes: read and write. If the example could be changed to the standard two characteristic, that would be great. Because it will compatible with NUS's terminal software.

I don't quite understand the Bluetooth principle. If the server and the client both perform write operations on the characteristic code at the same time, will there be a conflict?

Thanks.

[h2zero]

@LusterWong Thanks for brining this up, I did not realize that those UUID's were used as the example was contributed and I wasn't looking at them. Glad it brought this up though because that would be a great use for these classes. I'll see what I can do to make this work 😄