-
-
Notifications
You must be signed in to change notification settings - Fork 127
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 RX127X Transceiver Chipset #11
Comments
really nice, @SensorsIot feel free to subscribe if you want to follow |
Done. I am interested in the results... |
Research notes for the build 1 - Searching thru GitHub found a few libraries and packages supporting the chipset but on first pass did not find one that used ask/ook/fsk mode everything appeared to be geared towards LORA. May need to craft my own library from scratch unfortunately, but could use the cc1101 library as a base. 2 - Need to use continuous mode ( this is similar to asynchronis mode on the cc1101 )
3 - Signal RSSI is available here
4 - Digital IO PIN Mapping
|
If I am not mistaken this model has DIO2 connected to an OUTPUT only pin of the ESP32 which makes it unsuitable for our use |
Good question Looking at this diagram - https://resource.heltec.cn/download/WiFi_LoRa_32/V2 it appears that the RX127X DIO pins are wired like this DIO0 - GPIO26 I snagged the ESP32 GPIO details from here - https://randomnerdtutorials.com/esp32-pinout-reference-gpios/ What materials are you looking at ? PS Looking at my personal calendar, this will be on hold to the fall, the need to carve out time to write the library put a damper on quickly checking out the feasibility with a POC code. Need to enjoy the Canadian Summer |
My bad, it's an Input only! I remember now I had to discard this model because I also needed to output signal in my project! |
We (in my company) have created an open source IoT node that listens to weather station RF packets and forwards over WiFi/GSM. We use RFM95 lora modules on ESP32 to sniff the packets, so @NorthernMan54 you are on the right track :-) https://github.com/exmgr/exm-iot-node-firmware/blob/main/src/fo_sniffer.cpp We are very much interested in to extending our firmware to support other weather stations too, via rtl_433_ESP, so will keep an eye on this and try to help if possible. |
@NorthernMan54 How is this chipset integration? I have similar chipset from Heltect(without LCD) which I also want to try. |
It is still sitting on the shelf, as I did a quick scan for a library that supported a raw signal mode that handled ask modulation and couldn’t find one. Rtl_433_esp needs to input the raw signal, as the signal decoding is done in software and not on the receiver chipset itself. When I read the chipset data sheet I thought I saw the proper mode listed. |
It is beyond my understanding. |
Well spent some time this week on this and tested out using https://github.com/jgromes/RadioLib instead of https://github.com/LSatan/SmartRC-CC1101-Driver-Lib to interface with a CC1101 module, and was successful. To use the RadioLib library the most noticeable changes to rtl_433_ESP where 1 - getRssi is not supported in direct mode in RadioLib, so needed to provide my own function instead 2 - With SmartRC-CC1101-Driver-Lib it uses GDO2 to receive the raw signal, while RadioLib uses GDO0. Need to adjust this 3 - And for CC1101 deaf workaround, I needed to directly access the module using SPI to Idle and start Receive again. My test/sample code is here https://github.com/NorthernMan54/rtl_433_ESP/tree/4537d15d968e4ef48043ff0ba066d2ca91e8e4c1 in the RadioLib branch. Please note that I short circuit the platformio lib function and symlink to the repo, hence the RadioLib and rtf_433_ESP library is commented out. Now for the next step, try it out with a RX127X module. |
This has been released to production |
I finally received my parts today and am ready to start adding support for this chipset
For parts I have received the 433Mhz and 868Mhz modules https://heltec.org/project/wifi-lora-32/
Stay tuned over the next few weeks for this.
FYI @1technophile
The text was updated successfully, but these errors were encountered: