diff --git a/docs/CROWDIN/cs/AdvancedOptions/Autotune.md b/docs/CROWDIN/cs/AdvancedOptions/Autotune.md
index 020c37f03b35..4da78106a8e2 100644
--- a/docs/CROWDIN/cs/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/cs/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/cs/AdvancedOptions/DevBranch.md b/docs/CROWDIN/cs/AdvancedOptions/DevBranch.md
index babbac27fbec..e29bb635adac 100644
--- a/docs/CROWDIN/cs/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/cs/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/cs/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/cs/AdvancedOptions/FullClosedLoop.md
index 05e8f60b62ad..d5859e30aa36 100644
--- a/docs/CROWDIN/cs/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/cs/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/cs/CompatibleCgms/Juggluco.md b/docs/CROWDIN/cs/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/cs/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/cs/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/cs/CompatibleCgms/Libre3.md b/docs/CROWDIN/cs/CompatibleCgms/Libre3.md
index 1cff229b49d1..fd89586cc699 100644
--- a/docs/CROWDIN/cs/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/cs/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS (for looping only)
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- In xDrip+ select "Libre2 (patched App)" as data source
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/cs/CompatiblePhones/Jelly.md b/docs/CROWDIN/cs/CompatiblePhones/Jelly.md
index 423834248391..5aa96aa3451d 100644
--- a/docs/CROWDIN/cs/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/cs/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/cs/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/cs/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 23d86a8d37f5..96f8ef7d4513 100644
--- a/docs/CROWDIN/cs/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/cs/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ Combo lze provozovat přes Bluetooth v režimu _vzdáleného terminálu_ nebo v
(Uživatel na to nemá vliv; ovladač plně rozhoduje sám, jaký režim použije. To je pouze poznámka pro uživatele, aby věděli, proč jsou v tomto poli někdy vidět snímky Comba.)
-Zcela dole je tlačítko "Obnovit". To spustí okamžitou aktualizaci stavu pumpy. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+Zcela dole je tlačítko "Obnovit". To spustí okamžitou aktualizaci stavu pumpy. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Nastavení
@@ -176,8 +176,8 @@ Pro ovladač Combo jsou k dispozici tyto předvolby (položky jsou uvedeny od sh
1. _Párování_: Toto je tlačítko, kterým spustíte párování s pumpou Combo. Je zakázáno, pokud je již pumpa spárována.
2. _Zrušit párování_: Zruší párování s již připojenou pumpou Combo; pravý opak položky č. 1. Je zakázáno, pokud není žádná pumpa spárovaná.
3. _Doba hledání (v sekundách)_: Při párování ovladač nastaví telefon, aby byl zjistitelný pumpou. Toto určuje, jak dlouho je zjistitelnost spuštěná. Ve výchozím nastavení je vybráno maximum (300 sekund = 5 minut). Android neumožňuje spustit tuto funkci na dobu neurčitou, takže je nutné zvolit dobu trvání.
-4. _Automaticky zjistit a zadat výměnu inzulínu_: Pokud je povoleno, akce "Výměna zásobníku", kterou uživatel obvykle provádí prostřednictvím tlačítka "prime/plnění" na záložce Akce, je prováděna automaticky. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Automaticky zjistit a zadat výměnu baterie_: Pokud je povoleno, akce "Výměna baterie", kterou uživatel obvykle provádí prostřednictvím tlačítka "Výměna baterie v pumpe" na záložce Akce, je prováděna automaticky. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Automaticky zjistit a zadat výměnu inzulínu_: Pokud je povoleno, akce "Výměna zásobníku", kterou uživatel obvykle provádí prostřednictvím tlačítka "prime/plnění" na záložce Akce, je prováděna automaticky. This is explained [in further detail below](#combov2-autodetections).
+5. _Automaticky zjistit a zadat výměnu baterie_: Pokud je povoleno, akce "Výměna baterie", kterou uživatel obvykle provádí prostřednictvím tlačítka "Výměna baterie v pumpe" na záložce Akce, je prováděna automaticky. This is explained [in further detail below](#combov2-autodetections).
6. _Povolit detailní logování Combo_: Toto značně rozšiřuje množství logovaných informací prováděné ovladačem. **UPOZORNĚNÍ**: Nezapínejte, pokud o to nepožádal vývojář. V opačném případě to může do protokolů AndroidAPS přidat mnoho šumu a snížit jejich užitečnost.
Většina uživatelů používá pouze první dvě položky, _Párování_ a _Zrušit párování_.
@@ -202,7 +202,7 @@ Některá varování jsou automaticky zamítnuta ovladačem. Jedná se o:
- W2 "Battery low" : ovladač to změní v upozornění "Nízký stav baterie", které je zobrazeno na hlavní kartě AAPS
- W3, W6, W7, W8 : tato varování jsou čistě informační pro uživatele, takže je pro ovladač může bezpečně automaticky zamítnout
-Žádné další výstrahy _nejsou_ automaticky zamítnuty. Také chyby _nikdy nejsou_ automaticky zamítnuty. Oboje jsou zpracovány stejným způsobem: ovladač vytvoří výstražné dialogové okno nad rozhraním AAPS a přeruší vykonávání všech probíhajících příkazů. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). Tento stav neumožňuje provádění jakýchkoli příkazů. Uživatel musí vyřešit chybu na pumpě; například chyba okluze může vyžadovat výměnu kanyly. Jakmile uživatel vyřeší chybu, běžný provoz může být obnoven stisknutím tlačítka "Obnovit" na záložce Accu-Chek Combo. Ovladač se pak spojí s pumpou Combo, zaktualizuje její stav a zkontroluje, zda není na obrazovce stále zobrazena chyba atd. Ovladač také po chvíli automaticky aktualizuje stav pumpy, takže ruční stisknutí tohoto tlačítka není povinné.
+Žádné další výstrahy _nejsou_ automaticky zamítnuty. Také chyby _nikdy nejsou_ automaticky zamítnuty. Oboje jsou zpracovány stejným způsobem: ovladač vytvoří výstražné dialogové okno nad rozhraním AAPS a přeruší vykonávání všech probíhajících příkazů. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). Tento stav neumožňuje provádění jakýchkoli příkazů. Uživatel musí vyřešit chybu na pumpě; například chyba okluze může vyžadovat výměnu kanyly. Jakmile uživatel vyřeší chybu, běžný provoz může být obnoven stisknutím tlačítka "Obnovit" na záložce Accu-Chek Combo. Ovladač se pak spojí s pumpou Combo, zaktualizuje její stav a zkontroluje, zda není na obrazovce stále zobrazena chyba atd. Ovladač také po chvíli automaticky aktualizuje stav pumpy, takže ruční stisknutí tohoto tlačítka není povinné.
Zvláštní případ je dávkování bolusů. To probíhá v příkazovém režimu, který v průběhu podávání bolusu nereportuje, že se objevilo varování. Z toho důvodu ovladač nemůže automaticky zrušit _varování_ během podávání bolusu. To bohužel znamená, že pumpa bude v takovém případě pípat, dokud nebude ukončeno podávání bolusu. Nejčastější výstraha v průběhu bolusu je obvykle W1 "Reservoir low". V průběhu podávání bolusu **nevypínejte** upozornění přímo na pumpě. Riskujete tak přerušení podávání bolusu. Ovladač se o varování postará automaticky po dokončení bolusu.
@@ -215,8 +215,8 @@ Upozornění, která se objeví, zatímco ovladač není spojený s pumpou Combo
* Mějte na paměti, že se nejedná o produkt. Obzvlášť na začátku uživatel potřebuje monitorovat a pochopit systém, jeho limity a jeho možná selhání. Je důrazně doporučováno nepoužívat tento systém, pokud ho uživatel není schopen plně pochopit.
* Kvůli způsobu, jakým funguje vzdálené ovládání Comba, jsou některé operace (především nastavení bazálního profilu) jsou ve srovnání s jinými pumpami pomalejší. Jde o nešťastné omezení pump Combo, které není možné překonat.
* Neset nebo nezrušujte TBR na pumpě. Smyčka předpokládá, že řídí dočasné bazály a bez splnění tohoto předpokladu nemůže spolehlivě fungovat. Důvodem je, že nelze určit čas spuštění dočasného bazálu zadaného uživatelem přímo na pumpě.
-* Jestliže probíhá komunikace mezi AAPS a pumpou (na pumpě je během připojení zobrazeno logo Bluetooth), nesmíte na pumpě mačkat žádná tlačítka. Došlo by k přerušení Bluetooth připojení. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Nesmíte stisknout žádná tlačítka, pokud pumpa posílá bolus. Zejména se nepokoučejte zavřít jakákoli upozornění stiskem tlačítek. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Jestliže probíhá komunikace mezi AAPS a pumpou (na pumpě je během připojení zobrazeno logo Bluetooth), nesmíte na pumpě mačkat žádná tlačítka. Došlo by k přerušení Bluetooth připojení. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Nesmíte stisknout žádná tlačítka, pokud pumpa posílá bolus. Zejména se nepokoučejte zavřít jakákoli upozornění stiskem tlačítek. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist pro případ, kdy nelze navázat spojení s pumpou Combo
diff --git a/docs/CROWDIN/cs/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/cs/CompatiblePumps/DanaRS-Insulin-Pump.md
index 838c7c3edcd4..22a97d41ca29 100644
--- a/docs/CROWDIN/cs/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/cs/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Stiskněte OK pro zadání starého hesla.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ Pokud měníte telefon za nový, je nezbytné, abyste provedli následující kr
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Někdy může být nutné vymazat informace o párování v AAPS delším podržením ikony BT na kartě Dana-i/RS.
## Cestování mezi časovými pásmy s pumpou Dana RS
diff --git a/docs/CROWDIN/cs/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/cs/CompatiblePumps/MedtronicPump.md
index bfe563d7c00e..95c73d560dbc 100644
--- a/docs/CROWDIN/cs/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/cs/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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):
- pro USA & Kanadu je frekvence 916 MHz
- pro zbytek světa je frekvence 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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Historie pumpy
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Historie pumpy se načítá každých 5 minut a ukládá se místně. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## Stav RL (Stav RileyLink)
diff --git a/docs/CROWDIN/cs/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/cs/CompatiblePumps/MedtrumNano.md
index bef2a71b2abb..de5bb7183e24 100644
--- a/docs/CROWDIN/cs/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/cs/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Výchozí: 25 U.***
-Tímto nastavením se mění maximální množství inzulinu, které může být dodáno během jedné hodiny. Pokud je tento limit překročen, patch bude pozastaven a spustí se alarm. Alarm lze resetovat stisknutím tlačítka reset na obrazovce s přehledem, viz [Reset alarmů](#reset-alarms).
+Tímto nastavením se mění maximální množství inzulinu, které může být dodáno během jedné hodiny. Pokud je tento limit překročen, patch bude pozastaven a spustí se alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Nastavte na rozumnou hodnotu dle svých potřeb.
@@ -128,7 +128,7 @@ Nastavte na rozumnou hodnotu dle svých potřeb.
***Výchozí: 80 U.***
-Tímto nastavením se mění maximální množství inzulinu, které může být dodáno během jednoho dne. Pokud je tento limit překročen, patch bude pozastaven a spustí se alarm. Alarm lze resetovat stisknutím tlačítka reset na obrazovce s přehledem, viz [Reset alarmů](#reset-alarms).
+Tímto nastavením se mění maximální množství inzulinu, které může být dodáno během jednoho dne. Pokud je tento limit překročen, patch bude pozastaven a spustí se alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Nastavte na rozumnou hodnotu dle svých potřeb.
@@ -189,9 +189,9 @@ Toto nastavení lze při použití pumpy Medtrum změnit, ale doporučuje se nas
#### Aktivujte patch z karty Medtrum
-V rozhraní AAPS přejděte na [kartu Medtrum](#overview) a klepněte na tlačítko **Vyměnit patch** vpravo dole.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-Pokud je patch již aktivován, budete nejprve vyzváni k jeho deaktivaci. viz [Deaktivace patche](#deactivate-patch).
+Pokud je patch již aktivován, budete nejprve vyzváni k jeho deaktivaci. see [Deactivate Patch](#nano-deactivate-patch).
Postupujte podle pokynů pro naplnění a aktivaci nového patche. Upozornění – je důležité spojit základnu se zásobníkem (patchem) až ve chvíli, kdy vás k tomu aplikace vyzve. **Umístit pumpu na tělo a aplikovat kanylu je nutné až ve chvíli, kdy vás k tomu aplikace během aktivace vyzve (po dokončení plnění).**
@@ -242,9 +242,11 @@ Po dokončení aktivace se zobrazí následující obrazovka
Stiskněte **OK** pro návrat na hlavní obrazovku.
+(nano-deactivate-patch)=
+
### Deaktivace patche
-Chcete-li deaktivovat aktuálně aktivní patch, přejděte na [kartu Medtrum](#overview) v rozhraní AAPS a stiskněte tlačítko **Vyměnit patch**.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ Pokud AAPS nedokáže patch deaktivovat (například proto, že základna pumpy
Jakmile je deaktivace dokončena, stiskněte **OK** pro návrat na hlavní obrazovku nebo stiskněte **Další**, chcete-li pokračovat v procesu aktivace nového patche.
+(nano-resume-interrupted-activation)=
+
### Obnovení přerušené aktivace
-Pokud je aktivace patche přerušena, například proto, že dojde k vybití baterie telefonu, můžete proces aktivace znovu spustit – přejděte na [kartu Medtrum](#overview) v rozhraní AAPS a stiskněte tlačítko **Vyměnit patch**.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Stisknutím tlačítka **Další** pokračujte v procesu aktivace. Stisknutím t
Ovladač se pokusí zjistit aktuální stav aktivace patche. Bude-li proces úspěšný, aktivace naváže a bude pokračovat.
+(nano-overview)=
+
## Přehled
Přehled obsahuje informace o aktuálním stavu patche Medtrum. Obsahuje také tlačítka pro výměnu patche, resetování alarmů a obnovení stavu.
@@ -343,6 +349,8 @@ Toto tlačítko obnoví stav patche.
Toto tlačítko spustí proces výměny patche. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Resetovat alarmy
Tlačítko alarmu se zobrazí na obrazovce přehledu, když je aktivní alarm, který lze resetovat. Stisknutím tohoto tlačítka dojde k resetování alarmů a obnovení dodávky inzulínu, pokud byl patch pozastaven kvůli alarmu. E.g. když je pozastaven kvůli alarmu při dosažení maximální denní dávky inzulínu.
@@ -372,7 +380,7 @@ Pokud máte problémy s přípojením kvůli časovému limitu nebo jiné probl
### Aktivace přerušena
-Pokud je proces aktivace přerušen, například kvůli vybité baterii telefonu nebo poruše telefonu. Proces aktivace lze obnovit tak, že se přejde na obrazovku pro výměnu patche a budete postupovat dle pokynů pro obnovení aktivace, jak je uvedeno v části: [Obnovení přerušené aktivace](#resume-interrupted-activation)
+Pokud je proces aktivace přerušen, například kvůli vybité baterii telefonu nebo poruše telefonu. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Jak předejít chybám patche
diff --git a/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md
index 79b1079618a2..2f5b841a58e7 100644
--- a/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Aktivovat Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Deaktivovat Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Tab
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### Tlačítka
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Settings
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/cs/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/cs/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 46a8cd8908df..6ac2017b9db7 100644
--- a/docs/CROWDIN/cs/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/cs/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/cs/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/cs/Maintenance/UpdateAaps3204.md
index 3aae1a645763..5aac8b94b864 100644
--- a/docs/CROWDIN/cs/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/cs/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/cs/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuild.md
index 90db139eedf0..acc98f1c56e3 100644
--- a/docs/CROWDIN/cs/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/cs/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/cs/index.md b/docs/CROWDIN/cs/index.md
index f5c1b314c475..541e92e1a146 100644
--- a/docs/CROWDIN/cs/index.md
+++ b/docs/CROWDIN/cs/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/de/AdvancedOptions/Autotune.md b/docs/CROWDIN/de/AdvancedOptions/Autotune.md
index 4438ef560ec7..7adaae3ea926 100644
--- a/docs/CROWDIN/de/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/de/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Das Autotune-Plugin ist die Umsetzung des OpenAPS Autotune-Algorithmus in AAPS.
- Die Schaltfläche "Profile vergleichen" öffnet die Profilvergleichsansicht. Das Eingangsprofil ist blau und das Ergebnisprofil 'Angepasst' ist rot dargestellt.
- - Hinweis: im Beispiel unten hat das Eingangsprofil hat zirkadianisch angepasste Werte für IC und ISF, aber das Ergebnisprofil hat jeweils nur einen Wert. Wenn es Dir wichtig ist ein zirkadian verteiltes Ergebnisprofil zu bekommen, lies den Abschnitt [Zirkadiane Profile für KH- und Korrekturfaktoren (IC/ISF)](#circadian-ic-or-isf-profile) unten.
+ - Hinweis: im Beispiel unten hat das Eingangsprofil hat zirkadianisch angepasste Werte für IC und ISF, aber das Ergebnisprofil hat jeweils nur einen Wert. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Das Autotune-Plugin ist die Umsetzung des OpenAPS Autotune-Algorithmus in AAPS.
-- Automatisierung Profilwechsel (voreingestellt: AUS): Details hierzu findest Du unten im Abschnitt [Autotune mit einer Automatisierungsregel starten](#run-autotune-with-an-automation-rule). Wenn Du diese Einstellung auf AN änderst, wird in einer Automatisierungsregel das Eingabeprofil automatisch durch das berechnete Profil aktualisiert und anschliessend darauf gewechselt.
+- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#autotune-run-autotune-with-an-automation-rule) below. Wenn Du diese Einstellung auf AN änderst, wird in einer Automatisierungsregel das Eingabeprofil automatisch durch das berechnete Profil aktualisiert und anschliessend darauf gewechselt.
- **Sei vorsichtig und prüfe in den kommenden Tagen sehr genau, ob sich das Loop-Verhalten nach der Anpassung und Aktivierung des Profils verbessert.**
- UAM als Basal kategorisieren (voreingestellt: EIN): Diese Einstellung ist für Nutzende gedacht, die AAPS ohne Eingabe der Kohlenhydrate einsetzen (vollständiges UAM). Wenn die Option deaktiviert ist, werden UAM nicht als Basal bewertet.
- Hinweis: Wenn mindestens eine Stunde eines Tages erkannt wird, in der KH-Aufnahme stattgefunden hat, werden alle als "UAM" kategorisierte Daten, als Basal gewertet. Das ist unabhängig davon, ob Du die Option aktiviert hast oder nicht (AN oder AUS)
- Anzahl der Tage an Daten (voreingestellt: 5): Hier kannst Du den Standardwert festlegen. Jedes Mal, wenn Du ein neues Profil im Autotune-Plugin auswählst, wird der Parameter 'Anpassungstage' durch diesen Standardwert ersetzt.
-- Durchschnittsresultat im zirkadianen IC/ISF anwenden (voreingestellt: AUS): Details hierzu findest Du unten im Abschnitt [Zirkadiane Profile für KH- und Korrekturfaktoren (IC/ISF)](#circadian-ic-or-isf-profile).
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Andere Einstellungen
diff --git a/docs/CROWDIN/de/AdvancedOptions/DevBranch.md b/docs/CROWDIN/de/AdvancedOptions/DevBranch.md
index 6b9ddb127440..c67184977a7b 100644
--- a/docs/CROWDIN/de/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/de/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/de/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/de/AdvancedOptions/FullClosedLoop.md
index 61e8103d936e..c76d5faa23bc 100644
--- a/docs/CROWDIN/de/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/de/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Der **Hybrid Closed Loop** („HCL“) basiert zwar auf einem Algorithmus, erfor
Im **FCL** sind mahlzeitenbezogene Boli nicht mehr notwendig: Überlasse das dem Algorithmus! Der Modus, der es **AAPS** ermöglicht ohne KH-Eingaben und manuelle Boli auszukommen, nennt sich „unangekündigte Mahlzeiten“ (engl.: un-announced meals **„UAM“**). **UAM** ermöglicht **AAPS** aggressiver auf falsche Kohlenhydrateingaben zu reagieren, sodass sich AAPS damit toleranter auf diese Fehleingaben zeigt.
-### Was erwartet mich?
+## What to expect?
Es gibt viele veröffentlichte Studien über die guten Ergebnisse, die **FCL** erreichen kann. Weitere Informationen findest Du in den folgenden Quellen:
@@ -22,7 +22,7 @@ Um erfolgreich mit **FCL** zu sein, muss der Nutzende:
- die **AAPS**-Einstellungen (insbesondere die **Automatisierungen**) fein nachjustieren und anpassen.
-### Generelle Überlegungen, warum (nicht) von Hybrid zu Full Closed Loop gewechselt werden sollte
+## General considerations why (not to) move from HCL to FCL
Ein **FCL** (Full Closed Loop System) ist nicht für jeden geeignet:
@@ -32,7 +32,7 @@ Ein **FCL** (Full Closed Loop System) ist nicht für jeden geeignet:
- Es bleiben noch Schwierigkeiten beim **FCL** mit Kindern (weiter unten diskutiert).
-### Gut eingestellter Hybrid Closed Loop
+## Well-tuned hybrid closed loop
Es ist ratsam, zuerst eine gut abgestimmte Steuerung des Hybrid Closed Loop (**HCL**) zu haben, bevor Du den Schritt zum **FCL** überlegst. Ein erfolgreicher **FCL** braucht eine sehr individuelle Abstimmung der Einstellungen, damit **AAPS** so Insulin abgibt, wie es DEIN gut laufender Hybrid-Closed-Loop-Modus tut (d. h. er ahmt ihn nach).
@@ -40,7 +40,7 @@ Es ist ratsam, zuerst eine gut abgestimmte Steuerung des Hybrid Closed Loop (**H
**FCL ist ein DIY-Setup von Automatisierungen, das vom Benutzer durch die Analyse seiner Daten sowohl aus seinen erfolgreichen HCL- als auch aus seinen ersten FCL-Erfahrungen bei der Anpassung seiner Einstellungen erstellt wird.**
-### Schnelles Insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** benötigt schnelles Insulin. Es ist so, dass zu Beginn eines mahlzeitenbedingten **Glukosewert**-Anstiegs, **FCL** in der Lage ist, den **Glukosewert** im Zielbereich zu halten (üblicherweise unter 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
Allerdings können Fiasp oder Lyumjev häufig zu Verstopfungen führen, auch wenn Dinge wie beispielsweise die Nadellänge angepasst wurden. Es ist wichtig, ein Auge auf die Kanülen- oder Pod-Dauer zu haben. Bei vielen Nutzenden lässt die Insulinwirkung nach 48 Stunden nach, bevor die Kanüle bzw. der Pod letztendlich ausfällt.
-### Voraussetzungen
+## Prerequisites
**Glukosewerte** und eine stabile Bluetooth-Verbindung sind Voraussetzung dafür, dass **AAPS** optimal und zügig agieren kann. **FCL** benötigt rund um die Uhr ein technisch stabiles System:
@@ -76,13 +76,13 @@ Allerdings können Fiasp oder Lyumjev häufig zu Verstopfungen führen, auch wen
Das oben Genannte hängt von den jeweiligen Komponenten Deines **AAPS**-Systems und Deinem individuellem Lebensstil ab.
-### Mahlzeitbezogene Einschränkungen
+## Meal-related limitations
- Das Einrichten eines **FCL** für Menschen, deren Ernährung aus wenig schnellen Kohlenhydraten besteht und damit einen geringen Einfluss auf den **Glukosewert** hat und deren Mahlzeiten sich täglich ähneln, könnte einfacher sein. Dies bedeutet nicht automatisch „Low Carb“.
- Fette oder proteinreiche Ernährung oder langsame Verdauung/Gastroparese machen die Dinge eher einfacher als schwieriger für den **FCL**, weil späte Kohlenhydrate schön die unvermeidlichen „späten Wirkenden“ (tails), die durch die zur Spitzenabdeckung benötigten Boli abdecken.
-#### Glykämischer Index und Wirkung auf den Blutzucker
+### Glykämischer Index und Wirkung auf den Blutzucker
Die Herausforderung für den **UAM**-Modus steigt mit steigendem „Effekt auf Blutzucker“ („EBG“)
@@ -98,7 +98,7 @@ Die schwierigsten Mahlzeiten für den **FCL** sind diejenigen mit ausschließlic
Der falsche Konsum von Snacks und Süßgetränken, die aus schnell absorbierten Kohlenhydraten bestehen, ist für den **FCL** problematisch.
-#### Vorbereitung auf Aktivität/Sport
+## Preparing for activity/sports
Wenn Du mit einer Pumpe oder einem hybriden Closed Loop trainierst oder aktiv bist, wird empfohlen, das **IOB** vor der Aktivität zu reduzieren.
@@ -106,7 +106,7 @@ Mit **FCL** ist der Algorithmus so eingestellt, dass er **UAM** erkennt und bei
Ungewöhnliche oder fehlerhafte Aktivität sind für den **FCL** problematisch. Für sportliche Aktivitäten ist es nötig im Voraus zu planen (insbesondere, wenn der Bedarf an Notfall-KH/Snacks während einer Sport-Hypo reduziert werden soll). Nach einem aktiven Tag wird empfohlen, einen niedrigeres **prozentuales Profil** für die Nacht, nachdem das Abendessen vollständig verstoffwechselt ist, zu setzen: Setze in **Automatisierung** ein erhöhtes (>100 mg/dl) **Glukoseziel** und stelle sicher, dass in den **AAPS**-Einstellungen „keine **SMBs** bei erhöhtem Ziel“ausgewählt ist.
-#### Hindernisse für Kinder
+## Hurdles for kids
**FCL** kann für Kinder zusätzliche Herausforderungen mit sich bringen, unter anderem:
@@ -116,7 +116,7 @@ Ungewöhnliche oder fehlerhafte Aktivität sind für den **FCL** problematisch.
- Wachstumshormone und ausgeprägte Veränderungen der Insulinempfindlichkeit machen es schwierig, den **FCL** genau einzustellen.
-## Aktivierung stärkerer SMBs: Sicherheit
+## Enabling boosted SMBs: safety
Im **HCL** sind Sicherheitseinschränkungen hinsichtlich der Bolusgrößen, die vom Loop automatisch abgegeben werden dürfen, hinterlegt.
@@ -141,7 +141,7 @@ Beobachte/analysiere die **SMB**-Größen kurz nach Beginn der Mahlzeit sehr gen
Deine **AAPS**-Einstellungen müssen gut genug eingestellt sein, um Deine (!) Essensgewohnheiten und Mahlzeitenauswahl bewältigen zu können.
```
-## Mahlzeiterkennung / Deine Automationen zum Boosten
+## Meal detection/your Automations for boosting
Der Schlüssel für einen erfolgreichen **FCL** ist der richtig abgestimmte **ISF**-Parameter. Wenn der **AAPS**-Master mit **Automationen** genutzt wird, muss **bei der Erkennung einer Mahlzeit (über Glukose-Deltas) automatisch eine Profiländerung > 100% ausgelöst** werden, damit ein aggressiverer **ISF** zur Verfügung steht.
@@ -151,7 +151,7 @@ Die **AAPS**-Master-Version erlaubt im **HCL**-Modus ein maximales temporäres *
- Schritt 2 - Wende einen Faktor (1/Profil%, wie in **Automation** hinterlegt) an, um den **ISF** zu verstärken.
- Schritt 3 - Stelle sicher, dass der vorgeschlagene **ISF** innerhalb der festgelegten Sicherheitsgrenzen liegt.
-### FCL Automationsvorlagen
+### FCL's Automation templates
Kästchen, die oben markiert werden sollen. Du hast die Option:
@@ -163,7 +163,7 @@ Diese Funktion kann für bestimmte Situationen wie z. B. das Aufsteh-Phänomen (
Der untenstehende Abschnitt enthält Anleitungen, wie man die **Automatisierungs**-Bedingungen zusammenfasst und wie man Situationen begegnen kann, in denen **AAPS** die Insulinabgabe erhöhen (oder verringern) sollte. Da der **ISF** nicht direkt angepasst werden kann, wird das prozentuale Anheben des **Profils** über 100 % für unsern Zweck den gleichen Effekt haben.
-### Automatisierte große SMBs bei Glukoseanstieg
+### Automated big SMBs at bg rise
Der Schlüssel zu einem erfolgreichen **FCL** ist, **zu Beginn des mahlzeitbedingten Glukoseanstiegs so schnell wie möglich große automatische SMBs durch den Loop abzugeben**, um das benötigte **IOB** „aufzuholen” (verglichen mit dem normalerweise für vergleichbare Mahlzeiten abzugebenden Bolus im **HCL**!)
@@ -206,7 +206,7 @@ Kurz nachdem einige erste **SMBs** abgegeben wurden, kommt eine **balancierte Ph
Die **AAPS**-Übersicht (wo Du COB=0 bei **UAM** im Full Loop siehst) könnte in dieser Phase nach zusätzlichen Kohlenhydraten fragen. Im **UAM**-Modus bedeutet das einfach, dass Du eine sehr grobe Plausibilitätsprüfung machen kannst: Ist es wahrscheinlich, dass diese Kohlenhydrate der Mahlzeit von vor einer Stunde unverdaut in Deinem Körper sind (von denen Du dem Loop nichts mitgeteilt hast)?
-### IOB-Schwellenwert
+### iob threshold
Oft bewirken die **Automatisierung** #1 und/oder #2, dass das IOB soweit aufgebaut wird, dass es typischerweise **Deine** Mahlzeiten abdeckt. Für eine individuelles Tuning, schau in den Daten Deines **HCL** nach den maximalen IOB-Werten (max IOB), die bei gut kalkulierbaren Mahlzeiten auftreten (meist: Dein Mahlzeiten-Bolus), und in welchem Ausmaß danach eine Hypo (oder der Bedarf an zusätzlichen Kohlenhydraten) auftrat.
@@ -235,7 +235,7 @@ Nachdem die ersten geboosterten **SMBs** abgegeben wurden, sollte Dein eingestel
Falls sich beispielsweise Dein Frühstück kohlenhydratmäßig vollständig von Deinen durchschnittlichen Abendessen unterscheidet, kannst Du von **Automatisierungen**, die zu den jeweiligen Tageszeiten gelten und unterschiedliche **iobTH**-Werte haben (möglicherweise auch unterschiedliche Deltas und unterschiedliche **prozentuale Profileinstellungen**), profitieren. Sowohl Du mit der Definition Deines Essensspektrums und Einstellungen (insbesondere **iobTH**), als auch der Loop, der sich um den sich entwickelnden **Glukose**verlauf kümmert, müssen bestimmte hohe Spitzen akzeptieren, um die Hypo-Gefahr gegen Ende der **Insulinwirkdauer** der **SMBs** zu reduzieren.
-### Stagnierende hohe Glukosewerte
+### Stagnation at high bg values
Falls nach einer „reichhaltigen“ Mahlzeit ein lang anhaltender **hoher Glukosespiegel** auftritt, hilft die **Automatisierung** #6 (unten links), „Hoch nach dem Essen“ mit der Fettsäureresistenz umzugehen: Nach mehrgängigen Mahlzeiten, einer großen fettigen Pizza oder einem Raclette-Abend könen sich in der Glukosekurve zwei Höcker oder sehr oft auch ein längeres hohes Plateau zeigen.
@@ -251,7 +251,7 @@ Automation #4, “Hoch nach dem Essen”, ist auch für einen Hybrid Closed Loop
Außerdem muss die Automation#5 abgebrochen werden können ("Stopp Hoch nach dem Essen"), damit die Insulinabgabe bei einem sinkenden Glukosewert weniger aggressiv erfolgt. (Allerdings wird der Loop, bei einem niedrigen erwarteten Glukosewert oft ohnehin schon die Insulinabgabe reduzieren bzw. begrenzen).
-### Einer Hypo vorbeugen
+## Hypo prevention
Das Kernproblem hier ist natürlich, dass der **UAM**-**FCL** (ohne die Eingabe der Kohlenhydrate) **nicht wissen kann, wie viele Gramm an Kohlenhydraten für die Aufnahme noch verfügbar sind**, und möglicherweise das „Rest“-Insulin aufbraucht, ohne dass Du in eine Hypo kommst.
@@ -274,7 +274,7 @@ Die Gefahr einer Hypo einge Stunden nach dem Essen ist im Wesentlichen eine Frag
Im Laufe der Zeit wirst Du Muster erkennen, Deine Automatisierungen adjustieren - vielleicht sogar Deine Essgewohnheiten ein wenig anpassen, z.B. einfach einen gelegentlichen kleinen(!) Snack genießen, der helfen kann, eine gute **Balance zwischen Insulinaktivität und Kohlenhydratabsorption** für die **gesamte** Dauer der Mahlzeit (mit Verdauung, Absorption) zu halten und so das Leben Deines Loops (und für Dich selbst) einfacher zu machen.
-### Reihenfolge der programmierten Automationen
+### Order of programmed Automations
Es können Probleme mit sich überschneidenden Definitionen zwischen den **Automatisierungen** auftreten. Beispiel: Die Problemstellung ist, dass Delta >8 auch Delta >5 ist, d.h. es kann zwei konkurrierende **Automatisierungen** geben. Was macht der Loop in dieser Situation? Der Loop entscheidet immer nach der Sortierung Deiner **Automatisierungen** in der entsprechenden Ansicht (Hamburger-Menü/AAPS-Übersicht). Beispiel: Die Delta > +8-Regel muss als erstes ausgeführt werden (und startet, wenn alle Bedingungen zutreffen den stärksten Boost); danach folgt die Überprüfung auf Delta >5 (und eine sanftere Reaktion). Würden sie anders herum sortiert und ausgeführt werden, würde die Delta >8-Regel nie in Kraft treten, weil bereits Delta >5 angewendet wird, Fall abgeschlossen.
> Tipp für Automatisierungen: Die Reihenfolge ist sehr leicht änderbar. Tippe auf einen Listeneintrag in **AAPS/Automatisierungen** und sortiere die fraglichen **Automatisierungen** an eine andere Stelle ein.
@@ -283,7 +283,7 @@ Genauso schnell und einfach kannst Du Auslöser oder Aktionen binnen weniger Sek
## Problembehandlung
-### Wie man wieder in den Hybrid Closed Loop zurückkehrt
+### How to get back into Hybrid Closed Loop
Du kannst die oberen Kästchen in den **FCL**-bezogenen **Automatisierungen** abwählen und wieder mit Mahlzeiten-Boli und der Eingabe von Kohlenhydraten beginnen. Eventuell musst Du unter **AAPS** Einstellungen/Übersicht/Schaltflächen die Schaltflächen „Insulin“ und „Rechner…” aktivieren, um sie auf der **AAPS**-Übersicht anzuzeigen. Ab jetzt bist Du wieder selber für das Bolen der Mahlzeiten verantwortlich.
@@ -293,13 +293,13 @@ Nachdem **Automatisierungen** für Abendessenzeiten erstellt sind, ist es beispi
-### Sind die Voraussetzungen für einen FCL immer noch gegeben?
+### Are the pre-conditions for FCL still given?
- Ist das Basis-**Profil** noch korrekt?
- Hat sich die **CGM**-Qualität verschlechtert
- Bitte beachte die Voraussetzungen (oben).
-### Glukosewerte steigen zu weit an
+### Glucose goes too high
- Mahlzeiten werden nicht sofort erkannt
- Prüfe die Bluetooth-(In)Stabilität
@@ -313,7 +313,7 @@ Nachdem **Automatisierungen** für Abendessenzeiten erstellt sind, ist es beispi
> Wenn Du dazu bereit bist AAPS-Entwicklungsversionen zu nutzen, kannst Du auch eine Version verwenden, die größere SMBs zulässt. Einige Nutzende greifen auch auf einen kleinen Pre-Bolus in ihrem „FCL“ zurück. Das beeinflusst allerdings den Glukoseverlauf und verändern damit die Erkennung der Anstiege und wie sich abgegebene **SMBs** verhalten und kann damit nicht ohne weiteres aus einer Nutzensicht überzeugen.
- Eine wichtige Erkenntnis von Nutzenden im Piloten war, dass es sehr wichtig ist, wie sich Deine Glukose- und IOB-Kurven dem Beginn der Mahlzeit nähern, um zu bestimmen, wie stark sie durch Kohlenhydrate ansteigen: Das Abfallen (zum Beispiel in Richtung eines temporären Ziels "Bald Essen"), der Aufbau von etwas IOB und eine bereits begonnene positive Beschleunigung, scheinen zu helfen, die Spitzen niedrig zu halten.
-### Glukosewerte fallen zu weit ab
+### Glucose goes too low
- Mahlzeiten werden fälschlicherweise erkannt
- Prüfe, ob Du größere Deltas zum Auslösen des ersten **SMB** festlegen kannst
@@ -330,7 +330,7 @@ Nachdem **Automatisierungen** für Abendessenzeiten erstellt sind, ist es beispi
- Es könnte gut sein, dass Du höhere **Glukose**spitzen zum Vermeiden einer Hypo akzeptieren musst. Oder stelle Deine Ernährung auf kleinere Kohlenhydrat- und höhere Fett- und Proteinmengen um.
-### Weitere Informationen
+### More info
Stelle sicher Dich mit anderen **FCL**-Benutzenden zu vernetzen und auszutauschen.
diff --git a/docs/CROWDIN/de/CompatibleCgms/Juggluco.md b/docs/CROWDIN/de/CompatibleCgms/Juggluco.md
index d806a95bc850..af1aaca225f4 100644
--- a/docs/CROWDIN/de/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/de/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/de/CompatibleCgms/Libre3.md b/docs/CROWDIN/de/CompatibleCgms/Libre3.md
index 79263c9a9aaa..040dc0c63028 100644
--- a/docs/CROWDIN/de/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/de/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Der Sensor kann in xDrip+ im Bereich von -40 mg/dl bis +20 mg/dl (-2.2 mmol/l bi
## Methode 1: Direkte Nutzung der minütlich übertragenen Sensorwerte
AAPS ist auf „Sensorwerte alle 5 Minuten“ ausgelegt. Die Verarbeitung von minütlichen Werten bringt in einzelnen Situationen daher Einschränkungen mit sich.
-
+See [here](#juggluco-to-aaps).
## Methode 2: Umwandlung in xDrip+ der minütlichen Messwerte in 5-Minuten-Werte
@@ -28,8 +28,6 @@ Lade die Juggluco-App [hier](https://www.juggluco.nl/Juggluco/download.html) her
Stelle sicher, dass die Glukosewerte an xDrip+ gesendet werden: In den Juggluco Einstellungen, kannst Du Juggluco so konfigurieren, dass Glukosewerte an andere Apps weitergereicht werden. Juggluco kann auf drei Arten Werte weiterreichen: Der **gepatchte Libre Broadcast** wurde ursprünglich von der gepatchten Librelink App verwendet und kann genutzt werden, um Glukosewerte an xDrip+ zu senden
-
-
### Schritt 2: xDrip+ einrichten
Die Glukosewerte werden von der xDrip+ App auf dem Deinem Smartphone empfangen.
@@ -58,10 +56,10 @@ Nach einem Sensorwechsel erkennt xDrip+ den neuen Sensor automatisch und löscht
### Schritt 4: AndroidAPS konfigurieren
-- Wähle xDrip+ unter [KONFIGURATION, BZ-Quelle](#Config-Builder-bg-source) aus.
+- See [here](#juggluco-to-xdrip) and come back.
- Wenn sich das Smartphone im Flugmodus befindet und AAPS keine Glukosewerte erhält, verwende "Empfänger identifizieren"
-- Glättung deaktivieren (in xDrip+ bereits erfolgt)
+- Turn off Smoothing (done in xDrip+ already)
## Sensorwechsel
diff --git a/docs/CROWDIN/de/CompatiblePhones/Jelly.md b/docs/CROWDIN/de/CompatiblePhones/Jelly.md
index efb9233b4bf6..c05822225a7d 100644
--- a/docs/CROWDIN/de/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/de/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Unihertz Jelly
## Jelly 2
diff --git a/docs/CROWDIN/de/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/de/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 02640b10b1f0..a279402fee93 100644
--- a/docs/CROWDIN/de/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/de/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ Die Combo kann über Bluetooth im _Remote-Terminal_-Modus oder im _Befehls_-Modu
(Du kannst das nicht beeinflussen. Der Treiber entscheidet selbständig über den zu verwendenden Modus. Das ist eine Erklärung, warum manchmal 'Combo-Frames' in diesem Feld zu sehen sein können.)
-Ganz unten befindet sich der Button AKTUALISIEREN. Damit wird sofort der aktuelle Pumpenstatus abgefragt. Es wird auch verwendet, um AAPS wissen zu lassen, dass ein zuvor entdeckter Fehler nun behoben wurde und dass AAPS erneut überprüfen kann, ob alles in Ordnung ist (mehr dazu unter [der Abschnitt über Warnungen und Fehler](#alerts-warnings-and-errors-and-how-they-are-handled)).
+Ganz unten befindet sich der Button AKTUALISIEREN. Damit wird sofort der aktuelle Pumpenstatus abgefragt. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Einstellungen
@@ -176,8 +176,8 @@ Diese Einstellungen sind für den Combotreiber verfügbar (Elemente sind von obe
1. _Pumpe koppeln_: Dieser Button wird genutzt, um die Koppelung mit der Combo zu starten. Es ist deaktiviert, wenn bereits eine Pumpe gekoppelt ist.
2. _Pumpe entkoppeln_: Hebt die Koppelung mit der Combo auf. Es ist das genaue Gegenteil zur ersten Option (1). Es ist deaktiviert, wenn noch keine Pumpe gekoppelt ist.
3. _Sichtbarkeit (in Sekunden)_: Während des Koppelungsvorgangs macht der Treiber das Smartphone für die Pumpe sichtbar. Dies beinflusst die Dauer der Sichtbarkeit. Das Maximum (300 Sekunden = 5 Minuten) ist voreingestellt. Android erlaubt keine permanente Sichtbarkeit, sodass eine Dauer ausgewählt werden muss.
-4. _Ampullenwechsel automatisch erkennen und eintragen_: Vermerkt den Ampullenwechsel, der normalerweise händisch über den Tab AKTIONEN > Katheterwechsel > Insulinreservoir-Wechsel eingetragen wird. Dies wird [weiter unten](#autodetecting-and-automatically-entering-battery-and-reservoir-changes) genauer beschrieben.
-5. _Batteriewechsel automatisch erkennen und eintragen_: Vermerkt den Batteriewechsel, der normalerweise händisch auf dem AKTIONEN Tab über den Button 'Pumpenbatterie-Wechsel' eingetragen wird. Dies wird [weiter unten](#autodetecting-and-automatically-entering-battery-and-reservoir-changes) genauer beschrieben.
+4. _Ampullenwechsel automatisch erkennen und eintragen_: Vermerkt den Ampullenwechsel, der normalerweise händisch über den Tab AKTIONEN > Katheterwechsel > Insulinreservoir-Wechsel eingetragen wird. This is explained [in further detail below](#combov2-autodetections).
+5. _Batteriewechsel automatisch erkennen und eintragen_: Vermerkt den Batteriewechsel, der normalerweise händisch auf dem AKTIONEN Tab über den Button 'Pumpenbatterie-Wechsel' eingetragen wird. This is explained [in further detail below](#combov2-autodetections).
6. _Aktiviere erweitertes Combo-Logging_: Dies erhöht die Anzahl der Log-Einträge durch den Treiber. **ACHTUNG**: Aktiviere diese Option nur, wenn Du von einem Entwickler oder einer Entwicklerin dazu aufgefordert wirst. Ansonsten kann dies die AAPS-Logs überfluten und sie unübersichtlich machen und den Nutzen reduzieren.
Die meisten Benutzer nutzen nur die beiden ersten Elemente: die _Pumpe koppeln_ und _Pumpe entkoppeln_ Buttons.
@@ -202,7 +202,7 @@ Bestimmte Warnungen werden automatisch vom Treiber verworfen. Diese sind:
- W2 "Batterie fast leer": der Treiber macht daraus eine "low battery"-Warnung, die auf dem AAPS-Startbildschirm angezeigt wird
- W3, W6, W7, W8: Sind alle rein informativ, daher ist es OK, dass der Treiber diese Meldungen automatisch verwirft/bestätigt
-Andere Warnungen werden _nicht automatisch_ verworfen/bestätigt. Fehlermeldungen werden ebenfalls _niemals automatisch_ verworfen/bestätigt. Beide werden gleich behandelt: Sie führen dazu, dass der Treiber einen Warndialog auf der AAPS-Oberfläche anzeigt und der laufende Befehl abgebrochen wird. Der Treiber schaltet dann in einen "Fehler"-Status (vgl. dazu auch den Abschnitt [Accu-Chek Combo-Tab Inhalt](#accu-chek-combo-tab-contents)) oben. In diesem Zustand können keine weiteren Befehle ausgeführt werden. Du musst den Fehler auf der Pumpe lösen (z.B. kann ein Verstopfungs-Fehler einen Kanülenwechsel erfordern). Sobald der Fehler korrigiert wurde, kann der normale Betrieb wieder aufgenommen werden. Tippe dazu auf den Button 'Aktualisieren' auf dem Tab 'Accu-Chek Combo'. Der Treiber verbindet sich dann mit der Combo und aktualisiert den Status und prüft, ob noch andere Fehler bestehen. Der Treiber aktualisiert den Pumpenstatus in regelmäßigen Abständen automatisch. Ein manuelles Aktualisieren ist also nicht unbedingt erforderlich.
+Andere Warnungen werden _nicht automatisch_ verworfen/bestätigt. Fehlermeldungen werden ebenfalls _niemals automatisch_ verworfen/bestätigt. Beide werden gleich behandelt: Sie führen dazu, dass der Treiber einen Warndialog auf der AAPS-Oberfläche anzeigt und der laufende Befehl abgebrochen wird. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). In diesem Zustand können keine weiteren Befehle ausgeführt werden. Du musst den Fehler auf der Pumpe lösen (z.B. kann ein Verstopfungs-Fehler einen Kanülenwechsel erfordern). Sobald der Fehler korrigiert wurde, kann der normale Betrieb wieder aufgenommen werden. Tippe dazu auf den Button 'Aktualisieren' auf dem Tab 'Accu-Chek Combo'. Der Treiber verbindet sich dann mit der Combo und aktualisiert den Status und prüft, ob noch andere Fehler bestehen. Der Treiber aktualisiert den Pumpenstatus in regelmäßigen Abständen automatisch. Ein manuelles Aktualisieren ist also nicht unbedingt erforderlich.
Einen Bolus abzugeben ist ein Sonderfall. Dies wird über den Befehlsmodus, der während der Bolusabgabe keine Alarme bzw. Fehlermeldungen weitergibt, umgesetzt. Deshalb kann der Treiber Warnungen während der Bolusabgabe _nicht automatisch_ verwerfen bzw. bestätigen. Leider bedeutet das, dass die Combo in dieser Situation bis zum Ende des Bolus piepen wird. Der Alarm, der am häufigsten während einer Bolusabgabe auftritt, ist W1 'Ampulle fast leer'. Bestätige während eines laufenden Bolus **auf keinen Fall** Warnungen händisch direkt auf der Combo. Du riskierst sonst, den Bolus zu unterbrechen. Der Treiber wird sich um die Warnungen kümmern, sobald der Bolus durchgelaufen ist.
@@ -215,8 +215,8 @@ Alarme, die auftreten, während der Treiber nicht mit der Combo verbunden ist, k
* Beachten Sie, dass dies kein 'Produkt' ist. Besonders am Anfang musst Du das System überwachen und verstehen wo seine Grenzen sind und es versagen kann. Es wird dringend empfohlen, dieses System NICHT zu verwenden, wenn die Person, die es benutzt, nicht in der Lage ist, es vollständig zu verstehen.
* Aufgrund der Art wie die Fernbedienung der Combo funktioniert, sind einige Aktionen im Vergleich zu anderen Pumpen (insbesondere das Setzen eines Basalprofils) langsam. Leider ist das eine Beschränkung der Combo, die nicht überwunden werden kann.
* Gib keine TBR an der Pumpe ein und lösche dort auch keine. Der Loop übernimmt die Verwaltung der TBR. Sollte manuell eingegriffen werden, kann der Loop z.B. die Startzeit einer TBR nicht ermitteln und wird somit nicht zuverlässig funktionieren können.
-* Drücke keine Tasten an der Pumpe während AAPS mit der Pumpe kommuniziert (erkennbar am Bluetooth Logo, das auf dem Display der Pumpe angezeigt wird). Durch einen Knopfdruck wird die Bluetooth-Verbindung unterbrochen. Tue das nur, wenn es Probleme beim Verbindungsaufbau gibt (siehe Abschnitt ["Bevor Du startest"](#before-you-begin) oben).
-* Drücke keine Tasten während eines laufenden Bolus. Versuche insbesondere nicht, Alarme durch Drücken von Tasten zu verwerfen/bestätigen. Eine detailliertere Beschreibung zu den Hintergründen findest Du im Abschnitt [Alarme (Warnungen und Fehler)](#alerts-warnings-and-errors-and-how-they-are-handled).
+* Drücke keine Tasten an der Pumpe während AAPS mit der Pumpe kommuniziert (erkennbar am Bluetooth Logo, das auf dem Display der Pumpe angezeigt wird). Durch einen Knopfdruck wird die Bluetooth-Verbindung unterbrochen. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Drücke keine Tasten während eines laufenden Bolus. Versuche insbesondere nicht, Alarme durch Drücken von Tasten zu verwerfen/bestätigen. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checkliste für den Fall, dass keine Verbindung mit der Combo hergestellt werden kann
diff --git a/docs/CROWDIN/de/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/de/CompatiblePumps/DanaRS-Insulin-Pump.md
index ea357c3729bc..605235ac39b4 100644
--- a/docs/CROWDIN/de/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/de/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Drücke OK, um das bisherige Passwort einzugeben.
-* Gib das**bisherige Passwort** (Standard-Passwort siehe [oben](#default-password)) ein und drücke OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ Falls Du das Smartphone wechselst, sind die folgenden Schritte erforderlich:
### DanaRS v3, Dana-i
-* Starte den Kopplungsprozess wie [oben](#pairing-pump) beschrieben.
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* In Einzelfällen muss die Koppelung im alten Smartphone zunächst gelöscht werden. Um die Koppelung in AAPS zu löschen, drückst Du in der Dana-i/RS-Registerkarte lange auf das Bluetooth-Symbol.
## Mit der Dana RS Pumpe über Zeitzonen hinweg reisen
diff --git a/docs/CROWDIN/de/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/de/CompatiblePumps/MedtronicPump.md
index 6a8d8c7fd352..4788c7c004ff 100644
--- a/docs/CROWDIN/de/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/de/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ Während der Konfiguration Deiner Medtronic-Pumpe, solltest Du die folgenden Ein
- **Seriennummer der Pumpe**: Steht auf der Rückseite der Pumpe und beginnt mit 'SN'. Hier sollen nur die sechs Ziffern (keine Buchstaben) eingegeben werden (z.B. 123456).
- **Pumpentyp**: Das genutzte Pumpenmodell (z.B. 522).
-- **Pumpenfrequenz**: In Abhängigkeit davon, wo Deine Pumpe hergestellt wurde, wähle eine der beiden Optionen aus. Bitte schlage in den [FAQ](#faq) nach, wenn Du nicht sicher bist welche Option Du wählen solltest:
+- **Pumpenfrequenz**: In Abhängigkeit davon, wo Deine Pumpe hergestellt wurde, wähle eine der beiden Optionen aus. Please check the [FAQ](#MedtronicPump-faq) if you are unsure which option to select):
- für Pumpen aus den USA & Kanada ist die Frequenz 916 MHz.
- Pumpen aus anderen Ländern ("worldwide") nutzen 868 MHz.
- **Max Basal in der Pumpe (IE/h)**: Der Wert muss mit den Einstellungen auf Deiner Pumpe übereinstimmen (vgl. 'Pumpen-Einstellungen' oben). Auch hier gilt: Wähle die Einstellung sorgfältig, da dieser Wert bestimmt, welche Insulinmenge AAPS Dir über die Basalrate geben darf. Damit wird die maximale temporäre Basalrate festgelegt. Zum Beispiel würde die Einstellung dieses Wertes auf das Vierfache Deiner maximalen Standard-Basalrate eine temporäre Basalrate von 400% ermöglichen. Der Maximalwert der Pumpe beträgt 34,9 Einheiten pro Stunde.
@@ -99,10 +99,10 @@ Während der Konfiguration Deiner Medtronic-Pumpe, solltest Du die folgenden Ein
Am unteren Bildschirmrand befinden sich drei Schaltflächen:
- **Aktualisieren** ist zum Aktualisieren des Pumpen-Status. Dies sollte nur verwendet werden, wenn die Verbindung über einen längeren Zeitraum unterbrochen war. Dies löst eine vollständige Datenaktualisierung aus (Chronik abrufen abfragen/setzen der Zeit, Profil abfragen, Batteriestand abfragen, etc).
-- **Pumpen-Historie**: Zeigt die Pumpen-Historie (s. [unten](#pump-history))
-- **RL Stats**: Zeigt Statistiken zum RileyLink (s. [unten](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Pumpen Historie
@@ -110,7 +110,7 @@ Am unteren Bildschirmrand befinden sich drei Schaltflächen:
Die Pumpen Historie wird alle 5 Minuten abgerufen und lokal gespeichert. Nur die letzten 24 Stunden der Pumpen-Historie werden gespeichert. Damit können die Log-Dateien übersichtlich gehalten werden und das Pumpenverhalten gut analysiert werden, wenn es erforderlich werden sollte. Es werden nur die Einträge gespeichert, die eine Relevanz für AAPS haben. Konfigurations-Daten ohne Relevanz werden nicht gespeichert.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL Status (RileyLink Status)
diff --git a/docs/CROWDIN/de/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/de/CompatiblePumps/MedtrumNano.md
index 0e49e8dbe89d..45a0850b81a0 100644
--- a/docs/CROWDIN/de/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/de/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ Diese Einstellung ändert, wenn das [Patch Ablaufdatum](#medtrum-patch-expiratio
***Voreingestellt: 25 IE.***
-Diese Einstellung begrenzt die maximal in einer Stunde abzugebende Insulinmenge. Beim Überschreiten des Limits, wird der Patch die Insulinlieferung unterbrechen und einen Alarm auslösen. Der Alarm kann durch das Drücken der Reset-Taste im Übersichtsmenü zurückgesetzt werden (siehe [Alarme zurücksetzen](#reset-alarms)).
+Diese Einstellung begrenzt die maximal in einer Stunde abzugebende Insulinmenge. Beim Überschreiten des Limits, wird der Patch die Insulinlieferung unterbrechen und einen Alarm auslösen. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Setze den Wert auf eine für Deine speziellen Insulin-Anforderungen vernünftigen Wert.
@@ -128,7 +128,7 @@ Setze den Wert auf eine für Deine speziellen Insulin-Anforderungen vernünftige
***Voreingestellt: 80 IE.***
-Diese Einstellung begrenzt die maximal an einem Tag abzugebende Insulinmenge. Beim Überschreiten des Limits, wird der Patch die Insulinlieferung unterbrechen und einen Alarm auslösen. Der Alarm kann durch das Drücken der Reset-Taste im Übersichtsmenü zurückgesetzt werden (siehe [Alarme zurücksetzen](#reset-alarms)).
+Diese Einstellung begrenzt die maximal an einem Tag abzugebende Insulinmenge. Beim Überschreiten des Limits, wird der Patch die Insulinlieferung unterbrechen und einen Alarm auslösen. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Setze den Wert auf eine für Deine speziellen Insulin-Anforderungen vernünftigen Wert.
@@ -189,9 +189,9 @@ Diese Einstellung kann für eine Medtrum-Pumpe geändert werden. Aus Sicherheits
#### Patch über den Medtrum Übersichts-Reiter aktivieren
-Navigiere zum [MEDTRUM-Reiter](#overview) in der AAPS-Übersicht und tippe auf **Wechsele Patch** in der unteren rechten Ecke.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-Wenn ein Patch bereits aktiv ist, wirst Du aufgefordert, diesen aktiven Patch zuerst zu deaktivieren. Vgl. [Patch deaktivieren](#deactivate-patch).
+Wenn ein Patch bereits aktiv ist, wirst Du aufgefordert, diesen aktiven Patch zuerst zu deaktivieren. see [Deactivate Patch](#nano-deactivate-patch).
Befolge die Anweisungen, um den neuen Patch zu befüllen und zu aktivieren. Bitte beachten Sie, dass es wichtig ist, die Pumpbase nur an den Patch des Reservoirs anzuschließen, wenn Sie dazu aufgefordert werden. **Du darfst die Pumpe nur dann auf Deinem Körper anbringen und die Kanüle einführen, wenn Du während des Aktivierungsvorgangs dazu aufgefordert wirst (nachdem die Befüllung der Pumpe abgeschlossen ist).**
@@ -242,9 +242,11 @@ Wenn die Aktivierung abgeschlossen ist, wird Folgendes angezeigt
Drücke **OK** um zum Hauptbildschirm zurückzukehren.
+(nano-deactivate-patch)=
+
### Patch deaktivieren
-Um einen aktuell aktiven Patch zu deaktivieren, gehe zum [Medtrum-Reiter](#overview) in der AAPS-Übersicht und tippe auf **Wechsele Patch **.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ Falls AAPS den Patch nicht deaktivieren kann (zum Beispiel, weil die Pumpenbasis
Sobald die Deaktivierung abgeschlossen ist, tippe auf **OK**, um zum Hauptbildschirm zurückzukehren oder tippe auf **Weiter**, um einen neuen Patch zu aktivieren zu können.
+(nano-resume-interrupted-activation)=
+
### unterbrochene Aktivierung fortsetzen
-Wenn eine Patch-Aktivierung unterbrochen wird, zum Beispiel weil der Akkustand des Smartphones zu niedrig ist, kannst Du den Aktivierungsvorgang fortsetzen, indem Du auf den [Medtrum-Reiter](#overview) in der AAPS-Übersicht gehst und auf **Wechsele Patch** tippst.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Tippe auf **Weiter**, um den Aktivierungsprozess fortzusetzen. Drücke auf **Ver
AAPS wird versuchen, den aktuellen Status der Patch-Aktivierung zu bestimmen. Wenn das erfolgreich war, wird in den Aktivierungsfortschritt übergegangen.
+(nano-overview)=
+
## Übersicht
Die Übersicht enthält den aktuellen Status des Medtrum Patches. Sie enthält auch Schaltflächen zum Wechseln des Patches, Zurücksetzen von Alarmen und zur Status-Aktualisierung.
@@ -343,6 +349,8 @@ Diese Schaltfläche aktualisiert den Patch-Status.
Diese Schaltfläche startet den Prozess zum Wechseln des Patches. Weitere Informationen findest Du unter [Patch aktivieren](#medtrum-activate-patch).
+(nano-reset-alarms)=
+
### Alarme zurücksetzen
Die Alarmtaste wird auf der Übersicht angezeigt, wenn es einen aktiven Alarm, der zurückgesetzt werden kann, gibt. Durch Drücken dieser Taste werden die Alarme zurückgesetzt und die Insulinabgabe fortgesetzt, sofern die Abgabe aufgrund des Alarms unterbrochen wurde. z.B. wenn aufgrund eines "maximale tägliche Insulinmenge"-Alarms die Abgabe unterbrochen wurde.
@@ -372,7 +380,7 @@ Wenn Du Verbindungsabbrüche oder andere Verbindungsprobleme hast:
### Aktivierung unterbrochen
-Wenn der Aktivierungsprozess beispielsweise durch einen leeren Smartphone-Akku oder einen Smartphone-Absturz unterbrochen wird. Der Aktivierungsprozess kann fortgesetzt werden, indem Du zum "Wechsele Patch"-Bildschirm gehst und den entsprechenden Schritten zur Aktivierung, wie im Abschnitt [Aktivierung fortsetzen](#resume-interrupted-activation) beschrieben, folgst.
+Wenn der Aktivierungsprozess beispielsweise durch einen leeren Smartphone-Akku oder einen Smartphone-Absturz unterbrochen wird. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Patch-Fehler verhindern
diff --git a/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md
index 783d13c0c483..4d0943371493 100644
--- a/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ Wähle in der oberen linken Ecke im **Hamburger-Menü** den Punkt **Konfiguratio
Wenn Du das **Kontrollkästchen (4)** neben dem **Zahnrad (3)** wählst, wird das DASH-Menü als Registerkarte im **AAPS**-Interface mit dem Titel **DASH** als eigener Tab angezeigt. Wenn Du dieses Kästchen aktivierst, wird der Zugriff auf die DASH-Befehle bei der Verwendung von **AAPS** erleichtert.
-**HINWEIS:** Eine schnellere Möglichkeit, zu den [**DASH-Einstellungen**](#dash-settings) zu gelangen, findest Du im Abschnitt DASH-Einstellungen weiter unten in diesem Dokument.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Bitte **wische nach links **zur **DASH** Registerkarte, wo du alle Pod Funktione
 „Pod-Management“ (Aktivieren, Deaktivieren, Testsignal und Pod-Historie)
+(omnipod-dash-activate-pod)=
### Pod aktivieren
@@ -132,7 +133,7 @@ Stelle sicher, dass der neue Pod und das Smartphone, auf dem **AAPS** läuft, na
Klicke auf den Zurück-Knopf auf deinem Smartphone, um zum Tab-Bildschirm **DASH** zurückzukehren, auf dem jetzt Informationen zu deiner aktiven Pod-Sitzung angezeigt werden, einschließlich der aktuellen Basalrate, Pod Reservoir Level, abgegebenem Insulin, Pod Fehlern und Warnungen.
- Weitere Details zu den angezeigten Informationen findest Du im [**DASH-Tab**](#dash-tab)-Abschnitt dieses Dokuments.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Stelle sicher, dass der neue Pod und das Smartphone, auf dem **AAPS** läuft, na
Es ist zu empfehlen, NACH der Aktivierung des Pods die Einstellungen zu exportieren. Exportiere mit jedem Wechsel eines Pods und einmal im Monat die Einstellungen und kopiere die exportierte Datei in Deinen Cloudspeicher. Details hierzu findest Du in [**Erstellen und Wiederherstellen von Backups**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Pod deaktivieren
@@ -176,9 +177,11 @@ Gehe wie folgt vor, um einen Pod zu deaktivieren (entweder vor dem Ablaufen der
+(omnipod-dash-resuming-insulin-delivery)=
+
### Insulinabgabe fortsetzen
-**Hinweis**: Während eines **Profilwechsels**, muss der DASH vor dem Setzen eines neuen Basal-**Profils** die Insulinabgabe stoppen, da die Insulinabgabe unterbrochen sein kann. Lies [**Insulinabgabe unterbrochen**](#delivery-suspended) im Abschnitt Problembehandlung für weitere Details.
+**Hinweis**: Während eines **Profilwechsels**, muss der DASH vor dem Setzen eines neuen Basal-**Profils** die Insulinabgabe stoppen, da die Insulinabgabe unterbrochen sein kann. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Benutze diesen Befehl, um den aktiven, derzeit pausierten Pod anzuweisen, die Insulinabgabe fortzusetzen. Nachdem der Befehl erfolgreich verarbeitet wurde, wird die normale Insulinabgabe mit der aktuellen Basalrate fortgesetzt. Grundlage dafür ist das zu dieser Zeit aktive Basal**profil**. Der Pod akzeptiert dann wieder Befehle für Bolus, **TBR**und **SMB**.
@@ -215,7 +218,7 @@ In dem folgenden Prozess wird gezeigt, wie Warntöne bestätigt und stummgeschal
4. Wechsele zur Registerkarte **DASH**. Im Feld **Aktive Pod-Warnungen** wird keine Warnmeldung mehr angezeigt und der aktive Pod gibt keine Pieptöne zur Warnung mehr ab.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### Anzeige Pod-Historie
@@ -240,7 +243,7 @@ Diese Funktion ist hilfreich bei der Überprüfung von Bolus-, TBR- und Basalrat
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## Registerkarte DASH
@@ -275,7 +278,7 @@ Im Folgenden werden die Anordnung und die Bedeutung der Symbole und Statusfelder
* **Reservoir:** Zeigt 50+ IE übrig an, wenn mehr als 50 Einheiten im Reservoir vorhanden sind. Unter 50 IE werden die exakten Einheiten angezeigt.
* **Insgesamt abgegeben:** Zeigt die Gesamtzahl der aus dem Reservoir abgegebenen Insulineinheiten an. Dies schließt Insulin ein, das zum Aktivieren und Befüllen verwendet wurde.
-* **Fehler:** Zeigt den letzten Fehler an. Prüfe die [Pod Historie](#view-pod-history) und die Protokolldateien („log files“) auf vorhandene Fehlermeldungen und detailliertere Informationen.
+* **Fehler:** Zeigt den letzten Fehler an. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Aktive Pod-Warnungen:** Zeigt jeweils aktuelle Warnungen auf dem aktiven Pod.
### Schaltflächen
@@ -303,12 +306,12 @@ Im Folgenden ist die Bedeutung der Symbole im **Pod Management**-Bildschirm zu s
-* 2 - [**Pod aktivieren**](#activate-pod) : Füllt und aktiviert einen neuen Pod.
-* 3 - [**Pod deaktivieren**](#deactivate-pod) : Deaktiviert den derzeit aktiven Pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Testton abspielen**: Spielt einen einzelnen Test Piep auf dem Pod ab.
-* 5 - [**Pod Historie**](#view-pod-history) : Zeigt den Aktivitätsverlauf des aktiven Pods an.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## DASH-Einstellungen
@@ -388,6 +391,8 @@ Sonstiges
## Problembehandlung
+(omnipod-dash-delivery-suspended)=
+
### Insulinabgabe unterbrochen
* Es gibt keine Unterbrechen-Taste mehr. Wenn Du die Insulinabgabe unterbrechen möchtest, kannst Du eine Null-**TBR** für x Minuten setzen.
@@ -396,7 +401,7 @@ Sonstiges
- Es kann eine Benachrichtigung geben, dass einer der Befehle unbestätigt blieb: Dies hängt davon ab, wann der Fehler aufgetreten ist.
- **AAPS** wird alle 15 Minuten versuchen, das neue Basalprofil zu setzen.
- **AAPS** wird alle 15 Minuten darüber benachrichtigen, dass die Insulinabgabe unterbrochen ist, sofern die Abgabe noch immer unterbrochen ist (Insulinabgabe konnte nicht gestartet werden).
- - Die [**Insulin fortsetzen**](#resuming-insulin-delivery) Schaltfläche wird aktiv, wenn die Lieferung manuell fortgesetzt werden soll.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- Wenn **AAPS** die Abgabe nicht alleine fortsetzen kann (dies geschieht, wenn der Pod nicht erreichbar ist, der Ton stumm geschaltet ist, etc.), beginnt der Pod für 3 Minuten jede Minute viermal zu piepen. Das wird, wenn die Abgabe für mehr als 20 Minuten ausgesetzt ist, alle 15 Minuten wiederholt.
* Für unbestätigte Befehle sollte "Aktualisieren" des Podstatus diese bestätigen oder ablehnen.
diff --git a/docs/CROWDIN/de/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/de/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index c714aed75d18..3766974dc023 100644
--- a/docs/CROWDIN/de/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/de/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ Hier ist ein Beispiel eines Image-Blocks für second_hand, (in diesem Fall ist k
"color": "#BC906A"
}
```
-Um das "second_hand" Bild mit einer Standardfarbe einzufärben (lowRange, midRange oder highRange), muss die unterste Zeile mit dem Schlüsselwert `bgColor` geändert werden.
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/de/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/de/Maintenance/UpdateAaps3204.md
index c1c18237e99a..d45b48df2230 100644
--- a/docs/CROWDIN/de/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/de/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Auf AAPS 3.2.0.4 aktualisieren
(update-aaps-3204)=
diff --git a/docs/CROWDIN/de/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/de/SettingUpAaps/BrowserBuild.md
index 3b19973be1ec..745458312a06 100644
--- a/docs/CROWDIN/de/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/de/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/de/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/de/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/de/index.md b/docs/CROWDIN/de/index.md
index fd92da50fdef..905879d4f467 100644
--- a/docs/CROWDIN/de/index.md
+++ b/docs/CROWDIN/de/index.md
@@ -84,19 +84,21 @@ Komponentenübersicht <./Getting-Started/ComponentOverview.md>
```
```{toctree}
-:caption: 3) AAPS
+:caption: 3) Setting up AAPS
-Einrichten des Berichtsservers <./SettingUpAaps/SettingUpTheReportingServer.md>
+Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
-AAPS erstellen <./SettingUpAaps/BuildingAaps.md>
-AAPS übertragen und installieren <./SettingUpAaps/TransferringAndInstallingAaps.md>
-Einrichtungsassistent <./SettingUpAaps/SetupWizard.md>
-Dein AAPS-Profil <. SettingUpAaps/YourAapsProfile.md>
-Ändern der AAPS-Konfiguration <./SettingUpAaps/ChangeAapsConfiguration.md>
-- Konfiguation <./SettingUpAaps/ConfigBuilder.md>
-- Einstellungen <./SettingUpAaps/Preferences.md>
-Abschluss der Ziele <./SettingUpAaps/CompletingTheObjectives.md>
+Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
+Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
+Setup Wizard <./SettingUpAaps/SetupWizard.md>
+Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
+Change AAPS configuration <./SettingUpAaps/ChangeAapsConfiguration.md>
+- Config Builder <./SettingUpAaps/ConfigBuilder.md>
+- Preferences <./SettingUpAaps/Preferences.md>
+Completing the objectives <./SettingUpAaps/CompletingTheObjectives.md>
```
```{toctree}
@@ -139,13 +141,15 @@ Austausch-Plattform für eigene Zifferblätter <./ExchangeSiteCustomWatchfaces/i
```
```{toctree}
-:caption: 7) AAPS Wartung und Pflege
+:caption: 7) Maintenance of AAPS
-Export/Import der Einstellungen <./Maintenance/ExportImportSettings.md>
-Deine Daten reviewen <./Maintenance/Reviewing.md>
+Export/Import Settings <./Maintenance/ExportImportSettings.md>
+Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
-Dokumenten-Änderungen <./Maintenance/DocumentationUpdate.md>
-Update auf eine neue AAPS-Version <./Maintenance/UpdateToNewVersion.md>
+Documentation updates <./Maintenance/DocumentationUpdate.md>
+Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/el/AdvancedOptions/Autotune.md b/docs/CROWDIN/el/AdvancedOptions/Autotune.md
index e4b12704a749..53d39dd45b32 100644
--- a/docs/CROWDIN/el/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/el/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/el/AdvancedOptions/DevBranch.md b/docs/CROWDIN/el/AdvancedOptions/DevBranch.md
index 79b3101847ed..ffdb8ef3b47d 100644
--- a/docs/CROWDIN/el/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/el/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/el/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/el/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/el/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/el/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/el/CompatibleCgms/Juggluco.md b/docs/CROWDIN/el/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/el/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/el/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/el/CompatibleCgms/Libre3.md b/docs/CROWDIN/el/CompatibleCgms/Libre3.md
index 38ffea9e1445..8ad5f6783793 100644
--- a/docs/CROWDIN/el/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/el/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/el/CompatiblePhones/Jelly.md b/docs/CROWDIN/el/CompatiblePhones/Jelly.md
index 915ff0de90e3..e88a174ada4d 100644
--- a/docs/CROWDIN/el/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/el/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/el/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/el/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 4dfc69ecf342..8faee1b7e764 100644
--- a/docs/CROWDIN/el/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/el/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Προτιμήσεις
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. It is strongly advised NOT to use this system when the person using it is not able to fully understand the system.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* Μην ρυθμίσετε ή ακυρώσετε ένα TBR στην αντλία. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/el/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/el/CompatiblePumps/DanaRS-Insulin-Pump.md
index 280b7bd34c73..552f363f34e9 100644
--- a/docs/CROWDIN/el/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/el/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Πατήστε OK για να εισάγετε τον παλιό κωδικό πρόσβασης.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ In case the connection between AAPS and Dana RS is lost during bolus insulin del
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
## Ταξιδεύοντας σε διαφορετικές ζώνες ώρας με την Dana Rs
diff --git a/docs/CROWDIN/el/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/el/CompatiblePumps/MedtronicPump.md
index 811d3367614e..9be2957d9014 100644
--- a/docs/CROWDIN/el/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/el/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Ιστορικό αντλίας
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Pump history is retrieved every 5 minutes and stored locally. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## Κατάσταση RL (κατάσταση RileyLink)
diff --git a/docs/CROWDIN/el/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/el/CompatiblePumps/MedtrumNano.md
index 38b1b26b4813..a95acc1e9117 100644
--- a/docs/CROWDIN/el/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/el/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Σφαιρική Εικόνα
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md
index ddf4f0122ff7..a66c7622fb8a 100644
--- a/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activate Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Deactivate Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Tab
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### Buttons
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Settings
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/el/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/el/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/el/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/el/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/el/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/el/Maintenance/UpdateAaps3204.md
index 80e404bc6c25..131b633dbf22 100644
--- a/docs/CROWDIN/el/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/el/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/el/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/el/SettingUpAaps/BrowserBuild.md
index 58dbc578da98..a0497b5f39e7 100644
--- a/docs/CROWDIN/el/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/el/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/el/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/el/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/el/index.md b/docs/CROWDIN/el/index.md
index 69a9809e1df8..6fd2b0eb9d25 100644
--- a/docs/CROWDIN/el/index.md
+++ b/docs/CROWDIN/el/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/es/AdvancedOptions/Autotune.md b/docs/CROWDIN/es/AdvancedOptions/Autotune.md
index e4b12704a749..53d39dd45b32 100644
--- a/docs/CROWDIN/es/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/es/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/es/AdvancedOptions/DevBranch.md b/docs/CROWDIN/es/AdvancedOptions/DevBranch.md
index 6aae19500a78..cd5cbcbfd718 100644
--- a/docs/CROWDIN/es/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/es/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/es/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/es/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/es/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/es/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/es/CompatibleCgms/Juggluco.md b/docs/CROWDIN/es/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/es/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/es/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/es/CompatibleCgms/Libre3.md b/docs/CROWDIN/es/CompatibleCgms/Libre3.md
index 42f38114a833..38954dc4a5b7 100644
--- a/docs/CROWDIN/es/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/es/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Dentro de xDrip+, el sensor se puede calibrar en un rango de -40 mg/dl a +20 mg/
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Descarga e instala la aplicación Juggluco desde [aquí](https://www.juggluco.nl
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+
-
-
### Paso 2: Configurar xDrip+
Los valores de glucosa en sangre son recibidos por la aplicación xDrip+ en el teléfono móvil.
@@ -58,10 +56,10 @@ Después de un cambio de sensor, xDrip+ detectará automáticamente el nuevo sen
### Paso 4: Configurar AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Cambios posteriores del sensor
diff --git a/docs/CROWDIN/es/CompatiblePhones/Jelly.md b/docs/CROWDIN/es/CompatiblePhones/Jelly.md
index 7f2a49c7be8b..43476bfb13e3 100644
--- a/docs/CROWDIN/es/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/es/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/es/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/es/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index d4b922a496dd..4a81cb4e5104 100644
--- a/docs/CROWDIN/es/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/es/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Preferencias
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. It is strongly advised NOT to use this system when the person using it is not able to fully understand the system.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* Don't set or cancel a TBR on the pump. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/es/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/es/CompatiblePumps/DanaRS-Insulin-Pump.md
index d0903290a2b7..c4c9fc433e1c 100644
--- a/docs/CROWDIN/es/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/es/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Press OK to enter old password.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ When switching to a new phone the following steps are necessary:
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
## Cambio de zona horaria al viajar con la bomba Dana RS
diff --git a/docs/CROWDIN/es/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/es/CompatiblePumps/MedtronicPump.md
index 8ed527da5749..72c7ecbf8d03 100644
--- a/docs/CROWDIN/es/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/es/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Historial de la bomba
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Pump history is retrieved every 5 minutes and stored locally. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## Estado de RL (Estado de RileyLink)
diff --git a/docs/CROWDIN/es/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/es/CompatiblePumps/MedtrumNano.md
index 22b6f0645900..807f975cf417 100644
--- a/docs/CROWDIN/es/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/es/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Inicio
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md
index f99e21e82205..4a4bd195cf75 100644
--- a/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activar Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Desactivar Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Tab
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### Botones
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Settings
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/es/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/es/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/es/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/es/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/es/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/es/Maintenance/UpdateAaps3204.md
index 3217edde242f..118f532114ca 100644
--- a/docs/CROWDIN/es/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/es/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/es/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/es/SettingUpAaps/BrowserBuild.md
index 61074bb261c6..d3c2ea6129b4 100644
--- a/docs/CROWDIN/es/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/es/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/es/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/es/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/es/index.md b/docs/CROWDIN/es/index.md
index 5f5628f32afd..eadf60afeada 100644
--- a/docs/CROWDIN/es/index.md
+++ b/docs/CROWDIN/es/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/fr/AdvancedOptions/Autotune.md b/docs/CROWDIN/fr/AdvancedOptions/Autotune.md
index a7fee37d12a8..6aed4906917c 100644
--- a/docs/CROWDIN/fr/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/fr/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Le plugin Autotune est une implémentation de l'algorithme autotune OpenAPS dans
- Le bouton « Comparer les profils » ouvre la vue Comparateur de profil. Le profil d'entrée est en bleu, et le profil de sortie (nommé "Tuned") est en rouge.
- - Remarque : dans l'exemple ci-dessous, le profil d'entrée a une variation circadienne pour le G/I et la SI, mais le profil calculé en sortie a une seule valeur. Si pour vous il est important d'obtenir un profil de sortie circadien, voir [Profil G/I ou SI circadians](#circadian-ic-or-isf-profile) ci-dessous.
+ - Remarque : dans l'exemple ci-dessous, le profil d'entrée a une variation circadienne pour le G/I et la SI, mais le profil calculé en sortie a une seule valeur. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Le plugin Autotune est une implémentation de l'algorithme autotune OpenAPS dans
-- Changer le profil avec l'Automatisation (Désactivé par défaut) : voir [Exécuter Autotune avec une règle d'automatisation](#run-autotune-with-an-automation-rule) ci-dessous. Si vous activez ce paramètre, le profil d'entrée sera automatiquement mis à jour par le profil Tuned, et il sera activé.
+- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#autotune-run-autotune-with-an-automation-rule) below. Si vous activez ce paramètre, le profil d'entrée sera automatiquement mis à jour par le profil Tuned, et il sera activé.
- **Soyez prudent, vous devez prendre confiance en vérifiant pendant plusieurs jours qu'après une mise à jour et l'activation du profil Tuned sans aucune modification, cela améliore effectivement votre boucle**
- Catégoriser UAM comme basal (par défaut On) : Ce paramètre est pour les utilisateurs utilisant AndroidAPS sans aucun glucide entré (Full UAM). Il empêchera (quand désactivé) de catégoriser les RNS en tant que basal.
- Remarque : si vous avez au moins une heure d'absorption de glucides détectée pendant une journée, alors toutes les données catégorisées comme "RNS" seront catégorisées en tant que basal, quel que soit ce paramètre (Activé ou Désactivé)
- Nombre de jours de données (par défaut 5) : Vous pouvez définir la valeur par défaut avec ce paramètre. À chaque fois que vous sélectionnez un nouveau profil dans le plugin Autotune, le nombre de jours sera remplacé par cette valeur par défaut
-- Appliquer le résultat moyen dans les G/I & SI circadienne (Désactivation par défaut) : voir [Profil avec G/I ou SI Circadiens](#circadian-ic-or-isf-profile) ci-dessous.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/fr/AdvancedOptions/DevBranch.md b/docs/CROWDIN/fr/AdvancedOptions/DevBranch.md
index 8a6bebeeecdf..b8cc817d8f7d 100644
--- a/docs/CROWDIN/fr/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/fr/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/fr/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/fr/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/fr/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/fr/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/fr/CompatibleCgms/Juggluco.md b/docs/CROWDIN/fr/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/fr/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/fr/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/fr/CompatibleCgms/Libre3.md b/docs/CROWDIN/fr/CompatibleCgms/Libre3.md
index 5c5d7b214152..21318afd1b61 100644
--- a/docs/CROWDIN/fr/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/fr/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/fr/CompatiblePhones/Jelly.md b/docs/CROWDIN/fr/CompatiblePhones/Jelly.md
index 99c81b70bbe2..7febe990b427 100644
--- a/docs/CROWDIN/fr/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/fr/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/fr/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/fr/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index ea2734da934f..78511a3712c6 100644
--- a/docs/CROWDIN/fr/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/fr/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ Le Combo peut être commandé via Bluetooth en mode _terminal à distance_ ou en
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Préférences
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. Il est fortement conseillé de NE PAS utiliser ce système lorsque la personne n'est pas en mesure de bien le comprendre entièrement.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* Ne faites pas ou n'annulez pas de DBT sur la pompe. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/fr/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/fr/CompatiblePumps/DanaRS-Insulin-Pump.md
index b7ae8146975b..06c3c0998af3 100644
--- a/docs/CROWDIN/fr/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/fr/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Appuyez sur OK pour saisir l'ancien mot de passe.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ Lors du passage à un nouveau téléphone, les étapes suivantes sont nécessair
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Il est parfois nécessaire d'effacer les informations d'appairage dans AAPS en faisant un clic long sur l'icône BT dans l'onglet Dana-i/RS.
## Voyager avec différents fuseaux horaires avec la pompe DanaR
diff --git a/docs/CROWDIN/fr/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/fr/CompatiblePumps/MedtronicPump.md
index c325b1b7c439..102e479a9959 100644
--- a/docs/CROWDIN/fr/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/fr/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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):
- pour les US & le Canada, la fréquence utilisée est 916 Mhz
- pour le reste du monde, la fréquence utilisée est de 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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Historique pompe
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
L'historique de la pompe est récupéré toutes les 5 minutes et stocké localement. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## État RL (RileyLink État)
diff --git a/docs/CROWDIN/fr/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/fr/CompatiblePumps/MedtrumNano.md
index 899456e7cd52..9e9271f7dfd5 100644
--- a/docs/CROWDIN/fr/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/fr/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Aperçu
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. Par ex. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md
index 960104436956..af6272761667 100644
--- a/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activer le Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Cliquez sur le bouton Retour de votre téléphone pour retourner à l'onglet **DASH** qui affichera maintenant les informations du Pod pour votre session active de pod, y compris le débit de basal actuel, le niveau du réservoir de pod, l'insuline délivrée, les erreurs de pod et les alertes.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Désactiver Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Reprendre l'injection d'insuline
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Allez dans l'onglet **DASH**. Sous le champ **Alertes du Pod actif** , le message d'alerte n'est plus affiché, et le pod actif n'émettra plus de beeps d'expiration du pod.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### Voir l'historique du Pod
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## Onglet DASH
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Réservoir :** Affiche plus de 50+U quand plus de 50 unités sont dans le réservoir. Below 50 U, the exact units are displayed.
* **Total injecté :** Affiche le nombre total d'unités d'insuline injectées depuis le réservoir. This includes insulin used for activating and priming.
-* **Erreurs :** Affiche la dernière erreur rencontrée. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Erreurs :** Affiche la dernière erreur rencontrée. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Alertes Pod actif :** Réservées pour les alertes en cours sur le pod actif.
### Boutons
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Paramètres Dash
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/fr/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/fr/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index e3e1e45b9445..6cecf4852018 100644
--- a/docs/CROWDIN/fr/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/fr/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ Voir ci-dessous un exemple de bloc Image pour l'aiguille des secondes, (dans ce
"color": "#BC906A"
}
```
-Pour avoir la vue second_hand (aiguille des secondes) avec la couleur par défaut des glycémies (Hypo, dans la plage cible ou Hyper), il vous suffit de modifier la dernière ligne avec le mot clé `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/fr/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/fr/Maintenance/UpdateAaps3204.md
index 9c87d33b89a8..495c2701838e 100644
--- a/docs/CROWDIN/fr/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/fr/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/fr/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuild.md
index 405d9bac3108..5aaf3d1d7506 100644
--- a/docs/CROWDIN/fr/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/fr/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/fr/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/fr/index.md b/docs/CROWDIN/fr/index.md
index 77b74fcda7c9..e73316d67c0f 100644
--- a/docs/CROWDIN/fr/index.md
+++ b/docs/CROWDIN/fr/index.md
@@ -84,19 +84,21 @@ Les différents composants <./Getting-Started/ComponentOverview.md>
```
```{toctree}
-:caption: 3) Installation d'AAPS
+:caption: 3) Setting up AAPS
-Serveur de reporting <./SettingUpAaps/SettingUpTheReportingServer.md>
+Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
-Compilation d'AAPS <./SettingUpAaps/BuildingAaps.md>
-Transfert et Installation d'AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
-Assistant de configuration <./SettingUpAaps/SetupWizard.md>
-Votre Profil AAPS <./SettingUpAaps/YourAapsProfile.md>
-Modifier la configuration <./SettingUpAaps/ChangeAapsConfiguration.md>
-- Configuration <./SettingUpAaps/ConfigBuilder.md>
-- Préférences <./SettingUpAaps/Preferences.md>
-Compléter les objectifs <./SettingUpAaps/CompletingTheObjectives.md>
+Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
+Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
+Setup Wizard <./SettingUpAaps/SetupWizard.md>
+Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
+Change AAPS configuration <./SettingUpAaps/ChangeAapsConfiguration.md>
+- Config Builder <./SettingUpAaps/ConfigBuilder.md>
+- Preferences <./SettingUpAaps/Preferences.md>
+Completing the objectives <./SettingUpAaps/CompletingTheObjectives.md>
```
```{toctree}
@@ -139,13 +141,15 @@ Site d'échange des cadrans personnalisés <./ExchangeSiteCustomWatchfaces/index
```
```{toctree}
-:caption: 7) Maintenance d'AAPS
-
-Exporter/Importer les paramètres <./Maintenance/ExportImportSettings.md>
-Analyse des données <./Maintenance/Reviewing.md>
-Notes de version AAPS <./Maintenance/ReleaseNotes.md>
-Changements de la doc <. Maintenance/DocumentationUpdate.md>
-Mise à jour vers une nouvelle version d'AAPS <./Maintenance/UpdateToNewVersion.md>
+:caption: 7) Maintenance of AAPS
+
+Export/Import Settings <./Maintenance/ExportImportSettings.md>
+Reviewing your data <./Maintenance/Reviewing.md>
+AAPS Release Notes <./Maintenance/ReleaseNotes.md>
+Documentation updates <./Maintenance/DocumentationUpdate.md>
+Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/he/AdvancedOptions/Autotune.md b/docs/CROWDIN/he/AdvancedOptions/Autotune.md
index e4b12704a749..53d39dd45b32 100644
--- a/docs/CROWDIN/he/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/he/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/he/AdvancedOptions/DevBranch.md b/docs/CROWDIN/he/AdvancedOptions/DevBranch.md
index 55a587c2f90a..dd410c1dea17 100644
--- a/docs/CROWDIN/he/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/he/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/he/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/he/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/he/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/he/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/he/CompatibleCgms/Juggluco.md b/docs/CROWDIN/he/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/he/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/he/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/he/CompatibleCgms/Libre3.md b/docs/CROWDIN/he/CompatibleCgms/Libre3.md
index 38ffea9e1445..8ad5f6783793 100644
--- a/docs/CROWDIN/he/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/he/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/he/CompatiblePhones/Jelly.md b/docs/CROWDIN/he/CompatiblePhones/Jelly.md
index b0b8c94714b1..1acfdcd690a1 100644
--- a/docs/CROWDIN/he/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/he/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/he/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/he/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 2991b3c302ce..d5e9dbc3b339 100644
--- a/docs/CROWDIN/he/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/he/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## העדפות
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. It is strongly advised NOT to use this system when the person using it is not able to fully understand the system.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* אין להגדיר או לבטל בזאלי זמני על גוף המשאבה. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/he/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/he/CompatiblePumps/DanaRS-Insulin-Pump.md
index 490b88be2387..1a903e03065e 100644
--- a/docs/CROWDIN/he/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/he/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Press OK to enter old password.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ When switching to a new phone the following steps are necessary:
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
## Timezone traveling with Dana RS pump
diff --git a/docs/CROWDIN/he/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/he/CompatiblePumps/MedtronicPump.md
index 1d48919e5a43..38fc9f10f55c 100644
--- a/docs/CROWDIN/he/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/he/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Pump History
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Pump history is retrieved every 5 minutes and stored locally. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL Status (RileyLink Status)
diff --git a/docs/CROWDIN/he/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/he/CompatiblePumps/MedtrumNano.md
index 4c0652111621..09b5668a9d9c 100644
--- a/docs/CROWDIN/he/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/he/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## סקירה כללית
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md
index 450fba0d36dc..a49e67d0e082 100644
--- a/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activate Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
לחצו על כפתור החזרה בטלפון כדי לחזור ללשונית **DASH** שתציג כעת מידע על הפוד הנוכחי, כולל המינון הבזאלי הנוכחי, רמת מכל האינסולין, אינסולין שהוזרק, שגיאות של הפוד והתראות.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Deactivate Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### חידוש הזרקת האינסולין
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. נווטו ללשונית **DASH**. תחת **התראות פוד פעילות**, הודעת האזהרה אינה מוצגת עוד והפוד כבר לא יוציא צפצופי אזהרת תפוגה.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### הצגת היסטוריית הפוד
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## לשונית DASH
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **מכל:** מציג מעל 50+U כאשר נותרו יותר מ -50 יחידות במכל. כשיש פחות מ-50 יחידות, יתרתן מוצגת במדוייק.
* **סה"כ שהוזרק:** מציג את המספר הכולל של יחידות האינסולין שהוזרקו. זה כולל אינסולין המשמש להפעלה ולתיחול.
-* **שגיאות:** מציג את השגיאה האחרונה. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **שגיאות:** מציג את השגיאה האחרונה. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **התראות פוד פעילות:** שדה השמור להתראות הפועלות כרגע על הפוד הפעיל.
### מקשים
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## הגדרות Dash
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### הפסקת הזרקה
* אין יותר כפתור של הפסקת הזרקה. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- ייתכן שתהיה הודעה על כך שאחת הפקודות אינה מאושרת: זה תלוי במועד התרחשות הכשל.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* עבור פקודות לא ודאיות, "רענון סטטוס הפוד" אמור לאשר\לדחות אותן.
diff --git a/docs/CROWDIN/he/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/he/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/he/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/he/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/he/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/he/Maintenance/UpdateAaps3204.md
index 15e6048409c9..36661d12b2d3 100644
--- a/docs/CROWDIN/he/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/he/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/he/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/he/SettingUpAaps/BrowserBuild.md
index 8b57c7d16f50..91d7095afc92 100644
--- a/docs/CROWDIN/he/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/he/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/he/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/he/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/he/index.md b/docs/CROWDIN/he/index.md
index 4758ccf6a7d3..e9a9d777dfd9 100644
--- a/docs/CROWDIN/he/index.md
+++ b/docs/CROWDIN/he/index.md
@@ -93,6 +93,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -149,6 +151,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/ko/AdvancedOptions/Autotune.md b/docs/CROWDIN/ko/AdvancedOptions/Autotune.md
index e4b12704a749..53d39dd45b32 100644
--- a/docs/CROWDIN/ko/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/ko/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/ko/AdvancedOptions/DevBranch.md b/docs/CROWDIN/ko/AdvancedOptions/DevBranch.md
index 55a587c2f90a..dd410c1dea17 100644
--- a/docs/CROWDIN/ko/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/ko/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/ko/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/ko/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/ko/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/ko/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/ko/CompatibleCgms/Juggluco.md b/docs/CROWDIN/ko/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/ko/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/ko/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/ko/CompatibleCgms/Libre3.md b/docs/CROWDIN/ko/CompatibleCgms/Libre3.md
index 38ffea9e1445..8ad5f6783793 100644
--- a/docs/CROWDIN/ko/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/ko/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/ko/CompatiblePhones/Jelly.md b/docs/CROWDIN/ko/CompatiblePhones/Jelly.md
index b0b8c94714b1..1acfdcd690a1 100644
--- a/docs/CROWDIN/ko/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/ko/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/ko/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/ko/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index f2aaacf7ea14..dc6771af14b5 100644
--- a/docs/CROWDIN/ko/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/ko/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## 설정
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. It is strongly advised NOT to use this system when the person using it is not able to fully understand the system.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* Don't set or cancel a TBR on the pump. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/ko/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/ko/CompatiblePumps/DanaRS-Insulin-Pump.md
index 4cf587f030d1..a57ef07226d7 100644
--- a/docs/CROWDIN/ko/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/ko/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Press OK to enter old password.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ When switching to a new phone the following steps are necessary:
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
## Timezone traveling with Dana RS pump
diff --git a/docs/CROWDIN/ko/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/ko/CompatiblePumps/MedtronicPump.md
index ce8f564d5b6a..4cad8fe0eeb3 100644
--- a/docs/CROWDIN/ko/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/ko/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Pump History
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Pump history is retrieved every 5 minutes and stored locally. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL Status (RileyLink Status)
diff --git a/docs/CROWDIN/ko/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/ko/CompatiblePumps/MedtrumNano.md
index f93bba98dc82..ff04f7f9301a 100644
--- a/docs/CROWDIN/ko/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/ko/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## 개요
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md
index f804a23b72a9..f3ac422ba6de 100644
--- a/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activate Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Deactivate Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Tab
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### 버튼
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Settings
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/ko/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/ko/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/ko/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/ko/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/ko/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/ko/Maintenance/UpdateAaps3204.md
index 0761a9ebaaf6..2ed2b71818c9 100644
--- a/docs/CROWDIN/ko/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/ko/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/ko/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuild.md
index 9b342ae0e3cd..1dcffd1ac3dc 100644
--- a/docs/CROWDIN/ko/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/ko/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/ko/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/ko/index.md b/docs/CROWDIN/ko/index.md
index 2b21ba58a14f..f127433869b7 100644
--- a/docs/CROWDIN/ko/index.md
+++ b/docs/CROWDIN/ko/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/lt/AdvancedOptions/Autotune.md b/docs/CROWDIN/lt/AdvancedOptions/Autotune.md
index e4b12704a749..53d39dd45b32 100644
--- a/docs/CROWDIN/lt/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/lt/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/lt/AdvancedOptions/DevBranch.md b/docs/CROWDIN/lt/AdvancedOptions/DevBranch.md
index dfb5cadc0558..1ce1faca2aff 100644
--- a/docs/CROWDIN/lt/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/lt/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/lt/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/lt/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/lt/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/lt/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/lt/CompatibleCgms/Juggluco.md b/docs/CROWDIN/lt/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/lt/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/lt/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/lt/CompatibleCgms/Libre3.md b/docs/CROWDIN/lt/CompatibleCgms/Libre3.md
index 66d086203907..a3744739fb46 100644
--- a/docs/CROWDIN/lt/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/lt/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/lt/CompatiblePhones/Jelly.md b/docs/CROWDIN/lt/CompatiblePhones/Jelly.md
index 89e0719c9646..1128ad641663 100644
--- a/docs/CROWDIN/lt/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/lt/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/lt/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/lt/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 7b7b6bbd069e..8a7654d11fd5 100644
--- a/docs/CROWDIN/lt/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/lt/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Nustatymai
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. It is strongly advised NOT to use this system when the person using it is not able to fully understand the system.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* Don't set or cancel a TBR on the pump. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/lt/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/lt/CompatiblePumps/DanaRS-Insulin-Pump.md
index 801fe48e510c..7fd867ebbc7f 100644
--- a/docs/CROWDIN/lt/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/lt/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Paspauskite OK senojo slaptažodžio įvedimui.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ When switching to a new phone the following steps are necessary:
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
## Keliavimas per skirtingas laiko juostas su DanaRS pompa
diff --git a/docs/CROWDIN/lt/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/lt/CompatiblePumps/MedtronicPump.md
index 3b1b7bb897fb..6b1e3b48a7f6 100644
--- a/docs/CROWDIN/lt/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/lt/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Pump History
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Pump history is retrieved every 5 minutes and stored locally. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL Status (RileyLink Status)
diff --git a/docs/CROWDIN/lt/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/lt/CompatiblePumps/MedtrumNano.md
index 442fe04a1864..251e95a3456d 100644
--- a/docs/CROWDIN/lt/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/lt/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Apžvalga
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md
index 1788038f6957..23f154955200 100644
--- a/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activate Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Deactivate Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Tab
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### Mygtukai
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Settings
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/lt/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/lt/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/lt/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/lt/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/lt/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/lt/Maintenance/UpdateAaps3204.md
index 7b6498f124a3..e3d0201eb398 100644
--- a/docs/CROWDIN/lt/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/lt/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/lt/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuild.md
index d2d7ab95b9e9..3968b519e9eb 100644
--- a/docs/CROWDIN/lt/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/lt/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/lt/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/lt/index.md b/docs/CROWDIN/lt/index.md
index 9151e0ff4f81..98e15dfb4655 100644
--- a/docs/CROWDIN/lt/index.md
+++ b/docs/CROWDIN/lt/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/nl/AdvancedOptions/Autotune.md b/docs/CROWDIN/nl/AdvancedOptions/Autotune.md
index e4b12704a749..53d39dd45b32 100644
--- a/docs/CROWDIN/nl/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/nl/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/nl/AdvancedOptions/DevBranch.md b/docs/CROWDIN/nl/AdvancedOptions/DevBranch.md
index c69cdedea9b2..06c8b397abf3 100644
--- a/docs/CROWDIN/nl/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/nl/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/nl/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/nl/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/nl/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/nl/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/nl/CompatibleCgms/Juggluco.md b/docs/CROWDIN/nl/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/nl/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/nl/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/nl/CompatibleCgms/Libre3.md b/docs/CROWDIN/nl/CompatibleCgms/Libre3.md
index 56b81d80338f..888a08196569 100644
--- a/docs/CROWDIN/nl/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/nl/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/nl/CompatiblePhones/Jelly.md b/docs/CROWDIN/nl/CompatiblePhones/Jelly.md
index a04e87cbd5fe..7c55cfd04fc5 100644
--- a/docs/CROWDIN/nl/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/nl/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/nl/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/nl/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 025e175cc35f..fe66f2514914 100644
--- a/docs/CROWDIN/nl/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/nl/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Instellingen
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. It is strongly advised NOT to use this system when the person using it is not able to fully understand the system.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* Gebruik nooit de knoppen op de pomp om een TBR in te stellen of te annuleren. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/nl/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/nl/CompatiblePumps/DanaRS-Insulin-Pump.md
index e90b986d0a60..3488cc055547 100644
--- a/docs/CROWDIN/nl/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/nl/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Druk OK om oude wachtwoord in te voeren.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ When switching to a new phone the following steps are necessary:
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
## Wisselen van tijdzone met de DanaRS
diff --git a/docs/CROWDIN/nl/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/nl/CompatiblePumps/MedtronicPump.md
index f914aa3e935b..399ac1a6858e 100644
--- a/docs/CROWDIN/nl/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/nl/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Pump History
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Pump history is retrieved every 5 minutes and stored locally. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL Status (RileyLink Status)
diff --git a/docs/CROWDIN/nl/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/nl/CompatiblePumps/MedtrumNano.md
index d54a42f79a33..c82dffb3ebf5 100644
--- a/docs/CROWDIN/nl/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/nl/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Overzicht
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md
index d5619af7ebcd..b2097027ec2b 100644
--- a/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activeer Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Deactiveer Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Tab
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### Knoppen
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Settings
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/nl/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/nl/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/nl/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/nl/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/nl/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/nl/Maintenance/UpdateAaps3204.md
index 0cee3941dac7..aa31d6ccc980 100644
--- a/docs/CROWDIN/nl/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/nl/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/nl/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuild.md
index 166f988a31f7..bc6f7492fb5a 100644
--- a/docs/CROWDIN/nl/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/nl/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/nl/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/nl/index.md b/docs/CROWDIN/nl/index.md
index 0e796af4f949..25c478c1e8c0 100644
--- a/docs/CROWDIN/nl/index.md
+++ b/docs/CROWDIN/nl/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/pb/AdvancedOptions/Autotune.md b/docs/CROWDIN/pb/AdvancedOptions/Autotune.md
index e4b12704a749..53d39dd45b32 100644
--- a/docs/CROWDIN/pb/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/pb/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/pb/AdvancedOptions/DevBranch.md b/docs/CROWDIN/pb/AdvancedOptions/DevBranch.md
index 55a587c2f90a..dd410c1dea17 100644
--- a/docs/CROWDIN/pb/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/pb/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/pb/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/pb/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/pb/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/pb/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/pb/CompatibleCgms/Juggluco.md b/docs/CROWDIN/pb/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/pb/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/pb/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/pb/CompatibleCgms/Libre3.md b/docs/CROWDIN/pb/CompatibleCgms/Libre3.md
index 38ffea9e1445..8ad5f6783793 100644
--- a/docs/CROWDIN/pb/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/pb/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/pb/CompatiblePhones/Jelly.md b/docs/CROWDIN/pb/CompatiblePhones/Jelly.md
index b0b8c94714b1..1acfdcd690a1 100644
--- a/docs/CROWDIN/pb/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/pb/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/pb/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/pb/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index fd0525104821..54ab0c41c6c9 100644
--- a/docs/CROWDIN/pb/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/pb/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Preferences
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. It is strongly advised NOT to use this system when the person using it is not able to fully understand the system.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* Don't set or cancel a TBR on the pump. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/pb/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/pb/CompatiblePumps/DanaRS-Insulin-Pump.md
index 490b88be2387..1a903e03065e 100644
--- a/docs/CROWDIN/pb/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/pb/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Press OK to enter old password.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ When switching to a new phone the following steps are necessary:
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
## Timezone traveling with Dana RS pump
diff --git a/docs/CROWDIN/pb/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/pb/CompatiblePumps/MedtronicPump.md
index cfb5498b22a9..e93e6ceb89ad 100644
--- a/docs/CROWDIN/pb/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/pb/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Pump History
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Pump history is retrieved every 5 minutes and stored locally. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL Status (RileyLink Status)
diff --git a/docs/CROWDIN/pb/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/pb/CompatiblePumps/MedtrumNano.md
index 4ebc4d21b5e2..983a3951f75c 100644
--- a/docs/CROWDIN/pb/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/pb/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Overview
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md
index ddf4f0122ff7..a66c7622fb8a 100644
--- a/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activate Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Deactivate Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Tab
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### Buttons
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Settings
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/pb/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/pb/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/pb/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/pb/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/pb/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/pb/Maintenance/UpdateAaps3204.md
index ed40ebd3cd77..9501eadbeec2 100644
--- a/docs/CROWDIN/pb/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/pb/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/pb/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuild.md
index cef7e7098fd8..bf1304144304 100644
--- a/docs/CROWDIN/pb/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/pb/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/pb/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/pb/index.md b/docs/CROWDIN/pb/index.md
index 076e981a23b9..df3fef2ab755 100644
--- a/docs/CROWDIN/pb/index.md
+++ b/docs/CROWDIN/pb/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/pl/AdvancedOptions/Autotune.md b/docs/CROWDIN/pl/AdvancedOptions/Autotune.md
index e4b12704a749..53d39dd45b32 100644
--- a/docs/CROWDIN/pl/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/pl/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/pl/AdvancedOptions/DevBranch.md b/docs/CROWDIN/pl/AdvancedOptions/DevBranch.md
index 55a587c2f90a..dd410c1dea17 100644
--- a/docs/CROWDIN/pl/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/pl/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/pl/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/pl/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/pl/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/pl/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/pl/CompatibleCgms/Juggluco.md b/docs/CROWDIN/pl/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/pl/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/pl/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/pl/CompatibleCgms/Libre3.md b/docs/CROWDIN/pl/CompatibleCgms/Libre3.md
index 38ffea9e1445..8ad5f6783793 100644
--- a/docs/CROWDIN/pl/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/pl/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/pl/CompatiblePhones/Jelly.md b/docs/CROWDIN/pl/CompatiblePhones/Jelly.md
index b0b8c94714b1..1acfdcd690a1 100644
--- a/docs/CROWDIN/pl/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/pl/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/pl/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/pl/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 7f0c9f106e1f..eb49cd48d501 100644
--- a/docs/CROWDIN/pl/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/pl/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Preferences
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. It is strongly advised NOT to use this system when the person using it is not able to fully understand the system.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* Don't set or cancel a TBR on the pump. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/pl/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/pl/CompatiblePumps/DanaRS-Insulin-Pump.md
index 490b88be2387..1a903e03065e 100644
--- a/docs/CROWDIN/pl/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/pl/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Press OK to enter old password.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ When switching to a new phone the following steps are necessary:
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
## Timezone traveling with Dana RS pump
diff --git a/docs/CROWDIN/pl/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/pl/CompatiblePumps/MedtronicPump.md
index c9c772ae5a86..de9c5436c792 100644
--- a/docs/CROWDIN/pl/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/pl/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Pump History
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Pump history is retrieved every 5 minutes and stored locally. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL Status (RileyLink Status)
diff --git a/docs/CROWDIN/pl/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/pl/CompatiblePumps/MedtrumNano.md
index a8ffdc6b6c02..e29a16bd2fd7 100644
--- a/docs/CROWDIN/pl/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/pl/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Overview
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md
index ddf4f0122ff7..a66c7622fb8a 100644
--- a/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activate Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Deactivate Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Tab
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### Buttons
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Settings
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/pl/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/pl/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/pl/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/pl/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/pl/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/pl/Maintenance/UpdateAaps3204.md
index ed40ebd3cd77..9501eadbeec2 100644
--- a/docs/CROWDIN/pl/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/pl/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/pl/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuild.md
index cef7e7098fd8..bf1304144304 100644
--- a/docs/CROWDIN/pl/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/pl/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/pl/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/pl/index.md b/docs/CROWDIN/pl/index.md
index f36b155f25f6..7bfb43400b4b 100644
--- a/docs/CROWDIN/pl/index.md
+++ b/docs/CROWDIN/pl/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/pt/AdvancedOptions/Autotune.md b/docs/CROWDIN/pt/AdvancedOptions/Autotune.md
index e4b12704a749..53d39dd45b32 100644
--- a/docs/CROWDIN/pt/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/pt/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/pt/AdvancedOptions/DevBranch.md b/docs/CROWDIN/pt/AdvancedOptions/DevBranch.md
index 077a407a2bf6..9028e1caf8e2 100644
--- a/docs/CROWDIN/pt/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/pt/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/pt/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/pt/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/pt/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/pt/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/pt/CompatibleCgms/Juggluco.md b/docs/CROWDIN/pt/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/pt/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/pt/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/pt/CompatibleCgms/Libre3.md b/docs/CROWDIN/pt/CompatibleCgms/Libre3.md
index 38ffea9e1445..8ad5f6783793 100644
--- a/docs/CROWDIN/pt/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/pt/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/pt/CompatiblePhones/Jelly.md b/docs/CROWDIN/pt/CompatiblePhones/Jelly.md
index b0b8c94714b1..1acfdcd690a1 100644
--- a/docs/CROWDIN/pt/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/pt/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/pt/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/pt/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 2c1895f37244..88132a8139fd 100644
--- a/docs/CROWDIN/pt/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/pt/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Preferências
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. It is strongly advised NOT to use this system when the person using it is not able to fully understand the system.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* Don't set or cancel a TBR on the pump. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/pt/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/pt/CompatiblePumps/DanaRS-Insulin-Pump.md
index bf1f72c5fa35..c75bba22cb52 100644
--- a/docs/CROWDIN/pt/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/pt/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Press OK to enter old password.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ When switching to a new phone the following steps are necessary:
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
## Timezone traveling with Dana RS pump
diff --git a/docs/CROWDIN/pt/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/pt/CompatiblePumps/MedtronicPump.md
index 899477bc7b6d..896b63cabc01 100644
--- a/docs/CROWDIN/pt/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/pt/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Histórico da Bomba
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Pump history is retrieved every 5 minutes and stored locally. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## Estatísticas RL (Estado do RileyLink)
diff --git a/docs/CROWDIN/pt/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/pt/CompatiblePumps/MedtrumNano.md
index 5aa78e80dda3..07c92f2e6a7d 100644
--- a/docs/CROWDIN/pt/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/pt/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Visão Geral
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md
index ddf4f0122ff7..a66c7622fb8a 100644
--- a/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activate Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Deactivate Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Tab
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### Buttons
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Settings
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/pt/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/pt/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/pt/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/pt/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/pt/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/pt/Maintenance/UpdateAaps3204.md
index acc74d8c7e9b..674a88d6ec73 100644
--- a/docs/CROWDIN/pt/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/pt/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/pt/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuild.md
index 23f756dac11a..deb2fdec0b0f 100644
--- a/docs/CROWDIN/pt/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/pt/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/pt/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/pt/index.md b/docs/CROWDIN/pt/index.md
index 0c5e6973be4e..317430b27d03 100644
--- a/docs/CROWDIN/pt/index.md
+++ b/docs/CROWDIN/pt/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/ro/AdvancedOptions/Autotune.md b/docs/CROWDIN/ro/AdvancedOptions/Autotune.md
index e4b12704a749..53d39dd45b32 100644
--- a/docs/CROWDIN/ro/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/ro/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/ro/AdvancedOptions/DevBranch.md b/docs/CROWDIN/ro/AdvancedOptions/DevBranch.md
index 55a587c2f90a..dd410c1dea17 100644
--- a/docs/CROWDIN/ro/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/ro/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/ro/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/ro/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/ro/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/ro/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/ro/CompatibleCgms/Juggluco.md b/docs/CROWDIN/ro/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/ro/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/ro/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/ro/CompatibleCgms/Libre3.md b/docs/CROWDIN/ro/CompatibleCgms/Libre3.md
index 38ffea9e1445..8ad5f6783793 100644
--- a/docs/CROWDIN/ro/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/ro/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/ro/CompatiblePhones/Jelly.md b/docs/CROWDIN/ro/CompatiblePhones/Jelly.md
index b0b8c94714b1..1acfdcd690a1 100644
--- a/docs/CROWDIN/ro/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/ro/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/ro/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/ro/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 48491545f78b..708f8c5ed798 100644
--- a/docs/CROWDIN/ro/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/ro/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Preferințe
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. It is strongly advised NOT to use this system when the person using it is not able to fully understand the system.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* Don't set or cancel a TBR on the pump. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/ro/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/ro/CompatiblePumps/DanaRS-Insulin-Pump.md
index 80c48392a219..a8246590d1f9 100644
--- a/docs/CROWDIN/ro/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/ro/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Apăsaţi OK pentru a introduce parola veche.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ When switching to a new phone the following steps are necessary:
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
## Timezone traveling with Dana RS pump
diff --git a/docs/CROWDIN/ro/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/ro/CompatiblePumps/MedtronicPump.md
index 0baf610f7e3c..f9d17d2a5b50 100644
--- a/docs/CROWDIN/ro/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/ro/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Pump History
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Pump history is retrieved every 5 minutes and stored locally. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL Status (RileyLink Status)
diff --git a/docs/CROWDIN/ro/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/ro/CompatiblePumps/MedtrumNano.md
index bb3b94f35362..bc3eae21b389 100644
--- a/docs/CROWDIN/ro/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/ro/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Privire de ansamblu
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md
index eb99658edfa0..bfe1df883d94 100644
--- a/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activează Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Dezactivare Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Tab
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### Butoane
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Settings
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/ro/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/ro/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/ro/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/ro/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/ro/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/ro/Maintenance/UpdateAaps3204.md
index ed40ebd3cd77..9501eadbeec2 100644
--- a/docs/CROWDIN/ro/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/ro/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/ro/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuild.md
index cef7e7098fd8..bf1304144304 100644
--- a/docs/CROWDIN/ro/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/ro/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/ro/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/ro/index.md b/docs/CROWDIN/ro/index.md
index 076e981a23b9..df3fef2ab755 100644
--- a/docs/CROWDIN/ro/index.md
+++ b/docs/CROWDIN/ro/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/ru/AdvancedOptions/Autotune.md b/docs/CROWDIN/ru/AdvancedOptions/Autotune.md
index 61925e7804b8..024b1c2988de 100644
--- a/docs/CROWDIN/ru/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/ru/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- Кнопка "Сравнить профили" открывает окно сравнения профилей. Профиль на входе синий, а на выходе ("Настроенный") - красный.
- - Примечание: в примере ниже профиль на входе имеет циклические суточные отклонения для IC и ISF, но профиль на выходе имеет одно значение. Если вам нужно получить выходной посуточный профиль см[Посуточный профиль для IC или ISF](#circadian-ic-or-isf-profile) ниже.
+ - Примечание: в примере ниже профиль на входе имеет циклические суточные отклонения для IC и ISF, но профиль на выходе имеет одно значение. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Переключение профиля при Автоматизации (по умолчанию выключено): см. [Запуск Autotune с правилом автоматизации](#run-autotune-with-an-automation-rule) ниже. Если изменить эту настройку на Включить, профиль ввода будет автоматически обновлен профилем Tuned и активирован.
+- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#autotune-run-autotune-with-an-automation-rule) below. Если изменить эту настройку на Включить, профиль ввода будет автоматически обновлен профилем Tuned и активирован.
- **Будьте внимательны, в течение нескольких следующих дней следите, чтобы после обновления и активации настроенного профиля система заработала лучше по сравнен с профилем без изменений**
- Классифицировать UAM как базал (по умолчанию Вкл.): Этот параметр предназначен для пользователей, использующих AAPS без ввода углеводов (Полный UAM). Это помешает (когда Выключено) классифицировать UAM как базал.
- Примечание: если в течение одного дня обнаружен по крайней мере один час абсорбции углеводов, тогда все данные, классифицированные как UAM, будут классифицированы как basal, вне зависимости от того, включен параметр или выключен
- Количество дней данных (по умолчанию 5): Для этого параметра можно задать значение по умолчанию. Каждый раз, когда вы выбираете новый профиль в модуле Autotune, параметр "дней для анализа" будет заменен на это значение по умолчанию
-- Применить средний суточный результат IC/ISF (по умолчанию Off): см. [Circadian IC или ISF профиль](#circadian-ic-or-isf-profile) ниже.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/ru/AdvancedOptions/DevBranch.md b/docs/CROWDIN/ru/AdvancedOptions/DevBranch.md
index 6335663f506a..ecff1a8029fd 100644
--- a/docs/CROWDIN/ru/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/ru/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/ru/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/ru/AdvancedOptions/FullClosedLoop.md
index 8d4ac806870e..3a7ca3a9686e 100644
--- a/docs/CROWDIN/ru/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/ru/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### Чего ожидать?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Правильно настроенный гибридный замкнутый цикл
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Инсулины короткого действия (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ EEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Con
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Ограничения, относящиеся к приему пищи
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Подготовка к физическим нагрузкам
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Сложности для детей
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -141,7 +141,7 @@ Carefully observe/analyse the **SMB** sizes shortly after your meal commences.
Your **AAPS'** setting must be sufficiently set up to cope with your (!) variety of meals.
```
-## Обнаружение приёма пищи/ Автоматизация для повышения эффективности
+## Meal detection/your Automations for boosting
For successful **FCL**, **ISF** is the key tuning parameter. When utilising **AAPS** Master + **Automations**, a **> 100% profile change must automatically be triggered upon meal recognition** (via glucose deltas), and provide the sharpened **ISF**.
@@ -163,7 +163,7 @@ This feature can be useful for certain situations like “foot to floor” syndr
The section below provides guidance how to bundle **Automation’s** Conditions and how to tackle situations in which the **AAPS** should increase (or decrease) insulin delivery. As **ISF** cannot directly be tuned, raising **Profile Percentage** over 100% will do the same for our purposes.
-### Автоматизированные большие СМБ при росте ГК
+### 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 h**HCL**!)
@@ -206,7 +206,7 @@ Soon after a few initial **SMBs** are given comes a **balanced phase** where mod
The **AAPS** main screen (where you see cob=0 in **UAM** full loop) might in this phase ask for more carbs required. In **UAM** mode that simply means, you could make a very rough plausibility check: Is that amount of carbs likely in your body, un-absorbed from your meal just about an hour ago (about which you gave your loop no info)?
-### порог активного инсулина IOB
+### iob threshold
Often, **Automations** #1 and/or #2 make iob rise to heights that typically are enough for **your** meals. For personalised tuning, look in your **HCL** data at the max iob values that occur with well-managed meals (often: your meal bolus), and above which magnitude a hypo (or requirement for extra carbs) occurred at the end.
@@ -235,7 +235,7 @@ After the first boosted **SMB**s were given, your set iobTH and *Automation** #3
If your breakfast substantially deviates in carb content from your average dinner, you may benefit from defining **Automations** that apply in the respective times of day, and have different **iobTH** (possibly also different deltas, and different **Percentage Profile** set). Both, you with defining your meal spectrum and settings (notably, **iobTH**), and the loop managing the unfolding **BG** curve, must accept certain peak heights for reducing hypo danger towards the end of the **DIAs** from **SMBs**.
-### Застой на высоких значениях ГК
+### Stagnation at high bg values
In case, after a “rich” meal, a long-lasting stagnation with **high BG** value is seen, **Automation** #6 (below, left),"post-meal High”, helps deal with fatty acid resistance: After multi-course meals, large greasy pizza, raclette evening, the glucose curve can form two humps or, very often, an elongated high plateau.
@@ -251,7 +251,7 @@ In case, after a “rich” meal, a long-lasting stagnation with **high BG** val
Кроме того, Автоматизация #5, “Stop post-meal High”, применяется для снижения агрессивности подачи инсулина как только начинает падать уровень глюкозы. (Однако часто алгоритм всё равно ограничивает количество инсулина для предотвращения гипогликемии, поскольку прогнозируемый уровень глюкозы уже снижается).
-### Предотвращение гипогликемии
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
@@ -274,7 +274,7 @@ Before a special meal challenge, you can raise your **iob** threshold, or make a
Со временем вы изучите закономерности, настроите свою Автоматизацию – возможно, даже немного скорректируете свои привычки в еде, чтобы, например, просто получать удовольствие от случайного (!) перекуса, который поможет поддерживать хороший **баланс между активностью инсулина и усвоением углеводов**.
-### Очерёдность применимости настроек Автоматизаций
+### Order of programmed Automations
Problems can arise with overlapping definitions in **Automations**. Example: The problem is that delta >8 is also delta >5, i.e. there may be two competing **Automations** What does the loop do then? It always decides according to the sequence in which your **Automations** appear when looking into the burger menu / AdAPS main screen. Пример: Правило дельта > +8 должно быть первым в списке (и если все правила активны, запускать самый сильный ответ); потом алгоритм проверяет значение дельты >5 (соответственно более мягкий ответ). Если отсортировать список наоборот, правило дельта>8 никогда не вступит в силу, поскольку правило дельта>5 уже применяется первым.
> Tip for Automations: Order changes are very easy to make. Press on a list entry in **AAPS/Automations** and the user rearrange the **Automations** in question to another position.
@@ -283,7 +283,7 @@ Problems can arise with overlapping definitions in **Automations**. Example: The
## Устранение неполадок
-### Как вернуться к гибридному замкнутому циклу
+### How to get back into Hybrid Closed Loop
You can un-click the top boxes in the **Automations** related to your **FCL**, and go back to bolusing for meals and make carb inputs again. You may have to go to **AAPS** Preferences/Overview/Buttons and get your Buttons “Insulin, Calculator…” back for your **AAPS** main screen. Be aware that now it is again up to you to bolus for meals.
@@ -293,13 +293,13 @@ For instance, it is perfectly possible, without any extra steps after **Automati
-### Соблюдены ли все предварительные условия для самодостаточного замкнутого цикла?
+### Are the pre-conditions for FCL still given?
- Is the basic **Profile** still correct?
- Has the **CGM** quality deteriorated
- Refer to pre-requisites (above).
-### Уровень глюкозы поднимается слишком высоко
+### Glucose goes too high
- Момент приёма пищи не распознается вовремя
- Проверьте стабильность Bluetooth-соединений
@@ -313,7 +313,7 @@ For instance, it is perfectly possible, without any extra steps after **Automati
> Если вы готовы использовать AAPS версии для разработчиков, вы можете использовать ту, которая позволяет увеличить размер SMB. Некоторые пользователи также прибегают к небольшим преболюсам в своих "самодостаточных системах замкнутого цикла". However, this interferes with how glucose curve and hence detection of rises and triggered **SMBs** behave, and is therefore not easy to implement with convincing overall benefit.
- Важным наблюдением со стороны группы испытуемых было то, какую тенденцию ваши кривые глюкозы и активного инсулина (IOB) имеют к моменту приема пищи, это оказывает существенное влияние на пики от приёма углеводов: Снижение уровня (напр. настройка "Включить временную цель TT Ожидаемый прием пищи") позволяет увеличить содержание активного инсулина IOB и удерживать пики в более низких пределах.
-### Уровень глюкозы падает слишком низко
+### Glucose goes too low
- Некорректно определяется время начала приёма пищи
- Check whether you could set bigger deltas to trigger first **SMB**
@@ -330,7 +330,7 @@ For instance, it is perfectly possible, without any extra steps after **Automati
- It could well be that you simply have to accept higher **BG** peaks for not going low. Или поменяйте диету, чтобы в ней было меньше углеводов и больше белка и жиров.
-### Больше информации
+### More info
Make sure you stay in touch with other **FCL** users.
diff --git a/docs/CROWDIN/ru/CompatibleCgms/Juggluco.md b/docs/CROWDIN/ru/CompatibleCgms/Juggluco.md
index 614c07711a03..93345ad5d0bc 100644
--- a/docs/CROWDIN/ru/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/ru/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/ru/CompatibleCgms/Libre3.md b/docs/CROWDIN/ru/CompatibleCgms/Libre3.md
index 8a5e9b12cb67..5dc166ff7a7e 100644
--- a/docs/CROWDIN/ru/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/ru/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Libre 3 Freestyle (FSL3) требует уникальной настройки
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute valu
Убедитесь, что данные ГК отправляются в Xdrip+: В настройках Juggluco можно выбрать отправку значений глюкозы другим приложениям. Juggluco может отправить три типа трансляций: Трансляция **Librelink** изначально использовалась модифицированным приложением Librelink и может отправлять значения Гк в xDrip+
-
-
### Шаг 2: Настройка xDrip
Приложение xDrip+ получает значения ГК на телефоне.
@@ -58,10 +56,10 @@ AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute valu
### Шаг 4: Настройка AndroidAPS
-- В [Конфигураторе, Источник ГК](#Config-Builder-bg-source) выберите xDrip+.
+- See [here](#juggluco-to-xdrip) and come back.
- Если AndroidAPS не получает значения BG, когда телефон находится в режиме авиаперелета, проверьте, заполнено ли поле «Идентифицировать приемник»
-- Выключите сглаживание (уже сделано в Xdrip+)
+- Turn off Smoothing (done in xDrip+ already)
## Последующие замены сенсора
diff --git a/docs/CROWDIN/ru/CompatiblePhones/Jelly.md b/docs/CROWDIN/ru/CompatiblePhones/Jelly.md
index f9229eec0965..e357cbf1779c 100644
--- a/docs/CROWDIN/ru/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/ru/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/ru/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/ru/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index a24536500f4e..8e4c94fac76a 100644
--- a/docs/CROWDIN/ru/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/ru/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ Combo может управляться при помощи Bluetooth в реж
(Пользователь не влияет на это; драйвер самостоятельно решает, какой режим применить. Это примечание для пользователей, чтобы понимать, почему иногда они могут видеть фреймы Combo на этом месте
-В самом низу находится кнопка "Обновить". Она инициирует немедленное обновление статуса помпы. Она также используется для того, чтобы информировать AAPS о том, что обнаруженная ранее ошибка теперь исправлена и что AAPS может снова выполнить проверку работоспособности системы(подробнее об этом ниже в [разделе об оповещениях](#alerts-warnings-and-errors-and-how-they-are-handled)).
+В самом низу находится кнопка "Обновить". Она инициирует немедленное обновление статуса помпы. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Настройки
@@ -176,8 +176,8 @@ Combo может управляться при помощи Bluetooth в реж
1. _Выполнить сопряжение с помпой_ кнопка для сопряжения с Combo. Она неактивна, если сопряжение уже выполнено.
2. _Разъединиться с помпой_: Выполнить разъединение с помпой, действие, противоположное пункту № 1. Она неактивна, если нет сопряжения с помпой.
3. _Продолжительность обнаружения (в секундах)_: При сопряжении драйвер делает телефон видимым для помпы. Параметр определяет, сколько длится функция обнаружения. По умолчанию выбран максимум (300 секунд = 5 минут). Android не позволяет, чтобы обнаружение длилось бессрочно, поэтому следует задать продолжительность.
-4. _Автоопределение замены резервуара инсулинов_: Если включено, выполняется действие "reservoir change" (замена резервуара), которое обычно происходит через кнопку "prime/fill" на вкладке Action (Действия). This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Автоопределение замены батареи_: Если включено, выполняется действие "battery change" (замена батареи), которое обычно происходит через кнопку "pump battery change" на вкладке Action (Действия). This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Автоопределение замены резервуара инсулинов_: Если включено, выполняется действие "reservoir change" (замена резервуара), которое обычно происходит через кнопку "prime/fill" на вкладке Action (Действия). This is explained [in further detail below](#combov2-autodetections).
+5. _Автоопределение замены батареи_: Если включено, выполняется действие "battery change" (замена батареи), которое обычно происходит через кнопку "pump battery change" на вкладке Action (Действия). This is explained [in further detail below](#combov2-autodetections).
6. _Включить подробное журналирование Combo_: Это значительно увеличивает объем логов (журнала), выполняемого драйвером. **ПРЕДУПРЕЖДЕНИЕ**: Включайте только если об этом вас попросил разработчик. В противном случае это добавит много ненужной информации в логи AAPS и уменьшит их полезность.
Большинство пользователей используют только два первых элемента: кнопки _сопряжение с помпой_ и _разъединение с помпой_.
@@ -202,7 +202,7 @@ Combo показывает оповещения как экраны удален
- W1 "Низкий уровень заряда батареи" : драйвер превращает это в предупреждение "Battery low", которое отображается на вкладке AAPS
- W3, W6, W7, W8 : все это информационные сообщения, поэтому драйвер безопасно удаляет их
-Другие предупреждения - _не_ удаляются автоматически. Кроме того, ошибки _никогда_ не закрываются автоматически. Они обрабатываются одинаково, заставляя драйвера создавать диалог оповещения поверх интерфейса AAPS, а также приводит к прекращению выполнения любой текущей команды. Драйвер затем переходит в состояние "ошибка" (см. [Описание содержания вкладок Combo выше](#accu-chek-combo-tab-contents)). Это состояние не допускает выполнения команд. Пользователь должен разобраться с ошибкой на помпе; например, может потребоваться замена каннулы. Как только пользователь исправит причину ошибки, нормальная работа системы может быть возобновлена при нажатии на кнопку "Обновить" на вкладке Accu-Chek Combo. Затем драйвер подключается к Combo и обновляет еt статус, проверяет, отображается ли ошибка на экране и т. д. Также, драйвер автоматически обновляет статус помпы через некоторое время, поэтому ручное нажатие кнопки не является обязательным.
+Другие предупреждения - _не_ удаляются автоматически. Кроме того, ошибки _никогда_ не закрываются автоматически. Они обрабатываются одинаково, заставляя драйвера создавать диалог оповещения поверх интерфейса AAPS, а также приводит к прекращению выполнения любой текущей команды. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). Это состояние не допускает выполнения команд. Пользователь должен разобраться с ошибкой на помпе; например, может потребоваться замена каннулы. Как только пользователь исправит причину ошибки, нормальная работа системы может быть возобновлена при нажатии на кнопку "Обновить" на вкладке Accu-Chek Combo. Затем драйвер подключается к Combo и обновляет еt статус, проверяет, отображается ли ошибка на экране и т. д. Также, драйвер автоматически обновляет статус помпы через некоторое время, поэтому ручное нажатие кнопки не является обязательным.
Подача болюса - отдельный случай. Это делается в командном режиме Combo, который не сообщает посреди болюса о появлении оповещения. Как следствие, драйвер не может автоматически убрать предупреждения _во время_ подачи болюса. Это означает, что, к сожалению, помпа будет издавать сигнал до завершения подачи болюса. Наиболее распространенным предупреждением во время подачи болюса обычно является W1 "низкий уровень инсулина в резервуаре". **Не** сбрасывайте предупреждения Comnbo на помпе вручную во время подачи болюса. Вы рискуете прервать болюс. Драйвер сам разберется с оповещением по завершении подачи болюса.
@@ -215,8 +215,8 @@ Combo показывает оповещения как экраны удален
* Имейте в виду, вы имеете дело не с коммерческим продуктом; на начальном этапе пользователю следует отслеживать и понимать логику, ограничения и возможные ошибки системы. Настоятельно рекомендуем не пользоваться системой, если нет полного понимания принципов ее работы.
* Из-за особенностей функциональности дистанционного управления, на Combo, по сравнению с другими помпами, медленно работают некоторые операции (особенно установка базального профиля). Это ограничение Combo не может быть преодолено.
* Не устанавливайте и не отменяйте временный базал TBR на помпе. Алгоритм AAPS берет на себя контроль над временным базалом, он не будет работать надежно при иных решениях, поскольку начало подачи временного базала, заданного пользователем на помпе, невозможно определить.
-* Не нажимайте никаких кнопок на помпе во время обмена данными между AAPS и помпой (на экране помпы в это время высвечивается логотип блутуса). Если все же такое происходит, Bluetooth-соединение прерывается. Делайте это только если есть проблемы с установкой связи (См. выше раздел [Подготовка к работе](#before-you-begin)).
-* Не нажимайте никакие кнопки во время подачи болюса. В частности, не пытайтесь убрать оповещения, нажимая кнопки. См. [раздел об оповещениях](#alerts-warnings-and-errors-and-how-they-are-handled) где дано подробное разъяснение причин.
+* Не нажимайте никаких кнопок на помпе во время обмена данными между AAPS и помпой (на экране помпы в это время высвечивается логотип блутуса). Если все же такое происходит, Bluetooth-соединение прерывается. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Не нажимайте никакие кнопки во время подачи болюса. В частности, не пытайтесь убрать оповещения, нажимая кнопки. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Контрольный лист проверок на случай отсутствия соединения с Комбо
diff --git a/docs/CROWDIN/ru/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/ru/CompatiblePumps/DanaRS-Insulin-Pump.md
index d4040840bd32..b65000ac505a 100644
--- a/docs/CROWDIN/ru/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/ru/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Нажмите OK, чтобы ввести старый пароль.
-* Введите **старый пароль** (пароль по умолчанию см. [выше](#default-password)) и нажмите OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ orphan: true
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Иногда необходимо очистить информацию о сопряжении в AAPS - долгое нажатие на иконке BT на вкладке Dana-i/RS.
## Пересечение часовых поясов с помпой Dana RS
diff --git a/docs/CROWDIN/ru/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/ru/CompatiblePumps/MedtronicPump.md
index 7348dcede7d6..305ed4fd9642 100644
--- a/docs/CROWDIN/ru/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/ru/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ When configuring your Medtronic pump with the setup wizard it is possible that y
- **Серийный номер помпы**: Находится на задней панели помпы и начинается с SN. You should only enter the 6 numbers shown without any alphabetic characters (e.g. 123456).
- **Pump Type**: Используемая модель помпы (например, 522).
-- **Частота помпы**: Есть два варианта, в зависимости от региона рынка. Проверьте [FAQ](#faq) если не уверены что выбрать):
+- **Частота помпы**: Есть два варианта, в зависимости от региона рынка. Please check the [FAQ](#MedtronicPump-faq) if you are unsure which option to select):
- для США & Канады применяется частота 916 МГц
- для остального мира - 868 МГц
- **Макс. базал на помпе (ед./ч.)**: Должен соответствоватьпараметрам помпs (см. Конфигурация помпы выше). Опять же эта настройка должна быть тщательно подобрана, так как определяет, какую базу можно задать для AAPS. То есть установить максимальную величину временного базала. Например, установка этого значения в четыре раза выше максимальной стандартной скорости позволит задавать временную скорость базала на 400%. Максимальное допустимое значение помпы составляет 34,9 ед. в час.
@@ -99,10 +99,10 @@ When configuring your Medtronic pump with the setup wizard it is possible that y
В нижней части экрана расположены три кнопки:
- **Обновить** для обновления текущего статуса помпы. Ей следует пользоваться только в случае, когда соединение отсутствовало в течение длительного периода, так как потребует полного обновления данных (получение истории, установка времени, получение профиля, получение статуса батареи и т. д.).
-- **История помпы**: Показывает журнал помпы (см. [ниже](#pump-history))
-- **Статистика RL**: Показать статистику RL (см. [ниже](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Журнал помпы
@@ -110,7 +110,7 @@ When configuring your Medtronic pump with the setup wizard it is possible that y
Хронология помпы извлекается каждые 5 минут и сохраняется в памяти. Сохраняются только предыдущие 24 часа истории. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## Состояние RL (Состояние RileyLink)
diff --git a/docs/CROWDIN/ru/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/ru/CompatiblePumps/MedtrumNano.md
index 81ec90e287a5..6602e944a65f 100644
--- a/docs/CROWDIN/ru/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/ru/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ orphan: true
***По умолчанию: 25 ед.***
-Эта настройка изменяет максимальное количество инсулина, которое может быть подано в течение одного часа. Если этот предел превышен, патч будет приостановлен и подаст сигнал. Это оповещение может быть сброшено при нажатии на кнопку сброса на общем меню - см [Сброс оповещений](#reset-alarms).
+Эта настройка изменяет максимальное количество инсулина, которое может быть подано в течение одного часа. Если этот предел превышен, патч будет приостановлен и подаст сигнал. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Установите это значение на разумную величину вашей потребности.
@@ -128,7 +128,7 @@ orphan: true
***По умолчанию: 80 ед.***
-Эта настройка изменяет максимальное количество инсулина, которое может быть подано в течение одного дня. Если этот предел превышен, патч будет приостановлен и подаст сигнал. Это оповещение может быть сброшено при нажатии на кнопку сброса на общем меню - см [Сброс оповещений](#reset-alarms).
+Эта настройка изменяет максимальное количество инсулина, которое может быть подано в течение одного дня. Если этот предел превышен, патч будет приостановлен и подаст сигнал. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Установите это значение на разумную величину вашей потребности.
@@ -189,9 +189,9 @@ orphan: true
#### Активируйте патч из вкладки Medtrum
-Перейдите к [вкладке Medtrum](#overview) в интерфейсе AAPS и нажмите кнопку **Сменить Патч** в правом нижнем углу.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-Если патч активен, вам будет предложено сначала деактивировать его. см. [Деактивация патча](#deactivate-patch).
+Если патч активен, вам будет предложено сначала деактивировать его. see [Deactivate Patch](#nano-deactivate-patch).
Следуйте подсказкам при заполнении и активации нового патча. Обратите внимание - на этом шаге важно подключить базу помпы к резервуару патча только при появлении подсказки. **Поместить помпу на тело и вставить катетер следует при появлении запроса в процессе активации (после заполнения резервуара).**
@@ -242,9 +242,11 @@ orphan: true
Нажмите **OK** для возврата к главному экрану.
+(nano-deactivate-patch)=
+
### Деактивация патча
-Чтобы деактивировать патч, зайдите на [вкладку Medtrum](#overview) интерфейса AAPS и нажмите кнопку **Заменить Patch**.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ orphan: true
После завершения деактивации, нажмите **OK** для возврата в главное окно или нажмите **Далее** для продолжения активации нового патча.
+(nano-resume-interrupted-activation)=
+
### Возобновить прерванную активацию
-Если активация патча прервана, например, потому, что села батарея телефона, можно возобновить процесс, перейдя на вкладку [Medtrum](#overview) и нажав кнопку **Заменить Patch**.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ orphan: true
Драйвер попробует определить текущий статус активации патча. Если это пройдет успешно, то на текущем шаге начнется активация.
+(nano-overview)=
+
## Общие замечания
На обзорном экране отражен текущий статус патча Medtrum. На нем также находятся кнопки для замены патча, сброса оповещений и обновления статуса.
@@ -343,6 +349,8 @@ orphan: true
Эта кнопка запустит процесс замены патча. См [Активировать патч](#medtrum-activate-patch) для получения дополнительной информации.
+(nano-reset-alarms)=
+
### Сбросить оповещения
Кнопка оповещения появляется на главном экране, когда есть активное оповещение, которое может быть убрано с экрана. Нажатие этой кнопки сбросит оповещение и возобновит подачу инсулина, если работа патча была приостановлен из-за оповещения. Например, при приостановке из-за сигнала о достижения максимума суточной подачи инсулина.
@@ -372,7 +380,7 @@ orphan: true
### Активация прервана
-Если активация прервана, например, из-за низкого заряда батареи телефона или поломки телефона. Процесс активации может быть возобновлен если перейти на экран замены патча и следовать шагам, изложенным здесь: [Возобновление прерванной активации](#resume-interrupted-activation)
+Если активация прервана, например, из-за низкого заряда батареи телефона или поломки телефона. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Предотвращение сбоев в работе патча
diff --git a/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md
index b0a0a7a91e8a..d8ef8ed007a6 100644
--- a/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Активация Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Нажмите на кнопку Назад на телефоне, чтобы вернуться на вкладку **DASH**, которая теперь отображает текущую информацию о Pod включая скорость базала, наполненность резервуара, введенный инсулин, ошибки и предупреждения.
- Подробнее об информации на дисплее см в разделе [**Вкладка DASH**](#dash-tab) документации.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Деактивация Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Возобновление подачи инсулина
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Перейдите на вкладку **DASH**. В поле **оповещения активного Pod ** больше не отображается предупреждение об истечении срока действия.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### Просмотр истории Pod
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## Вкладка DASH
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Резервуар:** Показывает 50+ед. когда в резервуаре остается более 50 ед. Ниже 50 ед. показывается точное кол-во единиц.
* **Всего подано** Отображает общее количество единиц инсулина, доставленных из резервуара. Сюда входит инсулин, используемый для активации и заполнения инфузионного набора.
-* **Ошибки:** Отображает последнюю возникшую ошибку. Просмотрите [Журнал Pod](#view-pod-history) и файлы журналов для поиска прошлых ошибок и более подробной информации.
+* **Ошибки:** Отображает последнюю возникшую ошибку. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Активные оповещения Pod** зарезервировано для текущих оповещений на активном Pod.
### Кнопки
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Активировать Pod**](#activate-pod) : Заполняет и активирует новый Pod.
-* 3 - [**Деактивировать Pod**](#deactivate-pod) : Деактивирует текущий Pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Воспроизвести тестовый звуковой сигнал** : При нажатии воспроизводит один тестовый сигнал на поде.
-* 5 - [**журнал Pod **](#view-pod-history) : Отображает историю активности Pod.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Настройки Dash
@@ -388,6 +391,8 @@ Additional note:
## Устранение неполадок
+(omnipod-dash-delivery-suspended)=
+
### Подача приостановлена
* Кнопки приостановки больше нет. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- Может быть уведомление о том, что одна из команд не подтверждена: это зависит от того, когда произошел сбой.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - Если пользователь решит возобновить введение инсулина вручную, то к его услугам будет активна кнопка [**Возобновить подачу**](#resuming-insulin-delivery).
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* Для неподтвержденных команд "Обновить статус помпы" их подтвердит/запретит.
diff --git a/docs/CROWDIN/ru/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/ru/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 8ba9c62efdfd..a534254e7edc 100644
--- a/docs/CROWDIN/ru/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/ru/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ After the first block with metadata, you will set some general parameters (see [
"color": "#BC906A"
}
```
-Чтобы секундная_стрелка была окрашена в цвет ГК по умолчанию (низкий диапазон, средний диапазон или высокий диапазон), нужно просто изменить последний линь ligne с помощью величины KeyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/ru/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/ru/Maintenance/UpdateAaps3204.md
index 6b891fa599fe..2f05169a6d7f 100644
--- a/docs/CROWDIN/ru/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/ru/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/ru/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuild.md
index 57daa6e8d72f..5bf29e5426e9 100644
--- a/docs/CROWDIN/ru/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/ru/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/ru/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/ru/index.md b/docs/CROWDIN/ru/index.md
index e4a6dd3d1380..d9e06f227c09 100644
--- a/docs/CROWDIN/ru/index.md
+++ b/docs/CROWDIN/ru/index.md
@@ -84,19 +84,21 @@ Change version <./NavigateDoc/ChangeVersion.md>
```
```{toctree}
-:caption: 3) Настройка AAPS
+:caption: 3) Setting up AAPS
-Настройка сервера отчетов <./SettingUpAaps/SettingUpTheReportingServer.md>
+Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
-Сборка AAPS <./SettingUpAaps/BuildingAaps.md>
-Передача и установка AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
-Мастер установки <./SettingUpAaps/SetupWizard.md>
-Ваш профиль AAPS <./SettingUpAaps/YourAapsProfile.md>
-Изменение настроек AAPS <./SettingUpAaps/ChangeAapsConfiguration.md>
-- Конфигуратор <./SettingUpAaps/ConfigBuilder.md>
-- Настройки <./SettingUpAaps/Preferences.md>
-Выполнение целей <./SettingUpAaps/CompletingTheObjectives.md>
+Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
+Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
+Setup Wizard <./SettingUpAaps/SetupWizard.md>
+Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
+Change AAPS configuration <./SettingUpAaps/ChangeAapsConfiguration.md>
+- Config Builder <./SettingUpAaps/ConfigBuilder.md>
+- Preferences <./SettingUpAaps/Preferences.md>
+Completing the objectives <./SettingUpAaps/CompletingTheObjectives.md>
```
```{toctree}
@@ -139,13 +141,15 @@ AAPS для Wear OS <./WearOS/BuildingAapsWearOS.md>
```
```{toctree}
-:caption: 7) Обслуживание AAPS
-
-Экспорт/импорт настроек <./Maintenance/ExportImportSettings.md>
-Просмотр своих данных <./Maintenance/Reviewing.md>
-Заметки к выпускам AAPS <./Maintenance/ReleaseNotes.md>
-Обновления документации <./Maintenance/DocumentationUpdate.md>
-Обновление версии AAPS <./Maintenance/UpdateToNewVersion.md>
+:caption: 7) Maintenance of AAPS
+
+Export/Import Settings <./Maintenance/ExportImportSettings.md>
+Reviewing your data <./Maintenance/Reviewing.md>
+AAPS Release Notes <./Maintenance/ReleaseNotes.md>
+Documentation updates <./Maintenance/DocumentationUpdate.md>
+Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/sk/AdvancedOptions/Autotune.md b/docs/CROWDIN/sk/AdvancedOptions/Autotune.md
index e4b12704a749..53d39dd45b32 100644
--- a/docs/CROWDIN/sk/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/sk/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
- - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#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.
+- Automation 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 On): This setting is for the users using AndroidAPS 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)
- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/sk/AdvancedOptions/DevBranch.md b/docs/CROWDIN/sk/AdvancedOptions/DevBranch.md
index 55a587c2f90a..dd410c1dea17 100644
--- a/docs/CROWDIN/sk/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/sk/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/sk/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/sk/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/sk/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/sk/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/sk/CompatibleCgms/Juggluco.md b/docs/CROWDIN/sk/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/sk/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/sk/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/sk/CompatibleCgms/Libre3.md b/docs/CROWDIN/sk/CompatibleCgms/Libre3.md
index 38ffea9e1445..8ad5f6783793 100644
--- a/docs/CROWDIN/sk/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/sk/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/sk/CompatiblePhones/Jelly.md b/docs/CROWDIN/sk/CompatiblePhones/Jelly.md
index b0b8c94714b1..1acfdcd690a1 100644
--- a/docs/CROWDIN/sk/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/sk/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/sk/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/sk/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 0e44866037d0..8a3ed00b7dde 100644
--- a/docs/CROWDIN/sk/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/sk/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in
(The user does not influence this; the driver fully decides on its own what mode to use. This is merely a note for users to know why sometimes they can see Combo frames in that field.)
-At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+At the very bottom, there is the "Refresh" button. This triggers an immediate pump status update. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Preferences
@@ -176,8 +176,8 @@ These preferences are available for the combo driver (items are listed from top
1. _Pair with pump_: This is a button that can be pressed to pair with a Combo. It is disabled if a pump is already paired.
2. _Unpair pump_: Unpairs a paired Combo; the polar opposite of item no. 1. It is disabled if no pump is paired.
3. _Discovery duration (in seconds)_: When pairing, the drivers makes the phone discoverable by the pump. This controls how long that discoverability lasts. By default, the maximum (300 seconds = 5 minutes) is selected. Android does not allow for discoverability to last indefinitely, so a duration has to be chosen.
-4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _Autodetect and automatically enter insulin reservoir change_: If enabled, the "reservoir change" action that is normally done by the user through the "prime/fill" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
+5. _Autodetect and automatically enter battery change_: If enabled, the "battery change" action that is normally done by the user through the "pump battery change" button in the Action tab. This is explained [in further detail below](#combov2-autodetections).
6. _Enable verbose Combo logging_: This greatly expands the amount of logging done by the driver. **CAUTION**: Do not enable this unless asked to by a developer. Otherwise, this can add a lot of noise to AndroidAPS logs and lessen their usefulness.
Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
@@ -202,7 +202,7 @@ Certain warnings are automatically dismissed by the driver. These are:
- W2 "battery low" : the driver turns this into a "low battery" warning that is shown on the AAPS main tab
- W3, W6, W7, W8 : these are all purely informational for the user, so it is safe for the driver to auto-dismiss them
-Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
+Other warnings are _not_ automatically dismissed. Also, errors are _never_ automatically dismissed. Both of these are handled the same way: They cause the driver to produce an alert dialog on top of the AAPS UI, and also cause it to abort any ongoing command execution. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). This state does not allow for any command execution. The user has to handle the error on the pump; for example, an occlusion error may require replacing the cannula. Once the user took care of the error, normal operation can be resumed by pressing the "Refresh" button on the Accu-Chek Combo tab. The driver then connects to the Combo and updates its status, checking for whether an error is still shown on screen etc. Also, the driver auto-refreshes the pump status after a while, so manually pressing that button is not mandatory.
Bolusing is a special case. It is done in the Combo's command mode, which does not report mid-bolus that an alert appeared. As a consequence, the driver cannot automatically dismiss warnings _during_ a bolus. This means that unfortunately, the pump will be beeping until the bolus is finished. The most common mid-bolus alert typically is W1 "reservoir low". **Don't** dismiss Comnbo warnings on the pump itself manually during a bolus. You risk interrupting the bolus. The driver will take care of the warning once the bolus is over.
@@ -215,8 +215,8 @@ Alerts that happen while the driver is not connected to the Combo will not be no
* Keep in mind that this is not a product, esp. in the beginning the user needs to monitor and understand the system, its limitations and how it can fail. It is strongly advised NOT to use this system when the person using it is not able to fully understand the system.
* Due to the way the Combo's remote control functionality works, several operations (especially setting a basal profile) are slow compared to other pumps. This is an unfortunate limitation of the Combo that cannot be overcome.
* Don't set or cancel a TBR on the pump. The loop assumes control of TBRs and cannot work reliably otherwise, since it's not possible to determine the start time of a TBR that was set by the user on the pump.
-* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* Don't press any buttons on the pump while AAPS communicates with the pump (the Bluetooth logo is shown on the pump while it is connected to AAPS). Doing that will interrupt the Bluetooth connection. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Don't press any buttons while the pump is bolusing. In particular, don't try to dismiss alerts by pressing buttons. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Checklist for when no connection can be established with the Combo
diff --git a/docs/CROWDIN/sk/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/sk/CompatiblePumps/DanaRS-Insulin-Pump.md
index 971963b68209..5d50719d1697 100644
--- a/docs/CROWDIN/sk/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/sk/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Press OK to enter old password.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ When switching to a new phone the following steps are necessary:
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
## Timezone traveling with Dana RS pump
diff --git a/docs/CROWDIN/sk/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/sk/CompatiblePumps/MedtronicPump.md
index 5f62505854c5..f57a519e8496 100644
--- a/docs/CROWDIN/sk/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/sk/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **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](#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.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Pump History
@@ -110,7 +110,7 @@ At the bottom of the screen there are three buttons:
Pump history is retrieved every 5 minutes and stored locally. Only the previous 24 hours worth of history is stored. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL Status (RileyLink Status)
diff --git a/docs/CROWDIN/sk/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/sk/CompatiblePumps/MedtrumNano.md
index 7ca4e20fd983..4c84f8ab3e18 100644
--- a/docs/CROWDIN/sk/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/sk/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Overview
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md
index ddf4f0122ff7..a66c7622fb8a 100644
--- a/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activate Pod
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Deactivate Pod
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Tab
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### Buttons
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Settings
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### Delivery suspended
* There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* For unconfirmed commands, "refresh pod status" should confirm/deny them.
diff --git a/docs/CROWDIN/sk/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/sk/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/sk/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/sk/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/sk/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/sk/Maintenance/UpdateAaps3204.md
index ed40ebd3cd77..9501eadbeec2 100644
--- a/docs/CROWDIN/sk/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/sk/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/sk/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuild.md
index cef7e7098fd8..bf1304144304 100644
--- a/docs/CROWDIN/sk/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/sk/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/sk/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/sk/index.md b/docs/CROWDIN/sk/index.md
index 076e981a23b9..df3fef2ab755 100644
--- a/docs/CROWDIN/sk/index.md
+++ b/docs/CROWDIN/sk/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/tr/AdvancedOptions/Autotune.md b/docs/CROWDIN/tr/AdvancedOptions/Autotune.md
index 1246b8708126..7cb3db91f7d3 100644
--- a/docs/CROWDIN/tr/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/tr/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- "Profilleri karşılaştır" butonu, profil karşılaştırıcı görünümünü açar. Giriş profili mavi ve çıkış profili ("Ayarlanmış" olarak adlandırılır) kırmızıdır.
- - Not: Aşağıdaki örnekte, giriş profilinin Kİ ve İDF için sirkadiyen değişimi vardır, ancak hesaplanan çıktı profilinin tek bir değeri vardır. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+ - Not: Aşağıdaki örnekte, giriş profilinin Kİ ve İDF için sirkadiyen değişimi vardır, ancak hesaplanan çıktı profilinin tek bir değeri vardır. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. Bu ayarı Açık olarak değiştirirseniz, giriş profili Ayarlanmış profil tarafından otomatik olarak güncellenecek ve etkinleştirilecektir.
+- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#autotune-run-autotune-with-an-automation-rule) below. Bu ayarı Açık olarak değiştirirseniz, giriş profili Ayarlanmış profil tarafından otomatik olarak güncellenecek ve etkinleştirilecektir.
- **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**
- UAM'ı bazal olarak kategorize et (varsayılan Açık): Bu ayar, herhangi bir karbonhidrat girmeden AndroidAPS kullanan kullanıcılar içindir (Tam UAM). (Kapalı olduğunda) UAM'ın bazal olarak kategorize edilmesini önleyecektir.
- Not: Bir gün boyunca tespit edilen en az bir saatlik karbonhidrat emiliminiz varsa, bu ayar ne olursa olsun (Açık veya Kapalı) "UAM" olarak sınıflandırılan tüm veriler bazal olarak kategorize edilir.
- Veri gün sayısı (varsayılan 5): Bu ayar ile varsayılan değer tanımlayabilirsiniz. Otoayar eklentisinde her yeni profil seçtiğinizde, Ayar günleri parametresi bu varsayılan değerle değiştirilecektir.
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### Other settings
diff --git a/docs/CROWDIN/tr/AdvancedOptions/DevBranch.md b/docs/CROWDIN/tr/AdvancedOptions/DevBranch.md
index af67105b6e37..2c283445277f 100644
--- a/docs/CROWDIN/tr/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/tr/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/tr/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/tr/AdvancedOptions/FullClosedLoop.md
index 15d03b43d6aa..48e023eb7ae1 100644
--- a/docs/CROWDIN/tr/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/tr/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm! **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
-### What to expect?
+## What to expect?
There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following:
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
- fine tune and adjust the **AAPS** settings (notably **Automations**).
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
**FCL** is not for everyone:
@@ -32,7 +32,7 @@ Success for **FCL** requires the user to:
- Difficulties still remain to establish a **FCL** for kids (discussed below).
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**. Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode.
@@ -40,7 +40,7 @@ It is advisable to first establish a well-tuned **HC**L before considering the t
**FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and initial FCL experience when tuning your settings.**
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL** requires fast insulin. This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
-### Prerequisites
+## Prerequisites
**BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
The above will vary depending on your **AAPS** component system and your lifestyle.
-### Meal-related limitations
+## Meal-related limitations
- Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.
- Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL** because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
@@ -98,7 +98,7 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
-#### Preparing for activity/sports
+## Preparing for activity/sports
When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
@@ -106,7 +106,7 @@ With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver
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*** preferences.
-#### Hurdles for kids
+## Hurdles for kids
**FCL** can present extra challenges for children and these include:
@@ -251,7 +251,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
-### Hypo prevention
+## Hypo prevention
The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it.
diff --git a/docs/CROWDIN/tr/CompatibleCgms/Juggluco.md b/docs/CROWDIN/tr/CompatibleCgms/Juggluco.md
index bdd4a9fa2f9c..906757834714 100644
--- a/docs/CROWDIN/tr/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/tr/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/tr/CompatibleCgms/Libre3.md b/docs/CROWDIN/tr/CompatibleCgms/Libre3.md
index 180c43da9b36..436f98333a36 100644
--- a/docs/CROWDIN/tr/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/tr/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ Download and install the Juggluco app from [here](https://www.juggluco.nl/Jugglu
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
The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -58,10 +56,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
### Step 4: Configure AndroidAPS
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
- If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
## Subsequent sensor changes
diff --git a/docs/CROWDIN/tr/CompatiblePhones/Jelly.md b/docs/CROWDIN/tr/CompatiblePhones/Jelly.md
index e5ce9b5e5cc9..054eea956374 100644
--- a/docs/CROWDIN/tr/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/tr/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/tr/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/tr/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 9fe585716b29..02cab04eef01 100644
--- a/docs/CROWDIN/tr/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/tr/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ Combo, Bluetooth aracılığıyla _uzak terminal_ modunda veya _komut_ modunda
(Kullanıcı bundan etkilenmez; sürücü hangi modun kullanılacağına tamamen kendi karar verir. Bu, kullanıcıların neden bazen o alanda Combo çiziminde çerçeveler gördüğünü bilmeleri için bir nottur.)
-En altta "Yenile" düğmesi var. Bu anında pompa durumu güncellemesini tetikler. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled)).
+En altta "Yenile" düğmesi var. Bu anında pompa durumu güncellemesini tetikler. It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## Tercihler
@@ -176,8 +176,8 @@ Bu tercihler combo sürücüsü için mevcuttur (öğeler yukarıdan aşağıya
1. _Pompa ile eşleştir_: Bu Combo pompası ile eşleştirmek için basılabilen bir butondur. Bir pompa zaten eşleştirilmişse devre dışı bırakılır.
2. _Pompa eşleştirmesini kaldır_: Eşleştirilmiş bir pompanın eşlemesini kaldırır. Hiçbir pompa eşleştirilmemişse devre dışı bırakılır.
3. _Keşif süresi (saniye olarak)_: Eşleştirme sırasında, sürücüler telefonun pompa tarafından bulunabilir olmasını sağlar. Bu keşfedilebilirliğin ne kadar süreceğini kontrol eder. Varsayılan olarak maksimum (300 saniye = 5 dakika) seçilidir. Android, keşfedilebilirliğin süresiz olarak devam etmesine izin vermez, bu nedenle bir süre seçilmelidir.
-4. _İnsülin rezervuarı değişikliğini otomatik olarak algıla ve otomatik olarak gir_: Etkinleştirilirse, normalde "rezervuar değişikliği" işlemi kullanıcı tarafından Eylem sekmesindeki "hazırla/doldur" butonuyla yapılır. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
-5. _Pil değişikliğini otomatik olarak algıla ve otomatik olarak gir_: Etkinleştirilirse, normalde "pil değiştirme" işlemi kullanıcı tarafından Eylem sekmesindeki "pompa pili değiştirme" butonu aracılığıyla gerçekleştirilir. This is explained [in further detail below](#autodetecting-and-automatically-entering-battery-and-reservoir-changes).
+4. _İnsülin rezervuarı değişikliğini otomatik olarak algıla ve otomatik olarak gir_: Etkinleştirilirse, normalde "rezervuar değişikliği" işlemi kullanıcı tarafından Eylem sekmesindeki "hazırla/doldur" butonuyla yapılır. This is explained [in further detail below](#combov2-autodetections).
+5. _Pil değişikliğini otomatik olarak algıla ve otomatik olarak gir_: Etkinleştirilirse, normalde "pil değiştirme" işlemi kullanıcı tarafından Eylem sekmesindeki "pompa pili değiştirme" butonu aracılığıyla gerçekleştirilir. This is explained [in further detail below](#combov2-autodetections).
6. _Ayrıntılı combo günlük kaydını etkinleştir_: Sürücü tarafından yapılan günlük kaydını büyük ölçüde artırır. **DİKKAT**: Bir geliştirici tarafından istenmedikçe bunu etkinleştirmeyin. Aksi takdirde, AndroidAPS günlüklerine çok fazla gürültü ekleyebilir ve bunların kullanışlılığını azaltabilir.
Çoğu kullanıcı yalnızca en üstteki iki öğe, _Pompa ile eşleştir_ ve _Pompa eşleştirmesini kaldır_ butonlarını kullanır.
@@ -202,7 +202,7 @@ Belirli uyarılar sürücü tarafından otomatik olarak reddedilir. Bunlar:
- W2 "pil zayıf" : sürücü bunu AAPS ana sekmesinde gösterilen bir "düşük pil" uyarısına dönüştürür
- W3, W6, W7, W8 : bunların tümü kullanıcı için tamamen bilgi amaçlıdır, bu nedenle sürücünün bunları otomatik olarak reddetmesi güvenlidir
-Diğer uyarılar otomatik olarak _yok sayılmaz_. Ayrıca, hatalar _asla_ otomatik olarak reddedilmez. Bunların her ikisi de aynı şekilde ele alınır: Sürücünün AAPS Kullanıcı Arabirimi üzerinde bir uyarı iletişim kutusu oluşturmasına ve ayrıca devam eden herhangi bir komut yürütmeyi iptal etmesine neden olurlar. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#accu-chek-combo-tab-contents)). Bu durum, herhangi bir komut yürütülmesine izin vermez. Kullanıcının pompadaki hatayı halletmesi gerekir; örneğin, bir tıkanma hatası sebebiyle kanülün değiştirilmesini gerekebilir. Kullanıcı hatayı giderdikten sonra, Accu-Chek Combo sekmesindeki "Yenile" düğmesine basarak normal çalışmaya devam edilebilir. Sürücü daha sonra Combo'ya bağlanır ve durumunu günceller, ekranda hala bir hata gösterilip gösterilmediğini vb. kontrol eder. Ayrıca, sürücü bir süre sonra pompa durumunu otomatik olarak yeniler, bu nedenle bu butona manuel olarak basmak zorunlu değildir.
+Diğer uyarılar otomatik olarak _yok sayılmaz_. Ayrıca, hatalar _asla_ otomatik olarak reddedilmez. Bunların her ikisi de aynı şekilde ele alınır: Sürücünün AAPS Kullanıcı Arabirimi üzerinde bir uyarı iletişim kutusu oluşturmasına ve ayrıca devam eden herhangi bir komut yürütmeyi iptal etmesine neden olurlar. The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). Bu durum, herhangi bir komut yürütülmesine izin vermez. Kullanıcının pompadaki hatayı halletmesi gerekir; örneğin, bir tıkanma hatası sebebiyle kanülün değiştirilmesini gerekebilir. Kullanıcı hatayı giderdikten sonra, Accu-Chek Combo sekmesindeki "Yenile" düğmesine basarak normal çalışmaya devam edilebilir. Sürücü daha sonra Combo'ya bağlanır ve durumunu günceller, ekranda hala bir hata gösterilip gösterilmediğini vb. kontrol eder. Ayrıca, sürücü bir süre sonra pompa durumunu otomatik olarak yeniler, bu nedenle bu butona manuel olarak basmak zorunlu değildir.
Bolus özel bir durumdur. Bir uyarının göründüğünü bolus ortasında rapor etmeyen Combo'nun komut modunda yapılır. Sonuç olarak, sürücü bir bolus _sırasında_ uyarıları otomatik olarak kapatamaz. Bu ne yazık ki, bolus bitene kadar pompanın bip sesi çıkaracağı anlamına gelir. En yaygın bolus ortası uyarısı tipik olarak W1 "rezervuar düşük" uyarısıdır. Bir bolus sırasında pompanın kendisindeki Combo uyarılarını manuel olarak **kapatmayın**. Bolusu kesintiye uğratma riskiniz vardır. Bolus bittiğinde sürücü uyarıyı dikkate alacaktır.
@@ -215,8 +215,8 @@ Sürücü Combo'ya bağlı değilken meydana gelen uyarılar, sürücü tarafın
* Özellikle bu sürücünün bir ürün olmadığını unutmayın. Başlarken, kullanıcının sistemi, sınırlamalarını ve başarısız olabileceğini izlemesi ve anlaması gerekir. Kullanan kişi sistemi tam olarak anlayamamışsa bu sistemi KULLANMAMANIZ şiddetle tavsiye edilir.
* Combo'nun uzaktan kumanda işlevselliğinin çalışma şekli nedeniyle, bazı işlemler (özellikle bazal profili ayarlamak) diğer pompalara kıyasla yavaştır. Bu, Combo'nun üstesinden gelinemeyecek talihsiz bir sınırlamasıdır.
* Pompa üzerinden bir GBO (geçici bazal oran) ayarlamayın veya iptal etmeyin. Döngü, GBO'nun kontrolünü programda üstlenir. Aksi takdirde kullanıcı tarafından pompada ayarlanan bir GBO'nun başlangıç zamanını belirlemek mümkün olmadığından güvenilir şekilde çalışamaz.
-* AAPS pompa ile iletişim kurarken pompa üzerinde herhangi bir düğmeye basmayın (AAPS bağlandığında pompada Bluetooth logosu görünür). Bunu yapmak, Bluetooth bağlantısını kesecektir. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#before-you-begin)).
-* Pompa bolus yaparken herhangi bir butona basmayın. Özellikle uyarıları pompa butonlarına basarak kapatmaya çalışmayın. See [the section about alerts](#alerts-warnings-and-errors-and-how-they-are-handled) for a more detailed explanation why.
+* AAPS pompa ile iletişim kurarken pompa üzerinde herhangi bir düğmeye basmayın (AAPS bağlandığında pompada Bluetooth logosu görünür). Bunu yapmak, Bluetooth bağlantısını kesecektir. Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* Pompa bolus yaparken herhangi bir butona basmayın. Özellikle uyarıları pompa butonlarına basarak kapatmaya çalışmayın. See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Combo ile bağlantı kurulamadığında kontrol listesi
diff --git a/docs/CROWDIN/tr/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/tr/CompatiblePumps/DanaRS-Insulin-Pump.md
index 60912f2c9c71..25145e13f57e 100644
--- a/docs/CROWDIN/tr/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/tr/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* Eski şifreyi girmek için Tamam'a basın.
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ Yeni bir telefona geçerken aşağıdaki adımları yapmanız gerekir:
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* Bazen, Dana-i/RS sekmesindeki BT simgesine uzun tıklayarak AAPS'deki eşleştirme bilgilerinin temizlenmesi gerekebilir.
## Dana RS pompasıyla seyahat edenler için saat dilimi
diff --git a/docs/CROWDIN/tr/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/tr/CompatiblePumps/MedtronicPump.md
index ff1edb43a912..8e662a2da6e1 100644
--- a/docs/CROWDIN/tr/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/tr/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ While setting up AAPS to work with your medtronic pump you need to set following
- **Pompa Seri Numarası**: Pompanızın arkasında yer alır ve SN ile başlar. You should only enter the 6 numbers shown without any alphabetic characters (e.g. 123456).
- **Pompa Tipi**: Kullandığınız pompa modeli (ör. 522).
-- **Pompa Frekansı**: Pompanızın ilk dağıtıldığı yere bağlı olarak iki seçenek vardır. Please check the [FAQ](#faq) if you are unsure which option to select):
+- **Pompa Frekansı**: Pompanızın ilk dağıtıldığı yere bağlı olarak iki seçenek vardır. Please check the [FAQ](#MedtronicPump-faq) if you are unsure which option to select):
- ABD & Kanada için (NA-CA) kullanılan frekans 916 Mhz
- Dünya çapında (WW) kullanılan frekans 868 Mhz'dir.
- **Pompadaki Maks Bazal (Ü/s)**: Bunun, pompanızda ayarlanan değerle eşleşmesi gerekir (yukarıdaki pompa konfigürasyonuna bakın). Again this setting must be carefully selected as it will determine how much AAPS can deliver via your basal rate. Bu değer maksimum geçici bazal oranını etkin bir şekilde ayarlayacaktır. Örnek olarak, bu değeri maksimum standart bazal oranınızın dört katına ayarlamak %400 Geçici Bazal Oranına izin verir. Pompa tarafından izin verilen maksimum değer saatte 34,9 ünitedir.
@@ -99,10 +99,10 @@ While setting up AAPS to work with your medtronic pump you need to set following
Ekranın altında üç buton vardır:
- **Yenile**: Pompanın mevcut durumunu yenilemek içindir. Bu buton komple veri yenilediğinden (geçmişi al, zamanı al/ayarla, profil al, pil durumunu al, vb.) yalnızca bağlantı uzun bir süre boyunca kopmuşsa kullanılmalıdır.
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## Pompa geçmişi
@@ -110,7 +110,7 @@ Ekranın altında üç buton vardır:
Pompa geçmişi her 5 dakikada bir alınır ve yerel olarak saklanır. Yalnızca 24 saatlik geçmiş değerler depolanır. The allows for a convenient way to see pump behaviour should that be required. The only items stored are those relevenant to AAPS and will not include a configuration function that has no relevance.
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL Durumu (RileyLink Durumu)
diff --git a/docs/CROWDIN/tr/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/tr/CompatiblePumps/MedtrumNano.md
index 93300d0297d5..1b7e206d846c 100644
--- a/docs/CROWDIN/tr/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/tr/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +128,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +189,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +242,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Genel Bakış
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +349,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. Ör. when suspended due to a maximum daily insulin delivery alarm.
@@ -372,7 +380,7 @@ If you are experiencing connection timeouts or other connection issues:
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md
index 7c2dec03d81b..fa3b324ae7a2 100644
--- a/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ On the top-left hand corner **hamburger menu** select **Config Builder (1)**\
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ Please **swipe left** to the **DASH** tab where you will be able to manage all p
 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Pod Etkinleştirme
@@ -132,7 +133,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
**DASH** sekme ekranına dönmek için telefonunuzdaki geri düğmesini tıklayın. Şimdi aktif pod oturumunuz için mevcut bazal oran, pod rezervuar seviyesi, iletilen insülin, pod hataları ve uyarılar dahil Pod bilgileri görüntülenecektir.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit
It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Pod'u Devre Dışı Bırakma
@@ -176,9 +177,11 @@ To deactivate a pod (either from expiration or from a pod failure):
+(omnipod-dash-resuming-insulin-delivery)=
+
### İnsülin İletimini Sürdür
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
@@ -215,7 +218,7 @@ The process below will show you how to acknowledge and dismiss pod beeps when th
4. **DASH** sekmesine gidin. **Etkin Pod Alarmları** satırında, uyarı mesajı artık görüntülenmez ve etkin pod artık sona erme uyarısı bip sesi vermez.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### Pod Geçmişini Görüntüle
@@ -240,7 +243,7 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH Sekmesi
@@ -275,7 +278,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
* **Rezervuar:** Rezervuarda 50 üniteden fazla insülin olduğuda 50+Ü'den fazla kalanı gösterir. 50 Ü'nin altında, tam birimler görüntülenir.
* **Toplam iletilen:** Rezervuardan iletilen toplam insülin ünite miktarını görüntüler. Bu miktar etkinleştirme ve hazırlama için kullanılan insülini de içerir.
-* **Hatalar:** Karşılaşılan son hatayı görüntüler. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
+* **Hatalar:** Karşılaşılan son hatayı görüntüler. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **Etkin pod alarmları:** Etkin pod alarmlarını gösteren satırdır.
### Butonlar
@@ -303,12 +306,12 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash Ayarları
@@ -388,6 +391,8 @@ Additional note:
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
### İletimi askıya alma
* Artık iletimi askıya alma butonu yok. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
@@ -396,7 +401,7 @@ Additional note:
- Komutlardan birinin onaylanmadığına dair bir bildirim olabilir: bu, hatanın ne zaman gerçekleştiğine bağlıdır.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
* Onaylanmamış komutlar için "pod durumunu yenile" komutu, bunları onaylamalı/reddetmelidir.
diff --git a/docs/CROWDIN/tr/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/tr/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..01d63b0baa4c 100644
--- a/docs/CROWDIN/tr/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/tr/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ See below an example of an Image block for second_hand, (in this case there are
"color": "#BC906A"
}
```
-To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest ligne with the keyValue `bgColor`
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/tr/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/tr/Maintenance/UpdateAaps3204.md
index 8e12ffbebec4..8a16998ed583 100644
--- a/docs/CROWDIN/tr/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/tr/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# Updating to AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/tr/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuild.md
index e16fdd8c4f75..059816185c82 100644
--- a/docs/CROWDIN/tr/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/tr/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/tr/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/tr/index.md b/docs/CROWDIN/tr/index.md
index f1cd18dcd201..ed33c741913f 100644
--- a/docs/CROWDIN/tr/index.md
+++ b/docs/CROWDIN/tr/index.md
@@ -90,6 +90,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -146,6 +148,8 @@ Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/zh_CN/AdvancedOptions/Autotune.md b/docs/CROWDIN/zh_CN/AdvancedOptions/Autotune.md
index a7c2f80e639d..2f7a8883c706 100644
--- a/docs/CROWDIN/zh_CN/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/zh_CN/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune插件是OpenAPS自动调节算法在AAPS中的具体实现。
- 点击"对比配置文件"按钮将打开配置文件对比视图。 输入配置文件以蓝色标识，优化输出配置文件（标为"Tuned"）则以红色显示。
- - 注意：下例所示输入配置文件中的胰岛素碳水化合物比值（IC）与胰岛素敏感系数（ISF）均呈现昼夜节律变化，但经计算输出的优化配置文件将生成单一参数值。 若需获取昼夜节律性输出配置文件，请参阅下方[昼夜节律IC/ISF配置文件](#circadian-ic-or-isf-profile)说明。
+ - 注意：下例所示输入配置文件中的胰岛素碳水化合物比值（IC）与胰岛素敏感系数（ISF）均呈现昼夜节律变化，但经计算输出的优化配置文件将生成单一参数值。 If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
@@ -86,13 +86,13 @@ Autotune插件是OpenAPS自动调节算法在AAPS中的具体实现。
-- 自动化切换配置文件功能（默认关闭）：详见下方[通过自动化规则运行Autotune](#run-autotune-with-an-automation-rule)说明。 若将此设置切换为"开启"状态，系统将自动使用优化配置文件（Tuned profile）更新输入配置文件，并自动激活更新后的配置。
+- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#autotune-run-autotune-with-an-automation-rule) below. 若将此设置切换为"开启"状态，系统将自动使用优化配置文件（Tuned profile）更新输入配置文件，并自动激活更新后的配置。
- **警告：在随后数日内，您必须对未经修改即更新激活的优化配置文件（Tuned profile）进行持续验证，确保其确实能提升闭环系统运行效果。**
- 将未标记餐食（UAM）归类为基础率（默认开启）：本设置适用于使用AndroidAPS时未输入任何碳水化合物数据（完全UAM模式）的用户。 当设置为"关闭"时，系统将禁止将未标记餐食（UAM）归类为基础率。
- 注意：若系统在一天内检测到至少1小时的碳水化合物吸收活动，则无论当前设置为"开启"或"关闭"，所有标记为"未标记餐食（UAM）"的数据都将被归类为基础率。
- 数据采集天数（默认5天）：您可通过此设置定义默认值范围。 每当在Autotune插件中选择新配置文件时，"优化天数"参数将自动重置为此默认值。
-- 昼夜节律IC/ISF均值应用功能（默认关闭）：详见下方[昼夜节律IC/ISF配置文件](#circadian-ic-or-isf-profile)说明。
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
### 其他设置
diff --git a/docs/CROWDIN/zh_CN/AdvancedOptions/DevBranch.md b/docs/CROWDIN/zh_CN/AdvancedOptions/DevBranch.md
index c8998480ab63..e12404542353 100644
--- a/docs/CROWDIN/zh_CN/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/zh_CN/AdvancedOptions/DevBranch.md
@@ -62,6 +62,6 @@ Available from 3.3.2.1.dev
- Select the variant you need:
- fullRelease: For regular pump usage with full functionality.
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
- pumpcontrol
- Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/zh_CN/AdvancedOptions/FullClosedLoop.md
index 94227439c5ec..c283fe6ebad2 100644
--- a/docs/CROWDIN/zh_CN/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/zh_CN/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@
在**FCL**中，不再需要根据餐量推注胰岛素：将工作交给算法！ **AAPS** 可能允许用户不进行任何餐前大剂量注射，也不输入碳水化合物，这在一种称为“未声明膳食”（**‘UAM’**）的模式下进行。 **UAM** 通过更积极的方式，使 **AAPS** 能够更好地容忍不正确的碳水化合物输入。
-### 期望什么？
+## What to expect?
已有许多关于**FCL**积极效果的研究发表。 如需进一步阅读，请参阅以下内容：
@@ -22,7 +22,7 @@
- 微调**AAPS**设置（特别是**自动化规则**）。
-### 从HCL转向FCL的总体考量
+## General considerations why (not to) move from HCL to FCL
**FCL**并不适合所有人：
@@ -32,7 +32,7 @@
- 为儿童建立 **FCL** 仍然存在困难（下文讨论）。
-### 良好调校的混合闭环
+## Well-tuned hybrid closed loop
在考虑转向**FCL**前，建议先建立良好调校的**HCL**。 **FCL**成功需要高度个性化的设置调校，使**AAPS**能通过胰岛素输送精确模拟您成功的混合闭环模式。
@@ -40,7 +40,7 @@
**FCL是通过分析用户成功的HCL数据和初始FCL体验，自行设置自动化规则的过程。**
-### 速效胰岛素 (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
**FCL**需要速效胰岛素。 这是为了在进餐相关**血糖**上升初期，**FCL**能通过常规定义（低于180 mg/dl（10 mmol/l））保持**血糖**在范围内。
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
然而，即使在优化了诸如针头长度之类的事情之后，Fiasp 或 Lyumjev 仍可能导致频繁的泵阻塞。 密切关注套管或储药器的时间非常重要。 许多用户发现 48 小时是胰岛素在导致套管/储药器故障之前的有效极限。
-### 先决条件
+## Prerequisites
需要稳定的血糖值和蓝牙连接确保**AAPS**最佳性能，避免损失宝贵时间。 **FCL**需要24/7技术稳定系统：
@@ -76,13 +76,13 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
以上内容会因您的 **AAPS** 组件系统和您的生活方式而异。
-### 与膳食相关的限制
+## Meal-related limitations
- 对饮食中不含快速影响**血糖**成分且每日餐型变化不大的用户，设置**FCL**可能更容易。 这并不一定意味着低碳水化合物。
- 高脂肪或高蛋白饮食，或慢消化/胃轻瘫，反而使**FCL**更容易实施，因为后期碳水化合物能很好覆盖推注胰岛素不可避免的"尾部"效应。
-#### 升糖指数与血糖影响
+### 升糖指数与血糖影响
**UAM**模式的挑战随着"对血糖影响（EBG）"增加而增加：
@@ -98,7 +98,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
随意摄入富含快速吸收碳水化合物的零食和甜饮会给**FCL**带来问题。
-#### 为活动/运动做准备
+## Preparing for activity/sports
在使用泵或混合闭环进行锻炼或活动时，建议用户在锻炼前减少 **IOB**。
@@ -106,7 +106,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
异常或不定期的运动水平会给**FCL**带来困难。 锻炼需要提前计划（特别是如果您想减少运动期间低血糖时对急救碳水化合物/零食的需求）。 在活动一天后，建议在晚餐完全消化后为夜间设置较低的**百分比配置文件**：在**自动化**中设置一个升高（>100 mg/dl）的**BG** 目标，并在 ***AAPS*** 首选项中选择“在升高目标时不使用 **SMB**”。
-#### 孩子们的障碍
+## Hurdles for kids
**FCL** 可能给儿童带来额外的挑战，其中包括：
@@ -116,7 +116,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
- 生长激素和胰岛素敏感性显著变化使**FCL**难以准确调校。
-## 启用增强型 SMB：安全性
+## Enabling boosted SMBs: safety
在**HCL**中实施了关于闭环自动推注量的安全限制。
@@ -141,7 +141,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
您的**AAPS**设置必须充分适应您的各种餐食。
```
-## 进餐检测/您的增强自动化规则
+## Meal detection/your Automations for boosting
**FCL**成功的关键调校参数是**ISF**。 当使用 **AAPS** Master + **自动化**时，**必须在识别到膳食时（通过葡萄糖增量）自动触发 > 100% 的配置文件更改**，并提供强化的 **ISF**。
@@ -151,7 +151,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
- 第2步 - 应用系数（1/配置文件%，在**自动化规则**中设置）增强**ISF**。
- 步骤 3 - 检查建议的 **ISF** 是否在设定的安全限制范围内。
-### FCL 的自动化模板
+### FCL's Automation templates
顶部的复选框。 您可以选择：
@@ -163,7 +163,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
下文指导如何组合**自动化规则**条件，以及如何处理**AAPS**需要增加/减少胰岛素输送的情况。 由于 **ISF** 不能直接调整，因此将**配置文件百分比**提高到 100% 以上将达到我们的目的。
-### 在血糖上升时自动进行大剂量SMB。
+### Automated big SMBs at bg rise
**FCL**成功的关键在于：**在餐后血糖开始上升时，闭环必须尽快给予非常大的自动SMB**"追赶"所需**IOB**（与您在**HCL**中对类似餐食的典型推注量比较！）
@@ -206,7 +206,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
**AAPS**主屏幕（**UAM**全闭环下显示cob=0）在此阶段可能提示需要更多碳水。 在**UAM**模式下，这仅需简单合理性检查：这些碳水是否可能来自约1小时前进餐未吸收的部分？
-### iob 阈值
+### iob threshold
通常规则#1和/或#2使IOB升至足够高度。 个性化调校需查看**HCL**数据中管理良好餐食（通常是您的餐时推注）的最大IOB值，以及超过该值后出现低血糖（或需要额外碳水）的情况。
@@ -235,7 +235,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
如果您的早餐碳水化合物含量与您的平均晚餐有很大差异，您可能会受益于定义适用于一天中相应时间的**自动化**，并具有不同的 **iobTH**（可能还有不同的增量和不同的**百分比配置文件**设置）。 您通过定义餐谱和设置（特别是IOB阈值）与闭环共同管理**血糖**曲线，必须接受某些峰值高度以减少DIA末期的低血糖风险。
-### 高血糖值的停滞状态
+### Stagnation at high bg values
若在享用丰盛餐食后，出现**高血糖（BG）**值长期停滞的情况，可启用**自动化**方案#6（左下方所示）——"餐后高血糖"模式，该方案专门应对脂肪酸抵抗现象：在食用多道菜正餐、大量油脂披萨或奶酪火锅晚餐后，血糖曲线可能呈现双峰形态，或更常见表现为长时间的高位平台期。
@@ -251,7 +251,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
此外，还需要一个终止自动化 #5，“停止 pmH”，以便在血糖值下降时降低胰岛素给药的激进程度。 （但闭环通常因预测血糖走低而限制更多胰岛素）。
-### 低血糖预防
+## Hypo prevention
核心问题是**UAM** **FCL**（无碳水输入）无法知道还有多少克碳水待吸收，可能用完"尾部"胰岛素导致低血糖。
@@ -274,7 +274,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
随时间推移，您将学习模式、调校规则——甚至调整饮食习惯，例如偶尔享用帮助维持胰岛素活性和碳水吸收平衡的后期小零食，使闭环（和您自己）更轻松。
-### 自动化规则顺序
+### Order of programmed Automations
当**自动化规则**中存在定义重叠时，可能引发系统逻辑冲突。 示例：当Δ值>8mmol/L同时满足Δ值>5mmol/L时（即两条相互冲突的**自动化规则**同时被触发），闭环系统将如何执行？ 闭环系统始终依据**自动化规则**在汉堡菜单/AAPS主界面中的显示顺序执行决策。 示例：必须将Δ值>+8mmol/L的规则置于首位（当所有条件满足时触发最强调节），随后再检查Δ值>5mmol/L的情况（并执行较温和的响应）。 若顺序颠倒，Δ值>8mmol/L的规则将永远无法生效——因为系统会优先执行已适用的Δ值>5mmol/L规则并终止判断流程。
> 自动化提示：顺序更改非常容易。 在**AAPS/自动化**界面中，长按列表条目即可将指定的**自动化规则**重新排序至其他位置。
@@ -283,7 +283,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
## 故障排除
-### 如何恢复到混合闭环
+### How to get back into Hybrid Closed Loop
您可取消勾选**自动化规则**中与**FCL**相关的顶部复选框，即可恢复餐时大剂量注射功能并重新启用碳水化合物输入。 您可能需要进入**AAPS**的偏好设置/概览/按钮选项，为主屏幕重新启用"胰岛素"、"计算器"等按钮功能。 请注意：现在又需要您自行注射餐前大剂量胰岛素了。
@@ -293,13 +293,13 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
-### FCL前提条件是否仍满足？
+### Are the pre-conditions for FCL still given?
- 基本**配置文件**是否仍然正确？
- **CGM**质量是否下降
- 参考先决条件（上文）
-### 血糖过高
+### Glucose goes too high
- 餐食未被及时识别
- 检查蓝牙稳定性
@@ -313,7 +313,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
> 如果你已准备好使用AAPS开发版本，也可以选用支持进一步扩大SMB剂量的变体。 部分用户还会在其"FCL"中使用少量预注射剂量。 然而，这种做法会影响血糖曲线的形态，进而干扰对血糖上升的检测以及触发的**SMB**效果，因此难以实施且难以带来显著的整体效益。
- 试点用户的一个重要观察是：血糖曲线与活性胰岛素(iob)曲线在进食初期的走向，对碳水摄入后的峰值高度影响极大： 若呈下降趋势（例如接近预设的"即将进食临时目标"EatingSoonTT），同时积累适量活性胰岛素，且曲线已呈现强劲的正向加速态势，将显著有助于压低血糖峰值。
-### 血糖过低
+### Glucose goes too low
- 误识别餐食
- 检查您是否可以设置更大的增量来触发第一个 **SMB**
@@ -330,7 +330,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
- 这可能意味着您需要接受更高的**血糖**峰值以避免低血糖。 或者调整饮食结构——减少碳水化合物摄入，同时增加蛋白质和脂肪的比例。
-### 更多信息
+### More info
建议保持与其他**FCL**用户交流。
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/Juggluco.md b/docs/CROWDIN/zh_CN/CompatibleCgms/Juggluco.md
index ca2049823a2d..b675db2f2f7e 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
+(juggluco-to-aaps)=
+
## Juggluco to AAPS
Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+(juggluco-to-xdrip)=
+
## Juggluco to xDrip+
Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/Libre3.md b/docs/CROWDIN/zh_CN/CompatibleCgms/Libre3.md
index aab547640ea0..53e4b6ecbc12 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Freestyle Libre 3 (FSL3) 需要特殊设置才能将血糖值传输至AAPS系统
## Method 1: use 1-minute readings directly
AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations.
-
+See [here](#juggluco-to-aaps).
## Method 2: convert 1-minute readings into 5-minute values via xDrip
@@ -28,8 +28,6 @@ AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute valu
请确保将血糖值发送至xDrip+：在Juggluco的设置中，您可将其配置为向其他应用程序发送血糖值。 Juggluco可发送三种广播类型：**修改版Libre广播**最初由修改版Librelink应用使用，可用于向xDrip+发送血糖值。
-
-
### 步骤 2：设置 xDrip
智能手机上的xDrip+应用程序会接收到这些血糖数值。
@@ -58,10 +56,10 @@ AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute valu
### 步骤 4：配置 AndroidAPS
-- 在[ConfigBuilder, BG Source](#Config-Builder-bg-source)中选择xDrip+。
+- See [here](#juggluco-to-xdrip) and come back.
- 当手机处于飞行模式时若AndroidAPS未接收到血糖值，请使用"识别接收器"功能。
-- 关闭平滑处理（已在xDrip+中完成）
+- Turn off Smoothing (done in xDrip+ already)
## 后续传感器更换
diff --git a/docs/CROWDIN/zh_CN/CompatiblePhones/Jelly.md b/docs/CROWDIN/zh_CN/CompatiblePhones/Jelly.md
index dacecb5db07a..59667a7b4f10 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index aebc86fff467..bcc7064ad8a2 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ Combo可通过蓝牙在_远程终端_模式或_指令_模式下运行。 远程
（用户无法干预该行为；驱动程序完全自主决定使用何种模式。 此处说明仅为让用户了解为何有时能在该区域看到Combo界面。）
-最底部设有"刷新"按钮。 点击该按钮可立即触发泵体状态更新。 该按钮还用于通知AAPS先前发现的错误已修复，可重新检查系统状态是否正常（详见下文[警报相关章节](#alerts-warnings-and-errors-and-how-they-are-handled)）。
+最底部设有"刷新"按钮。 点击该按钮可立即触发泵体状态更新。 It also is used to let AAPS know that a previously discovered error is now fixed and that AAPS can check again that everything is OK (more on that below in [the section about alerts](#combov2-alerts)).
## 偏好设置
@@ -176,8 +176,8 @@ Combo可通过蓝牙在_远程终端_模式或_指令_模式下运行。 远程
1. _与泵体配对_：点击此按钮可与Combo建立配对。 若已配对泵体，该按钮将自动禁用。
2. _解除泵体配对_：断开已配对的Combo连接；与第1项功能完全相反。 若未配对泵体，该按钮将自动禁用。
3. _设备发现时长（秒）_：配对时，驱动程序使手机能被泵体检测到。 此项控制设备可被发现的持续时间。 默认选择最大值（300秒=5分钟）。 Android系统不允许无限期保持可发现状态，因此必须设定具体时长。
-4. _自动检测并执行储药器更换操作_：若启用，通常由用户通过"操作"标签页中"填充/灌注"按钮完成的"储药器更换"动作将自动执行。 具体说明详见[下文详解](#autodetecting-and-automatically-entering-battery-and-reservoir-changes)。
-5. _自动检测并执行电池更换操作_：若启用，通常由用户通过"操作"标签页中"泵体电池更换"按钮完成的"电池更换"动作将自动执行。 具体说明详见[下文详解](#autodetecting-and-automatically-entering-battery-and-reservoir-changes)。
+4. _自动检测并执行储药器更换操作_：若启用，通常由用户通过"操作"标签页中"填充/灌注"按钮完成的"储药器更换"动作将自动执行。 This is explained [in further detail below](#combov2-autodetections).
+5. _自动检测并执行电池更换操作_：若启用，通常由用户通过"操作"标签页中"泵体电池更换"按钮完成的"电池更换"动作将自动执行。 This is explained [in further detail below](#combov2-autodetections).
6. _启用Combo详细日志记录_：该选项将大幅增加驱动程序生成的日志数据量。 **注意**：除非开发者要求，否则请勿启用此选项。 否则可能大幅增加AndroidAPS日志冗余信息，降低日志可用性。
大多数用户仅使用顶部两项功能：_与泵体配对_和_解除泵体配对_按钮。
@@ -202,7 +202,7 @@ Combo通过远程终端界面显示警报信息。 警告信息以"Wx"代码（x
- W2 "电池电量低"：驱动程序将其转换为AAPS主界面显示的"低电量"警告
- W3、W6、W7、W8：此类警告仅向用户提供参考信息，驱动程序可安全执行自动消除
-其余警告_不会_被自动消除。 此外，错误信息_绝不_会自动消除。 这两类警报采用相同处理机制：触发后驱动程序将在AAPS界面弹出警示对话框，并立即终止所有正在执行的指令。 随后驱动程序将切换至"错误"状态（详见[上文Accu-Chek Combo标签页说明](#accu-chek-combo-tab-contents)）。 该状态下禁止执行任何指令。 用户须在胰岛素泵上处理错误，例如发生输注阻塞错误时可能需要更换输注管路。 用户处理完错误后，点击Accu-Chek Combo标签页的"刷新"按钮即可恢复正常操作。 驱动程序将重新连接Combo并更新状态，检查屏幕是否仍显示错误信息等。 此外，驱动程序会定期自动刷新胰岛素泵状态，因此并非必须手动点击该按钮。
+其余警告_不会_被自动消除。 此外，错误信息_绝不_会自动消除。 这两类警报采用相同处理机制：触发后驱动程序将在AAPS界面弹出警示对话框，并立即终止所有正在执行的指令。 The driver then switches to the "error" state (see [the Accu-Chek Combo tab contents description above](#combov2-tab-contents)). 该状态下禁止执行任何指令。 用户须在胰岛素泵上处理错误，例如发生输注阻塞错误时可能需要更换输注管路。 用户处理完错误后，点击Accu-Chek Combo标签页的"刷新"按钮即可恢复正常操作。 驱动程序将重新连接Combo并更新状态，检查屏幕是否仍显示错误信息等。 此外，驱动程序会定期自动刷新胰岛素泵状态，因此并非必须手动点击该按钮。
大剂量注射属于特殊情况。 该操作在Combo的命令模式下执行，此模式不会在注射过程中报告出现的警报。 因此，驱动程序_无法_在大剂量注射期间自动消除警告。 这意味着胰岛素泵将持续发出蜂鸣声直至大剂量注射完成。 大剂量注射期间最常见的警报通常是W1"储药器余量低"。 **切勿**在大剂量注射过程中手动消除胰岛素泵上的Combo警告。 此操作可能导致大剂量注射中断。 驱动程序将在大剂量注射完成后处理该警告。
@@ -215,8 +215,8 @@ Combo通过远程终端界面显示警报信息。 警告信息以"Wx"代码（x
* 请注意这并非商业化产品，尤其在初始阶段，用户需持续监控并充分理解系统功能、使用限制及潜在故障模式。 强烈建议不具备完全理解该系统能力的人员不要使用。
* 由于Combo远程控制功能的工作原理，多项操作（特别是设置基础率配置文件）相比其他胰岛素泵更为缓慢。 这是Combo无法克服的固有缺陷。
* 切勿在胰岛素泵上设置或取消临时基础率。 闭环系统需完全掌控临时基础率，否则无法可靠运行，因无法确定用户在胰岛素泵上设置的临时基础率起始时间。
-* 当AAPS与胰岛素泵通信时（泵体显示蓝牙标识期间），请勿操作泵体任何按键。 此操作将中断蓝牙连接。 仅当建立连接出现问题时方可操作（参见[上文"使用前准备"章节](#before-you-begin)）。
-* 大剂量注射期间请勿操作任何按键。 特别提醒：切勿通过按键操作来消除警报。 具体原因详见[警报相关章节](#alerts-warnings-and-errors-and-how-they-are-handled)的详细说明。
+* 当AAPS与胰岛素泵通信时（泵体显示蓝牙标识期间），请勿操作泵体任何按键。 此操作将中断蓝牙连接。 Only do that if there are problems with establishing a connection (see [the "Before you begin" section above](#combov2-before-you-begin)).
+* 大剂量注射期间请勿操作任何按键。 特别提醒：切勿通过按键操作来消除警报。 See [the section about alerts](#combov2-alerts) for a more detailed explanation why.
## Combo无法建立连接时的排查清单
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/zh_CN/CompatiblePumps/DanaRS-Insulin-Pump.md
index 75896ba4172d..cd0948d6bebd 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* 按确定输入旧密码。
-* 输入<0>旧密码（默认密码见<1>上），然后按确定
+* Enter **old password** (Default password see [above](#DanaRS-Insulin-Pump-default-password)) and press OK
@@ -130,7 +130,7 @@ orphan: true
### DanaRS v3, Dana-i
-* 按[上文](#pairing-pump)所述步骤启动配对程序。
+* Start pairing procedure as described [above](#DanaRS-Insulin-Pump-pairing-pump).
* 有时需长按Dana-i/RS标签页的蓝牙图标清除AAPS中的配对信息。
## 使用Dana RS泵进行跨时区旅行
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtronicPump.md
index e1355220c228..b3d69e141d48 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ orphan: true
- **泵序列号**：显示在泵背面，以SN开头。 只需输入显示的6位数字，无需输入任何字母字符（例如123456）。
- **泵型号**：您正在使用的泵型号（例如522）。
-- **泵频率**：根据泵的原始销售地区有两种选项。 如不确定选择哪个选项，请查阅[常见问题](#faq)）：
+- **泵频率**：根据泵的原始销售地区有两种选项。 Please check the [FAQ](#MedtronicPump-faq) if you are unsure which option to select):
- 美国及加拿大地区使用的频率为916 MHz
- 全球其他地区使用的频率为868 MHz
- **泵上最大基础率（单位/小时）**：必须与泵上的设置保持一致（参见上文泵配置部分）。 此设置必须谨慎选择，因为它将决定AAPS能通过基础率输送多少胰岛素。 这将实际设定临时基础率的最大值。 例如，将此值设为标准最大基础率的四倍，将允许400%的临时基础率。 泵允许的最大值为每小时34.9单位。
@@ -99,10 +99,10 @@ orphan: true
屏幕底部有三个按钮：
- **刷新**用于刷新泵的当前状态。 仅当连接长时间中断时才应使用此功能，因为这将需要完整的数据刷新(检索历史记录、获取/设置时间、获取配置文件、获取电池状态等)。
-- **泵历史记录**：显示泵历史记录（参见[下文](#pump-history)）
-- **RL统计**：显示RL统计信息（参见[下文](#rl-status-rileylink-status)）
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## 泵历史记录
@@ -110,7 +110,7 @@ orphan: true
泵历史记录每5分钟检索一次并存储在本地。 仅存储最近24小时的历史记录。 这为查看泵行为（如有需要）提供了便捷方式。 仅存储与AAPS相关的项目，不包括无关的配置功能。
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL状态(RileyLink状态)
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md
index 0ae1968d1aa5..d89074b02d9a 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ orphan: true
***默认值：25单位。***
-此设置将修改每小时的最大胰岛素输注量。 若超过此限制，贴片将暂停输注并发出警报。 可通过概览菜单中的[重置警报](#reset-alarms)按钮来解除警报。
+此设置将修改每小时的最大胰岛素输注量。 若超过此限制，贴片将暂停输注并发出警报。 The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
请根据您的胰岛素需求设置合理数值。
@@ -128,7 +128,7 @@ orphan: true
***默认值：80单位。***
-此设置将修改每日最大胰岛素输注量。 若超过此限制，贴片将暂停输注并发出警报。 可通过概览菜单中的[重置警报](#reset-alarms)按钮来解除警报。
+此设置将修改每日最大胰岛素输注量。 若超过此限制，贴片将暂停输注并发出警报。 The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
请根据您的胰岛素需求设置合理数值。
@@ -189,9 +189,9 @@ orphan: true
#### 从移宇概览标签页激活贴片
-在AAPS界面中导航至[移宇标签页](#overview)，并点击右下角的**更换贴片**按钮。
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-如果已有贴片处于激活状态，系统将提示您先停用当前贴片。 请参阅[停用贴片](#deactivate-patch)。
+如果已有贴片处于激活状态，系统将提示您先停用当前贴片。 see [Deactivate Patch](#nano-deactivate-patch).
请按照提示操作，完成新贴片的填充和激活。 请注意 - 必须严格按提示步骤操作，仅在系统提示时才能将泵底座与储药贴片连接。 **必须严格遵照激活流程提示操作，仅当完成预充程序后系统提示时，方可将泵体佩戴至身上并插入导管。**
@@ -242,9 +242,11 @@ orphan: true
点击**确定**返回主界面。
+(nano-deactivate-patch)=
+
### 停用贴片
-要停用当前激活的贴片，请进入AAPS界面中的[移宇标签页](#overview)，然后点击**更换贴片**按钮。
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +260,11 @@ orphan: true
停用完成后，点击**确定**返回主界面，或点击**下一步**继续新贴片激活流程。
+(nano-resume-interrupted-activation)=
+
### 继续中断的激活
-若贴片激活流程被中断（例如因手机电量耗尽），可通过进入AAPS界面中的[移宇标签页](#overview)并点击**更换贴片**按钮来恢复激活流程。
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +274,8 @@ orphan: true
驱动程序将尝试检测当前贴片激活状态。 若检测成功，系统将从当前步骤继续激活流程。
+(nano-overview)=
+
## 概览
该概览显示移宇贴片的当前状态。 同时包含更换贴片、重置警报和刷新状态的按钮。
@@ -343,6 +349,8 @@ orphan: true
此按钮将启动更换贴片流程。 详见[激活贴片](#medtrum-activate-patch)获取更多信息。
+(nano-reset-alarms)=
+
### 重置警报
当存在可重置的激活警报时，警报按钮将显示在概览屏幕上。 按下此按钮将重置警报，若贴片因警报暂停，将恢复胰岛素输注。 例如 当日胰岛素最大输注量警报触发暂停时。
@@ -372,7 +380,7 @@ orphan: true
### 激活中断
-若激活流程因手机电量耗尽或系统崩溃等原因中断。 可通过进入更换贴片界面，按此处所述步骤继续激活流程：[恢复中断的激活](#resume-interrupted-activation)
+若激活流程因手机电量耗尽或系统崩溃等原因中断。 The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### 预防贴片故障
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md
index 18c4452e320a..973968d3a32f 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ orphan: true
勾选**设置齿轮图标(3)**旁的**复选框(4)**后，DASH菜单将作为标签页显示在**AAPS**界面中，标题为**DASH**。 勾选此选项后，您在使用**AAPS**时将能更便捷地调用DASH指令功能。
-**注意：** 您可在本文档的DASH设置章节找到更快捷访问[**Dash设置**](#dash-settings)的方法。
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
@@ -83,6 +83,7 @@ orphan: true
 "储药器管理"（激活、停用、测试蜂鸣音、查看使用记录）
+(omnipod-dash-activate-pod)=
### 激活Pod
@@ -132,7 +133,7 @@ orphan: true
点击手机返回键回到**DASH**标签页，该界面现在将显示当前使用中储药器的信息，包括基础率设定值、储药器剩余量、已输注胰岛素量、储药器报错及警报等内容。
- 有关显示信息的更多详情，请参阅本文档[**DASH标签页**](#dash-tab)部分。
+ For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.
@@ -141,7 +142,7 @@ orphan: true
建议在激活储药器后导出设置。 应在每次更换储药器时导出设置，并每月将导出文件备份至云存储。 参见[**导出设置文档**](../Maintenance/ExportImportSettings.md)。
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### 停用Pod
@@ -176,9 +177,11 @@ orphan: true
+(omnipod-dash-resuming-insulin-delivery)=
+
### 恢复胰岛素输注
-**注意**：在执行**配置文件切换**时，DASH必须先暂停输注才能设置新的基础**配置文件**，因为输注功能可能被暂停。 详情请参阅故障排除章节中的[**输注暂停**](#delivery-suspended)部分。
+**注意**：在执行**配置文件切换**时，DASH必须先暂停输注才能设置新的基础**配置文件**，因为输注功能可能被暂停。 Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
此指令用于命令当前暂停中的储药器恢复胰岛素输注。 指令成功执行后，系统将根据当前激活的基础**配置文件**，按当前时间对应的基础率恢复胰岛素正常输注。 储药器将重新接受大剂量注射、**临时基础率**和**超微大剂量**指令。
@@ -215,7 +218,7 @@ orphan: true
4. 请进入**DASH**标签页。 在**使用中储药器警报**字段下，警告信息不再显示，且使用中的储药器将不再发出到期警告提示音。
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### 查看 Pod 历史
@@ -240,7 +243,7 @@ orphan: true
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH标签页
@@ -275,7 +278,7 @@ orphan: true
* **储药量：**当储药器剩余药量超过50单位时，显示"50+单位剩余"。 低于50单位时，将显示精确剩余药量。
* **总输注量：**显示储药器已输送的胰岛素总量（单位）。 该数值包含激活储药器和管路填充所消耗的胰岛素。
-* **错误信息：**显示最近发生的错误。 请查阅[储药器历史记录](#view-pod-history)和日志文件以获取过往错误详情及更完整的信息。
+* **错误信息：**显示最近发生的错误。 Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
* **活动储药器警报：** 保留用于当前活动储药器上正在运行的警报。
### 按钮
@@ -303,12 +306,12 @@ orphan: true
-* 2 - [**激活储药器**](#activate-pod)：对新储药器进行管路填充和激活操作。
-* 3 - [**停用储药器**](#deactivate-pod)：停用当前活动中的储药器。
+* 2 - [**Activate Pod**](#omnipod-dash-activate-pod) : Primes and activates a new pod.
+* 3 - [**Deactivate Pod**](#omnipod-dash-deactivate-pod) : Deactivates the currently active pod.
* 4 - **播放测试提示音**：按下时使储药器发出单次测试提示音。
-* 5 - [**储药器历史记录**](#view-pod-history)：显示活动储药器的操作历史记录。
+* 5 - [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history.
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## DASH设置
@@ -388,6 +391,8 @@ DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器(
## 故障排除
+(omnipod-dash-delivery-suspended)=
+
### 输注暂停
* 不再设有暂停按钮。 如需"暂停"储药器，可设置持续时间为X分钟的零值**临时基础率(TBR)**。
@@ -396,7 +401,7 @@ DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器(
- 系统可能显示某条指令未确认的通知（具体取决于通信失败发生的时机）。
- **AAPS**将每15分钟尝试设置新的基础率配置文件。
- 若输注仍处于暂停状态（恢复输注失败），**AAPS**将每15分钟显示一次输注暂停的提醒通知。
- - 若用户选择手动恢复输注，[**恢复输注**](#resuming-insulin-delivery)按钮将处于激活状态。
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- 若**AAPS**自动恢复输注失败（当储药器无法连接、静音等情况发生时），储药器将每分钟发出4次蜂鸣、持续3分钟；若暂停状态超过20分钟仍未恢复，则每15分钟重复此警报模式。
* 对于未确认的指令，"刷新储药器状态"操作可予以确认或否决。
diff --git a/docs/CROWDIN/zh_CN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/zh_CN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 3f8204ac060f..a8a4d30fecb4 100644
--- a/docs/CROWDIN/zh_CN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/zh_CN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ JSON文件可通过记事本（或notepad++）文本编辑器编辑（推荐能
"color": "#BC906A"
}
```
-要使秒针(second_hand)显示默认血糖颜色（低/中/高范围），只需将最后一行键值改为`bgColor`即可。
+To have second_hand colored with default BG color (lowRange, midRange or highRange), you just have to modify the latest line with the keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/zh_CN/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/zh_CN/Maintenance/UpdateAaps3204.md
index 4aa6859a21b2..158dabcdb13b 100644
--- a/docs/CROWDIN/zh_CN/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/zh_CN/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# 更新至AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuild.md
index e86fea03a2f9..383fd9731cb1 100644
--- a/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 1 – Generate JKS
- Suitable for first-time users, or those without a JKS, or who have forgotten the password or alias.
- Here are examples using multiple platforms below.
+- Select your platform in the list below, between Android (preferred choice), iOS or Computer.
-(aaps-ci-option1-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - Compatible with iOS (using iPad as an example)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} Computer
(aaps-ci-option1-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
+:::{include} BrowserBuildO1C.md
+:::
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
-
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- As described in the video, please copy it to the corresponding field.
@@ -178,69 +123,28 @@ The AAPS app will be saved in your Google Cloud drive once built:
### AAPS-CI Option 2 – Upload Existing JKS
- Suitable for users who already have a JKS and know the JKS password and alias.
- Here are examples using multiple platforms below.
+ - Select your platform in the list below, between Android (preferred choice) or Computer)
-(aaps-ci-option2-android)=
- - Compatible with Android(The simplest, recommended as the first choice)
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- Use a computer (supports Windows/Mac/Linux)
-
- Open the webpage https://simplewebserver.org/download.html
-
- Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
-
- Example on Mac:
-
- - get → install → open 
-
- - Click Get Started 
-
- - Click Get Server 
- - In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+```{tab-set}
- - Seeing this screen means the server has been started. 
-
- - Do not close Simple HTTP 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.
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} Computer
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- As described in the video, please copy it to the corresponding field.
-- For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, please enter your actual password and alias in GitHub.
+- For `KEYSTORE_PASSWORD`, `KEY_ALIAS`, and `KEY_PASSWORD`, please enter your actual password and alias in GitHub.
@@ -290,7 +194,7 @@ Customizations are usually not necessary. This is for your information ony.
(aaps-ci-troubleshooting)=
## AAPS-CI Troubleshooting
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation web page
- When you open aaps-ci-preparation.html using a file manager, it will start a temporary local server on your phone to display the webpage and receive the Google refresh token.
- If you see the screen below, it means you have been inactive for a while, and the file manager has already shut down the local server.
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..e9ac0ebdf119
--- /dev/null
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..91163591a7ec
--- /dev/null
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..90325cdc5d2d
--- /dev/null
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with iOS (using iPad as an example)
+
+
+
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..d3aa40cf46ee
--- /dev/null
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+Compatible with Android (The simplest, recommended as the first choice)
+
+
+
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..0cbac400948c
--- /dev/null
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+Use a computer (supports Windows/Mac/Linux)
+
+Open the webpage [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+Install Simple HTTP Server If you are a Windows/Mac user, you can install it from the store. After clicking the link, you will be asked whether to allow opening it. Please choose Open Link. 
+
+Example on Mac:
+
+- get → install → open 
+
+- Click Get Started 
+
+- Click Get Server 
+
+- In Folder Path, select the folder where aaps-ci-preparation.html is located, and then click Create Server. 
+
+- Seeing this screen means the server has been started. 
+
+- Do not close Simple HTTP 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.
+
+
+
diff --git a/docs/CROWDIN/zh_CN/index.md b/docs/CROWDIN/zh_CN/index.md
index 9ea680972652..2bef19e76661 100644
--- a/docs/CROWDIN/zh_CN/index.md
+++ b/docs/CROWDIN/zh_CN/index.md
@@ -83,19 +83,21 @@ AAPS简介 <./Getting-Started/Introduction.md>
```
```{toctree}
-:caption: 3) AAPS设置
+:caption: 3) Setting up AAPS
-配置远程数据服务器 <./SettingUpAaps/SettingUpTheReportingServer.md>
+Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
-构建（Building）AAPS <./SettingUpAaps/BuildingAaps.md>
-传输和安装AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
-安装向导 <./SettingUpAaps/SetupWizard.md>
-你的AAPS配置文件 <./SettingUpAaps/YourAapsProfile.md>
-调整AAPS参数设置 <./SettingUpAaps/ChangeAapsConfiguration.md>
-- 配置生成器 <./SettingUpAaps/ConfigBuilder.md>
-- 首选项 <./SettingUpAaps/Preferences.md>
-完成目标 <./SettingUpAaps/CompletingTheObjectives.md>
+Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
+Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
+Setup Wizard <./SettingUpAaps/SetupWizard.md>
+Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
+Change AAPS configuration <./SettingUpAaps/ChangeAapsConfiguration.md>
+- Config Builder <./SettingUpAaps/ConfigBuilder.md>
+- Preferences <./SettingUpAaps/Preferences.md>
+Completing the objectives <./SettingUpAaps/CompletingTheObjectives.md>
```
```{toctree}
@@ -138,13 +140,15 @@ Android Auto <./RemoteFeatures/AndroidAuto.md>
```
```{toctree}
-:caption: 7) AAPS的维护
-
-导出/导入设置 <./Maintenance/ExportImportSettings.md>
-回顾你的数据 <./Maintenance/Reviewing.md>
-AAPS发布说明 <./Maintenance/ReleaseNotes.md>
-文档更新 <./Maintenance/DocumentationUpdate.md>
-升级到新版本的AAPS <./Maintenance/UpdateToNewVersion.md>
+:caption: 7) Maintenance of AAPS
+
+Export/Import Settings <./Maintenance/ExportImportSettings.md>
+Reviewing your data <./Maintenance/Reviewing.md>
+AAPS Release Notes <./Maintenance/ReleaseNotes.md>
+Documentation updates <./Maintenance/DocumentationUpdate.md>
+Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
diff --git a/docs/CROWDIN/zh_TW/AdvancedOptions/Autotune.md b/docs/CROWDIN/zh_TW/AdvancedOptions/Autotune.md
index eeb5703970fa..c19c78d8a63c 100644
--- a/docs/CROWDIN/zh_TW/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/zh_TW/AdvancedOptions/Autotune.md
@@ -43,7 +43,7 @@ Autotune 外掛是在 AAPS 中實作的 OpenAPS 自動調整算法。
- 「比較設定檔」按鈕會打開設定檔比較視圖。 輸入設定檔顯示為藍色，輸出設定檔（名稱為「調整後」）顯示為紅色。
- - 注意：以下範例中，輸入設定檔有 IC 和 ISF 的日夜變化，但輸出計算後的設定檔只有單一數值。 如果你希望獲得生理節律輸出配置，請參見[生理節律 IC 或 ISF 配置](#circadian-ic-or-isf-profile)。
+ - 注意：以下範例中，輸入設定檔有 IC 和 ISF 的日夜變化，但輸出計算後的設定檔只有單一數值。 如果您對獲得日夜變化輸出檔案感興趣，請參見 [日夜變化 IC 或 ISF 檔案](#autotune-circadian-ic-or-isf-profile) 下方。
@@ -86,13 +86,13 @@ Autotune 外掛是在 AAPS 中實作的 OpenAPS 自動調整算法。
-- 自動開關配置 (預設關閉)：請參見[使用自動化規則運行 Autotune](#run-autotune-with-an-automation-rule)。 如果你將此設定更改為開啟，則輸入設定檔將自動被調整後的設定檔更新並啟用。
+- 自動化切換檔案（預設為關閉）：請參見 [使用自動化規則運行自動調整](#autotune-run-autotune-with-an-automation-rule) 下方。 如果你將此設定更改為開啟，則輸入設定檔將自動被調整後的設定檔更新並啟用。
- **請小心，你必須在接下來幾天內信任並驗證，在更新和啟用未修改的調整配置後，它會改善你的循環運行**
- 將 UAM 分類為基礎率（預設為開啟）：此設定適用於未輸入碳水化合物的 AndroidAPS 用戶（完全 UAM）。 當關閉時，他將阻止 UAM 被分類為基礎率。
- 注意：如果當天偵測到至少一小時的碳水化合物吸收，無論此設定（開啟或關閉），所有分類為「UAM」的資料都會被分類為基礎率。
- 資料天數（預設為5天）：你可以使用此設定定義預設值。 每次你在 Autotune 外掛中選擇新設定檔時，調整天數參數將被替換為此預設值。
-- 將平均結果應用於日夜變化的 IC/ISF（預設為關閉）：請參閱[日夜變化 IC 或 ISF 設定檔](#circadian-ic-or-isf-profile)。
+- 將平均結果應用於日夜變化的 IC/ISF（預設為關閉）：請參閱[日夜變化 IC 或 ISF 設定檔](#autotune-circadian-ic-or-isf-profile)。
### 其他設置
diff --git a/docs/CROWDIN/zh_TW/AdvancedOptions/DevBranch.md b/docs/CROWDIN/zh_TW/AdvancedOptions/DevBranch.md
index ce02f7b0fe02..a05cc3e2ae1c 100644
--- a/docs/CROWDIN/zh_TW/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/zh_TW/AdvancedOptions/DevBranch.md
@@ -63,6 +63,6 @@ AAPS 的開發版本僅適用於能處理堆棧追蹤、查找日誌文件，甚
- 選擇您需要的變種：
- fullRelease: 用於正常的幫浦使用，具有完整功能。
- - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) 針對照護者使用（需 [Nightscout](../SettingUpAaps/Nightscout.md)）。
+ - [aapsclient, aapsclient2](#RemoteControl_aapsclient) 供看護人員使用（需要 [Nightscout](../SettingUpAaps/Nightscout.md)）。
- pumpcontrol
- 以“Debug”結尾的文字表示 APK 將在除錯模式下建置，這對於除錯很有幫助。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_TW/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/zh_TW/AdvancedOptions/FullClosedLoop.md
index 5f27826a78e2..e812ec78b477 100644
--- a/docs/CROWDIN/zh_TW/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/zh_TW/AdvancedOptions/FullClosedLoop.md
@@ -7,7 +7,7 @@ Full Closed Looping **全閉環(FCL)** 的主要吸引力在於它具有模擬
在 **全閉環(FCL)** 中，不再需要根據餐量進行注射：一切讓演算法來處理！ **AAPS** 可能在用戶不進行任何注射的情況下運行，並且不需要輸入碳水化合物，這是一種稱為‘未公告用餐’ **（‘UAM’）** 的模式。 **UAM** 可允許 **AAPS** 處理更寬容的碳水化合物範圍，並且會更積極的補充胰島素。
-### 值得期待什麼？
+## 值得期待什麼？
已有許多發表的研究顯示 **全閉環(FCL)** 可以達到的良好結果。 如需進一步閱讀，請參閱以下內容：
@@ -22,7 +22,7 @@ Full Closed Looping **全閉環(FCL)** 的主要吸引力在於它具有模擬
- 微調並調整 **AAPS** 的設置（特別是 **Automations**）。
-### 從 混合閉環(HCL) 過渡到 全閉環(FCL) 的一般考量（理由）
+## 從 混合閉環(HCL) 過渡到 全閉環(FCL) 的一般考量（理由）
**全閉環(FCL)** 不是適合每個人：
@@ -32,7 +32,7 @@ Full Closed Looping **全閉環(FCL)** 的主要吸引力在於它具有模擬
- 在為小孩建立 **全閉環(FCL)** 上仍然存在困難（如下討論）。
-### 良好調整的混合自動循環
+## 良好調整的混合自動循環
建議在考慮過渡到 **全閉環(FCL)** 之前，先建立一個調整良好的 **混合閉環(HCL)**。 成功使用 **全閉環(FCL)** 需要對用戶的設定進行高度個性化的微調，以便 **AAPS** 能夠提供胰島素，緊密模擬您成功的混合閉環模式。
@@ -40,7 +40,7 @@ Full Closed Looping **全閉環(FCL)** 的主要吸引力在於它具有模擬
**全閉環(FCL) 是 DIY 由用戶根據其成功的 混合閉環(HCL) 和初次 全閉環(FCL) 體驗分析數據而設置的 **Automations**。**
-### 快速胰島素（Lyumjev, Fiasp）
+## 快速胰島素（Lyumjev, Fiasp）
**全閉環(FCL)** 需要快速作用的胰島素。 這樣在餐點相關的**血糖**升高開始時，**全閉環(FCL)** 可以保持**血糖**在範圍內（根據一般定義，在 180 mg/dl（10 mmol/l）以下）。
@@ -62,7 +62,7 @@ IEEE 控制系統雜誌，ResearchGate [人工胰臟與餐點控制：1型糖尿
不過，Fiasp 或 Lyumjev 可能會導致頻繁的胰島素幫浦堵塞，即使在優化針長等因素後。 重要的是要注意導管或藥囊的時間。 許多用戶發現 48 小時是胰島素效能的極限，否則將導致導管/藥囊失敗。
-### 前置條件
+## 前置條件
**血糖**值和穩定的藍牙連線對於確保 **AAPS** 能夠最佳運作而不浪費寶貴的時間是必要的。 **全閉環(FCL)** 需要一個 24/7 技術穩定的系統：
@@ -76,13 +76,13 @@ IEEE 控制系統雜誌，ResearchGate [人工胰臟與餐點控制：1型糖尿
以上內容將根據您的 **AAPS** 組件系統以及您的生活方式而有所不同。
-### 進餐相關的限制
+## 進餐相關的限制
- 對於不包含快速高影響 **血糖** 食物成分的飲食以及日常不大變化的用餐模式的人來說，設定 **全閉環(FCL)** 可能更容易。 這並不一定意味著低碳水化合物飲食。
- 高脂肪或高蛋白飲食，或慢消化/胃輕癱，對 **全閉環(FCL)** 而言使事情變得更容易而不是更難，因為晚餐碳水化合物可以很好地覆蓋在高峰時需進行注射後的不可避免的“尾部”反應。
-#### 血糖指數與血糖影響
+### 血糖指數與血糖影響
對於 **UAM** 模式而言，隨著“血糖影響”（'EBG'）的上升，挑戰也隨之增加。
@@ -98,7 +98,7 @@ IEEE 控制系統雜誌，ResearchGate [人工胰臟與餐點控制：1型糖尿
不規律地食用含有快速吸收碳水化合物的零食和甜飲料，對 **全閉環（FCL）** 系統而言是一大問題。
-#### 運動/活動準備
+## 運動/活動準備
在運動或活動時，若使用幫浦或混合閉環系統，建議用戶在運動前減少 **IOB**。
@@ -106,7 +106,7 @@ IEEE 控制系統雜誌，ResearchGate [人工胰臟與餐點控制：1型糖尿
不尋常或不穩定的運動活動水平對 **全閉環(FCL)** 造成困難。 在運動前做好計畫是必要的（尤其是如果您想降低在運動期間需要急救碳水化合物/零食的需求）。 在活動量較高的一天之後，建議在晚上餐點消化完全後設定較低的 **設定檔百分比**：在 **自動化** 中設定一個較高（>100 mg/dl）的 **血糖** 目標，並在 AAPS 偏好設定中勾選「在高目標值時不使用 **SMB**。
-#### 兒童的挑戰
+## 兒童的挑戰
**全閉環(FCL)** 對孩子來說可能帶來額外挑戰，包括：
@@ -251,7 +251,7 @@ Automation(#3)，“iobTH 達到 => **SMBs** 關閉”，這定義了結束（
此外，還需要一個終止自動化 #5，「停止餐後高血糖」，以便當血糖開始下降時減少胰島素輸送的積極性。 （然而，通常循環系統為防止低血糖，已經會限制更多胰島素，因為預測的血糖已經偏低）。
-### 防止低血糖
+## 防止低血糖
核心問題在於 **UAM** **全閉環(FCL)**（沒有碳水化合物攝入）可能完全不知道還有多少克的碳水化合物可供吸收，並可能耗盡這“尾部”胰島素，而不會讓你因此低血糖。
diff --git a/docs/CROWDIN/zh_TW/CompatibleCgms/Juggluco.md b/docs/CROWDIN/zh_TW/CompatibleCgms/Juggluco.md
index 8530d683107e..e7afff1f672a 100644
--- a/docs/CROWDIN/zh_TW/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/zh_TW/CompatibleCgms/Juggluco.md
@@ -19,6 +19,8 @@ orphan: true
+(juggluco-to-aaps)=
+
## Juggluco 到 AAPS
Juggluco 可以將血糖直接傳送到 AAPS，當您使用 [可信任的感測器](#GettingStarted-TrustedBGSource) 時，讓 SMB 始終啟用。
@@ -31,6 +33,8 @@ Juggluco 可以將血糖直接傳送到 AAPS，當您使用 [可信任的感測
+(juggluco-to-xdrip)=
+
## Juggluco 到 xDrip+
Juggluco 可以將血糖傳送到 xDrip+，然後它會將資料傳送到 AAPS。
diff --git a/docs/CROWDIN/zh_TW/CompatibleCgms/Libre3.md b/docs/CROWDIN/zh_TW/CompatibleCgms/Libre3.md
index c8c5020617bd..7adb8a43b69f 100644
--- a/docs/CROWDIN/zh_TW/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/zh_TW/CompatibleCgms/Libre3.md
@@ -17,7 +17,7 @@ Freestyle Libre 3 (FSL3) 需要特殊設定才能將血糖值接收至 AAPS。
## 方法一：直接使用每分鐘的資料值
AndroidAPS 是專為每 5 分鐘的資料值量身打造的。 因此，在某些情況下處理每分鐘的資料值時，會有些侷限。
-
+請參閱 [這裡](#juggluco-to-aaps).
## 方法二：透過 xDrip 將每分鐘的資料值轉換為每 5 分鐘的資料值。
@@ -28,8 +28,6 @@ AndroidAPS 是專為每 5 分鐘的資料值量身打造的。 因此，在某
確保將血糖值傳送到 xDrip+：在 Juggluco 的設定中，你可以配置 Juggluco 將其血糖值傳送到其他應用程式。 Juggluco 可以發送三種類型的廣播：**修補版 Libre 廣播** 最初由修補版 Librelink 應用程式使用，並可用於將葡萄糖值傳送至 xDrip+。
-
-
### 步驟 2：設定 xDrip
血糖值會由智慧型手機上的 xDrip+ 應用程式接收。
@@ -58,10 +56,10 @@ AndroidAPS 是專為每 5 分鐘的資料值量身打造的。 因此，在某
### 步驟 4：配置 AndroidAPS
-- 在[ConfigBuilder 的血糖來源](#Config-Builder-bg-source)中選擇 xDrip+。
+- 請參閱 [這裡](#juggluco-to-xdrip)然後返回。
- 如果 AndroidAPS 在手機處於飛行模式時無法接收血糖值，請使用「識別接收器」。
-- 關閉平滑功能（已在 xDrip+ 中完成）。
+- 關閉平滑設定（在 xDrip+ 中已完成）
## 後續傳感器更換
diff --git a/docs/CROWDIN/zh_TW/CompatiblePhones/Jelly.md b/docs/CROWDIN/zh_TW/CompatiblePhones/Jelly.md
index 3b5660f84be5..6b0603451ece 100644
--- a/docs/CROWDIN/zh_TW/CompatiblePhones/Jelly.md
+++ b/docs/CROWDIN/zh_TW/CompatiblePhones/Jelly.md
@@ -1,3 +1,9 @@
+* * *
+
+orphan: true
+
+* * *
+
# Jelly
## Jelly 2
diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md b/docs/CROWDIN/zh_TW/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
index 480205554851..17b6d334f146 100644
--- a/docs/CROWDIN/zh_TW/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
+++ b/docs/CROWDIN/zh_TW/CompatiblePumps/Accu-Chek-Combo-Pump-v2.md
@@ -165,7 +165,7 @@ Combo 可以在 _遠端終端_ 模式或 _指令_ 模式下透過藍牙操作。
（用戶不影響這一點；驅動完全自主決定使用何種模式。這僅是為了讓用戶知道為什麼有時可以在該欄位中看到 Combo 畫面。） 最底部有一個 「重新整理」 按鈕。
-這會觸發幫浦狀態的即時更新。 他也用於告訴 AAPS 之前發現的錯誤現在已修復，可以讓 AAPS 再次檢查一切是否正常（更多相關訊息請參閱 [警報部分](combov2-alerts)）。 他還用於讓AAPS知道之前發現的錯誤已修復，並且AAPS可以再次檢查一切是否正常（更多內容請參閱[關於警報的部分](#alerts-warnings-and-errors-and-how-they-are-handled)）。
+這會觸發幫浦狀態的即時更新。 他也用於告訴 AAPS 之前發現的錯誤現在已修復，可以讓 AAPS 再次檢查一切是否正常（更多相關訊息請參閱 [警報部分](combov2-alerts)）。 他還用於讓AAPS知道之前發現的錯誤已修復，並且AAPS可以再次檢查一切是否正常（更多內容請參閱[關於警報的部分](#combov2-alerts)）。
## 偏好設定
@@ -176,8 +176,8 @@ Combo 可以在 _遠端終端_ 模式或 _指令_ 模式下透過藍牙操作。
1. _與幫浦配對_：這是一個可以按下的按鈕，用於與 Combo 配對。 如果已經配對了幫浦，他將無法使用。
2. _取消幫浦配對_：取消配對已配對的 Combo；與項目1相反。 如果沒有已配對的幫浦，他將無法使用。
3. _發現持續時間（以秒為單位）_：配對時，驅動會使手機對幫浦可見。 這控制了這種可見性持續多久。 預設選擇最大值（300 秒 = 5 分鐘）。 Android 不允許可見性無限期持續，因此必須選擇一個持續時間。
-4. _自動偵測並自動輸入胰島素儲存庫變更_：如果啟用，通常透過 Action 標籤中的 "注射/填充" 按鈕由用戶完成的 "儲存庫變更" 操作。 這在[下面進一步詳細說明](#autodetecting-and-automatically-entering-battery-and-reservoir-changes)。
-5. _自動偵測並自動輸入電池更換_：如果啟用，通常由用戶透過 Action 標籤中的 "幫浦電池變更" 按鈕完成的 "電池更換" 操作。 這在[下面進一步詳細說明](#autodetecting-and-automatically-entering-battery-and-reservoir-changes)。
+4. _自動偵測並自動輸入胰島素儲存庫變更_：如果啟用，通常透過 Action 標籤中的 "注射/填充" 按鈕由用戶完成的 "儲存庫變更" 操作。 這在[下面進一步詳細說明](#combov2-autodetections)。
+5. _自動偵測並自動輸入電池更換_：如果啟用，通常由用戶透過 Action 標籤中的 "幫浦電池變更" 按鈕完成的 "電池更換" 操作。 這在[下面進一步詳細說明](#combov2-autodetections)。
6. _啟用詳細 Combo 日誌紀錄_：這大大擴展了驅動紀錄的日誌數量。 **注意**：除非開發人員要求，否則不要啟用此功能。 否則，這會增加大量的干擾到 AndroidAPS 日誌中，減少他們的實用性。
大多數用戶只使用頂部兩個項目，即 _與幫浦配對_ 和 _取消幫浦配對_ 按鈕。
@@ -202,7 +202,7 @@ Combo 以遠端終端螢幕的形式顯示警報。 警告會顯示一個“Wx
- W2 “電池低”：驅動程式會將其轉為顯示於 AAPS 主標籤上的“電池低”警告
- W3、W6、W7、W8：這些僅供用戶參考資訊，驅動程式會自動消除他們，因此是安全的
-其他警告 _不會_ 被自動消除。 此外，錯誤 _絕不_ 會被自動消除。 這兩者都是以相同方式處理：他們會導致驅動程式在 AAPS 介面上顯示警報對話框，並中止任何正在執行的指令。 驅動程式會切換到“錯誤”狀態（詳見 [上述 Accu-Chek Combo 標籤內容描述](#accu-chek-combo-tab-contents)）。 此狀態不允許任何指令執行。 用戶需要在幫浦上處理錯誤；例如，阻塞錯誤可能需要更換套管。 用戶處理好錯誤後，按下 Accu-Chek Combo 標籤上的“重新整理”按鈕即可恢復正常操作。 然後驅動程式會連線到 Combo 並更新其狀態，檢查畫面上是否仍顯示錯誤等。 此外，驅動程式會在稍後自動重新整理幫浦狀態，因此手動按該按鈕並非必要。
+其他警告 _不會_ 被自動消除。 此外，錯誤 _絕不_ 會被自動消除。 這兩者都是以相同方式處理：他們會導致驅動程式在 AAPS 介面上顯示警報對話框，並中止任何正在執行的指令。 驅動程式會切換到“錯誤”狀態（詳見 [上述 Accu-Chek Combo 標籤內容描述](#combov2-tab-contents)）。 此狀態不允許任何指令執行。 用戶需要在幫浦上處理錯誤；例如，阻塞錯誤可能需要更換套管。 用戶處理好錯誤後，按下 Accu-Chek Combo 標籤上的“重新整理”按鈕即可恢復正常操作。 然後驅動程式會連線到 Combo 並更新其狀態，檢查畫面上是否仍顯示錯誤等。 此外，驅動程式會在稍後自動重新整理幫浦狀態，因此手動按該按鈕並非必要。
注射是一個特殊案例。 他在 Combo 的指令模式下執行，此模式下不會在中途報告出現的警報。 因此，驅動程式無法在注射期間自動消除警告。 這意味著不幸的是，幫浦在注射完成之前會一直發出哔哔聲。 最常見的中途警報通常是 W1“儲液槽低”。 **不要** 在注射期間手動取消幫浦上的 Comnbo 警告。 這會有中斷注射的風險。 注射結束後驅動程式會處理警告。
@@ -215,8 +215,8 @@ Combo 以遠端終端螢幕的形式顯示警報。 警告會顯示一個“Wx
* 請記住這不是一個產品，特別是在初期，使用者需要監控並暸解系統、其限制以及可能出現的故障方式。 強烈建議不要在不充分瞭解系統的人使用該系統時使用他。
* 由於 Combo 的遠端控制功能運作方式，幾個操作（特別是設定基礎設定檔）相比其他幫浦較慢。 這是 Combo 無法克服的不便限制。
* 不要在幫浦上設置或取消 TBR。 循環假設他控制 TBR，否則系統無法可靠工作，因為無法確定用戶在幫浦上設定 TBR 的開始時間。
-* 當 AAPS 與幫浦進行通訊時（幫浦上顯示藍牙標誌時），請不要按任何按鈕。 這樣做會中斷藍牙連線。 只有在建立連線時出現問題時才這樣做 (請參見[上述的 "開始之前" 部分](#before-you-begin))。
-* 在幫浦注射時請不要按任何按鈕。 特別是，不要嘗試透過按下按鈕來取消警報。 請參閱[有關警報的部分](#alerts-warnings-and-errors-and-how-they-are-handled)以獲取更詳細的解釋。
+* 當 AAPS 與幫浦進行通訊時（幫浦上顯示藍牙標誌時），請不要按任何按鈕。 這樣做會中斷藍牙連線。 只有在建立連線時出現問題時才這樣做 (請參見[上述的 "開始之前" 部分](#combov2-before-you-begin))。
+* 在幫浦注射時請不要按任何按鈕。 特別是，不要嘗試透過按下按鈕來取消警報。 請參閱[有關警報的部分](#combov2-alerts)以獲取更詳細的解釋。
## 無法建立與 Combo 連線時的檢查清單
diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/zh_TW/CompatiblePumps/DanaRS-Insulin-Pump.md
index 4adfc61a06f9..11936d742a06 100644
--- a/docs/CROWDIN/zh_TW/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/zh_TW/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -79,7 +79,7 @@ orphan: true
* 按下「OK」進入舊密碼。
-* 輸入**舊密碼**（預設密碼見[上方](#default-password)）並按下 OK。
+* 輸入 **舊密碼** (預設密碼請參閱 [上方](#DanaRS-Insulin-Pump-default-password)) 並按下 OK
@@ -130,7 +130,7 @@ orphan: true
### DanaRS v3, Dana-i
-* 開始配對程序，如上所述[以上](#pairing-pump)。
+* 開始配對程序，如上所述[以上](#DanaRS-Insulin-Pump-pairing-pump)。
* 有時可能需要透過長按 Dana-i/RS 標籤上的藍牙圖示來清除 AAPS 中的配對資訊。
## Dana RS 幫浦跨時區旅行
diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/zh_TW/CompatiblePumps/MedtronicPump.md
index 1d85e0d21158..21ee6df51044 100644
--- a/docs/CROWDIN/zh_TW/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/zh_TW/CompatiblePumps/MedtronicPump.md
@@ -60,7 +60,7 @@ orphan: true
- **幫浦序列號**：顯示在幫浦背面，以 SN 開頭。 您應該只輸入顯示的 6 位數字，沒有任何字母字符（例如：123456）。
- **幫浦型號**：你使用的幫浦型號（例如 522）。
-- **幫浦頻率**：有兩個選項，根據你的幫浦最初發行的地區。 如果你不確定選擇哪個選項，請檢查[常見問題解答](#faq)：
+- **幫浦頻率**：有兩個選項，根據你的幫浦最初發行的地區。 如果你不確定選擇哪個選項，請檢查[常見問題解答](#MedtronicPump-faq)：
- 美國和加拿大使用的頻率為 916 Mhz
- 全球其他地區使用的頻率為 868 Mhz
- **幫浦最大基礎率（U/h）**：這需要與你的幫浦上設置的設定相符（請參閱上方的幫浦配置）。 再次提醒，此設定必須謹慎選擇，因為他將決定 AAPS 可透過你的基礎率提供的胰島素量。 這將有效地設置最大臨時基礎率。 作為範例，將此數值設置為你最大標準基礎率的四倍，將允許 400% 的臨時基礎率。 幫浦允許的最大值為每小時 34.9 單位。
@@ -99,10 +99,10 @@ orphan: true
螢幕底部有三個按鈕：
- **重新整理**：用於重新整理幫浦的目前狀態。 此功能應僅在連線長時間中斷時使用，因為這將需要完整的資料重新整理（檢索歷史紀錄、獲取/設置時間、獲取設定檔、獲取電池狀態等）。
-- **幫浦歷史**：顯示幫浦歷史（見[下文](#pump-history)）
-- **RL 狀態**：顯示 RL 狀態（見[下文](#rl-status-rileylink-status)）
+- **幫浦歷史**：顯示幫浦歷史（見[下文](#MedtronicPump-pump-history)）
+- **RL 狀態**：顯示 RL 狀態（見[下文](#MedtronicPump-rl-status-rileylink-status)）
-(MedtronicPump-pump-history)=
+(MedtronicPump-MedtronicPump-pump-history)=
## 幫浦歷史紀錄
@@ -110,7 +110,7 @@ orphan: true
幫浦歷史紀錄每 5 分鐘檢索一次並存儲在本地。 僅存儲過去 24 小時的歷史紀錄。 這提供了一種方便的方式來查看幫浦的行為，若需要的話。 存儲的項目僅限於 AAPS 相關的資料，並不包括任何無關的配置功能。
-(MedtronicPump-rl-status-rileylink-status)=
+(MedtronicPump-MedtronicPump-rl-status-rileylink-status)=
## RL 狀態（RileyLink 狀態）
diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/zh_TW/CompatiblePumps/MedtrumNano.md
index f80a7b405276..c131b3126880 100644
--- a/docs/CROWDIN/zh_TW/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/zh_TW/CompatiblePumps/MedtrumNano.md
@@ -120,7 +120,7 @@ orphan: true
***預設：25U。***
-此設置更改每小時最多輸送的胰島素量。 如果此限制被超過，修補版將暫停並發出警報。 可以透過點擊總覽選單中的重置按鈕來重置此警報，請參閱[重置警報](#reset-alarms)。
+此設置更改每小時最多輸送的胰島素量。 如果此限制被超過，修補版將暫停並發出警報。 可以透過點擊總覽選單中的重置按鈕來重置此警報，請參閱[重置警報](#nano-reset-alarms)。
根據你的胰島素需求，設置一個合適的值。
@@ -128,7 +128,7 @@ orphan: true
***預設：80U。***
-此設置更改每日最多輸送的胰島素量。 如果此限制被超過，修補版將暫停並發出警報。 可以透過點擊總覽選單中的重置按鈕來重置此警報，請參閱[重置警報](#reset-alarms)。
+此設置更改每日最多輸送的胰島素量。 如果此限制被超過，修補版將暫停並發出警報。 可以透過點擊總覽選單中的重置按鈕來重置此警報，請參閱[重置警報](#nano-reset-alarms)。
根據你的胰島素需求，設置一個合適的值。
@@ -189,9 +189,9 @@ orphan: true
#### 從Medtrum總覽標籤啟動修補版
-在AAPS介面中導航至[Medtrum標籤](#overview)，然後按下右下角的**更換修補版**按鈕。
+在AAPS介面中導航至[Medtrum標籤](#nano-overview)，然後按下右下角的**更換修補版**按鈕。
-如果修補版已啟動，系統將提示你先停用該修補版。 請參閱[停用修補版](#deactivate-patch)。
+如果修補版已啟動，系統將提示你先停用該修補版。 請參閱[停用修補版](#nano-deactivate-patch)。
按照提示填充並啟動新的修補版。 請注意——只有在系統提示時才應將幫浦基座連線到儲液瓶修補版。 **你應在系統提示啟動過程時（填充完成後）才將幫浦放在身體上並插入套管。**
@@ -242,9 +242,11 @@ orphan: true
按**確定**返回主畫面。
+(nano-deactivate-patch)=
+
### 停用修補版
-要停用目前啟動的修補版，請前往AAPS介面中的[Medtrum標籤](#overview)，然後按下**更換修補版**按鈕。
+要停用目前啟動的修補版，請前往AAPS介面中的[Medtrum標籤](#nano-overview)，然後按下**更換修補版**按鈕。
@@ -258,9 +260,11 @@ orphan: true
停用完成後，按**確定**返回主畫面，或按**下一步**繼續啟動新修補版的過程。
+(nano-resume-interrupted-activation)=
+
### 恢復中斷的啟動過程
-如果修補版啟動過程被中斷，例如由於手機電量耗盡，你可以前往AAPS介面中的Medtrum標籤，並按下**更換修補版**按鈕來恢復啟動過程。
+如果貼片註冊過程被中斷，例如因為手機電池耗盡，您可以在 AAPS 介面中進入 [Medtrum 頁籤](#nano-overview)，然後按下 **更換貼片**
@@ -270,6 +274,8 @@ orphan: true
驅動將嘗試確定目前的修補版啟動狀態。 如果成功，他將進入目前步驟的啟動進度。
+(nano-overview)=
+
## 首頁總覽
總覽顯示了Medtrum修補版的目前狀態。 他還包含更換修補版、重置警報和重新整理狀態的按鈕。
@@ -343,6 +349,8 @@ orphan: true
此按鈕將啟動更換修補版的過程。 詳情請參見 [啟用藥匣](#medtrum-activate-patch)。
+(nano-reset-alarms)=
+
### 重置警報
當有可重置的警報時，警報按鈕將顯示在總覽畫面中。 按下此按鈕將重置警報，並在修補版因警報暫停時恢復胰島素輸送。 例如： 當因每天最大胰島素輸送量警報而暫停時。
@@ -372,7 +380,7 @@ orphan: true
### 啟動中斷
-如果啟動過程被中斷，例如手機電量耗盡或手機當機。 你可以前往更換修補版畫面，並按照[恢復中斷的啟動](#resume-interrupted-activation)中的步驟繼續啟動過程。
+如果啟動過程被中斷，例如手機電量耗盡或手機當機。 你可以前往更換修補版畫面，並按照[恢復中斷的啟動](#nano-resume-interrupted-activation)中的步驟繼續啟動過程。
### 防止修補版故障
diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md
index 5e5c90c10f2a..5f3cd9007f85 100644
--- a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md
@@ -65,7 +65,7 @@ orphan: true
選中**設定齒輪(3)**旁邊的**復選框(4)**將使DASH選單顯示為**AAPS**介面的標籤**DASH**。 勾選此框將方便你在使用**AAPS**時訪問DASH指令。
-**注意：** 有一個更快速的方式可以在本文件的DASH設定部分中找到，訪問[**Dash設定**](#dash-settings)。
+**注意：** 有一個更快速的方式可以在本文件的DASH設定部分中找到，訪問[**Dash設定**](#omnipod-dash-settings)。
@@ -83,6 +83,7 @@ orphan: true
 “ Pod 管理”（啟動、停用、播放測試嗶聲及 Pod 歷史）
+(omnipod-dash-activate-pod)=
### 註冊 Pod
@@ -132,7 +133,7 @@ orphan: true
點擊手機上的返回按鈕，返回到 **DASH** 標籤畫面，該畫面現在會顯示你的啟用 Pod 的資訊，包括目前基礎率、Pod 儲液量、輸送的胰島素、Pod 錯誤和警報。
- 有關顯示的訊息的更多詳細資訊，請轉到本文件的[**DASH 標籤**](#dash-tab)部分。
+ 有關顯示資訊的更多詳細資訊，請前往此文件的 [**DASH 頁籤**](#omnipod-dash-tab) 部分。
@@ -141,7 +142,7 @@ orphan: true
在註冊 Pod 後匯出設置是一個好習慣。 每次更換藥量時應該進行匯出設置，並每月將匯出的檔案複製到你的雲端儲存。 請見[**匯出設定文件**](../Maintenance/ExportImportSettings.md)。
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### 停用 Pod
@@ -176,9 +177,11 @@ orphan: true
+(omnipod-dash-resuming-insulin-delivery)=
+
### 恢復胰島素輸送
-**注意**：在**設定檔切換**期間，DASH 必須在設置新的基礎**設定檔**之前中斷送藥，因為送藥可能會被暫停。 在問題排除部分閱讀[**暫停交付**](#delivery-suspended)以獲取更多詳細資訊。
+**注意**：在**設定檔切換**期間，DASH 必須在設置新的基礎**設定檔**之前中斷送藥，因為送藥可能會被暫停。 在問題排除部分閱讀[**暫停交付**](#omnipod-dash-delivery-suspended)以獲取更多詳細資訊。
使用此指令指示目前暫停的活動 Pod 恢復胰島素輸送。 命令成功處理後，胰島素將根據當前時間從活動的基礎**設定檔**恢復正常送藥。 藥量將再次接受注射、**TB** 和**SMB**的命令。
@@ -215,7 +218,7 @@ orphan: true
4. 進入 **DASH** 標籤。 在 **啟用 Pod 警報** 欄位下，警告訊息將不再顯示，且活動 Pod 將不再發出 Pod 過期警告嗶聲。
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### 查看 Pod 歷史紀錄
@@ -240,7 +243,7 @@ orphan: true
 
-(OmnipodDASH-dash-tab)=
+(omnipod-dash-tab)=
## DASH 標籤
@@ -275,7 +278,7 @@ orphan: true
* **儲液量：** 當儲液量超過 50 單位時顯示 50+ 單位。 當儲液量低於 50 單位時，顯示確切的單位數。
* **總輸送量：** 顯示從儲液中輸送的胰島素總單位數。 這包含已使用和排空的胰島素。
-* **錯誤：** 顯示遇到的最後一個錯誤。 檢查[Pod 歷史](#view-pod-history)和日誌檔案以獲取過去錯誤的詳細資訊和更多訊息。
+* **錯誤：** 顯示遇到的最後一個錯誤。 檢閱 [Pod 歷史](#omnipod-dash-view-pod-history) 和日誌檔案以了解過去的錯誤和更詳細的資訊。
* **啟用 Pod 警報：** 保留目前啟用 Pod 上運作的警報。
### 按鈕
@@ -303,12 +306,12 @@ orphan: true
-* 2 - [**啟動 Pod**](#activate-pod)：對新的 Pod 進行灌注並啟動。
-* 3 - [**停用 Pod**](#deactivate-pod)：停用目前啟用的 Pod。
+* 2 - [**啟動 Pod**](#omnipod-dash-activate-pod)：對新的 Pod 進行灌注並啟動。
+* 3 - [**停用 Pod**](#omnipod-dash-deactivate-pod)：停用目前啟用的 Pod。
* 4 - **播放測試嗶聲** ：按下時播放 Pod 的單次測試嗶聲。
-* 5 - [**Pod 歷史**](#view-pod-history)：顯示當前 Pod 的活動歷史紀錄。
+* 5 - [**Pod 歷史**](#omnipod-dash-view-pod-history)：顯示當前 Pod 的活動歷史紀錄。
-(DanaRS-Insulin-Pump-dash-settings)=
+(omnipod-dash-settings)=
## Dash 設定
@@ -388,6 +391,8 @@ orphan: true
## 問題排除
+(omnipod-dash-delivery-suspended)=
+
### 輸送暫停
* 現在已無暫停按鈕。 如果你想要「暫停」藥量，你可以將 TBR 設置為零，持續 x 分鐘。
@@ -396,7 +401,7 @@ orphan: true
- 可能會通知某個指令未確認：這取決於失敗發生的時間。
- **AAPS** 每 15 分鐘嘗試設置新的基礎設定檔。
- **AAPS** 每 15 分鐘將顯示一則通知，告知送藥已暫停，如果送藥仍然暫停（恢復送藥失敗）。
- - 如果使用者選擇手動重新開始給藥，[**重新開始給藥**](#resuming-insulin-delivery)按鈕將會啟用。
+ - 如果使用者選擇手動恢復供給，[**恢復供給**](#omnipod-dash-resuming-insulin-delivery)按鈕將會啟用。
- 如果**AAPS**無法自行恢復送藥（如果藥量無法連線、聲音被靜音等情況會發生），藥量每分鐘將發出 4 次嗶聲，持續 3 分鐘，然後如果送藥暫停超過 20 分鐘將每 15 分鐘重複這個過程。
* 對於未確認的指令，「重新整理 Pod 狀態」應能確認/否認他們。
diff --git a/docs/CROWDIN/zh_TW/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/zh_TW/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 0684f7bd7faa..36cce33f3af4 100644
--- a/docs/CROWDIN/zh_TW/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/zh_TW/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -94,7 +94,7 @@ JSON 文件可以在 Notepad（或 Notepad++）文本編輯器中編輯（建議
"color": "#BC906A"
}
```
-要將秒針著色為預設的血糖顏色（範圍低、中或高），只需修改最後一行的鍵值 `bgColor`。
+要將秒針著色為預設的血糖顏色（低範圍、中範圍或高範圍），您只需修改最新行的 keyValue `bgColor`
```json
"color": "bgColor"
diff --git a/docs/CROWDIN/zh_TW/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/zh_TW/Maintenance/UpdateAaps3204.md
index d2ec28d2f4b9..1672e6401f6a 100644
--- a/docs/CROWDIN/zh_TW/Maintenance/UpdateAaps3204.md
+++ b/docs/CROWDIN/zh_TW/Maintenance/UpdateAaps3204.md
@@ -1,3 +1,7 @@
+- - -
+orphan: true
+- - -
+
# 更新至 AAPS 3.2.0.4
(update-aaps-3204)=
diff --git a/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuild.md
index 0bacb562a223..a742a5200009 100644
--- a/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuild.md
@@ -94,80 +94,25 @@ AAPS 應用程式在建立後會保存在你的 Google 雲端硬碟中：
### AAPS-CI 選項 1 – 生成 JKS
- 適合首次使用者、沒有 JKS 的使用者或忘記密碼或別名的使用者。
- 以下是使用多個平台的範例。
+- 在以下列表中選擇您的平台， Android（優先選擇）、iOS 或電腦。
-(aaps-ci-option1-android)=
- - Android 上的作法（最簡單，建議使用這個方法）
-```{eval-rst}
-.. raw:: html
+```{tab-set}
-
-
-```
+:::{tab-item} Android
+(aaps-ci-option1-android)=
+:::{include} BrowserBuildO1A.md
+:::
+:::{tab-item} iOS
(aaps-ci-ios-ipad)=
- - iOS 上相容的作法（以 iPad 為例）
-```{eval-rst}
-.. raw:: html
-
-
-
-```
+:::{include} BrowserBuildO1I.md
+:::
+:::{tab-item} 電腦
(aaps-ci-option1-computer)=
-- 電腦上相容的作法（支援 Windows/Mac/Linux）
-
- 打開網頁 https://simplewebserver.org/download.html
-
- 安裝 Simple HTTP Server 如果您是 Windows/Mac 使用者，可以從應用商店安裝。 點擊連結後，系統會詢問您是否允許打開它。 請選擇打開連結。 
-
- 在 Mac 上的範例：
-
- - 取得 → 安裝 → 開啟 
-
- - 按一下 「Get Started」鈕 
-
- - 按一下「New Server」鈕 
+:::{include} BrowserBuildO1C.md
+:::
- - 在文件夾路徑中，選擇包含 aaps-ci-preparation.html 的資料夾，然後按一下「Create Server」鈕。 
-
- - 看到這個畫面表示伺服器已啟動。 
-
- - 請勿關閉 Simple HTTP Server。 請切換到您的瀏覽器並打開 [http://127.0.0.1:8080/aaps-ci-preparation.html](http://127.0.0.1:8080/aaps-ci-preparation.html)
-
- - 後續步驟請參考下方影片，從 1 分 37 秒開始。
-
-```{eval-rst}
-.. raw:: html
-
-
-
```
- 如影片所示，請將他複製到對應的欄位中。
@@ -178,69 +123,28 @@ AAPS 應用程式在建立後會保存在你的 Google 雲端硬碟中：
### AAPS-CI 選項 2 – 上傳現有 JKS
- 適合已經擁有 JKS 並且知道 JKS 密碼和別名的用戶。
- 以下是使用多個平台的範例。
+ - 在以下列表中選擇您的平台， Android（優先選擇）或電腦
-(aaps-ci-option2-android)=
- - Android 上的作法（最簡單，建議使用這個方法）
-```{eval-rst}
-.. raw:: html
-
-
-
-```
-
-(aaps-ci-option2-computer)=
-- 電腦上相容的作法（支援 Windows/Mac/Linux）
-
- 打開網頁 https://simplewebserver.org/download.html
-
- 安裝 Simple HTTP Server 如果您是 Windows/Mac 使用者，可以從應用商店安裝。 點擊連結後，系統會詢問您是否允許打開它。 請選擇打開連結。 
-
- 在 Mac 上的範例：
-
- - 取得 → 安裝 → 開啟 
-
- - 按一下 「Get Started」鈕 
-
- - 按一下「New Server」鈕 
- - 在文件夾路徑中，選擇包含 aaps-ci-preparation.html 的資料夾，然後按一下「Create Server」鈕。 
+```{tab-set}
- - 看到這個畫面表示伺服器已啟動。 
-
- - 請勿關閉 Simple HTTP Server。 請切換到您的瀏覽器並打開 [http://127.0.0.1:8080/aaps-ci-preparation.html](http://127.0.0.1:8080/aaps-ci-preparation.html)
-
- - 後續步驟請參考下方影片，從 2 分 18 秒開始。
+:::{tab-item} Android
+(aaps-ci-option2-android)=
+:::{include} BrowserBuildO2A.md
+:::
-```{eval-rst}
-.. raw:: html
+:::{tab-item} 電腦
+(aaps-ci-option2-computer)=
+:::{include} BrowserBuildO2C.md
+:::
-
-
```
- 如影片所示，請將他複製到對應的欄位中。
-- 而 KEYSTORE_PASSWORD、KEY_ALIAS 和 KEY_PASSWORD 欄位，請在 GitHub 中輸入你的實際密碼和別名。
+- 對於 `KEYSTORE_PASSWORD`、`KEY_ALIAS` 和 `KEY_PASSWORD`，請在 GitHub 中輸入您的實際密碼和別名。
@@ -290,7 +194,7 @@ Google 雲端硬碟授權中的「自訂」欄位，適合熟悉Google Oauth2的
(aaps-ci-troubleshooting)=
## AAPS-CI 問題排除
-(aaps-ci-preparation)=
+(aaps-ci-preparation-web)=
### aaps-ci-preparation 網頁
- 當你使用「檔案管理器」打開 aaps-ci-preparation.html 時，它會在你的手機上啟動一個臨時本地伺服器來顯示網頁並接收 Google Refresh token。
- 如果你看到以下螢幕，這表示你已經一段時間未進行操作，檔案管理器已經關閉本地伺服器。
diff --git a/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO1A.md b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO1A.md
new file mode 100644
index 000000000000..86d3f07dafce
--- /dev/null
+++ b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO1A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+與 Android 相容（最簡單，建議優先選擇）
+
+
+
diff --git a/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO1C.md b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO1C.md
new file mode 100644
index 000000000000..aaa03b8b08f1
--- /dev/null
+++ b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO1C.md
@@ -0,0 +1,38 @@
+- - -
+orphan: true
+- - -
+
+電腦上相容的作法（支援 Windows/Mac/Linux）
+
+打開網頁 [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+安裝 Simple HTTP Server 如果您是 Windows/Mac 使用者，您可以從商店安裝它。 點擊連結後，系統會詢問您是否允許開啟它。 請選擇打開連結。 
+
+在 Mac 上的範例：
+
+- 取得 → 安裝 → 開啟 
+
+- 按一下 「Get Started」鈕 
+
+- 按一下「New Server」鈕 
+
+- 在文件夾路徑中，選擇包含 aaps-ci-preparation.html 的資料夾，然後按一下「Create Server」鈕。 
+
+- 看到這個畫面表示伺服器已啟動。 
+
+- 請勿關閉 Simple HTTP Server。 請切換到您的瀏覽器並打開 [http://127.0.0.1:8080/aaps-ci-preparation.html](http://127.0.0.1:8080/aaps-ci-preparation.html)
+
+- 後續步驟請參考下方影片，從 1 分 37 秒開始。
+
+
+
+
diff --git a/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO1I.md b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO1I.md
new file mode 100644
index 000000000000..20cf0dee24af
--- /dev/null
+++ b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO1I.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+iOS 上相容的作法（以 iPad 為例）
+
+
+
diff --git a/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO2A.md b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO2A.md
new file mode 100644
index 000000000000..4e9bb714db55
--- /dev/null
+++ b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO2A.md
@@ -0,0 +1,17 @@
+- - -
+orphan: true
+- - -
+
+與 Android 相容（最簡單，建議優先選擇）
+
+
+
diff --git a/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO2C.md b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO2C.md
new file mode 100644
index 000000000000..efcf7a19c202
--- /dev/null
+++ b/docs/CROWDIN/zh_TW/SettingUpAaps/BrowserBuildO2C.md
@@ -0,0 +1,37 @@
+- - -
+orphan: true
+- - -
+
+電腦上相容的作法（支援 Windows/Mac/Linux）
+
+打開網頁 [https://simplewebserver.org/download.html](https://simplewebserver.org/download.html)
+
+安裝 Simple HTTP Server 如果您是 Windows / Mac 使用者，您可以從商店安裝它。 點擊連結後，系統會詢問您是否允許打開它。 請選擇打開連結。 
+
+在 Mac 上的範例：
+
+- 取得 → 安裝 → 開啟 
+
+- 按一下 「Get Started」鈕 
+
+- 按一下「New Server」鈕 
+
+- 在文件夾路徑中，選擇包含 aaps-ci-preparation.html 的資料夾，然後按一下「Create Server」鈕。 
+
+- 看到這個畫面表示伺服器已啟動。 
+
+- 請勿關閉 Simple HTTP Server。 請切換到您的瀏覽器並打開 [http://127.0.0.1:8080/aaps-ci-preparation.html](http://127.0.0.1:8080/aaps-ci-preparation.html)
+
+- 後續步驟請參考下方影片，從 2 分 18 秒開始。
+
+
+
diff --git a/docs/CROWDIN/zh_TW/index.md b/docs/CROWDIN/zh_TW/index.md
index 1fc452f44bd0..f9c0d155f622 100644
--- a/docs/CROWDIN/zh_TW/index.md
+++ b/docs/CROWDIN/zh_TW/index.md
@@ -84,17 +84,19 @@ AAPS 簡介 <./Getting-Started/Introduction.md>
```
```{toctree}
-:caption: 3) 設置 AAPS
+:caption: 3) 設定 AAPS
-設置報告伺服器 <./SettingUpAaps/SettingUpTheReportingServer.md>
+設定報告伺服器 <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
-建立 AAPS <./SettingUpAaps/BuildingAaps.md>
+建置 AAPS <./SettingUpAaps/BuildingAaps.md>
+- 瀏覽器建置 <./SettingUpAaps/BrowserBuild.md>
+- 電腦建置 <./SettingUpAaps/ComputerBuild.md>
傳輸和安裝 AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
-設置嚮導 <./SettingUpAaps/SetupWizard.md>
-你的 AAPS 配置 <./SettingUpAaps/YourAapsProfile.md>
+嚮導 <./SettingUpAaps/SetupWizard.md>
+您的 AAPS 設定檔 <./SettingUpAaps/YourAapsProfile.md>
變更 AAPS 配置 <./SettingUpAaps/ChangeAapsConfiguration.md>
-- 配置建置工具 <./SettingUpAaps/ConfigBuilder.md>
+- 配置建構器 <./SettingUpAaps/ConfigBuilder.md>
- 偏好設定 <./SettingUpAaps/Preferences.md>
完成目標 <./SettingUpAaps/CompletingTheObjectives.md>
```
@@ -139,13 +141,15 @@ AAPS for Wear OS <./WearOS/BuildingAapsWearOS.md>
```
```{toctree}
-:caption: 7) AAPS 的維護
+:caption: 7) AAPS 維護
匯出/匯入設定 <./Maintenance/ExportImportSettings.md>
-檢視你的資料 <./Maintenance/Reviewing.md>
-AAPS 發佈說明 <./Maintenance/ReleaseNotes.md>
-文件更新 <./Maintenance/DocumentationUpdate.md>
-更新至新的 AAPS 版本 <./Maintenance/UpdateToNewVersion.md>
+檢查您的資料 <./Maintenance/Reviewing.md>
+AAPS 版本更新說明 <./Maintenance/ReleaseNotes.md>
+文檔更新 <./Maintenance/DocumentationUpdate.md>
+更新到新的 AAPS 版本 <./Maintenance/UpdateToNewVersion.md>
+- 瀏覽器更新 <./Maintenance/UpdateBrowserBuild.md>
+- 電腦更新 <./Maintenance/UpdateComputerBuild.md>
```