-
Updated
Oct 27, 2020
hardware
Here are 2,499 public repositories matching this topic...
-
Updated
Jun 7, 2021 - Go
-
Updated
May 1, 2021
-
Updated
Nov 2, 2019 - C
-
Updated
Feb 3, 2021 - C++
-
Updated
Jul 7, 2021 - C++
-
Updated
Sep 14, 2020 - Rich Text Format
Blynk library version: master branch at 144a90f3bdb66c3b6c03cce0335c1f1e304d91d6
IDE: VS Code + PlatformIO
IDE version: 1.52.1
Board type: ESP8266
Additional modules: Arduino ESP8266
Scenario, steps to reproduce
Blynk.run()
blocks if there is no internet connection on the network and connecting to a local server via SSL.
According to my investigation, `BlynkArduinoClientSecure::conn
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
Jul 1, 2021
-
Updated
Jun 7, 2021 - Python
-
Updated
Jul 3, 2021 - Java
-
Updated
Nov 20, 2020
Is your feature request related to a problem? Please describe.
When encountering a bug it is a bit tedious to open github, navigate to the iGlance repository and open a new bug issue. Not everyone is going to jump through those hoops in order to report a bug.
Describe the solution you'd like
It should be possible to click a button in the main window and be directly redirected to the
-
Updated
Mar 12, 2017
-
Updated
Jun 2, 2021
-
Updated
Jul 1, 2021
-
Updated
Jan 11, 2021 - C
-
Updated
Jun 11, 2021
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
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