-
-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for configuration and use #10
Comments
I agree with you that the documentation is currently lacking and I will be improving over time. I mostly just threw a README up and had concentrated on the integration with OpenMQTTGateway for the first release. You should be able to clone the repo, and open a new empty platformio window and "add folder to workspace" the rtl_433_ESP/example/sample/ folder. With Platformio you should then be able to build and deploy the sample to your ESP32. Platformio will then pull all the required libraries in ( including an additional copy of this library ). I had included my platformio.ini with all the settings needed to build and deploy. With the current sample it uses the sample wiring from LSATAN, but with the next release with support for FSK Modulation I will be changing the wiring as usage of GPIO2 is currently problematic. I was also thinking to add a example of this library to LSatan/SmartRC-CC1101-Driver-Lib once the FSK modulation release is complete. Expect that in the near future. Can you share more details about your issue ? |
Nothing, just listen for ASK/OOK signals This from my device ( '-DRTL_DEBUG=4' is very verbose )
|
This is when '-DRTL_DEBUG=4' is commented out I have several devices and they are chatty so I get multiple messages per minute.
|
I have tried transmitting with several remote controls but I get nothing on the serial monitor Where can I change the MISO, MOSI, etc. pins? I have tried to change this with ELECHOUSE_cc1101.setSpiPin (sck, miso, mosi, csn1); But it seems that this change does not work correctly with your example. Thanks |
This is not a scenario I took into account when designing the library. And the library is currently not checking for a live cc1101 as well ;-( Can you just edit the rtl_433_ESP library to try and set the values? |
Do you mean changing the pins in the library? |
Yes change either the rtl_433_ESP or SmartRC-CC1101-Driver-Lib ? |
ELECHOUSE_cc1101.setSpiPin (sck, miso, mosi, csn1); change in SmartRC library Where do you specify the pins in your rtl_433_ESP library? |
do you use the internal reception functions for reception or an interrupt that records the pulses? |
I’m watching the RSSI level in the arduino Loop function, then when RSSI is above MINRSSI a interrupt routine records pulse duration of GDO2. Start and end of signal is determined based on RSSI
My next release with FSK modulation support will utilize a second interupt triggered by carrier sense on GDO0 to determine start and end of signal.
For receiving I’m not using the onboard packet decoders but am leveraging asynchronous serial mode.
… On Apr 29, 2021, at 4:58 PM, LSatan ***@***.***> wrote:
do you use the internal reception functions for reception or an interrupt that records the pulses?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@NorthernMan54 I am using the same connections that you indicate in the readme.md sck = 18 With these connections I do not receive any data on the serial monitor either Thanks |
Humm...any thoughts on how to troubleshoot this further, is it possibly a wiring issue, signal modulation issue, background noise or ??? 1 - Is the wiring to the device working correctly ?
2 - The compiler directives RAW_SIGNAL_DEBUG and DEMOD_DEBUG will log more details about any received signal 3 - Does your ESP32 board have an onboard LED on gpio2 ( mine does ), is it off, on or flashing ? It is configured to turn on and off when a signal is received. The start and end of signal is determined when a signal RSSI raises above and drops below MSSI. If the LED is stuck on, you have a lot of background noise and need to set the MINRSSI to a higher value. It defaults to -82, try 5 higher ( -78 ) to see if it starts and stops receiving a signal If your LED is on a different GPIO, the compiler directive ONBOARD_LED allows you to change it. 4 - Do you know what the modulation scheme is of your devices ? ASK/OOK or ??? If it isn't ASK/OOK the current code base can't receive the signal ? |
@NorthernMan54 Hello! My device works correctly with other examples from the SmartRC library. The wiring is correct About the leds, my device has 3 leds, but they are configured on pins io12, io13 and io15. This does not affect the device About the compiler directives you indicate, I think they are commented. Only '-DRTL_DEBUG=4' is uncommented. I will try to uncomment the others you indicate Where can I change MINRSSI? About my remote controls they are all ASK/OOK. Thanks! |
If you look at the header file you can see the additional compiler directives and their defaults. Line 26 in b4a1cc0
I would recommend enabling one of your LEDs and then seeing what is happening another thought is to occasionally call this function in the loop, maybe once a minute to trigger display of receiver status and current Rssi level. Calling it every loop would be too often. rtl_433_ESP/src/rtl_433_ESP.cpp Line 533 in b4a1cc0
|
Sorry skip the getstatus function as it currently calls a message received callback, which isn’t implemented in the sample. |
Hello, with DoIT's NodeMCU32 (1st one with less pins) this works fine ->
|
This does not work for me, if I comment out that line in platformio.ini ESP32 board craps out and does not run code. Barfs something about falling back to internal interpreter. |
@mozgy Can you share the message, I'm thinking it may be related to resource constraints on your device. RTL_DEBUG mode is resource intensive. |
Something strange is going on here -
Will test more later .. |
This is a great idea, but I just can't get it to work. I'm pretty sure the basic connections are correct. I've connected my cc1101 board to RF test equipment and verified that it basically works using TI's Smartrf studio and a CC-programmer. It's definitely a 433 Mhz board and not a 866 Mhz board (power output on 425 Mhz is .66 milliwatt, but only .022 milliwatt on 853Mhz). The measured transmit frequency on 433.92 Mhz is about 20Khz high. I've tried recompiling the code for 433.90 and 433.94 but that didn't help any. I have a Acurite 00592TXR temperature sensor outside of the house which is picked up fine by the Acurite base station in the next room. Ages ago I played with an actual RTL dongle and using the same external antenna I was able to decode several devices from my neighbors as well as my own. I'm building from the master branch of the repo, hopefully that's correct. Here's my log. Can you give me some guidance on what to try? Thanks! |
One of my findings with the board is receiver sensitivity, I find that the range that it receives signals is about 50% of a usb-sdr or the accurate receiver. |
What bandwidth do you set the receiver to? Do you think off frequency is the issue? 20Khz doesn't seem all that bad if the receiver is wide band. I'll try bring in my temperature sensor and see if i works in the same room. |
Well that was the problem. With the sensor in the same room it works fine! Kind of disappointing, but at least it works!
Thanks for the fast response! |
Hi!
LSatan and I are trying to test your rtl_433 example, but we can't get it to work
I think the documentation is a bit sparse and causes confusion
Can you tell me the full process to make this work?
Thanks!
The text was updated successfully, but these errors were encountered: