Heltec ESP32 LoRa v3 (using SX1262 radio) does not work #10
Comments
|
@SamKirsch10 I created a new branch, 'idf.py' with a few changes that might solve the issues.
Please try this branch and see if it works. The git submodules have changed, so you may need to ensure the sx127x driver gets updated after you checkout the new branch. It should build without any errors or need to modify anything. I don't have an S3, so I don't know for sure if it solves the problem. Give it a try and let me know if it works. If it successfully builds/flashes, but doesn't function as expected, please keep the device connected to your computer and paste the output of Thanks for reporting the issue and helping me get it resolved. |
|
I found this schematic of the V3. You'll need to modify the SPI pinouts (via |
|
Yeah, I dove into the schematic last night and got the following. Will try that branch in a minute and report back! Thanks!! |
|
It looks like the app crashes with the below trace. Looking around, I think the V3 actually uses the |
|
I just pushed a commit to the dev branch that adds a configuration option to use a SX126x library. Be sure to rerun I don't have the hardware to test it on, so I can only promise that it will compile without error. There are certainly going to be runtime errors/crashes of some sort, but the logs should help identify them. |
G-Two
changed the title
|
I just got my hands on a Heltec v3, and the SX126x driver is not working at all. I receive a similar SPI error described here and here. I'm changing the title of this issue to reflect that (and since idf.py is now fully supported). When I get time, I'll dig into the SX126x datasheet and try to get the driver working with the Heltec v3. |
|
@SamKirsch10, just letting you know that this now works with the Heltec LoRa 32 v3 as of commit 27638dc. Give it a try and let me know if you still run into problems. Thanks to @Glowman554 and @nopnop2002 for getting the SX126x driver working! |
|
I have the same device and am having issues. I got everything to compile and flash, but I'm not able to actually pair it with the Smoke X2. When I put the Smoke into Sync mode, nothing happens on the Heltec. |
|
@omrishiv can you run Here is my output from a successful sync using a Heltec ESP32 LoRa v3 and a Smoke X2: |
|
I'm just seeing |
|
Can you reset the device and paste in the SPI setup output that happens early on? Similar to what is below: Can you also paste the very beginning that shows your chip ROM version and IDF version? |
|
|
Everything looks good in your logs as far as ESP32 configuration goes and the radio seems to be properly switching between the X2 and X4 sync frequencies. Maybe there's a problem with the X2 transmitter? What does the X2 show on its LCD display when it is in sync mode? I guess there also might be a chance that your X2 has a different software revision that uses a different sync frequency. Do you have any RF gear to check for the sync bursts in the 902-928MHz range? When the X2 is in sync mode, there should be a burst every 3-5 seconds. |
|
When in Sync mode, it says Sync for a bit, then END. I have it paired to a receiver, and within the last few weeks, a smoke gateway. I don't have any RF gear to test, but they would have had to submit something to the FCC, wouldn't they? |
|
For reference, the FCC ID on mine is: 2AI67-TX1300CH |
|
My Smoke X does have an FCC ID (2AI67-S2T) but the documentation just says that the device operates in the US 915MHz ISM band. The sync function requires the radio to be tuned to a very specific center frequency within that band to capture the sync burst. This frequency is known to vary between models (which this code accounts for in the X2 and X4 models). The sync is a 2-way handshake that informs the receiver to switch to another frequency and the receiver is actually required to transmit an acknowledgement to the transmitter before the sync mode will end (otherwise it will stay in sync forever). |
|
Ah...I see with your FCC ID that you have a Thermoworks Smoke and not a Smoke X. These two devices use different radio technologies (Smoke X uses LoRa). This code will only work for the Smoke X. There is another repo that might be helpful for your Smoke/Gateway: |
|
ARGH! Yes, thank you. The naming is awfully confusing. I've actually looked through that one given I have a smoke gateway, but the code doesn't work. I tried to update it myself but am not knowledgeable with firebase and prefer to have everything local, so found this repo. Too bad. Thanks for the help and sorry for the confusion. |
|
No problem, I agree the naming isn't the greatest! Depending on how much work you want to do, you could always pick up where this project stopped: https://hackaday.io/project/160386-blanket-the-smoke-signal-gateway |
|
Yeah, while that could be fun, that's a bit beyond my abilities; I'll keep working on trying to fix the python integration. |
|
Hello , Please suggest me the possible solution |
First of all, I have had a SDR radio dongle and have been trying to decode these for forever, so thanks for this project!! Unfortunately, the LoRa device I bought is S3, and from reading lots of github issues, the
makeusage for the esp-idf is deprecated. So using theidf.py build flash monitorcommand, it errors about a missing lora file. After moving the lora component directory to the esp-idf component directory, I'm met with a lora.c error that I can't get past...If I change that variable to the suggested
SPI3_HOSTit does build, but the program never syncs with my unit, so I assume that's wrong. Any insight is incredibly appreciated!-- EDIT --
Looks like the S3 chip does use the SPI3_HOST var, so something else is amiss here... This is the one I bought. Looks like it's the Heltec V3, so probably there's a pinout difference? I can't figure out what matches what since the names don't match. Here's that pinout.
The text was updated successfully, but these errors were encountered: