STRLCPY/flipperzero-bruteforce

Total 1 files

■ ■ ■ ■ ■ ■ ■

README.md

		skipped 75 lines
76	76		- pilot_period: aka preamble, a recurring pattern at the beginning of each key, defaults to `None`
77	77		- frequency: working frequency, defaults to 433.92
78	78
	79	+	### Optimization
	80	+
	81	+	After a little testing working with CAME 12 bit, it seems that as long as the ratio between the bits' lenghts is respected (`x`: short pulse, `2x`: long pulse, `36x`: pilot period) the actual duration of x can be lowered from the original 320 microseconds. From testing it seems that 250 microseconds is stable, shortening the bruteforce by a good minute (224 seconds against 287 seconds). From a code point of view:
	82	+
	83	+	```python
	84	+	protocols = [
	85	+	# Old CAME
	86	+	Protocol("CAME", 12, {"0": "-320 640 ", "1": "-640 320 "}, "-11520 320 "),
	87	+	# New CAME
	88	+	Protocol("CAME", 12, {"0": "-250 500 ", "1": "-500 250 "}, "-9000 250 "),
	89	+	]
	90	+	```
	91	+
	92	+	Further testing will be performed for the other protocols.
	93	+
79	94		# Timing
80	95
81	96		To compute the time it takes to perform a bruteforce attack, we need to sum the time it takes to send each code:
		skipped 5 lines
87	102		For example, computing this for CAME turns out to be:
88	103
89	104		```
90		-	[(11520 + 320) + 12 * (320 + 640)] * 3 * 2^12 = 287.047.680 microseconds ~ 287 seconds
	105	+	[(9000 + 250) + 12 * (250 + 500)] * 3 * 2^12 = 224.256.000 microseconds ~ 224 seconds
91	106		```
92	107