Releases · Clooney82/MavLink_FrSkySPort

08 Dec 21:46

athertop

Latest

Updates in this release to the lua scripts include:

New layout on Main telemetry screen
One telemetry screen for both Copter and Plane AP versions - telempc.lua (the choice of Copter/Plane is now an option in the offset.lua mixer script). This new script replaces both coptr217 and plane217 telemetry scripts.
offset.lua has been updated to include additional options:
- SpeedUnits - choose between 1 (m/s), 2 (kph), 3 (mph) - this affects the displayed units for GSpd and Aspd on main telemetry screen
- AltUnits - choose between 1 (metres), 2 (feet) - this affects the displayed units for Alt, Distance from home, and Climb rate (although m/s, f/s in this case).
- Coptr/Plan - choose between 1 (copter), 2 (plane) - this sets up the script with the correct flight modes for the chosen version.
txtmsg.lua telemetry script added - this displays the status messages - support for this script added to teensy code in this release.
Support for the standard naming convention of Tmp1 and Tmp2 sensors - OpenTx uses these names by default during discovery. So just discover these and its done - no further configuration of them required. For this release, it is suggested to delete the previous T1 and T2 sensors and re-run the discovery to add these back in.
Have removed the use of OpenTx Model Global Variables by mixer and telemetry scripts.

Updates in this release to the Teensy code include:

New code added to support the TxtMsg lua screen
Updates to the FrSkySportTelemetry library - some standardisation changes plus new functions to allow more efficient coding in main teensy sketch. Be sure to install the new FrSkySportTelemetry.zip library included with this release before writing the Teensy sketch - otherwise there will be compile time errors.
Changes to the presentation of the GSpd telemetry sensor - this allows for standardisation changes in the FrSkySportTelemetry library (bringing it closer to the original Pawelsky library) and allows for the default sensor configuration provided by the OpenTx sensor discovery process. It also aligns the sensor configuration of GSpd in with ASpd in OpenTx (both are discovered with the unit of kts - this should be left alone, even though the value shown is in m/s). For this release, it is suggested to delete the previous GSpd and ASpd sensors and re-run the discovery to add these back in.

The Wiki has been updated to reflect the changes in this release.

Assets 2

24 Oct 20:09

athertop

This release 1.7 has several updates including:

written for the latest FrSkySportTelemetry library (included in zip format in this repo).
Includes support for Ultimate LRS, including:
- sensor polling (used where the Teensy is not connected to a FrSky X series Rx - I.e. connected directly to Taranis module bay s.port pin, receiving mavlink stream natively from the Tx module - such as is the case using an Ultimate LRS Tx module)
- mavlink based RSSI display (sends mavlink RxRSSI to the A3 sensor (and 0 to A4). LUA screen will automatically display this in place of regular RSSI where the teensy code is configured with: #define USE_MAV_RSSI

Tested in the following 3 configurations:

Teensy connected in standard configuration - I.e. connected to FrSky X series Rx which polls teensy for sensor data, installed in model listening to mavlink messages from the Pixhawk/APM Telemetry port (using standard FrSky RSSI)
Teensy connected in a ground station repeater - I.e. Teensy installed in a repeater enclosure on the ground listening to Mavlink messages coming from the serial port of a ULRS Tx installed in the same enclosure. Teensy output connected to s.port of X4R Rx in this same enclosure. X4R polls the Teensy for s.port telemetry sensor data (using mavlink RSSI, and no polling)
Teensy connected directly to a ULRS Tx connected directly to Taranis module bay in PPM mode - I.e. Teensy collects Mavlink from ULRS Tx serial port, and provides its own polling requests, sending s.port telemetry sensor data into the s.port pin within the Taranis module bay (uses both polling and mavlink RSSI in this configuration).

The Wiki will be updated to reflect these changes under the AddOns section

Assets 2