From 8824c39aef4f7b579a2a542e6f88378b0c7751c8 Mon Sep 17 00:00:00 2001 From: Milos Kozak Date: Sun, 1 Nov 2026 21:39:46 +0100 Subject: [PATCH] EN: fix errors found by translators Typos, grammar, double spaces, broken markup and links, app labels that changed. Links to headings now use explicit anchors, so translated headings no longer break them. Release dates of 3.4.1.0 and 3.4.2.0 corrected. --- docs/EN/AdvancedOptions/Autotune.md | 8 ++-- docs/EN/AdvancedOptions/DevBranch.md | 2 +- docs/EN/AdvancedOptions/FullClosedLoop.md | 19 ++++---- .../AdvancedOptions/InsulinConcentration.md | 2 +- docs/EN/CompatibleCgms/DexcomG6.md | 2 +- docs/EN/CompatibleCgms/DexcomG7.md | 6 +-- .../GeneralCGMRecommendation.md | 4 +- docs/EN/CompatibleCgms/Juggluco.md | 2 +- docs/EN/CompatibleCgms/Libre2.md | 6 +-- docs/EN/CompatibleCgms/Libre2MinimalL00per.md | 20 ++++---- docs/EN/CompatibleCgms/Libre3.md | 6 +-- docs/EN/CompatibleCgms/OttaiM8.md | 2 +- docs/EN/CompatibleCgms/SyaiTagX1.md | 2 +- docs/EN/CompatibleCgms/xDrip.md | 4 +- docs/EN/CompatiblePhones/Jelly.md | 4 +- .../Accu-Chek-Combo-Pump-v2.md | 2 +- .../CompatiblePumps/Accu-Chek-Insight-Pump.md | 4 +- docs/EN/CompatiblePumps/CareLevo.md | 4 +- docs/EN/CompatiblePumps/DanaR-Insulin-Pump.md | 2 +- .../Future-possible-Pump-Drivers.md | 4 +- docs/EN/CompatiblePumps/MedtronicPump.md | 4 +- docs/EN/CompatiblePumps/MedtrumNano.md | 4 +- docs/EN/CompatiblePumps/OmnipodDASH.md | 16 +++---- docs/EN/CompatiblePumps/OmnipodEros.md | 12 ++--- docs/EN/DailyLifeWithAaps/AapsScreens.md | 16 +++---- docs/EN/DailyLifeWithAaps/Automations.md | 46 +++++++++---------- docs/EN/DailyLifeWithAaps/CobCalculation.md | 10 ++-- docs/EN/DailyLifeWithAaps/DynamicISF.md | 12 ++--- docs/EN/DailyLifeWithAaps/ExtendedCarbs.md | 4 +- docs/EN/DailyLifeWithAaps/GlobalSearch.md | 2 +- docs/EN/DailyLifeWithAaps/KeyAapsFeatures.md | 18 ++++---- .../ProfileSwitch-ProfilePercentage.md | 11 +++-- docs/EN/DailyLifeWithAaps/PumpsAndCannulas.md | 6 +-- docs/EN/DailyLifeWithAaps/TempTargets.md | 10 ++-- .../TimezoneTraveling-DaylightSavingTime.md | 8 ++-- .../CustomWatchfaceReference.md | 42 ++++++++--------- docs/EN/ExchangeSiteCustomWatchfaces/index.md | 2 +- docs/EN/Getting-Started/CompatiblesCgms.md | 6 +-- docs/EN/Getting-Started/Introduction.md | 20 ++++---- docs/EN/Getting-Started/Phones.md | 2 +- docs/EN/Getting-Started/PreparingForAaps.md | 4 +- docs/EN/Getting-Started/Watches.md | 10 ++-- docs/EN/GettingHelp/AccessingLogFiles.md | 4 +- .../GettingHelp/BluetoothTroubleshooting.md | 12 ++--- .../BrowserBuildTroubleshooting.md | 4 +- .../TroubleshootingAndroidStudio.md | 10 ++-- .../EN/GettingHelp/TroubleshootingNsClient.md | 2 +- docs/EN/GettingHelp/WhereCanIGetHelp.md | 4 +- docs/EN/Maintenance/DocumentationUpdate.md | 10 ++-- docs/EN/Maintenance/ExportImportSettings.md | 8 ++-- docs/EN/Maintenance/ReleaseNotes.md | 18 ++++---- docs/EN/Maintenance/Reviewing.md | 10 ++-- docs/EN/Maintenance/UpdateBrowserBuild.md | 6 +-- docs/EN/Maintenance/UpdateComputerBuild.md | 4 +- docs/EN/Maintenance/UpdateToNewVersion.md | 6 +-- docs/EN/RemoteFeatures/AndroidAuto.md | 4 +- docs/EN/RemoteFeatures/FollowingOnly.md | 8 ++-- docs/EN/RemoteFeatures/RemoteControl.md | 14 +++--- docs/EN/RemoteFeatures/RemoteControlWearOS.md | 8 ++-- docs/EN/RemoteFeatures/RemoteMonitoring.md | 2 +- docs/EN/RemoteFeatures/SMSCommands.md | 16 +++---- docs/EN/Sandbox/sandbox1.md | 2 +- .../SettingUpAaps/BrowserBuildDownloadPrep.md | 2 +- docs/EN/SettingUpAaps/BrowserBuildFork.md | 12 ++--- docs/EN/SettingUpAaps/BrowserBuildKeystore.md | 4 +- docs/EN/SettingUpAaps/BrowserBuildO1.md | 2 +- .../SettingUpAaps/BrowserBuildO1Computer.md | 32 ++++++------- docs/EN/SettingUpAaps/BrowserBuildO2.md | 2 +- .../SettingUpAaps/BrowserBuildO2Computer.md | 32 ++++++------- docs/EN/SettingUpAaps/BuildingAaps.md | 2 +- .../SettingUpAaps/ChangeAapsConfiguration.md | 2 +- .../SettingUpAaps/CompletingTheObjectives.md | 16 +++---- docs/EN/SettingUpAaps/ComputerBuild.md | 10 ++-- docs/EN/SettingUpAaps/ConfigBuilder.md | 8 ++-- docs/EN/SettingUpAaps/Nightscout.md | 2 +- docs/EN/SettingUpAaps/Preferences.md | 6 +-- .../SettingUpTheReportingServer.md | 2 +- docs/EN/SettingUpAaps/SetupWizard.md | 9 ++-- docs/EN/SettingUpAaps/YourAapsProfile.md | 10 ++-- docs/EN/SupportingAaps/HowCanIHelp.md | 2 +- docs/EN/SupportingAaps/HowToEditTheDocs.md | 24 +++++----- docs/EN/SupportingAaps/OpenHumans.md | 4 +- docs/EN/SupportingAaps/StateOfTranslations.md | 4 +- docs/EN/SupportingAaps/Translations.md | 6 +-- docs/EN/UsefulLinks/ClinicianGuideToAaps.md | 10 ++-- .../DedicatedGoogleAccountForAaps.md | 12 ++--- docs/EN/UsefulLinks/FAQ.md | 10 ++-- docs/EN/UsefulLinks/Glossary.md | 24 +++++----- docs/EN/WearOS/BuildingAapsWearOS.md | 2 +- docs/EN/WearOS/WearOsSmartwatch.md | 12 ++--- docs/EN/index.md | 6 +-- 91 files changed, 396 insertions(+), 395 deletions(-) diff --git a/docs/EN/AdvancedOptions/Autotune.md b/docs/EN/AdvancedOptions/Autotune.md index 73030dadaa0c..e1932a21823d 100644 --- a/docs/EN/AdvancedOptions/Autotune.md +++ b/docs/EN/AdvancedOptions/Autotune.md @@ -78,7 +78,7 @@ Tap **Open plugin** on the **Autotune** card to open the Autotune screen: - If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - Activate Tuned profile will automatically create a new profile "Tuned" in your profile list (**Manage → Profile**). + - "Activate profile" will automatically create a new profile "Tuned" in your profile list (**Manage → Profile**). - If you already have a profile named "Tuned" in **Manage → Profile**, then this profile will be updated with calculated Autotune profile before the activation ![Autotune Activate profile](../images/Autotune/Autotune_6.png) @@ -123,7 +123,7 @@ The **Auto switch profile** feature is only available in Dev/Engineering mode. - **Auto switch profile** (default Off): see [Run Autotune with an automation rule](#autotune-run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - **Be Careful, you must trust and verify during several following days, that after an update and activation of Tuned profile without modification, it improves your loop** -- **Categorize UAM as basal** (default Off): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. +- **Categorize UAM as basal** (default Off): This setting is for the users using AAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) - **Default tune days** (default 5): You can define the default value with this setting. Each time you select a new profile in the Autotune plugin, the **Number of days of data** will be replaced by this default value - **Use circadian IC/ISF** (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below. @@ -188,7 +188,7 @@ Note: for more information on how to set an automation rule, see [here](../Daily ![Autotune default screen](../images/Autotune/Autotune_17.png) -- Then you can select the **Autotune profile** action (in the **Loop & insulin** group) +- Then you can select the **Run Autotune** action (in the **Loop & insulin** group) ![Autotune default screen](../images/Autotune/Autotune_18.png) @@ -212,7 +212,7 @@ Autotune works with information existing in your database, so if you just instal Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. -Always use Autotune several days manually to check results before applying them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) +Always use Autotune several days manually to check results before applying them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile then you start to use Automation (Never before) - Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** diff --git a/docs/EN/AdvancedOptions/DevBranch.md b/docs/EN/AdvancedOptions/DevBranch.md index 348dcbc4dd87..7913b7ddd235 100644 --- a/docs/EN/AdvancedOptions/DevBranch.md +++ b/docs/EN/AdvancedOptions/DevBranch.md @@ -6,7 +6,7 @@ Dev branch is for the further development of AAPS only. It should be used on a s The most stable version of AAPS to use is that in the [Master branch](https://github.com/nightscout/AndroidAPS/tree/master). It is advised to stay on the Master branch for actual looping. -The dev version of AAPS is only for developers and testers comfortable dealing with stacktraces, looking through log files and maybe firing up the debugger to produce bug reports that are helpful to the developers (in short: people that know what they are doing without being assisted!). Therefore many unfinished features are disabled. To enable these features enter **Engineering Mode** by creating a file named `engineering_mode` in directory /AAPS/extra . Enabling the engineering mode might break the loop entirely. +The dev version of AAPS is only for developers and testers comfortable dealing with stacktraces, looking through log files and maybe firing up the debugger to produce bug reports that are helpful to the developers (in short: people that know what they are doing without being assisted!). Therefore many unfinished features are disabled. To enable these features enter **Engineering Mode** by creating a file named `engineering_mode` in the directory /AAPS/extra. Enabling the engineering mode might break the loop entirely. However, the Dev branch is a good place to see what features are being tested and to help iron out the bugs and give feedback on how the new features work in practice. Often people will test the Dev branch on an old phone and pump until they are confident it is stable - any use of it is at your own risk. When testing any new features, remember that you are choosing to test a still-in-development feature. Do so at your own risk & with due diligence to keep yourself safe. diff --git a/docs/EN/AdvancedOptions/FullClosedLoop.md b/docs/EN/AdvancedOptions/FullClosedLoop.md index a0eea254c4bb..632d9c24cde1 100644 --- a/docs/EN/AdvancedOptions/FullClosedLoop.md +++ b/docs/EN/AdvancedOptions/FullClosedLoop.md @@ -88,7 +88,7 @@ The above will vary depending on your **AAPS** component system and your lifesty ### Glycemic index and effect on blood glucose -The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG') +The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose' ('EBG') - Start moderate/low, and tune your **Profile's** settings. Only then, "test" meals with high **EBG**. - Consider a < 50% initial bolus if consuming very high **EBG**. @@ -96,7 +96,7 @@ The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose (' 1) **No EBG**: e.g. fresh meat, fish, eggs, bacon, oils, cheese. 2) **Low EBG**: e.g. fresh vegetables and berries, mushrooms, nuts, milk, yoghurt, cottage cheese. 3) **Moderate EBG**: e.g. whole grain bread/noodles, potatoes, wild rice, oats, dried fruits. -4) **High EBG**:e.g. wheat breads, baguette, toast, waffles, cookies, mash potatoes, noodles, rice. +4) **High EBG**: e.g. wheat breads, baguette, toast, waffles, cookies, mash potatoes, noodles, rice. 5) **Very High EBG**: e.g. sugar, sweet drinks, fruit juices, cornflakes, candy, sweets, potato chips, salty pretzel sticks. ![Glycemic index and effect on blood glucose](../images/fullClosedLoop01.png) @@ -112,7 +112,7 @@ When exercising or being active, with a pump or hybrid closed loop it is recomme With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver insulin to counter **BG** rises. A high **Temp Target** and lower **Profile Percentage** (effective already around meal start) should be set well in advance of any activity. -Unusual or erratic exercise activity levels present difficulties for **FCL**. Planning ahead is required for exercise (especially if you want to reduce the need for rescue carbs/snacks during sports low). After an active day it is recommended that a lower **Percentage Profile** is set for overnight after the evening meal is fully digested: set in **Automations** an elevated (>100 mg/dL) **BG** target, with “no **SMBs** at elevated target” selected in **AAPS** **Settings**. +Unusual or erratic exercise activity levels present difficulties for **FCL**. Planning ahead is required for exercise (especially if you want to reduce the need for rescue carbs/snacks during sports low). After an active day it is recommended that a lower **Percentage Profile** is set for overnight after the evening meal is fully digested: set in **Automations** an elevated (>100 mg/dL) **BG** target, with **Enable SMB with high temp target** switched off in **AAPS** **Settings**. ## Hurdles for kids @@ -155,7 +155,7 @@ For successful **FCL**, **ISF** is the key tuning parameter. When utilising **AA **AAPS** Master allows up to 130% temporary **Profile** in **HCL** mode. Boosting the **ISF** is done in 3 steps: -- Step 1 - review the **ISF** applicable for this meal time hour within the **Profile**, and see whether e.g. Autosens suggest a modification that takes care of the current (last few hours’) insulin sensitivity status of the body.. +- Step 1 - review the **ISF** applicable for this meal time hour within the **Profile**, and see whether e.g. Autosens suggest a modification that takes care of the current (last few hours’) insulin sensitivity status of the body. - Step 2 - apply a factor (1/Profile%, as set in **Automation**) to boost **ISF**. - Step 3 - check that the suggested **ISF** falls within set safety limits. @@ -173,10 +173,9 @@ The section below provides guidance how to bundle **Automation’s** Conditions ### Automated big SMBs at bg rise -The key to successful **FCL** **at the beginning of BG increases from meals, very large automatic SMBs must be given by the loop as quickly as possible** “to catch up” with the required **IOB** needed (compare with your typical administered bolus for similar meal in **HCL**!) +The key to successful **FCL**: **at the beginning of BG increases from meals, very large automatic SMBs must be given by the loop as quickly as possible** “to catch up” with the required **IOB** needed (compare with your typical administered bolus for similar meal in **HCL**!) -To achieve this, data from your **HCL** should be analyzed to determine which **deltas** might be not meal –related and those delta - which might be. +To achieve this, data from your **HCL** should be analyzed to determine which **deltas** might not be meal-related and which might be. - As you can define the **Automation** within a pre-defined time-window, you need only to analyze there. - If you do very different kinds of meals (e.g. a rather high carb breakfast, but low carb lunch) you can choose to do two different (sets of) **Automations** for each of the time slots. @@ -224,7 +223,7 @@ Sensible **iob thresholds** at which you should reduce aggressiveness of your lo For exceptional meals, or to lower it if sports follow, the **iob** threshold can rapidly be set differently in your **Automation**. -Automation(#3),”iobTH reached => **SMBs** off”, is defined to end (or pause, until another wave of carb-related rise hits) the aggressive **SMB** boosting. +Automation (#3), "iobTH reached => **SMBs** off”, is defined to end (or pause, until another wave of carb-related rise hits) the aggressive **SMB** boosting. ![Automation #3: IOB of 5.5 or more with no temp target running starts a temp target of 111 mg/dL](../images/fullClosedLoop04.png) @@ -242,7 +241,7 @@ One way to do this is to set up an **Automation** Condition that ends an eventua >Ways to work with EatingSoonTT Some loopers set (by pressing the TT button, or automated via a lowered **Profile** **BG** target if eating time slots are fairly fixed) an EatingSoonTT roughly an hour or more before meal start, just to guarantee a low starting **BG** and slightly increased **iob**. -But, assuming the **FCL** is always en route towards target, this might not yield much and you may prefere to define an **Automation** that sets an EatingSoonTT at recognition of meal start (glucose delta, or acceleration = delta > avg delta). +But, assuming the **FCL** is always en route towards target, this might not yield much and you may prefer to define an **Automation** that sets an EatingSoonTT at recognition of meal start (glucose delta, or acceleration = delta > avg delta). A low **TT** is important in this stage because any **SMB** is calculated by your loop using (predicted glucose minus TT)/sens, so a small TT makes the resulting insulinReq bigger. After the first boosted **SMB**s were given, your set iobTH and **Automation** #3 should strike a good balance of limiting the glucose peak, but also not leading to a hypo after the meal. @@ -346,7 +345,7 @@ Going down (e.g. towards a set EatingSoonTT), building some iob, and curving alr - Problems with insulin “tail” after meals - You may need to take a snack (seeing hypo prediction) or glucose tablets (if already in hypo zone). But note that the carbs required the loop might tell you at some point are very likely exaggerated as the loop has absolutely zero info on your carb intake (while you may be able to guess how much more, incl. from fats and proteins) is still waiting to be absorbed. - A valuable information would be whether the problem originates mostly in the bg rise phase already. Then setting a lower iobTH might be an easy remedy. - - If the need for additional carbs happens frequently, note down how many grams were needed (not counting what you eventually took too much and required extra insulin again). Then use your profile IC value to estimate how much insulin less the **SMB** should have delivered, and go with this info into your tuning (regarding the **Percentage Profile** in **Automations**, or maybe also your set iobTH). This may relate to the **SMBs** given when glucose was high, or also extending regarding also the **SMBs** during the **BG** rise. + - If the need for additional carbs happens frequently, note down how many grams were needed (not counting what you eventually took too much and required extra insulin again). Then use your profile IC value to estimate how much insulin less the **SMB** should have delivered, and go with this info into your tuning (regarding the **Percentage Profile** in **Automations**, or maybe also your set iobTH). This may relate to the **SMBs** given when glucose was high, or also to the **SMBs** during the **BG** rise. - It could well be that you simply have to accept higher **BG** peaks for not going low. Or change diet to something with lower amounts of carbs, and higher amount of protein and fats. diff --git a/docs/EN/AdvancedOptions/InsulinConcentration.md b/docs/EN/AdvancedOptions/InsulinConcentration.md index bd3853318b15..bd3d61a72c8e 100644 --- a/docs/EN/AdvancedOptions/InsulinConcentration.md +++ b/docs/EN/AdvancedOptions/InsulinConcentration.md @@ -30,7 +30,7 @@ Insulin comes in different strengths, defined by the number of units per millili Using a concentration with a non-matching device is extremely dangerous and can cause a severe overdose or underdose. **Always triple-check that the insulin concentration matches the syringe, pen, or pump specifications.** ``` -## When using a non-standard concentration? +## When is a non-standard concentration used? While insulin pumps are designed for U100 insulin, certain specific medical situations require non-standard concentrations. These scenarios require extreme caution and meticulous management. diff --git a/docs/EN/CompatibleCgms/DexcomG6.md b/docs/EN/CompatibleCgms/DexcomG6.md index f538c7a297ae..3a33befcd356 100644 --- a/docs/EN/CompatibleCgms/DexcomG6.md +++ b/docs/EN/CompatibleCgms/DexcomG6.md @@ -40,7 +40,7 @@ Dexcom BYODA is now a very old version of the app and cannot be updated. - Install the downloaded apk - Enter sensor code and transmitter serial no. in patched app. - In phone settings go to apps > Dexcom G6 > permissions > additional permissions and press 'Access Dexcom app'. -- After short time BYODA should pick-up transmitter signal. +- After a short time BYODA should pick up the transmitter signal. ### Settings for AAPS diff --git a/docs/EN/CompatibleCgms/DexcomG7.md b/docs/EN/CompatibleCgms/DexcomG7.md index b99353154af2..9f19175d9f1b 100644 --- a/docs/EN/CompatibleCgms/DexcomG7.md +++ b/docs/EN/CompatibleCgms/DexcomG7.md @@ -13,9 +13,9 @@ Read [Smoothing method](../CompatibleCgms/SmoothingBloodGlucoseData.md) suggesti - xDrip connects to the sensor itself: uninstall the Dexcom app, as only one app can connect to the sensor. To keep the Dexcom app, use [xDrip Companion App](#DexcomG7-xdrip-companion-app) instead. - Follow the instructions here: [xDrip G7, ONE+ and Stelo](https://navid200.github.io/xDrip/docs/Dexcom/G7.html). A recent xDrip release is required — see the linked page for the minimum version. -- Select xDrip in [**Configuration → BG Source**](#Config-Builder-bg-source). +- Select xDrip in [**Configuration → BG Source**](#Config-Builder-bg-source). -- Adjust the xDrip settings according to the explanations on the xDrip settings page [xDrip settings](../CompatibleCgms/xDrip.md) +- Adjust the xDrip settings according to the explanations on the xDrip settings page [xDrip settings](../CompatibleCgms/xDrip.md). ## 2. Build Your Own Dexcom App (G7 only) @@ -30,7 +30,7 @@ Dexcom BYODA is now a very old version of the app and cannot be updated. Not ava - Uninstall the original Dexcom app - Install the downloaded apk - Enter sensor code in patched app -- After short time BYODA should pick-up transmitter signal +- After a short time BYODA should pick up the sensor signal. (DexcomG7-xdrip-companion-app)= diff --git a/docs/EN/CompatibleCgms/GeneralCGMRecommendation.md b/docs/EN/CompatibleCgms/GeneralCGMRecommendation.md index 83bab1e13ace..5401d1dbf428 100644 --- a/docs/EN/CompatibleCgms/GeneralCGMRecommendation.md +++ b/docs/EN/CompatibleCgms/GeneralCGMRecommendation.md @@ -9,7 +9,7 @@ Whichever CGM system you are using, if you are going to use blood based calibrat - Avoid calibrating when glucose levels are moving up or down. - Do “enough” calibrations – on official apps, you will be prompted for once or twice per day checks. On DIY systems you may not be, and should be careful about continuing without calibrations. - For sensors not requiring or not allowing calibration, check at least daily real blood sugar. AAPS will be as safe as your sensor readings are reliable. -- If it all possible, calibrate with some of your readings in a lower range (4-5mmol/L or 72-90mg/dL) and some at a slightly higher level (7-9mmol/L or 126-160mg/dL) as this provides a better range for the point/slope calibration. +- If at all possible, calibrate with some of your readings in a lower range (4-5mmol/L or 72-90mg/dL) and some at a slightly higher level (7-9mmol/L or 126-160mg/dL) as this provides a better range for the point/slope calibration. ## Setting sensor (G6) @@ -38,5 +38,5 @@ You might try to change settings for noise blocking in xDrip (Settings - Inter-A ![Sensor age on the Sensor row of the expanded status panel](../images/main/main_status_row_expanded.png) -The sensor age is shown on the **Sensor** row of the status panel on the main screen (tap the chevron to expand it). A negative age occurs if there is either a double "CGM Sensor Insert" [careportal entry](#aaps-screens-careportal) or a +The sensor age is shown on the **Sensor** row of the status panel on the main screen (tap the chevron to expand it). A negative age occurs if there is either a double "Sensor Insert" [careportal entry](#aaps-screens-careportal) or a sensor insert with wrong date. Open **Treatments history** (menu ☰), select the **Careportal** tab and delete the wrong entry. diff --git a/docs/EN/CompatibleCgms/Juggluco.md b/docs/EN/CompatibleCgms/Juggluco.md index 94e96d2804cc..94c8e36765f2 100644 --- a/docs/EN/CompatibleCgms/Juggluco.md +++ b/docs/EN/CompatibleCgms/Juggluco.md @@ -36,6 +36,6 @@ Juggluco can send blood glucose to xDrip which will then send them to AAPS. Enable Patched Libre in Juggluco (do not enable xDrip broadcast), confirm and save the dexdrip package information. Select the xDrip BG data source in AAPS. -Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS if necessary, when using a Libre 2/2+/3/3+ sensor, xDrip will average the minute-by-minute to 5 minutes readings and [also smoothen](#libre2-value-smoothing-raw-values) them. +Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS if necessary. When using a Libre 2/2+/3/3+ sensor, xDrip will average the minute-by-minute readings to 5-minute readings and [also smooth](#libre2-value-smoothing-raw-values) them. ![Juggluco to xDrip](../images/juggluco/Juggluco-xDrip+.png) diff --git a/docs/EN/CompatibleCgms/Libre2.md b/docs/EN/CompatibleCgms/Libre2.md index fa48717188a0..e94e2f557f1b 100644 --- a/docs/EN/CompatibleCgms/Libre2.md +++ b/docs/EN/CompatibleCgms/Libre2.md @@ -49,7 +49,7 @@ activation and make a new initial calibration. ![Configuration > BG Source with xDrip+ BG selected](../images/v4/Configuration/configuration_bg_source.png) - If AAPS does not receive BG values when phone is in airplane - mode, use 'Identify receiver' as describe on [xDrip settings page](#xdrip-identify-receiver). + mode, use 'Identify receiver' as described on [xDrip settings page](#xdrip-identify-receiver). ## 2. Use xDrip direct connection @@ -85,7 +85,7 @@ sensor info is available in the system menu. The raw values are very helpful when the blood sugar is moving fast. Even if the dots are jumpier you would detect the tendency much better -as using the smoothed line to make proper therapy decisions. +than using the smoothed line to make proper therapy decisions. → Hamburger menu → Settings → Less common settings → Advanced settings for Libre 2 @@ -96,7 +96,7 @@ as using the smoothed line to make proper therapy decisions. #### Calibration You can calibrate the Libre2 **with an offset of -40 mg/dL to +20 mg/dL -\[-2,2 mmol/L to +1,1 mmol/L\]** (intercept). The slope isn't changeable. Please check +\[-2.2 mmol/L to +1.1 mmol/L\]** (intercept). The slope isn't changeable. Please check by fingerpricking after setting a new sensor, keeping in mind it might not be accurate in the first 12 hours after insertion. Since there can be large differences to the blood measurements, verify every 24 hours and calibrate if necessary. If the sensor is completely off after a few days, it should then be replaced. diff --git a/docs/EN/CompatibleCgms/Libre2MinimalL00per.md b/docs/EN/CompatibleCgms/Libre2MinimalL00per.md index d432aa9e242a..1da998ae856d 100644 --- a/docs/EN/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/EN/CompatibleCgms/Libre2MinimalL00per.md @@ -82,7 +82,7 @@ It is strongly recommended to follow this process with a **new sensor**. While i (minimallooper-started-sensor)= -### What if my sensor is already started? Can I still get reading in xDrip? YES! +### What if my sensor is already started? Can I still get readings in xDrip? YES! Many people have asked if this method can be used with an already active sensor and I can say with a resounding **YES**, you can start an actively running sensor. @@ -94,7 +94,7 @@ Many people have asked if this method can be used with an already active sensor ## How to Start a FSL2 Sensor in Bluetooth Native mode using LL and xDrip -*NOTE: If there are settings in the screenshots that are not called out with a BOX specifically and are UNCHECKED (IE, disabled) then PLEASE KEEP THEM DISABLED. The screenshots are reflective of a working configuration for ALL settings shown. If you want to experiment turning other features on/off after you have a working sensor, you are free do to so at your own risk.* +*NOTE: If there are settings in the screenshots that are not called out with a BOX specifically and are UNCHECKED (IE, disabled) then PLEASE KEEP THEM DISABLED. The screenshots are reflective of a working configuration for ALL settings shown. If you want to experiment turning other features on/off after you have a working sensor, you are free to do so at your own risk.* (minimallooper-step1)= @@ -253,7 +253,7 @@ On the **Start New Sensor** screen press **Start Sensor**. A prompt will ask **D ### Step 7: Wait 60 seconds and NFC Scan the sensor again -A second NFC scan is needed in order to **ADD** the sensor as the Bluetooth device from which xDrip will use to retrieve the readings. Once complete you will see a notification stating **NEW SENSOR STARTED**. +A second NFC scan is needed in order to **ADD** the sensor as the Bluetooth device that xDrip will use to retrieve the readings. Once complete you will see a notification stating **NEW SENSOR STARTED**. ![xDrip scan](../images/minimal00per/xdripscan2.png) @@ -288,7 +288,7 @@ It will change xDrip Bluetooth settings to: ### Step 9: Verify Sensor is connected and delivering data -Press the Hamburger menu in the upper left of the xDrip Overview screen and select **System Status**. On the System Status screen the active **Bluetooth Device:** field displays the FSL2 Bluetooth naming convention of **ABB___XXXXXXXXXXX**, where the XXX’s represent the sensor serial number. The **Connection Status** field displays **Connected** and the **Sensor Start:** field displayed the time the sensor was started. +Press the Hamburger menu in the upper left of the xDrip Overview screen and select **System Status**. On the System Status screen the active **Bluetooth Device:** field displays the FSL2 Bluetooth naming convention of **ABB___XXXXXXXXXXX**, where the XXX’s represent the sensor serial number. The **Connection Status** field displays **Connected** and the **Sensor Start:** field displays the time the sensor was started. ![xDrip scan](../images/minimal00per/xdripSSlog.png) @@ -301,8 +301,8 @@ On the **BT Device** (swipe left) screen you can verify further connection detai - **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - **Device Mac Address**: This is the hardware ID of the sensor -- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. -- **Slowest wake up**: You can ignore this. xDrip doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip doesn't spend its time waiting for readings: it will start expecting them after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. - **Next Wake up**: Should say 5 minutes ![xDrip scan](../images/minimal00per/xdripSStat.png) @@ -313,7 +313,7 @@ On the **BT Device** (swipe left) screen you can verify further connection detai - **Using LL NFC Scans AFTER bonding/pairing in xDrip is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip needs to be completed first. Always look at xDrip and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. -- - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip is not aware of the new key and will not be able to communicate with the sensor. +- **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip is not aware of the new key and will not be able to communicate with the sensor. - Several users have reported that the LL app can be restarted after successfully starting the sensor and receiving readings in xDrip. In the LL app Android permission you simply need to turn off the **Allow Location** setting. Once this is done you should be able to use the LL app and xDrip simultaneously. I would recommend that you don't select a default app for NFC scanning and pick which app you want to read the sensor for an NFC scan. Also, DON'T FORGET, on your next sensor change to force close the LL app after the initial warmup NFC scan on the new sensor. After the sensor is configured and receiving readings in xDrip you can then start the LL app again. @@ -399,7 +399,7 @@ On the **BT Device** (swipe left) screen you can verify further connection detai - **FSL** - FreeStyle Libre - **Libre 1 (FSL1)** - NFC only. First version of the sensor - - **FSL2 (FSL2)** - Bluetooth and NFC. Second version of the sensor. + - **Libre 2 (FSL2)** - Bluetooth and NFC. Second version of the sensor. - **Libre 3 (FSL3)** - Bluetooth and NFC. Third smaller version of the sensor. Not supported by OOP2 (see Juggluco). @@ -413,7 +413,7 @@ On the **BT Device** (swipe left) screen you can verify further connection detai - **OOP1** - Out of Process Algorithm version 1, the 3rd party app that receives raw values (delivered to xDrip from the sensor by Bluetooth or NFC scan) and then uses an algorithm (very similar to the hardware algorithm on the sensor chip) to process the raw values and returns a calibrated (by the OOP1 algorithm, not by xDrip’s native calibrations) blood sugar back to xDrip to either display or be further processed with xDrip’s calibration (with a finger pick blood calibration) if needed. -- **OOP2** - Out of Process Algorithm version 2, the 3rd party app that receives encrypted data delivered to from the FSL 2 sensor (by Bluetooth or NFC scan) and then decrypts the encrypted data. Once decrypted, the data is then sent to xDrip. +- **OOP2** - Out of Process Algorithm version 2, the 3rd party app that receives encrypted data delivered from the FSL 2 sensor (by Bluetooth or NFC scan) and then decrypts the encrypted data. Once decrypted, the data is then sent to xDrip.   @@ -474,4 +474,4 @@ Sensor age has not advanced might also be a sign your sensor has issues. This me 2. xDrip menu -> System status -> Forget device 3. Scan the sensor with xDrip NFC. Wait at least one minute 4. xDrip menu -> Start sensor. Wait at least one minute -5. Scan the sensor with xDrip NFC, a few times, always waiting at least one minute between two scans +5. Scan the sensor with xDrip NFC, a few times, always waiting at least one minute between two scans. diff --git a/docs/EN/CompatibleCgms/Libre3.md b/docs/EN/CompatibleCgms/Libre3.md index 11dc80dcf69f..756f6458cce5 100644 --- a/docs/EN/CompatibleCgms/Libre3.md +++ b/docs/EN/CompatibleCgms/Libre3.md @@ -24,7 +24,7 @@ This method uses Juggluco to receive raw, 1-minute interval data from the sensor Download and install the Juggluco app from [here](https://www.juggluco.nl/Juggluco/download.html). Follow the instructions [here]( https://www.juggluco.nl/Juggluco/libre3/) -Make sure you send the glucose values to xDrip: In Juggluco's settings you can configure Juggluco to send its glucose value to other apps. Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip +Make sure you send the glucose values to xDrip: In Juggluco's settings you can configure Juggluco to send its glucose value to other apps. Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip. ### Step 2: Setup xDrip @@ -71,7 +71,7 @@ After a sensor change xDrip will automatically detect the new sensor and will de ![Terminate sensor](../images/libre3/step_14.jpg) -Note: When two sensors are active Juggluco will send the most recent value from either sensor to xDrip. If the sensors are not calibrated and reading BG similarly, this may result in jumpy BG values being reported to xDrip. If you terminate the wrong sensor, you can reactivate it by simply scanning the sensor. +Note: When two sensors are active Juggluco will send the most recent value from either sensor to xDrip. If the sensors are not calibrated to read BG similarly, this may result in jumpy BG values being reported to xDrip. If you terminate the wrong sensor, you can reactivate it by simply scanning the sensor. ## Switch sensor between Libre 3 and Juggluco app @@ -101,4 +101,4 @@ In order to switch from the Libre 3 app to Juggluco, you need to force-stop Libr Original instructions: [jkaltes website](https://www.juggluco.nl/Juggluco/libre3/) -Additional Github repo: [Github link](https://github.com/maheini/FreeStyle-Libre-3-patch) +Additional GitHub repo: [GitHub link](https://github.com/maheini/FreeStyle-Libre-3-patch) diff --git a/docs/EN/CompatibleCgms/OttaiM8.md b/docs/EN/CompatibleCgms/OttaiM8.md index e8813c0abf49..93e829d37ddb 100644 --- a/docs/EN/CompatibleCgms/OttaiM8.md +++ b/docs/EN/CompatibleCgms/OttaiM8.md @@ -8,7 +8,7 @@ - Start sensor -- Select **Syai/Ottai** in [Configuration, BG Source](#Config-Builder-bg-source). +- Select **Syai/Ottai** in [**Configuration → BG Source**](#Config-Builder-bg-source). Enable broadcast in the Ottai app: diff --git a/docs/EN/CompatibleCgms/SyaiTagX1.md b/docs/EN/CompatibleCgms/SyaiTagX1.md index fb14bff038b7..873e496c64c7 100644 --- a/docs/EN/CompatibleCgms/SyaiTagX1.md +++ b/docs/EN/CompatibleCgms/SyaiTagX1.md @@ -7,7 +7,7 @@ - Start X1 sensor -- Select **Syai/Ottai** in [Configuration, BG Source](#Config-Builder-bg-source). +- Select **Syai/Ottai** in [**Configuration → BG Source**](#Config-Builder-bg-source). Enable broadcast in the Syai app: diff --git a/docs/EN/CompatibleCgms/xDrip.md b/docs/EN/CompatibleCgms/xDrip.md index e793a40df6e9..db7e86ef61b1 100644 --- a/docs/EN/CompatibleCgms/xDrip.md +++ b/docs/EN/CompatibleCgms/xDrip.md @@ -10,7 +10,7 @@ Disable battery optimization and allow background activity for the xDrip app. You shouldn't let any other app upload data (blood glucose and treatments) to Nightscout. -→ Hamburger Menu (1) → Settings (2) → Cloud Upload (3) -> Nightscout Sync (REST-API)(4) → Switch **OFF** `Enabled` (5) +→ Hamburger Menu (1) → Settings (2) → Cloud Upload (3) → Nightscout Sync (REST-API) (4) → Switch **OFF** `Enabled` (5) ![xDrip Basic Settings 1](../images/xDrip_Basic1.png) @@ -36,7 +36,7 @@ Option `Alert on failures` should also be deactivated (10). Otherwise you will g ### **Inter-app Settings** (Broadcast) -If you are going to use AAPS and the data should be forwarded to i.e. AAPS you have to activate broadcasting in xDrip in Inter-App settings. +If you use AAPS, you must activate broadcasting in xDrip's Inter-App settings so the data is forwarded to AAPS. → Hamburger Menu (1) → Settings (2) → Inter-app settings (3) → Broadcast locally **ON** (4) diff --git a/docs/EN/CompatiblePhones/Jelly.md b/docs/EN/CompatiblePhones/Jelly.md index 309eaf430778..0a4f407a7a88 100644 --- a/docs/EN/CompatiblePhones/Jelly.md +++ b/docs/EN/CompatiblePhones/Jelly.md @@ -14,7 +14,7 @@ **Disadvantages** -* Recommended only for experienced loopers (some settings are not recognizable, you have to know from experience with a big Android AAPS phone, how and where what is located. Some AAPS buttons are hard to touch with a lot of feeling, but not with stubby fingers.) +* Recommended only for experienced loopers. Some settings are not easy to recognize: you have to know from experience with a big Android AAPS phone how and where things are located. Some AAPS buttons are small and hard to tap: you need a precise touch, not stubby fingers. * Can only be used as LooperPhone. It's better to have a normal smartphone in your pocket. ### Battery life optimization @@ -43,7 +43,7 @@ Remember to disable Google Play Protect. ### Remote Connection for Wear apk -For certain smart watches, like the Samsung Galaxy, 'Remote Connection' under Samsung Galaxy's Advanced Features must be switched **on** to use the Jelly, **Wear.apk** & **AAPS** remotely via Wi-Fi. +For certain smart watches, like the Samsung Galaxy, 'Remote connection' under Advanced features in the Galaxy Wearable app must be switched **on** to use the Jelly, **Wear.apk** & **AAPS** remotely via Wi-Fi. ![Galaxy Wearable, Advanced features, Remote connection switched on](../images/wearos/galaxy_wearable_remote_connection.png) diff --git a/docs/EN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/EN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md index 2706d49a9d17..99f2af256afa 100644 --- a/docs/EN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md +++ b/docs/EN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md @@ -317,7 +317,7 @@ If your battery life is significantly shorter than the ranges given above, pleas ### Extended bolus, multiwave bolus The OpenAPS algorithm does not support a parallel extended bolus or multiwave bolus. But a similar treatment can be achieved by the following alternatives: * Use **e-Carbs** when entering carbs or using the Bolus wizard by entering the carbs of the full meal and the duration you expect the carbs to arrive as glucose in your blood. The system will then calculate small carbs equally distributed over the whole duration which will cause the algorithm to provide equivalent insulin dosing while still permanently checking the overall rise/decrease of the blood glucose level. For a multiwave bolus approach, you can also combine a smaller immediate bolus with e-carbs. -* Before eating, set a temporary **Eating Soon** target with glucose 80 for several hours (press the target on the main screen, or **Manage** > **Temp Target**). The duration should be based on the interval you would choose for an extended bolus. This will keep your target lower than usual and therefore increase the amount of insulin delivered. +* Before eating, set a temporary **Eating Soon** target of 80 mg/dL (4.4 mmol/L) for several hours (press the target on the main screen, or **Manage** > **Temp Target**). The duration should be based on the interval you would choose for an extended bolus. This will keep your target lower than usual and therefore increase the amount of insulin delivered. * Then use the **Bolus wizard** to enter the full carbs of the meal, but do not directly apply the values it suggests. If a multiwave-like bolus is to be delivered, correct the insulin dosage down. Depending on the meal, the algorithm now has to deliver additional SMBs or higher temporary basal rates to counteract the increase in blood sugar. Here, the safety limitation of the basal rate (Max U/h, Maximum basal IOB) should be very carefully experimented with and, if necessary, temporarily changed. * Don't use the extended or multiwave bolus directly on the pump. The driver does not support them (see [Before you begin](#combov2-before-you-begin)); if a multiwave bolus is given on the pump anyway, **AAPS** records it from the pump history as a normal bolus plus an extended bolus, so it is counted in IOB. An extended bolus does not work in a closed loop environment (see [this page](#extended-bolus-and-why-they-wont-work-in-closed-loop-environment) for details). diff --git a/docs/EN/CompatiblePumps/Accu-Chek-Insight-Pump.md b/docs/EN/CompatiblePumps/Accu-Chek-Insight-Pump.md index 262d2968d00a..30df1720b53e 100644 --- a/docs/EN/CompatiblePumps/Accu-Chek-Insight-Pump.md +++ b/docs/EN/CompatiblePumps/Accu-Chek-Insight-Pump.md @@ -97,7 +97,7 @@ Open the settings with **Settings** on the **Accu-Chek Insight** card in **Confi ![Accu-Chek Insight driver settings](../images/v4/Pumps/accu_chek_insight_settings.png) In the Insight settings in **AAPS** you can enable the following options: -* **Log reservoir changes**: automatically records an insulin cartridge change when you run the "fill cannula" program on the pump. +* **Log reservoir changes**: automatically records an insulin cartridge change when you change the cartridge in the pump. * **Log tube changes**: adds a note to the **AAPS** database when you run the "tube filling" program on the pump. @@ -168,7 +168,7 @@ Firmware version can be found in the menu. ## Battery replacement -Battery life for Insight when looping range from 10 to 14 days, max. 20 days. The user reporting this is using Energizer lithium batteries. +Battery life for Insight when looping ranges from 10 to 14 days, maximum 20 days. The user reporting this is using Energizer lithium batteries. The Insight pump has a small internal battery to keep essential functions like the clock running while you are changing the removable battery. If changing the battery takes too long, this internal battery may run out of power, the clock will reset, and you will be asked to enter a new time and date after inserting a new battery. If this happens, all entries in AAPS prior to the battery change will no longer be included in calculations as the correct time cannot be identified properly. diff --git a/docs/EN/CompatiblePumps/CareLevo.md b/docs/EN/CompatiblePumps/CareLevo.md index ade7e75636b8..ed739774e30b 100644 --- a/docs/EN/CompatiblePumps/CareLevo.md +++ b/docs/EN/CompatiblePumps/CareLevo.md @@ -134,7 +134,7 @@ Insulin delivery has stopped. Act now: * **Low Insulin**: less than 10 U remain. Deactivate the patch and change it. * **Patch Expired**: the patch reached the end of its life. Deactivate the patch and change it. * **Low Battery**: discard the patch and change it. -* **High/Low Temperature**: move to a suitable temperature, between 40 ℉ and 99 ℉ (5 ℃ and 37 ℃). +* **High/Low Temperature**: move to a suitable temperature, between 40 ℉ and 99 ℉ (4.4 ℃ and 37.2 ℃). * **Auto-Off**: the patch stopped because the Auto-Off alert was ignored. Press **Start Insulin** to restart basal delivery. * **Patch Application Timeout**, **Self-Diagnosis Failed**, **Patch Error**, **Occlusion** and **Needle Insertion Error**: deactivate the patch and change it. @@ -145,7 +145,7 @@ Insulin delivery continues, but something needs your attention: * **Low Insulin**: the reservoir reached the amount set in **Low Insulin Notification Setting**. Prepare to change the patch. * **Patch Will Expire Soon** and **Patch Operating Life Expired**: change the patch. * **Low Battery**: prepare to change the patch. -* **High/Low Temperature**: delivery is paused until the patch is back between 40 ℉ and 99 ℉. +* **High/Low Temperature**: delivery is paused until the patch is back between 40 ℉ and 99 ℉ (4.4 ℃ and 37.2 ℃). * **Auto-Off**: tap **OK**. If ignored, the alert escalates to a critical alarm and delivery stops. * **Patch Activation Incomplete**: tap **OK** to complete the activation. * **Start Insulin**: the pause you set has ended. Tap **Start Insulin** to resume delivery. diff --git a/docs/EN/CompatiblePumps/DanaR-Insulin-Pump.md b/docs/EN/CompatiblePumps/DanaR-Insulin-Pump.md index 5cfeedef0575..8b0f508aa5e3 100644 --- a/docs/EN/CompatiblePumps/DanaR-Insulin-Pump.md +++ b/docs/EN/CompatiblePumps/DanaR-Insulin-Pump.md @@ -15,7 +15,7 @@ _These instructions are for configuring the app and your pump if you have a Dana ![DanaR pump](../images/danar1.png) * Go to Main Menu > Setting > Discovery -* In phone settings go to Bluetooth, scan for nearby devices, select your DanaR serial number and input your password (Pairing password is 0000). If DanaR is not showing in scan then restart phone and take DanaR battery out, replace and start these two steps again. +* In phone settings go to Bluetooth, scan for nearby devices, select your DanaR serial number and input your password (Pairing password is 0000). If DanaR is not showing in scan then restart phone and take DanaR battery out, replace and start these two steps again. * In **AAPS**, open the **menu** (☰) in the top-left corner, go to **Configuration** > **Pump** and select the type of DanaR you have (**DanaR**, **DanaR Korean** or **DanaRv2**). diff --git a/docs/EN/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/EN/CompatiblePumps/Future-possible-Pump-Drivers.md index df3e6af8346c..787f70bf079c 100644 --- a/docs/EN/CompatiblePumps/Future-possible-Pump-Drivers.md +++ b/docs/EN/CompatiblePumps/Future-possible-Pump-Drivers.md @@ -1,6 +1,6 @@ # Future (possible) Pump Drivers -This is list of some Pumps floating around there, and status of support for them in any of Looping systems and then status in AAPS. On end there is some info, what is required for a pump to be "Loop capable". +This is a list of some pumps on the market, the status of their support in other looping systems, and their status in AAPS. At the end there is some information about what a pump needs to be "Loop capable". ```{contents} Table of contents :depth: 1 @@ -43,7 +43,7 @@ Tandem: t:Mobi ([Homepage](https://www.tandemdiabetes.com/)) ### Willcare Insulin pump ([Homepage](http://shinmyungmedi.com/en/)) -**Loop status:** At the moment its not Loop candidate, but we were contacted by their staff and they interested in extending their pump to be loopable (at the moment I think its missing only get/set profile commands). +**Loop status:** At the moment it is not a Loop candidate, but their staff contacted us and they are interested in making the pump loopable (it seems to be missing only the get/set profile commands). **Hardware requirement for AAPS:** None. It seems to be BT enabled. diff --git a/docs/EN/CompatiblePumps/MedtronicPump.md b/docs/EN/CompatiblePumps/MedtronicPump.md index 4c319a7bba7d..769fdf6639ef 100644 --- a/docs/EN/CompatiblePumps/MedtronicPump.md +++ b/docs/EN/CompatiblePumps/MedtronicPump.md @@ -70,13 +70,13 @@ When configuring your Medtronic pump with the setup wizard it is possible that y While setting up AAPS to work with your medtronic pump you need to set the following items in **Settings** (see the settings picture above): - **Pump Serial Number**: Displayed on the back of your pump and starts with SN. You should only enter the 6 numbers shown without any alphabetic characters (e.g. 123456). - **Pump Type**: The model pump you are using (e.g. 522). -- **Pump Frequency**: There are two options based on where your pump was originally distributed. Please check the [FAQ](#MedtronicPump-faq) if you are unsure which option to select): +- **Pump Frequency**: There are two options based on where your pump was originally distributed. Please check the [FAQ](#MedtronicPump-faq) if you are unsure which option to select: - for US & Canada, frequency used is 916 MHz - for Worldwide, frequency used is 868 MHz - **Max Basal on Pump (U/h)**: This needs to match the setting set on your pump (see Configuration of the pump above). Again this setting must be carefully selected as it will determine how much AAPS can deliver via your basal rate. This will effectively set the maximum temporary basal rate. As an example, setting this value to four times your maximum standard basal rate would allow a 400% Temporary Basal Rate. The maximum value permitted by the pump is 34.9 units per hour. - **Max Bolus on Pump (U)** (in an hour): This needs to match the setting set on your pump (see Configuration of the pump above). This setting should be carefully considered as it determines how large a bolus AAPS can ever set. - **Delay before Bolus is started (s)**: The number of seconds after a bolus is issued before the command is actually sent to the pump. This period of time allows the user to cancel the bolus in the event a bolus command is sent in error. It is not possible to cancel a bolus that has started via AAPS. The only way to cancel a bolus that has already started is to suspend the pump manually followed by resuming it. -- **Medtronic Encoding**: Determines if the medtronic encoding is carried out. Selecting Hardware encoding (i.e. carried out by the Rileylink compatible device) is preferred as this results in less data being sent. Selecting Software encoding (i.e. carried out by AAPS) can help in the event frequent disconnects are seen. This setting will be ignored if you have firmware version 0.x on Rileylink devices. +- **Medtronic Encoding**: Determines where the Medtronic encoding is carried out (hardware or software). Selecting Hardware encoding (i.e. carried out by the Rileylink compatible device) is preferred as this results in less data being sent. Selecting Software encoding (i.e. carried out by AAPS) can help in the event frequent disconnects are seen. This setting will be ignored if you have firmware version 0.x on Rileylink devices. - **Battery Type (Power View)**: In order to correctly determine the remaining battery power level you should select the type of AAA battery in use. When a value other than simple view is selected AAPS will display the remaining calculated battery percentage level and volts. The following options are available: - Not selected (Simple view) diff --git a/docs/EN/CompatiblePumps/MedtrumNano.md b/docs/EN/CompatiblePumps/MedtrumNano.md index 2add86fb8a09..9e4b66f4e987 100644 --- a/docs/EN/CompatiblePumps/MedtrumNano.md +++ b/docs/EN/CompatiblePumps/MedtrumNano.md @@ -408,7 +408,7 @@ All of the development work for the Medtrum driver is done by the community on a - **Level 0:** Read the relevant section of this documentation to ensure you understand how the functionality with which you are experiencing difficulty is supposed to work. - **Level 1:** If you are still encountering problems that you are not able to resolve by using this document, then please go to the *#Medtrum* channel on **Discord** by using [this invite link](https://discord.gg/4fQUWHZ4Mw). -- **Level 2:** Search existing issues to see if your issue has already been reported at [Issues](https://github.com/nightscout/AAPS/issues) -if it exists, please confirm/comment/add information on your problem. +- **Level 2:** Search existing issues to see if your issue has already been reported at [Issues](https://github.com/nightscout/AAPS/issues). +If it exists, please confirm/comment/add information on your problem. If not, please create a [new issue](https://github.com/nightscout/AndroidAPS/issues) and attach [your log files](../GettingHelp/AccessingLogFiles.md). - **Be patient - most of the members of our community consist of good-natured volunteers, and solving issues often requires time and patience from both users and developers.** \ No newline at end of file diff --git a/docs/EN/CompatiblePumps/OmnipodDASH.md b/docs/EN/CompatiblePumps/OmnipodDASH.md index 893d6a42d3e6..3442c3af5e63 100644 --- a/docs/EN/CompatiblePumps/OmnipodDASH.md +++ b/docs/EN/CompatiblePumps/OmnipodDASH.md @@ -38,16 +38,16 @@ Key characteristics of the **Omnipod DASH** ('DASH'): ![Omnipod Pod](../images/DASH_images/Omnipod_Pod.png) -- **A Compatible Android phone** with a Bluetooth Low Energy (BLE) (see [Phones](../Getting-Started/Phones.md) for more info), additionally the following information will help guide you on other key considerations around successfully activating and using the DASH on a compatible phone: +- **A Compatible Android phone** with Bluetooth Low Energy (BLE) (see [Phones](../Getting-Started/Phones.md) for more info). In addition, the following information will help guide you on other key considerations around successfully activating and using the DASH on a compatible phone: - The **AAPS** Omnipod Dash driver connects with the DASH Pod using Bluetooth. **AAPS** will automatically establish a new Bluetooth connection to the Pod every time it needs to send a command (e.g a Bolus), after sending the command the Bluetooth connection is immediately disconnected. - **NOTE:** - The Bluetooth connection can be interrupted/disturbed by other Bluetooth devices linked to the phone that is running **AAPS**, like earbuds etc... Devices like this can cause connection errors or pod activation issues on some models of phones. It's a good idea to review the [tested hardware setups](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) list for known working configurations when choosing the phone for an Omnipod DASH setup. - - There are a number of known issues with Bluetooth which can cause pod activation problems (See [Troubleshooting](#troubleshooting) for advice on other Bluetooth issues) specifically the [Bluetooth related issues](#omnipod-dash-bluetooth-related-issues) section. + - There are a number of known issues with Bluetooth which can cause pod activation problems (See [Troubleshooting](#omnipod-dash-troubleshooting) for advice on other Bluetooth issues) specifically the [Bluetooth related issues](#omnipod-dash-bluetooth-related-issues) section. - The phone must run **Android 12 or newer**, with **AAPS** built and installed using the [**Build APK**](../SettingUpAaps/BuildingAaps.md) instructions. Always run the latest released version. - A supported [**Continuous Glucose Monitor (CGM)**](../Getting-Started/CompatiblesCgms.md) -The instructions below explain how to activate a new pod session using **AAPS**. You should wait for your current Pod to be close expiry, as you will need to activate a new Pod with **AAPS**. Once a pod is de-activated it cannot be reused/re-activated, the de-activation is final. +The instructions below explain how to activate a new pod session using **AAPS**. You should wait for your current Pod to be close to expiry, as you will need to activate a new Pod with **AAPS**. Once a pod is de-activated it cannot be reused/re-activated, the de-activation is final. ## Before you begin @@ -618,7 +618,7 @@ A failed pod cannot be used again. Check your blood glucose, then [deactivate th ### Preventing error 49 pod failures This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. This is when the driver and Pod disagree on the actual state. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. -The exact origin of a “49 pod failure” often is hard to trace. In situations that are suspected for this failure to occur (for instance on application crashes, running a development version or re-installation). +The exact origin of a “49 pod failure” often is hard to trace. It can happen, for example, after application crashes, when running a development version or after a re-installation. --- @@ -697,8 +697,8 @@ A summary of the main alerts that you may encounter is listed below: - *Pod Fault: XXX NAME*, followed by *Ref: ...*: the pod has failed and stopped delivering insulin. Change the pod. See [Pod Failures](#omnipod-dash-pod-failures). - *No Active Pod*: no pod session was found. This notification keeps coming back until you activate a new pod. Once a pod is activated, it disappears automatically. - *Insulin delivery suspended*: the pod has suspended insulin delivery. See [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery). -- *Setting basal profile might have failed. Delivery might be suspended! Please manually refresh the Pod status from the Omnipod tab and resume delivery if needed.* - Setting the basal **Profile** on the pod may have failed. Press **Refresh** on the DASH pump screen (the message still says "Omnipod tab"), and press **Resume Delivery** if it is shown. +- *Setting basal profile might have failed. Delivery might be suspended! Please manually refresh the Pod status on the pump screen and resume delivery if needed.* + Setting the basal **Profile** on the pod may have failed. Press **Refresh** on the DASH pump screen, and press **Resume Delivery** if it is shown. - *Unable to verify whether SMB (X U) succeeded. Refresh pod status to confirm or deny this command.* **AAPS** could not confirm that the **SMB** was delivered. Press **Refresh** on the DASH pump screen and check the **Last bolus** field. - *Bolus delivery status uncertain. Refresh pod status to confirm or deny.* @@ -714,8 +714,8 @@ All of the development work for the DASH is done by the community on a **volunte - **Level 0:** Read the relevant section of this documentation to ensure you understand how the functionality with which you are experiencing difficulty is supposed to work. - **Level 1:** If you are still encountering problems that you are not able to resolve by using this document, then please go to the *#AAPS* channel on **Discord** by using [this invite link](https://discord.gg/4fQUWHZ4Mw). There are also numerous Facebook and other groups you can ask in too (see [**Getting Help**](../GettingHelp/WhereCanIGetHelp.md)) -- **Level 2:** Search existing issues to see if your issue has already been reported at [Issues](https://github.com/nightscout/AndroidAPS/issues) -if it exists, please confirm/comment/add information on your problem. +- **Level 2:** Search existing issues to see if your issue has already been reported at [Issues](https://github.com/nightscout/AndroidAPS/issues). +If it exists, please confirm/comment/add information on your problem. If not, please create a [new issue](https://github.com/nightscout/AndroidAPS/issues) and attach [your log files](../GettingHelp/AccessingLogFiles.md). - **Be patient - most of the members of our community consist of good-natured volunteers, and solving issues often requires time and patience from both users and developers.** diff --git a/docs/EN/CompatiblePumps/OmnipodEros.md b/docs/EN/CompatiblePumps/OmnipodEros.md index a0051b35a249..8e16dc22abd5 100644 --- a/docs/EN/CompatiblePumps/OmnipodEros.md +++ b/docs/EN/CompatiblePumps/OmnipodEros.md @@ -35,7 +35,7 @@ The [Omnipod System](https://www.omnipod.com/current-podders/resources/omnipod-s - ![Omnipod_Pod](../images/omnipod/Omnipod_Pod.png) **Insulin Delivery Device** -> Component that will interpret commands received from the Pod communication device originating from your AAPS enable phone. +> Component that will interpret commands received from the Pod communication device originating from your AAPS enabled phone. > > > - A new Omnipod pod (Eros generation - **NOT DASH**) @@ -47,7 +47,7 @@ In this page, **RileyLink** means any of the pod communication devices listed ab **SAFETY FIRST** - do not attempt this process in an environment where you cannot recover from an error (extra pods, insulin, charged RileyLink, and phone devices are must-haves). -**Your Omnipod PDM will no longer work after the AAPS Omnipod driver activates your pod**. Previously you used your Omnipod PDM to send commands to your Omnipod Eros pod. An Omnipod Eros pod only allows a single device to send communication to it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate an Omnipod Eros pod with your RileyLink through the AAPS Omnipod driver, **you will no longer be able to use your PDM with your pod**. The AAPS Omnipod driver with the RileyLink is now your acting PDM. *This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup, and for emergencies with AAPS is not working correctly.* +**Your Omnipod PDM will no longer work after the AAPS Omnipod driver activates your pod**. Previously you used your Omnipod PDM to send commands to your Omnipod Eros pod. An Omnipod Eros pod only allows a single device to send communication to it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate an Omnipod Eros pod with your RileyLink through the AAPS Omnipod driver, **you will no longer be able to use your PDM with your pod**. The AAPS Omnipod driver with the RileyLink is now your acting PDM. *This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup, and for emergencies when AAPS is not working correctly.* **Only one RileyLink at a time can communicate with a pod.** **AAPS** remembers one paired RileyLink. If you pair a different one, it replaces the previous one. @@ -281,7 +281,7 @@ To deactivate a pod (either from expiration or from a pod failure): The process below shows you how to suspend and resume insulin delivery. -*NOTE - if you do not see a **Suspend** button*, it is hidden by default. Enable **Show Suspend Delivery button in Omnipod tab** in the [Omnipod settings](#OmnipodEros-omnipod-settings) under **Other**. +*NOTE - if you do not see a **Suspend** button*, it is hidden by default. Enable **Show Suspend Delivery button on the pump screen** in the [Omnipod settings](#OmnipodEros-omnipod-settings) under **Other**. #### Suspending Insulin Delivery @@ -592,7 +592,7 @@ The buttons at the bottom of the pump screen change depending on the situation. The screenshot above is from an earlier **AAPS** version. In **AAPS** 4 this is a text button named **Set time** on the Omnipod pump screen. ``` -- **Suspend:** Suspends insulin delivery on the active pod. Only shown if enabled in the settings (**Show Suspend Delivery button in Omnipod tab**). +- **Suspend:** Suspends insulin delivery on the active pod. Only shown if enabled in the settings (**Show Suspend Delivery button on the pump screen**). ![suspend](../images/omnipod/ICONS/omnipod_overview_suspend.png) @@ -783,7 +783,7 @@ Provides AAPS notifications and audible phone alerts when it is uncertain if TBR Provides advanced settings to assist debugging. -- **Show Suspend Delivery button in Omnipod tab:** Hide or display the **Suspend** button on the Omnipod pump screen. +- **Show Suspend Delivery button on the pump screen:** Hide or display the **Suspend** button on the Omnipod pump screen. - **Show Pulse Log button in Pod Management menu:** This setting is still listed, but the current version of the pump screen has no **Pulse Log** button. - **Show RileyLink Stats button in Pod Management menu:** Hide or display the **RileyLink Stats** button on the Omnipod pump screen. @@ -897,7 +897,7 @@ No active Pod session detected. This alert can temporarily be dismissed by press Informational alert that Pod has been suspended. -#### Setting basal profile failed. Delivery might be suspended! Please manually refresh the Pod status from the Omnipod tab and resume delivery if needed. +#### Setting basal profile failed. Delivery might be suspended! Please manually refresh the Pod status on the pump screen and resume delivery if needed. Informational alert that the Pod basal profile setting has failed. Open the Omnipod pump screen and press **Refresh**, then **Resume Delivery** if needed. diff --git a/docs/EN/DailyLifeWithAaps/AapsScreens.md b/docs/EN/DailyLifeWithAaps/AapsScreens.md index 164ac858578c..34af539a80c9 100644 --- a/docs/EN/DailyLifeWithAaps/AapsScreens.md +++ b/docs/EN/DailyLifeWithAaps/AapsScreens.md @@ -130,7 +130,7 @@ Your loop keeps running, but only to protect you against lows: **AAPS** can stil ``` You need to find out why you get duplicate BGs: -* Is Dexcom bridge enabled on your Nightscout site? Disable the bridge by going to the administration panel of your Nightscout instance, edit the "enable" variable and remove the "bridge" part there. (For heroku [details can be found here](https://nightscout.github.io/troubleshoot/troubleshoot/#heroku).) +* Is Dexcom bridge enabled on your Nightscout site? Disable the bridge by going to the administration panel of your Nightscout instance, edit the "enable" variable and remove the "bridge" part there. (For Heroku [details can be found here](https://nightscout.github.io/troubleshoot/troubleshoot/#heroku).) * Do multiple sources upload your BG to Nightscout? If you use the BYODA app, enable the upload in **AAPS** but do not enable it in xDrip, if you use that. * Do you have any followers that might receive your BG but do also upload it again to your Nightscout site? * Last resort: In [NSClient settings](#Preferences-nsclient), select the Synchronization settings and disable the "Receive CGM data from NS" option. @@ -328,7 +328,7 @@ When **PRED** is on, AAPS draws its predictions as **dotted lines** to the right When two predictions give the same values, their dots overlap and you only see one of the colors (for example, UAM on top of IOB when BG is flat). -* **COB** line (orange): [carbs on board](CobCalculation) (orange is used throughout AAPS for COB and carbs) +* **COB** line (orange): [carbs on board](CobCalculation.md) (orange is used throughout AAPS for COB and carbs) This prediction line shows where your BG (not where COB itself!) will go based on the current **Profile** settings, assuming that the deviations due to carb absorption remain constant. This line only appears if there are known COB. * **IOB** line (blue): insulin on board (blue is used throughout AAPS for IOB and insulin) @@ -347,7 +347,7 @@ When two predictions give the same values, their dots overlap and you only see o * **aCOB** line (pale, see-through orange): accelerated carbohydrate absorption - Similar to COB, but assuming a static 10 mg/dL/5m (-0.555 mmol/L/5m) carb absorption rate. Deprecated and of limited usefulness. + Similar to COB, but assuming a static 10 mg/dL/5m (0.555 mmol/L/5m) carb absorption rate. Deprecated and of limited usefulness. *This line appears only when the older [AMA](#Config-Builder-aps) algorithm is used.* @@ -465,7 +465,7 @@ This line shows the degree to which BG ‘should’ rise or fall based on insuli ![Deviations and BGI](../images/main/graph_dev_bgi.png) -It is a good combination to display this line along with the Deviation bars. They share the same scale, but it is a different one than the other optional data, so it is a good idea to display them on a separate graph, as shown above. Comparing the BGI line and the Deviation bars is another way to understand how **BG** fluctuates. Here, at the time marked **1**, the Deviation bars are well above the BGI line: BG rises more than insulin activity alone explains (for example after carbs). At the time marked **2**, the Deviation bars are below zero (red): BG is lower than the algorithm expected. +It is a good combination to display this line along with the Deviation bars. They share the same scale, but it is a different one than the other optional data, so it is a good idea to display them on a separate graph, as shown above. Comparing the BGI line and the Deviation bars is another way to understand how **BG** fluctuates. Here, at the time marked **1**, the Deviation bars are well above the BGI line: BG rises more than insulin activity alone explains (for example after carbs). At the time marked **2**, the Deviation bars are below zero (red): BG is lower than the algorithm expected. ### Section F - QuickLaunch toolbar @@ -486,13 +486,13 @@ To give a certain amount of insulin without using the [bolus calculator](#aaps-s By enabling **Start Eating soon TT**, you can automatically start your [eating soon temp target](#TempTargets-eating-soon-temp-target). -If you do not want to bolus through the pump but record an insulin amount (i.e. insulin given by pen) enable "**Bolus will be recorded only**". An additional **Time** row, set to **Now**, lets you record an insulin injection made in the past: use **-** / **+** to change it, or tap the chevron to type the minutes or pick a date and time. +If you do not want to bolus through the pump but record an insulin amount (i.e. insulin given by pen) enable "**Bolus will be recorded only (not delivered by pump)**". An additional **Time** row, set to **Now**, lets you record an insulin injection made in the past: use **-** / **+** to change it, or tap the chevron to type the minutes or pick a date and time. ![The Time row, folded](../images/v4/Screens/insulin_dialog_record_only_time.png) ![The Time row, opened with the chevron](../images/v4/Screens/insulin_dialog_time_open.png) You can use the **+0.5 / +1.0 / +2.0** buttons to quickly increase the insulin quantity. The increment values can be changed in the [Bolus wizard settings](#Preferences-deliver-this-part-of-bolus-wizard-result). -The insulin dialog can be used when the pump is suspended or disconnected as well, e.g. to record insulin injected with a pen. In this case, "**Bolus will be recorded only**" is forced on (shown in red) and additional fields appear to select the insulin type and a **Time** offset for an injection made in the past: +The insulin dialog can be used when the pump is suspended or disconnected as well, e.g. to record insulin injected with a pen. In this case, "**Bolus will be recorded only (not delivered by pump)**" is forced on (shown in red) and additional fields appear to select the insulin type and a **Time** offset for an injection made in the past: ![Insulin dialog with pump disconnected](../images/main/insulin_dialog_pump_disconnected.png) @@ -506,7 +506,7 @@ Certain [pre-set temporary targets](#TempTargets-hypo-temp-target) (Hypo, Eating **Carb time**: When will you / have you been eating carbs. -**Duration**: To be used for ["extended carbs"](ExtendedCarbs). This row is folded, so that you do not type the grams into it by mistake: use **-** / **+** to change it, or tap the chevron to open it and type a value. +**Duration**: To be used for ["extended carbs"](ExtendedCarbs.md). This row is folded, so that you do not type the grams into it by mistake: use **-** / **+** to change it, or tap the chevron to open it and type a value. You can use the **+5 / +10 / +20** buttons to quickly increase the carb amount. @@ -606,7 +606,7 @@ The result button at the bottom shows the proposed bolus; pressing it asks for c Good to know: * If the calculated bolus is above your **[Maximum bolus](#Preferences-maximum-bolus)**, it is reduced to the max bolus, and the confirmation shows the warning "Bolus constraint applied". A [QuickWizard](../DailyLifeWithAaps/QuickWizards.md) is refused instead. -* When the bolus is only recorded (for example while the pump is disconnected), the "**Bolus will be recorded only**" warning stays at the top of the dialog, also when you scroll. +* When the bolus is only recorded (for example while the pump is disconnected), the "**Bolus will be recorded only (not delivered by pump)**" warning stays at the top of the dialog, also when you scroll. * A bolus you give by hand has priority over an [SMB](#Open-APS-features-super-micro-bolus-smb) that is waiting to be delivered: the SMB is dropped and the loop calculates again. If an SMB is being delivered right now, your bolus is refused with the message "An SMB is being delivered right now. Try again when it has finished." No insulin is given, and carbs entered with that bolus are not saved: wait a moment and enter them again. (AapsScreens-wrong-cob-detection)= diff --git a/docs/EN/DailyLifeWithAaps/Automations.md b/docs/EN/DailyLifeWithAaps/Automations.md index 073736d3b125..15ca5374973e 100644 --- a/docs/EN/DailyLifeWithAaps/Automations.md +++ b/docs/EN/DailyLifeWithAaps/Automations.md @@ -19,7 +19,7 @@ Automation rules are created and modified from the **Automation** screen (**Mana - One or more actions to perform. - Such as an alarm or settings a profile percentage or exporting the AAPS settings on Pod change. + Such as an alarm or setting a profile percentage or exporting the AAPS settings on Pod change. There are a wide range of Automation options, and users are encouraged to study these within the AAPS app, in the Automation section. @@ -39,11 +39,11 @@ The example below illustrates how an **Automation** can enable steps to be elimi User exercises every morning at 6 am: he needs to remember to manually set a "Temp Target-Activity" in AAPS at 5am, before exercising. -![Alt text](../images/Automations/automation_concept_manual.png) +![Manual actions without automation](../images/Automations/automation_concept_manual.png) The user has set an **Automation** to trigger a 5am ‘Temp Target-Activity’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: -![Alt text](../images/Automations/automation_concept_automated.png) +![Actions done by an automation](../images/Automations/automation_concept_automated.png) ## Key considerations before starting with Automations @@ -92,12 +92,12 @@ To set up an **Automation**, press the **+** button on the Automation screen to To deactivate an **Automation** rule, untick the box left of the name of the **Automation**. The example below shows an **Automation** as either activated (‘ticked') or deactivated (‘unticked’): -![Alt text](../images/Automations/automation_rule_activated_deactivated.png) +![Automation rules switched on and off](../images/Automations/automation_rule_activated_deactivated.png) When setting up an **Automation**, you can first test it by activating the ‘notification’ option under "Actions". This triggers **AAPS** to first display a notification rather than actually automating an action. When you are comfortable that the notification has been triggered at the correct time/conditions, the **Automation** rule can be updated to replace the ‘Notification’ with an ‘Action’. -![Alt text](../images/Automations/automation_alert_actions.png) +![Alert actions](../images/Automations/automation_alert_actions.png) ```{admonition} Important note :class: note @@ -116,7 +116,7 @@ There are safety limits set for **Automations**: * A **Temp Target** set by an **Automation** has to be between 72 and 180 mg/dL (or 4 and 10 mmol/L). * The **Profile Percentage** has to be between 50% and 130%. -* There is a 5 minute time limit between executions of **Automation** (and first execution). +* There is a 5 minute time limit between executions of **Automation** (and first execution). ## Correct use of negative values @@ -128,7 +128,7 @@ Please be careful when selecting a negative value in **Automation** Caution must be taken when selecting a ‘negative value’ within the ‘Condition’ like "less than" in **Automations**. For example: -![Alt text](../images/Automations/automation_comparison_operators.png) +![Comparison operators](../images/Automations/automation_comparison_operators.png) **Example 1:** Creating a Condition **"is lesser than"** "-0.1mmol/L" (or "-2mg/dL") will: @@ -243,7 +243,7 @@ none ![The events of the Note action](../images/Automations/automation_action_careportal_events.png) ![The Note action set to Pump Site Change](../images/Automations/automation_action_careportal_site_change.png) -**Actions:** **Send SMS** (in the **Alerts** group) +**Actions:** **Send SMS to all numbers** (in the **Alerts** group) **Options:** @@ -261,7 +261,7 @@ none * choose **On** or **Off**. This changes the **Enable SMB** setting of OpenAPS SMB, exactly as if you had changed it in **Settings**, and stays until you or another rule change it back. -**Actions:** **Autotune profile** (in the **Loop & insulin** group) +**Actions:** **Run Autotune** (in the **Loop & insulin** group) **Options:** @@ -281,39 +281,39 @@ none Once the ‘Action’ is added, the default values must be changed to the desired number by clicking and adjusting the default values. -![Alt text](../images/Automations/automation_action_temp_target_values.png) +![Temp target action values](../images/Automations/automation_action_temp_target_values.png) (Automations-the-order-of-the-automations-in-the-list-matters)= ## The order of the **Automations** in the list matters - **AAPS** will automate the rules created in the order of preference, starting from the top of the **Automation** list. For example, if the ‘Low’ **Automation** is the most important **Automation**, above all other rules, then this **Automation** should appear at the top of the user’s **Automation** list as demonstrated below: + **AAPS** will automate the rules created in the order of preference, starting from the top of the **Automation** list. For example, if the ‘Low’ **Automation** is the most important **Automation**, above all other rules, then this **Automation** should appear at the top of the user’s **Automation** list as demonstrated below: -![Alt text](../images/Automations/automation_rule_list.png) +![List of automation rules](../images/Automations/automation_rule_list.png) -To reprioritize the **Automation** rules, touch and hold the **=** handle on the right side of the rule. Reorder the **Automations** by moving the rules up or down. +To reprioritize the **Automation** rules, touch and hold the **=** handle on the right side of the rule. Reorder the **Automations** by moving the rules up or down. -![Alt text](../images/Automations/automation_rule_reorder.png) +![Reorder automation rules](../images/Automations/automation_rule_reorder.png) ## How to delete Automation rules To delete an **Automation** rule click on the trash icon. -![Alt text](../images/Automations/automation_rule_delete.png) +![Delete automation rules](../images/Automations/automation_rule_delete.png) ## Examples of Automations -Below are examples of **Automations**. Further discussion on **Automations** and how users have individualised their **Automation** can be found in Facebook discussions groups or on Discord. The examples below should not be replicated without the user having a good understanding of how the **Automation** will work. +Below are examples of **Automations**. Further discussion on **Automations** and how users have individualised their **Automation** can be found in Facebook discussions groups or on Discord. The examples below should not be replicated without the user having a good understanding of how the **Automation** will work. (automations-low-glucose-temp-target)= ### Low Glucose Temp Target This **Automation** triggers an automatic **Temp Target** when **BG** falls below a certain threshold — here, when glucose is lesser than 70 mg/dL, a target of 110 mg/dL is started for 30 minutes: -![Alt text](../images/Automations/automation_example_low_glucose_rule.png) +![Example: low glucose rule](../images/Automations/automation_example_low_glucose_rule.png) ### Lunch Time Temp Target (with ‘Location’) -![Alt text](../images/Automations/automation_example_lunch_rule.png) +![Example: lunch rule](../images/Automations/automation_example_lunch_rule.png) This **Automation** has been created for a user who eats their lunch at work around the same time every weekday but triggered only if the user is situated within a set ‘location’. So if the user is not at work one day, this **Automation** will not activate. @@ -321,7 +321,7 @@ This **Automation** will set a low **Temp Target** (Eating Soon) at 13:00 to dri The ‘Trigger’ location has a name, a position (tap **Pick from map**, or use your current location) and a radius in metres, and fires when you are inside (or outside) the area: -![Alt text](../images/Automations/automation_example_lunch_location_condition.png) +![Example: lunch rule with location condition](../images/Automations/automation_example_lunch_location_condition.png) Because of the ‘And’ connection, the **Automation** only happens during the ‘chosen time’ and if the user is at the selected location. @@ -331,10 +331,10 @@ The **Automation** will not be triggered on any other time at this location or a Using a Wi-Fi SSID is a good option to trigger an **Automation** while within range of a specific Wi-Fi network (compared with GPS): it is fairly precise, uses less battery, and works in enclosed spaces where GPS and other location services might not be available. -Here is another example of setting up a **Temp Target** for work days only before breakfast(1). +Here is another example of setting up a **Temp Target** for work days only before breakfast (1). -The **Automation** will trigger at 05:30am only on Monday-Friday(2) +The **Automation** will trigger at 05:30am only on Monday-Friday (2) and while being connected to a home Wi-Fi network (3). @@ -353,7 +353,7 @@ Here is the screenshot detailing the **Automation** triggers: 1) Recurring time = M,T,W,T,F At 5:30am 1) Wi-Fi SSID = My_Home_WiFi_Name -![Alt text](../images/Automations/automation_example_wifi_condition.png) +![Example: WiFi condition](../images/Automations/automation_example_wifi_condition.png) (automating-preference-settings-export)= @@ -401,7 +401,7 @@ In the example below, the **Low glucose temp target** rule (1) (see [Low Glucose Check that the box left of the **Automation** name is ‘ticked’ to ensure the rule is activated: -![Alt text](../images/Automations/automation_rule_activated_deactivated.png) +![Automation rules switched on and off](../images/Automations/automation_rule_activated_deactivated.png) * Problem: __My automations are being triggered in the wrong order.__ diff --git a/docs/EN/DailyLifeWithAaps/CobCalculation.md b/docs/EN/DailyLifeWithAaps/CobCalculation.md index 9749e1ffc221..f7783cf000d6 100644 --- a/docs/EN/DailyLifeWithAaps/CobCalculation.md +++ b/docs/EN/DailyLifeWithAaps/CobCalculation.md @@ -12,13 +12,13 @@ The formula adopted by **AAPS** is: The effect on the user’s **Profile** will: -- _increase_ **IC**- by increasing the carbs absorbed every 5 minutes thus shorten total time of absorption; +- _increase_ **IC** - by increasing the carbs absorbed every 5 minutes thus shorten total time of absorption; - _increase_ **ISF** - by decreasing the carbs absorbed every 5 minutes thus prolong total time of absorption; and -- _change_ **Profile Percentage** - increase/decrease both values thus has no impact on carbs absorption time. +- _change_ **Profile Percentage** - increase/decrease both values thus has no impact on carbs absorption time. -For example, if the user’s **Profile** **ISF** is 100 and the **I:C** is 5, the user’s Carb Sensitivity Factor would be 20. For every 20 mg/dL the user’s **BG** goes up, 1 g of carbs will be calculated as absorbed by **AAPS**. Positive **IOB** also affects the **COB** calculation. So, if **AAPS** predicts the user’s **BG** to go down by 20 mg/dL because of **IOB** and it instead stayed flat, **AAPS** would also calculate 1 g of carbs as absorbed. +For example, if the user’s **Profile** **ISF** is 100 and the **I:C** is 5, the user’s Carb Sensitivity Factor would be 20. For every 20 mg/dL the user’s **BG** goes up, 1 g of carbs will be calculated as absorbed by **AAPS**. Positive **IOB** also affects the **COB** calculation. So, if **AAPS** predicts the user’s **BG** to go down by 20 mg/dL because of **IOB** and it instead stayed flat, **AAPS** would also calculate 1 g of carbs as absorbed. Carbs will also be absorbed via the methods described below based on which sensitivity algorithm has been selected within the user's **AAPS**. @@ -47,7 +47,7 @@ If minimal carbs absorption (min_5m_carbimpact) is used instead of value calcula (CobCalculation-detection-of-wrong-cob-values)= ## Detection of wrong COB values -**AAPS** will warn the user if they are about to bolus with **COB** from a previous meal if the algorithm detects current **COB** calculation as incorrect. In this case it will give the user an additional hint on the confirmation screen after usage of bolus wizard. +**AAPS** will warn the user if they are about to bolus with **COB** from a previous meal if the algorithm detects current **COB** calculation as incorrect. In this case it will give the user an additional hint on the confirmation screen after usage of bolus wizard. ### How does AAPS detect wrong COB values? @@ -62,7 +62,7 @@ In the screenshot above, 66% of time the carb absorption was calculated by the m - Consider cancelling the treatment - press ‘Cancel’ instead of OK. - Calculate your upcoming meal again with bolus wizard leaving **COB** unticked. - If you need a correction bolus, enter it manually. -- Be careful not to overdose or insulin stacking! +- Be careful not to overdose or stack insulin! ### Why does the algorithm not detect COB correctly? diff --git a/docs/EN/DailyLifeWithAaps/DynamicISF.md b/docs/EN/DailyLifeWithAaps/DynamicISF.md index a134405b4343..dbd0a40bfc74 100644 --- a/docs/EN/DailyLifeWithAaps/DynamicISF.md +++ b/docs/EN/DailyLifeWithAaps/DynamicISF.md @@ -16,14 +16,14 @@ When using **Dynamic ISF**, disable any temporary **Profile** change as an **Aut To use **Dynamic ISF**, **AAPS'** database requires a minimum of 7 days of the user's **AAPS** data. -## What does Dynamic ISF do ? +## What does Dynamic ISF do? **Dynamic ISF** adapts the insulin sensitivity factor (**ISF**) dynamically based on the user's: - Total Daily Dose of insulin (**TDD**); and - current and predicted blood glucose values. -When using **Dynamic ISF**, the **ISF** values entered in the **Profile** are not used at all anymore, except as a fallback if there is not enough TDD data in **AAPS** database (*i.e.* fresh reinstallation of the app). +When using **Dynamic ISF**, the **ISF** values entered in the **Profile** are not used at all anymore, except as a fallback if there is not enough TDD data in **AAPS** database (*i.e.* fresh reinstallation of the app). **SMB/AMA** - an example of a user's **Profile** with static **ISF** as set by the user and utilised by **SMB** and **AMA**. @@ -38,7 +38,7 @@ Tapping on this section shows a dialog with additional information, such as the The **DynISF** value can also be shown in a graph: tap **Add graph** below the graphs on the main screen and select **VSENS** (variable sensitivity). It shows as a white line (bottom of the image above). -## How is Dynamic ISF calculated ? +## How is Dynamic ISF calculated? **Dynamic ISF** uses Chris Wilson’s model to determine **ISF** instead of the user's static **ISF** value as set within the **Profile**. A detailed explanation can be found here: [Chris Wilson on Insulin Sensitivity (Correction Factor) with Loop and Learn, 2/6/2022](https://www.youtube.com/watch?v=oL49FhOts3c). @@ -73,9 +73,9 @@ This is done to prevent dosing too much insulin when **BG** is low or predicted **Future ISF** uses the same formula as described above, except that it may use **minimum predicted BG** instead of **current BG**. **Minimum predicted BG**, [as calculated in oref1](#aaps-screens-how-predictions-become-a-dosing-decision), is the minimum value your BG is predicted to go during all the course of the predictions. -* If the current **BG** is above target
+* If the current **BG** is above target
**and** if **BG** levels are flat, within +/- 3 mg/dL:
BG is used in the formula as follows: `average(minimum predicted BG, current BG)`. -* If eventual **BG** is above target and glucose levels are increasing,
+* If eventual **BG** is above target and glucose levels are increasing,
**or** eventual **BG** is above current **BG**:
BG is used in the formula as follows: `current BG`. * Otherwise:
BG is used in the formula as follows: `minimum predicted BG`. @@ -116,7 +116,7 @@ The **Adjustment Factor** is a value between 1% and 300%. This acts as a multipl The **Adjustment Factor** is also altered when activating a [**Profile Switch** with percentage](../DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md). A lower **Profile Percentage** will lower the **Adjustment Factor**, and vice versa in respect of higher **Profile Percentage**. -For example, if your **Adjustment Factor** is 80%, and **Profile Switch** to 80% is actioned , the resulting **Adjustment Factor** will be `0.8*0.8=0.64`. +For example, if your **Adjustment Factor** is 80%, and **Profile Switch** to 80% is actioned, the resulting **Adjustment Factor** will be `0.8*0.8=0.64`. This means that, when using **DynISF**, you can use **Profile Percentage** to temporarily fine tune your sensitivity manually. This can be useful for physical activity (lower percentage), illness (higher percentage), etc. diff --git a/docs/EN/DailyLifeWithAaps/ExtendedCarbs.md b/docs/EN/DailyLifeWithAaps/ExtendedCarbs.md index fafa785c8186..c841c86552c3 100644 --- a/docs/EN/DailyLifeWithAaps/ExtendedCarbs.md +++ b/docs/EN/DailyLifeWithAaps/ExtendedCarbs.md @@ -26,7 +26,7 @@ The eCarbs on the main screen: the number in brackets in the **COB** field shows In the [Bolus wizard](#aaps-screens-bolus-wizard), three buttons below the **Carbs** field let you choose how fast your meal is absorbed. Pick one before you confirm. Depending on the type, **AAPS** takes a part of the carbs you typed as normal carbs, and adds [extended carbs ("eCarbs")](#Extended-Carbs-extended-carbs-ecarbs) later for slow, rich meals. Press the **(i)** icon next to the buttons to see the typical foods for the selected type and what it does to your carbs. -| Type | Typical foods (as listed in the app) | Carbs now, used for the bolus | eCarbs added | +| Type | Typical foods (examples from the app) | Carbs now, used for the bolus | eCarbs added | |---|---|---|---| | **Bread** (default) | Bread, savory pastries, yogurt, fruit, potatoes, rice, oatmeal, vegetables | 100 % | None | | **Cake** | Dumplings, pasta, Asian dishes rich in carbs and fats, sweet and yeast pastries, cereals, honey, jam | 90 % | 20 %, starting 60 minutes later, spread over 2 hours | @@ -61,7 +61,7 @@ For a quicker start, the *Bolus wizard* can add eCarbs for you: choose the [carb With low carb, high fat/protein meals it may be enough to only use eCarbs without manual boluses (see the blog post above). When eCarbs are generated, a Careportal note is also created to document all inputs, to make it easier to iterate and improve inputs. (extended-bolus-and-why-they-wont-work-in-closed-loop-environment)= -## Extended bolus and why they won't work in closed-loop environment? +## Extended boluses and why they don't work in a closed-loop environment As mentioned above extended or multiwave boluses do not really work in a closed loop environment. [See below](#why-extended-boluses-won-t-work-in-a-closed-loop-environment) for details diff --git a/docs/EN/DailyLifeWithAaps/GlobalSearch.md b/docs/EN/DailyLifeWithAaps/GlobalSearch.md index 1f693eddbf32..793f7aa00e85 100644 --- a/docs/EN/DailyLifeWithAaps/GlobalSearch.md +++ b/docs/EN/DailyLifeWithAaps/GlobalSearch.md @@ -73,7 +73,7 @@ Tap a result to go straight to it: - **Preference** → opens the setting **in place** (jumps to it within its screen). - **Documentation** → opens the page in your browser. -Opening settings and protected actions still respects your **[protection](../SettingUpAaps/ConfigBuilder.md)** (PIN/password), exactly as it would if you had navigated there by hand. After you act on a result you can press **Back** to return to your search results. +Opening settings and protected actions still respects your **[protection](#Preferences-protection)** (PIN/password), exactly as it would if you had navigated there by hand. After you act on a result you can press **Back** to return to your search results. --- diff --git a/docs/EN/DailyLifeWithAaps/KeyAapsFeatures.md b/docs/EN/DailyLifeWithAaps/KeyAapsFeatures.md index f2e59ef95697..62109464c79f 100644 --- a/docs/EN/DailyLifeWithAaps/KeyAapsFeatures.md +++ b/docs/EN/DailyLifeWithAaps/KeyAapsFeatures.md @@ -116,7 +116,7 @@ For example, if the highest basal rate in your profile was 0.5 U/h you could mul *See also [overview of hard-coded limits](#Open-APS-features-overview-of-hard-coded-limits).* (Open-APS-features-maximum-total-iob-openaps-cant-go-over)= -### Maximum total IOB OpenAPS can’t go over +### Max IOB for SMB This value determines the maximum **Insulin on Board** (basal and bolus IOB) that **AAPS** will remain under while running in closed loop mode. It is also known as **maxIOB**. @@ -211,7 +211,7 @@ This setting is not visible if "Enable SMB always" is switched on. #### SMB interval This feature limits the frequency of SMBs. This value determines the minimum time between SMBs. -Note that the loop runs every time a glucose value comes in (generally 5 minutes). Subtract 2 minute to give loop additional time to complete. E.g. if you want SMB to be given every loop run, set this to 3 minutes. +Note that the loop runs every time a glucose value comes in (generally 5 minutes). Subtract 2 minutes to give loop additional time to complete. E.g. if you want SMB to be given every loop run, set this to 3 minutes. Default value: 3 min. @@ -231,7 +231,7 @@ This setting allows you to adjust the strength of SMB during UAM, when there are Default value : the same as **Max minutes of basal to limit SMB**. -This setting is only visible if "Enable SMB" and "Enable UAM " are switched on. +This setting is only visible if "Enable SMB" and "Enable UAM" are switched on. (enable-uam)= ### Enable UAM @@ -255,7 +255,7 @@ In any case, the required carbs will be displayed in the COB section on your mai For the full parameter reference (including settings not covered here), see [OpenAPS's preferences and safety settings documentation](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/preferences-and-safety-settings.html). -**Always use short average delta instead of simple data** If you enable this feature, **AAPS** uses the short average delta/blood glucose from the last 15 minutes, which is usually the average of the last three values. This helps **AAPS** to be steadier with noisy data sources like xDrip and Libre. +**Always use short average delta instead of simple delta** If you enable this feature, **AAPS** uses the short average delta/blood glucose from the last 15 minutes, which is usually the average of the last three values. This helps **AAPS** to be steadier with noisy data sources like xDrip and Libre. **Max daily safety multiplier** This is an important safety limit. The default setting (which is unlikely to need adjusting) is 3. This means that **AAPS** will never be allowed to set a temporary basal rate that is more than 3x the highest hourly basal rate programmed in a user’s pump and/or profile. Example: if your highest basal rate is 1.0 U/h and max daily safety multiplier is 3, then **AAPS** can set a maximum temporary basal rate of 3.0 U/h (= 3 x 1.0 U/h). @@ -285,7 +285,7 @@ After selecting it, its **Settings** contain the OpenAPS SMB settings plus an ** - while glucose is **above target**, ISF is strengthened; - a **post-prandial** weight and a **duration** weight act after meals and when glucose stays high for a long time. - **SMB delivery ratio** (with a minimum, a maximum and a BG range): what share of the insulin required can be delivered as SMB. -- **SMB max range extension**: by what factor the usual SMB size limit ([max minutes of basal](#Open-APS-features-max-minutes-of-basal-to-limit-smb-to), normally 120 minutes) may be exceeded. The default value 1 changes nothing; up to 5 is possible. Increase this experimental value slowly and with caution. +- **SMB max range extension**: by what factor the usual SMB size limit ([max minutes of basal](#Open-APS-features-max-minutes-of-basal-to-limit-smb-to), 30 minutes by default) may be exceeded. The default value 1 changes nothing; up to 5 is possible. Increase this experimental value slowly and with caution. - **IOB threshold percent**: the percentage of max IOB above which SMBs are disabled. ```{admonition} Only for experienced users @@ -314,10 +314,10 @@ The hardcoded parameters in **AAPS** are: *See also [overview of hard-coded limits](#Open-APS-features-overview-of-hard-coded-limits).* -### Maximum basal IOB OpenAPS can deliver [U] (OpenAPS "max-iob") -This parameter limits the maximum of basal IOB where **AAPS** still works. If the IOB is higher, it stops giving additional basal insulin until the basal IOB is under the limit. +### Max IOB for AMA +This parameter limits the maximum of basal IOB where **AAPS** still works. If the IOB is higher, it stops giving additional basal insulin until the basal IOB is under the limit. -The default value is 2, but you should rise this parameter slowly to see how much it affects you and which value fits best. It is different for anyone and also depends on the average total daily dose (TDD). For safety reason, there is a limit, which depends on the patient age . The 'hard limit' for maxIOB is lower in AMA than in SMB. +The default value is 2, but you should raise this parameter slowly to see how much it affects you and which value fits best. It is different for everyone and also depends on the average total daily dose (TDD). For safety reason, there is a limit, which depends on the patient age. The 'hard limit' for maxIOB is lower in AMA than in SMB. * Child: 3 * Teenager: 5 @@ -338,7 +338,7 @@ If you have this option enabled, autosens can adjust targets (next to basal and - Normally you do not have to change the settings in this dialog! - If you want to change them anyway, make sure you understand what you are doing — see the full parameter reference in [OpenAPS's preferences and safety settings documentation](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/preferences-and-safety-settings.html). -**Always use short average delta instead of simple data** If you enable this feature, **AAPS** uses the short average delta/blood glucose from the last 15 minutes, which is usually the average of the last three values. This helps **AAPS** to work more steady with noisy data sources like xDrip and Libre. +**Always use short average delta instead of simple delta** If you enable this feature, **AAPS** uses the short average delta/blood glucose from the last 15 minutes, which is usually the average of the last three values. This helps **AAPS** to work more steady with noisy data sources like xDrip and Libre. **Max daily safety multiplier** This is an important safety limit. The default setting (which is unlikely to need adjusting) is 3. This means that **AAPS** will never be allowed to set a temporary basal rate that is more than 3x the highest hourly basal rate programmed in a user’s pump. Example: if your highest basal rate is 1.0 U/h and max daily safety multiplier is 3, then **AAPS** can set a maximum temporary basal rate of 3.0 U/h (= 3 x 1.0 U/h). diff --git a/docs/EN/DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md b/docs/EN/DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md index b5a80c46c8f8..22ee12b7d100 100644 --- a/docs/EN/DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md +++ b/docs/EN/DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md @@ -10,7 +10,7 @@ When first embarking on your **AAPS** journey, you will need to create a **Profi - Night or pattern shift workers - a time shift in **Profile** can be set up for pattern shift workers by altering the number of hours in the **Profile** to how much later/earlier the user will go to bed or wake up. -Why use a **Profile Percentage** rather than a temporary basal adjustment? To be more effective in its application a **Profile Percentage** applies a proportionate reduction or increase across: basal, ISF and I:C. This ensures a balanced approach is calculated by **AAPS** when administering the user’s insulin intake. Little benefit can be gained in a user’s **Profile** in **AAPS** by a basal reduction if the algorithm continues to deliver the same ratios for ISF and I:C. +Why use a **Profile Percentage** rather than a temporary basal adjustment? To be more effective in its application a **Profile Percentage** applies a proportionate reduction or increase across: basal, ISF and I:C. This ensures a balanced approach is calculated by **AAPS** when administering the user’s insulin intake. Little benefit can be gained in a user’s **Profile** in **AAPS** by a basal reduction if the algorithm continues to deliver the same ratios for ISF and I:C. (ProfileSwitch-change-percentage)= ## Change the Profile Percentage from the main screen @@ -80,7 +80,7 @@ Select a profile and tap **▶ Activate**. The **Activate** screen lets you tail ![The Activate screen — percentage, duration, time shift, time](../images/v4/Profiles/profile_activate.png) -- **Percentage** (30–250 %, starts at 100 % every time) — scale the whole profile. 100 % uses it as-is; for example 70 % reduces basal and the calculated insulin dose (both meal boluses and corrections) by 30 %. It does not change your glucose targets or carb absorption. See [Profile Percentage](#profile-percentage) for the full effect. +- **Percentage** (30–250 %, starts at 100 % every time) — scale the whole profile. 100 % uses it as-is; for example 70 % reduces basal and the calculated insulin dose (both meal boluses and corrections) by 30 %. It does not change your glucose targets or carb absorption. See [Profile Percentage](#ProfileSwitch-profile-percentage) for the full effect. - **Duration** (0–10080 minutes, that is up to 7 days) — how long the switch lasts. **0 = indefinite** (until you switch again); a non-zero value reverts to the previous profile when it ends. - **Temporary target / Activity** — appears only when you set a **Duration** and a **Percentage** below 100 %. Switch it on to also start an [Activity temp target](#TempTargets-activity-temp-target) for the same duration, as you would before exercise. - **Time shift** — shows *0h*; tap **Change** to move the schedule forward or back by up to 23 hours (useful for shift work or travel). See [Time shift](#ProfileSwitch-ProfilePercentage-time-shift-of-the-circadian-percentage-profile). @@ -112,6 +112,7 @@ Rather than building many similar profiles, keep one base profile and apply it a A profile switch is not limited to this screen. The same switch can also be triggered from a **Wear OS watch**, a paired **client** (see [Master ↔ Client control](../RemoteFeatures/ClientMasterControl.md)), a **[scene](Scenes.md)**, or an **Automation** rule. +(ProfileSwitch-profile-percentage)= ## Profile Percentage It is important that a user understands the essential features of a **Profile Percentage**. By applying a percentage increase or decrease to a **Profile Switch** this will apply in the same percentage to either raise or lower the user’s settings parameters as set within the **Profile**. @@ -127,7 +128,7 @@ Once selected, **AAPS** readjusts the default basal rate, and **AAPS** (open or The effect of a **Profile** Percentage is summarized in the table below: -| Profile Switch
Percentage | Effect | I:C
g/U | example
15g | ISF
mmol/L/U
mg/dL/U | U to lower
2mmol/L
40mg/dL | +| Profile Switch
Percentage | Effect | I:C
g/U | Example
15 g | ISF
mmol/L/U
mg/dL/U | U to lower
2mmol/L
40mg/dL | | :--------------------------: | :----------: | :----------------: | :------------: | :--------------------------------------------: | :---------------------------------: | | 90% | Weaker | 5/0.9
=**5.55** | 2.7 U | 2.2/0.9
=**2.4**

40/0.9
=**44.4** | 0.8 U | | **100%** | **Standard** | **5** | **3 U** | **2.2
40** | **0.9** U | @@ -138,7 +139,7 @@ The effect of a **Profile** Percentage is summarized in the table below: A ‘time shift’ within a user’s **Profile** feature will move the user’s **Profile’s** settings around the day-to-day clock (‘circadian’) to the desired number of hours entered. This can be helpful for: -- __night shift or pattern workers__: work night shifts by altering the number of hours to how much later/earlier in the **Profile** the user will go to bed or wake up; +- __night shift or pattern workers__: work night shifts by altering the number of hours to how much later/earlier in the **Profile** the user will go to bed or wake up; - __users changing time zones during travelling__; or - __users who are type 1 children__: and have a set bedtime routine and insulin resistance catered for within their **Profile**. If for whatever reason, there is a predicted later bedtime for the child, the caregiver can apply a ‘time shift’ to the child’s **Profile** to allow **AAPS** to react to insulin resistance at a desired time period as set by the user. @@ -153,7 +154,7 @@ It is always a question of which hour’s **Profile’s** settings should replac ![Profile switch timeshift directions](../images/ProfileSwitch_PlusMinus2.png) -This mechanism of taking snapshots of the **Profile** allows a much more precise calculation of the past and the possibility to track **Profile** changes. +This mechanism of taking snapshots of the **Profile** allows a much more precise calculation of the past and the possibility to track **Profile** changes. (ProfileSwitch-keep-for-later)= ## Keep a profile switch for later use diff --git a/docs/EN/DailyLifeWithAaps/PumpsAndCannulas.md b/docs/EN/DailyLifeWithAaps/PumpsAndCannulas.md index 69e646f7ae0a..aa869ba53b7b 100644 --- a/docs/EN/DailyLifeWithAaps/PumpsAndCannulas.md +++ b/docs/EN/DailyLifeWithAaps/PumpsAndCannulas.md @@ -57,7 +57,7 @@ As you are not getting any insulin while the pump is disconnected, you should re (pumps-cannulas-announce-insulin)= ## To announce delivered insulin without actually bolusing -To announce insulin delivered from the pump either while **AAPS** was disconnected, or from pen injections: open the [Insulin dialog](#aaps-screens-buttons-insulin) (**Treatments** in the bottom navigation, or a QuickLaunch button), enter the amount in units and enable **Bolus will be recorded only**. A **Time** row (set to **Now**) then lets you record the actual time of the injection: you can ignore it if the injection was given recently. If the bolus was given some time ago, use **-** to move the time back (_e.g._ -30 min), or open the row with the chevron to pick the exact date and time. **AAPS** will then take into account the duration of insulin action and calculate the remaining insulin still in the system accordingly. +To announce insulin delivered from the pump either while **AAPS** was disconnected, or from pen injections: open the [Insulin dialog](#aaps-screens-buttons-insulin) (**Treatments** in the bottom navigation, or a QuickLaunch button), enter the amount in units and enable **Bolus will be recorded only (not delivered by pump)**. A **Time** row (set to **Now**) then lets you record the actual time of the injection: you can ignore it if the injection was given recently. If the bolus was given some time ago, use **-** to move the time back (_e.g._ -30 min), or open the row with the chevron to pick the exact date and time. **AAPS** will then take into account the duration of insulin action and calculate the remaining insulin still in the system accordingly. If you are using **AAPS** as a caregiver, you can remotely disconnect (and reconnect) the pump very easily by [SMS command](../RemoteFeatures/SMSCommands.md) using commands such as "pump disconnect 120" and "pump connect 120". The range of duration for remote disconnect is from 1 - 120 min, (in this example it is 120 minutes). This is very useful if the **AAPS** handset is inconvenient for you to access, buried in a pump belt on a kid who is running off towards the swimming complex, or being closely guarded (or in use) by a teenager. @@ -92,7 +92,7 @@ Which strategy you prefer is highly personal, and is best determined by trial an ![User profile for site rotation dialog](../images/SiteRotation/Type.png) -*Note: this setting will be used to automatically open or not Site Rotation Dialog (Edit mode) when a new entry is done from "Prime/Fill button" or "CGM Sensor Insert button"* +*Note: this setting decides whether the Site Rotation dialog (Edit mode) opens automatically when a new entry is made with the "Prime/Fill" button or the "Sensor Insert" button.* - For Site change done directly from Pump, you have to open the View Mode and Edit the new entry to select Location and Arrow @@ -100,7 +100,7 @@ Edit Mode allows you to select Location, Arrow, and Note associated to selected - The entry being edited is shown below the body images, with its type icon (cannula or sensor) - Front and back views are shown side by side: tap the area where you placed it -- Once a Site selected (highlighted in green), you will see in the list below the list of all entries done in the past 45 days in this site +- Once a site is selected (highlighted in green), the list below shows all entries made in this site in the past 45 days. ![Edit Mode](../images/SiteRotation/EditMode.png) diff --git a/docs/EN/DailyLifeWithAaps/TempTargets.md b/docs/EN/DailyLifeWithAaps/TempTargets.md index 22cca478a872..c5ed53000e5d 100644 --- a/docs/EN/DailyLifeWithAaps/TempTargets.md +++ b/docs/EN/DailyLifeWithAaps/TempTargets.md @@ -19,7 +19,7 @@ Users should have realistic expectations on the results that can be achieved whe A **Temp-Target** can take approximately 30 minutes or longer in order to attain a desired **BG** target. It is impossible for **AAPS** to achieve a **BG** target with immediate effect and users should be mindful of this when selecting a **Temp-Target**. -The sections below summarize the features of **Temp-Target- Activity**, **Temp-Target- Eating soon**, and **Temp-Target-Hypo**. The values shown are the shipped defaults — you can [adjust each preset](#TempTargets-change-preset-defaults) to your own needs. +The sections below summarize the features of **Temp-Target Activity**, **Temp-Target Eating soon** and **Temp-Target Hypo**. The values shown are the shipped defaults — you can [adjust each preset](#TempTargets-change-preset-defaults) to your own needs. ### TT - Activity @@ -194,9 +194,9 @@ Sometimes when hypo-treated carbs are eaten, the user's **BG** can rapidly rise, Some users wish to avoid **SMBs** being given during **Temp-Target Hypo**. This is achieved by deactivating _'Enable SMB with high temp target'_ in **Settings** → **OpenAPS SMB** (see further below): -- In (Advanced, objective 9): the user can enable _“High temp target raises sensitivity”_ for **Temp-Targets** of 100 mg/dL (5.6 mmol/L) or higher in OpenAPS SMB, **AAPS** will be more sensitive. +- Advanced, objective 9: the user can enable _“High temp target raises sensitivity”_ for **Temp-Targets** of 100 mg/dL (5.6 mmol/L) or higher in OpenAPS SMB, **AAPS** will be more sensitive. -- In (Advanced, objective 9): the user can deactivate _“Enable SMB with high temp target”_, so that even if **AAPS** has COB > 0, “Enable SMB with low temp target” or “Enable SMB always” enabled and OpenAPS SMB active, **AAPS** will not give SMBs while high temp targets are active. +- Advanced, objective 9: the user can deactivate _“Enable SMB with high temp target”_, so that even if **AAPS** has COB > 0, “Enable SMB with low temp target” or “Enable SMB always” enabled and OpenAPS SMB active, **AAPS** will not give SMBs while high temp targets are active. Note: if you open the **Carbs dialog** while your blood glucose is less than 72 mg/dL or 4 mmol/L, **AAPS** pre-selects the **Start Hypo TT** toggle automatically. @@ -218,9 +218,9 @@ Additionally, if _'Enable SMB with high temp target'_ is deactivated, **AAPS** w (TempTargets-eating-soon-temp-target)= ## Eating soon Temp-Target -**Temp-Target -Eating soon** can help accomplish a gentle drive down of **BG** and ensure there is ample **IOB** before eating. +**Temp-Target Eating soon** can help accomplish a gentle drive down of **BG** and ensure there is ample **IOB** before eating. -This can be an important tool for those users who do not pre bolus, however the efficacy of **Temp-Target -Eating soon** will depend on a number of factors including: the user’s settings, if they eat a low carb diet and whether they are using a fast acting insulin (like Fiasp or Lyumjev) in order to eliminate the need to pre bolus. Ordinarily, until users are experienced in **AAPS** they should expect to pre bolus when using **Temp-Target -Eating soon** and this is particularly so, if eating a high carb diet. +This can be an important tool for those users who do not pre bolus, however the efficacy of **Temp-Target Eating soon** will depend on a number of factors including: the user’s settings, if they eat a low carb diet and whether they are using a fast acting insulin (like Fiasp or Lyumjev) in order to eliminate the need to pre bolus. Ordinarily, until users are experienced in **AAPS** they should expect to pre bolus when using **Temp-Target Eating soon** and this is particularly so, if eating a high carb diet. You can read more about the “Eating soon mode” in the article ['How to do “eating soon” mode'](https://diyps.org/2015/03/26/how-to-do-eating-soon-mode-diyps-lessons-learned/) or [here](https://diyps.org/tag/eating-soon-mode/). diff --git a/docs/EN/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md b/docs/EN/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md index ab57706abffe..9ecf7fec181b 100644 --- a/docs/EN/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md +++ b/docs/EN/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md @@ -76,7 +76,7 @@ The driver automatically adjusts the time of the pump to the time of the phone. Time zone changes keep the history intact, only TDD may be affected. Manually changing the time on the phone can cause problems with the history and **IOB**. If you change time manually double check the **IOB**. -When the time zone or time changes running **TBR's** are stopped. +When the time zone or time changes running **TBRs** are stopped. (time-adjustment-daylight-savings-time-dst)= @@ -113,8 +113,8 @@ If you bolus with **AAPS'** calculator please do not use **COB** and **IOB** dat ### DST for Omnipod Dash -* Either allow **AAPS** to temporarily default background basal after DST has taken place as explained above. -* Otherwise, if you do not want **AAPS** to temporarily default to background basal overnight, you can change the time zone the day prior DST is due to take place to avoid overnight disruption. NOTE THIS OPTION MAY CAUSE YOUR POD TO PREMATURELY EXPIRE. PLEASE HAVE SUPPLIES WITH YOU IF OPTING FOR THE FEATURE BELOW. +* Either allow **AAPS** to temporarily default to background basal after DST has taken place as explained above. +* Otherwise, if you do not want **AAPS** to temporarily default to background basal overnight, you can change the time zone the day before DST is due to take place to avoid overnight disruption. NOTE THIS OPTION MAY CAUSE YOUR POD TO PREMATURELY EXPIRE. PLEASE HAVE SUPPLIES WITH YOU IF OPTING FOR THE FEATURE BELOW. #### Actions to take before the clock change 1. Switch OFF any Phone's settings that automatically sets the Phone's time zone, so the user can change to a desired time zone that does not use DST. How to enable this will depend on your smartphone and Android version. @@ -137,7 +137,7 @@ If you bolus with **AAPS'** calculator please do not use **COB** and **IOB** dat 3. In **AAPS** refresh your pump and switch to your desired **Profile**. -4. Check **AAPS's** **IOB** and **COB** and if this is inaccurate disable the **Loop** for at least one DIA and Max-Carb-Time - whatever is bigger. +4. Check **AAPS's** **IOB** and **COB** and if this is inaccurate disable the **Loop** for at least one DIA or the maximum carb absorption time (**Absorption max time**), whichever is longer. 5. Actions to take after the clock change. A good time to make revert to local time zone is with low **IOB**. E.g. an hour before a meal such as breakfast. Ideally your **COB** and **IOB** should both be close to zero. diff --git a/docs/EN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/EN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md index a8f33c69854c..8ddc4667c415 100644 --- a/docs/EN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md +++ b/docs/EN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md @@ -104,7 +104,7 @@ To have second_hand colored with default BG color (lowRange, midRange or highRan ### TextView settings -TexView have more available parameters compare to ImageView: you can tune rotation (integer value in degrees), textsize (integer value in pixel), gravity (to define if text value will be centered (default value), or aligned left or right), set the font, fontStyle and fontColor, and also background color of the TextView +TextView have more available parameters compare to ImageView: you can tune rotation (integer value in degrees), textsize (integer value in pixel), gravity (to define if text value will be centered (default value), or aligned left or right), set the font, fontStyle and fontColor, and also background color of the TextView ```text "basalRate": { @@ -198,7 +198,7 @@ Default watchface is very simple and zip file will contains only the 2 files: ### Organize your files within your computer -The easiest way to work is to have phone connected to the computer, and work with to specific folders: +The easiest way to work is to have phone connected to the computer, and work with two specific folders: - one explorer opened on a specific folder that will have all files (json, bitmap images, vector images, fonts), and the CustomWatchface.zip file within it - another explorer (or navigation tree tuned) opened to have Phone/AAPS/exports folder available @@ -221,7 +221,7 @@ Then you will have to define which information you want to show so which view sh Now you can start to modify json file with the `"visibility":` key of each view set to `"visible"` or `"gone"` (if you want to keep or not the view) -You can also start to tune approximativaly top, left margin and width height values to start organizing the watchface (these values will be tuned later using image editor) +You can also start to tune approximately top, left margin and width height values to start organizing the watchface (these values will be tuned later using image editor) Note: everything is design within a **400px x 400px rectangle**. So everything will be position in absolute coordinates within this size. @@ -538,7 +538,7 @@ Then we will use a series of images, starting from `"image1":` to `"image8":`. T **freetext2 to freetext4** -For these views will will combine dynamic images and rotation feature explained before: +For these views we will combine dynamic images and rotation feature explained before: ```text "freetext2": { @@ -693,7 +693,7 @@ To illustrate DynPref feature, we will use two example: #### Simple usage of dynPref within Steampunk watchface -Within Steampunk, we have to set of images according to units: `background` image that will have BG scale and will turn according to BG value. and `freeText1` that contains dynamic scale according to avgDelta value.To be able to have one watchface that will automatically show correct units, we should select image according to unit selected. +Within Steampunk, we have two sets of images according to units: `background` image that will have BG scale and will turn according to BG value. and `freeText1` that contains dynamic scale according to avgDelta value.To be able to have one watchface that will automatically show correct units, we should select image according to unit selected. To do that we will replace `dynData` key by a `dynPref`key within view block: @@ -895,7 +895,7 @@ You will see within default view settings the text size (19 on `iob1` and 24 on ``` You can see here that according to detailed iob parameter (`"key_show_detailed_iob"` key), when it's "true" then textsize is defined to a fix value bigger than default (24 instead of 19): this is done using textsize "step" feature, within only one value so one step... (note that for all parameter others than images,if invalidTextSize is not set, then textsize1 will be used for invalid data) -Then "dark" dynPref block will be used to set colorand fontColor +Then "dark" dynPref block will be used to set color and fontColor In this example the dynData block that will be used for iob1 view will be if detailed IOB is enabled and dark enabled: @@ -907,7 +907,7 @@ In this example the dynData block that will be used for iob1 view will be if det }, ``` -So the text will be inwhite on black background and the size 24 will replace default size of 19 set into the view +So the text will be in white on black background and the size 24 will replace default size of 19 set into the view The dynData block that will be used for the same view iob1 if detailed IOB is disabled and dark disabled will be: @@ -924,7 +924,7 @@ Now the text will be in black on white background with a size of 19 - You can combine as many pref than you want, but be careful, the number of blocks to describe can increase very fast (it's exponential): if you chain 3 parameters and you want to define all situations, you will have 8 blocks to describe, if each parameter has only 2 values... - Be careful to not build "infinite loop" (for example if dynpref1 block should be completed by dynpref2 block that should be completed by dynpref1 block...). In this case the dynpref blocks will be considered as invalid... -- Do not forget to include the numéric index after the key (when you use for example `"textsize"`key within a view, you will have to use `"textsize1"`within the dynPref value block, because it's a "dynData" format, so linked to value with a single step in this case) +- Do not forget to include the numeric index after the key (when you use for example `"textsize"`key within a view, you will have to use `"textsize1"`within the dynPref value block, because it's a "dynData" format, so linked to value with a single step in this case) - Only one key `"valueKey"` should be set for one view, so if the final `dynData` block is built from several `dynPref`blocks, do not include several `"valueKey"` (and associated `"minData"`, `"maxData"`, ...) (cwf-reference-new-v2-features)= @@ -933,7 +933,7 @@ Now the text will be in black on white background with a size of 19 Note that the watchfaces using these new features or views will require the latest wear apk built from 3.3.0 version of AAPS. -If you use a zip "v2" with a watch that includes CustomWachface V1, you will have missing information or wrong content into the watchface. +If you use a zip "v2" with a watch that includes CustomWatchface V1, you will have missing information or wrong content into the watchface. CustomWatchface V2 includes these new features: @@ -951,7 +951,7 @@ The key of this view is `"status"` and associated block is automatically include This view was included into previous AAPS (NoChart), AAPS (BigChart) and AAPS (Large) previous existing watchfaces available and include a string value (built within wear apk). -These previous watchfaces has been removed and replaced by 3 new custom watchfaces in AAPS 3.3.0. +These previous watchfaces have been removed and replaced by 3 new custom watchfaces in AAPS 3.3.0. - the minimum information is IOB value (always visible whatever IOB parameter into watch) - then you have detailed IOB values (BolusIOB|BasalIOB) if enabled within preferences @@ -1097,7 +1097,7 @@ By default `"uploader_battery"` view is linked to `"uploader_battery"` , so no The formatting string is included into `"textvalue1"` key (`"textvalue1"`, `"textvalue2"`, etc keys are linked to `"textvalue"` key that could be included into `view` block) - `"textvalue"` key can be used with formatting information within the view block (in this situation format will be static, whatever the value or the settings) -- If you want to modify formatting information according to settings or values, thenall dynData feature can be applied, and the dedicated keys are `"invalidTextValue"` key (without "formatting information" because value is not valid) and `"textvalue1"`, `"textvalue2"`... (and as many values that you want to manage steps between minData and maxData) +- If you want to modify formatting information according to settings or values, then all dynData feature can be applied, and the dedicated keys are `"invalidTextValue"` key (without "formatting information" because value is not valid) and `"textvalue1"`, `"textvalue2"`... (and as many values that you want to manage steps between minData and maxData) - the additional `"dynPref"` keys are used to define other blocks for positioning variation and color variation depending on visible views, dark and matchDivider settings Concerning now the formatting string, syntax is the following: `%[flags][width][.precision]f` @@ -1165,7 +1165,7 @@ To use this feature, you need to: Note that if main app in phone is AAPSCLIENT and secondary app which broadcast data is AAPSCLIENT2, you will have to enable `Switch external data in watchface` parameter within Custom Watchface dedicated parameter if you use a watchface which use standard views and Ext1 additional views (Ext1 is linked to AAPSCLIENT and Ext2 is linked to AAPSCLIENT2) -Additionally three new views (`"patient_name"` , `"patient_name_Ext1"` and `"patient_name_Ext2"` *) has been added to be able to automatically include patient name (set within AAPS preferences) within watchface (see example below) +Additionally three new views (`"patient_name"` , `"patient_name_Ext1"` and `"patient_name_Ext2"` *) have been added to be able to automatically include patient name (set within AAPS preferences) within watchface (see example below) ![CustomWatchface_7](../images/CustomWatchface_7.png) @@ -1231,14 +1231,14 @@ Additionally three new views (`"patient_name"` , `"patient_name_Ext1"` and `"pa | `"highColor"` | `"#FFFF00"`(default Yellow): Color of BG value, trend arrows and bg value in graph if bg is above upper limit (Hyper) | | `"midColor"` | `"#00FF00"`(default Green): Color of BG value, trend arrows and bg value in graph if bg is within range | | `"lowColor"` | `"#FF0000"`(default Red): Color of BG value, trend arrows and bg value in graph if bg is below lower limit (Hypo) | -| `"lowBatColor"` | `"#E53935"`(default Dark Red): Color of `uploader_battery` when value is low (below 20% tbc) | +| `"lowBatColor"` | `"#E53935"`(default Dark Red): Color of `uploader_battery` when value is low (below 30%) | | `"carbColor"` | `"#FB8C00"`(default Orange): Color of Carbs points within graph | | `"basalBackgroundColor"` | `"#0000FF"`(default Dark blue): Color of TBR curve within graph | | `"basalCenterColor"` | `"#64B5F6"`(default Light blue): Color of Bolus or SMB points within graph | | `"gridColor"` | `"#FFFFFF"`(default White): Color of lines and text scale within graph | | `"pointSize"` | 2 (default): size of points in graph (1 for small point, 2 for big points) | | `"enableSecond"` | false (default): specify if watchface will manage seconds or not within `time`, `second` or `second_hand` views. it's important to be consistent between view visibility and this overall setting that will allow update every second of time information | -| `"dayNameFormat"` | "E" (default): from "E" to "EEEE" specify dayname format (number, short name, full name) tbc | +| `"dayNameFormat"` | "E" (default): from "E" to "EEEE" specify dayname format (number, short name, full name) | | `"monthFormat"` | "MMM" (default): from "M" to "MMMM" specify month format (number, short name, full name) | (cwf-reference-list-of-hardcoded-resource-files)= @@ -1289,7 +1289,7 @@ Note: all keys including `_Ext1` or `_Ext2` at the end are new and dedicated for | `"iob2"`
`"iob2_Ext1"` *
`"iob2_Ext2"` * | Text View | IOB Total or IOB Detailed | | | `"cob1"`
`"cob1_Ext1"` *
`"cob1_Ext2"` * | Text View | Carb label | | | `"cob2"`
`"cob2_Ext1"` *
`"cob2_Ext2"` * | Text View | COB Value | | -| `"delta"`
`"delta_Ext1"` *
`"delta_Ext2"` * | Text View | Short delta (5 min) | delta
delta_Ext1
delta_Ext2 | +| `"delta"`
`"delta_Ext1"` *
`"delta_Ext2"` * | Text View | Short delta (5 min) | delta
delta_Ext1
delta_Ext2 | | `"avg_delta"`
`"avg_delta_Ext1"` *
`"avg_delta_Ext2"` * | Text View | Avg Delta (15 min) | avg_delta
avg_delta_Ext1
avg_delta_Ext2 | | `"tempTarget"`*
`"tempTarget_Ext1"` *
`"tempTarget_Ext2"` * | Text View | BG Target (single value or min - max targets values) | tempTarget
tempTarget_Ext1
tempTarget_Ext2 | | `"reservoir"`*
`"reservoir_Ext1"` *
`"reservoir_Ext2"` * | Text View | Reservoir level | reservoir
reservoirLevel
reservoir_Ext1
reservoirLevel_Ext1
reservoir_Ext2
reservoirLevel_Ext2 | @@ -1416,10 +1416,10 @@ Note: all keys including `_Ext1` or `_Ext2` at the end are new and dedicated for | `"valueKey"` | string | name of dynamic data to use (generally same that associated view key).
If not existing, the default will be the values used for the view that uses this block.
for example you can define one block to customize battery level percentage without specifying valueKey, and then use the same block to customize uploader_battery and rig_battery | | `"minData"` | int | specify the minimum value to take into account for AAPS data : for example if value is sgv (unit mgdl internally), if minData is set to 50, all bg values below 50mgdl will be set to 50.
- Note that minData and maxData will be used to calculate dynamic values (in pixel or in degrees). | | `"maxData"` | int | specify the maximum value to take into account for AAPS data : for example if value is sgv (unit mgdl internally), if maxData is set to 330, all bg values above 330mgdl will be set to 330. | -| `"leftOffset"` | block | Specify the horizontal shift of the view according to min and max values in pixels.
- It includes minValue key, maxValueKey and invalidValue key (optional)
- If data is below or equal minData, then the view will be shifted to minValue pixels, and if data is above or equal to maxData, then the view will be shifted to maxValue pixels
Note that to apply this shift, `leftOffset` should be set to true within the view | -| `"topOffset"` | block | Specify the vertical shift of the view according to min and max values in pixels.
- It includes minValue key, maxValueKey and invalidValue key (optional)
- If data is below or equal minData, then the view will be shifted to minValue pixels, and if data is above or equal to maxData, then the view will be shifted to maxValue pixels
Note that to apply this shift topOffset should be set to true within the view | -| `"rotationOffset"` | block | Specify the rotation angle in degrees of the view according to min and max values in pixels.
- It includes `minValue` key, `maxValue` Key and `invalidValue` key (optional)
- If data is below or equal `minData`, then the view will rotate by `minValue` degrees, and if data is above or equal to `maxData`, then the view will rotate by `maxValue` degrees
Note that to apply this rotation, `rotationOffset` should be set to true within the view | -| `"dynValue"`* | block | Specify the dynValue conversion from min and max range to min and max values in pixels.
- It includes `minValue` key, `maxValue` Key and `invalidValue` key (optional)
- If data is below or equal `minData`, then the dynValue sent will be minValue (converted to double) , and if data is above or equal to `maxData`, then the dynValue calculated will be maxValue (converted to double)
Note that to apply this conversion, `dynValue` key should be set to true within the view | +| `"leftOffset"` | block | Specify the horizontal shift of the view according to min and max values in pixels.
- It includes `minValue` key, `maxValue` key and `invalidValue` key (optional)
- If data is below or equal minData, then the view will be shifted to minValue pixels, and if data is above or equal to maxData, then the view will be shifted to maxValue pixels
Note that to apply this shift, `leftOffset` should be set to true within the view | +| `"topOffset"` | block | Specify the vertical shift of the view according to min and max values in pixels.
- It includes `minValue` key, `maxValue` key and `invalidValue` key (optional)
- If data is below or equal minData, then the view will be shifted to minValue pixels, and if data is above or equal to maxData, then the view will be shifted to maxValue pixels
Note that to apply this shift topOffset should be set to true within the view | +| `"rotationOffset"` | block | Specify the rotation angle in degrees of the view according to min and max values.
- It includes `minValue` key, `maxValue` Key and `invalidValue` key (optional)
- If data is below or equal `minData`, then the view will rotate by `minValue` degrees, and if data is above or equal to `maxData`, then the view will rotate by `maxValue` degrees
Note that to apply this rotation, `rotationOffset` should be set to true within the view | +| `"dynValue"`* | block | Specify the dynValue conversion from min and max range to min and max values.
- It includes `minValue` key, `maxValue` Key and `invalidValue` key (optional)
- If data is below or equal `minData`, then the dynValue sent will be minValue (converted to double) , and if data is above or equal to `maxData`, then the dynValue calculated will be maxValue (converted to double)
Note that to apply this conversion, `dynValue` key should be set to true within the view | | `"minValue"` | int | result value to apply to the view (key only applicable within a leftOffset, topOffset or rotationOffset block) | | `"maxValue"` | int | result value to apply to the view (key only applicable within a leftOffset, topOffset or rotationOffset block) | | `"invalidValue"` | int | result value to apply to the view if data is invalid (key only applicable within a leftOffset, topOffset or rotationOffset block) | @@ -1450,10 +1450,10 @@ Note: all keys including `_Ext1` or `_Ext2` at the end are new and dedicated for | ------------------------------------------------------------ | -------- | ------------------------------------------------------------ | | `"sgv"`
`"sgv_Ext1"` *
`"sgv_Ext2"` * | valueKey | default minData = 39 mgdl
default maxData = 400 mgdl
- Note that real maxData is linked to your sensor and units are always in mgdl for internal values | | `"sgvLevel"`
`"sgvLevel_Ext1"` *
`"sgvLevel_Ext2"` * | valueKey | default minData = -1 (Hypo)
default maxData = 1 (Hyper)
if BG is within Range = 0 | -| `"direction"`
`"direction_Ext1"` *
`"direction_Ext2"` * | valueKey | default minData = 1 (double Down)
default maxValue = 7 (double Up)
flat arrow data = 4
Error or missing data = 0 (??) | +| `"direction"`
`"direction_Ext1"` *
`"direction_Ext2"` * | valueKey | default minData = 1 (double Down)
default maxData = 7 (double Up)
flat arrow data = 4
Error or missing data = 0 | | `"delta"`
`"delta_Ext1"` *
`"delta_Ext2"` * | valueKey | default minData = -25 mgdl
default maxData = 25 mgdl
- Note that real min and maxData can be above, and units are always mgdl for internal values | | `"avg_delta"`
`"avg_delta_Ext1"` *
`"avg_delta_Ext2"` * | valueKey | default minData = -25 mgdl
default maxData = 25 mgdl
- Note that real min and maxData can be above, and units are always mgdl for internal values | -| `"tempTarget"`*
`"tempTarget_Ext1"` *
`"tempTarget_Ext2"` * | valueKey | default minData = 0 (Profile Target)
default maxData = 2 (Temp Target)
Target is adjusted byt the loop = 1
Default or missing information = 0 | +| `"tempTarget"`*
`"tempTarget_Ext1"` *
`"tempTarget_Ext2"` * | valueKey | default minData = 0 (Profile Target)
default maxData = 2 (Temp Target)
Target is adjusted by the loop = 1
Default or missing information = 0 | | `"reservoir"`*
`"reservoir_Ext1"` *
`"reservoir_Ext2"` * | valueKey | default minData = 0 U
default maxData = 500 U | | `"reservoirLevel"`*
`"reservoirLevel_Ext1"` *
`"reservoirLevel_Ext2"` * | valueKey | default minData = 0 (Standard Color)
default maxData = 2 (Urgent Color)
Warning Color = 1 | | `"uploader_battery"` | valueKey | default minData = 0 %
default maxData = 100% | diff --git a/docs/EN/ExchangeSiteCustomWatchfaces/index.md b/docs/EN/ExchangeSiteCustomWatchfaces/index.md index 3717f52b0249..2093d13801b9 100644 --- a/docs/EN/ExchangeSiteCustomWatchfaces/index.md +++ b/docs/EN/ExchangeSiteCustomWatchfaces/index.md @@ -16,7 +16,7 @@ During merge of the pull request the documentation team will extract the CustomW | [![DigitalBigGraph](../images/ExchangeSiteCustomWatchfaces/DigitalBigGraph-CustomWatchface.png)
**DigitalBigGraph**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/DigitalBigGraph_v1.5.zip) | [![Gears](../images/ExchangeSiteCustomWatchfaces/Gears-CustomWatchface.jpg)
**Gears**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Gears.zip) | [![Gota](../images/ExchangeSiteCustomWatchfaces/Gota-CustomWatchface.png)
**Gota**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Gota_v2.4.zip) | | [![LuckyLoopKoeln](../images/ExchangeSiteCustomWatchfaces/LuckyLoopKoeln-CustomWatchface.png)
**LuckyLoopKoeln**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/LuckyLoopKoeln.zip) | [![P-Zero watchface](../images/ExchangeSiteCustomWatchfaces/pzero_v1.0-CustomWatchface.png)
**P-Zero watchface**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/pzero_v1.0.zip) | [![PinkFloydTheWall](../images/ExchangeSiteCustomWatchfaces/PinkFloydTheWall-CustomWatchface.png)
**PinkFloydTheWall**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/PinkFloydTheWall.zip) | | [![Robby watchface](../images/ExchangeSiteCustomWatchfaces/Robby_watchface-CustomWatchface.png)
**Robby watchface**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Robby_watchface.zip) | [![SimpleDigital](../images/ExchangeSiteCustomWatchfaces/SimpleDigital_v1.3-CustomWatchface.png)
**SimpleDigital**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/SimpleDigital_v1.3.zip) | [![SteamPunk](../images/ExchangeSiteCustomWatchfaces/SteamPunk-CustomWatchface.png)
**AAPS (SteamPunk)**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/SteamPunk.zip) | -| [![SteamPunk](../images/ExchangeSiteCustomWatchfaces/Blue_Ring-CustomWatchface.jpg)
**Blue Ring**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Blue_Ring.zip) | [![AAPSV2 TT DarkOnly](../images/ExchangeSiteCustomWatchfaces/AAPSV2_TT_DarkOnly-CustomWatchface.png)
**AAPSV2 + TT DarkOnly** *](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPSV2_TT_DarkOnly.zip) | | +| [![Blue Ring](../images/ExchangeSiteCustomWatchfaces/Blue_Ring-CustomWatchface.jpg)
**Blue Ring**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Blue_Ring.zip) | [![AAPSV2 TT DarkOnly](../images/ExchangeSiteCustomWatchfaces/AAPSV2_TT_DarkOnly-CustomWatchface.png)
**AAPSV2 + TT DarkOnly** *](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPSV2_TT_DarkOnly.zip) | | *Requires Custom WatchFace V2 or above installed within Wear Watch (AAPS V3.3.0 or above) diff --git a/docs/EN/Getting-Started/CompatiblesCgms.md b/docs/EN/Getting-Started/CompatiblesCgms.md index 1eea56fdd714..6285c356bd26 100644 --- a/docs/EN/Getting-Started/CompatiblesCgms.md +++ b/docs/EN/Getting-Started/CompatiblesCgms.md @@ -69,10 +69,10 @@ Trusted data sources allow **SMB** delivery, all the time. | Sensor | CGM app | | --------------------- | :----------------------------------------------------------: | | Dexcom G6 | BYODA, xDrip (**Direct, Native**) | -| Dexcom G7 | BYODA, xDrip (**Direct, Native**),
Juggluco (**xDrip broadcast** without xDrip) | -| Dexcom ONE+ | xDrip (**Direct, Native**),
Juggluco (**xDrip broadcast** without xDrip) | +| Dexcom G7 | BYODA, xDrip (**Direct, Native**),
Juggluco (**xDrip broadcast** without xDrip) | +| Dexcom ONE+ | xDrip (**Direct, Native**),
Juggluco (**xDrip broadcast** without xDrip) | | Dexcom ONE/Stelo | xDrip (**Direct, Native**) | -| Libre 2/2+ (EU) | xDrip (OOP2 **no calibration**),
Juggluco (**xDrip broadcast** without xDrip, or **Patched Libre** with xDrip) | +| Libre 2/2+ (EU) | xDrip (OOP2 **no calibration**),
Juggluco (**xDrip broadcast** without xDrip, or **Patched Libre** with xDrip) | | Libre 2/2+/3/3+ | Juggluco (**xDrip broadcast** without xDrip, or **Patched Libre** with xDrip) | | Syai | Syai App | diff --git a/docs/EN/Getting-Started/Introduction.md b/docs/EN/Getting-Started/Introduction.md index c10775aa5614..17396502f335 100644 --- a/docs/EN/Getting-Started/Introduction.md +++ b/docs/EN/Getting-Started/Introduction.md @@ -42,7 +42,7 @@ Several commercial hybrid closed loop systems have also been launched. These are **Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. -Android APS (**AAPS**) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established [OpenAPS](https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting T1D community. +Android APS (**AAPS**) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established [OpenAPS](https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting T1D community. Since OpenAPS is only compatible with certain older insulin pumps, **AAPS** (which can be used with a wider range of insulin pumps) was first developed in 2016 for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by many thousands of people worldwide. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes software and platforms. The fundamental components of the current **AAPS** system are outlined in **Figure 1** above. @@ -54,7 +54,7 @@ The “brain” of AAPS is an **app** which you build yourself. There are detail The **Android smartphone** will also need to have another app installed on it as well as **AAPS**. This [additional app](../Getting-Started/CompatiblesCgms.md) receives glucose data from a sensor (**2**) by Bluetooth, and then sends the data internally on the phone to the **AAPS app**. -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (**3**) on how much insulin to deliver by Bluetooth. All the information can be sent by mobile data or Wi-Fi to the internet (**4**). This data can also be shared with followers if desired, and/or collected for analysis. Optionally, you can also pair a [smartwatch](../Getting-Started/Watches.md) (**5**) with the phone to see your data at a glance and, with some watches, send basic commands to **AAPS**. +The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (**3**) on how much insulin to deliver by Bluetooth. All the information can be sent by mobile data or Wi-Fi to the internet (**4**). This data can also be shared with followers if desired, and/or collected for analysis. Optionally, you can also pair a [smartwatch](../Getting-Started/Watches.md) (**5**) with the phone to see your data at a glance and, with some watches, send basic commands to **AAPS**. ## What are the advantages of the AAPS system? @@ -98,13 +98,13 @@ Users can easily add or remove modules or functionality, and **AAPS** can be use a) The ability to set a lower **BG** target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). - b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to (for example) a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. + b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to (for example) a 120% profile (resulting in a 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. - c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. + c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. - d) After reconnecting a tubed pump which has been disconnected for swimming, **AAPS** will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. + d) After reconnecting a tubed pump which has been disconnected for swimming, **AAPS** will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. - e) **AAPS** has the facility for you to set different profiles for different situations and easily switch between them. For example, features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“**SMB**”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. + e) **AAPS** has the facility for you to set different profiles for different situations and easily switch between them. For example, features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“**SMB**”) and unannounced meals (“**UAM**”)) can be set to only work during the daytime, if you are worried about night-time hypos. These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles _etc_. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. @@ -296,9 +296,9 @@ Doctors (at least in the UK) are not prohibited from prescribing unlicensed medi 3. A DIY ‘bionic pancreas’ is changing diabetes care — what's next? [_Nature_ (2023), _620_, 940-941](https://doi.org/10.1038/d41586-023-02648-9) 4. Prescribing unapproved medical devices? The case of DIY artificial pancreas systems [_Medical law international_, (2021), _21_, 42-68](http://pure-oai.bham.ac.uk/ws/files/120241375/0968533221997510.pdf) 5. [Berlin Institute of Health position statement, 2022](https://www.bihealth.org/en/notices/do-it-yourself-solutions-for-people-with-diabetes-are-safe-and-recommended) -6. Do-It-Yourself Automated Insulin Delivery: A Health-care Practitioner User’s Guide (Diabetes Canada position and guide) [_Canadian Journal of Diabetes_, (2023)_47_, E8, 389-397](https://www.canadianjournalofdiabetes.com/article/S1499-2671(23)00138-7/fulltext) +6. Do-It-Yourself Automated Insulin Delivery: A Health-care Practitioner User’s Guide (Diabetes Canada position and guide) [_Canadian Journal of Diabetes_ (2023), _47_, E8, 389-397](https://www.canadianjournalofdiabetes.com/article/S1499-2671(23)00138-7/fulltext) 7. Netherlands (EN/NL) - for clinicians - [how to help people on open source automated insulin delivery systems](https://www.diabetotech.com/blog/how-to-help-people-on-open-source-automated-insulin-delivery-systems) -8. First Use of Open-Source Automated Insulin Delivery AndroidAPS in Full Closed-Loop Scenario: Pancreas4ALLRandomized Pilot Study [_Diabetes Technol. Ther._, +8. First Use of Open-Source Automated Insulin Delivery AndroidAPS in Full Closed-Loop Scenario: Pancreas4ALL Randomized Pilot Study [_Diabetes Technol. Ther._, 25, _5_, 2023](https://www.liebertpub.com/doi/pdf/10.1089/dia.2022.0562?casa_token=D13eFx5vCwwAAAAA:MYvO8hChbViXVJFgov1T11RXBPx2N_wOMThLHwl3TVUxbCuANegPrIFRC5R5VXx_S71FoQYW-qg) 9. Pre-school and school-aged children benefit from the switch from a sensor-augmented pump to an AndroidAPS hybrid closed loop: A retrospective analysis [_Pediatr. Diabetes_ 2021, _22_, 594-604. 2021](https://onlinelibrary.wiley.com/doi/epdf/10.1111/pedi.13190) @@ -382,9 +382,9 @@ or: 2) Press Windows key and enter “Control Panel” in the search field, open with Enter. It opens: “All Control Panel Items”. -Press the letter C to get to “Center for Ease of Use”, open with Enter. +Press the letter E to get to “Ease of Access Centre”, open with Enter. -Then open “Use computer without a screen” with Enter. +Then open “Use computer without a display” with Enter. There, at the bottom, you will find the checkbox “Enable Java Access Bridge”, select it. diff --git a/docs/EN/Getting-Started/Phones.md b/docs/EN/Getting-Started/Phones.md index 1a578e899ea7..ee7f5ec2c433 100644 --- a/docs/EN/Getting-Started/Phones.md +++ b/docs/EN/Getting-Started/Phones.md @@ -30,7 +30,7 @@ The document is read-only. With CTRL-F, you can search in the text of the Google To record your test of a hardware setup, please fill in this [form](https://docs.google.com/forms/d/e/1FAIpQLSfoGKLYEx4aUAJ5RWL3xLJeNdmRyxtXmDzpGhuU3Rfcj2H_Jw/viewform). After you fill in the form data, the sheet is updated automatically every 5 minutes. -Any problems with the spreadsheet, please contact its maintainer, *@theodoor5137*, on Discord, or see the [Where can I get help? page](../GettingHelp/WhereCanIGetHelp.md). +Any problems with the spreadsheet, please contact its maintainer, *@theodoor5137*, on Discord, or see the page on [how to get help](../GettingHelp/WhereCanIGetHelp.md). ## I didn't find my phone diff --git a/docs/EN/Getting-Started/PreparingForAaps.md b/docs/EN/Getting-Started/PreparingForAaps.md index 8bf78c653e75..abd901fb9002 100644 --- a/docs/EN/Getting-Started/PreparingForAaps.md +++ b/docs/EN/Getting-Started/PreparingForAaps.md @@ -53,7 +53,7 @@ SGLT-2 inhibitors, also called gliflozins, inhibit reabsorption of glucose in th In a nutshell: - **Example 1: risk of Hypo** ->During lunch, you use **AAPS** to bolus based on consuming 45 g of glucose. The problem is that, unbeknownst to AAPS, the inhibitors cause the body to eliminate some of the carbs. This leaves your body with too much insulin compared to the absorbed carbs, resulting in hypoglycemia. +>During lunch, you use **AAPS** to bolus based on consuming 45 g of carbs. The problem is that, unbeknownst to AAPS, the inhibitors cause the body to eliminate some of the carbs. This leaves your body with too much insulin compared to the absorbed carbs, resulting in hypoglycemia. - **Example 2: risk of Ketoacidosis** >The inhibitors eliminate some of the carbs in the background, causing a reduction in your BG. **AAPS** will automatically instruct the pump to decrease insulin intake, including basal. Over time this can result in your BG remaining below target value, to the point where the body does not have enough background insulin to absorb any carbs, resulting in ketoacidosis. Ordinarily, ketoacidosis develops in T1D patients because their pump fails, which would trigger alerts on their phone and be noticeable due to a high BG value. However, the danger with gliflozins is that there would be no AAPS alerts, as the pump remains operational and the BG potentially remains within target. @@ -80,7 +80,7 @@ In the preliminary stages of getting started with **AAPS**, you may experience d #### App build time and progressing to full looping -The time to build the **AAPS** app depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build **AAPS**. The process will significantly speed up for newer **AAPS** versions, as you become more experienced. +The time to build the **AAPS** app depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build **AAPS**. The process will significantly speed up for newer **AAPS** versions, as you become more experienced. Several parts of this documentation are dedicated to helping you through the build process: diff --git a/docs/EN/Getting-Started/Watches.md b/docs/EN/Getting-Started/Watches.md index e78c6ce1a552..dcbba5c98c3d 100644 --- a/docs/EN/Getting-Started/Watches.md +++ b/docs/EN/Getting-Started/Watches.md @@ -17,7 +17,7 @@ Integrating a smartwatch with **AAPS** can be useful in many situations, includi ## Specific advantages for parents/carers using **AAPS** -For a child - if their **AAPS** phone is nearby - a caregiver can use a smartwatch to monitor or make modifications without needing to use the **AAPS** phone. This can be useful, for example, if the **AAPS** phone is hidden away in a pump belt. +For a child - if their **AAPS** phone is nearby - a caregiver can use a smartwatch to monitor or make modifications without needing to use the **AAPS** phone. This can be useful, for example, if the **AAPS** phone is hidden away in a pump belt. A smartwatch can be used either _in addition_ to, or as an _alternative_ to the PHONE-based options for remote control or [following only](../RemoteFeatures/FollowingOnly.md). @@ -49,7 +49,7 @@ The best way to choose a smartwatch is to search for "watch" posts on either Dis ## Full Android -It sounds like an attractive option, right? However, at present, only a few enthusiasts are experimenting with **AAPS** on a stand-alone watch. There are a limited number of smartwatches with a reasonable interface which also work well with standalone use of **AAPS** and your CGM app. Popular models include the LEMFO LEM 15 Pro and 16. You will need to load the watch with the **AAPS** "full" apk (the apk which is usually installed on a smartphone) rather than the **AAPS** "wear" apk. +It sounds like an attractive option, right? However, at present, only a few enthusiasts are experimenting with **AAPS** on a stand-alone watch. There are a limited number of smartwatches with a reasonable interface which also work well with standalone use of **AAPS** and your CGM app. Popular models include the LEMFO LEM 15 Pro and 16. You will need to load the watch with the **AAPS** "full" apk (the apk which is usually installed on a smartphone) rather than the **AAPS** "wear" apk. While there is no clear specification which helps you to know if a watch will work well for standalone **AAPS** use, the following parameters will help: @@ -58,13 +58,13 @@ While there is no clear specification which helps you to know if a watch will wo 3) Very good battery life. 4) Good Bluetooth range. -Most of the frustrations of standalone **AAPS** watches come from interacting with a tiny screen, and the fact that the current AAPS full app interface has not been designed for a watch. You may prefer to use a stylus to edit **AAPS** settings on the watch, due to the restricted screen size, and some AAPS buttons may not be visible on the watch screen. +Most of the frustrations of standalone **AAPS** watches come from interacting with a tiny screen, and the fact that the current AAPS full app interface has not been designed for a watch. You may prefer to use a stylus to edit **AAPS** settings on the watch, due to the restricted screen size, and some AAPS buttons may not be visible on the watch screen. Additional challenges are that it is hard to get sufficient battery life, and watches with sufficient battery are often bulky and thick. Users report fighting with the OS and power-saving settings, difficulty in starting sensors on the watch, poor Bluetooth range (for maintaining connection with both the sensor and pump) and questionable water resistance. Examples are shown in the photos below. ![image](../images/6d787373-bc0c-404d-89aa-54d3127c4a6f.png) -If you are interested in setting up a standalone watch, read the posts and comments on the **AAPS** Facebook group (good search options are “standalone” and “Lemfo”) and Discord for more information. +If you are interested in setting up a standalone watch, read the posts and comments on the **AAPS** Facebook group (good search options are “standalone” and “Lemfo”) and Discord for more information. ## Wear OS @@ -181,7 +181,7 @@ You can read more about them, including how to set them up, on the [WatchDrip+ w ![image](../images/935d28bb-a909-4ca8-850d-6a765bd4fcde.png) -Pebble watches ([now discontinued](https://en.wikipedia.org/wiki/Pebble_(watch))) were on general sale from 2013 to 2016, and may still be available second-hand. Fitbit took over Pebble’s assets. Pebble users can use the Urchin watchface to view Nightscout data. Displayed data options include IOB, currently active temp basal rate and predictions. If open looping you can use IFTTT to create an applet that says if a Notification has been received from **AAPS** then send either an SMS or pushover notification. +Pebble watches ([now discontinued](https://en.wikipedia.org/wiki/Pebble_(watch))) were on general sale from 2013 to 2016, and may still be available second-hand. Fitbit took over Pebble’s assets. Pebble users can use the Urchin watchface to view Nightscout data. Displayed data options include IOB, currently active temp basal rate and predictions. If open looping you can use IFTTT to create an applet that says if a Notification has been received from **AAPS** then send either an SMS or pushover notification. ### [Bluejay watches](https://bluejay.website/) diff --git a/docs/EN/GettingHelp/AccessingLogFiles.md b/docs/EN/GettingHelp/AccessingLogFiles.md index 4f60d9b0977e..da9ade12c9b9 100644 --- a/docs/EN/GettingHelp/AccessingLogFiles.md +++ b/docs/EN/GettingHelp/AccessingLogFiles.md @@ -5,10 +5,10 @@ * Locate the log files in the AAPS data directory, in `Android\data\info.nightscout.androidaps\files`.
The naming of the root storage folder may vary a little depending on the phone. * The location is `Android\data\info.nightscout.aapsclient\files` for [AAPSClient](#RemoteControl_aapsclient). -* Note : log location has changed in **AAPS 3.3**. See the previous versions' documentation if needed. +* Note: log location has changed in **AAPS 3.3**. See the previous versions' documentation if needed. ![logs](../images/aapslog.png) -* The current log is a .log file which can be viewed in a number of ways such as [LogCat](https://developer.android.com/studio/debug/am-logcat.html) within Android Studio, any Log Viewer android app, or simply as plain text. +* The current log is a .log file which can be viewed in a number of ways such as [LogCat](https://developer.android.com/studio/debug/am-logcat.html) within Android Studio, any log viewer Android app, or simply as plain text. * Previous log files are zipped and stored in folders in date/time order. * If you are sharing your log file in [discord](https://discord.gg/4fQUWHZ4Mw) to talk about a potential bug, please unzip and upload the file dated before the error occurred. diff --git a/docs/EN/GettingHelp/BluetoothTroubleshooting.md b/docs/EN/GettingHelp/BluetoothTroubleshooting.md index c100ff6f0fe2..eb5e7a03ddfc 100644 --- a/docs/EN/GettingHelp/BluetoothTroubleshooting.md +++ b/docs/EN/GettingHelp/BluetoothTroubleshooting.md @@ -11,7 +11,7 @@ Some of these issues likely apply to other Bluetooth Insulin pumps too, the Medt (bluetoothtroubleshooting-cannot-start-omnipod-with-android-16)= ## Cannot start Omnipod with Android 16 -- Android 16 needs at a minimum **AAPS** version 3.3.2.1 for the Omnipod DASH to work correctly, as this versions has fixes added to specifically address known problems introduced in Android 16 for Omnipod. +- Android 16 needs at a minimum **AAPS** version 3.3.2.1 for the Omnipod DASH to work correctly, as this version has fixes added to specifically address known problems introduced in Android 16 for Omnipod. --- @@ -48,11 +48,11 @@ Ping @XiTatiON on #omnipod-dash Discord channel to discuss apps to be added to t - **myBMW** MyBMW interrupted Medtrum Nano and Omnipod DASH. The MyBMW app prompts regarding permission for "find nearby devices" only once, if you don't grant it, it still works absolutely OK -- **Amazon Alexa** Removing "Nearby devices" for Alexa app resolved problem for some people but will break the ability to pair Matter IOT devices +- **Amazon Alexa** Removing "Nearby devices" for Alexa app resolved problem for some people but will break the ability to pair Matter IoT devices - **MINI app** Appears the app is based on myBMW app and might mirror its behavior as a result -- **BM2** Solar Battery Monitoring app, used in a some camper van and camping solar setups, when the app is running it prevented activation of a new Pod. Force Stopping the app while activating an new pod is a workaround to the issue. Running the app after that didn't appear to interfere with Dash functionality (On a Pixel 8 Pro running A16). +- **BM2** Solar Battery Monitoring app, used in some camper van and camping solar setups: when the app was running, it prevented activation of a new Pod. Force Stopping the app while activating a new pod is a workaround to the issue. Running the app after that didn't appear to interfere with Dash functionality (On a Pixel 8 Pro running A16). (bluetoothtroubleshooting-revoke-nearby-device-permission)= @@ -63,7 +63,7 @@ Follow this procedure to revoke the "Nearby device" permission for all apps exce ```{admonition} Menus and settings :class: note -The screenshots and instructions in this guide are from a Vanilla Android 16 install on Google Pixel 8 Pro. Other manufactures and devices will likely not exactly match these menus and settings descriptions, adjust the steps to suit the device you have and if you are stuck see [Where to get help for dash](#omnipod-dash-where-to-get-help-for-dash) section on how to reach out to the community for support. +The screenshots and instructions in this guide are from a Vanilla Android 16 install on Google Pixel 8 Pro. Other manufacturers and devices will likely not exactly match these menus and settings descriptions, adjust the steps to suit the device you have and if you are stuck see [Where to get help for dash](#omnipod-dash-where-to-get-help-for-dash) section on how to reach out to the community for support. ``` 1. Open Android settings on your phone, scroll down and press on **Security and privacy (1)**. @@ -103,7 +103,7 @@ If you are unsure which app is causing you an issue, disable them all (remember ### How to re-enable "Nearby device" permissions for system apps and other apps: -1. If required Reference the **"How to revoke "Nearby device" permissions for other apps"** section on how to get to the app privacy settings, then once in the **Nearby device** configuration proceed to 2. +1. If required Reference the **"How to revoke 'Nearby device' permissions for other apps"** section on how to get to the app privacy settings, then once in the **Nearby device** configuration proceed to 2. 2. Browse the list of apps and press on the app you wish to allow **Nearby devices** permissions for. @@ -122,7 +122,7 @@ If an app is revoked you will need to scroll down until you see the list of revo ![android_auto_nearby_dev_missing_hamburger](../images/android_16/android_auto_nearby_dev_missing_hamburger.png) ![android_auto_nearby_show_system](../images/android_16/android_auto_nearby_show_system.png) ![android_nearby_dev_system](../images/android_16/android_nearby_dev_system.png) -5. Follow the guidance in **"How to revoke "Nearby device" permissions for other apps"** in reverse to re-enable permissions for each app. +5. Follow the guidance in **"How to revoke 'Nearby device' permissions for other apps"** in reverse to re-enable permissions for each app. --- diff --git a/docs/EN/GettingHelp/BrowserBuildTroubleshooting.md b/docs/EN/GettingHelp/BrowserBuildTroubleshooting.md index d9f35237e7a6..c223a93b6f9f 100644 --- a/docs/EN/GettingHelp/BrowserBuildTroubleshooting.md +++ b/docs/EN/GettingHelp/BrowserBuildTroubleshooting.md @@ -107,8 +107,8 @@ Tap **Re-run jobs**. You can also start a new build from **Run workflow** as usu - [Update the `GDRIVE_OAUTH2` secret](#aaps-ci-update-secret) in your GitHub repository with the new token, then [re-run the build](#aaps-ci-rerun). (aaps-ci-disable-software)= -### Disable Software That May Interfere With OAUTH Verification - - Disable any VPN or security app (firewall, antimalware,...) on the phone before trying to get the OAUTH key. +### Disable Software That May Interfere With OAuth Verification + - Disable any VPN or security app (firewall, antimalware,...) on the phone before trying to get the OAuth key. (aaps-ci-actions-permission)= ### Check GitHub Actions Permission Settings diff --git a/docs/EN/GettingHelp/TroubleshootingAndroidStudio.md b/docs/EN/GettingHelp/TroubleshootingAndroidStudio.md index c1df83ea4455..ead5ff8b13ad 100644 --- a/docs/EN/GettingHelp/TroubleshootingAndroidStudio.md +++ b/docs/EN/GettingHelp/TroubleshootingAndroidStudio.md @@ -50,7 +50,7 @@ Clone sources again as described in wiki and do not allow gradle update * You must receive a message saying what Git version is installed, as you can see in the screenshot above. In this case, go to [Step 2](#troubleshooting-android-studio-check-for-uncommitted-changes). - * In case you get an message saying + * In case you get a message saying ``` Git: command not found ``` @@ -60,13 +60,13 @@ Clone sources again as described in wiki and do not allow gradle update * If you are on Windows and Git was just installed, you should restart your computer to make Git globally available after the installation - * If Git is installed, you have restarted (if on windows), and Git still cannot be found: + * If Git is installed, you have restarted (if on Windows), and Git still cannot be found: * Search your computer for a file "git.exe". Note for yourself, which directory it is saved in. - * Go to the Environment variables in windows, select the variable "PATH" and click edit. Add the directory where + * Go to the Environment variables in Windows, select the variable "PATH" and click edit. Add the directory where you have found your Git installation. * Save and close. @@ -142,7 +142,7 @@ Or: Cause: error: invalid source release: 21 ``` -If you experience the above error message, you need to download a correct JVM version before you can try rebuild again: +If you experience the above error message, you need to download a correct JVM version before you can try to rebuild: 1. Check in the [requirement table](#Building-APK-recommended-specification-of-computer-for-building-apk-file) which JVM version you need for the **AAPS** version you are building, and make a note of it. @@ -257,7 +257,7 @@ Your apk was built successfully and can be transferred to your phone! ## Apk installed but old version -If you built the app successfully, transferred it to your phone and installed it successfully but the version number stays the same then you might have missed to [update your local copy](#Update-to-new-version-update-your-local-copy) +If you built the app successfully, transferred it to your phone and installed it successfully but the version number stays the same then you might have forgotten to [update your local copy](#Update-to-new-version-update-your-local-copy) ## None of the above worked diff --git a/docs/EN/GettingHelp/TroubleshootingNsClient.md b/docs/EN/GettingHelp/TroubleshootingNsClient.md index 77754fbf81a0..d54c0ac841a3 100644 --- a/docs/EN/GettingHelp/TroubleshootingNsClient.md +++ b/docs/EN/GettingHelp/TroubleshootingNsClient.md @@ -37,6 +37,6 @@ If **AAPS** connects to Nightscout correctly but BG displays as N/A: in the [NSC * If you still get an error... -Check the size of your database in MongoDB (or via the database size plugin in nightscout). If you are using the free tier in MongoDB, 496MB means it is full and needs to be cleaned up. [Follow these Nightscout instructions for checking the size of your database and clearing out data](https://nightscout.github.io/troubleshoot/troublehoot/#database-full). +Check the size of your database in MongoDB (or via the database size plugin in nightscout). If you are using the free tier in MongoDB, 496MB means it is full and needs to be cleaned up. [Follow these Nightscout instructions for checking the size of your database and clearing out data](https://nightscout.github.io/troubleshoot/troubleshoot/#database-full). Before clearing data from your database and if you haven't already set it up, you should consider donating your AAPS data to the Open Humans project (for research). The instructions are on the [OpenHumans configuration page](../SupportingAaps/OpenHumans.md). diff --git a/docs/EN/GettingHelp/WhereCanIGetHelp.md b/docs/EN/GettingHelp/WhereCanIGetHelp.md index 07763de17ea9..6ddd6dacec43 100644 --- a/docs/EN/GettingHelp/WhereCanIGetHelp.md +++ b/docs/EN/GettingHelp/WhereCanIGetHelp.md @@ -1,6 +1,6 @@ -# Where can I get help ? +# Where can I get help? -## I'm stuck; What should I do? Who can I ask? +## I'm stuck; what should I do? Who can I ask? This project is based on volunteer work and a few rules apply to any requests for help to avoid unnecessary time being wasted by those who kindly pay it forward: diff --git a/docs/EN/Maintenance/DocumentationUpdate.md b/docs/EN/Maintenance/DocumentationUpdate.md index 8140d38e62f1..b460e6d05a49 100644 --- a/docs/EN/Maintenance/DocumentationUpdate.md +++ b/docs/EN/Maintenance/DocumentationUpdate.md @@ -48,7 +48,7 @@ - DiaKEM: new installs don't work after servers upgrade @psonnera - Removed Libre 2 patched app (obsolete): doesn't work with new sensors @psonnera -- Reworked Omnipod Dash page @XiTatiON +- Reworked Omnipod DASH page @XiTatiON ## August 2025 @@ -97,7 +97,7 @@ AAPS 3.1 documentation is available [here](https://androidaps.readthedocs.io/en/ - [BG quality warning sign](#aaps-screens-bg-warning-sign) @tanja - [Medtronic pump update](../CompatiblePumps/MedtronicPump.md) @dottedfingertips - [Necessary checks after update to AAPS 3.0](Update3_0.md) @tanja -- [Omnipod Dash](../CompatiblePumps/OmnipodDASH.md) @Freloner @robertrub @vanelsberg +- [Omnipod DASH](../CompatiblePumps/OmnipodDASH.md) @Freloner @robertrub @vanelsberg - Update docs for AAPS 3.0 (partly) @xJoe - [Wear OS for AAPS 3.0](../WearOS/WearOsSmartwatch.md) @peterleimbach @@ -112,7 +112,7 @@ AAPS 3.1 documentation is available [here](https://androidaps.readthedocs.io/en/ ## November 2021 -- Best practices for calibrating a libre 2 sensor +- Best practices for calibrating a Libre 2 sensor - [ISF](../UsefulLinks/FAQ.md) reformulation of impact - Update [troubleshooting Android studio](../GettingHelp/TroubleshootingAndroidStudio.md) - Removed patched [Dexcom](../CompatibleCgms/DexcomG6.md) app as it is obsolete @@ -212,7 +212,7 @@ AAPS 3.1 documentation is available [here](https://androidaps.readthedocs.io/en/ ## December 2019 -- [Android auto](../RemoteFeatures/AndroidAuto.md) - setup with screenshots +- [Android Auto](../RemoteFeatures/AndroidAuto.md) - setup with screenshots - [Accu-Chek Insight & Autotune](#Accu-Chek-Insight-Pump-settings-in-aaps) - workaround for usage - [Glimp](#Config-Builder-bg-source) - version 4.15.57 and newer supported - [Watchfaces](../WearOS/WearOsSmartwatch.md) - major update, way more details @@ -238,7 +238,7 @@ AAPS 3.1 documentation is available [here](https://androidaps.readthedocs.io/en/ ## October 2019 - [AAPS version 2.5](#Releasenotes-version-2-5-0) updates (especially on [update page](../Maintenance/UpdateToNewVersion.md)) -- [AccuChek Insight - log options](#Accu-Chek-Insight-Pump-settings-in-aaps) +- [Accu-Chek Insight - log options](#Accu-Chek-Insight-Pump-settings-in-aaps) - [COB calculation on separate page](../DailyLifeWithAaps/CobCalculation.md) - [COB - wrong COB value detection](#CobCalculation-detection-of-wrong-cob-values) - [Dexcom G6 specific troubleshooting](#DexcomG6-troubleshooting-g6) diff --git a/docs/EN/Maintenance/ExportImportSettings.md b/docs/EN/Maintenance/ExportImportSettings.md index 1fcdf55763be..e3a30fc22ba1 100644 --- a/docs/EN/Maintenance/ExportImportSettings.md +++ b/docs/EN/Maintenance/ExportImportSettings.md @@ -61,11 +61,11 @@ Exporting the AAPS settings to file enables you to restore its configuration to * Any time you plan to make significant changes to your configuration (change SMB settings, change insulin types, change pump, make changes to automations) you should back up your **Settings** before and after making the changes. This way you have your most recent settings as well as a copy of what they were before the changes in case you need to revert back to them. -* Tubeless pumps (Such as Omnipod and Medtrum) users only : the **Settings** file contains connection details on your current pod and can be used to restore connection to that pod with a new phone. If you do not have a copy of your preferences exported after you started your current pod you will need to start a new pod in the event you need to replace your current phone. +* Tubeless pumps (Such as Omnipod and Medtrum) users only: the **Settings** file contains connection details on your current pod and can be used to restore connection to that pod with a new phone. If you do not have a copy of your preferences exported after you started your current pod you will need to start a new pod in the event you need to replace your current phone. **How to back-up manually:** -1. If this your first time importing or exporting **Settings** you will need to set a master password in [Settings > Protection](#Preferences-master-password). Set a password and record this in a safe place. _You will be unable to access your **Settings** back-ups without this password._ +1. If this is your first time importing or exporting **Settings** you will need to set a master password in [Settings > Protection](#Preferences-master-password). Set a password and record this in a safe place. _You will be unable to access your **Settings** back-ups without this password._ 2. From the **AAPS** main screen, open the **menu** (☰) > **Maintenance**. Choose where to save the file with the **Local** and **Cloud** chips next to **Export settings** (see **Exporting or Importing Settings** below), then tap **Export settings**. **AAPS** shows where the file will go: the file name for **Local**, **Google Drive** for **Cloud**. Tap **OK**. @@ -108,7 +108,7 @@ To export or import settings, open the **menu** (☰) and select **Maintenance** (ExportImportSettings-Automating-Settings-Export)= ### Automating Settings Export ### -For doing automating settings exports [(**see Automation**)](../DailyLifeWithAaps/Automations.md#automating-preference-settings-export) open [**Settings** > **Maintenance**](#preferences-maintenance-settings), expand **Unattended Settings Export** and switch on **Enable automated settings export**. +To automate settings exports [(**see Automation**)](../DailyLifeWithAaps/Automations.md#automating-preference-settings-export) open [**Settings** > **Maintenance**](#preferences-maintenance-settings), expand **Unattended Settings Export** and switch on **Enable automated settings export**. You can now configure [Automation](../DailyLifeWithAaps/Automations.md#automating-preference-settings-export) to export settings, either on a regular basis (_i.e._ each week), or after a pod change. @@ -179,7 +179,7 @@ By default, an import leaves your pump settings alone: the pump selected in **Co 12. **AAPS** asks **Apply imported settings?** and tells you how many settings will change and, if you left the box unticked, how many pump settings are kept. Nothing has been written yet, so **Cancel** leaves your phone exactly as it was. Tap **OK** to apply. - ![Apply imported settings? dialog](../images/Maintenance/import_settings_apply.png) + ![Apply imported settings dialog](../images/Maintenance/import_settings_apply.png) 13. **AAPS** applies the imported settings straight away, without restarting. Only the plugins whose settings changed are restarted. While this runs, **AAPS** shows **Applying settings…**; if the pump is busy, it shows **Waiting for pump…** and applies the settings once the pump is idle. If the pump is still busy after one minute, **AAPS** offers to try again. A **Settings applied** message confirms that the imported settings are in use. Any treatment you had queued while the import ran is dropped and **AAPS** tells you that it was cancelled, so nothing is sent to the pump twice. diff --git a/docs/EN/Maintenance/ReleaseNotes.md b/docs/EN/Maintenance/ReleaseNotes.md index b491dbe27bbc..9f40779c5721 100644 --- a/docs/EN/Maintenance/ReleaseNotes.md +++ b/docs/EN/Maintenance/ReleaseNotes.md @@ -97,7 +97,7 @@ Release date: 31-10-2026 **Pump Driver Improvements** - Pump overview screens rebuilt for Insight, Medtronic, Medtrum, Omnipod, Dana, Diaconn and Equil @MilosKozak -- **Omnipod Dash**: PDM style Ref codes and readable fault descriptions, drift compensation always on, better bolus type reporting @nl-ruud +- **Omnipod DASH**: PDM style Ref codes and readable fault descriptions, drift compensation always on, better bolus type reporting @nl-ruud - **Omnipod**: hard-end date for Dash & Eros @mcnelson - **DanaR, RS**: pump emulator for testing @MilosKozak - **Equil**: pump emulator for testing @MilosKozak @@ -188,7 +188,7 @@ Full changelog: nightscout > +6. You will see the message Workflow run was successfully requested. Refresh your browser page and you will be able to monitor the build progress. When the action completes, the AAPS CI action will show a green tick mark. You have successfully built the updated version of **AAPS**. This means that the Master and Wear apk is now directly saved into your Google Drive (as per below). AAPSClient apk can be downloaded from Github > nightscout > AndroidAPS [here](https://github.com/nightscout/AndroidAPS/releases) diff --git a/docs/EN/Maintenance/UpdateComputerBuild.md b/docs/EN/Maintenance/UpdateComputerBuild.md index 7f0d8b064c5f..30255fed4f8a 100644 --- a/docs/EN/Maintenance/UpdateComputerBuild.md +++ b/docs/EN/Maintenance/UpdateComputerBuild.md @@ -5,7 +5,7 @@ **AAPS** is not available to download, due to regulations concerning medical devices. It is legal to build the app for your own use, but you must not give a copy to others! See [FAQ page](../UsefulLinks/FAQ.md) for details. ```{note} -In case you want to build **AAPS** on a new computer : copy your back-up keystore file to the new computer. Then follow the [Initial build **AAPS** procedure](../SettingUpAaps/BuildingAaps.md) instead of this guide. With the only difference that instead of creating a new keystore, you can select the one you have copied on the new computer. +In case you want to build **AAPS** on a new computer: copy your back-up keystore file to the new computer. Then follow the [Initial build **AAPS** procedure](../SettingUpAaps/BuildingAaps.md) instead of this guide. With the only difference that instead of creating a new keystore, you can select the one you have copied on the new computer. ``` ## Overview for updating to a new version of AAPS with Android Studio @@ -96,6 +96,6 @@ If anything goes wrong, don't panic. Take a breath! -Then see the separate page [troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) if your problem is already documented! +Then check if your problem is already documented on the separate page [troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md). If you need further help, please reach out to other **AAPS** users on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). \ No newline at end of file diff --git a/docs/EN/Maintenance/UpdateToNewVersion.md b/docs/EN/Maintenance/UpdateToNewVersion.md index 4a123034079b..6c24d31fe80a 100644 --- a/docs/EN/Maintenance/UpdateToNewVersion.md +++ b/docs/EN/Maintenance/UpdateToNewVersion.md @@ -34,9 +34,9 @@ These steps are the same for every build method. Check in the [Release Notes](.. After you installed the new apk: -- you can check the __AAPS'__ version on your phone by opening the __menu__ (☰) on the top left and then __About__ (as per the screenshot below). The __AAPS'__ current version can be viewed; -- ensure import settings have been actioned; and -- please check your __AAPS'__ settings under __Settings__ and ensure these remain accurate. +- you can check the __AAPS__ version on your phone by opening the __menu__ (☰) on the top left and then __About__ (as per the screenshot below). The current __AAPS__ version can be viewed; +- make sure you have imported your settings; and +- please check your __AAPS__ settings under __Settings__ and ensure these remain accurate. ![About dialog with the AAPS version installed](../images/about_dialog_version.png) diff --git a/docs/EN/RemoteFeatures/AndroidAuto.md b/docs/EN/RemoteFeatures/AndroidAuto.md index ca20c4adbde1..577c12e563b4 100644 --- a/docs/EN/RemoteFeatures/AndroidAuto.md +++ b/docs/EN/RemoteFeatures/AndroidAuto.md @@ -5,7 +5,7 @@ ## Requirements -**AAPS** uses a feature of Android Auto which allows messages from apps on the mobile to be routed to the display of Auto Audio in the car. +**AAPS** uses a feature of Android Auto which allows messages from apps on the mobile to be routed to the display of the car audio system. That means that: @@ -38,7 +38,7 @@ Please check now that you see the **AAPS** status notification on the phone befo As **AAPS** is not an official Android Auto app, notifications have to be activated for "unknown sources" in Android Auto. This is done through the use of the developer mode which we will show you here. -Go to your car and connect your mobile with the cars audio system. +Go to your car and connect your mobile with the car's audio system. You should now see a screen similar to this screen. diff --git a/docs/EN/RemoteFeatures/FollowingOnly.md b/docs/EN/RemoteFeatures/FollowingOnly.md index 761dafd9504a..93c44fdb84e2 100644 --- a/docs/EN/RemoteFeatures/FollowingOnly.md +++ b/docs/EN/RemoteFeatures/FollowingOnly.md @@ -119,7 +119,7 @@ If your **AAPS** data source is not xDrip but you can display BG data from the C ![image](../images/remote_control_and_following/xdrip4ios.jpg) -xDripSwift was created from porting the original xDrip app to iOS and evolved to "xDrip for iOS" written **xDrip4iOS** . +xDripSwift was created from porting the original xDrip app to iOS and evolved into "xDrip for iOS", written as **xDrip4iOS**. ```{admonition} Further detail about how to attempt to obtain the original **xDrip4iOS** app :class: dropdown @@ -157,7 +157,7 @@ Sugarmate is compatible with: * Apple iPad (Requires software version 13.0 or later) * Google Android (Save web app to your homescreen) -It has been reported by users of Sugarmate that it can be used with Apple CarPlay in the USA to display glucose readings when driving. It is not yet established if this is possible in countries outside the USA. If you know more about this, please add details in here to the documentation by completing a pull-request (link) which is quick and easy to do. +It has been reported by users of Sugarmate that it can be used with Apple CarPlay in the USA to display glucose readings when driving. It is not yet established if this is possible in countries outside the USA. If you know more about this, please add details in here to the documentation by completing a [pull request](../SupportingAaps/HowToEditTheDocs.md), which is quick and easy to do. ### [Spike](https://spike-app.com/) (iOS) @@ -180,13 +180,13 @@ See [here](../Getting-Started/Watches.md). :local: true ``` -### M5 stack +### M5Stack ![image](../images/061edb52-56d2-45f4-b3da-82b2036d7bc6.png) The M5Stack is a small box which can be programmed for many applications, Martin's project [M5Stack NightscoutMon](https://github.com/mlukasek/M5_NightscoutMon/wiki) is displaying sensor glucose values and trends, IOB and COB. It is in a plastic box, equipped with a colour display, micro SD card slot, 3 buttons, speaker and internal battery. It is a great blood sugar monitor and is relatively easy to set up if you have a Nightscout account. Users typically run it on their home Wi-Fi, but some users report using it as a display when motorbiking, by running it off a phone Wi-Fi hotspot. -### Sugarpixel +### SugarPixel SugarPixel is a device for secondary glucose display alert system for continuous glucose monitoring that connects with Dexcom app or Nightscout app on the user’s smartphone. The device displays real time blood sugar readings. This CGM hardware monitor benefits from random tone generation audio alerts (which are incredibly loud), vibration alerts for hearing impaired, customizable display options and native multi-user following. diff --git a/docs/EN/RemoteFeatures/RemoteControl.md b/docs/EN/RemoteFeatures/RemoteControl.md index d8c46ccc447c..999ab1f83229 100644 --- a/docs/EN/RemoteFeatures/RemoteControl.md +++ b/docs/EN/RemoteFeatures/RemoteControl.md @@ -45,7 +45,7 @@ Note: the opacity of the widget background can be set in the widget configuratio **AAPSClient** can be installed on a single phone or multiple follower phones (i.e. parent 1’s follower phone and parent 2’s follower phone) in order for both caregivers to be granted access and remote control a patient's **AAPS** phone. -To download **AAPSClient**, navigate to the [Github repository](https://github.com/nightscout/AndroidAPS/releases/) and click on the asset +To download **AAPSClient**, navigate to the [GitHub repository](https://github.com/nightscout/AndroidAPS/releases/) and click on the asset **“app-AAPSClient-release_x.x.x.x”** (it may be a newer version to that shown in the screenshot below): ![image](../images/remote_control_and_following/AAPSClient_download_02.png) @@ -61,7 +61,7 @@ The **AAPSClient** apk can now be either: Transferred by a USB cable onto the follower phone; or Dragged into Google drive folder, and then added onto the follower phone by clicking on the "app-AAPSClient-release" file. -Should you be needing **AAPS** for yourself, and **AAPSClient** for monitoring someone else, you will need to build **AAPSClient** yourself instead of downloading it from the Github repository as described above. The reason is that you can't install both **AAPS** and **AAPSClient** on the same phone, signed by a different key.
+Should you be needing **AAPS** for yourself, and **AAPSClient** for monitoring someone else, you will need to build **AAPSClient** yourself instead of downloading it from the GitHub repository as described above. The reason is that you can't install both **AAPS** and **AAPSClient** on the same phone, signed by a different key.
To build **AAPSClient** yourself, follow the same process as [regular AAPS build](../SettingUpAaps/BuildingAaps.md). On the **Generate signed App Bundle or APK** page, select **aapsclientRelease** instead of **fullRelease**. The same rule applies when you install several client apps (**AAPSClient**, **AAPSClient2**, **AAPSClient3**) on one follower phone: they must all be signed with the **same key**. Otherwise Android refuses to install the second one (error `INSTALL_FAILED_DUPLICATE_PERMISSION`). @@ -134,7 +134,7 @@ A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. (RemoteControl_nightscout)= ## 3) Nightscout -As well as Nightscout being a server in “the Cloud”, there is also a dedicated **Nightscout** app which can be downloaded directly from the App Store on your iPhone. If you have an Android follower phone, there is not a dedicated Nightscout app and it is better to use [**AAPSClient**](#2-aapsclient), or, if you only want to follow, and not send treatments you can download and install the [Nightwatch](https://play.google.com/store/apps/details?id=se.cornixit.nightwatch) app from the Playstore. +As well as Nightscout being a server in “the Cloud”, there is also a dedicated **Nightscout** app which can be downloaded directly from the App Store on your iPhone. If you have an Android follower phone, there is not a dedicated Nightscout app and it is better to use [**AAPSClient**](#RemoteControl_aapsclient), or, if you only want to follow, and not send treatments you can download and install the [Nightwatch](https://play.google.com/store/apps/details?id=se.cornixit.nightwatch) app from the Playstore. Once you have installed the **Nightscout** app on your iPhone, open the app and follow the set-up prompts, entering your Nightscout address (see below, left). The form of this may vary depending on how your Nightscout is hosted. (_e.g._ http://youraddresshere.herokuapp.com). Then enter your Nightscout API secret (see below, right). If not prompted for your API password, then you need to enter this by clicking on the padlock at the top of the app: @@ -184,7 +184,7 @@ Looking in more detail at the top left menu of the Nightscout app: 3. Hamburger - for setting preferences 4. Careportal - Log treatment (see [below](#RemoteControl_nightscout-treatments) for when **AAPS** applies these) -![nightscout top bar](../images/remote-control-29.png) +![Nightscout top bar](../images/remote-control-29.png) There is a huge amount of information on the status of the **AAPS** system in the grey tabs (and even more information is revealed if you tap the tab) on this screen: @@ -209,7 +209,7 @@ Press "refresh" at the bottom of the page to close the popup. (RemoteControl_nightscout-treatments)= ### Sending treatments through the Nightscout app to AAPS -In **AAPS** 4 the supported way to control **AAPS** remotely is a **paired AAPSClient**, see [Master ↔ Client control](#client-master-control): each client has a [role](#client-master-control-roles) that limits what it may do, and every command is signed, checked and confirmed by the **AAPS** phone. While client control is on, the **AAPS** phone is in [hardened mode](#client-master-control-hardened-mode): treatments, temporary targets and profile switches entered on the Nightscout website or in the Nightscout app are **not** applied. The Nightscout app is then a tool for following only. +In **AAPS** 4 the supported way to control **AAPS** remotely is a **paired AAPSClient**, see [Master ↔ Client control](#client-master-control): each client has a [role](#client-master-control-roles) that limits what it may do, and every command is signed by the client, then checked and confirmed by the **AAPS** phone. While client control is on, the **AAPS** phone is in [hardened mode](#client-master-control-hardened-mode): treatments, temporary targets and profile switches entered on the Nightscout website or in the Nightscout app are **not** applied. The Nightscout app is then a tool for following only. ```{admonition} Only when client control is off :class: warning @@ -285,7 +285,7 @@ a) **AAPSClient** or **SMS** commands cannot work; or b) The user wishes to avoid typing an authentication code (as required for SMS commands). -A smartwatch needs **Wear OS 3 or newer** to be able to control **AAPS**. Please check the technical specifications of the watch, and see the [Smartwatches page](../Getting-Started/Watches.md). Search, or ask in the **AAPS** Facebook/Discord groups if unsure. +A smartwatch needs **Wear OS 3 or newer** to be able to control **AAPS**. Please check the technical specifications of the watch, and see the [Smartwatches page](../Getting-Started/Watches.md). Search, or ask in the **AAPS** Facebook/Discord groups if unsure. Specific How-to guides for setting up **AAPS** on the popular Samsung Galaxy Watch 4 (40mm) are given below. The [Garmin](https://apps.garmin.com/en-US/apps/a2eebcac-d18a-4227-a143-cd333cf89b55?fbclid=IwAR0k3w3oes-OHgFdPO-cGCuTSIpqFJejHG-klBTm_rmyEJo6gdArw8Nl4Zc#0) watch is also a popular choice. If you have experience of setting up a different smartwatch which you think would be useful to others, please add it into these pages [edit the documentation](../SupportingAaps/HowToEditTheDocs.md) to share your findings with the wider **AAPS** community. @@ -293,7 +293,7 @@ Specific How-to guides for setting up **AAPS** on the popular Samsung Galaxy Wat ![Wear Remote 2](../images/Wear_Remote2.png) -The software for the watch, **AAPSClient** Wear apk, can be downloaded directly from [Github](https://github.com/nightscout/AndroidAPS/releases/). +The software for the watch, **AAPSClient** Wear apk, can be downloaded directly from [GitHub](https://github.com/nightscout/AndroidAPS/releases/). To download the software, click on the watch app that matches the client app on the phone: **wear-aapsclient-release_**_version_ goes with **AAPSClient**, **wear-aapsclient2-release_**_version_ goes with **AAPSClient2** (see [About AAPSClient, AAPSClient2 and AAPSClient3](#remotecontrol-aapsclient-versions)): diff --git a/docs/EN/RemoteFeatures/RemoteControlWearOS.md b/docs/EN/RemoteFeatures/RemoteControlWearOS.md index ed6b8651a3b0..6553d79b7283 100644 --- a/docs/EN/RemoteFeatures/RemoteControlWearOS.md +++ b/docs/EN/RemoteFeatures/RemoteControlWearOS.md @@ -291,7 +291,7 @@ The dialogs the buttons open. Swipe from right to left to reach the next page of | --- | --- | --- | --- | --- | --- | | ![Treatment dialog, insulin page](../images/wearos/dialogs/dialog_treatment.png) | ![Insulin dialog](../images/wearos/dialogs/dialog_insulin.png) | ![Carbs dialog](../images/wearos/dialogs/dialog_carbs.png) | ![eCarbs dialog](../images/wearos/dialogs/dialog_ecarbs.png) | ![Temp Target dialog, duration page](../images/wearos/dialogs/dialog_temp_target.png) | ![Profile switch dialog](../images/wearos/dialogs/dialog_profile_switch.png) | -[1] In the watch's **Settings** > **Interface**, turn on **Calculator Percentage** to show the percentage input in the bolus calculator. The default percentage comes from the phone's ["Deliver this part of the bolus wizard result %"](#Preferences-deliver-this-part-of-bolus-wizard-result). The other calculator settings are those of the phone under **Settings** > **Bolus wizard settings**. +[1] In the watch's **Settings** > **Interface**, turn on **Calculator Percentage** to show the percentage input in the bolus calculator. The default percentage comes from the phone's ["Bolus percentage"](#Preferences-deliver-this-part-of-bolus-wizard-result). The other calculator settings are those of the phone under **Settings** > **Bolus wizard settings**. [2] In the watch's **Settings** > **Interface**, turn on **Calculator Meal Type** to show the **Meal type** page, where you pick **Bread**, **Cake** or **Pizza** to split the carbs of a slow meal into carbs now and eCarbs later. See [Choosing the meal type](#WearOsSmartwatch-wizard-meal-type). @@ -361,7 +361,7 @@ While charging, it would be helpful if the display could stay “always-on” an The simplified UI mode is available for the Digital Style and Custom watchfaces. The simplified UI is optional and is configured through the watch face settings (long press the watch face and click “edit” or the gear icon). Select the configuration “Simplify UI" and set it to “During Charging” or “Always On and Charging”. -The Android developer options enable your watch to stay awake during charging. To make the developer options available, see the [official documentation](https://developer.android.com/training/wearables/get-started/debugging). Set the “Stay awake when charging” to “on” in the developer options”. +The Android developer options enable your watch to stay awake during charging. To make the developer options available, see the [official documentation](https://developer.android.com/training/wearables/get-started/debugging). Set the “Stay awake when charging” to “on” in the developer options. Note: not all displays can handle always-on very well. It can cause screen burn-in, especially on the older OLED displays. The watches will generally dim the display to prevent burn-in; please check your owner’s manual, the manufacturing, or the internet for advice. @@ -389,7 +389,7 @@ The *time to eat* reminder is not sent this way: the watch rings that one by its ## Snooze Alert shortcut -The watch [shows the alarm](#WearOsSmartwatch-phone-alarms) itself; the shortcut is a second way to silence it, with one press. It is possible to create a shortcut to snooze the alerts/alarm of AAPS. Muting the sound via your watch is convenient and faster without reaching for your phone. Note; you still have to check your alarm message on your phone and handle it accordingly, but you can check that later. When your watch has two buttons, you can assign a key to the `AAPS Snooze Alert` program. +The watch [shows the alarm](#WearOsSmartwatch-phone-alarms) itself; the shortcut is a second way to silence it, with one press. It is possible to create a shortcut to snooze the alerts/alarm of AAPS. Muting the sound via your watch is convenient and faster without reaching for your phone. Note: you still have to check your alarm message on your phone and handle it accordingly, but you can check that later. When your watch has two buttons, you can assign a key to the `AAPS Snooze Alert` program. To link the button on the Samsung Watch 4 go to `Settings > Advanced Features > Customize Buttons > Double press > AAPS Snooze Alert` @@ -439,7 +439,7 @@ If the watch shows no data or old data, first check the connection between the w If you want to build your own watchface, follow the [guide here](../ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md). -Once you have built a custom watchface, you can share your own **AAPS** custom watchface with others, the zip-file can be uploaded in the folder "ExchangeSiteCustomWatchfaces" via a Pull Request into Github. During merge of the pull request, the documentation team will extract the CustomWatchface.png file and prefix it with the filename of the Zip-file. +Once you have built a custom watchface, you can share your own **AAPS** custom watchface with others, the zip-file can be uploaded in the folder "ExchangeSiteCustomWatchfaces" via a Pull Request into GitHub. During merge of the pull request, the documentation team will extract the CustomWatchface.png file and prefix it with the filename of the Zip-file. (WearOsSmartwatch-complications-watchface-download)= diff --git a/docs/EN/RemoteFeatures/RemoteMonitoring.md b/docs/EN/RemoteFeatures/RemoteMonitoring.md index 2bd4d6c5ab15..f0f5574dafe6 100644 --- a/docs/EN/RemoteFeatures/RemoteMonitoring.md +++ b/docs/EN/RemoteFeatures/RemoteMonitoring.md @@ -8,7 +8,7 @@ __AAPS__ offers several features for remote monitoring of type 1 diabetic childr - Kid's pump is controlled by kid's phone using __AAPS__. - Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their Android phone (an iPhone version of **AAPSClient** is in development, see [AAPSClient](AapsClient.md)). Settings amended in __AAPS__ will synchronize with __AAPSClient__ and vice versa. -- Caregivers can be alarmed by using **xDrip app in follower mode** on their Android phone if xdrip companion mode is set up. +- Caregivers can be alarmed by using **xDrip app in follower mode** on their Android phone if xDrip companion mode is set up. - Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication. - Remote control through __AAPSClient__ uses the signed command channel introduced in **AAPS** 4: the client must first be **paired** with the master (with a QR code or a PIN), and every command is confirmed and executed by the master. Each caregiver's phone can get its own [role](#client-master-control-roles), from read-only to full control — see [Master ↔ Client control](#client-master-control). diff --git a/docs/EN/RemoteFeatures/SMSCommands.md b/docs/EN/RemoteFeatures/SMSCommands.md index f15305402852..319798c7c364 100644 --- a/docs/EN/RemoteFeatures/SMSCommands.md +++ b/docs/EN/RemoteFeatures/SMSCommands.md @@ -205,13 +205,13 @@ The *Auth* column in the tables below, indicates whether such a strong authentic | Command | Auth | Function & *Response* | |------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | BG | No | Returns: last BG, delta, IOB (bolus and basal), COB
*Last BG: 5.6 4min ago, Delta: -0,2 mmol, IOB: 0.20U (Bolus: 0.10U Basal: 0.10U)* | -| CAL 5.6/90 | Yes | Will calibrate the CGM with a value of 5.6/90
(use the value appropriate to your glucose units)
Works only if properly set-up in **AAPS**.
*Calibration sent* | +| CAL 5.6/90 | Yes | Will calibrate the CGM with a value of 5.6/90
(use the value appropriate to your glucose units)
Works only if properly set-up in **AAPS**.
*Calibration sent. Receiving must be enabled in xDrip+.* | ### Pump | Command | Auth | Function & *Response* | |----------------------|------|-------------------------------------------------------------------------------------------| -| PUMP | No | Last conn: 1 min ago
Temp: 0.00U/h @11:38 5/30min
IOB: 0.5U Reserv: 34U Batt: 100 | +| PUMP | No | LastConn: 1 min ago
Temp: 0.00U/h @11:38 5/30min
IOB: 0.5U Reserv: 34U Batt: 100 | | PUMP DISCONNECT *30* | Yes | To disconnect pump for *30* minutes | | PUMP CONNECT | Yes | Pump reconnected | @@ -232,12 +232,12 @@ Some pumps take a temp basal only in percent, others only in U/h. If you use the | Command | Auth | Function & *Response* | |-------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| LOOP STATUS | No | Response depends on actual status:
- *Loop is disabled* if the loop is disabled or LGS
- *Loop is enabled* if the loop is closed or open
- *Suspended (10 min)* if the loop is disconnected or suspended | +| LOOP STATUS | No | Response depends on actual status:
- *Loop is disabled* if the loop is disabled
- *Loop is enabled* if the loop is closed, open or LGS
- *Pump disconnected* if the pump is disconnected
- *Suspended (10 m)* if the loop is suspended | | LOOP STOP/DISABLE | Yes | The pump will revert to the pre-programmed basal rate.
*Loop has been disabled* | -| LOOP SUSPEND 20 | Yes | *Loop suspended for 20 minutes* | +| LOOP SUSPEND 20 | Yes | *Loop suspended* | | LOOP RESUME | Yes | *Loop resumed* | -| LOOP CLOSED | Yes | *Current loop mode: Closed Loop* | -| LOOP LGS | Yes | *Current loop mode: Low Glucose Suspend* | +| LOOP CLOSED | Yes | *Current running mode: Closed Loop* | +| LOOP LGS | Yes | *Current running mode: Low Glucose Suspend* | ### Bolus @@ -355,6 +355,6 @@ If the other app is installed on multiple phones make sure to deactivate upload ### I am getting far too many text messages from SMS Commands. Can I reduce the frequency, or make them stop? Using SMS commands may generate a lot of automated messages from the **AAPS** phone to the caregiver’s phone. You will also receive messages, for example “basal profile in pump updated” if you have automations set up in **AAPS**. It can be useful to have unlimited SMS allowance on your **AAPS** phone plan (and for each caregiver phone used) if a lot of SMS will be sent, and to deactivate SMS notifications, alarms or vibrations on all phones. It is not possible to use SMS commands and not receive these updates. -Because of this, you may want an alternative way to communicate directly with your child (if they are old enough), instead of SMS. Common alternative communication apps used by **AAPS** caregivers include Whatsapp, Lime, Telegram, and Facebook Messenger. +Because of this, you may want an alternative way to communicate directly with your child (if they are old enough), instead of SMS. Common alternative communication apps used by **AAPS** caregivers include WhatsApp, LINE, Telegram, and Facebook Messenger. -It is possible to disable the "Profile changed" SMS, when the Profile change originated from Nightscout. To do this, create a file named **exactly** `do_not_send_sms_on_profile_change` in the `extra` dir of your AAPS directory. +It is possible to disable the "Basal profile in pump updated" SMS, when the Profile change originated from Nightscout. To do this, create a file named **exactly** `do_not_send_sms_on_profile_change` in the `extra` dir of your AAPS directory. diff --git a/docs/EN/Sandbox/sandbox1.md b/docs/EN/Sandbox/sandbox1.md index eff1e91f25bc..f797b76cd19a 100644 --- a/docs/EN/Sandbox/sandbox1.md +++ b/docs/EN/Sandbox/sandbox1.md @@ -55,7 +55,7 @@ Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod Label in the middle of [nowhere](#sandbox1-in-the-middle-of-nowhere) This instead is the label to [](#sandbox1-this-is-another-test) and it should display its name -Links with anchor : +Links with anchor: - [how long will it take?](#preparing-how-long-will-it-take) - [NSClient settings in Preferences](#Preferences-nsclient). - [prediction lines in AAPS OVERVIEW](#aaps-screens-prediction-lines) to header level 4 diff --git a/docs/EN/SettingUpAaps/BrowserBuildDownloadPrep.md b/docs/EN/SettingUpAaps/BrowserBuildDownloadPrep.md index 4f0cbb5d13ef..751f3e231797 100644 --- a/docs/EN/SettingUpAaps/BrowserBuildDownloadPrep.md +++ b/docs/EN/SettingUpAaps/BrowserBuildDownloadPrep.md @@ -14,7 +14,7 @@ Or visit the latest release page: https://github.com/nightscout/aaps-ci-preparation/releases/latest ``` -2.Backup copy hosted on this site: +2. Backup copy hosted on this site: - If the external link is also unavailable, you can use this backup file to download. diff --git a/docs/EN/SettingUpAaps/BrowserBuildFork.md b/docs/EN/SettingUpAaps/BrowserBuildFork.md index ced5dbdda528..537f21fced73 100644 --- a/docs/EN/SettingUpAaps/BrowserBuildFork.md +++ b/docs/EN/SettingUpAaps/BrowserBuildFork.md @@ -6,7 +6,7 @@ This is **Step 1** of the [Browser build](BrowserBuild.md). ``` -You will need to secretly store your personal Android Java Key and Google Drive information in GitHub (later in the process, we will explain how). +You will need to store your personal Android Java Key and Google Drive information as secrets in GitHub (later in the process, we will explain how). Since this cannot be done inside the public repository of AndroidAPS, you need to make your personal copy of the source code (called a fork). @@ -29,15 +29,15 @@ Scroll down the next screen and tap **Create Fork**. ![fork_aaps_confirm](../images/Building-the-App/CI/ForkAAPS2.png) -*Note: you can **unselect** "Copy the master branch only" if you will want to build developers versions or customizations.* +*Note: you can **unselect** "Copy the master branch only" if you will want to build developer versions or customizations.* ![fork_aaps_main](../images/Building-the-App/CI/ForkAAPS3.png) ```{note} -You cannot fork and you see this?

-**`No available destinations to fork this repository.`**

-![Already forked](../images/Building-the-App/CI/ForkAAPS3b.png)

-This means you already have an existing fork of AndroidAPS.
+You cannot fork and you see this?

+**`No available destinations to fork this repository.`**

+![Already forked](../images/Building-the-App/CI/ForkAAPS3b.png)

+This means you already have an existing fork of AndroidAPS.
Make sure it's up to date and continue to Preparation Steps. ``` diff --git a/docs/EN/SettingUpAaps/BrowserBuildKeystore.md b/docs/EN/SettingUpAaps/BrowserBuildKeystore.md index 1cfe42c99339..59d40b050b07 100644 --- a/docs/EN/SettingUpAaps/BrowserBuildKeystore.md +++ b/docs/EN/SettingUpAaps/BrowserBuildKeystore.md @@ -6,7 +6,7 @@ This is **Step 2** of the [Browser build](BrowserBuild.md). First complete [Step 1 – Create your GitHub fork](BrowserBuildFork.md). ``` -AndroidAPS must be signed with private keys stored in a **Java KeyStore (JKS)**. This is the most important decision of the whole process, because it determines whether you will be able to **upgrade** AAPS later without reinstalling. +AAPS must be signed with private keys stored in a **Java KeyStore (JKS)**. This is the most important decision of the whole process, because it determines whether you will be able to **upgrade** AAPS later without reinstalling. ```{note} In the next steps you will store private information (your keystore, and later your Google Drive access) inside GitHub as **secrets**. A secret is simply an encrypted value that only your own build can read – nobody else, not even people looking at your fork, can see it. This is what keeps your build yours. @@ -74,7 +74,7 @@ Before using this export method, make sure your keystore and Google Drive settin 2. **Run Export Workflow:** - Go to the **Actions** tab in your repository - - Select **CI KeyStore Export** + - Select **CI Keystore Export** - Click **Run workflow** - The exported keystore ZIP file will be saved to your Google Drive diff --git a/docs/EN/SettingUpAaps/BrowserBuildO1.md b/docs/EN/SettingUpAaps/BrowserBuildO1.md index 9112f46842e3..11ec798b1ea0 100644 --- a/docs/EN/SettingUpAaps/BrowserBuildO1.md +++ b/docs/EN/SettingUpAaps/BrowserBuildO1.md @@ -3,7 +3,7 @@ # Option 1 – Generate a new keystore ```{note} -This is part of [Step 2 – Create your signing keystore](BrowserBuildKeystore.md) of the [Browser build](BrowserBuild.md). Make sure you have read the [Option 1 vs Option 2 decision](#aaps-ci-preparation) and downloaded the preparation file. +This is part of [Step 2 – Create your signing keystore](BrowserBuildKeystore.md) of the [Browser build](BrowserBuild.md). Make sure you have read the [Option 1 vs Option 2 decision](#aaps-ci-preparation). ``` Option 1 generates a brand-new signing keystore for you. It is suitable for first-time users, or those without a JKS, or who have forgotten the password or alias. diff --git a/docs/EN/SettingUpAaps/BrowserBuildO1Computer.md b/docs/EN/SettingUpAaps/BrowserBuildO1Computer.md index dabf6b92a7b5..1edffc936eaf 100644 --- a/docs/EN/SettingUpAaps/BrowserBuildO1Computer.md +++ b/docs/EN/SettingUpAaps/BrowserBuildO1Computer.md @@ -18,30 +18,30 @@ Use a computer (supports Windows/Mac/Linux) Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html) -Install Simple Web Server
-If you are a Windows or Mac user, you can install it from the Microsoft Store or the Mac App Store.
-If your browser asks whether to open the store app, allow it.

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_store.png)
+Install Simple Web Server
+If you are a Windows or Mac user, you can install it from the Microsoft Store or the Mac App Store.
+If your browser asks whether to open the store app, allow it.

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_store.png)
Example on Mac: -- get → install → open

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server.png)

+- get → install → open

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server.png)

-- Click Get Started

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step1.png)

