RFQuak ESP32 w/CC1101 #2
Comments
|
Hi @dgeppert - I'd suggest to try the HSPI. @Guglio95 you used RFQuack with an ESP32: do you by any chance recall or have a picture of your SPI wiring? |
|
same with SPI and HSPI: |
|
@dgeppert can you edit the and run the |
|
replaced the last line in and ran but strangely do not see the effect of maybe I misunderstood? |
|
btw I only downloaded your docker, did not build it |
|
Do you have any other way to see the content of main.cpp?
…________________________________
From: dgeppert <notifications@github.com>
Sent: Monday, October 12, 2020 12:40:04 PM
To: rfquack/RFQuack <RFQuack@noreply.github.com>
Cc: Federico Maggi <federico.maggi@gmail.com>; Comment <comment@noreply.github.com>
Subject: Re: [rfquack/RFQuack] RFQuak ESP32 w/CC1101 (#2)
btw I only downloaded your docker, did not build it
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#2 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AABPCNGYDXPWANEIVP4DYP3SKLMIJANCNFSM4SMRVFDQ>.
|
|
sorry, I do not know where to find it. btw I build RFQuak and RFQuack-cli from source, I up to now have problems to get e.g. and I noticed that in this example the platformio.ini points to the old v1 whereas I use a v4: maybe this was used to build the docker container and this causes the problem? |
|
Ciao! |
|
ciao Guglio, yes I am using a newer devkit v4 : az-delivery-devkit-v4 I am trying to build from an example using platformio, but need some time to learn I do not want to get this issue too long, maybe I will come back later unless you do have some other idea |
|
@dgeppert using PlatformIO directly is best because running PlatformIO into Docker will give you less control. Can you share the error messages you mentioned? No problem for making this issue long ;-) the longer it gets, the more informative it will be for the future! |
|
Hello @phretor well you asked for it and it happened that I just prepared this post ;-) here we go: here the log file: thanks for your help! |
|
I forgot to mention that if you go the PlatformIO route there are a couple of oddities you should be careful of. There are multiple errors there, but let's try to rule them out one at a time:
|
|
gracie, I will give it a try for waht concerns the last bullet, does this test make sense and the versions seem ok? [dirk@t520 RFQuack]$ rpm -qa | grep protobuf |
|
Sort of OK. The last bit to check is that |
|
scratched and reinstalled platformio as before, now checking out the official version: |
|
however a successive pio run still results in the same kind of errors however, this one kind of looks strange to me. any idea? |
|
Oh, I get what's happening! You clone the repo, you generate the .h file from the .proto by running Can you verify this? |
|
make proto generates new after I am not sure what the example compilation it also clones the following from git: but it seems it does not clone again, but copies from the local directory: are you able to reproduce this build problem if you perform the same steps, i.e. reinstall platformio, checkout RFQuack, install the RFQuack libraries into the platformio and the try to build an example? |
|
for what concerns the proto error messages: before
but later in there are also some references to installing the same nanopb master, now the error messages are much less, but from the error messages it seems to me that code development advanced and not everything for all classes was consistent, e.g. the missing _br for CC1101 and some more missing (inherited) methods. so maybe a consistent version of packages would make it possible to compile the examples. |
|
@dgeppert correct - all the refs should be updated from "trendmicro/rfquack" to "rfquack/rfquack". Good move to upgrade to nanopb@master (someone should definitely update the instructions, but time lacks on my side: feel free to send a pull request if you have time, or get someone involved to help building some community around this tool). Do you mind posting the output of the building process after you upgraded to nanopb@master? You mentioned you get way fewer error messages, but still getting some: I'm curious to see those! |
|
here the requested log:
the same kind of errors show up in successivly compiling other radio modules, the main problem seems the private bitrate variable hth & cheers |
|
Spot on! https://github.com/rfquack/RFQuack/blob/master/src/radio/RFQCC1101.h#L205 @Guglio95 can you check whether you forgot to commit some changes? That looks to be part of RadioLib - so maybe it's a fork that we forgot to PR to RadioLib? |
|
Hi everybody! I tried to compile from source and diagnosticate the errors. I succeeded in finding the cause and fixing them. Basically there are some inconsistencies in (our version of) RadioLib:
I corrected these problems and now it works flawlessly by my side. FYI I compiled and flashed using |
|
Hello Alessandro @FiorixF1, many thanks for your efforts bringing the repos in consistent states again. I had to look up the different commands I used to build: However, I still get error messages in the build of the CC1101 example, please see the attached log file: RFQuack_compile_run_20201128a.txt If it works for you, what are you doing different (and I am doing wrong ;-) ) Best regards, Dirk |
|
Sure. I modified this repository, but also RFQuack-cli and RadioLib. My PR here has been accepted, but those in the other two repos not yet. So I ask @phretor or @Guglio95 if they can accept them, since they are necessary to fix the errors. In the meantime, you could use my fork here for the CLI, and change "https://github.com/rfquack/RadioLib" in "https://github.com/FiorixF1/RadioLib" inside To compile the examples, I copied If the compilation and flashing are successful, you should be able to communicate with the dongle using the CLI with the command |
|
Hello Alessandro @FiorixF1, yes, this looks so much better!!! using your RadioLib fork I could successfully compile and upload to my ESP32. then using your RFQuack-cli (and fiddling around to set up a penv for Python 3.8) I could get into RFQuack: However now I need to check the cabling between the ESP devkit4 (probably much different from the older Arduino Feather / devkit1) and the CC1101 module since the communication does not seem to work. But that's a project for another day ;-) btw a small comment (no complain): RFQuack Readme.md contains some photos of the modules but not the cabling. Maybe if familiar with the Ardafruit playground this is obvious. I had to find the module descriptions and and kind-of reverse-engineer to make a guess how it could be cabled to adapt it to my actual ESP. Many thanks to the team for your help getting this compiled and run. A fun project! Maybe I will try to make it talk to the Yardstick One which I bought in the meantime. Mille grazie e a piu tardi! P.S. I do not close the issue until Alessandro's fixes make it into the corresponding project masters, but of course you may just close it if you think it's been solved. |
|
Also relevant if you're using CC1101 - jgromes/RadioLib#208 |
|
@dgeppert: Have you figured out the correct cabling? @phretor: I also got the ESP32_Devkitc_V4 and even two CC1101 (one optimized for 433Mhz the other for 868MHz). Could both transceivers be connected to my esp32? Could you please provide a reference cabling along with corresponding init commands? Have all repos been aligned already? How does this project compare to SignalDuino (running on an ESP32 it also utilizes a CC1101 to decode yet unknown signals) in terms of visibility of unknown signals? I've got a 868MHz doorbell unfortunately not visible by the former project. Similarily with Somfy protocol. |
|
hello @TheChatty I connected the CC1101 to az-delivery-devkit-v4 VSPI bus, see the pinout diagram depending on if you are using Docker build/run or one of the examples:
however, I am using RadioLib and RFQuack from @FiorixF1 because I experienced compilation issues. and somhow my CC1101 uses the legacy hth |
|
Just checking if this issue needs any other actions or we could close it. Please check the new Dockerfile (I just committed here) and respective images I just pushed (to Docker Hub). |
|
Hello Fede, great to see you aligned to RadioLib and all compilation issues disappeared. I just ran the latest docker hub images for rfquack and rfquack-cli and also built local ones, all ran and compiled well for ESP32 and CC1101. Great to see this progress and efforts, now one may actually start the interesting stuff: using RFQuack! mille grazie |
|
@dgeppert: Thank you so much for helping out. You saved myself a lot of time for research. When I finally started the CLI along with the baud parameters I could eventually use q.guessing.start() to see non-chunked output while pressing some remote control buttons. May the quacking begin. |
|
@TheChatty |
|
With RFQuack I could only see receiptions from remotes which also worked with SIGNALDuino (all with 433 MHz). My doorbell (868 MHz) was not visible (I changed the frequency of course). But I found the general usage of RFQuack quite unintuitive and not well documented thus I gave up. |
Can't agree more 😄 RFQuack is meant to be generic rather than a tool that works out of the box, so the learning curve is definitely steeper. Documentation may really help, but my time (like everyone else, I'd say) is very limited. If anyone is feeling to contribute with some doc improvements, PRs are more than welcome! 🍻 |
Using the instructions in Git I managed to flash the ESP32 using the rfquack/rfquack docker and connect via rfquack/cli docker:
However, the CC1101 connected via the ESP32 VSPI seems not to be correctly initialised, the cli only reports Select a dongle typing: q.dongle(id) i.e. no radioA object is available.
Using other software I manage to communicate with the CC1101 and exactly the same setup, so I wonder if RFQuack uses a different way to connect the ESP SPI? From the instructions and the photos I found, I unfortunately could not deduct the cabling.
q.[tab completion] only proposes:
connecting via screen and pressing RESET show:
I wired up ESP32 VSPI (MOSI GPIO 23, MISO GPIO 19, SCLK GPIO 18, CS GPIO 5, GDO0 GPIO 4).
which SPI bus RFQuak is using? seems there are three; SPI (used for flash, so usually not recommended), VSPI and HSPI
as far as I understand all three SPI, VSPI, HSPI are h/w SPI.
currently I am using VSPI, last night I tried SPI but no success, maybe try again. which SPI bus i.e. GPIOs RFQuak using?
Devkit-v4
Using a second set of h/w results in the same problem.
Thanks in advance for your help on this issue!
Regads, Dirk
The text was updated successfully, but these errors were encountered: