From 0004a39218fcc2ee39ed641a5632ea44bc4e44a7 Mon Sep 17 00:00:00 2001 From: Vitaliy Ryumshyn Date: Wed, 30 Oct 2024 17:49:33 +0100 Subject: [PATCH] fix html doc --- app/build.gradle | 4 +- ...-your-own-BlueTooth-RC-Throwmeter-V2.0.htm | 176 +++++++++--------- 2 files changed, 90 insertions(+), 90 deletions(-) diff --git a/app/build.gradle b/app/build.gradle index 7e63439..7448668 100644 --- a/app/build.gradle +++ b/app/build.gradle @@ -2,8 +2,8 @@ apply plugin: 'com.android.application' android { defaultConfig { - versionCode 8 - versionName "1.6.2" + versionCode 9 + versionName "1.6.3" resValue "string", "app_version", "$versionName" applicationId "com.pitchgauge.j9pr.pitchgauge" minSdkVersion 21 diff --git a/app/src/main/assets/Make-your-own-BlueTooth-RC-Throwmeter-V2.0.htm b/app/src/main/assets/Make-your-own-BlueTooth-RC-Throwmeter-V2.0.htm index 8b7d245..8eeb741 100644 --- a/app/src/main/assets/Make-your-own-BlueTooth-RC-Throwmeter-V2.0.htm +++ b/app/src/main/assets/Make-your-own-BlueTooth-RC-Throwmeter-V2.0.htm @@ -687,7 +687,7 @@ {mso-style-priority:9; mso-style-unhide:no; mso-style-qformat:yes; - mso-style-link:"�berschrift 4 Zchn1"; + mso-style-link:"Überschrift 4 Zchn1"; mso-margin-top-alt:auto; margin-right:0cm; mso-margin-bottom-alt:auto; @@ -725,12 +725,12 @@ mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast;} span.berschrift4Zchn - {mso-style-name:"�berschrift 4 Zchn"; + {mso-style-name:"Überschrift 4 Zchn"; mso-style-noshow:yes; mso-style-priority:9; mso-style-unhide:no; mso-style-locked:yes; - mso-style-link:"�berschrift 4"; + mso-style-link:"Überschrift 4"; mso-ansi-font-size:11.0pt; mso-bidi-font-size:11.0pt; font-family:"Calibri Light",sans-serif; @@ -771,10 +771,10 @@ mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast;} span.berschrift4Zchn1 - {mso-style-name:"�berschrift 4 Zchn1"; + {mso-style-name:"Überschrift 4 Zchn1"; mso-style-unhide:no; mso-style-locked:yes; - mso-style-link:"�berschrift 4"; + mso-style-link:"Überschrift 4"; font-family:"Times New Roman",serif; mso-ascii-font-family:"Times New Roman"; mso-hansi-font-family:"Times New Roman"; @@ -870,49 +870,49 @@

�·        Android API33 (needed for playstore compatibility)

�·        New app permission dialog for Android versions 12 or later

�·        Support WitMotion BWT901CL modules, in addition to BWT61CL

�·        New WitMotion configuration dialog

�·        New throw calculation option

�·        Min/Max values more robust against noise

�·        New difference display option in Dual-Mode

@@ -923,21 +923,21 @@

�·        Android -permission issues fixed.�

+permission issues fixed. 

�·        New difference display with percentage (%) values.

�·        STL files for 3D printing and more ideas documented on �·        Android API34 (needed for playstore compatibility)

�·        Reset max/min display when chord value changes (minor fix)

@@ -979,42 +979,42 @@

�·        Can bind and use 2022 WitMotion modules (with other HC-06 inside)

�·        Prevent screensaver to lock Throwmeter screen

�·        Improved reliability of Bluetooth binding

�·        Prevent max UP/DOWN to catch fast travel glitches

�·        Fast and smooth screen update in Dual-Mode

�·        Ensure proper Witmotion configuration at startup

@@ -1031,28 +1031,28 @@

�·        Support two sensors simultaneously

�·        Calibration support, no need for manufacturer app

�·        Bluetooth status bar

�·        More stable Bluetooth connection, and reconnection when exiting of standby/sleeping @@ -1060,41 +1060,41 @@

�·        Clearer separation between max travel feature and limit setting with alarm feature

�·        Localization

�·        German language support

�·        Sensor option to choose more robust X/Y only calculation

�·        Compacter screen layout for small displays

�·        Reminder to power off sensor when App is left

@@ -1153,35 +1153,35 @@ font-family:"Times New Roman",serif;color:black'>Characteristics

�·        Voltage: 3.3V-5V

�·        Current: <40mA

�·        Size: 51.3mm x 36mm X 15mm

�·        Weight: 16gr

�·        Dimension: Accelerated @@ -1189,38 +1189,38 @@ style='mso-fareast-font-family:"Times New Roman";color:black'>

�·        Air pressure 1d

�·        Range: Accelerated speed --�16g Angular speed -�2000�/s Angle---�180�

�·        Stability: Accelerated -speed -0.01g Angular speed -0.05�/s

�·        Attitude measurement -stability: 0.05�

�·        Output content: Time, @@ -1228,7 +1228,7 @@ "Times New Roman";color:black'>

�·        Output frequenc

�·        Date interface: Serial -TTL level, Bitrate 115200 (default and can�t be changed)

�·        Bluetooth transmission @@ -1254,14 +1254,14 @@ color:black'>

�·        Support for Android

�·       Working time: 2 to 3 hours (full charge)The Android App has been developed by Yannick and Vitaliy. The App is divided in several screens, the start screen giving access to the top left menu, the "BT -Sensors" screen to connect the App with the desired throwmeter(s), �Preferences� +Sensors" screen to connect the App with the desired throwmeter(s), “Preferences” provide user settings, and finally the "Throw meter" screen where everything happens once sensors have been paired in android bluetooth menu.

@@ -1390,7 +1390,7 @@ style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black'>On your smartphone navigate to the parameter/bluetooth menu and scan for new devices. The BWT61CL and BWT901CL will show as HC-06. When asked, -enter the code �1234�. The sensor is now paired and you are ready to +enter the code “1234”. The sensor is now paired and you are ready to open the App.

Starting -with Android version 12, the user must allow �Nearby Devices� -permission. Please allow �Nearby Devices�. Otherwise, the app cannot +with Android version 12, the user must allow “Nearby Devices” +permission. Please allow “Nearby Devices”. Otherwise, the app cannot access the WitMotion sensors and will refuse work and a pop-up window with warnings appears.

@@ -1410,7 +1410,7 @@ style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black'>If you have denied once, Android will not ask again. If it happens, please un-install the app and re-install it or change the permission in the Android Apps -menu.�

+menu. 

 

@@ -1495,7 +1495,7 @@

In -dual sensor mode the app can display differences between two sensors. Press �Diff� +dual sensor mode the app can display differences between two sensors. Press “Diff” button (bottom right) to toggle between normal and difference displays. Angle difference between left and right sensors is shown between the Angle display fields. Travel difference between left and right sensor is shown between the @@ -1513,13 +1513,13 @@

 

If �Diff� +style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black'>If “Diff” is pressed again, the difference display mode changes to a percentage display instead showing absolute values. For calculation it compares the absolute of the throw values. Then it uses the larger value from either side, left or right, as reference and calculates the percentage. If both sides are equal, it -will show 0%. The �<� indicates that the reference value (larger value) is on -the left, �>� indicates the reference is on the right.

+will show 0%. The “<” indicates that the reference value (larger value) is on +the left, “>” indicates the reference is on the right.

If the device is providing inconsistent or weird measures, it probably needs a full calibration. Level the sensor(s) horizontally and do not move. To activate Calibration long -press the �Reset/Calib� button, confirm dialog and wait until +press the “Reset/Calib” button, confirm dialog and wait until calibration completes.

Measure the chord of you control surface and click on the chord field at the top of the screen to enter the value. There is no unit, so it can -be �mm� or �inches�. Travel will be shown in the same unit.

+be “mm” or “inches”. Travel will be shown in the same unit.

This is a very useful feature that allows you to quickly measure the maximum up and down -travels of a control surface. Use �Reset� to clear the Max UP/DOWN values for a +travels of a control surface. Use “Reset” to clear the Max UP/DOWN values for a new measurement.

If -your objective is to do settings, not to measure, you can enter a �Max positiv -travel� and a �Min negativ travel� separately. This instructs the App to +your objective is to do settings, not to measure, you can enter a “Max positiv +travel” and a “Min negativ travel” separately. This instructs the App to display an alarm (in RED color instead GREEN) when the travel value exceeds a -threshold, either above the �Max positiv travel� or below the �Min negativ -travel�.

+threshold, either above the “Max positiv travel” or below the “Min negativ +travel”.

 

@@ -1777,10 +1777,10 @@

+“Reset” if this occurs.

�·        Use XY axes (default)

@@ -1792,7 +1792,7 @@

�·        Use XYZ axes

@@ -1809,22 +1809,22 @@

The throw calculation of the deflection -may use one of these formulas.��

+may use one of these formulas.  

�·        Orthogonal deflection (default)
-����� (A) throw = chord * +      (A) throw = chord * sin(alpha)

�·        Chord length
-������ (B) throw = chord * 2 * +       (B) throw = chord * 2 * sin(alpha/2)

�·        Auto-Detect (default)
-����� The app recognizes the proper +      The app recognizes the proper WitMotion model automatically.

�·        BWT61CL
-����� The app assumes usage of BWT61CL.

+      The app assumes usage of BWT61CL.

�·        BWT901CL
-����� The app assumes usage of BWT901CL.

+      The app assumes usage of BWT901CL.

Important Note:FAQ -� Frequently Asked Questions

+– Frequently Asked Questions

 

Q: The app fails to connect -devices at the �Throw meter� screen

+devices at the “Throw meter” screen

A: Please leave screen and go back to main -screen. Retry �Throw meter� again. In most cases, it will connect. The reason +screen. Retry “Throw meter” again. In most cases, it will connect. The reason is unknown, possible radio interference happens. You can try to change the -distance between your mobile phone and the sensors, e.g. 30�100 cm. For unknown +distance between your mobile phone and the sensors, e.g. 30–100 cm. For unknown reasons connection fails happen in dual sensor configuration mainly. You could try to leave the app, disable/enable bluetooth on android phone, power-off/power-on sensors and re-try.

@@ -2010,4 +2010,4 @@

- \ No newline at end of file +