Cleanup

Author: teckel12

.github/stale.yml

@@ -1,47 +1,31 @@
-# Configuration for probot-stale - https://github.com/probot/stale
-
-# Number of days of inactivity before an Issue or Pull Request becomes stale
-daysUntilStale: 30
-
-# Number of days of inactivity before a stale Issue or Pull Request is closed.
-# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 120
+# Number of days of inactivity before a stale issue is closed
 daysUntilClose: 7
-
-# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
+# Issues with these labels will never be considered stale
 exemptLabels:
-  - BUG
-  - Feature Request
-  - Pinned
-
+  - pinned
+  - security
 # Set to true to ignore issues in a project (defaults to false)
 exemptProjects: false
-
 # Set to true to ignore issues in a milestone (defaults to false)
-exemptMilestones: true
-
-# Label to use when marking as stale
-staleLabel: Inactive
-
-# Comment to post when marking as stale. Set to `false` to disable
+exemptMilestones: false
+# Label to use when marking an issue as stale
+staleLabel: wontfix
+# Comment to post when marking an issue as stale. Set to `false` to disable
 markComment: >
-  This issue / pull request has been automatically marked as stale because it
-  has not had recent activity. It will be closed if no further activity occurs
-  within a week.
-
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed if no further activity occurs. Thank you
+  for your contributions.
 # Comment to post when removing the stale label.
 # unmarkComment: >
 #   Your comment here.
-
-# Comment to post when closing a stale Issue or Pull Request.
-closeComment: >
-  Automatically closing as inactive.
-
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false
 # Limit the number of actions per hour, from 1-30. Default is 30
-limitPerRun: 30
-
+limitPerRun: 1
 # Limit to only `issues` or `pulls`
-# only: issues
-
+only: issues
 # Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
 # pulls:
 #   daysUntilStale: 30

.gitignore

@@ -1,47 +1,2 @@
-# Compiled Lua sources
-luac.out
-
-# luarocks build files
-*.src.rock
-*.zip
-*.tar.gz
-
-# Object files
-*.o
-*.os
-*.ko
-*.obj
-*.elf
-
-# Precompiled Headers
-*.gch
-*.pch
-
-# Libraries
-*.lib
-*.a
-*.la
-*.lo
-*.def
-*.exp
-
-# Shared objects (inc. Windows DLLs)
-*.dll
-*.so
-*.so.*
-*.dylib
-
-# Executables
-*.exe
-*.out
-*.app
-*.i*86
-*.x86_64
-*.hex
-
-# Eclipse
-.project
-
-#directories
-tmp
-obj
+.vscode/
+desktop.ini

README.md

@@ -1,53 +1,5 @@
-# betaflight-tx-lua-scripts
+# Taranis VTx Lua Script
 
