Reach rs+ valid and invalid baud rates for RS232 interface

[marcel.d (Marcel)]

Dear Emlid Team,
Dear Emlid Users,

I’ve been trying out the RS232 output of the Reach RS+ (v2.18.1) and I found that not all baud rates available in the settings (and specified here https://docs.emlid.com/reachrs/common/reachview/base-mode/ ) do actually work. Here is the list:

460800 - invalid
256000 - invalid
230400 - OK
153600 - invalid
128000 - invalid
115200 - OK
57600 - OK
56000 - invalid
38400 - OK
28800 - invalid
19200 - OK
14400 - invalid
9600 - OK
4800 - OK

When changing baud rates, the last valid (OK) setting was preserved and used until the next valid setting was used.

Example:
Step | Set | Actual
1 | 57600 | 57600
2 | 14400 | 57600
3 | 256000 | 57600
4 | 230400 | 230400
…
…

Did anyone else encounter such behaviour? In case this is true, will the documentation please be updated? As well as removing the invalid settings from the app?

Thanks!

PS: I checked the results with both an oscilloscope and a serial terminal on PC.

[dmitriy.ershov]

Hi Marcel,

Thanks for noticing and sorry for the confusion. We’ve recently updated the list of baud rates in ReachView but haven’t done it yet in the docs.

[gleb.gira]

Hi Marcel,

We removed unsupported baud rates in dev release v2.21.0. The current supported are 9600, 19200, 38400, 57600, 115200. Reach RS2 also supports 230400.

We’ll update the docs after releasing the next stable version.