Replies: 1 comment
-
Yes, removing the DLLs and running from the Pothos folder is the right way to get the Pothos libs to load. Looks like a x1527 protocol, 24 OOK PWM bits plus 1 sync. The x1527 encoders allow for the last bits to encode some state, like which button is pressed. If those are the last 4 bits then just e.g. Omit sync ( Record with Look at https://github.com/merbanan/rtl_433/tree/master/conf for some other remotes with button codes. |
Beta Was this translation helpful? Give feedback.
-
I have a pair of Neewer ZC-10S LED light panels - each panel has its own three button 433.920 MHz remote. one panel is coded "red" and the other "white". I have two aims: 1. to add this product to rtl_433, and 2. be able to emit the remote signals with a PlutoSDR. This is my first foray into using rtl_433 to investigate a RF remote controlled product.
What I've Done So Far
I am using
rtl_433-rtlsdr-soapysdr-tls.exe
fromrtl_433-win-msvc-x64-nightly
(d/l April 30) with a PlutoSDR. In order to get that working withPothosSDR-2021.07.25-vc16-x64
, it was necessary to rename all the DLL files in the nightly folder to *.DLO and then run rtl_433 from the PothosSDR bin folder.Analysis with -A
Many Experiments Later
I think I have correctly narrowed down the configuration to
which shows all 6 possible key code transmissions from "red" (0xada1f) and "white" (0x6f4af) with no junk decodes.
The one nibble before the trailing 8 is the unique value for each keypress.
What Next
Beta Was this translation helpful? Give feedback.
All reactions