support 921600 baudrate #176

Activity

1. hiddenalpha

   added a commit that references this issue on Nov 27, 2024

   Add java constant for non-standard baud rate 921600

   ...

   f5c1f66
2. hiddenalpha commented on Nov 28, 2024

   

   hiddenalpha

   on Nov 28, 2024

   Last edited by hiddenalpha

   More actions

   Having a look into jssc code, to me it seems that the underlying implementations already support 921600 (see the two jssc.cpp files). There is just no constant defined on java side for it.

   Maybe it's worth a try to pass the baud rate as a naked int. But make sure to check the returned value for errors. Maybe this could give us a hint. Disclaimer: I did not try this myself ever. So I do not know if this works.

   boolean ok;
   ok = serialNativeInterface.setParams(
       handle, 921600, dataBits, stopBits, parity, setRTS, setDTR, flags);
   if( !ok ){
       whops();
   }

   I don't know about the described truncation issue.
3. tresf commented on Dec 1, 2024

   

   tresf

   on Dec 1, 2024

   More actions

   Maybe it's worth a try to pass the baud rate as a naked int. But make sure to check the returned value for errors. Maybe this could give us a hint. Disclaimer: I did not try this myself ever. So I do not know if this works.

   Just updating this thread with information gathered from #177, quoting:

   ... we [do] use [the] setParam function and provide any baud rate parameter they choose, not just the predefined ones in [this] library.

   However, we've encountered an issue when users send very long commands (via the writeBytes function) at 921600 baud. The commands are being truncated even if they use rts/cts flow control.(when the command are with regular size the command are sent fine, for example a command that truncated has 980 characters).
   Our OS is windows.
4. hiddenalpha commented on Aug 1, 2025

   

   hiddenalpha

   on Aug 1, 2025

   More actions

   Could this issue maybe relate to #129 ? (and therefore, indirectly to #195?)