Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Data logging finds an "incident"
#9

The ELRS website does recommend a telemetry ratio of at least 1:32 with the 100Hz packet rate.

What does your TQLY reading look like at those points where the TX power is increased?

If the system misses a few telemetry packets it will also raise the TX power level.

Quote:To be proactive when telemetry is not received, Dynamic Power will also increase power one level for each missed telemetry packet, starting when two are missed back to back.
Reply


Messages In This Thread
Data logging finds an "incident" - by greggold - 07-06-2023, 09:50 AM
RE: Data logging finds an "incident" - by greggold - 07-06-2023, 03:59 PM
RE: Data logging finds an "incident" - by caffeine - 07-06-2023, 06:17 PM
RE: Data logging finds an "incident" - by greggold - 07-06-2023, 07:36 PM
RE: Data logging finds an "incident" - by caffeine - 07-06-2023, 09:09 PM
RE: Data logging finds an "incident" - by greggold - 12-06-2023, 08:58 AM
RE: Data logging finds an "incident" - by caffeine - 13-06-2023, 10:09 AM
RE: Data logging finds an "incident" - by greggold - 13-06-2023, 12:58 PM
RE: Data logging finds an "incident" - by caffeine - 13-06-2023, 01:16 PM
RE: Data logging finds an "incident" - by greggold - 13-06-2023, 01:21 PM
RE: Data logging finds an "incident" - by greggold - 13-06-2023, 01:28 PM
RE: Data logging finds an "incident" - by greggold - 13-06-2023, 03:40 PM
RE: Data logging finds an "incident" - by caffeine - 14-06-2023, 09:20 PM
RE: Data logging finds an "incident" - by caffeine - 16-06-2023, 09:41 PM
RE: Data logging finds an "incident" - by greggold - 18-06-2023, 09:21 AM
RE: Data logging finds an "incident" - by greggold - 18-06-2023, 10:32 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)