krzysztofkuczek / qczek_lrs Goto Github PK

Hi, Is it possible to use qczek lrs to transmit location data (lat, lon, altitude, heading, speed)(take data from mavlink telemetry) and receive data from other qczek lrs, like https://github.com/mistyk/inavradar-ESP32, in normal mode?
Data can be transferred to FC (INAV), for example, through the MSP2 protocol, the MSP2_COMMON_SET_RADAR_POS packet (https://github.com/iNavFlight/inav/blob/af08641f9539dbd4275a510accec977c431d4e6b/src/main/fc/fc_msp.c#L2411)

There is also an audible warning: the engines disarmed / engines armed. Sounds are erroneous and do not affect the result. Also the mode switching in LUA to Taranis is not displayed correctly.

FPort is an easy way to connect FRsky Rx as a relay to QLrs TX. RC + Telem by one wire.
https://github.com/betaflight/betaflight/wiki/The-FrSky-FPort-Protocol

FPort will be supported soon by Ardupilot too. Might be a great option to connect QLrs RX to Ardupilot using FPort.

I know that is not easy, but is it possible make version for E32-433T30D 1B ?
New version module E32-433T.. 1B is not based on old good stm8 MCU, but new cortex M0 based Chinese MCU called HC32L110C4UA-SFN20TR https://www.hdsc.com.cn/Category82-1396

Adding a bootloader with serial support will allow us to update the firmware without using STLINK, but even using serial passthrough of FC

As per your request from RCG thread: Also would appreciate a lot if all the math for converting reg values to a correct RSSI in dbm and SNR in db would be done in firmware instead of putting out raw values of corresponding registers to S.Port telemetry feed. They anyway need to be converted on user's end otherwise they are useless.

M0 + M1 + AUX = 3 PWM channels

CDBYTE cały czasz produkuje moduły z 32kb pamięci.

Hi Kris!
The idea of this enhancement is to detect and change most noise affected hop channels.
If resources are still sufficient it can be implemented as packet lost counter for each channel that can be retrieved later with configurator.

This counter will sum all lost packets during the flight (up to an hour or two time) than right after the flight RX must be connected to the configurator and this info will be read from RX together with the settings.
Thanks!

to be investigated, maybe problems with switching frequency?

RSSI and SNR sensors are active and contain correct data. Values of other sensors are received by Taranis, but contain zeroes. Rediscovery of all sensors doesn't help.

Hello Krzysztof,

Is it possible to use FHSS with modules like https://heltec.org/project/wifi-lora-32/ ?

It is convenient that LoRa chip built in one module. I'd like to create something like 3dr radio from this boards.

proposed by RocketMouse
"I would like to propose to make different logic here for no SBUS input. If there is no SBUS-in then it's better to switch TX off. It will be useful for a relay in case radio is switched off, let's say for some flight preparation, and QLRS will also stay off until radio will be switched on again. It will help to keep module cold and save relay powering battery."

There is a discrepancy in the way setting mode is entered for RX and TX which may be confusing sometimes. According to the documentation:

Settings mode is only available, when M1 pin is connected to ground – for TX modules, or M0 is connected to M1 – for RX modules.

To avoid confusion it would would be nice to have it done the same way for both TX and RX.

Bi-directional transparency mode for data transmission to UAVs

Can you support 3-channel pwm signal, because many people's flying wings do not need flight control ppm, they can only be controlled by 3 pwm, but qlrs can only output two-channel pwm signal at present, if the current cppm output can be changed to The third pwm can directly control the flying wings

Im try: 1.92, 2.1 f/w.
I need mavlink from air to ground.
Its work if TX f/w not sbus (cppm/frsky).
On sbus TX pin ground module send zerows.
e32-868t20s air and ground, im try f/w for 20s and 30s, work identical.

Is it possible to implement support of SmartAudio protocol?

Giving as granted your valuable experience with the modules used by QLRS would be great to start a new project.

Drop RX input / output and make QLRS telemetry link.

Allowing to send data transparently or even better having the option to allign MSP or MAVLINK packets in order to minimise packet losses and improve efficiency.
Would be great to be allowed to change coding and spreading settings too

This would outperform the original firmware, which cannot handle MSP and MAVLINK and wipe out of the market SIK radios

Hi, sometime while we on the field we can't arm the plane (arduplane), so it will be help, if we can know the problem with malink status msg.

thanks

When installing the SBUS protocol, the port speed should be 57600, but actually 9600. Module E32-433T30D. Firmware T433A_P_SBUS_T_SPORT_V1.92.s19
Param:
{ParSetStr v. QLRSM1.92_433A}
{ParSetStr f. P_SBUS T_SPORT }
{ParSetInt pCode xxxxx}
{ParSetInt noOfCPPMChnls 11}
{ParSetInt pwrSelChnl 10}
{ParSetInt rssiChnl 0}
{ParSetInt txMinPwr 0}
{ParSetInt txMidPwr 4}
{ParSetInt txMaxPwr 15}
{ParSetInt serPortSpd 57600}
{ParSetInt serMode 0}
{ParSetInt fr0 xxx}
{ParSetInt fr1 xxx}
{ParSetInt fr2 xxx}
{ParSetInt fr3 xxx}
{ParSetInt fr4 xxx}
{ParSetInt fr5 xxx}
{ParSetInt fr6 xxx}
{ParSetInt fr7 xxx}
{ParSetInt timeToFS 1}
{ParSetInt proto 2}
{ParSetInt devThrs 20}
{ParSetInt sTelFrmR 1}
{ParSetInt lTelFrmR 16}
{ParSetInt rssiT 0}
{ParSetInt lbeep 0}
{ParSetInt racem 0}
{ParSetInt wdTime 1}
{ParSetInt fsDontT 0}
{ParSetInt m0PWMChn 0}
{ParSetInt m1PWMChn 0}
{ParSetInt silent 0}
{ParSetInt beaFreq 0}
{ParSetInt fs00 1000}
{ParSetInt fs01 1000}
{ParSetInt fs02 1000}
{ParSetInt fs03 1000}
{ParSetInt fs04 1000}
{ParSetInt fs05 1000}
{ParSetInt fs06 1000}
{ParSetInt fs07 1000}
{ParSetInt fs08 1000}
{ParSetInt fs09 1000}
{ParSetInt fs10 1000}
{ParSetInt fs11 1000}
{ParSetInt fs12 1000}
{ParSetInt fs13 1000}
{ParSetInt fs14 1000}
{ParSetInt fs15 1000}

Two PWMs didn't work with LBEEP, but maybe one can.
It will be useful to trigger buzzer or video switch.
Thank you!

SNR is calculated in incorrect way

When there is a failsafe and SBUS is used, add an option to keep all the channels as they are and just set failsafe flag.
Will simplify a lot the setup without any risk of misconfiguration

LUA script: In Taranis X7, the azimuth is transmitted as a single digit, since the value on the sensor comes in the form Х.ХХ

https://ibb.co/nwj70xk

qczek lrs connection failed
I'm having a problem with the video. connection is constantly breaking. what should I do? Thank you.
oğuzhan

Is there a reason why you won't release a source code for your LRS? There is no information about it neither on your website nor on the GitHub project page

SBAS + S.Port Telemetry. The module is connected to Taranis X7 and is binded with a receiver. Тelemetry lost when i moved stiks and the LED on the transmitter goes out at the end, the connection will be completely lost.

It is restored only if the Taranis X7 is rebooted. But it is lost again, after a sticks using.

legacy stuff can't recognize the gap...

Flight mode is displayed incorrectly in the setup inav + qczek 2.1 (MAVLINK+SPORT) + inav lua telementry script.

With SPORT telemetry, lua script expects flight mode in Tmp1 sensor as described here:
https://github.com/iNavFlight/inav/b...s/Telemetry.md

When inav outputs mavlink, it encodes flight mode in baseFlags, systemState and mainly customMode flags of Hearbeat message:
https://github.com/iNavFlight/inav/b...etry/mavlink.c

so in order to display flight mode correctly, qczek TX module has to map mavlink heartbeat to Tmp1.

But the only values of Tmp1 I see are 1 (when not armed ) and 4( when armed).

"Mavlink encapsulation + SPORT (inav)" mode with inav-specific flight mode encoding to Tmp1 would be nice to have.

The angle seems to be divided by 100 when sent through Mavlink.
RCG link

here is the result with a transparent serial link :
mavlink_msg_global_position_int_get_hdg : 11914
mavlink_msg_vfr_hud_get_heading : 11900

here is the the result with QLRS :
mavlink_msg_global_position_int_get_hdg : 116
mavlink_msg_vfr_hud_get_heading : 116

Heading with the serial transparent link is 100 times bigger .