Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
49 commits
Select commit Hold shift + click to select a range
1c49492
New translations omnipoddash.md (French)
MilosKozak Jan 14, 2026
ff52c64
New translations omnipoddash.md (Spanish)
MilosKozak Jan 14, 2026
b062156
New translations omnipoddash.md (Czech)
MilosKozak Jan 14, 2026
d13da53
New translations omnipoddash.md (German)
MilosKozak Jan 14, 2026
1fa545b
New translations omnipoddash.md (Greek)
MilosKozak Jan 14, 2026
8f12c73
New translations omnipoddash.md (Hebrew)
MilosKozak Jan 14, 2026
a1a182f
New translations omnipoddash.md (Korean)
MilosKozak Jan 14, 2026
2d581e4
New translations omnipoddash.md (Lithuanian)
MilosKozak Jan 14, 2026
1a19755
New translations omnipoddash.md (Dutch)
MilosKozak Jan 14, 2026
8c826e8
New translations omnipoddash.md (Polish)
MilosKozak Jan 14, 2026
04af736
New translations omnipoddash.md (Portuguese)
MilosKozak Jan 14, 2026
1b50189
New translations omnipoddash.md (Russian)
MilosKozak Jan 14, 2026
a261858
New translations omnipoddash.md (Slovak)
MilosKozak Jan 14, 2026
c956a6c
New translations omnipoddash.md (Turkish)
MilosKozak Jan 14, 2026
094cd57
New translations omnipoddash.md (Chinese Simplified)
MilosKozak Jan 14, 2026
5da4f7a
New translations omnipoddash.md (Chinese Traditional)
MilosKozak Jan 15, 2026
65b9118
New translations omnipoddash.md (Portuguese, Brazilian)
MilosKozak Jan 15, 2026
91c9940
New translations omnipoddash.md (Romanian)
MilosKozak Jan 15, 2026
9e3c538
New translations omnipod_address_in_use.png (Romanian)
MilosKozak Jan 15, 2026
eb64e30
New translations omnipod_address_in_use.png (French)
MilosKozak Jan 15, 2026
07beec4
New translations omnipod_address_in_use.png (Spanish)
MilosKozak Jan 15, 2026
8c03330
New translations omnipod_address_in_use.png (Czech)
MilosKozak Jan 15, 2026
a3c31bb
New translations omnipod_address_in_use.png (German)
MilosKozak Jan 15, 2026
41437e8
New translations omnipod_address_in_use.png (Greek)
MilosKozak Jan 15, 2026
81836a6
New translations omnipod_address_in_use.png (Hebrew)
MilosKozak Jan 15, 2026
a0013a6
New translations omnipod_address_in_use.png (Korean)
MilosKozak Jan 15, 2026
c7f4eee
New translations omnipod_address_in_use.png (Lithuanian)
MilosKozak Jan 15, 2026
b11a5da
New translations omnipod_address_in_use.png (Dutch)
MilosKozak Jan 15, 2026
64f7cf2
New translations omnipod_address_in_use.png (Polish)
MilosKozak Jan 15, 2026
68d2664
New translations omnipod_address_in_use.png (Portuguese)
MilosKozak Jan 15, 2026
e418414
New translations omnipod_address_in_use.png (Russian)
MilosKozak Jan 15, 2026
0127309
New translations omnipod_address_in_use.png (Slovak)
MilosKozak Jan 15, 2026
33ce29d
New translations omnipod_address_in_use.png (Turkish)
MilosKozak Jan 15, 2026
31fdf9b
New translations omnipod_address_in_use.png (Chinese Simplified)
MilosKozak Jan 15, 2026
eaa2bfb
New translations omnipod_address_in_use.png (Chinese Traditional)
MilosKozak Jan 15, 2026
619d900
New translations omnipod_address_in_use.png (Portuguese, Brazilian)
MilosKozak Jan 15, 2026
ebd8e9a
New translations aapsscreens.md (Chinese Traditional)
MilosKozak Jan 15, 2026
a366d48
New translations keyaapsfeatures.md (Chinese Traditional)
MilosKozak Jan 15, 2026
8fa5a63
New translations omnipoddash.md (Chinese Traditional)
MilosKozak Jan 15, 2026
9e29cfe
New translations preferences.md (Chinese Traditional)
MilosKozak Jan 15, 2026
f4199c9
New translations releasenotes.md (Chinese Traditional)
MilosKozak Jan 15, 2026
709d1ae
New translations autotune.md (Chinese Traditional)
MilosKozak Jan 15, 2026
26a7710
New translations omnipoderos.md (Chinese Traditional)
MilosKozak Jan 15, 2026
4150498
New translations medtrumnano.md (Chinese Traditional)
MilosKozak Jan 15, 2026
a37f47a
New translations completingtheobjectives.md (Chinese Traditional)
MilosKozak Jan 15, 2026
5da026f
New translations setupwizard.md (Chinese Traditional)
MilosKozak Jan 15, 2026
994a7e1
New translations youraapsprofile.md (Chinese Traditional)
MilosKozak Jan 15, 2026
93e6db7
New translations bluetoothtroubleshooting.md (Chinese Traditional)
MilosKozak Jan 15, 2026
7d58116
New translations profiletuning.md (Chinese Traditional)
MilosKozak Jan 15, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. Nach der zweiten oder dritten Wiederholung erhälst Du die Möglichkeit, den Pod zu entfernen.
4. Sobald der alte Pod gelöscht ist, kannst Du einen neuen Pod aktivieren.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. After the second or third retry you will get the option to remove the pod.
4. Once the old pod is removed you will be able to activate a new pod.

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,18 @@ To remove the old pod session:
3. 经过两到三次重试后,系统将提供移除储药器的选项。
4. 待旧储药器移除后,即可激活新储药器。

### Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.

If you receive this error when attempting to Initialize a new pod **AAPS** fails as it still has settings for an old pod stored in configuration.

![omnipod_address_in_use](../images/DASH_images/Errors/omnipod_address_in_use.png)

This can happen if you restore from a backup, or a pod deactivation fails.

To resolve keep clicking on `RETRY` until a `Discard` option is shown, then discard. This procedure should work for De-Activating a pod too.

You should now be able to Activate a new pod.

---
### Reinstalling AAPS

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6 changes: 3 additions & 3 deletions docs/CROWDIN/zh_TW/AdvancedOptions/Autotune.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,17 +8,17 @@ Autotune 外掛自 [3.4](#version3400) 版起在 AAPS 釋出中提供,但預

## 顯示 Autotune 外掛

Create an empty file named `enable_autotune` in the `extra` subfolder of your phone [AAPS directory](#preferences-maintenance-settings).
在手機的 [AAPS 目錄](#preferences-maintenance-settings) 下的 `extra` 子資料夾中,建立一個名為 `enable_autotune` 的空白檔案。

***NOTE: Ensure you check in the **AAPS** settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.***
***注意:請在 **AAPS** 設定中確認你的 AAPS 目錄位置,並確定你把檔案放在正確的目錄裡。已有多人因把檔案放錯資料夾而受影響。***

![啟用 Autotune](../images/Autotune/Autotune_0.png)

重新啟動 AAPS 後,Autotune 會顯示在組態建置工具中。

![自動調整外掛](../images/Autotune/Autotune_1.png)

***NOTE: If you are unable to see the `Autotune` option you will need to click the highlighted (red box) arrow to expand and show all settings in the `General` section.***
***注意:若看不到 `Autotune` 選項,請點擊標示(紅框)的箭頭展開,以顯示 `General` 區段中的所有設定。***

## Autotune 使用者介面

Expand Down
4 changes: 2 additions & 2 deletions docs/CROWDIN/zh_TW/CompatiblePumps/MedtrumNano.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,15 +45,15 @@

### 步驟1:選擇Medtrum幫浦

#### Option 1: New installations
#### 選項 1:新安裝

如果你是首次安裝AAPS,**安裝嚮導**將引導你完成AAPS的安裝過程。 當你到達幫浦選擇時,請選擇「Medtrum」。

如果有疑問,你也可以選擇「虛擬幫浦」,並在設置完成後選擇「Medtrum」(見選項2)。

![安裝嚮導](../images/medtrum/SetupWizard.png)

#### Option 2: The Config Builder
#### 選項 2:組態建置工具

在現有安裝中,可以在[組態建置工具 > 幫浦](#Config-Builder-pump)中選擇**Medtrum**幫浦:

Expand Down
Loading