Switching Parity Issues

[wxwxwz]

I need to quickly switch Parity before writing data (to solve the 9-bit problem). I use MARK_PARITY to write the address, then switch to SPACE_PARITY to write the data, and finally switch to NO_PARITY to receive the data. Each switch must be kept for 1ms, otherwise either invalid data will be sent or data will be lost. Can this be solved or optimized? Also, if I use NO_PARITY or SPACE_PARITY directly when writing data, the received data will be different.

[hedgecrw]

I will try to add some "quick switching" functions in the next release to help with this.

[hedgecrw]

I was able to get this implemented in the latest SNAPSHOT release. If you wouldn't mind testing when you get a chance, I'd appreciate it. There is a new method called quickSetConfig(int newDataBits, int newStopBits, int newParity) that you can call on an already-opened serial port to quickly change those parameters with as little overhead as possible. Also, if this works for you, please report back and also let me know which OS you are testing this on. Thanks!

[wxwxwz]

Okay, thank you, I will try it.

[wxwxwz]

My test platform is Android, compiled from the latest source code. The switching speed seems acceptable, but I must wait 1ms after switching to avoid sending invalid data (this 1ms is acceptable, but I don't understand why). You can refer to the screenshot below.