-
|
Here are a few pics of the gear I'm trying to set up: And here's the code I'm running on this ESP32 D1 Mini (it's a modified version of /*
RadioLib Non-Arduino ESP-IDF Example
This example shows how to use RadioLib without Arduino.
In this case, a Liligo T-BEAM (ESP32 and SX1276)
is used.
Can be used as a starting point to port RadioLib to any platform!
See this API reference page for details on the RadioLib hardware abstraction
https://jgromes.github.io/RadioLib/class_hal.html
For full API reference, see the GitHub Pages
https://jgromes.github.io/RadioLib/
*/
// NOTE: I have modified this file slightly
// include the library
#include <RadioLib.h>
// include the hardware abstraction layer
#include "EspHal.h"
// create a new instance of the HAL class
// (we're just configuring SPI here)
// SCK: 18
// MISO: 19
// MOSI: 23
EspHal *hal = new EspHal(18, 19, 23); // SPI pins for my Wemos ESP32 D1 Mini + SX12662
// now we can create the radio module
// NSS pin: 18
// DIO0 pin: 26
// NRST pin: 14
// DIO1 pin: 33
// SX1276 radio = new Module(hal, 18, 26, 14, 33);
// NSS pin: 5
// BUSY pin: 33
// NRESET pin: 4
SX1262 radio = new Module(hal, 5, 33, 4, RADIOLIB_NC); // for my ESP32 D1 Mini + SX1262. It works, kinda
static const char *TAG = "main";
// the entry point for the program
// it must be declared as "extern C" because the compiler assumes this will be a C function
extern "C" void app_main(void)
{
// initialize just like with Arduino
ESP_LOGI(TAG, "Initializing ... ");
// radio.XTAL = true; // it seems I need this for the particular SX1262 module I'm using
// but alternatively I can pass a 0 as the 8th argument to radio.begin()
int state = radio.begin(868.0, 500.0, 6, 5, RADIOLIB_SX126X_SYNC_WORD_PRIVATE, 22, 6, 0, false);
if (state != RADIOLIB_ERR_NONE)
{
ESP_LOGI(TAG, "failed, code %d\n", state);
while (true)
{
hal->delay(500);
}
}
ESP_LOGI(TAG, "success!\n");
// this message is 255 bytes
const char* msg = "The Union Of Conscientiously Workshy Elements, a humorous critique of the relentless "
"glorification of hard work, celebrates intentional idleness and the joy of leisure, "
"advocating for a society where relaxation is esteemed, as is the art of doing nothing.";
TickType_t wakeup = xTaskGetTickCount();
// loop forever
for (;;)
{
// send a packet
ESP_LOGI(TAG, "Transmitting packet ... ");
state = radio.transmit(msg);
if (state == RADIOLIB_ERR_NONE)
{
// the packet was successfully transmitted
ESP_LOGI(TAG, "success!");
}
else
{
ESP_LOGI(TAG, "failed, code %d\n", state);
}
// transmit every second
xTaskDelayUntil(&wakeup, 1000 / portTICK_PERIOD_MS);
}
}It kinda works. Here's the output: With the pins assigned as I have them now, I can get the SX1262 transmitting the 255 byte message at a maximum rate of once per second (1000 ms). I am picking up the RF signal on my RTL-SDRv4 hooked up to SDR#, and also receiving the message (some of it, anyway), with a Heltec Lora V3 ESP32-S3 SX1262 also running RadioLib but in Arduino framework. So this works, but if I try to get it to transmit the message more frequently (by altering the call to xTaskDelayUntil()), nothing changes. It refuses to go faster. So I think I am not assigning the pins correctly, particularly those carrying interrupt signals. The mystery SX1262 + PA module has six pins whose purposes I am uncertain about, namely: All I know so far is that connecting the BUSY pin seems to need to be passed as the I would be most grateful if someone could explain how these pins should be connected, and if there's anything else I need to do to ensure that the PA is enabled. Eventually I'd like to replace the ESP32 with an ESP32-S3 while staying wholly within the ESP-IDF API, but that's for the future. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
|
Wow, a LoRa setup with Nitrous AND go-faster stripes! This is over expectation of hardware with sprinkles and some handcuffs & court fines. There will be a good technical reason why it can only do one message per second, but there's no point looking at the why because in the EU you can only send 256 bytes at DR6 once every 20 seconds and then only at 14dBm. In fact there are no jurisdictions in the world where you can use a shared ISM bands to send that frequently. At that power level & send time you will probably get a reduced fine if you just hand yourself in now, because you will be very easy to find with a directional antenna surrounded by all the other users you have enacted a denial of service on, they will be the angry ones with pitch forks. It seems strange that you are pushing the pedal to the metal but don't understand the use of the BUSY & DIO pins. They are the carburettor in this V24, managing the flow of fuel/data. And that first picture, what the heck? As you need to go at least a 20th the speed with a vast reduction in power, there is nothing to help with, iIn summary, this is not the technology you are looking for, neither the radio, the library or the frequency fit with shifting lots of data in the way you want. |
Beta Was this translation helpful? Give feedback.
-
You mean the pine furniture? |
Beta Was this translation helpful? Give feedback.
-
|
The blank metal with a uFl connector - didn't convey much information! |
Beta Was this translation helpful? Give feedback.
-
That can be expected, take a look at the timestamps in your log: As you can see, it takes 900 ms just to send the packet - which is quite natural, since it is huge. I would also like to point out that since you are using 500 kHz bandwidth and transmitting as fast as you can, you have effectively built a jammer. Your local authorities may want to have a word with you about that, since now you have rendered the 868 band useless, at least in your vicinity ;)
This is all shown in the SX126x examples.
Seeing as you have built a jammer and are actively trying to make it as loud as possible - no, I don't think I will. |
Beta Was this translation helpful? Give feedback.
-
Ah thank you :) I should have checked these. I'd focused on the single ESP-IDF example, forgetting there are more available specifically for the SX126x. I think I've figured out BYP, EN, BUSY, DIO1 and DIO2 now. It's lucky you pointed out that I was rather overdoing the transmission. I'll only test the gear out again when I next go spelunking, particularly the PA. |
Beta Was this translation helpful? Give feedback.
@imfatant
That can be expected, take a look at the timestamps in your log:
As you can see, it takes 900 ms just to send the packet - which is quite natural, since it is huge. I would also like to point out that since you are using 500 kHz bandwidth and transmitting as fast as you can, you have effectively built a jammer. Your local authorities may want to have a word with you about that, since now you have rendered t…