zhangyuqing
/
RF433any
mirror of https://github.com/sebmillet/RF433any
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
RF433any/extras/testplan/track/09/expect2.txt

23 lines
596 B
Plaintext
Raw Normal View History

Initial Upload
2021-06-04 17:57:28 +08:00
IH_max_pending_timings = 3
Manages compact integers in the test plan *WARNING* Actual code *DOES NOT PASS* tests 3 and above. It only passes test 1 and 2 - In order to save memory during the test plan, the read durations are saved in 'compact' form, using compact() to reduce their size and uncompact() to get their 'original' value (not exactly 'original' as some precision is lost on the way). Durations (without compact) are typically uint16_t whereas in compact form, it is uint8_t, saving 50% of space. The precision loss (see comment written on top of compact()) is fine with the code logic.
2022-09-18 01:00:15 +08:00
> nb_sections = 5, initseq = 8448
Initial Upload
2021-06-04 17:57:28 +08:00
00 SSEP
Manages compact integers in the test plan *WARNING* Actual code *DOES NOT PASS* tests 3 and above. It only passes test 1 and 2 - In order to save memory during the test plan, the read durations are saved in 'compact' form, using compact() to reduce their size and uncompact() to get their 'original' value (not exactly 'original' as some precision is lost on the way). Durations (without compact) are typically uint16_t whereas in compact form, it is uint8_t, saving 50% of space. The precision loss (see comment written on top of compact()) is fine with the code logic.
2022-09-18 01:00:15 +08:00
sep = 21504
Initial Upload
2021-06-04 17:57:28 +08:00
low: [2] n = 12, v = 0x00000D1A
high: [2] n = 11, v = 0x0000068D
01 SSEP
Manages compact integers in the test plan *WARNING* Actual code *DOES NOT PASS* tests 3 and above. It only passes test 1 and 2 - In order to save memory during the test plan, the read durations are saved in 'compact' form, using compact() to reduce their size and uncompact() to get their 'original' value (not exactly 'original' as some precision is lost on the way). Durations (without compact) are typically uint16_t whereas in compact form, it is uint8_t, saving 50% of space. The precision loss (see comment written on top of compact()) is fine with the code logic.
2022-09-18 01:00:15 +08:00
sep = 21504
Initial Upload
2021-06-04 17:57:28 +08:00
low: [2] n = 12, v = 0x00000AAA
high: [2] n = 11, v = 0x00000555
02 SSEP
Manages compact integers in the test plan *WARNING* Actual code *DOES NOT PASS* tests 3 and above. It only passes test 1 and 2 - In order to save memory during the test plan, the read durations are saved in 'compact' form, using compact() to reduce their size and uncompact() to get their 'original' value (not exactly 'original' as some precision is lost on the way). Durations (without compact) are typically uint16_t whereas in compact form, it is uint8_t, saving 50% of space. The precision loss (see comment written on top of compact()) is fine with the code logic.
2022-09-18 01:00:15 +08:00
sep = 21504
Initial Upload
2021-06-04 17:57:28 +08:00
low: [2] n = 12, v = 0x00000AAA
high: [2] n = 11, v = 0x00000555
03 SSEP
Manages compact integers in the test plan *WARNING* Actual code *DOES NOT PASS* tests 3 and above. It only passes test 1 and 2 - In order to save memory during the test plan, the read durations are saved in 'compact' form, using compact() to reduce their size and uncompact() to get their 'original' value (not exactly 'original' as some precision is lost on the way). Durations (without compact) are typically uint16_t whereas in compact form, it is uint8_t, saving 50% of space. The precision loss (see comment written on top of compact()) is fine with the code logic.
2022-09-18 01:00:15 +08:00
sep = 21504
Initial Upload
2021-06-04 17:57:28 +08:00
low: [2] n = 12, v = 0x00000AAA
high: [2] n = 11, v = 0x00000555
04 SSEP
Manages compact integers in the test plan *WARNING* Actual code *DOES NOT PASS* tests 3 and above. It only passes test 1 and 2 - In order to save memory during the test plan, the read durations are saved in 'compact' form, using compact() to reduce their size and uncompact() to get their 'original' value (not exactly 'original' as some precision is lost on the way). Durations (without compact) are typically uint16_t whereas in compact form, it is uint8_t, saving 50% of space. The precision loss (see comment written on top of compact()) is fine with the code logic.
2022-09-18 01:00:15 +08:00
sep = 21504
Initial Upload
2021-06-04 17:57:28 +08:00
low: [2] n = 12, v = 0x00000AAA
high: [2] n = 11, v = 0x00000555