+- Click Get Started

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step1.png)

-- Click New Server

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step2.png)

+- Click New Server

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step2.png)

-- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server.

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step3.png)

+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server.

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step3.png)

-- Seeing this screen means the server has been started.

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step4.png)

+- Seeing this screen means the server has been started.

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step4.png)

-- Do not close Simple Web Server. Please switch to your browser and open
-[http://127.0.0.1:8080/aaps-ci-preparation.html](http://127.0.0.1:8080/aaps-ci-preparation.html)

+- Do not close Simple Web Server. Please switch to your browser and open
+[http://127.0.0.1:8080/aaps-ci-preparation.html](http://127.0.0.1:8080/aaps-ci-preparation.html)

- For the subsequent steps, please refer to the video below, starting from 1 minute 37 seconds. diff --git a/docs/EN/SettingUpAaps/BrowserBuildO2.md b/docs/EN/SettingUpAaps/BrowserBuildO2.md index bdf13f356497..e53d18ab830b 100644 --- a/docs/EN/SettingUpAaps/BrowserBuildO2.md +++ b/docs/EN/SettingUpAaps/BrowserBuildO2.md @@ -3,7 +3,7 @@ # Option 2 – Upload your existing keystore ```{note} -This is part of [Step 2 – Create your signing keystore](BrowserBuildKeystore.md) of the [Browser build](BrowserBuild.md). Make sure you have read the [Option 1 vs Option 2 decision](#aaps-ci-preparation) and downloaded the preparation file. +This is part of [Step 2 – Create your signing keystore](BrowserBuildKeystore.md) of the [Browser build](BrowserBuild.md). Make sure you have read the [Option 1 vs Option 2 decision](#aaps-ci-preparation). ``` Option 2 reuses the JKS you already created on a previous build of AAPS from a computer in Android Studio. It is suitable for users who already have a JKS and know the JKS password and alias. diff --git a/docs/EN/SettingUpAaps/BrowserBuildO2Computer.md b/docs/EN/SettingUpAaps/BrowserBuildO2Computer.md index b313c9260164..a6e6c2ea91d0 100644 --- a/docs/EN/SettingUpAaps/BrowserBuildO2Computer.md +++ b/docs/EN/SettingUpAaps/BrowserBuildO2Computer.md @@ -28,32 +28,32 @@ Use a computer (supports Windows/Mac/Linux) -Install Simple Web Server

+Install Simple Web Server

If you are a Windows or Mac user, you can install it from the Microsoft Store or the Mac App Store. -If your browser asks whether to open the store app, allow it.

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_store.png)

+If your browser asks whether to open the store app, allow it.

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_store.png)

