-
Updated
Oct 27, 2020
hardware
Here are 2,117 public repositories matching this topic...
-
Updated
Nov 16, 2020 - Go
-
Updated
Nov 19, 2020
-
Updated
Nov 2, 2019 - C
-
Updated
Nov 17, 2020 - C++
-
Updated
Nov 26, 2020 - C++
-
Updated
Sep 14, 2020 - Rich Text Format
-
Updated
Nov 6, 2020 - C++
-
Updated
Nov 24, 2020 - Python
-
Updated
Nov 15, 2020 - Java
-
Updated
Nov 20, 2020
API documentation?
I'm looking for documentation, or even just the source code, for the API for pikvm. I looked through this repo, the website, and subreddit and I couldn't find anything.
If documentation doesn't exist I'm absolutely willing to help with that too..
-
Updated
Mar 12, 2017
-
Updated
Nov 12, 2020
-
Updated
Sep 8, 2020
-
Updated
Oct 2, 2020
-
Updated
Jun 13, 2020 - Java
Revisit CLI syntax
Currently, the architecture of the CLI is based on (sub)commands and options. Commands are expected to be provided as the first argument, and do effectively decide which feature is to be used. OTOH, options provide parameters to the commands. However, there is no syntactical difference, as both commands and options start with --
or -i
. As a result, we rely on properly formating --help
and on
-
Updated
Nov 16, 2020 - C
-
Updated
Sep 27, 2020
-
Updated
Oct 21, 2020
Improve this page
Add a description, image, and links to the hardware topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the hardware topic, visit your repo's landing page and select "manage topics."
Summary of Problem
Not able to open port with stopbits as 1.5
I am currently building a desktop client using electron, where the COM port receives data correctly for values: baudRate: 2400, dataBits: 7, stopBits: 1.5, parity: 'none'
I found from the node-serialport documentation, stopBits Must be one of these: 1 or 2. But, should 1.5 be supported as well? especially for old & slow