Skip to content

Latest commit

 

History

History
101 lines (83 loc) · 6.15 KB

README.md

File metadata and controls

101 lines (83 loc) · 6.15 KB
Raw

Welcome to ESC S.Port (escsport)

General purpose ESC telemetry adapter for connection to FrSky s.port receivers

USE AT YOUR OWN RISK

About escsport

Why? To get heli quality ESC telemetry for fixed wing applications.
We use bettery capacity/consumption telemetry info to maximize flighttime and voltage telemetry monitor battery performance/warnings.
So much better than flying by a timer. This project addresses this need and is now standard equipment in my new builds.

Release notes

  • 2024.12.10 - revised to accept power from Rx on port labled RX2 w/ VBT bridged to Vx (thanks Ben)

Requirements

  • an ESC w/ telemetry supported by RotorFlight (YGE, Scorpion, HobbyWing, Kontronik ...)
  • small RotorFlight flight controller (FC) - e.g. Matek G474-HLITE, it's 30x23x13mm 9g
  • RotorFlight 2.0 (release 4.3.0) firmware - install using the configurator

Caution

  • some powersafe receivers e.g. the FrSky TD SR18 don't like power from an external source to appear on the +ve of the servo bus
    • removing the +ve lead from the ESC telemetry lead to the FC avoids this

ESC

Some ESCs need to be told which protocol to use, e.g.

  • Scorpion - set the ESC to "UNSC (Unsolicited)" telemetry mode
  • YGE - set the ESC to "OpenYGE" telemetry mode
  • See RotorFlight ESC Telemetry for more info if needed

The connections

  • connect the FC with a 3 pin servo cable to one of the FrSky Rx's s.port ports
    • most FrSky Rx's can be configured to accept s.port devices on any free port
    • this connection will power the FC
  • connect the ESC's telemetry signal and optionally the -ve/gnd, omit the +ve this WILL damage certain setups

Hardware

  • solder pins to the FC
    • RX2: 3-pin w/ bridge between VBT and adjacent Vx
    • RX3: 2-pin signal+gnd, again: the +ve pin is removed to avoid possible damage image image image image image image

Firmware

  • install RotorFlight 2.0 using the RotorFlight configurator, if already installed skip to configuration

Configuration

  • download RTFL_cli_escsport.txt
  • connect to the FC using the configurator, you will likely see this warning - ignore it
  • click the [CLI] tab
  • Load the RTFL_cli_escsport.txt you downloaded above
  • type 'save' to commit the loaded settings. The FC will reboot and reconnect
  • go to the [Power] tab
    • change the 'Capacity [mAh]' setting to match your battery
    • do not change anything else
    • save
  • goto the [Motors] tab
    • change 'ESC Telemetry protocol' to match your ESC
    • change 'Main Motor pole count' to match your motor (for accurate RPM)
    • do not change anything else
    • save

Installation

  • install securely anywhere
  • connect the ESC telemetry cable to the 2-pin RX3 port
  • connect the 3-pin RX2 port to a port on the FrSky Rx that's been configured to accept s.port image image

On the transmitter

  • power up Tx, Rx and ESC
  • discover new sensors, the ESC supplied sensors like VFAS, Current, Fuel etc should appear
  • there may be duplicates e.g. temp, RPM etc - delete what you don't need
    Note: both main and tail rotor RPM are reported as 'RPM', power the motor briefly to see which one responds - delete the others image
  • the 'mAh' current consumption sensor may not have been auto discovered
    • create a DIY sensor
    • click 'AutoDetect' and select the sensor with ID 5250
    • set decimals, units and range as shown image image

Done

These sensors can be displayed with widgets, used for alarms etc just like any other sensor.
Enjoy.

image image