Example on Mac: -- get → install → open

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server.png)

+- get → install → open

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server.png)

-- Click Get Started

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step1.png)

+- Click Get Started

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step1.png)

-- Click New Server

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step2.png)

+- Click New Server

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step2.png)

-- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server.

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step3.png)

+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server.

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step3.png)

-- Seeing this screen means the server has been started.

-![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step4.png)

+- Seeing this screen means the server has been started.

+![simple_http_server](../images/Building-the-App/CI/aaps_ci_simple_http_server_step4.png)

-- Do not close Simple Web Server. Please switch to your browser and open

-[http://127.0.0.1:8080/aaps-ci-preparation.html](http://127.0.0.1:8080/aaps-ci-preparation.html)

+- Do not close Simple Web Server. Please switch to your browser and open

+[http://127.0.0.1:8080/aaps-ci-preparation.html](http://127.0.0.1:8080/aaps-ci-preparation.html)

-- For the subsequent steps, please refer to the video below, starting from 2 minute 18 seconds.

+- For the subsequent steps, please refer to the video below, starting from 2 minutes 18 seconds.

diff --git a/docs/EN/SettingUpAaps/BuildingAaps.md b/docs/EN/SettingUpAaps/BuildingAaps.md index dbd1bc16fa71..366ca86628dd 100644 --- a/docs/EN/SettingUpAaps/BuildingAaps.md +++ b/docs/EN/SettingUpAaps/BuildingAaps.md @@ -12,7 +12,7 @@ Three methods are available to build the AAPS app: ### Build with a browser (recommended) -You can build the app with your smartphone using GitHub Actions. From an Android phone, the [AAPS Builder](#aaps-builder) setup page walks you through it, and you start each build yourself. From a computer or an iPhone, you can also build with a fork and save the app in your Google Drive. +You can build the app in a web browser using GitHub Actions. From an Android phone, the [AAPS Builder](#aaps-builder) setup page walks you through it, and you start each build yourself. From a computer or an iPhone, you can also build with a fork and save the app in your Google Drive. **[Follow these instructions.](./BrowserBuild.md)** diff --git a/docs/EN/SettingUpAaps/ChangeAapsConfiguration.md b/docs/EN/SettingUpAaps/ChangeAapsConfiguration.md index d37a9cc44d46..1a384762df77 100644 --- a/docs/EN/SettingUpAaps/ChangeAapsConfiguration.md +++ b/docs/EN/SettingUpAaps/ChangeAapsConfiguration.md @@ -1,4 +1,4 @@ -# Making changes to your AAPS' configuration +# Making changes to your AAPS configuration After you have completed the **[Setup Wizard](../SettingUpAaps/SetupWizard.md)**, you don't need to run the entire Wizard again if you want to only change parts of your **AAPS**' configuration. diff --git a/docs/EN/SettingUpAaps/CompletingTheObjectives.md b/docs/EN/SettingUpAaps/CompletingTheObjectives.md index 660ba89d76e6..83689406c818 100644 --- a/docs/EN/SettingUpAaps/CompletingTheObjectives.md +++ b/docs/EN/SettingUpAaps/CompletingTheObjectives.md @@ -10,7 +10,7 @@ When **AAPS** is installed for the first time, each objective must be completed **Objectives 1 to 8** will guide you from configuring **AAPS** on your smartphone to “basic” hybrid closed looping. This will take about 6 weeks to complete. You can proceed up to **Objective 5** using a virtual pump (and using some other method of insulin delivery in the meantime). **Objectives 9 and 10** are designed to test more advanced **AAPS** features with the aim of better control of your diabetes, and will take up to 3 months to complete, possibly longer. Further details on an estimated breakdown of time can be obtained here: [How long will it take?](#preparing-how-long-will-it-take) -As well as progressing through the **Objectives**, if required, you can also remove your progress and [go back to an earlier objective](#go-back-in-objectives). +As well as progressing through the **Objectives**, if required, you can also remove your progress and [go back to an earlier objective](#CompletingTheObjectives-go-back-in-objectives). ## Backup your settings @@ -39,7 +39,7 @@ The **Objectives** will need to be restarted from the beginning should you fail - If using Tidepool: - Follow instructions in [Tidepool](../SettingUpAaps/Tidepool.md) page to ensure **Tidepool** can receive and display **AAPS** data. -Note - *You may need to wait for the next sensor glucose reading to arrive before **AAPS** will recognize it.* +Note: *You may need to wait for the next sensor glucose reading to arrive before **AAPS** will recognize it.* (objectives-objective2)= ## Objective 2: Learn how to control AAPS @@ -52,7 +52,7 @@ Each task shows its status (**1**): the orange "**Not completed yet**" turns int Tasks to complete **Objective 2** are: - Set your **Profile** to 90% for a duration of 10 min. - _Hint_: Tap your Profile name on the main screen to open the **Profile** screen, then use the **Activate** (▶) button and set percentage and duration. More information in [Profile switch & Profile Percentage](../DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md). - - _Note_: **AAPS** does not accept basal rates below 0.05U/hr. If your **Profile** includes rates 0.06U/hr or lower you will need to create a temporary **Profile** with higher basal rates before completing this task. Switch back to your normal **Profile** after completing this task. + - _Note_: **AAPS** does not accept basal rates below 0.05U/hr. If your **Profile** includes rates 0.05U/hr or lower you will need to create a temporary **Profile** with higher basal rates before completing this task. Switch back to your normal **Profile** after completing this task. - Simulate "taking a shower" by [disconnecting your pump](#AapsScreens-loop-status) in **AAPS** for a duration of 1h. - _Hint_: press the loop icon on the main screen to open the Loop dialog, then choose a duration under **Disconnect pump**. - End "taking a shower" by reconnecting your pump. @@ -95,7 +95,7 @@ The minimal time to complete this objective: **7 days**. This is a mandatory wai - Use [**Temp Targets**](../DailyLifeWithAaps/TempTargets.md) when necessary. After treating a hypo, use the predefined "hypo temp target" to prevent the system from overcorrecting upon the bounce back. - If you are still in [Simple Mode](#preferences-simple-mode) at this point, now is probably a good time to switch it off. -To reduce the number of proposed basal rate changes while in Open Loop, you can still use the tips described in [**Objective 3**](#objective-3-prove-your-knowledge). +To reduce the number of proposed basal rate changes while in Open Loop, you can still use the tips described in [**Objective 3**](#objectives-objective3). Additionally, you can change the minimum percentage for recommended basal rate changes with the "**Open mode minimum change**" setting in **Settings → Loop**. The higher the value, the fewer change notifications you will receive. ![Open Loop minimal request change](../images/OpenLoop_MinimalRequestChange2.png) @@ -122,7 +122,7 @@ You might wish to set your [**Profile** BG target](#profile-glucose-targets) hig ```{admonition} If you have been using a virtual pump, change to a real insulin pump now! :class: note -If you are open looping with a virtual pump **stop here**. Only click verify at the end of this **Objective** once you have changed to using a "real" pump which delivers insulin. +If you are open looping with a virtual pump **stop here**. Only tap **Verify** at the end of this **Objective** once you have changed to using a "real" pump which delivers insulin. ``` @@ -170,14 +170,14 @@ Minimal time to complete this objective: **1 day**. This is a mandatory wait tim - Select **Closed Loop** by pressing the [Loop icon](#AapsScreens-loop-status) on the main screen and choosing **Closed Loop** as running mode. Stay in **Closed Loop** over a period of 1 day. -- Slowly raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0, until you find the settings that work best for you. +- Slowly raise your 'Max IOB for SMB' (in OpenAPS called 'max-iob') above 0, until you find the settings that work best for you. The default recommendation for this setting is “**average meal bolus + 3x max daily basal**”, where “max daily basal” is the maximum hourly value in any time segment of the day. ![max daily basal](../images/MaxDailyBasal2.png) This recommendation should be seen as a starting point. If you use this rule but are experiencing AAPS delivering too much insulin as glucose levels rise, you may need to : -* lower the "Maximum total IOB OpenAPS can’t go over" value; +* lower the "Max IOB for SMB" value; * review your **Profile** settings, only making one adjustment at a time. Alternatively, if you are very insulin resistant, raise the **maxIOB** value very cautiously. @@ -206,7 +206,7 @@ Minimal time to complete this objective: **28 days**. This is a mandatory wait t - The [SMB section in this documentation](#Open-APS-features-super-micro-bolus-smb) and [oref1 coverage in the openAPS docs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) are must-reads to understand **SMB** and the concept of **zero-temping**. - Once done, you can [raise maxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over) to get **SMBs** working more effectively. maxIOB now includes all **IOB**, not just accumulated basal. This threshold pauses **SMBs** until IOB drops below this value (_e.g._ **maxIOB** is set to 7U and a bolus of 8U is given to cover a meal: SMBs will be paused and not given unless **IOB** drops below 7U). - A good start is setting **maxIOB** = **average meal bolus + 3x max daily basal** where "max daily basal" is the maximum hourly value in any time segment of the day. See [objective 7](#objective-7-tuning-the-closed-loop-raising-maxiob-above-0-and-gradually-lowering-bg-targets) as reference. + A good start is setting **maxIOB** = **average meal bolus + 3x max daily basal** where "max daily basal" is the maximum hourly value in any time segment of the day. See [objective 7](#objectives-objective7) as reference. - Evaluate your carb absorption rate and consider changing the “min_5m_carbimpact”-parameter in [Settings → Absorption settings → min_5m_carbimpact](#Preferences-min_5m_carbimpact) if you find it too slow or too fast. (objectives-objective10)= diff --git a/docs/EN/SettingUpAaps/ComputerBuild.md b/docs/EN/SettingUpAaps/ComputerBuild.md index 6019e9559601..2c380ee5ae2e 100644 --- a/docs/EN/SettingUpAaps/ComputerBuild.md +++ b/docs/EN/SettingUpAaps/ComputerBuild.md @@ -110,12 +110,12 @@ Git is a program that allows you to track changes in code and to collaborate wit (BuildingAaps-steps-for-installing-git)= #### Steps for Installing Git -1. Check that you don’t already have **Git** installed. You can do this by typing “git” in the Windows search bar – if you see **“Git bash”** or some other form of Git, it is already installed and you can go straight to [installing Android Studio](#install-android-studio): +1. Check that you don’t already have **Git** installed. You can do this by typing “git” in the Windows search bar – if you see **“Git bash”** or some other form of Git, it is already installed and you can go straight to [installing Android Studio](#Building-APK-install-android-studio): ![Git_installed](../images/Building-the-App/001_check_git_installed.png) -2. If you don’t have Git installed, download and install the latest version for your system from the "Download" section on [**here**](https://git-scm.com/downloads). Any recent Git version should work, select the correct version according to your system, either Mac, Windows and Linux. +2. If you don’t have Git installed, download and install the latest version for your system from the "Download" section [**here**](https://git-scm.com/downloads). Any recent Git version should work, select the correct version according to your system, either Mac, Windows and Linux. **Note for Mac users:** the Git webpage will also guide you to install an additional program called "homebrew" to aid the installation. If you install Git via homebrew, there is no need to change any preferences. @@ -173,7 +173,7 @@ Once it's completed, press "Next" ![Installation_Complete](../images/Building-the-App/015_InstallLadybug.png) -In the last step, click on "Finished" to start Android Studio for the first time. +In the last step, click on "Finish" to start Android Studio for the first time. ![Completing_Android_Studio_Setup](../images/Building-the-App/016_InstallLadybug.png) @@ -306,7 +306,7 @@ This opens the following window, click to expand the dropdown called **Version C ![Version_control_Git](../images/Building-the-App/038_SettingsGit.png) -Check if **Android Studio** can automatically locate the correct **Path to Git executable** automatically by clicking the button "Test" (1): +Check if **Android Studio** can automatically locate the correct **Path to Git executable** by clicking the button "Test" (1): ![Git Executable](../images/Building-the-App/039_GitTest.png) @@ -374,7 +374,7 @@ If you have built AAPS before, do NOT create a new keystore but select your exis ```{admonition} WARNING! :class: warning -Make sure to note down for yourself where your keystore is stored. You will need it when you build the next AndroidAPS update! +Make sure to note down for yourself where your keystore is stored. You will need it when you build the next AAPS update! ``` * Now choose a simple password (and make a note of it), enter it in the password box (2), and confirm it (2). diff --git a/docs/EN/SettingUpAaps/ConfigBuilder.md b/docs/EN/SettingUpAaps/ConfigBuilder.md index 19826e5cf77f..2a8373904615 100644 --- a/docs/EN/SettingUpAaps/ConfigBuilder.md +++ b/docs/EN/SettingUpAaps/ConfigBuilder.md @@ -73,8 +73,8 @@ In **AAPS** 4 the insulin is no longer a plugin selected in **Configuration**. O The insulin editor lets you: -* give the profile an **Insulin nickname** so it is easy to recognise, -* set the **Peak** (time to maximum insulin activity, in minutes) and the **DIA** (Duration of Insulin Activity, in hours), either by typing the value or using the **–** / **+** buttons, +* give the insulin an **Insulin nickname** so it is easy to recognise, +* set the **Peak** (time to maximum insulin activity, in minutes) and the **DIA** (Duration of Insulin Action, in hours), either by typing the value or using the **–** / **+** buttons, * tap a **Load peak from** preset button — **Novorapid** (75 min), **Fiasp** (55 min) or **Lyumjev** (45 min) — to fill in the standard peak time for that insulin in one step. The allowed ranges are the same whatever insulin you use: @@ -282,7 +282,7 @@ When you select another pump, **AAPS** asks you to confirm the change: * [Equil 5.3](../CompatiblePumps/Equil5.3.md) * [Carelevo](../CompatiblePumps/CareLevo.md) * Virtual pump: open loop - **AAPS** suggestions only - * as you make you first steps with **AAPS**, during the first [objectives](../SettingUpAaps/CompletingTheObjectives.md) + * as you make your first steps with **AAPS**, during the first [objectives](../SettingUpAaps/CompletingTheObjectives.md) * for pump which doesn't have any driver yet (config-builder-wrong-pump-data)= @@ -302,7 +302,7 @@ To use the new pump, change the pump driver: select **Virtual pump**, confirm, t Select the type of sensitivity detection. For more details of different designs please [read on here](../DailyLifeWithAaps/SensitivityDetectionAndCob.md). This will analyze historical data on the go and make adjustments if it recognizes that you are reacting more sensitively (or conversely, more resistant) to insulin than usual. More details about how the sensitivity ratio itself is calculated can be found in [Key AAPS Features > Autosens](#Open-APS-features-autosens). -You can view your sensitivity on the main screen in an [additional graph](#AapsScreens-section-g-additional-graphs), by selecting SEN and watching the white line. Note, you need to be in [Objective 8](#objectives-objective8) in order to let Sensitivity Detection/[Autosens](#Open-APS-features-autosens) automatically adjust the amount of insulin delivered. Before reaching that objective, the Autosens percentage / the line in your graph is displayed for information only. +You can view your sensitivity on the main screen in an [additional graph](#AapsScreens-section-g-additional-graphs), by selecting SENS% and watching the white line. Note, you need to be in [Objective 8](#objectives-objective8) in order to let Sensitivity Detection/[Autosens](#Open-APS-features-autosens) automatically adjust the amount of insulin delivered. Before reaching that objective, the Autosens percentage / the line in your graph is displayed for information only. ### Absorption settings If you use Oref1 with **SMB** you must change **min_5m_carbimpact** to 8. The value is only used during gaps in **CGM** readings or when physical activity "uses up" all the blood glucose rise that would otherwise cause **AAPS** to decay COB. At times when [carb absorption](../DailyLifeWithAaps/CobCalculation.md) can't be dynamically worked out based on your blood's reactions it inserts a default decay to your carbs. Basically, it is a failsafe. diff --git a/docs/EN/SettingUpAaps/Nightscout.md b/docs/EN/SettingUpAaps/Nightscout.md index d50e6c4f9722..c0c7b832a4a2 100644 --- a/docs/EN/SettingUpAaps/Nightscout.md +++ b/docs/EN/SettingUpAaps/Nightscout.md @@ -29,7 +29,7 @@ Accepting data from Nightscout (profile changes, treatments, ...) is optional an #### Do not sync from Nightscout -Keeping all the "Receive ... from NS" options disabled makes sure no Nightscout change will be used by AAPS: +Keeping all the "Receive … from NS" options disabled makes sure no Nightscout change will be used by AAPS: ![Nightscout upload only](../images/preferences/settings_nsclient_sync.png) diff --git a/docs/EN/SettingUpAaps/Preferences.md b/docs/EN/SettingUpAaps/Preferences.md index 60c3296c59ed..e0b746674a16 100644 --- a/docs/EN/SettingUpAaps/Preferences.md +++ b/docs/EN/SettingUpAaps/Preferences.md @@ -137,7 +137,7 @@ If the app is protected, you must enter the password or use the phone's biometri - Safety limits are set based on the age you select in this setting. - If you start hitting these hard limits (like max bolus) it's time to move one step up. -- It's a bad idea to select higher than real age because it can lead to overdosing by entering the wrong value in the insulin dialog (by skipping the decimal dot, for example). +- It's a bad idea to select higher than real age because it can lead to overdosing by entering the wrong value in the insulin dialog (by skipping the decimal separator, for example). - If you want to know the actual numbers for these hard-coded safety limits, scroll to the algorithm feature you are using on [this page](../DailyLifeWithAaps/KeyAapsFeatures.md). (Preferences-maximum-bolus)= @@ -280,7 +280,7 @@ Depending on your settings in [Configuration > APS](../SettingUpAaps/ConfigBuild - [Advanced meal assist (OpenAPS AMA)](#Open-APS-features-advanced-meal-assist-ama) - state of the algorithm in 2017 - [Super Micro Bolus (OpenAPS SMB)](#Open-APS-features-super-micro-bolus-smb) - most recent algorithm recommended for beginners -As of [**AAPS** version 3.3](#version3300), [Dynamic ISF](../DailyLifeWithAaps/DynamicISF.md) feature has been moved as part of OpenAPS SMB. +As of [**AAPS** version 3.3](#version3300), the [Dynamic ISF](../DailyLifeWithAaps/DynamicISF.md) feature has been moved into OpenAPS SMB. ### OpenAPS AMA @@ -496,7 +496,7 @@ You can help develop **AAPS** further by sending crash reports to the developers **Unattended Settings Export**
By enabling this feature, you allow **AAPS** to execute settings exports without user intervention. For this the master password -is securely stored on your phone (only) at the next manually export. The stored password will be used for up to 4 weeks. +is securely stored on your phone (only) at the next manual export. The stored password will be used for up to 4 weeks. After 4 weeks you will be notified the password is about to expire. During a grace period of 1 week, the password can then be refreshed by manually exporting settings from the maintenance menu. diff --git a/docs/EN/SettingUpAaps/SettingUpTheReportingServer.md b/docs/EN/SettingUpAaps/SettingUpTheReportingServer.md index c3948d633c64..5f60315faec4 100644 --- a/docs/EN/SettingUpAaps/SettingUpTheReportingServer.md +++ b/docs/EN/SettingUpAaps/SettingUpTheReportingServer.md @@ -43,7 +43,7 @@ Once you have your Nightscout instance up and running, see [Nightscout configura Tidepool has been available in **AAPS** since version 3.2 which was released in late 2023. ```{admonition} Tidepool with **AAPS** is only for reporting -:class: danger +:class: danger As there is a delay of three hours between data income and data reporting when using **AAPS**, Tidepool is not suitable for sharing real-time information with caregivers. On the other hand, Tidepool can be a great solution for sharing reports with a patient's endocrinologist if Nightscout is not an accepted solution. ``` diff --git a/docs/EN/SettingUpAaps/SetupWizard.md b/docs/EN/SettingUpAaps/SetupWizard.md index 417b415e9497..141782ea8e7d 100644 --- a/docs/EN/SettingUpAaps/SetupWizard.md +++ b/docs/EN/SettingUpAaps/SetupWizard.md @@ -122,9 +122,9 @@ Follow these steps on Android 16; other versions will vary slightly from the pro ![settings_apps_1](../images/setup-wizard/apps_search_blue_13-14.png) ![settings_apps_2](../images/setup-wizard/apps_search_blue_12.png) ![settings_apps_3](../images/setup-wizard/apps_search_blue_15.png) - 1. On Android 12 Click on `Battery`, Android 13+ Click on `App battery usage`, + 1. On Android 12 click on `Battery`, on Android 13+ click on `App battery usage`. - ![settings_apps_16](../images/setup-wizard/app_bluetooth.png)) ![settings_apps_12](../images/setup-wizard/app_bluetooth_12.png) + ![settings_apps_16](../images/setup-wizard/app_bluetooth.png) ![settings_apps_12](../images/setup-wizard/app_bluetooth_12.png) 5. On Android 12+ select the `Unrestricted` option, on Android 15+ you need to expand the `Allow background usage` setting, click on the section highlighted in red to do this then follow step 6 to complete. @@ -454,7 +454,7 @@ When you select a real pump, **AAPS** asks for a confirmation, because it will c ![Confirmation when selecting a hardware pump](../images/setup-wizard/Wizard-Pump-Confirmation.png) -If the pump you select communicates over Bluetooth, **AAPS** asks for permission to connect to nearby devices once you finish the Wizard (see [Bluetooth permission](#bluetooth-permission)). +If the pump you select communicates over Bluetooth, **AAPS** asks for permission to connect to nearby devices once you finish the Wizard (see [Bluetooth permission](#setup-wizard-bluetooth-permission)). If you have already set up your profile and know how to connect your pump, feel free to connect it now. Otherwise leave it on **Virtual Pump** for the moment — you can change it anytime, or leave the Setup Wizard using the arrow in the top left corner and let **AAPS** first show you some blood glucose values. @@ -505,7 +505,7 @@ Press "**Open Objectives**": Here we start Objective 1, even if at the moment our setup is not completely ready to successfully complete this Objective. But this is the start. -Press the "**Start**" button next to "**1. Objective**": +Press the "**Start**" button of **Objective 1**: ![Objectives list](../images/setup-wizard/Wizard-Objectives-List.png) @@ -521,6 +521,7 @@ After pressing "**FINISH**" you arrive at the main screen of **AAPS**. A "**Noti If you accidentally leave the Setup Wizard at any point, you can either simply re-start the Wizard, or change the [configuration of the AAPS loop](../SettingUpAaps/ChangeAapsConfiguration.md) manually. +(setup-wizard-bluetooth-permission)= ## Bluetooth permission If you select a pump that connects over Bluetooth (for example **Omnipod Dash**), a banner reminds you that **AAPS** needs Bluetooth permission. You can press "**Dismiss**" for now — the permission is granted after you finish the Wizard: diff --git a/docs/EN/SettingUpAaps/YourAapsProfile.md b/docs/EN/SettingUpAaps/YourAapsProfile.md index bce711ece7a7..4222ef147043 100644 --- a/docs/EN/SettingUpAaps/YourAapsProfile.md +++ b/docs/EN/SettingUpAaps/YourAapsProfile.md @@ -140,9 +140,9 @@ From these examples you can see that the _smaller_ the **ISF** value, the less s ### Impact -A **lower / stronger ISF** (i.e. 40 instead of 50) means insulin drops your **BG** less per unit. This leads to a more aggressive / stronger correction from the loop with **more insulin**. If your **ISF** is too strong (small value), this can lead to low **BG**. +A **lower / stronger ISF** (e.g. 40 instead of 50) means insulin drops your **BG** less per unit. This leads to a more aggressive / stronger correction from the loop with **more insulin**. If your **ISF** is too strong (small value), this can lead to low **BG**. -A **higher / weaker ISF** (i.e. 45 instead of 35) means insulin drops your **BG** more per unit. This leads to a less aggressive / weaker correction from the loop with **less insulin**. If your **ISF** is too weak (large value), this can lead to high **BG**. +A **higher / weaker ISF** (e.g. 45 instead of 35) means insulin drops your **BG** more per unit. This leads to a less aggressive / weaker correction from the loop with **less insulin**. If your **ISF** is too weak (large value), this can lead to high **BG**. **Example:** * **BG** is 190 mg/dL (10.5 mmol/L) and target is 100 mg/dL (5.6 mmol/L). @@ -207,7 +207,7 @@ It is common to have different **ICR** at different times of day due to hormone > > BU factor 2,4 U / 12g ===> IC = 12g / 2,4 U = 5,0 g/U > -> Conversion tables are available online i.e. [here](https://www.mylife-diabetescare.com/files/media/03_Documents/11_Software/FAS/SOF_FAS_App_KI-Verha%CC%88ltnis_MSTR-DE-AT-CH.pdf). +> Conversion tables are available online, e.g. [here](https://www.mylife-diabetescare.com/files/media/03_Documents/11_Software/FAS/SOF_FAS_App_KI-Verha%CC%88ltnis_MSTR-DE-AT-CH.pdf). ### Impact @@ -307,7 +307,7 @@ Profile helper offers data sets from two different hospitals for children to fin 4. Change to the **Profile 2** tab. 5. Press **Profile type** and select "DPV Default profile". 6. Adjust DPV Default profile (based on another hospital data set) by entering kids age, TDD Total and percentage of basal. Note that the DPV data set provides **basal rates** only, so IC and ISF are shown as zero for this profile. -7. Open the **Comparation** tab. Comparison of the two adjusted profiles will be displayed (see screenshot below). +7. Open the **Comparison** tab. Comparison of the two adjusted profiles will be displayed (see screenshot below). 8. If you want to start tweaking your profile based on one of these suggestions, use the **Clone** button at the bottom of the comparison. ![Profile Helper Kids 2](../images/ProfileHelperKids2.png) @@ -357,6 +357,6 @@ You can also use the [Profile Helper](#aaps-screens-profile-helper) (menu ☰ 4. Change to the **Profile 2** tab. 5. In **Profile type**, select "Profile switch" to choose in the history of all your **Profile Switches**. 6. Choose the **Profile Switch** you want to compare to. -7. Open the **Comparation** tab. Comparison of the two profiles will be displayed (see screenshot below). +7. Open the **Comparison** tab. Comparison of the two profiles will be displayed (see screenshot below). ![Profile Helper 2](../images/ProfileHelper2.png) diff --git a/docs/EN/SupportingAaps/HowCanIHelp.md b/docs/EN/SupportingAaps/HowCanIHelp.md index f92face42417..5f535ea8d1f2 100644 --- a/docs/EN/SupportingAaps/HowCanIHelp.md +++ b/docs/EN/SupportingAaps/HowCanIHelp.md @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](StateOfTranslations.md). * If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/EN/SupportingAaps/HowToEditTheDocs.md b/docs/EN/SupportingAaps/HowToEditTheDocs.md index fc617b869e93..7871753aace7 100644 --- a/docs/EN/SupportingAaps/HowToEditTheDocs.md +++ b/docs/EN/SupportingAaps/HowToEditTheDocs.md @@ -3,7 +3,7 @@ **This description is just for editing the English documentation. All new information must be added in English first. If you want to translate to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs).** -For hints how to format text (headline, bold...) and set links please see the ["code syntax"](#code-syntax) section of this page. +For hints how to format text (headline, bold...) and set links please see the ["code syntax"](#edit-the-docs-code-syntax) section of this page. ## General @@ -35,11 +35,11 @@ For our example we are going to make an edit to AndroidAPSdocs. This can be done 3. One or the other of the options in Step 2 will create a new branch in YOUR repository where your edits will be saved. Make your edits to the file. -We are using markdown for the docs pages. The files have the suffix ".md". The Markdown specification is not fixed and we use at the moment the myst_parser for our markdown files. Take care to use the correct syntax as [described below](#code-syntax). +We are using markdown for the docs pages. The files have the suffix ".md". The Markdown specification is not fixed and we use at the moment the myst_parser for our markdown files. Take care to use the correct syntax as [described below](#edit-the-docs-code-syntax). ![Edit branch](../images/PR3.png) -4. You have been working in the "<>Edit file" tab. Select the "Preview changes" tab for a fresh look to make sure everything you changed looks like you meant it to (typos sic.). If you see a needed improvement, go back to the edit tab to make more improvements. +4. You have been working in the "<>Edit file" tab. Select the "Preview changes" tab for a fresh look to make sure everything you changed looks like you meant it to (check for typos). If you see a needed improvement, go back to the edit tab to make more improvements. ![preview mode](../images/PR5.png) @@ -55,7 +55,7 @@ We are using markdown for the docs pages. The files have the suffix ".md". The M ![PR tracking](../images/PR7.png) -PS: Your fork and branch will still be sitting on your own personal GitHub account. After you get a notification that your PR has been merged, you can delete your branch if you are done with it (Step 8's notification area will provide a link to delete the branch once it has been closed or merged). For future edits, if you follow this procedure the edits will always start with an updated version of the AndroidAPSdocs repositories. If you choose to use another method to start a PR request (e.g., editing starting from your forked repo's master branch as the starting point), you will need to ensure your repo is up-to-date by performing a "compare" first and merging in any updates that have happened since you last updated your fork. Since people tend to forget to update their repos, we recommend using the PR process outlined above until you get familiar with performing "compares". +PS: Your fork and branch will still be sitting on your own personal GitHub account. After you get a notification that your PR has been merged, you can delete your branch if you are done with it (Step 7's notification area will provide a link to delete the branch once it has been closed or merged). For future edits, if you follow this procedure the edits will always start with an updated version of the AndroidAPSdocs repositories. If you choose to use another method to start a PR (e.g., editing starting from your forked repo's master branch as the starting point), you will need to ensure your repo is up-to-date by performing a "compare" first and merging in any updates that have happened since you last updated your fork. Since people tend to forget to update their repos, we recommend using the PR process outlined above until you get familiar with performing "compares". (edit-the-docs-code-syntax)= ## Code syntax @@ -68,7 +68,7 @@ The writer only e.g. marks a headline as level 1 headline and the markdown proce The idea behind this is that * the writer should think about the text and not the formatting first, -* the markdown text is open for exchange between different markdown tools instead of e.g. proprietary tools like Microsoft Windows and +* the markdown text is open for exchange between different markdown tools instead of e.g. proprietary tools like Microsoft Word and * you can generate several output formats from one markdown file. Markdown is not a 100% fixed standard and we try to stay as near as possible to the standard, to @@ -225,7 +225,7 @@ This is a note. This is a warning. ``` ```` -```{admonition} Warning headline +```{admonition} Warning headline :class: warning This is a warning. ``` @@ -256,7 +256,7 @@ without it taking up too much space on the page. ## Tables -Avoid using tables with long texts as the contents is difficult to set in Markdown, they will usually not fit in a mobile phone screen width, and probably won't display the same after translation. +Avoid using tables with long texts as the content is difficult to set in Markdown, they will usually not fit in a mobile phone screen width, and probably won't display the same after translation. ## Style Guide @@ -274,9 +274,9 @@ Avoid using tables with long texts as the contents is difficult to set in Markdo Use plain English wherever possible. This helps non-native readers and also aids translation of AAPS documents into other languages. Write in a conversational way with the user, imagine you are sitting across the desk from the person you are writing for. Remember - most AAPS users do not have programming backgrounds. Diabetes itself also has a lot of jargon and abbreviations. Bear in mind that some people may be recently diagnosed, may not be as experienced as you with diabetes, or may have been given different diabetes training. If you use shorthand or an abbreviation, write it out in full the first time you use it, giving the abbreviation directly after it in brackets, like “super micro bolus (SMB)”. Also, link to the glossary. Technical terms which might not be familiar to the reader can be also be added in brackets. -Instead of: *“What causes high postprandial BG peaks in closed loop?"* +Instead of: *“What causes high postprandial BG peaks in closed loop?”* -Use: *“What causes a high BG peak **after lunch** (postprandial) in closed loop?"* +Use: *“What causes a high BG peak **after lunch** (postprandial) in closed loop?”* ##### Use plain words that everyone can understand @@ -309,7 +309,7 @@ Particularly if you record video or screenshots, make sure not to disclose your Commands are the fastest way to give instructions, but writers sometimes fear giving commands, writing “you should do this” instead of just “do this”. Perhaps people worry that commands sound too harsh. You can often solve this by putting the word 'please' in front. However, if something must be done, it is best not to say ‘please’ as it gives the reader the option to refuse. -Instead of: *“You should just think of it as a complete statement."* +Instead of: *“You should just think of it as a complete statement.”* Use: *“Think of it as a complete statement.”* @@ -324,7 +324,7 @@ Example of an **active verb**: Example of a **passive verb**: -- *“The insulin (subject) is delivered (verb) by the pump (object)”* +- *“The insulin (subject) is delivered (verb) by the pump (object).”* *“delivered”* is a passive verb here. The subject and object are switched around, compared to the active verb sentence. We have had to make the sentence longer by introducing “is” and “by the”. Also consider starting with the active verb. @@ -475,7 +475,7 @@ A how-to guide’s purpose is to help the already-competent user perform a parti - HOW-to -- narrator directly talks to the reader: In this tutorial **you** will +- narrator directly talks to the reader: In this guide **you** will - Future Tense -> to show the final target diff --git a/docs/EN/SupportingAaps/OpenHumans.md b/docs/EN/SupportingAaps/OpenHumans.md index a8e104f04a65..e46ab2d0c29b 100644 --- a/docs/EN/SupportingAaps/OpenHumans.md +++ b/docs/EN/SupportingAaps/OpenHumans.md @@ -2,7 +2,7 @@ ## Donate your data for science -You can help the community by donating your data to research projects! This helps scientists to pay it forward, develop new scientific ideas and broaden the open mind of open source closed loop systems. +You can help the community by donating your data to research projects! This helps scientists to pay it forward, develop new scientific ideas and make open source closed loop systems better known. AAPS is ready to synchronize your data with [Open Humans](https://www.openhumans.org), a platform allowing you to upload, connect, and store your personal data – such as genetics, activity and health data. You retain full control about what happens to your data and what projects you want to support by giving them access to your data. Depending on the project you have joined, data is evaluated and used by them in different ways and extent. @@ -77,7 +77,7 @@ The screenshot above is from an earlier **AAPS** version. In **AAPS** 4 the conf The 'OPEN' project brings together an international and intersectoral consortium of patient innovators, clinicians, social scientists, computer scientists and patient advocacy organizations in order to investigate various aspects of Do-it-Yourself Artificial Pancreas Systems (DIY APS) that are used by an increasing number of people with diabetes. For more details see their [website](https://www.open-diabetes.eu/). -September 2020 the 'OPEN' project launched a [survey](https://survey.open-diabetes.eu/) including the option to donate data you uploaded to Open Humans. A [tutorial](https://open-diabetes.eu/en/open-survey/survey-tutorials/) how to donate your data to the 'OPEN' project is available on their site and within the survey itself. +In September 2020 the 'OPEN' project launched a [survey](https://survey.open-diabetes.eu/) including the option to donate data you uploaded to Open Humans. A [tutorial](https://open-diabetes.eu/en/open-survey/survey-tutorials/) how to donate your data to the 'OPEN' project is available on their site and within the survey itself. ### [OpenAPS Data Commons](https://www.openhumans.org/activity/openaps-data-commons/) diff --git a/docs/EN/SupportingAaps/StateOfTranslations.md b/docs/EN/SupportingAaps/StateOfTranslations.md index 3f5c1ec4fab9..293148e0053b 100644 --- a/docs/EN/SupportingAaps/StateOfTranslations.md +++ b/docs/EN/SupportingAaps/StateOfTranslations.md @@ -1,9 +1,9 @@ -# state of translation for app and the documentation +# State of translation for the app and the documentation The state is once per hour updated and reflects only the state in Crowdin. ```{tip} -Be careful the percentage of proofreading must be lower than the percentage of translations but they decided to show it on top of the translations. +Be careful the percentage of proofreading is always lower than or equal to the percentage of translations but Crowdin shows it on top of the translations. It's better to look only at the percentage level of translations to see if work is to be done. ``` diff --git a/docs/EN/SupportingAaps/Translations.md b/docs/EN/SupportingAaps/Translations.md index 6f06b3b339d4..f26e2770c000 100644 --- a/docs/EN/SupportingAaps/Translations.md +++ b/docs/EN/SupportingAaps/Translations.md @@ -74,7 +74,7 @@ When a proofreader approves a translation it will be added to the next version o 1. the translation is proofread - 1. the sync run between Crowdin and Github finished (once an hour) which creates an PR for Github. + 1. the sync run between Crowdin and Github finished (once an hour) which creates a PR for GitHub. 1. the PR in Github was approved. @@ -85,11 +85,11 @@ In general this needs 1 - 3 days but might during holiday take a little bit long ```{admonition} Links are not translated anymore :class: note -Links are not translated anymore. In the past we had a topic here but this is gone as through migraton to Markdown and the myst_parser we explicitly create labels in the english text and propagate these labels under the hood to the languages. +Links are not translated anymore. In the past we had a topic here but this is gone as through migration to Markdown and the myst_parser we explicitly create labels in the english text and propagate these labels under the hood to the languages. ``` -You are translating the text which represents the link. Please you have to be careful **not** to remove the link which is represented by a pair of `<0>` tags or if their are more in one paragraph other numbers. +You are translating the text which represents the link. Please be careful **not** to remove the link, which is represented by a pair of `<0>` tags (or other numbers, if there are more links in one paragraph). It's the proofreaders job to have a special look on this! diff --git a/docs/EN/UsefulLinks/ClinicianGuideToAaps.md b/docs/EN/UsefulLinks/ClinicianGuideToAaps.md index 8ceb0c7a0c5f..5db2a2bcb067 100644 --- a/docs/EN/UsefulLinks/ClinicianGuideToAaps.md +++ b/docs/EN/UsefulLinks/ClinicianGuideToAaps.md @@ -21,7 +21,7 @@ Without a closed loop system, a person with diabetes gathers data from their pum With automated insulin delivery, the system does the same thing: it gathers data from the pump, CGM, and anywhere else information is logged (such as Nightscout), uses this information to do the maths and decide how much more or less insulin is needed (above or below the underlying basal rate), and uses temporary basal rates to make the necessary adjustments to keep or eventually bring BGs into target range. -If the device running AAPS breaks or goes out of range of the pump, once the latest temporary basal rate ends, the pump falls back to being a standard pump with the preprogrammed basals rates running. +If the device running AAPS breaks or goes out of range of the pump, once the latest temporary basal rate ends, the pump falls back to being a standard pump with the preprogrammed basal rates running. ## How data is gathered: @@ -37,7 +37,7 @@ It will also gather any information about boluses, carbohydrate consumption, and ## How does it know what to do? -The open source software is designed to make it easy for the device to do the work people used to do (in manual mode) to calculate how insulin delivery should be adjusted. It first collects data from all the supporting devices and from the cloud, prepares the data and runs the calculations, makes predictions of expected BG-levels during the next hours will be expected to do in different scenarios, and calculates the needed adjustments to keep or bring BG back into target range. Next it sends any necessary adjustments to the pump. Then it reads the data back, and does it over and over again. +The open source software is designed to make it easy for the device to do the work people used to do (in manual mode) to calculate how insulin delivery should be adjusted. It first collects data from all the supporting devices and from the cloud, prepares the data and runs the calculations, makes predictions of what BG levels are expected to do during the next hours in different scenarios, and calculates the needed adjustments to keep or bring BG back into target range. Next it sends any necessary adjustments to the pump. Then it reads the data back, and does it over and over again. As the most important input parameter is the blood glucose level coming from the CGM, it is important to have high-quality CGM data. @@ -68,7 +68,7 @@ In this example, BG is predicted to go low in the near-term, but is predicted to ### Scenario 3 - More insulin needed -In this example, a near-term prediction shows a dip below target. However, it is not predicted to be below the safety threshold. The eventual BG is above target. Therefore, AAPS will restrain from adding any insulin that would contribute to a near-term low (by adding insulin that would make the prediction go below threshold). It will then assess adding insulin to bring the lowest level of the eventual predicted BG down to target, once it is safe to do so. *(Depending on settings and the amount and timing of insulin required, this insulin may be delivered via temp basals or SMB's (super micro boluses) ).* +In this example, a near-term prediction shows a dip below target. However, it is not predicted to be below the safety threshold. The eventual BG is above target. Therefore, AAPS will refrain from adding any insulin that would contribute to a near-term low (by adding insulin that would make the prediction go below threshold). It will then assess adding insulin to bring the lowest level of the eventual predicted BG down to target, once it is safe to do so. *(Depending on settings and the amount and timing of insulin required, this insulin may be delivered via temp basals or SMBs (super micro boluses)).* ![Dosing scenario 3](../images/Dosing_scenario_3.jpg) @@ -84,13 +84,13 @@ As a clinician who may not have experience with AAPS or DIY closed loops, you ma The most important thing for patients to do is make one change at a time, and observe the impact for 2-3 days before choosing to change or modify another setting (unless it’s obviously a bad change that makes things worse, in which case they should revert immediately to the previous setting). The human tendency is to turn all the knobs and change everything at once; but if someone does so, then they may end up with further sub-optimal settings for the future, and find it hard to get back to a known good state. -One of the most powerful tools for making settings changes is an automated calculation tool for basal rates, ISF, and carb ratio. This is called “[Autotune](#autotune-how-autotune-calculates-adjustments)”. It is designed to be run independently/manually, and allow the data to guide you or your patient in making incremental changes to settings. It is best practice in the community to run (or review) Autotune reports first, prior to attempting to make manual adjustments to settings. Autotune is built into AAPS as a plugin (**Configuration** → **General** → **Autotune**); see [Autotune](../AdvancedOptions/Autotune.md). It can be run on demand or automatically. +One of the most powerful tools for making settings changes is an automated calculation tool for basal rates, ISF, and carb ratio. This is called “[Autotune](#autotune-how-autotune-calculates-adjustments)”. It is designed to allow the data to guide you or your patient in making incremental changes to settings. It is best practice in the community to run (or review) Autotune reports first, prior to attempting to make manual adjustments to settings. Autotune is built into AAPS as a plugin (**Configuration** → **General** → **Autotune**); see [Autotune](../AdvancedOptions/Autotune.md). It can be run on demand or automatically. As these parameters are a prerequisite both for standard pump insulin delivery and for closed loop insulin delivery, discussion of the autotune results and adjustment of these parameters would be the natural link to the clinician. Additionally, human behavior (learned from manual diabetes mode) often influences outcomes, even with a DIY closed loop. For example, if BG is predicted to go low and AAPS reduces insulin on the way down, only a small amount of carbs (e.g. 3-4g carbs) may be needed to bring BG up from 70 mg/dL (3.9 mmol/L). However, in many cases, someone may choose to treat with many more carbs (e.g. sticking to the 15 rule), which will cause a resulting faster spike both from the extra glucose and because insulin had been reduced in the timeframe leading up to the low. ## OpenAPS -**This guide was adopted from [The clinician's guide to OpenAPS](https://openaps.readthedocs.io/en/latest/docs/Resources/clinician-guide-to-OpenAPS.html).** +**This guide was adapted from [The clinician's guide to OpenAPS](https://openaps.readthedocs.io/en/latest/docs/Resources/clinician-guide-to-OpenAPS.html).** OpenAPS is a system developed to be run on a small portable computer (generally referred to as the "rig"). AAPS uses many of the techniques implemented in OpenAPS, and shares much of the logic and algorithms, which is why this guide is very similar to the original guide. Much of the information about OpenAPS can be easily adapted to AAPS, with the main difference being the hardware platform where each piece of software is run. diff --git a/docs/EN/UsefulLinks/DedicatedGoogleAccountForAaps.md b/docs/EN/UsefulLinks/DedicatedGoogleAccountForAaps.md index 693bb20915cd..ee477b8f2015 100644 --- a/docs/EN/UsefulLinks/DedicatedGoogleAccountForAaps.md +++ b/docs/EN/UsefulLinks/DedicatedGoogleAccountForAaps.md @@ -7,7 +7,7 @@ If you don't want to set up an **AAPS**-dedicated Gmail account, you can just go ```{admonition} Advantages of a dedicated Google account for AAPS :class: dropdown -- Dedicated Google drive space means you will not risk filling up your personal Google drive limit with **Export Preferences**. +- Dedicated Google Drive space means you will not risk filling up your personal Google Drive limit with **Export settings**. - Each version of **AAPS** (and supporting apps like xDrip, BYODA, etc) will be stored in one single place which is independent of your computer hardware. If your PC or phone is stolen/lost/broken you will still have access. - By harmonizing the setup, it will make online support simpler across users with similar folder structure. - Depending on the setup (see below), you will have a separate identity as an alias to communicate within the community which can protect your privacy.  @@ -45,14 +45,14 @@ Click [here]( ; ![](../images/Building-the-App/building_0002.png) +- Your existing “_Everyday_” Google account is ; ![](../images/Building-the-App/building_0002.png) - Your new “_AAPS_” Gmail account will be: ; ![](../images/Building-the-App/building_0003.png) -### Go to   +### Go to    If you are already logged into Google, this will direct you to your “Everyday” **My Account** page. -(1) Click on the top right of the page on your profile picture (in this case, a simple ![](../images/Building-the-App/building_0002.png) +(1) Click on the top right of the page on your profile picture (in this case, a simple ![](../images/Building-the-App/building_0002.png)) (2) select “_add another account_”. ![](../images/Building-the-App/building_0005.png) @@ -89,7 +89,7 @@ Gmail will display the account name. It will ask you to accept Gmail’s terms a ### Customize the new profile display -At this point you should be on Gmail’s MyAccount page showing your new **AAPS**-dedicated email account. The profile picture will be set by default to the first letter of your name. Change it to something unique to avoid confusion… in this example, Donald.Muck.AAPS has replaced ![](../images/Building-the-App/building_0002.png) with ![](../images/Building-the-App/building_0003.png) +At this point you should be on Gmail’s MyAccount page showing your new **AAPS**-dedicated email account. The profile picture will be set by default to the first letter of your name. Change it to something unique to avoid confusion… in this example, Donald.Muck.AAPS has replaced ![](../images/Building-the-App/building_0002.png) with ![](../images/Building-the-App/building_0003.png). ![](../images/Building-the-App/building_0007.png)\ ![](../images/Building-the-App/building_0008.png) @@ -103,7 +103,7 @@ This part can be a bit confusing, since you will have to switch back and forth b 2. Right click on your Browser logo in your taskbar 3. From the menu select “New Window”... and adjust it so it only takes the bottom half of the screen. -Open in each browser window. Make sure your personal account is on top and the new dedicated **AAPS** account is on the bottom, and is easily identifiable by the profile picture in the top right corner. (if needed you can always switch accounts by clicking on the profile picture and selecting the correct one. +Open in each browser window. Make sure your personal account is on top and the new dedicated **AAPS** account is on the bottom, and is easily identifiable by the profile picture in the top right corner. If needed, you can always switch accounts by clicking on the profile picture and selecting the correct one. ![](../images/Building-the-App/building_0009.png) diff --git a/docs/EN/UsefulLinks/FAQ.md b/docs/EN/UsefulLinks/FAQ.md index 0f237ec44d4c..7caf42df4a5e 100644 --- a/docs/EN/UsefulLinks/FAQ.md +++ b/docs/EN/UsefulLinks/FAQ.md @@ -149,7 +149,7 @@ You have to rework your old sports habits from pre-loop times. If you simply con So, you would have more carbohydrates on board, but at the same time the loop would counteract and release insulin. When looping you should try these steps: -* Make a [profile switch](#ProfileSwitch-change-percentage) < 100%: tap the profile name on the main screen, tap the round **▶** button, then set **Percentage** and **Duration**. +* Make a [profile switch](#ProfileSwitch-change-percentage) below 100%: tap the profile name on the main screen, tap the round **▶** button, then set **Percentage** and **Duration**. * Set an [activity temp target](#TempTargets-activity-temp-target) above your standard target. With a percentage below 100 % and a duration, the same **Activate** screen offers a **Temporary target / Activity** switch that starts both at once. * If you are using SMB make sure ["Enable SMB with high temp targets"](#Open-APS-features-enable-smb-with-high-temp-targets) and ["Enable SMB always"](#Open-APS-features-enable-smb-always) are disabled. @@ -166,7 +166,7 @@ You can remove the pump to be 'free', but you should tell AAPS so that the IOB c Drinking alcohol is risky in closed loop mode as the algorithm cannot predict the alcohol influenced BG correctly. You have to check out your own method for treating this using the following functions in AAPS: * Deactivating closed loop mode and treating the diabetes manually or -* setting high temp targets and deactivating UAM to avoid the loop increasing IOB due to an unattended meal or +* setting high temp targets and deactivating UAM to avoid the loop increasing IOB due to an unannounced meal or * do a [profile switch](#ProfileSwitch-change-percentage) to noticeably less than 100% The *Alcohol* [scene](#scenes) template is a starting point you can adapt to your own method. @@ -327,9 +327,9 @@ You can also change when the alert is raised: press the **Settings** (gear) icon (FAQ-link-unresponsive)= #### My link/pump/pod is unresponsive (RL/OL/EmaLink…) -With some phones, there are Bluetooth disconnects from the Links (RL/OL/EmaL...). +With some phones, there are Bluetooth disconnects from the Links (RL/OL/EmaLink). -Some also have non responsive Links (AAPS says that they are connected but the Links can't reach or command the pump.) +Some also have non responsive Links (AAPS says that they are connected but the Links can't reach or command the pump). First try the **Reset RileyLink** button on the pump screen (see your pump's page: [Medtronic](#MedtronicPump-what-to-do-if-i-loose-connection-to-rileylink-and-or-pump), [Omnipod Eros](#OmnipodEros-reset-rileylink-config-notes)). If this does not help, the easiest way to get all these parts working together is: @@ -379,5 +379,5 @@ The Pod state is included in the exported settings, so an active Pod can be move Read these sections first: -* [Export and import settings](#omnipod-dash-export-import) on the Omnipod DASH page, and [Tubeless pumps](#ExportImportSettings-tubeless-pumps): on the new phone, tick **Also replace pump settings** and use a file exported during the Pod you are wearing now, +* [Export and import settings](#omnipod-dash-export-import) on the Omnipod DASH page, and [Tubeless pumps](#ExportImportSettings-tubeless-pumps): on the new phone, tick **Also replace pump settings** and use a file exported while wearing your current Pod, * [Discarding a pod](#omnipod-dash-discard-pod), to remove the Pod from the old phone afterwards. Keep the old phone in airplane mode until the Pod is discarded, so that the two phones never talk to the Pod at the same time. diff --git a/docs/EN/UsefulLinks/Glossary.md b/docs/EN/UsefulLinks/Glossary.md index 08518975ce82..3efbab9ff6e5 100644 --- a/docs/EN/UsefulLinks/Glossary.md +++ b/docs/EN/UsefulLinks/Glossary.md @@ -21,7 +21,7 @@ __Android Auto__ = a system used to host certain functions of an Android smartph __APK__ = Android application Package. A software installation file. Further info → [Wiki - 'Building APK'](../SettingUpAaps/BuildingAaps.md). -__Autosens__ = calculation of sensitivity to insulin between a period of a 24 and 8 hour window etc. Further info → [DIABETTECH - __Autosens__](https://www.diabettech.com/what-conclusions-can-we-draw-when-investigating-insulin-sensitivity-using-the-autosens-function-within-openaps-an-n1-study/). +__Autosens__ = calculation of sensitivity to insulin over a 24-hour and an 8-hour window etc. Further info → [DIABETTECH - __Autosens__](https://www.diabettech.com/what-conclusions-can-we-draw-when-investigating-insulin-sensitivity-using-the-autosens-function-within-openaps-an-n1-study/). __Azure__ = cloud computing platform to host __Nightscout__ web app → see also __Nightscout__. @@ -49,7 +49,7 @@ __CAN__ = status light for overdue cannula change, shown in the status row of __ __CGM__ = Continuous Glucose Monitor → see also __FGM__. -__Closed Loop__ = a closed loop system which makes automatic adjustments to the user’s basal delivery based on an __AAPS’s__ algorithm and the user’s __Profile__ settings without requiring the user’s-approval. Further info → Wiki - 'closed loop' and see also __HCL__ / __FCL__. +__Closed Loop__ = a closed loop system which makes automatic adjustments to the user’s basal delivery based on an __AAPS’s__ algorithm and the user’s __Profile__ settings without requiring the user’s approval. Further info → [Wiki - 'closed loop'](#KeyAapsFeatures-ClosedLoop) and see also __HCL__ / __FCL__. __COB__ = Carbs On Board. This is the amount of carbohydrates currently available for the user's digestion → see also IOB. @@ -59,7 +59,7 @@ i.e. how much does the user’s __BG__ increase for 1g of carbs absorbed. __DIA__ = Duration of Insulin Action. Further info → [Wiki - 'DIA'](#Config-Builder-insulin-dia) and see also → [DIABETTECH - 'DIA'](https://www.diabettech.com/why-we-are-regularly-wrong-in-the-duration-of-insulin-action-dia-times-we-use-and-why-it-matters/). -__DST__ = Daylight Savings Time. See [Wiki - Timezone Change and Daylight Saving](../DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md). +__DST__ = Daylight Saving Time. See [Wiki - Timezone Change and Daylight Saving](../DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md). __Dynamic ISF (or DynISF)__ = a feature within **AAPS** that adapts the insulin sensitivity factor (**ISF**) dynamically based on the user’s **TDD** and **BG**. @@ -67,15 +67,15 @@ __eCarbs__ = extended Carbs. Carbs split up over several hours (e.g. to cover fat/protein), which lets __AAPS__ spread the insulin like an extended bolus. Further info → [Wiki - 'Extended Carbs'](../DailyLifeWithAaps/ExtendedCarbs.md) __FCL__ = Full Closed Loop. -A loop which needs no mealtime input from the user: no carb counting and no meal bolus. Further info → Wiki - 'full closed loop' and see also __HCL__. +A loop which needs no mealtime input from the user: no carb counting and no meal bolus. Further info → [Wiki - 'full closed loop'](../AdvancedOptions/FullClosedLoop.md) and see also __HCL__. __FGM__ = Flash Glucose Monitor such as the Abbott Freestyle Libre. - Further info → Wiki - 'BG source' and see also 'CGM'. + Further info → [Wiki - 'BG source'](#Config-Builder-bg-source) and see also 'CGM'. -__git__ = a tool used store and download the __AAPS’__ source code. +__git__ = a tool used to store and download the __AAPS’__ source code. __GitHub__ = a web-based service that hosts the __AAPS__ source code and its version control (tracking changes in files and coordinating work on them, especially for teams), and can also build the app. -It is also necessary for __APK__ updates. Further info → Wiki - 'update APK'. +It is also necessary for __APK__ updates. Further info → [Wiki - 'update APK'](../Maintenance/UpdateToNewVersion.md). __Glimp__ = an app to collect values from Freestyle Libre. @@ -100,7 +100,7 @@ __Log files__ = __AAPS’__ records of the user's actions (useful for troublesho __maxIOB__ = maximum total IOB. This is a safety feature and prevents __AAPS__ delivering insulin over the user’s settings. Further info → [Wiki - 'Maximum total IOB OpenAPS can’t go over'](#Open-APS-features-maximum-total-iob-openaps-cant-go-over). -__min_5m_carbimpact__ = safety feature that is a calculation of default carb decay when carb absorption cannot be determined based on the user’s blood’s reactions. Further info → [Wiki - 'Preferences'](#Preferences-min_5m_carbimpact). +__min_5m_carbimpact__ = safety feature that is a calculation of default carb decay when carb absorption cannot be determined based on the user’s blood’s reactions. Further info → [Wiki - 'min_5m_carbimpact'](#Preferences-min_5m_carbimpact). __Nightscout__ = open source project to access and report __CGM__ data. The central data hub for the user’s __AAPS__ data and can generate reports to view the user’s historical __Nightscout__ data, such as expected HbA1c, time in range or search for patterns in the data via percentile chart etc. @@ -115,7 +115,7 @@ __OpenAPS__ = Open Artificial Pancreas System, the predecessor project and basis __Open Loop system__ = an __AAPS__ feature that will recommend adjustments and which must be performed manually by the user on __AAPS__. Further info → [Wiki - 'Open Loop'](#KeyAapsFeatures-OpenLoop). -__Oref0 / Oref1__ = sensitivity detection and "reference design implementation version 0/1". It is the key algorithm behind OpenAPS Wiki - sensitivity detection. +__Oref0 / Oref1__ = sensitivity detection and "reference design implementation version 0/1". It is the key algorithm behind OpenAPS. Further info → [Wiki - 'sensitivity detection'](../DailyLifeWithAaps/SensitivityDetectionAndCob.md). __OS-AID__ = Open-Source Automated Insulin Delivery. An __AID__ system built from open-source software, such as __AAPS__, __OpenAPS__, Loop or Trio. These systems are not formally approved by health bodies (FDA, NHS etc.) → see also __AID__. @@ -154,16 +154,16 @@ __Super bolus__ = shift of basal to bolus insulin for faster __BG__ adjustment. __TBB__ = total base basal (sum of basal rate within 24 hours) → see also __TBR__ / __TDD__. -__TBR__ = temporary basal rate→ see also __TBB__ / __TDD__. +__TBR__ = temporary basal rate → see also __TBB__ / __TDD__. __TDD__ = total daily dose (bolus + basal per day) → see also __TBB__ / __TBR__. -__TT__ = temporary target temporary increase/decrease of the user’s __BG__ target (range) e.g. for eating or sport activities. Further info → [Wiki - 'temp targets'](../DailyLifeWithAaps/TempTargets.md). +__TT__ = temporary target: temporary increase/decrease of the user’s __BG__ target (range) e.g. for eating or sport activities. Further info → [Wiki - 'temp targets'](../DailyLifeWithAaps/TempTargets.md). __UAM__ = unannounced meals. Detection of significant increase in __BG__ levels due to meals, adrenaline or other influences and attempt to adjust this. Further info → [Wiki - 'UAM'](#enable-uam) and see also __SMB__. -__Virtual pump__ = an __AAPS__ feature which allows the user to try __AAPS’__ functions or for PWD using a pump model with no __AAPS__ driver for looping → see also __Open Loop__. +__Virtual pump__ = an __AAPS__ feature which allows the user to try __AAPS’__ functions, or lets PWD whose pump model has no __AAPS__ driver use __AAPS__ as an open loop → see also __Open Loop__. __Wallpaper__ = __AAPS__ background image see phones page. diff --git a/docs/EN/WearOS/BuildingAapsWearOS.md b/docs/EN/WearOS/BuildingAapsWearOS.md index 0227ef2f0e84..dbdbe416bbb9 100644 --- a/docs/EN/WearOS/BuildingAapsWearOS.md +++ b/docs/EN/WearOS/BuildingAapsWearOS.md @@ -78,7 +78,7 @@ Next: install the Wear apk on the watch, see [Set up AAPS on your Wear OS watch] In the process of building the full **AAPS** app (and in fact any signed app), Android Studio generates a .json file in the same folder. This then causes errors with [uncommitted changes](#troubleshooting_androidstudio-uncommitted-changes) when you try to build the next signed app, like the **AAPS** wear app. The quickest way to resolve this is to navigate to the folder where the full AAPS app has been built, your folder is probably something like: -`C:\Users\Your Name\AndroidStudioProjects\AndroidAPS\app\aapsclient\release. ` +`C:\Users\Your Name\AndroidStudioProjects\AndroidAPS\app\full\release. ` Either delete, or move the unneeded .json file out of the folder. Then try to build the **AAPS** wear app again. If that doesn't work, the more detailed [troubleshooting guide](../GettingHelp/TroubleshootingAndroidStudio.md) will help you to identify the specific file causing the issue, which could also be your keystore file. diff --git a/docs/EN/WearOS/WearOsSmartwatch.md b/docs/EN/WearOS/WearOsSmartwatch.md index 2bb285412031..cee645546d3f 100644 --- a/docs/EN/WearOS/WearOsSmartwatch.md +++ b/docs/EN/WearOS/WearOsSmartwatch.md @@ -91,7 +91,7 @@ Install the **AAPS Wear** apk using [Wear Installer 2](https://youtu.be/abgN4jQq ```{admonition} Wear OS 5 :class: warning -On Wear OS 5 the AAPS watchface has to be selected with Wear Installer 2 right after installing the Wear app: the installer offers the **AAPS (Custom)** watchface at the end of the installation. If you accidentally switch to another watchface, repeat the installation. Changing the watchface settings (Dark, Watchdivider, etc.) may not be possible. +On Wear OS 5 the AAPS watchface has to be selected with Wear Installer 2 right after installing the Wear app: the installer offers the **AAPS (Custom)** watchface at the end of the installation. If you accidentally switch to another watchface, repeat the installation. Changing the watchface settings (Dark, Matching divider, etc.) may not be possible. If the classic watchface currently works for you, **disable automatic watch updates**: the next firmware update is likely to break it. If you update to Wear OS 6 anyway, read the section above: **AAPS** then installs its own watchface in the new format. ``` @@ -115,13 +115,13 @@ Here are basic setup guides for the [Galaxy Watch 5](https://www.youtube.com/wat ## Basic smartwatch familiarity After basic setup of your watch according to the video above, go to the playstore on the phone and download the following apps: -"Galaxy Wearable" “Samsung” and either “Easy Fire tools” or "Wear Installer 2". +"Galaxy Wearable", “Samsung” and either “Easy Fire tools” or "Wear Installer 2". There are plenty of 3rd party YouTube videos which will help you with getting familiar with your new smartwatch, for example: [https://www.youtube.com/watch?v=tSVkqWNmO2c](https://www.youtube.com/watch?v=tSVkqWNmO2c) -The app “Galaxy Wearable” also has an instruction manual section in it. Open galaxy wearable on the phone, search for the watch, attempt to pair the watch with the phone. Depending on your version, this may prompt you to install a further 3rd app “galaxy watch 4 plugin” from the playstore (takes a while to download). Install this on the phone, and then attempt to pair the watch and phone again in the wearable app. Go through a series of menus and tick various preferences. +The app “Galaxy Wearable” also has an instruction manual section in it. Open galaxy wearable on the phone, search for the watch, attempt to pair the watch with the phone. Depending on your version, this may prompt you to install one more app, “galaxy watch 4 plugin”, from the playstore (takes a while to download). Install this on the phone, and then attempt to pair the watch and phone again in the wearable app. Go through a series of menus and tick various preferences. ## Setting up a Samsung account @@ -280,8 +280,8 @@ The final step is to configure **AAPS** on the phone to interact with **Wear.apk To bolus or take other actions from the watch, also turn on **Wear control** in [Settings > Wear](#preferences-wear). -To change to a different **AAPS** watchface, press on the home screen of the -watch and it will come to “customise”. Then swipe right until you get to all the **AAPS** faces. +To change to a different **AAPS** watchface, long-press the watchface on the home screen of the +watch and tap **Customize**. Then swipe right until you get to all the **AAPS** faces. If the **AAPS** Wear.apk has been successfully side-loaded onto the smartwatch, it will look like this: @@ -359,7 +359,7 @@ F - phone battery G - basal rate (shown in U/h during standard rate and in % during TBR) -H - BGI (blood glucose interaction) +H - BGI (blood glucose impact) -> the degree to which BG “should” be rising or falling based on insulin activity alone. I - carbs (carbs on board | e-carbs in the future) diff --git a/docs/EN/index.md b/docs/EN/index.md index fb5ed06158b3..9785ae79d298 100644 --- a/docs/EN/index.md +++ b/docs/EN/index.md @@ -5,7 +5,7 @@ ```{admonition} Latest Release :class: note - 31 October 2026 : Version 4.0.0 is out. Check the [Release Notes](#latestrelease) to see what's new and follow the instructions in the [update manual](./Maintenance/UpdateToNewVersion.md) to update. +31 October 2026: Version 4.0.0 is out. Check the [Release Notes](#latestrelease) to see what's new and follow the instructions in the [update manual](./Maintenance/UpdateToNewVersion.md) to update. ``` @@ -17,7 +17,7 @@ This documentation explains how to set up and use **AAPS**. You can navigate thr Section **1) Getting Started**, the [Introduction](Getting-Started/Introduction.md) explains the general concept of what an artificial pancreas system (APS) is designed to do. It outlines the background of looping in general, why **AAPS** was developed, compares **AAPS** to other systems, and addresses safety. It gives suggestions about how to talk to your clinical team about **AAPS**, explains why you need to build the **AAPS** app yourself rather than just downloading it, and gives an overview of the typical connectivity of an **AAPS** system. It also addresses accessibility, and who is likely to benefit from **AAPS**. -[Preparing for AAPS](./Getting-Started/PreparingForAaps.md) gives more detail about safety considerations, and the phones, CGMs (Continuous Glucose Monitors) and insulin pumps which are compatible with **AAPS**. It gives an overview of the process you will go through, and provides an approximate timeline for gaining full functionality of **AAPS**. This section gets you technically prepared to assemble your **AAPS** setup as quickly and efficiently as possible. The subsection [CGM Configuration](./Getting-Started/CompatiblesCgms.md) explains how to optimize your CGM setup and which smoothing options are best. +[Preparing for AAPS](./Getting-Started/PreparingForAaps.md) gives more detail about safety considerations, and the phones, CGMs (Continuous Glucose Monitors) and insulin pumps which are compatible with **AAPS**. It gives an overview of the process you will go through, and provides an approximate timeline for gaining full functionality of **AAPS**. This section gets you technically prepared to assemble your **AAPS** setup as quickly and efficiently as possible. The subsection [Compatible CGMs](./Getting-Started/CompatiblesCgms.md) explains how to optimize your CGM setup and which smoothing options are best. Now that you have a solid understanding of the process, you can start assembling your **AAPS** loop. @@ -42,7 +42,7 @@ Section **9) [Help & Troubleshooting](GettingHelp/WhereCanIGetHelp.md)** should Section **10)** covers **[Advanced AAPS options](./AdvancedOptions/FullClosedLoop.md)** such as how to progress from using **AAPS** for hybrid-closed looping (bolusing for meals _etc._) to full closed looping (no bolusing), how to [tune your profile](./GettingHelp/ProfileTuning.md) and use Autotune, and details development and engineering modes. Most users get on just fine with the main or "Master" **AAPS** version without looking into these options, this section is for users who already have good control and are looking to further improve their setup. -In section **11) [How to support AAPS](SupportingAaps/HowToEditTheDocs.md)** we provide information so that you can support this project. You can donate money, equipment or expertise. You can suggest/make changes to the documentation yourself, help with [translation of the documentation](SupportingAaps/Translations) and provide your data through the Open Humans project. +In section **11) [How to support AAPS](SupportingAaps/HowCanIHelp.md)** we provide information so that you can support this project. You can donate money, equipment or expertise. You can suggest/make changes to the documentation yourself, help with [translation of the documentation](SupportingAaps/Translations.md) and provide your data through the Open Humans project. Section **12) Resources**, contains archived or additional documentation, including a subsection for [clinicians](UsefulLinks/ClinicianGuideToAaps.md) who have expressed interest in open source artificial pancreas technology such as **AAPS**, or for patients who want to share such information with their clinicians, this topic is also addressed in the introduction. More diabetes and looping references and resources are also contained in this section. It includes the [Glossary](./UsefulLinks/Glossary.md), a list of the acronyms (or short-term names) used throughout **AAPS**. This is where to go to find out what the terms ISF or TT, stand for, for example.