Closed elektron-bbs closed 3 years ago
Merging #1022 (4a4f00c) into master (c6d1c01) will decrease coverage by
0.01%
. The diff coverage is100.00%
.
@@ Coverage Diff @@
## master #1022 +/- ##
==========================================
- Coverage 50.03% 50.01% -0.02%
==========================================
Files 218 218
Lines 15279 15274 -5
Branches 2859 2859
==========================================
- Hits 7645 7640 -5
Misses 5995 5995
Partials 1639 1639
Flag | Coverage Δ | |
---|---|---|
fhem | 50.24% <ø> (ø) |
|
modules | 50.01% <100.00%> (-0.02%) |
:arrow_down: |
perl | 50.95% <100.00%> (-0.03%) |
:arrow_down: |
unittests | 50.01% <100.00%> (-0.02%) |
:arrow_down: |
Flags with carried forward coverage won't be shown. Click here to find out more.
Impacted Files | Coverage Δ | |
---|---|---|
FHEM/lib/SD_ProtocolData.pm | 100.00% <ø> (ø) |
|
t/FHEM/00_SIGNALduino/01_SIGNALduino_Attr_rfmode.t | 100.00% <ø> (ø) |
|
t/SD_ProtocolData/01_verifyFSK.t | 98.70% <100.00%> (-0.05%) |
:arrow_down: |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update c6d1c01...4a4f00c. Read the comment docs.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
[ ] Bugfix (please link issue)
[ ] Feature enhancement
[ ] Documentation update
[ ] Unittest enhancement
[x] other
What is the current behavior? (You can also link to an open issue here, if this describes the current behavior) GDO0 is defined as an output. Interrupt is only given in the FIFOTHR register specified number of bytes triggered (can only be set in steps of 4 bytes). 16/16 + carrier-sense above threshold
What is the new behavior (if this is a feature change)? GDO0 output pin configuration, High impedance (3-state) - unused in FSK-modes CC1101 will wake up with optimal ADC settings for low data rate (≤ 100 kbps) The interrupt is triggered when the number of bytes required by the message is reached. SYNC_MODE 16/16 sync word bits detected
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) no
Other information: