Hi,
maybe you could fix the configurator V2.10 earlier versions of the configurators like 2.00 were working fine. I think anybody else would have a similar problem. I think it is the resolution… (see screenshot) https://imgur.com/a/MR0BfG2
Please add a wiring diagram. I’m already confused. 1.91 works fine if RX goes to PPM pin on Taranis Q X7, M0 to S-Por. I select SBUS on Taranis and receiver, RSSI works and telemetry data is transmitted at 9600.
With firmware 2.10 I can’t use this, Taranis swears for a weak signal.
Please add a wiring diagram. I’m already confused. 1.91 works fine if RX goes to Taranis Q X7 hardware, M0 to S-Por. I select SBUS on Taranis and receiver, RSSI works and telemetry data is transmitted at 9600.
With firmware 2.10 I can’t use this, Taranis swears for a weak signal.
wow, really cool.
Maybe you can make version compatible with 32 bit stm L0 mcu ? Or maybe event something really small and unique stm32wle5 with embeded lora chip…?
Kris
I flew this system with telemetry disabled on the standard frequency grid (default) in rx silent mode . During the flight (approximately every 2-3 minutes), failsafe was turned on for a few seconds (the engine was turned off, the corresponding indication was displayed on the fpv monitor). The LRS 2.1 was connected to the fs-ia6b receiver via a transistor inverter (repeater). What can be the reason for the loss of communication at a distance of about 300-400 meters?
It’s just that this unit was separately attached to a branch, and I was carefully looking at the fpv screen and could not be distracted by the repeater. And so with this version, the plane at least took off (unlike 2.0, where due to constant glitches, it could not even take off)
You can’t communicate an e32 module with e220 module and e32 has a stm8 chip which can be reflashed using st-link but e220 don’t use this chip so you can’t flash with the st-link. I don’t know if you can flash with other tool.
Qczek 2.1, Inav 3.0 – Mavlink telemetry not returning from RX to TX. May be this is because inav 3.0 uses mavlink 2.0 version. Same setup works fine in inav 2.61!
Hi,
maybe you could fix the configurator V2.10 earlier versions of the configurators like 2.00 were working fine. I think anybody else would have a similar problem. I think it is the resolution… (see screenshot)
https://imgur.com/a/MR0BfG2
Yes, mee too 🙂
Hello, why is PPM not supported on the transmitter? How can I connect it directly to Radiolink AT9S hardware via the trainer port?
2.1, TX module 915, sbus – LED (M0) always on. RX module LED blinks 4 slow, 4 fast. Nothing happen im receiver tab in inav.
Please add a wiring diagram. I’m already confused. 1.91 works fine if RX goes to PPM pin on Taranis Q X7, M0 to S-Por. I select SBUS on Taranis and receiver, RSSI works and telemetry data is transmitted at 9600.
With firmware 2.10 I can’t use this, Taranis swears for a weak signal.
Please add a wiring diagram. I’m already confused. 1.91 works fine if RX goes to Taranis Q X7 hardware, M0 to S-Por. I select SBUS on Taranis and receiver, RSSI works and telemetry data is transmitted at 9600.
With firmware 2.10 I can’t use this, Taranis swears for a weak signal.
please ask your question using rcgroups topic…
Can you please explain difference between
Mavlink enc. + SPORT MASTER
and
Mavlink enc. + SPORT SLAVE?
It’s easy, if you connect directly to taranis, choose sport master, if you connect as relay to frsky rx choose slave 😉
Thank you! When I connect as relay to frsky rx – I must use resistor 1 kOm?
yes, you have to.
Can you please compile PPM version for 915 Mhz , 2.1 release? Now getting popular remote control like that: https://www.banggood.com/Payne-Open-Source-DIY-Remote-Control-Transmitter-Kit-With-PPM-Output-For-RC-Airplanes-p-1225954.html?rmmds=myorder&cur_warehouse=CN&ID=532401
please use 868MHz compilation instead…
Hey!
See my free pcb for qczek!)
https://github.com/whoim2/qczek-E32xxxTy0s-pcb
wow, really cool.
Maybe you can make version compatible with 32 bit stm L0 mcu ? Or maybe event something really small and unique stm32wle5 with embeded lora chip…?
Kris
I flew this system with telemetry disabled on the standard frequency grid (default) in rx silent mode . During the flight (approximately every 2-3 minutes), failsafe was turned on for a few seconds (the engine was turned off, the corresponding indication was displayed on the fpv monitor). The LRS 2.1 was connected to the fs-ia6b receiver via a transistor inverter (repeater). What can be the reason for the loss of communication at a distance of about 300-400 meters?
what does RX led show?
Is it stop blinking fast?
It’s just that this unit was separately attached to a branch, and I was carefully looking at the fpv screen and could not be distracted by the repeater. And so with this version, the plane at least took off (unlike 2.0, where due to constant glitches, it could not even take off)
I am asking for compilation of the newest version for lora 433 version 1.1? thank you very much
what do you exactly mean?
I have a lora e32 433 module but in the older version with 2 pins and I want to use lrs 2.10, I need hex files, that’s it
can i use E220 / LLCC68 instead of E32 / SX12nn?
Thanks
You can’t communicate an e32 module with e220 module and e32 has a stm8 chip which can be reflashed using st-link but e220 don’t use this chip so you can’t flash with the st-link. I don’t know if you can flash with other tool.
Can I use E220 / LLCC68?
Thanks
Hi. Do you provide sources for your awesome project?
Qczek 2.1, Inav 3.0 – Mavlink telemetry not returning from RX to TX. May be this is because inav 3.0 uses mavlink 2.0 version. Same setup works fine in inav 2.61!
yes, the mavlink 2.0 is not supported