wireless
Here are 577 public repositories matching this topic...
-
Updated
May 20, 2021 - Shell
-
Updated
Apr 18, 2020 - Python
These blocks use "Vec Length" instead of "vector length" AND this is not documented on the wiki pages. It's really just a multiplier for the itemsize.
To fix this,
- Fix the GRC .block.yml files to use the canonical "vector size" / "vector length" (look that up)
- Modify the wiki pages for the deinterleave / interleave blocks, explainin
-
Updated
May 21, 2021 - C++
-
Updated
Aug 26, 2020 - Java
-
Updated
Nov 3, 2019 - Python
-
Updated
Apr 23, 2019 - Python
-
Updated
May 4, 2021 - Go
Whenever we long press on the tile ( notification panel > share files) it takes to the app settings ( system settings).
I think it would be more useful if it take us to the app itself.
Hope you understood and thank you for the app!
-
Updated
May 13, 2021 - Python
#238 introduced a workaround to enable excluding files from minification and versioning because of #232
Since, that functionality has been ported in openwisp-utils in openwisp/openwisp-utils#172 (to simplify maintenance), we can remove the workaround from the ansible role and update the settings accordingly.
Blockers
- Requires openwisp-utils 0.8.0
-
Updated
May 20, 2021 - JavaScript
-
Updated
May 20, 2021 - Python
Indicator CC V4 adds two new commands:
- Indicator Description Get Command
- Indicator Description Report Command
TODOs:
- Implement the new commands
- Implement a
getDescriptionmethod onIndicatorCCAPI - update
@implementedVersiondecor
Using LSHIFT or RSHIFT instead of LSHFT or RSHFT seems to be a recurring error. We should probably add those aliases.
Examples:
-
Updated
Apr 24, 2021
-
Updated
Apr 27, 2021 - Python
-
Updated
Nov 22, 2019 - Shell
Improve this page
Add a description, image, and links to the wireless topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the wireless topic, visit your repo's landing page and select "manage topics."


A common protocol structure is to have a header containing a
lengthfield, followed by data oflengthbytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.I do not know the best way to address this, but quick and easy way to support