In the latest version of the code the problem is not fixed. The problem can be traced to the BaudRateEnum defining the different baud rate speed. The BAUD_INVALID value takes by default the value of the previous enum value +1. The previous enum value happens to be 4097. BAUD_INVALID becomes 4098 the same as BAUD_115200.
A fix would be to specify the underlying type of the enum and force BAUD_INVALID to be its maximum value
I have updated the latest source code package to include the fix from SVN. Hopefully this will help other. Sorry you had to waste your time tracking this issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the latest version of the code the problem is not fixed. The problem can be traced to the BaudRateEnum defining the different baud rate speed. The BAUD_INVALID value takes by default the value of the previous enum value +1. The previous enum value happens to be 4097. BAUD_INVALID becomes 4098 the same as BAUD_115200.
A fix would be to specify the underlying type of the enum and force BAUD_INVALID to be its maximum value
The issue was fixed in SVN (see this comment) by setting BAUD_INVALID to -1. It is not in a released version yet.
I have updated the latest source code package to include the fix from SVN. Hopefully this will help other. Sorry you had to waste your time tracking this issue.
Thanks