#ELRS 433 MHz
112 messages · Page 1 of 1 (latest)
This is a very vague question - what hardware do you have?
and esp32
Well, that module is UART not SPI so...
Can you send me the necessary equipment?
Why do you want to build 433MHz rather than using commercial hardware? TBH it sounds like you're in a little over your head. 😅
I need a frequency below 700 MHz
Spi...
The E22-400T30S you sent is UART. So which one do you have?
I looked, and on some of them there is spi, but somewhere it is missing. How can I upload firmware and subsequently add an OLED monitor?
Which firmware you upload will depend on how you wire up the SPI pins
You'll also need to build custom firmware with the regulatory domain set. Where will you be using this? Australia, EU, US, or something else?
Australia
the module you described will need another microcontroller to handle the translation between the data received/sent to functional input/output as well as the code for the OLED. what's the full scope of your project?
Okay, follow this guide:
Right now, I want to set up ELRS on 433 MHz, and then add an OLED screen if it's not too complicated.
So, let's be very frank:
"I want to build a car. I have these tires, and an engine. I want to add a gauge cluster too."
Well, what you have are motorcycle tires, and your engine is four pistons and a crankshaft. We need you to meet us halfway. Which ESP32? Are you gonna solder the EByte modules to the ESP32? Is this the RX or TX side you're doing first?
Firstly, I want to make the TX side, for this I will use the E32-400M30S and this ESP32
Follow this, wire up the pins as laid out here: https://github.com/ExpressLRS/targets/blob/master/TX/DIY 900 E19.json
You may need to change a few, we can help with that if you tell us which you can't find.
For the receiving side, I want to use the E32-400M20S and the ESP32 SuperMini. or DIY board
"I don't understand why as many as 5 parameters relate to pin 2. And what are these pins:
"power_rxen": 13,
"power_txen": 12,
"power_min": 2,
"power_high": 4,
"power_max": 6,
"power_default": 2,
"power_control": 0,
"power_values": [114,117,120,124,127],
And there are no such pins in the ESP (114,117,120,124,127), and why are there several of them?"
Sorry that I'm so slow, but for me as a web developer, this is a new world that I'm very interested in.
they wouldn't be pin declarations but other variables set for the rest of the code you'll be uploading
you'll be hooking up the transmitter module to the pins specified in the configuration file then building the firmware with the ELRS configurator.
Those aren't all pins
also I'd reccomend maybe trying to build for https://github.com/ExpressLRS/targets/blob/master/TX/DIY 900 TTGO V2.json, it has support for a IIC display built in on pin 21 and 22
Thank you, but how can I generate firmware for 433?
besides the hardware difference to modulate 433MHz and 900MHz, is there any difference in how the controller talks to the radio module? I would think a 900mhz build should work for 433 if there isn't any commands that specify the frequency used apart from values on a table
No, everything else is the same
Alright, so for them flashing the TTGO 900mhz build from the ELRSConfigurator should work well with an ESP32 and IIC 128x64 display
If the pin assignments are the same and they use the correct regulatory domain
what board are you using for the RX? @gusty python
so i got the firmware for the esp32 900mhz flashed to a ttgo v1 as a receiver and a esp module with that lora chip and a IIC display as a transmitter. both are connected over seial to my computer but I'm getting just nonsense at 420000 baud, is there something else i should be setting it to?
When you say nonsense, what exactly are you expecting to see? CRSF is a binary protocol.
a boot sequence log, I have the ttgo plugged into my computer through a ftdi chip and I'm getting a "brownout log" at that baud
How are you powering it? Just via FTDI?
for now yhea, the brownout warning is obviously no good but it's an indication of readable output
Use a different power supply
Make sure you keep a ground connected to the FTDI though
👍 trying to figure out a way to see if I'm sending/receiving properly over the link
ah, Alessandro made some CRSF package generation scripts for arduinos, looks like I'm going to have to get 2 more microcontrollers to get any data 
Why? What are you using now?
endgame is using 915Mhz lora modules to make a backpack for my radiomaster boxer to drive a RC tank
I just have the receiver/transmitter wired up to 915Mhz modules and serial to my computer on both of them to see if it's kosher
I don't want to threadjack so I've been keeping it to flashing and using low frequency lora modules as per the original post
For the receiving side, I want to use the E32-400M20S and the ESP32 SuperMini. or DIY board
Can I use a ready-made BetaFPV ELRS 900 receiver, which has an SX1276 module with a frequency range from 137MHz to 1020MHz?
Can I reflash the HappyModel 900 TX to work on 433?
normally if it's not software defined radio the range of a tranceiver is limited by the RC circutry, I think even if the sx1276 is designed to handle that range it's with other passive components that dictate what the actual range is
Not without modifying the hardware. 900 MHz hardware uses the RF_HF output, and has a 900MHz filter network, while 433MHz would need to use the RF_LF output and have a different filter network
Understood
Why the requirement for <700MHz?
As for the firmware for the 433 module, should I use TTGO 900MHz?
that would probably be the closest thing to it, I've been trying out some things on my own along those lines but nothing came ut of it yet
Just use the unified target matching your hardware and then edit the pin definitions in hardware.html
I installed equipment operating at 900 MHz on my airplane, and it jams the transmitters. 2.4 GHz is too high a frequency, and I need to fly close to the ground. I even have a 15-meter mast.
But this equipment emits a lot of noise on other frequencies, so I need a transmitter on 433 MHz
any way to sheild the equpment?
There are omnidirectional antennas installed, and the main unit is in a ventilated case, otherwise it overheats during flight.
I'm building for the unified firmware for esp32 right now like V22 suggested, looks like through the hardware page i can just set my pins so fingers crossed I won't have to do any more soldering.
Shouldn't higher frequency work better then as the Fresnel zone is smaller? What are you using for video?
2.4GHz is too high a frequency
Too high for what?
Wavelength: The lower the frequency, the longer the wavelength. Longer radio waves can better circumvent or penetrate obstacles than shorter waves.
Absorption: All materials absorb radio waves to some degree. At higher frequencies, such as 900 MHz, materials like brick or concrete may absorb radio energy more than at lower frequencies, such as 433 MHz.
Scattering: At higher frequencies, radio waves are more prone to scattering on irregularities and small objects. At low frequencies, waves are less sensitive to such small obstructions.
Refraction: At low frequencies, radio waves can bend around obstacles or penetrate them better due to the phenomenon of refraction.
... You're talking to a chat full of very experienced people.
By "too high for what", what I mean is "what analysis have you done that says it wouldn't work for your use case?"
The video transmitter is located in the payload block at 900 MHz.
In other words, where's your free-space path loss calculations? Your fresnel calculations? Your clutter models?
2.4GHz will perform better lower to the ground than 433MHz due to the fresnel zone's area being negatively correlated with frequency.
I didn't do the calculations, but flying on 2.4, the connection lasted up to 34 km, although with TBS I achieved a greater distance.
Okay... 2.4GHz ELRS? What settings? What antennas?
1W yagi 22dBi
good news, build upload and settings were sucessful on my esp32 / 433MHz build
it's getting late so I'm going to wait till tomorrow to upload and connect the RX version to my radiomaster, then some short tests outputting PWM should say if everything is 100%
So, to sum up, it seems I need to follow this guide (https://github.com/ExpressLRS/targets/blob/master/TX/DIY 900 TTGO V2.json) to make the connection, and then flash it to the TTGO 900MHz?
I wouldn't jump the gun on wiring just yet, I followed the guide for the esp8285 by mistake to the ESP32 and there might be some variance for the pins used
that being said the web page of the receiver lets you inputs LOTS of variables
for better viewing purposes
and don't use the ttgo, the "unified" build seems to be a lot more versatile
... Update rate? LNA RX?
A 22dBi antenna would have a very narrow beamwidth. How did you assure your RX was within its beamwidth?
Your range should be nearly 1000km with a 22dBi antenna and 1W TX power... So I suspect your antenna did more harm than good.
I say this as one of the very few people using 433MHz ELRS, with my own custom board designs to do Gemini 433MHz.
2.4GHz is the right solution for 99.999% of cases. I'm worried you're jumping to conclusions and adding significant complexity where it's not needed.
Alright, I'll add an antenna tracker to the 2.4 GHz setup, but I also want to make a transmitter and receiver on 433 MHz.
Tbh, just run a lower gain antenna. A 5dBi moxon is more than enough for tremendous range.
that looks amazing @fiery spoke
I'm going to resolder my receiver today, do you recommend me going with the hardware SPI0 pins or with the pins in the gemini .json file?
@gusty python I got it all workin! lmk where you're at with yours and i can tell you where to go
Hello! Sorry for the long silence. Can you send me photos of how you soldered everything and how you loaded the firmware? I tried to figure out PlatformIO and VSCode, but I still couldn't get it to work.
Hi. Anyone tried changing carrier frequency by chnging RegFr values?
Let say I have 433MHz lora and want to use 900MHz target. If 900 carrier is too high 750MHz should work with HF filter without hardware modifications... Theoreticaly
the 900 target is the same for all of the sub ghz, you can just change the regulatory domain in the settings
From the html page of the "generic_900" target
The soldering is using the hardwareSPI ports for 50% of the connections, the reset and di0 I put on pins that were close to them and available for basic GPIO functions.
I'm going to be using that one in the pic for something with lots of PWMs, I ordered a 1W 433mhz transceiver for the external module of my controller which will be paired with a WeMos D1 mini because all of the connections plus a sbus can be achieved with it's limited amount of pins. Plus they're cheaper $$
If you intend to use the standard frequency, yes. But what if you like to have carrier frequency 550MHz for example? In this case perhaps you need to change the registers defining it in 1278 driver lib
Not sure if it'll work. But I'll try this out...
550mhz might be too big of a mismatch for the RC hardware. Check on the datasheet to see how much power it'll actually put out on that frequency
I'll check this out;)
550MHz is not a frequency you are legally permitted to use.
that's a issue as well. @fiery spoke I see you've made most of the firmware for VRx backpacks, I'm struggling a bit to adapt it for a headtracker. Do you have time to help?
most of the firmware
Uhh I've made a few contributions that's all
I have a headtracker firmware that takes in sbus and outputs ESPNOW HT, is that what you want?
that would be a great help, I'm going to try to skip the SBUS part and just do reads from a MPU6050 and then.... smoothing algorithms 🙃
Hopefully an esp01 has the firepower for something like this, the disable/recentering with a controller aux makes it feasible to implement on something that only has 2 usable GPIOs
It's beyond overpowered for this 🤣
lol, they're so cheap and I've been using them for the most menial things