-### Important:
+This stripped-down fork of [betaflight-tx-lua-scripts](https://github.com/betaflight/betaflight-tx-lua-scripts) includes only VTx configuration for Taranis transmitters only.  Taranis VTx was created to save memory on your transmitter so other Lua scripts (for example [Lua Telemetry](https://github.com/iNavFlight/LuaTelemetry)) can run on the same model. This script should work with [Betaflight](https://github.com/betaflight/betaflight) as well as [INAV](https://github.com/iNavFlight/inav).
 
-Some changes in the recently released OpenTX 2.2.1 cause this version to have less RAM available for lua scripts than previous versions. This often leads to problems when using the Betaflight TX lua scripts on the Taranis X9D. A discussion of these problems can be found [here](https://github.com/betaflight/betaflight-tx-lua-scripts/issues/97).
-A potential fix to increase the amount of RAM available has been identified: (https://github.com/opentx/opentx/pull/5579).
-For now, the recommendation is for users wanting to update OpenTX from 2.2.0 to 2.2.1 on a Taranis X9D (and keep using the Betaflight TX lua scripts) to hold on and monitor the situation, in the hope that OpenTX will release a version with this bugfix in the near future.
-
-### How to download the scripts
-
-Please visit the [releases page](https://github.com/betaflight/betaflight-tx-lua-scripts/releases) to download a zip file containing latest version.
-
-## Firmware Considerations
-- Betaflight - As a best practice, it is recommended to use the most recent stable release of Betaflight to obtain the best possible results.
-- Crossfire - v2.11 or greater
-- FrSky - While most receivers work fine, it's recommended to update the XSR family of receivers to their most recent firmware version to correct any known bugs in SmartPort telemetry.
-
-## Installing
-
-!! IMPORTANT: DON'T COPY THE CONTENTS OF THIS REPOSITORY ONTO YOUR SDCARD !!
-
-Unzip the files from the link above and drag the contents to your radio. If you do this correctly, the SCRIPTS directory will merge with your existing directories, placing the scripts in their appropriate paths.  You will know if you did this correctly if the bf.lua file shows up in your /SCRIPTS/TELEMETRY directory.
-
-The src directory is not required for use and is only available for maintenance of the code.  While it may work to use this directory, you may encounter memory issues on your transmitter.
-
-How to install:
-
-Bootloader Method
-1. Power off your transmitter and power it back on in boot loader mode.
-2. Connect a USB cable and open the SD card drive on your computer.
-3. Unzip the file and copy the scripts to the root of the SD card.
-4. Unplug the USB cable and power cycle your transmitter.
-
-Manual method (varies, based on the model of your transmitter)
-1. Power off your transmitter.
-2. Remove the SD card and plug it into a computer
-3. Unzip the file and copy the scripts to the root of the SD card.
-4. Reinsert your SD card into the transmitter
-5. Power up your transmitter.
-
-If you copied the files correctly, you can now go into the telemetry screen setup page and set up the script as telemetry page.
-
-## Adding the script as a telemetry page
-Setting up the script as a telemetry page will enable access at the press of a button. (For now, this only applies to the Taranis X9D series).
-1. Hit the [MENU] button and select the model for which you would like to enable the script.
-2. While on the [MODEL SELECTION] screen, long-press the [PAGE] button to navigate to the [DISPLAY] page.
-3. Use the [-] button to move the cursor down to [Screen 1] and hit [ENT].
-4. Use the [+] or [-] buttons to select the [Script] option and press [ENT].
-5. Press [-] to move the cursor to the script selection field and hit [ENT].
-6. Select 'bf' and hit [ENT].
-7. Long-press [EXIT] to return to your model screen.
-
-To invoke the script, simply long-press the [PAGE] button from the model screen.
+_TODO: Installation instructions..._

SCRIPTS/TELEMETRY/VTx.lua

@@ -1,9 +1,5 @@
 SCRIPT_HOME = "/SCRIPTS/TELEMETRY/VTx"
 
-PageFiles = {
-  "vtx.lua"
-}
-
 MenuBox = { x=15, y=12, w=100, x_offset=36, h_line=8, h_offset=3 }
 SaveBox = { x=15, y=12, w=100, x_offset=4,  h=30, h_offset=5 }
 NoTelem = { 30, 55, "No Telemetry", BLINK }

SCRIPTS/TELEMETRY/VTx.luac

@@ -1,4 +1,30 @@
-local userEvent = assert(loadScript(SCRIPT_HOME.."/events.lua"))()
+local userEvent = {
+    press = {
+        minus = EVT_MINUS_FIRST,
+        plus = EVT_PLUS_FIRST,
+        pageDown = EVT_PAGEDN_FIRST,
+        pageUp = EVT_PAGEUP_FIRST or EVT_LEFT_BREAK
+    },
+    longPress = {
+        enter = EVT_ENTER_LONG,
+        menu = EVT_MENU_LONG or EVT_RIGHT_LONG
+    },
+    repeatPress = {
+        minus = EVT_MINUS_REPT,
+        plus = EVT_PLUS_REPT
+    },
+    release = {
+        enter = EVT_ENTER_BREAK,
+        exit = EVT_EXIT_BREAK,
+        menu = EVT_MENU_BREAK or EVT_RIGHT_BREAK,
+        minus = EVT_MINUS_BREAK,
+        plus = EVT_PLUS_BREAK
+    },
+    dial = {
+        left = EVT_ROT_LEFT or EVT_UP_BREAK,
+        right = EVT_ROT_RIGHT or EVT_DOWN_BREAK
+    }
+}
 
 local pageStatus =
 {

SCRIPTS/TELEMETRY/VTx/events.lua

@@ -4,7 +4,7 @@ return {
     write          = 89, -- MSP_VTX_SET_CONFIG
     eepromWrite    = true,
     reboot         = false,
-    title          = "VTX",
+    title          = "Taranis VTX",
     minBytes       = 5,
     prevBandVal    = 0,
     prevChanVal    = 0,

SCRIPTS/TELEMETRY/VTx/events.luac

@@ -0,0 +1,35 @@
+#!/bin/bash
+
+if [ -d obj ]; then
+    rm -fR obj/*
+else
+    mkdir obj
+fi
+
+cp -fR src/* obj
+
+MANIFEST=(`find obj/ -name *.lua -type f`);
+LAST_FAILURE=0
+
+if [ ${#MANIFEST[@]} -eq 0 ]; then
+    echo -e "\e[1m\e[39m[\e[31mTEST FAILED\e[39m]\e[21m No scripts could be found!."
+    exit 1
+fi
+
+for f in ${MANIFEST[@]};
+do
+    SRC_NAME=$f
+    OBJ_NAME=$(dirname ${f})/$(basename ${f} .lua).luac
+    echo -e "Compiling file \e[1m${SRC_NAME}\e[21m..."
+    luac -s -o ${OBJ_NAME} ${SRC_NAME}
+    _fail=$?
+    if [[ $_fail -ne 0 ]]; then
+        LAST_FAILURE=$_fail
+        echo -e "\e[1m\e[39m[\e[31mBUILD FAILED\e[39m]\e[21m Compilation error in file ${SRC_NAME}\e[1m"
+    fi
+done
+
+if [[ $LAST_FAILURE -eq 0 ]]; then
+    echo -e "\e[1m\e[39m[\e[32mTEST SUCCESSFUL\e[39m]\e[21m All lua files built successfully!"
+fi
+exit $LAST_FAILURE