![]() |
Step 1 Search synchronization There are two long times with enough other times between 11981 and 11987- The times for synchronization are marked with 'sync'. Step 2 Search for similar times If you look at the times, the following three times are noticeable: Time A: (401, 374, 371, 404, 373,..) Average value approx. 385 Time B: (1187, 1178, 1183, 1144, 1158,....) Average value approx. 1170 Time C: the long synchronization times (11981, 11978) Average value approx. 11980 Other times are not available. Step 3 Estimate pulse length The largest common divisor of the three determined average values is approx. 390 Time A average value 385 divided by 390 = 0.98 -> approx. 1 Time B average value 1170 divided by 390 = 3 Time C average 11980 divided by 390 = 30.71 -> approx. 31 This does not have to be exact, an approximation is sufficient here. Step 4 Determine pairs and enter multiples of the pulse length Synchronization High (first time short ) 401 / 390 gives about 1 Synchronization Low (second time long) 11981 / 390 gives about 31 So the synchronization pair in multiples of the pulse tones (1.31) Immediately after the long time you go through the row in pairs and look for combinations: Time for High is marked with *. Time for Low is marked with '**'. The first pair (1187 *, 374**) corresponds in multiples of the pulse length (1, 3) The next two pairs are the same. The fourth pair (404 *, 1144 **) corresponds in multiples of the pulse length (3.1) other combinations are not available. The found combinations can now be entered. ![]() We did not find any times for Data 2, just enter 0 here. Since it is a normal protocol, Gap Value must be set to Low. Once a value has been entered, you must press the Return/Enter key or click in another field to accept the value. Note: If it would be an inverted protocol, so the synchronization would consist of 11981, 1187 and the marks in the example would be shifted down by one: 11981 sync High 1187 sync Low 374 * High 1178 ** Low But then you would need further combinations with (372,404) in lines 604 and 605 and (1158,1174) in lines 608 and 609, this does not work out very well. Therefore, we assume in our example that this is a normal protocol. Step 5 Test Hold the handheld transmitter again very close to the board and press the same button as before. If the protocol was estimated correctly, a sequence of values should now be recognized: ![]() Now you can click on ![]() If no value sequence is recognized or your receiver does not react, you will have to play around with steps 3 and 4 and change the estimate a little. You can also start from the beginning, maybe the recording of the data was inaccurate due to disturbances. Tipp: The software remembers the last expert setting. If you have several cryptic transmitters and are trying out different expert settings in the meantime, you can open an already used (saved) setting for a handheld transmitter button and then close the Sniffer window again. This makes that expert setting the last one again and you can use it for another button on your remote control. Another alternative would be to write down the combinations and put this to your handheld transmitter! |
Another tricky example: |
The following times were recorded for radio sockets from delayCON |
![]() |
Here there are three combinations of pairs of values: Red circle: (290 High, 2634 Low) yellow circles: (308 high, 1280 low) and (296 high, 237 low) this means that the code consists of three values and you have to enter combinations of pulse lengths for Data 0, Data 1 and Data 2. This time sequence is a bit tricky, with the following values it worked: estimated pulse length 60 synchronization (5, 173) Data 0: (5, 4) Data 1: (5, 21) Data 2: (5, 44) - red circle |