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 3782067d33ee..aebc86fff467 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
@@ -4,87 +4,87 @@ orphan: true
# 罗氏Accu-Chek Combo胰岛素泵
-**本软件是DIY解决方案的一部分而非完整的产品，需要您仔细研学包括使用方法在内的系统知识。 它无法为您全权处理糖尿病治疗的全部，但如果你愿意投入必要的时间，它将有助于改善病情并提高生活质量。 不要想着一蹴而就，请给自己足够的学习时间。 只有你才能对自己的行为负责。**
+**该软件是DIY解决方案的一部分，并非成品，但需要您阅读、学习并理解系统，包括其使用方法。 该工具并非全自动糖尿病管理系统，但如果您愿意投入必要时间，它能帮助您改善糖尿病状况并提高生活质量。 切勿操之过急，给自己留出学习的时间。 使用后果由您自行承担。**
-## Hardware and software requirements
+## 硬件和软件要求
-* A Roche Accu-Chek Combo (any firmware, they all work).
-* A Smartpix or Realtyme device together with the 360 Configuration Software to configure the pump. (Roche sends out Smartpix devices and the configuration software free of charge to their customers upon request.)
-* A compatible phone. Android 9 (Pie) or newer is a must. If using LineageOS, the minimum supported version is 16.1. See [release notes](#maintenance-android-version-aaps-version) for details.
-* The AndroidAPS app installed on your phone.
+* Roche Accu-Chek Combo 泵（任何固件版本均可）。
+* 需使用Smartpix或Realtyme设备配合360配置软件来设置胰岛素泵。 （罗氏公司应客户要求可免费提供Smartpix设备及配置软件。）
+* 一部兼容的手机。 必须是 Android 9 (Pie) 或更新版本。 如使用LineageOS，最低支持版本为16.1。 详情请参阅[版本说明](#maintenance-android-version-aaps-version)。
+* 您手机上安装的AndroidAPS应用程序。
-Some phones may work better than others, depending on their quality of Bluetooth support and whether or not they have additional, very aggressive power saving logic. A list of phones can be found in the [AAPS Phones](#Phones-list-of-tested-phones) document. Please be aware that this is not complete list and reflects personal user experience. You are encouraged to also enter your experience and thereby help others (these projects are all about paying it forward).
+某些手机可能比其他手机表现更好，这取决于其蓝牙支持的质量以及是否具有额外且非常激进的省电逻辑。 手机列表详见[AAPS Phones](#Phones-list-of-tested-phones)文档。 请注意，这并非完整列表，仅反映用户个人使用体验。 我们鼓励您分享使用体验，以此帮助他人（这些项目的核心理念正是薪火相传）。
(combov2-before-you-begin)=
-## Before you begin
+## 在您开始前
-**SAFETY FIRST** - do not attempt this process in an environment where you cannot recover from an error. Keep your Smartpix / Realtyme device handy, along with the 360 Configuration Software. Plan on spending about an hour for setting everything up and checking that everything is working properly.
+**安全第一**——请勿在无法从错误中恢复的环境中进行此操作。 请将您的Smartpix/Realtyme设备及360配置软件置于手边备用。 预计需花费约1小时完成全部设置并确保各项功能正常运行。
-Be aware of the following limitations:
+请注意以下限制条件：
-* Extended bolus and multiwave bolus are currently not supported (you can use [Extended Carbs](../DailyLifeWithAaps/ExtendedCarbs.md) instead).
-* Only one basal profile (the first one) is supported.
-* The loop is disabled if the currently active profile on the pump isn't profile no. 1. This continues until profile no. 1 is made the active one; when that is done, the next time AAPS connects (either on its own after a while or because the user presses the Refresh button in the combov2 user interface), it will notice that profile no. 1 is the current one, and enable the loop again.
-* If the loop requests a running TBR to be cancelled, the Combo will set a TBR of 90% or 110% for 15 minutes instead. This is because actually cancelling a TBR causes an alert on the pump which causes a lot of vibrations, and these vibrations cannot be disabled.
-* Bluetooth connection stability varies with different phones, causing "pump unreachable" alerts, where no connection to the pump is established anymore. If that error occurs, make sure Bluetooth is enabled, press the Refresh button in the Combo tab to see if this was caused by an intermitted issue and if still no connection is established, reboot the phone which should usually fix this.
-* There is another issue were a restart doesn't help but a button on the pump must be pressed (which resets the pump's Bluetooth stack), before the pump accepts connections from the phone again.
-* Setting a TBR on the pump is to be avoided since the loop assumes control of TBRs. Detecting a new TBR on the pump might take up to 20 minutes and the TBR's effect will only be accounted from the moment it is detected, so in the worst case there might be 20 minutes of a TBR that is not reflected in IOB.
+* 当前不支持扩展大剂量和多波大剂量功能（可使用[扩展碳水化合物](../DailyLifeWithAaps/ExtendedCarbs.md)功能替代）。
+* 仅支持一个基础率配置文件（第一个配置文件）。
+* 若当前泵上激活的配置文件不是1号配置文件，循环功能将被禁用。 此状态将持续至1号配置文件被激活；激活后，待AAPS下次连接时（系统自动重连或用户点击combov2界面的刷新按钮），将检测到1号配置文件为当前使用配置，随即重新启用循环功能。
+* 若循环系统请求取消正在运行的临时基础率，Combo泵将改为设置15分钟90%或110%的临时基础率替代。 这是因为直接取消临时基础率会触发泵体警报并伴随强烈震动，且该震动功能无法关闭。
+* 蓝牙连接稳定性因手机型号而异，可能导致"无法连接泵体"警报，此时将完全无法建立与泵的连接。 若出现此错误，请确保蓝牙已启用，点击Combo标签页的刷新按钮以排查是否为间歇性问题；若仍无法连接，重启手机通常可解决。
+* 还存在另一种情况：重启无效时，必须按压泵体按钮（重置泵的蓝牙协议栈）才能恢复手机与泵的连接功能。
+* 应避免在泵体上直接设置临时基础率，因循环系统已接管临时基础率控制权。 检测泵上新设置的临时基础率最长可能需要20分钟，且其效果仅从被检测到的那一刻起计算，因此在最坏情况下，可能有20分钟的临时基础率未被计入活性胰岛素量。
-If you have been using the old Combo driver that depends on the separate Ruffy app, and want to move to this new one, note that the pairing has to be done again - Ruffy and the new Combo driver are not able to share pairing information. Also, make sure that Ruffy is _not_ running. If in doubt, long-press the Ruffy app icon to bring up a context menu. In that menu, press on "App Info". In the UI that just opened up, press "Force stop". That way, it is ensured that an active Ruffy instance cannot interfere with the new driver.
+若您曾使用依赖独立Ruffy应用的旧版Combo驱动，现需切换至新版驱动时，请注意必须重新进行配对操作——Ruffy与新版Combo驱动无法共享配对信息。 同时，请确保Ruffy应用_未处于_运行状态。 如有疑问，请长按Ruffy应用图标调出上下文菜单。 在该菜单中，点击"应用信息"。 在打开的界面中，点击"强制停止"。 如此可确保正在运行的Ruffy实例不会干扰新版驱动。
-Also, if you are migrating from the old driver, be aware that the new driver communicates a bolus command in an entirely different way to the Combo that is much faster, so don't be surprised when a bolus starts immediately regardless of the dosage. Furthermore, the general suggestions, tips and tricks etc. about dealing with Ruffy pairing and connection problems do not apply here, since this is an entirely new driver that shares no code with the old one.
+此外，若您正从旧版驱动迁移，请注意新版驱动以完全不同的方式向Combo泵传输大剂量指令，速度显著提升，因此无论剂量大小，大剂量都将立即开始执行，无需惊讶。 此外，关于Ruffy配对及连接问题的通用建议与技巧均不适用于此，因新版驱动采用全新架构，与旧版驱动无任何代码关联。
-This new driver is currently written to support the following languages on the Combo. (This is unrelated to the language in AAPS - it is the language shown on the Combo's LCD itself.)
+新版驱动目前支持以下Combo泵语言版本。 （此设置与AAPS应用语言无关——特指Combo泵液晶屏显示的语言。）
-* English
-* Spanish
-* French
-* Italian
-* Russian
-* Turkish
-* Polish
-* Czech
-* Hungarian
-* Slovak
-* Romanian
-* Croatian
-* Dutch
-* Greek
-* Finnish
-* Norwegian
-* Portuguese
-* Swedish
-* Danish
-* German
-* Slovenian
-* Lithuanian
+* 英语
+* 西班牙语
+* 法语
+* 意大利语
+* 俄语
+* 土耳其语
+* 波兰语
+* 捷克语
+* 匈牙利语
+* 斯洛伐克语
+* 罗马尼亚语
+* 克罗地亚语
+* 荷兰语
+* 希腊语
+* 芬兰语
+* 挪威语
+* 葡萄牙语
+* 瑞典语
+* 丹麦语
+* 德语
+* 斯洛文尼亚语
+* 立陶宛语
-**Important**: If your pump is set to a language that is not part of this list, please contact the developers, and set the pump's language to one in this list. Otherwise, the driver won't work properly.
+**重要提示**：若您的泵体语言设置不在本列表范围内，请联系开发人员，并将泵体语言切换至列表内选项。 否则该驱动将无法正常运行。
-## Phone setup
+## 手机设置
-It is very important to make sure that battery optimizations are turned off. AAPS already auto-detects when it is subject to these optimizations, and requests in its UI that these be turned off. But, on modern Android phones, Bluetooth _itself_ is an app (a system app). And, usually, that "Bluetooth app" is run _with battery optimizations on by default_. As a result, Bluetooth can refuse to respond when the phone aims to save power because it kills off the Bluetooth app. This means that in that Bluetooth system app's settings, battery optimizations must be turned off as well. Unfortunately, how one can find that Bluetooth system app differs between phones. In stock Android, go to Settings -> Apps -> See all N apps (N = the number of apps on your phone). Then, open the menu to the top right corner, tap on "Show system" or "Show system apps" or "All apps". Now, in the newly expanded list of apps, look for a "Bluetooth" app. Select it, and on its "App info" UI, tap on "Battery". There, disable battery optimizations (sometimes called "battery usage").
+务必确保已关闭电池优化功能。 AAPS已自动检测是否受电池优化影响，并在界面中提示要求关闭该功能。 但在现代安卓手机上，蓝牙_本身_就是一个应用（系统应用）。 通常，该"蓝牙应用"_默认启用电池优化功能_。 这将导致手机为省电终止蓝牙应用时，蓝牙功能可能停止响应。 这意味着必须在蓝牙系统应用的设置中同时关闭电池优化功能。 遗憾的是，不同手机查找该蓝牙系统应用的方式各不相同。 在原生安卓系统中，请前往设置 -> 应用 -> 查看全部N个应用（N代表您手机上的应用总数）。 然后点击右上角菜单，选择"显示系统应用"或"全部应用"。 现在，在展开的应用列表中查找"蓝牙"应用。 选择该应用后，在其"应用信息"界面点击"电池"选项。 在此界面关闭电池优化功能（有时称为"电池用量"）。
-## Combo setup
+## Combo 设置
-* Configure the pump using the Accu-Chek 360 Configuration Software. If you do not have the software, please contact your Accu-Chek hotline. They usually send registered users a CD with the "360° Pump Configuration Software" and a SmartPix USB-infrared connection device (the Realtyme device also works if you have that).
+* 请使用Accu-Chek 360配置软件设置泵体参数。 若未获取该软件，请联系Accu-Chek服务热线。 客服通常会给注册用户寄送含"360°泵体配置软件"的光盘及SmartPix USB红外连接设备（若持有Realtyme设备亦可使用）。
- - **Required settings** (marked green in screenshots):
+ - **必要设置**（截图中绿色标记部分）：
- * Set/leave the menu configuration as "Standard", this will show only the supported menus/actions on the pump and hide those which are unsupported (extended/multiwave bolus, multiple basal rates), which cause the loop functionality to be restricted when used because it's not possible to run the loop in a safe manner when used.
- * Verify the _Quick Info Text_ is set to "QUICK INFO" (without the quotes, found under _Insulin Pump Options_).
- * Set TBR _Maximum Adjustment_ to 500%
- * Disable _Signal End of Temporary Basal Rate_
- * Set TBR _Duration increment_ to 15 min
- * Enable Bluetooth
+ * 将/保持菜单配置设为"标准模式"，该设置将仅显示泵体支持的菜单/操作，并隐藏不受支持的功能（扩展/多波大剂量、多段基础率）。使用非支持功能会导致闭环功能受限，因其无法以安全方式运行闭环系统。
+ * 确认_快速信息文本_设置为"QUICK INFO"（不带引号，位于_胰岛素泵选项_下）。
+ * 将临时基础率_最大调节幅度_设为500%
+ * 禁用_临时基础率结束提示_
+ * 将临时基础率_持续时间增量_设为15分钟
+ * 启用蓝牙
- - **Recommended settings** (marked blue in screenshots)
+ - **推荐设置**（截图中蓝色标记部分）
- * Set low cartridge alarm to your liking
- * Configure a max bolus suited for your therapy to protect against bugs in the software
- * Similarly, configure maximum TBR duration as a safeguard. Allow at least 3 hours, since the option to disconnect the pump for 3 hours sets a 0% for 3 hours.
- * Enable key lock on the pump to prevent bolusing from the pump, esp. when the pump was used before and quick bolusing was a habit.
- * Set display timeout and menu timeout to the minimum of 5.5 and 5 respectively. This allows the AAPS to recover more quickly from error situations and reduces the amount of vibrations that can occur during such errors
+ * 请按需设置药筒低量警报
+ * 请根据治疗方案设置最大单次大剂量值，以防软件漏洞风险
+ * 同理，请设置临时基础率最长持续时间作为安全防护。 请至少允许3小时，因为"断开泵体3小时"的选项会设置3小时0%输注率。
+ * 启用泵体按键锁功能以防止通过泵体直接输注大剂量，特别是当泵体之前使用过且用户已养成快速输注习惯时。
+ * 将屏幕超时和菜单超时分别设为最小值5.5和5。 这能让AAPS更快从错误状态恢复，并减少此类错误发生时可能产生的振动次数。
@@ -92,17 +92,17 @@ It is very important to make sure that battery optimizations are turned off. AAP
- 
+ 
-## Activating the driver and pairing it with the Combo
+## 激活驱动程序并与Combo配对
-* Select the "Accu-Chek Combo" driver in [Config builder > Pump](../SettingUpAaps/ConfigBuilder.md). **Important**: There is the old driver, called "Accu-Chek Combo (Ruffy)", in that list as well. Do _not_ select that one.
+* 在[配置生成器 > 泵体](../SettingUpAaps/ConfigBuilder.md)中选择"Accu-Chek Combo"驱动程序。 **重要提示**：该列表中同时存在旧版驱动程序"Accu-Chek Combo (Ruffy)"。 请_勿_选择该选项。
-* Tap the cog-wheel to open the driver settings.
+* 点击齿轮图标打开驱动程序设置。
-* In the settings user interface, tap on the button 'Pair with pump' at the top of the screen. This opens the Combo pairing user interface. Follow the instructions shown on screen to start pairing. When Android asks for permission to make the phone visible to other Bluetooth devices, press "allow". Eventually, the Combo will show a custom 10-digit pairing PIN on its screen, and the driver will request it. Enter that PIN in the corresponding field.
+* 在设置界面中，点击屏幕顶部的"与泵体配对"按钮。 这将打开Combo配对界面。 请按照屏幕提示开始配对操作。 当Android系统请求允许手机对其他蓝牙设备可见时，请点击"允许"。 最终，Combo将在屏幕上显示10位自定义配对PIN码，驱动程序将要求输入该码。 在对应字段中输入该PIN码。
@@ -114,115 +114,115 @@ It is very important to make sure that battery optimizations are turned off. AAP
-* When the driver asks for the 10-digit PIN that is shown on the Combo, and the code is entered incorrectly, this is shown: 
+* 当驱动程序要求输入Combo显示的10位PIN码且输入错误时，将显示如下提示：
-* Once pairing is done, the pairing user interface is closed by pressing the OK button in the screen that states that pairing succeeded. After it is closed, you return to the driver settings user interface. The 'Pair with pump' button should now be greyed out and disabled.
+* 配对完成后，在显示"配对成功"的界面点击OK按钮即可关闭配对界面。 关闭后将返回驱动程序设置界面。 此时"与泵体配对"按钮应显示为灰色不可用状态。
- The Accu-Chek Combo tab looks like this after successfully pairing:
+ 成功配对后，Accu-Chek Combo标签页显示如下：
- if however there is no pairing with the Combo, the tab looks like this instead:
+ 若未与Combo配对成功，标签页将显示如下：
-* To verify your setup (with the pump **disconnected** from any cannula to be safe!) use AAPS to set a TBR of 500% for 15 min and issue a bolus. The pump should now have a TBR running and the bolus in the history. AAPS should also show the active TBR and delivered bolus.
+* 为验证设置（为确保安全，请将泵体**断开**与任何输注管路连接），使用AAPS设置500%的临时基础率持续15分钟并执行一次大剂量输注。 此时泵体应显示临时基础率正在运行，且历史记录中可见大剂量输注信息。 AAPS也应显示当前运行的临时基础率及已输注的大剂量。
-* On the Combo, it is recommended to enable the key lock to prevent bolusing from the pump, esp. when the pump was used before and using the "quick bolus" feature was a habit.
+* 建议在Combo上启用按键锁功能以防止通过泵体直接输注大剂量，特别是当泵体之前使用过且用户已养成使用"快速大剂量"功能的习惯时。
-## Notes about pairing
+## 关于配对的注意事项
-The Accu-Chek Combo was developed before Bluetooth 4.0 was released, and just one year after the very first Android version was released. This is why its way of pairing with other devices is not 100% compatible with how it is done in Android today. To fully overcome this, AAPS would need system level permissions, which are only available for system apps. These are installed by the phone makers into the phone - users cannot install system apps.
+Accu-Chek Combo的开发时间早于蓝牙4.0发布，距离首个Android版本问世仅一年。 因此其设备配对方式与现行Android系统的标准配对流程并非完全兼容。 要彻底解决此问题，AAPS需获取系统级权限，而该权限仅对系统应用开放。 这些系统应用由手机制造商预装——用户无法自行安装系统级应用。
-The consequence of this is that pairing will never be 100% without problems, though it is greatly improved in this new driver. In particular, during pairing, Android's Bluetooth PIN dialog can briefly show up and automatically go away. But sometimes, it stays on screen, and asks for a 4-digit PIN. (This is not to be confused with the 10-digit Combo pairing PIN.) Do not enter anything, just press cancel. If pairing does not continue, follow the instructions on screen to retry the pairing attempt.
+其结果是配对过程永远无法完全避免问题，尽管新版驱动程序已大幅改善此状况。 特别说明：配对过程中，Android系统的蓝牙PIN码对话框可能会短暂闪现后自动消失。 但有时该对话框会持续显示，并要求输入4位PIN码。 （请注意：这与Combo要求的10位配对PIN码不同） 无需输入任何内容，直接点击取消即可。 若配对未继续进行，请按屏幕提示重试配对操作。
(combov2-tab-contents)=
-## Accu-Chek Combo tab contents
+## Accu-Chek Combo 选项卡内容
-The tab shows the following information when a pump was paired (items are listed from top to bottom):
+当泵体完成配对后，该标签页将显示以下信息（条目按从上至下顺序排列）：
-1. _Driver state_: The driver can be in one of the following states:
- - "Disconnected" : There is no Bluetooth connection; the driver is in this state most of the time, and only connects to the pump when needed - this saves power
- - "Connecting"
- - "Checking pump" : the pump is connected, but the driver is currently performing safety checks to ensure that everything is OK and up to date
- - "Ready" : the driver is ready to accept commands from AAPS
- - "Suspended" : the pump is suspended (shown as "stopped" in the Combo)
- - "Executing command" : an AAPS command is being executed
- - "Error" : an error occurred; the connection was terminated, any ongoing command was aborted
-2. _Last connection_: How many minutes ago did the driver successfully connect to the Combo; if this goes beyond 30 minutes, this item is shown with a red color
-3. _Current activity_: Additional detail about what the pump is currently doing; this is also where a thin progress bar can show a command's execution progress, like setting a basal profile
-4. _Battery_: Battery level; the Combo only indicates "full", "low", "empty" battery, and does not offer anything more accurate (like a percentage), so only these three levels are shown here
-5. _Reservoir_: How many IU are currently in the Combo's reservoir
-6. _Last bolus_: How many minutes ago the last bolus was delivered; if none was delivered yet after AAPS was started, this is empty
-7. _Temp basal_: Details about the currently active temporary basal; if none is currently active, this is empty
-8. _Base basal rate_: Currently active base basal rate ("base" means the basal rate without any active TBR influencing the basal rate factor)
-9. _Serial number_: Combo serial number as indicated by the pump (this corresponds to the serial number shown on the back of the Combo)
-10. _Bluetooth address_: The Combo's 6-byte Bluetooth address, shown in the `XX:XX:XX:XX:XX:XX` format
-
-The Combo can be operated through Bluetooth in the _remote-terminal_ mode or in the _command_ mode. The remote-terminal mode corresponds to the "remote control mode" on the Combo's meter, which mimics the pump's LCD and four buttons. Some commands have to be performed in this mode by the driver, since they have no counterpart in the command mode. That latter mode is much faster, but, as said, limited in scope. When the remote-terminal mode is active, the current remote-terminal screen is shown in the field that is located just above the Combo drawing at the bottom. When the driver switches to the command mode however, that field is left blank.
-
-(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)).
+1. _驱动程序状态_：驱动程序可能处于以下任一状态：
+ - "已断开连接"：蓝牙未建立连接；驱动程序大部分时间处于此状态，仅在需要时连接泵体——这有助于节省电量
+ - "正在连接"
+ - "正在检查泵体"：已连接泵体，但驱动程序正在执行安全检查以确保一切正常且数据最新
+ - "准备就绪"：驱动程序已准备好接收来自AAPS的指令
+ - "已暂停"：泵体处于暂停状态（在Combo上显示为"已停止"）
+ - "正在执行指令"：AAPS指令正在处理中
+ - "错误"：发生异常；连接已中断，所有进行中的指令均被终止
+2. _最后连接时间_：显示驱动程序上次成功连接Combo的分钟数；若超过30分钟未连接，此项将显示为红色
+3. _当前活动_：详细显示泵体当前执行的操作；此处细进度条可显示指令执行进度（如设置基础率配置文件）
+4. _电池状态_：显示电池电量；Combo仅提供"满电"、"低电量"、"无电"三种粗略指示（无百分比等精确数据），故此处仅显示这三档状态
+5. _储药器_：显示Combo储药器中当前剩余的药量（单位：IU）
+6. _最后大剂量_：显示最近一次大剂量输注的分钟数；若AAPS启动后未执行过大剂量输注，此项为空
+7. _临时基础率_：显示当前运行的临时基础率详情；若无临时基础率运行，此项为空
+8. _基础基础率_：当前生效的基础基础率（"基础"指不受临时基础率影响的基准基础率数值）
+9. _序列号_：泵体显示的Combo序列号（与Combo背面标注的序列号一致）
+10. _蓝牙地址_：Combo的6字节蓝牙地址，以`XX:XX:XX:XX:XX:XX`格式显示
+
+Combo可通过蓝牙在_远程终端_模式或_指令_模式下运行。 远程终端模式对应Combo血糖仪上的"遥控模式"，可模拟泵体LCD屏及四个按键的操作。 由于部分操作在指令模式下无法实现，驱动程序必须在此模式下执行这些特定指令。 指令模式虽速度更快，但如前所述，其功能范围存在局限。 当远程终端模式激活时，当前远程终端界面会显示在底部Combo图示上方的区域中。 但当驱动程序切换至指令模式时，该区域将保持空白。
+
+（用户无法干预该行为；驱动程序完全自主决定使用何种模式。 此处说明仅为让用户了解为何有时能在该区域看到Combo界面。）
+
+最底部设有"刷新"按钮。 点击该按钮可立即触发泵体状态更新。 该按钮还用于通知AAPS先前发现的错误已修复，可重新检查系统状态是否正常（详见下文[警报相关章节](#alerts-warnings-and-errors-and-how-they-are-handled)）。
## 偏好设置
-These preferences are available for the combo driver (items are listed from top to bottom):
+以下是移宇驱动程序的可配置选项（按从上至下顺序排列）：
-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).
-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.
+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)。
+6. _启用Combo详细日志记录_：该选项将大幅增加驱动程序生成的日志数据量。 **注意**：除非开发者要求，否则请勿启用此选项。 否则可能大幅增加AndroidAPS日志冗余信息，降低日志可用性。
-Most users only ever use the top two items, the _Pair with pump_ and _Unpair pump_ buttons.
+大多数用户仅使用顶部两项功能：_与泵体配对_和_解除泵体配对_按钮。
(combov2-autodetections)=
-## Autodetecting and automatically entering battery and reservoir changes
+## 自动检测并执行电池及储药器更换操作
-The driver is capable of detecting battery and reservoir changes by keeping track of the battery and reservoir levels. If the battery level was reported by the Combo as low the last time the pump status was updated, and now, during the new pump status update, the battery level shows up as normal, then the driver concludes that the user must have replaced the battery. The same logic is used for the reservoir level: If it now is higher than before, this is interpreted as a reservoir change.
+驱动程序通过持续监测电池电量及储药器余量，可自动识别电池更换与储药器更换操作。 若Combo在上次状态更新时报告电池电量低，而本次更新显示电量恢复正常，驱动程序将判定用户已完成电池更换。 储药器余量采用相同逻辑判定：若当前余量高于先前数值，则视为已完成储药器更换。
-This only works if the battery and reservoir are replaced when these levels are reported as low _and_ the battery and reservoir are sufficiently filled.
+此功能仅在电池/储药器余量报告为低值时进行更换_且_新电池/储药器已充分填充的情况下生效。
-These autodetections can be turned off in the Preferences UI.
+用户可在偏好设置界面关闭上述自动检测功能。
(combov2-alerts)=
-## Alerts (warnings and errors) and how they are handled
+## 警报（警告与错误）及其处理机制
-The Combo shows alerts as remote-terminal screens. Warnings are shown with a "Wx" code (x is a digit), along with by a short description. One example is "W7", "TBR OVER". Errors are similar, but show up with an "Ex" code instead.
+Combo通过远程终端界面显示警报信息。 警告信息以"Wx"代码（x为数字）及简短描述形式呈现。 例如"W7"表示"临时基础率超限"。 错误信息采用相同格式，但代码前缀为"Ex"。
-Certain warnings are automatically dismissed by the driver. These are:
+特定警告可由驱动程序自动消除。 自动消除的警告包括：
-- W1 "reservoir low" : the driver turns this into a "low reservoir" warning that is shown on the AAPS main tab
-- 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
+- W1 "储药器余量低"：驱动程序将其转换为AAPS主界面显示的"低药量"警告
+- W2 "电池电量低"：驱动程序将其转换为AAPS主界面显示的"低电量"警告
+- W3、W6、W7、W8：此类警告仅向用户提供参考信息，驱动程序可安全执行自动消除
-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.
+其余警告_不会_被自动消除。 此外，错误信息_绝不_会自动消除。 这两类警报采用相同处理机制：触发后驱动程序将在AAPS界面弹出警示对话框，并立即终止所有正在执行的指令。 随后驱动程序将切换至"错误"状态（详见[上文Accu-Chek Combo标签页说明](#accu-chek-combo-tab-contents)）。 该状态下禁止执行任何指令。 用户须在胰岛素泵上处理错误，例如发生输注阻塞错误时可能需要更换输注管路。 用户处理完错误后，点击Accu-Chek Combo标签页的"刷新"按钮即可恢复正常操作。 驱动程序将重新连接Combo并更新状态，检查屏幕是否仍显示错误信息等。 此外，驱动程序会定期自动刷新胰岛素泵状态，因此并非必须手动点击该按钮。
-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.
+大剂量注射属于特殊情况。 该操作在Combo的命令模式下执行，此模式不会在注射过程中报告出现的警报。 因此，驱动程序_无法_在大剂量注射期间自动消除警告。 这意味着胰岛素泵将持续发出蜂鸣声直至大剂量注射完成。 大剂量注射期间最常见的警报通常是W1"储药器余量低"。 **切勿**在大剂量注射过程中手动消除胰岛素泵上的Combo警告。 此操作可能导致大剂量注射中断。 驱动程序将在大剂量注射完成后处理该警告。
-Alerts that happen while the driver is not connected to the Combo will not be noticed by the driver. The Combo has no way of automatically pushing that alert to the phone; it is always the phone that has to initiate the connection. As a consequence, the alert will persist until the driver connects to the pump. Users can press the "Refresh" button to trigger a connection and let the driver handle the alert right then and there (instead of waiting until AAPS itself decides to initiate a connection).
+驱动程序未连接Combo时发生的警报将无法被检测到。 Combo无法自动推送警报至手机，必须由手机主动发起连接。 因此，警报将持续显示直至驱动程序连接胰岛素泵。 用户可点击"刷新"按钮立即建立连接，使驱动程序当场处理警报（无需等待AAPS自行发起连接）。
-**IMPORTANT**: If an error occurs, or a warning shows up that isn't one of those that are automatically dismissed, the driver enters the error state. In that state, the loop **WILL BE BLOCKED** until the pump status is refreshed! It is unblocked after the pump status is updated (either by manual "Refresh" button press or by the driver's eventual auto-update) and no error is shown anymore.
+**重要提示**：若发生错误或出现非自动消除类警告，驱动程序将进入错误状态。 在此状态下，闭环系统**将被阻断**，直至刷新胰岛素泵状态！ 当胰岛素泵状态更新后（通过手动点击"刷新"按钮或驱动程序最终自动更新）且不再显示错误时，阻断状态即解除。
-## Things to be careful about when using the Combo
+## 使用Combo时的注意事项
-* 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.
+* 请注意这并非商业化产品，尤其在初始阶段，用户需持续监控并充分理解系统功能、使用限制及潜在故障模式。 强烈建议不具备完全理解该系统能力的人员不要使用。
+* 由于Combo远程控制功能的工作原理，多项操作（特别是设置基础率配置文件）相比其他胰岛素泵更为缓慢。 这是Combo无法克服的固有缺陷。
+* 切勿在胰岛素泵上设置或取消临时基础率。 闭环系统需完全掌控临时基础率，否则无法可靠运行，因无法确定用户在胰岛素泵上设置的临时基础率起始时间。
+* 当AAPS与胰岛素泵通信时（泵体显示蓝牙标识期间），请勿操作泵体任何按键。 此操作将中断蓝牙连接。 仅当建立连接出现问题时方可操作（参见[上文"使用前准备"章节](#before-you-begin)）。
+* 大剂量注射期间请勿操作任何按键。 特别提醒：切勿通过按键操作来消除警报。 具体原因详见[警报相关章节](#alerts-warnings-and-errors-and-how-they-are-handled)的详细说明。
-## Checklist for when no connection can be established with the Combo
+## Combo无法建立连接时的排查清单
-The driver does its best to connect to the Combo, and uses a couple of tricks to maximize reliability. Still, sometimes, connections aren't established. Here are some steps to take for trying to remedy this situation.
+驱动程序会竭尽全力连接Combo，并采用多种技巧来最大限度地提高可靠性。 尽管如此，有时仍无法建立连接。 以下是尝试解决此问题的步骤。
-1. Press a button on the Combo. Sometimes, the Combo's Bluetooth stack becomes non-responsive, and does not accept connections anymore. By pressing a button on the Combo and making the LCD show something, the Bluetooth stack is reset. Most of the time, this is the only step that's needed to fix the connection issues.
-2. Restart the phone. This may be needed if there is an issue with the phone's Bluetooth stack itself.
-3. If the Combo's battery cap is old, consider replacing it. Old battery caps can cause issues with the Combo's power supply, which affect Bluetooth.
-4. If connection attempts still keep failing, consider unpairing and then re-pairing the pump.
+1. 按下Combo上的任意按键。 有时Combo的蓝牙协议栈会停止响应，不再接受任何连接。 通过按下Combo按键使LCD屏幕显示内容，可重置蓝牙协议栈。 大多数情况下，仅需此步骤即可解决连接问题。
+2. 重启手机。 当手机蓝牙协议栈自身出现问题时可能需要此操作。
+3. 若Combo电池盖老旧，建议更换新部件。 老化的电池盖可能导致Combo供电异常，进而影响蓝牙功能。
+4. 若连接尝试持续失败，建议解除配对后重新配对胰岛素泵。
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Tips-for-Basic-usage.md b/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Tips-for-Basic-usage.md
index 71d647d173dc..bfa76cb7f25e 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Tips-for-Basic-usage.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Combo-Tips-for-Basic-usage.md
@@ -4,33 +4,33 @@ orphan: true
* * *
-# Accu-Chek Combo Tips for basic usage
+# Accu-Chek Combo基础使用技巧
-## How to ensure smooth operations
+## 如何确保操作顺畅
-* Always **carry the smartphone with you**, leave it next to your bed at night. As your pump may lay behind or under you body while you sleep, a higher position (on a shelf or board) works best.
-* Always make sure that the pump battery is as full as possible. See the battery section for tipps regarding the battery.
-* Whenever possible, only operate the pump via the AAPS app. To facilitate this, activate the key lock on the pump under **PUMP SETTINGS / KEY LOCK / ON**. Only when changing the battery or the cartridge, it is necessary to use the pump's keys.
+* 请始终**随身携带智能手机**，夜间将其置于床边。 由于睡眠时胰岛素泵可能被身体遮挡，置于较高位置（如架子或床头板）效果最佳。
+* 务必确保胰岛素泵电池始终保持充足电量。 电池使用技巧请参阅电池章节。
+* 尽可能仅通过AAPS应用程序操作胰岛素泵。为便于操作，请在泵上启用按键锁定功能：**泵设置/按键锁定/开启**。 仅当更换电池或储药器时，才需使用胰岛素泵的按键。
-## Pump not reachable. What to do?
+## 胰岛素泵不可连接。 怎么办？
-### Activate pump unreachable alarm
+### 启用胰岛素泵失联警报
-* In AAPS, go to **Settings / Local Alarms** and activate **alarm when pump is unreachable** and set **pump not reachable limit [Min]** to **31** minutes.
-* This will give you enough time to not trigger the alarm when leaving the room while your phone is left on the desk, but informs you if the pump cannot be reached for a time that exceeds the duration of a temporary basal rate.
+* 在AAPS中，进入**设置/本地警报**，启用**胰岛素泵失联警报**，并将**胰岛素泵失联时限[分钟]**设为**31**分钟。
+* 该设置可确保您离开房间时将手机留在桌上时不会触发警报，同时当胰岛素泵失联时间超过临时基础率持续时间时会及时提醒您。
-### Restore reachability of the pump
+### 恢复胰岛素泵的可连接状态
-* When AAPS reports a **pump unreachable** alarm, first release the keylock and **press any key on the pump** (e.g. "down" button). As soon as the pump display has turned off, press **Refresh** on the **Combo Tab** in AAPS. Mostly then the communication works again.
-* If that does not help, reboot your smartphone. After the restart, AAPS will be reactivated and a new connection will be established with the pump. If you are using the old driver, ruffy will be reactivated as well.
+* 当AAPS报告**胰岛素泵失联**警报时，请先解除按键锁定并**按下胰岛素泵任意按键**（如下行键）。 当胰岛素泵屏幕熄灭后，立即点击AAPS中**Combo标签页**的**刷新**按钮。 通常此时通信功能即可恢复。
+* 若上述方法无效，请重启智能手机。 重启后AAPS将自动重新激活，并与胰岛素泵建立新连接。 若使用旧版驱动程序，ruffy也将同步重新激活。
-* The tests with different smartphones have shown that certain smartphones trigger the "pump unreachable" error more often than others. See [AAPS Phones](#Phones-list-of-tested-phones) for successfully tested smartphones.
+* 多款智能手机测试表明，某些机型更易触发"胰岛素泵失联"错误。 经测试验证的智能手机型号请参阅[AAPS适用手机](#Phones-list-of-tested-phones)列表。
-### Root causes and consequences of frequent communication errors
+### 频繁通信错误的根本原因和后果
-* On phones with **low memory** (or **aggressive power-saving** settings), AAPS is often shut down. You can tell by the fact that the Bolus and Calculator buttons on the Home screen are not shown when opening AAPS because the system is initializing. This can trigger "pump unreachable alarms" at startup. In the **Last Connection** field of the Combo tab, you can check when AAPS last communicated with the pump.
+* 在**内存不足**或启用**激进省电**设置的手机上，AAPS常被强制关闭。 若打开AAPS时主屏幕未显示大剂量和计算器按钮（系统正在初始化），即可判定此情况。 这可能会在启动时触发“泵无法连接警报”。 在Combo标签页的**最后连接**字段中，可查看AAPS最近一次与胰岛素泵通信的时间。
@@ -38,68 +38,68 @@ orphan: true
-* This error can drain the pump's battery faster because the basal profile is read from the pump when the app is restarted.
-* It also increases the likelihood of causing the error that causes the pump to reject all incoming connections until a button on the pump is pressed.
+* 此错误会加速消耗胰岛素泵电量，因为应用重启时需要从泵中读取基础率配置文件。
+* 同时会增大泵机故障概率，导致必须手动按键才能恢复外部连接。
-## Cancellation of temporary basal rate fails
+## 临时基础率取消失败
-* Occasionally, AAPS can not automatically cancel a **TBR CANCELED** alert. Then you have to either press **UPDATE** in the AAPS **Combo tab** or the alarm on the pump will need to be confirmed.
+* 偶尔AAPS无法自动消除**临时基础率已取消**警报。 此时需点击AAPS**Combo标签页**的**更新**按钮，或在胰岛素泵上手动确认警报。
-## Pump battery considerations
+## 胰岛素泵电池注意事项
-### Changing the battery
+### 更换电池
-* After a **low battery** alarm, the battery should be changed as soon as possible to always have enough energy for a reliable Bluetooth communication with the smartphone, even if the phone is within a wider distance of the pump.
-* Even after a **low battery** alarm, the battery might be used for a significant amount of time. However, it is recommended to always have a fresh battery with you after a "low battery" alarm rang.
-* Before changing the battery, press on the **Loop** symbol on the main screen and select **Suspend loop for 1h**.
-* Wait for the pump to communicate with the pump and the bluetooth logo on the pump has faded.
+* 出现**低电量**警报后应立即更换电池，确保维持足够的电量进行可靠的蓝牙通信（即使手机与泵距离较远时）。
+* 即便出现**低电量**警报后，电池仍可持续使用较长时间。 但建议触发"低电量"警报后随身携带新电池备用。
+* 更换电池前，请点击主屏幕**循环**图标并选择**暂停循环1小时**。
+* 等待胰岛素泵完成通信且泵体蓝牙标识熄灭。
-* Release the key lock on the pump, put the pump into stop mode, confirm a possibly canceled temporary basal rate, and change the battery quickly.
-* When using the old driver, if the clock on the pump did not survive the battery change, re-set the date and time on the pump to exactly the date/time on your phone running AAPS. (The new driver automatically updates the pump's date and time.)
-* Then put the pump back in run mode select **Resume** when pressing on the **Suspended Loop** icon on the main screen.
-* AAPS will re-set a necessary temporary basal rate with the arrival of the next blood sugar value.
+* 解除泵体按键锁，切换至停止模式，确认可能已取消的临时基础率，并快速更换电池。
+* 使用旧版驱动时，若更换电池导致泵体时钟失效，请将泵体日期时间精确设置为运行AAPS的手机当前时间。 （新版驱动程序会自动更新胰岛素泵的日期时间。）
+* 将泵体切换回运行模式后，点击主屏幕**暂停循环**图标选择**恢复**。
+* AAPS将在获取下一个血糖值时重新设置所需的临时基础率。
(Accu-Chek-Combo-Tips-for-Basic-usage-battery-type-and-causes-of-short-battery-life)=
-### Battery type and causes of short battery life
+### 电池类型与寿命缩短原因
-* As intensive Bluetooth communication consumes a lot of energy, only use **high-quality batteries** like Energizer Ultimate Lithium, the "power one"s from the "large" Accu-Chek service pack, or if you are going for a rechargeable battery, use Eneloop batteries.
+* 由于高强度蓝牙通信耗电量大，请仅使用**高品质电池**，如劲量终极锂电池、Accu-Chek大容量服务包中的"power one"电池，若选择充电电池则推荐使用爱乐普。
 
-Ranges for typical life time of the different battery types are as follows:
+各类电池典型使用寿命范围如下：
-* **Energizer Ultimate Lithium**: 4 to 7 weeks
-* **Power One Alkaline** (Varta) from the service pack: 2 to 4 weeks
-* **Eneloop rechargeable** batteries (BK-3MCCE): 1 to 3 weeks
+* **Energizer Ultimate Lithium**：4 到 7 周
+* 服务包中的 **Power One Alkaline** (Varta)：2 到 4 周
+* **Eneloop 可充电电池** (BK-3MCCE)：1 到 3 周
-If your battery life is significantly shorter than the ranges given above, please check the following possible causes:
+若电池寿命显著短于上述范围，请排查以下可能原因：
-* There are some variants of the screw-on battery cap of the Combo pump, which partially short circuit the batteries and drain them quickly. The caps without this problem can be recognized by the golden metal contacts.
-* If the pump clock does not "survive" a short battery change, it is likely that the capacitor is broken which keeps the clock running during a brief power outage. In this case, a replacement of the pump by Roche might help, which is not a problem during the warranty period.
-* The smart phone hardware and software (Android operating system and bluetooth stack) also impact the battery lifetime of the pump, even though the exact factors are not completely known yet. If you have the opportunity, try another smartphone and compare battery lifetimes.
+* 部分Combo泵的旋入式电池盖存在设计缺陷，可能导致电池短路并加速耗电。 无此缺陷的电池盖可通过金色金属触点识别。
+* 若短暂更换电池导致泵体时钟失效，可能是维持时钟运行的电容元件损坏。 此时可联系罗氏更换泵体（保修期内可免费处理）。
+* 智能手机硬件及软件（安卓操作系统与蓝牙协议栈）同样影响泵体电池寿命，具体作用机制尚未完全明确。 如有条件，可尝试更换其他智能手机对比电池续航表现。
-## Extended bolus, multiwave bolus
+## 扩展大剂量，多波大剂量
-The OpenAPS algorithm does not support a parallel extended bolus or multiwave bolus. But a similar treatment can be achieved by the following alternatives:
+OpenAPS算法不支持并行执行扩展大剂量或多波大剂量。 但可通过以下替代方案实现类似治疗效果：
-* Use **e-Carbs** when entering carbs or using the Calculator by entering the carbs of the full meal and the duration you expect the carbs to arrive as glucose in you blood. The system will then calculate small carbs equally distributed over the whole duration which will cause th algorithm to provide equivalent insulin dosing while still permanently checking the overall rise/decrease of the blood glucose level. For a multiwave bolus approach, you can also combine a smaller immediate bolus with e-carbs.
-* Before eating, on the **Actions tab** in AAPS set as a temporary **Eating Soon** goal with target glucose 80 for several hours. The duration should be based on the interval you would choose for an extended bolus. This will keep your target lower than usual and therefore increase the amount of insulin delivered.
-* Then use the **CALCULATOR** to enter the full carbs of the meal, but do not directly apply the values suggested by the bolus calculator. If a multiwave-like bolus is to be delivered, correct the insulin dosage down. Depending on the meal, the algorithm now has to deliver additional SMBs or higher temporary basal rates to counteract the increase in blood sugar. Here, the safety limitation of the basal rate (Max IE / h, Maximum basal IOB) should be very carefully experimented with and, if necessary, temporarily changed.
+* 输入碳水化合物时使用**电子碳水**功能，或在计算器中输入完整餐食的碳水化合物总量及预估的血糖吸收时长。 系统将自动计算该时段内均匀分布的小剂量碳水化合物，使算法在持续监测血糖升降趋势的同时提供等效的胰岛素剂量。 实现多波大剂量效果时，可将小剂量即时大剂量与电子碳水功能结合使用。
+* 进食前，在AAPS**操作标签页**设置临时**即将进食**目标，将目标血糖值设为80并持续数小时。 持续时间应根据您通常选择的扩展大剂量间隔设定。 该设置将使目标血糖值低于常规水平，从而增加胰岛素输注量。
+* 随后使用**计算器**输入完整餐食碳水化合物量，但不要直接采用大剂量计算器建议的数值。 若需执行类多波大剂量，应向下调整胰岛素剂量。 根据餐食情况，算法将通过追加超微大剂量或提高临时基础率来抵消血糖上升。 此时需谨慎测试基础率安全限制（最大单位/小时、基础胰岛素最大存量），必要时可临时调整。
-* If you are tempted to just use the extended or multiwave bolus directly on the pump, AAPS will penalize you with disabling the closed loop for the next six hours to ensure that no excess insulin dosage is calculated.
+* 若直接通过泵体执行扩展/多波大剂量，AAPS将禁用闭环6小时作为惩罚机制，以避免过量胰岛素计算。
-## Alarms at bolus delivery
+## 大剂量输注警报
-* If AAPS detects that an identical bolus has been successfully delivered at the same minute, bolus delivery will be prevented with identical number of insulin units. If your really want to bolus the same insulin twice in short succession, just wait two more minutes and then deliver the bolus again. If the fist bolus has been interrupted or was not delivered for other reasons, you can immediately re-submit the bolus since AAPS 2.0.
-* The alarm is a safety mechanism that reads the pump's bolus history before submitting a new bolus to correctly calculate insulin on board (IOB), even when a bolus is delivered directly from the pump. Here indistinguishable entries must be prevented.
+* 若AAPS检测到相同剂量的大剂量已在同一分钟成功输注，系统将阻止重复输注相同单位的胰岛素。 如需在短时间内重复输注相同剂量胰岛素，请等待两分钟后再次执行大剂量操作。 自AAPS 2.0版本起，若首次大剂量输注中断或未完成，可立即重新提交输注请求。
+* 该警报是安全机制，会在提交新大剂量前读取泵体输注记录，确保胰岛素存量（IOB）计算准确（即使大剂量直接从泵体输注）。 必须防止出现无法区分的记录条目。
-* This mechanism is also responsible for a second cause of the error: If during the use of the bolus calculator another bolus is delivered via the pump and thereby the bolus history changes, the basis of the bolus calculation is wrong and the bolus is aborted.
+* 该机制也是导致报错的另一原因：若使用大剂量计算器期间，另一大剂量通过泵体输注导致记录变更，计算基准失效将中止当前大剂量。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Insight-Pump.md b/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Insight-Pump.md
index 3fb41ee9c2cb..87c5868d36aa 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Insight-Pump.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/Accu-Chek-Insight-Pump.md
@@ -4,156 +4,156 @@ orphan: true
* * *
-# Accu-Chek Insight Pump
+# Accu-Chek Insight 泵
-**This software is part of a DIY artificial pancreas solution and is not a product, but requires YOU to read, learn and understand the system including how to use it. It is not something that does all your diabetes management for you but allows you to improve your diabetes and your quality of life, if you're willing to put in the time required. Don't rush into it, but allow yourself time to learn. You alone are responsible for what you do with it.**
+**本软件属于人工胰腺DIY解决方案组件，并非商业产品，需用户自行研习系统原理及操作方法。 本工具无法替代糖尿病自主管理，但若愿投入必要时间研习，可助您改善病情并提升生活质量。 请勿操之过急，预留充足时间循序渐进学习。 使用后果需自行承担全部责任。**
* * *
-## ***WARNING:** If you have been using the Insight with **SightRemote** in the past, please **update to the newest AAPS version** and **uninstall SightRemote**.*
+## ***警告：**若曾搭配**SightRemote**使用Insight，请**升级至最新版AAPS**并**卸载SightRemote**。*
-## Hardware and software requirements
+## 硬件和软件要求
-* A Roche Accu-Chek Insight pump (any firmware, they all work)
+* 罗氏Accu-Chek Insight泵（任意固件版本均兼容）
-Note: AAPS will write data always in **first basal rate profile in the pump**.
+注：AAPS始终将数据写入**泵中首个基础率配置文件**。
-* An Android phone (Basically every Android version would work with Insight, but check on the [Module](../Getting-Started/ComponentOverview) page which Android version is required to run AAPS.)
-* The AAPS app installed on your phone
+* 安卓手机（原则上所有安卓版本均可兼容Insight，但需查阅[模块](../Getting-Started/ComponentOverview)页面确认运行AAPS所需的安卓版本）
+* 手机端安装的AAPS应用程序
## 设置
-* The Insight pump should only be connected to one device at a time. If you have previously used the Insight remote control (meter), you must remove the meter from the paired devices list of your pump: Menu > Settings > Communication > Remove device
+* Insight泵每次仅限连接一台设备。 若曾使用Insight遥控器（血糖仪），需从泵体配对设备列表中删除该设备：菜单 > 设置 > 通信 > 移除设备
-* In [Config builder > Pump](../SettingUpAaps/ConfigBuilder.md), select Accu-Chek Insight.
+* 在[配置构建器 > 泵](../SettingUpAaps/ConfigBuilder.md)中选择Accu-Chek Insight。
-* Tap the cog-wheel to open Insight settings.
+* 点击齿轮图标进入Insight设置界面。
-* In settings, tap on the button 'Insight pairing' at the top of the screen. You should see a list of all nearby bluetooth devices (below left).
-* On the Insight pump, go to Menu > Settings > Communication > Add Device. The pump will display the following screen (below right) showing the serial number of the pump.
+* 在设置界面，点击屏幕顶部的"Insight配对"按钮。 系统将显示附近所有蓝牙设备列表（左下图）。
+* 在Insight泵上操作：菜单 > 设置 > 通信 > 添加设备。 泵体将显示含序列号的界面（右下图）。
-* Going back to your phone, tap on the pump serial number in the list of bluetooth devices. Then tap on Pair to confirm.
+* 返回手机端，在蓝牙设备列表中点击泵体序列号。 点击"配对"进行确认。
-* Both the pump and phone will then display a code. Check that the codes are the same on both devices and confirm on both the pump and the phone.
+* 泵体与手机将同步显示配对验证码。 核验两端验证码一致性后，在泵体与手机端同步确认。
-* 成功! Pat yourself on the back for successfully pairing your pump with AAPS.
+* 成功! 恭喜您已完成泵体与AAPS的配对操作。
-* To check all is well, go back to Config builder in AAPS and tap on the cog-wheel by the Insight Pump to get into Insight settings, then tap on Insight Pairing and you will see some information about the pump:
+* 返回AAPS配置构建器，点击Insight泵旁的齿轮图标进入设置界面，选择"Insight配对"即可查看泵体信息：
-Note: There will be no permanent connection between pump and phone. A connection will only be established if necessary (i.e. setting temporary basal rate, giving bolus, reading pump history...). Otherwise battery of phone and pump would drain way too fast.
+注：泵体与手机之间不会保持常时连接。 仅在必要时建立连接（如设置临时基础率、执行大剂量输注、读取泵体记录等操作）。 否则将导致手机与泵体电量过快耗尽。
(Accu-Chek-Insight-Pump-settings-in-aaps)=
-## Settings in AAPS
+## AAPS 中的设置
-**Note : It is now possible (only with AAPS v2.7.0 and above) to use ‘Always use basal absolute values’ if you want to use Autotune with Insight pump, even if 'sync is enabled' with Nightscout.** (In AAPS go to [Preferences > NSClient > Advanced Settings](#Preferences-advanced-settings-nsclient)).
+**注：现可通过AAPS v2.7.0及以上版本使用"始终采用基础率绝对值"功能（即使Nightscout同步已启用），以配合Insight泵实现Autotune。**（路径：AAPS [偏好设置 > NS客户端 > 高级设置](#Preferences-advanced-settings-nsclient)）
-
+
-In the Insight settings in AAPS you can enable the following options:
+在AAPS的Insight设置中可启用以下选项：
-* "Log reservoir changes": This will automatically record an insulin cartridge change when you run the "fill cannula" program on the pump.
+* "记录储药器更换"：执行泵体"填充套管"程序时将自动记录胰岛素盒更换操作。
-* "Log tube changes": This adds a note to the AAPS database when you run the "tube filling" program on the pump.
+* "记录导管更换"：执行泵体"导管填充"程序时将在AAPS数据库添加备注。
-* "Log site change": This adds a note to the AAPS database when you run the "cannula filling" program on the pump. **Note: A site change also resets Autosens.**
+* "记录输注部位更换"：执行泵体"套管填充"程序时将在AAPS数据库添加备注。 **注：输注部位更换将重置自动灵敏度检测。**
-* "Log battery changes": This records a battery change when you put a new battery in the pump.
+* "记录电池更换"：泵体装入新电池时将生成更换记录。
-* "Log operating mode changes": This inserts a note in the AAPS database whenever you start, stop or pause the pump.
+* "记录运行模式变更"：启动/停止/暂停泵体操作时均在AAPS数据库插入备注。
-* "Log alerts": This records a note in the AAPS database whenever the pump issues an alert (except reminders, bolus and TBR cancellation - those are not recorded).
+* "记录警报"：泵体触发警报时在AAPS数据库生成记录（提醒、大剂量及临时基础率取消除外）。
-* "Enable TBR emulation": The Insight pump can only issue temporary basal rates (TBRs) up to 250%. To get round this restriction, TBR emulation will instruct the pump to deliver an extended bolus for the extra insulin if you request a TBR of more than 250%.
+* "启用临时基础率模拟"：Insight泵仅支持最高250%的临时基础率设定。 突破该限制时，若临时基础率超过250%，模拟功能将通过延长大剂量输注补充超额胰岛素。
- **Note: Just use one extended bolus at a time as multiple extended boluses at the same time might cause errors.**
+ **注：请勿同时执行多个延长大剂量输注，以免引发系统错误。**
-* "Disable vibrations on manual bolus delivery": This disables the Insight pump's vibrations when delivering a manual bolus (or extended bolus). This setting is available only with the latest version of Insight firmware (3.x).
+* "禁用手动大剂量震动提示"：执行手动大剂量（或延长大剂量）输注时关闭泵体震动反馈。 该功能仅支持最新版Insight固件（3.x及以上版本）。
-* "Disable vibrations on automated bolus delivery": This disables the Insight pump's vibrations when delivering an automatic bolus (SMB or Temp basal with TBR emulation). This setting is available only with the latest version of Insight firmware (3.x).
+* "禁用自动大剂量震动提示"：执行自动大剂量（超微大剂量或临时基础率模拟）输注时关闭泵体震动反馈。 该功能仅支持最新版Insight固件（3.x及以上版本）。
-* "Recovery duration": This defines how long AAPS will wait before trying again after a failed connection attempt. You can choose from 0 to 20 seconds. If you experience connection problems, choose a longer wait time.
+* "恢复间隔"：定义连接失败后AAPS的重试等待时长。 可设置0至20秒的间隔时间。 若存在连接故障，建议延长该间隔时间。
- Example for min. recovery duration = 5 and max. recovery duration = 20
+ 最短恢复间隔示例： 恢复间隔最小值=5 最大恢复间隔=20
- no connection -> wait **5** sec.
- retry -> no connection -> wait **6** sec.
- retry -> no connection -> wait **7** sec.
- retry -> no connection -> wait **8** sec.
+ 连接失败 -> 等待**5**秒
+ 重试 -> 连接失败 -> 等待**6**秒
+ 重试 -> 连接失败 -> 等待**7**秒
+ 重试 -> 连接失败 -> 等待**8**秒
...
- retry -> no connection -> wait **20** sec.
- retry -> no connection -> wait **20** sec.
+ 重试 -> 连接失败 -> 等待**20**秒
+ 重试 -> 连接失败 -> 等待**20**秒
...
-* "Disconnect delay": This defines how long (in seconds) AAPS will wait to disconnect from the pump after an operation is finished. Default value is 5 seconds.
+* "断开延迟"：定义操作完成后AAPS与泵体保持连接的时长（秒）。 默认值为5秒。
-For periods when pump was stopped AAPS will log a temp. basal rate with 0%.
+泵体停用期间，AAPS将记录临时基础率为0%。 基础率为0%。
-In AAPS, the Accu-Chek Insight tab shows the current status of the pump and has two buttons:
+在AAPS中，Accu-Chek Insight标签页显示泵体当前状态，并提供两个按钮：
-* "Refresh": Refreshes pump status
-* "Enable/Disable TBR over notification": A standard Insight pump emits an alarm when a TBR is finished. This button lets you enable or disable this alarm without the need for configuration software.
+* "刷新"：更新泵体状态
+* "启用/禁用临时基础率结束通知"：标准Insight泵在临时基础率结束时触发警报。 该按钮可直接启用/禁用警报功能，无需配置软件。
-## Settings in the pump
+## 泵体参数设置
-Configure alarms in the pump as follows:
+按以下方式配置泵体警报：
-* Menu > Settings > Device settings > Mode settings > Quiet > Signal > Sound
-* Menu > Settings > Device settings > Mode settings > Quiet > Volume > 0 (remove all bars)
-* Menu > Modes > Signal mode > Quiet
+* 菜单 > 设置 > 设备设置 > 模式设置 > 静音 > 信号 > 声音
+* 菜单 > 设置 > 设备设置 > 模式设置 > 静音 > 音量 > 0（删除所有条）
+* 菜单 > 模式 > 信号模式 > 静音
-This will silence all alarms from the pump, allowing AAPS to decide if an alarm is relevant to you. If AAPS does not acknowledge an alarm, its volume will increase (first beep, then vibration).
+该设置将静默所有泵体警报，由AAPS判定警报相关性。 若AAPS未确认警报，泵体将逐级提升提示强度（先鸣响后震动）。
(Accu-Chek-Insight-Pump-vibration)=
-### Vibration
+### 振动
-Depending on the firmware version of your pump, the Insight will vibrate briefly every time a bolus is delivered (for example, when AAPS issues an SMB or TBR emulation delivers an extended bolus).
+根据泵体固件版本差异，Insight可能在每次大剂量输注时短暂震动（如AAPS执行超微大剂量或临时基础率模拟触发延长大剂量时）。
-* Firmware 1.x: No vibration by design.
-* Firmware 2.x: Vibration cannot be disabled.
-* Firmware 3.x: AAPS delivers bolus silently. (minimum [version 2.6.1.4](#Releasenotes-version-2-6-1-4))
+* 固件 1.x：设计上没有振动。
+* 固件 2.x：无法禁用振动。
+* 固件3.x版本：AAPS执行静默大剂量输注。 （最低[版本2.6.1.4](#Releasenotes-version-2-6-1-4)）
-Firmware version can be found in the menu.
+固件版本信息可通过菜单查询。
-## Battery replacement
+## 更换电池
-Battery life for Insight when looping range from 10 to 14 days, max. 20 days. The user reporting this is using Energizer lithium batteries.
+闭环模式下Insight电池续航为10至14天，最长为 20 天。 该数据由使用劲量锂电池的用户提供。
-The Insight pump has a small internal battery to keep essential functions like the clock running while you are changing the removable battery. If changing the battery takes too long, this internal battery may run out of power, the clock will reset, and you will be asked to enter a new time and date after inserting a new battery. If this happens, all entries in AAPS prior to the battery change will no longer be included in calculations as the correct time cannot be identified properly.
+Insight泵体内置微型电池，可在更换可拆卸电池时维持时钟等核心功能运行。 若更换电池耗时过长导致内置电池耗尽，时钟将重置，插入新电池后需重新输入时间日期。 若发生此情况，因时间戳无法正确识别，电池更换前所有AAPS记录将不再参与计算。
(Accu-Chek-Insight-Pump-insight-specific-errors)=
-## Insight specific errors
+## Insight专属错误代码
### 扩展大剂量(方波)
-Just use one extended bolus at a time as multiple extended boluses at the same time might cause errors.
+请勿同时设置多个延长大剂量，单次仅允许一个延长大剂量运行，否则可能引发错误。
-### Time out
+### 超时
-Sometimes it might happen that the Insight pump does not answer during connection setup. In this case AAPS will display the following message: "Timeout during handshake - reset bluetooth".
+偶发情况下，Insight泵可能在建立连接时无响应。 此时AAPS将显示："握手超时 - 重置蓝牙"。
-In this case turn off bluetooth on pump AND smartphone for about 10 seconds and then turn it back on.
+遇到此情况，请同时关闭泵体与智能手机的蓝牙功能约10秒后重新启用。
-## Crossing time zones with Insight pump
+## 携带Insight泵跨时区注意事项
-For information on traveling across time zones see section [Timezone traveling with pumps](#timezone-traveling-insight).
\ No newline at end of file
+跨时区操作指南请参阅[泵体时区切换](#timezone-traveling-insight)章节。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/DanaR-Insulin-Pump.md b/docs/CROWDIN/zh_CN/CompatiblePumps/DanaR-Insulin-Pump.md
index baab20e53f80..8e8a2cd9dd10 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/DanaR-Insulin-Pump.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/DanaR-Insulin-Pump.md
@@ -4,29 +4,29 @@ orphan: true
* * *
-# DanaR Pump
+# DanaR 泵
-*These instructions are for configuring the app and your pump if you have a DanaR. Visit [DanaRS Insulin Pump](./DanaRS-Insulin-Pump.md) if you have the DanaRS launched in 2017 instead.*
+*本指南适用于DanaR泵体的应用程序配置操作。 若使用2017年发布的DanaRS泵体，请参阅[DanaRS胰岛素泵](./DanaRS-Insulin-Pump.md)章节。*
-* In the pump go to Main Menu > Setting > User Option
-* Turn on "8. 扩展大剂量"
+* 在泵体操作界面进入：主菜单 > 设置 > 用户选项
+* 开启“8. 扩展大剂量"
-
+
-* Go to Main Menu > Setting > Discovery
-* In phone settings go to Bluetooth, scan for nearby devices, select your DanaR serial number and input your password (Pairing password is 0000). If DanaR is not showing in scan then restart phone and take DanaR battery out, replace and start these two steps again.
+* 转到主菜单 > 设置 > 发现
+* 手机端进入蓝牙设置，扫描周边设备后选择DanaR序列号，输入配对密码（默认密码0000）。 若扫描未发现DanaR设备，请重启手机并取出DanaR电池后重新执行上述步骤。
-* In AAPS go to Config Builder and select the type of DanaR you have (DanaR, DanaR Korean, DanaRv2)
+* 在AAPS配置生成器中，选择您使用的DanaR型号（DanaR/DanaR韩版/DanaRv2）。
-* Select Menu by tapping the 3 dots in the top right. Select Preferences.
-* Select DanaR Bluetooth device, and click your DanaR serial number.
-* Select Pump password, and input your password. (Default password is 1234)
-* If you want AAPS to allow basal rate above 200%, enable Use extended boluses for >200%. Note this means you cannot loop with high TBRs whilst using extended boluses for food.
-* In Preferences under DanaR pump settings you can change the default bolus speed used (12sec per 1u, 30sec per 1u or 60sec per 1u).
-* Set basal step on pump to 0.01 U/h
-* Set bolus step on pump to 0.1 U/h
+* 点击右上角三点图标选择菜单。 选择首选项。
+* 选择DanaR蓝牙设备，点击您的DanaR序列号。
+* 选择泵体密码选项，输入您的密码。 (默认密码为 1234）
+* 如需允许AAPS设置超过200%的基础率，请启用"使用延长大剂量实现>200%"功能。 请注意：启用该功能后，进食期间使用延长大剂量时将无法同步执行高临时基础率闭环。
+* 在DanaR泵体设置的偏好选项中，可修改默认大剂量输注速度（12秒/单位、30秒/单位或60秒/单位）。
+* 将泵体基础率步进值设为0.01单位/小时。
+* 将泵体大剂量步进值设为0.1单位/小时。
* 在泵上启用扩展大剂量
-## Timezone traveling with Dana R pump
+## Dana R泵跨时区操作指南
-For information on traveling across time zones see section [Timezone traveling with pumps](#timezone-traveling-danarv2-danars).
\ No newline at end of file
+跨时区操作说明请参阅[泵体时区切换](#timezone-traveling-danarv2-danars)章节。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/DanaRS-Insulin-Pump.md b/docs/CROWDIN/zh_CN/CompatiblePumps/DanaRS-Insulin-Pump.md
index f6ea1650c5e5..75896ba4172d 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/DanaRS-Insulin-Pump.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/DanaRS-Insulin-Pump.md
@@ -4,135 +4,135 @@ orphan: true
* * *
-# DanaRS and Dana-i Pump
+# DanaRS 和 Dana-i 泵
-*These instructions are for configuring the app and your pump if you have a DanaRS from 2017 onwards or the newer Dana-i. Visit [DanaR Insulin Pump](./DanaR-Insulin-Pump.md) if you have the original DanaR instead.*
+*本指南适用于2017年起发布的DanaRS及新款Dana-i泵体的应用程序配置。 若使用初代DanaR泵体，请参阅[DanaR胰岛素泵](./DanaR-Insulin-Pump.md)章节。*
-**New Dana RS firmware v3 can be used from AAPS version 2.7 onwards.**
+**AAPS 2.7及以上版本支持新版Dana RS固件v3。**
-**New Dana-i can be used from AAPS version 3.0 onwards.**
+**AAPS 3.0及以上版本支持Dana-i泵体。**
-* In DanaRS/i pump "BASAL A" is used by the app. Existing data gets overwritten.
+* DanaRS/i泵体中"基础率A"通道已被应用程序占用，原有数据将被覆盖。
(DanaRS-Insulin-Pump-pairing-pump)=
-## Pairing pump
+## 配对泵
-* On AAPS homescreen click hamburger menu on the top left corner and go to Config Builder.
-* In pump section select 'Dana-i/RS'.
-* Click on gear wheel to get directly to the pump settings or return to homescreen.
+* 在AAPS主界面点击左上角三横菜单，进入配置生成器。
+* 在泵体选项中选择'Dana-i/RS'。
+* 点击齿轮图标可直接进入泵体设置，或返回主界面。
-* Go to 'DANA-i/RS' tab.
+* 进入'DANA-i/RS'标签页。
-* Select preferences menu by tapping the 3 dots in the top right.
-* Select 'Dana-i/RS Preferences'.
-* Click on "Selected pump".
-* In the pairing window click on the entry for your pump.
+* 点击右上角三点图标选择偏好菜单。
+* 选择'Dana-i/RS偏好设置'。
+* 单击“选择的泵”。
+* 在配对窗口点击您的泵体条目。
-* **You have to confirm the pairing on the pump!** That's just the way you are used to from other bluetooth pairings (i.e. smartphone and car audio).
+* **需在泵体端确认配对！** 此操作与常规蓝牙配对流程一致（如手机与车载音响配对）。
-* Follow the pairing process based on the type and firmware of your pump:
+* 根据泵体型号及固件版本执行配对流程：
- * For DanaRS v1 select pump password in preferences and set your password.
- * For DanaRS v3 you have to type 2 sequences of numbers and letters displayed on pump to AAPS pairing dialog.
- * For Dana-i standard Android pairing dialog appear and you have to enter 6-digit number displayed on pump.
+ * DanaRS v1用户需在偏好设置中选择泵体密码并设置密码。
+ * DanaRS v3用户需将泵体显示的两组数字字母组合输入AAPS配对对话框。
+ * Dana-i用户需在标准Android配对对话框中输入泵体显示的6位数字。
-* Select Bolus Speed to change the default bolus speed used (12sec per 1u, 30sec per 1u or 60sec per 1u).
+* 选择大剂量输注速度可修改默认值（12秒/单位、30秒/单位或60秒/单位）。
-* Set basal step on pump to 0.01 U/h using Doctors menu (see pump user guide).
-* Set bolus step on pump to 0.05 U/h using Doctors menu (see pump user guide).
+* 通过医生菜单将泵体基础率步进值设为0.01单位/小时（详见泵体使用手册）。
+* 通过医生菜单将泵体大剂量步进值设为0.05单位/小时（详见泵体使用手册）。
* 在泵上启用扩展大剂量
(DanaRS-Insulin-Pump-default-password)=
-### Default password
+### 默认密码
-* For DanaRS with firmware v1 and v2 the default password is 1234.
-* For DanaRS with firmware v3 or Dana-i the default password is derived from the manufacturing date and calculates as MMDD where MM is the month and DD is the day, the pump was produced (i.e. '0124' representing month 01 and day 24).
+* DanaRS固件v1/v2的默认密码为1234。
+* DanaRS固件v3及Dana-i的默认密码采用生产日期MMDD格式（例如'0124'表示1月24日生产）。
- * From MAIN MENU select REVIEW then open SHIPPING INFORMATION from the sub menu
- * Number 3 is manifacturing date.
- * For v3/i this password is used only for locking menu on pump. It's not used for communication and it's not necessary to enter it in AAPS.
+ * 从主菜单选择查看功能，然后打开子菜单中的运输信息
+ * 第三项为生产日期。
+ * v3/i版本中该密码仅用于锁定泵体菜单。 该密码不用于通信交互，也无需在AAPS中输入。
(DanaRS-Insulin-Pump-change-password-on-pump)=
-## Change password on pump
+## 修改泵体密码
-* Press OK button on pump
-* In main menu select "OPTION" (move right by pressing arrow button several times)
+* 按下泵上的确定按钮
+* 在主菜单中选择"选项"（多次按右箭头键切换）
-* In options menu select "USER OPTION"
+* 在选项菜单中选择"用户设置"
-* Use arrow button to scroll down to "11. password"
+* 使用箭头按钮向下滚动到“11. 密码”
-* Press OK to enter old password.
+* 按确定输入旧密码。
-* Enter **old password** (Default password see [above](#default-password)) and press OK
+* 输入<0>旧密码（默认密码见<1>上），然后按确定
-* If wrong password is entered here there will be no message indicating failure!
+* 此处输入错误密码时系统不会提示失败信息！
-* Set **new password** (Change numbers with + & - buttons / Move right with arrow button).
+* 设置**新密码**（用加减键修改数字/按右箭头键切换）。
-* Confirm with OK button.
+* 按 "确定 "按钮确认。
-* Press OK to save setting.
+* 按 OK 保存设置。
-* Move down to "14. EXIT" and press OK to exit.
+* 向下移动到 "14. EXIT"（退出），然后按确定退出。
(DanaRS-Insulin-Pump-dana-rs-specific-errors)=
-## Dana RS specific errors
+## Dana RS 特定错误
-### Error during insulin delivery
+### 胰岛素输送过程中的错误
-In case the connection between AAPS and Dana RS is lost during bolus insulin delivery (i.e. you walk away from phone while Dana RS is pumping insulin) you will see the following message and hear an alarm sound.
+若AAPS与Dana RS在大剂量胰岛素输注期间断开连接（例如泵体输注时远离手机），将显示以下提示信息并触发警报音。
-* In most cases this is just a communication issue and the correct amount of insulin is delivered.
-* Check in pump history (either on the pump or through Dana tab > pump history > boluses) if correct bolus is given.
-* Delete error entry in [treatments tab](#screens-bolus-carbs) if you wish.
-* Real amount is read and recorded on next connect. To force this press BT icon on dana tab or just wait for next connect.
+* 多数情况下仅为通信故障，实际胰岛素输注剂量仍准确。
+* 请通过泵体历史记录（直接在泵体操作或通过Dana标签页>泵体历史>大剂量记录）核查实际输注剂量是否正确。
+* 如需可删除[治疗记录](#screens-bolus-carbs)中的错误条目。
+* 实际剂量将在下次连接时读取并记录。 强制读取可点击Dana标签页的蓝牙图标，或等待下次自动连接。
-## Special note when switching phone
+## 手机更换特别注意事项
-When switching to a new phone the following steps are necessary:
+更换新手机时必须执行以下步骤：
-* [Export settings](../Maintenance/ExportImportSettings.md) on your old phone
-* Transfer settings from old to new phone
+* 在旧手机[导出设置](../Maintenance/ExportImportSettings.md)
+* 将设置从旧手机转移到新手机
### DanaRS v1
-* **Manually pair** Dana RS with the new phone
-* As pump connection settings are also imported AAPS on your new phone will already "know" the pump and therefore not start a bluetooth scan. Therefore new phone and pump must be paired manually.
-* Install AAPS on the new phone.
-* [Import settings](../Maintenance/ExportImportSettings.md) on your new phone
+* **手动配对**Dana RS与新手机
+* 由于泵体连接设置已导入，新手机上的AAPS将自动"识别"泵体，故不会启动蓝牙扫描。 因此必须手动完成新手机与泵体的配对。
+* 在新手机上安装AAPS。
+* 在新手机上[导入设置](../Maintenance/ExportImportSettings.md)
### DanaRS v3, Dana-i
-* Start pairing procedure as described [above](#pairing-pump).
-* Sometimes it may be necessary to clear pairing information in AAPS by long-click BT icon on Dana-i/RS tab.
+* 按[上文](#pairing-pump)所述步骤启动配对程序。
+* 有时需长按Dana-i/RS标签页的蓝牙图标清除AAPS中的配对信息。
-## Timezone traveling with Dana RS pump
+## 使用Dana RS泵进行跨时区旅行
-For information on traveling across time zones see section [Timezone traveling with pumps](#timezone-traveling-danarv2-danars).
\ No newline at end of file
+跨时区操作说明请参阅[泵体时区切换](#timezone-traveling-danarv2-danars)章节。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/DiaconnG8.md b/docs/CROWDIN/zh_CN/CompatiblePumps/DiaconnG8.md
index bc512f6db641..6090b7547c4e 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/DiaconnG8.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/DiaconnG8.md
@@ -2,94 +2,94 @@
orphan: true
- - -
-# Diaconn G8 Insulin Pump
+# Diaconn G8 胰岛素泵
-## Insulin Pump Bluetooth Pairing
+## 胰岛素泵蓝牙配对
-- Click on the hamburger menu in the top left corner.
+- 点击左上角的汉堡菜单。
-- Click on Config Builder.
+- 点击 Config Builder。
-- After selecting the Diaconn G8 Pump click on the Settings icon (cog wheel).
+- 选择 Diaconn G8 泵后，点击设置图标（齿轮）。
-- Choose Selected pump.
+- 选择 Selected pump（选择的泵）。
-- Select your insulin pump’s model number once it appears in the list.
+- 在列表中出现您的胰岛素泵型号后，选择它。
-- There are two options to check your model number:
+- 有两种方法可以检查您的型号：
-1. The last 5 digits of the SN number on the back of the pump.
-2. Click on O button > Information > BLE > Last 5 digits.
+1. 泵背面 SN 码的最后 5 位数字。
+2. 点击 O 按钮 \> Information（信息）> BLE > 最后 5 位数字。
-- Once you select your pump, a window appears asking for a pin code. Enter the pin number displayed on your pump to complete the connection.
+- 选择您的泵后，会出现一个窗口，要求输入密码。 输入泵上显示的密码以完成连接。
-## Pump status check and log synchronization
+## 泵状态检查和日志同步
-- Once your pump is connected, click on the Bluetooth symbol to check the status and to synchronize logs.
+- 泵连接后，点击蓝牙符号以检查状态并同步日志。
-## Bluetooth Troubleshooting
+## 蓝牙故障排除
-**What to do in the case of an unstable Bluetooth connection with the pump.**
+**当与泵的蓝牙连接不稳定时，该怎么办。**
-### Method 1 ) Check the pump again after AAPS application is completed.
+### 方法 1) 在 AAPS 应用程序完成后再次检查泵。
-- Click on the 3 dots button on the top right.
+- 点击右上角的 3 个点按钮。
-- Click on Exit.
+- 点击 Exit（退出）。
-### Method 2) If the first method doesn’t work, disconnect Bluetooth and then reconnect.
+### 方法 2) 如果第一种方法不起作用，断开蓝牙连接，然后重新连接。
-- Press and hold the Bluetooth button at the top for about 3 seconds.
+- 按住顶部的蓝牙按钮约 3 秒钟。
-- Click on the Setting button on the paired Diaconn G8 Insulin pump.
+- 点击已配对的 Diaconn G8 胰岛素泵上的 Setting（设置）按钮。
-- Unpair.
+- 取消配对。
-- Repeat the Bluetooth pairing process for the pump (see above).
+- 重复泵的蓝牙配对过程（见上文）。
-## Further Information
+## 更多信息
-### Diaconn G8 Insulin pump option setting
+### Diaconn G8 胰岛素泵选项设置
-- Config manager > pump > Diaconn G8 > Settings
-- DIACONN G8 at the top> 3 dots button on the top right > Diaconn G8 Preferences
+- 配置管理器 > 泵体 > Diaconn G8 > 设置
+- DIACONN G8顶部 > 右上角三点按钮 > Diaconn G8偏好设置
-- If the **Log reservoir change** option is activated, the relevant details are automatically uploaded to the careportal when an “Insulin Change” event occurs.
-- If the **Log needle change** option is activated, the relevant details are automatically uploaded to the careportal when a “Site Change” event occurs.
-- If the **Log tube change** option is activated, the relevant details are automatically uploaded to the careportal when a “Tube Change” event occurs.
-- If the **Log battery change** option is activated, the relevant details are automatically uploaded to the careportal when a “Battery Change” event occurs, and the PUMP BATTERY CHANGE button in the ACTION tab is deactivated. (Note: To change the battery, please stop all in-progress injection functions before proceeding.)
+- 若启用**记录储药器更换**选项，发生"胰岛素更换"事件时将自动上传相关数据至careportal。
+- 若启用**记录针头更换**选项，发生"输注部位更换"事件时将自动上传相关数据至careportal。
+- 若启用**记录管路更换**选项，发生"管路更换"事件时将自动上传相关数据至careportal。
+- 若启用**记录电池更换**选项，发生"电池更换"事件时将自动上传相关数据至careportal，同时操作标签页中的泵电池更换按钮将失效。 （注意：更换电池前请先停止所有正在执行的输注功能。）
-### Extended Bolus function
+### 扩展大剂量功能
-- If you use extended bolus it will disable closed loop.
-- See [this page](#Extended-Carbs-why-extended-boluses-won-t-work-in-a-closed-loop-environment) for details why extended bolus does not work in a closed loop environment.
+- 使用扩展大剂量功能将关闭闭环系统。
+- 具体原因请参阅[此页面](#Extended-Carbs-why-extended-boluses-won-t-work-in-a-closed-loop-environment)了解为何扩展大剂量功能在闭环环境中不可用。
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/EOPatch2.md b/docs/CROWDIN/zh_CN/CompatiblePumps/EOPatch2.md
index a25540cb1dc4..d9a8597b50b2 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/EOPatch2.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/EOPatch2.md
@@ -2,159 +2,159 @@
orphan: true
- - -
-# EOPatch2 Instruction Manual
+# EOPatch2 使用说明书
-The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage.
+贴片泵需使用速效U-100型胰岛素（如诺和锐或优泌乐）。 根据医生处方使用适合您的速效胰岛素，并注射规定剂量。
-The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U.
+使用贴片泵时最小可注射剂量为0.05单位，故配置文件基础率应设为≥0.05单位/小时且间隔为0.05单位/小时，否则可能导致配置文件预估总量与贴片实际输注量间出现误差。 同样地，大剂量也需设置最小输注量为0.05单位进行输注。
-## Pump Setup
-1. On the AAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder.
-1. Select 'EOPatch2' in the Pump section.
-1. Press the Back key to return to the home screen.
+## 泵设置
+1. 在AAPS主界面点击左上角汉堡菜单，进入配置生成器。
+1. 在泵体选项中选择'EOPatch2'。
+1. 按“返回”键返回主屏幕。
 
## 设置
-Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab.
+在主界面顶部选择EOPATCH2进入EOPATCH2标签页。
-Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner.
+点击右上角三点图标选择EOPatch2偏好设置菜单。
-The EOPatch2 Preferences menu offers a menu to set 3 types of notifications.
+EOPatch2偏好设置菜单提供3种通知类型设定选项。
### 储药器药量低警告
-A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments.
+当储药器内剩余胰岛素量达到或低于设定值时，贴片泵将显示警告。 可设置范围为10至50单位，以5单位为增量。
### 敷贴更换提醒
-This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours.
+此为当前贴片到期前的剩余时间提醒功能。 可设置范围为1至24小时，以1小时为增量。 初始设定值为4小时。
-### Patch buzzer Reminder
-This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off.
+### 贴片蜂鸣提醒
+此为除基础输注外的注射提醒功能。 若使用(扩展)大剂量注射或临时基础率注射，贴片将在注射开始时及完成时发出蜂鸣声。 初始设定值为关闭。
-## Connecting the Patch
+## 连接贴片泵
-### Move to patch connection screen
+### 转至贴片泵连接界面
-Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left.
+在主界面顶部选择EOPATCH2，并点击左下角的激活贴片按钮。
-### Connecting the patch
-Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen.
+### 连接贴片泵
+将注射器针头插入贴片泵的胰岛素注入口，然后缓慢推动活塞注射胰岛素。 当注入胰岛素量超过80单位时，贴片泵会发出启动提示音（1声蜂鸣）并开始启动。 确认蜂鸣声后，点击屏幕上的开始配对按钮。
[警告]
-- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise.
-- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work.
-- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C.
+- 在收到指示前请勿转动针头操作杆。 否则可能导致注射过程或安全检查中出现严重问题。
+- 贴片泵可注射胰岛素量为80~200单位。 若初始注入量少于80单位，贴片泵将无法工作。
+- 将准备注入贴片泵的胰岛素从冰箱取出，提前在室温下放置15至30分钟。 待注射胰岛素温度必须≥10°C。
-### patch pairing
-The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again.
+### 贴片泵配对
+贴片泵配对界面将显示，系统会自动尝试配对。 若通信成功，将显示蓝牙配对请求通知。 当出现带验证码的蓝牙配对请求通知时点击确定，第二次出现时再次选择确定。
[警告]
-- For pairing, the patch and the smartphone must be located within 30 cm of each other.
-- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete.
-- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded.
+- 配对时，贴片泵与智能手机间距须保持在30厘米以内。
+- 贴片泵启动完成后，将每3分钟发出一次蜂鸣直至配对完成。
+- 贴片泵启动后，须在60分钟内通过应用程序完成敷贴操作。 若60分钟内无法完成敷贴，应弃用该贴片泵。
  
-### patch preparation
-After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT.
+### 贴片泵准备
+揭除贴片泵胶带后，请检查针头是否外露。 若贴片泵无异常，请点击下一步。
-### Patch attachment
-Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location.
+### 贴片泵敷贴
+胰岛素应注射至皮下脂肪丰富而神经血管较少的部位，故推荐选择腹部、手臂或大腿作为贴片泵敷贴部位。 选择敷贴部位并消毒后，即可敷贴贴片泵。
[警告]
-- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin.
-- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch.
+- 请确保将贴片泵胶带接触身体的一侧展平，使其完全贴合皮肤。
+- 若贴片泵未完全粘合，空气可能渗入贴片与皮肤之间，导致粘附力及防水效果下降。
-### Safety Check
-When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once.
+### 安全检查
+敷贴完成后，请轻触开始安全检查。 安全检查完成后，贴片泵将发出一次蜂鸣声。
[警告]
-- For safe use, do not turn the needle action lever until the safety check has been completed.
+- 为确保安全使用，在安全检查完成前请勿转动针头操作杆。
 
-### Inserting the needle
-The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT.
+### 插入针头
+手持贴片泵周围，将针头操作杆向上方转动超过100度即可完成插针。 正确插入针头时会发出蜂鸣提示音。 沿顺时针方向继续转动针头操作杆以释放该装置。 点击“下一步”。
-[Caution]
+[注意]
-- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear.
+- 若未听到蜂鸣声就进入下一步，将出现针头插入错误警告。
-## Discarding the patch
-Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch.
+## 废弃贴片泵
+当胰岛素余量不足、使用到期或设备出现缺陷时，必须更换贴片泵。 每台贴片泵建议使用期限为启动后84小时。
-### Discarding the patch
-Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed.
+### 废弃贴片泵
+在主页顶部选择EOPATCH2，并点击底部废弃/更换贴片泵按钮。 在下一界面点击废弃贴片泵按钮。 将再次弹出确认对话框，选择废弃贴片泵按钮即可完成处置。
   
-## Suspending and Resuming Insulin Delivery
-Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes.
+## 暂停和恢复胰岛素输注
+暂停胰岛素输注将同时取消大剂量延注和临时基础率功能。 恢复胰岛素输注时，被取消的大剂量延注和临时基础率不会自动恢复。 胰岛素输注暂停期间，贴片泵将每15分钟发出提示音。
-### Suspending insulin delivery
-Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time.
+### 暂停胰岛素输注
+在主页顶部选择EOPATCH2，并点击右下角暂停按钮。 选择确认框中的确定后，将出现时间选择框。 选定时间后点击确认按钮，胰岛素输注将按设定时长暂停。
  
-### Resuming insulin delivery
-Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box.
+### 恢复胰岛素输注
+在主页顶部选择EOPATCH2，并点击右下角恢复按钮。 在确认对话框中选择确定即可恢复胰岛素输注。
 
-## Alarms/Warnings
+## 警报/警告
### 报警
-Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed.
+警报针对最高优先级的紧急情况发出，需立即采取应对措施。 该警报信号在被确认前不会自动消失或超时终止。 当使用中的贴片泵出现问题时将触发警报，此时可能需要废弃当前设备并更换新贴片泵。 警告信息将以对话框形式显示，在处理完成前无法切换至其他界面。
 
-The different types of alarms are explained below.
+各类警报说明如下。
-| 报警 | Explanation |
-| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 储药器空了 | Occurs when the patch’s reservoir runs out of insulin. |
-| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. |
-| 堵管 | Occurs when it appears that the patch's insulin inlet is clogged. |
-| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. |
-| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. |
-| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. |
-| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. |
-| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. |
-| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. |
+| 报警 | 说明 |
+| ------- | ---------------------------------------------------------- |
+| 储药器空了 | 当贴片泵储药器内胰岛素耗尽时触发。 |
+| 贴片泵过期 | 当贴片泵使用期限届满且无法继续输注胰岛素时触发。 |
+| 堵管 | 当检测到贴片泵胰岛素入口堵塞时触发。 |
+| 上电自检失败 | 当贴片泵在启动后自检过程中发现意外错误时触发。 |
+| 温度异常 | 当贴片泵在佩戴使用期间超出正常工作温度范围时触发。 处理此警报需将贴片泵移至适宜工作温度环境（4.4至37摄氏度）。 |
+| 针头插入错误 | 当贴片泵佩戴过程中针头插入异常时触发。 请检查贴片泵针头插入端与针头启动按钮是否保持直线对齐。 |
+| 贴片泵电池故障 | 当贴片泵内置电池即将耗尽并关机前触发。 |
+| 贴片泵启动故障 | 当贴片泵启动后60分钟内应用程序未能完成佩戴流程时触发。 |
+| 贴片泵故障 | 当贴片泵在佩戴使用过程中遭遇意外错误时触发。 |
### 警告
-A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen.
+在中等或低优先级情况下会发出警告。 警告触发时，将以通知形式显示在总览界面。
-The different types of warnings are explained below.
+各类警告说明如下。
-| Warnings | Explanation |
-| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
-| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. |
-| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. |
-| Patch operating life expired | Occurs when the patch usage period is over. |
-| Patch will expire soon | Occurs 1 hour before the patch must be discarded. |
-| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. |
-| Patch battery low | Occurs when the patch's battery is low. |
+| 警告 | 说明 |
+| --------- | ------------------------------ |
+| 胰岛素暂停结束 | 当用户设定的胰岛素输注暂停时间届满时触发。 |
+| 储药量低 | 当贴片泵内剩余胰岛素低于设定量时触发。 |
+| 贴片泵使用期限届满 | 当贴片泵使用期限届满时触发。 |
+| 贴片泵即将到期 | 当贴片泵达到必须废弃时间前1小时触发。 |
+| 贴片泵启动未完成 | 当贴片泵完成配对后的佩戴阶段因中断导致耗时超过3分钟时触发。 |
+| 贴片泵电量不足 | 当贴片泵电池电量不足时触发。 |
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/zh_CN/CompatiblePumps/Equil5.3.md
index 62fe9e54d18e..c6e6e6c4067f 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/Equil5.3.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/Equil5.3.md
@@ -4,22 +4,22 @@ orphan: true
# Equil 5.3
-These instructions are for configuring the Equil insulin pump.
+以下说明用于配置Equil胰岛素泵。
-## Pump capabilities with AAPS
+## AAPS支持的胰岛素泵功能
§todo
-## Hardware and Software Requirements
-* **Compatible Equil hardware**
+## 硬件和软件要求
+* **兼容的Equil硬件设备**
§todo
-* [Version 3.3.0.0](#version3300) or newer of AAPS
+* [版本3.3.0.0](#version3300)或更高版本的AAPS
-### Select Equil pump
+### 选择 Equil 泵
-In [Config Builder > Pump](#Config-Builder-pump), switch to **Equil 5.3**.
+在[配置构建器 > 泵](#Config-Builder-pump)中，切换至**Equil 5.3**。
### 设置
@@ -27,7 +27,7 @@ In [Config Builder > Pump](#Config-Builder-pump), switch to **Equil 5.3**.
### Activate patch
-Navigate to the Equil Tab and press **Pair Equil Patch Pump**.
+进入Equil标签页，点击**配对Equil贴片泵**。
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/zh_CN/CompatiblePumps/Future-possible-Pump-Drivers.md
index c4ea3879f67f..be85463d06e2 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -4,43 +4,43 @@ orphan: true
* * *
-# Future (possible) Pump Drivers
+# 未来（可能）的泵驱动程序
-This is list of some Pumps floating around there, and status of support for them in any of Looping systems and then status in AAPS. On end there is some info, what is required for a pump to be "Loop capable".
+这是市面上部分胰岛素泵的清单，包含各循环系统对其支持状态及在AAPS中的兼容情况。 文末附有胰岛素泵实现"闭环兼容"所需条件的说明。
-## Pumps that are Loopable
+## 能闭环的泵
-### Kaleido ([Homepage](https://www.hellokaleido.com/))
+### Kaleido ([主页](https://www.hellokaleido.com/))
-**Loop status:** Pump is a Loop candidate, but protocol is unknown at the time. No interest in open source from the vendor.
+**闭环状态:** 泵是闭环候选，但当前协议未知。 厂商对开源不感兴趣。
-**Hardware requirement for AAPS:** None. It seems to be BT enabled.
+**硬件要求 AAPS：** 无。 似乎启用了蓝牙。
-### Tandem: t:slim X2 ([Homepage](https://www.tandemdiabetes.com/))
+### Tandem: t:slim X2 ([主页](https://www.tandemdiabetes.com/))
-**Loop status:** Not yet loopable.
+**闭环状态:** 尚不可闭环。
-While in the past company has decided not to allow their pumps to be controlled by external devices, it seems that last few years have been a game changer. Company decided to upgrade their t:slim X2 pump to be able to be controlled remotely (via t:connect app), which means that avenues are opened that we might be able to look forward to have control of pump via AAPS in the future. New pump firmware is planned to be released soon (this or next year, before their tubeless pump t:sport comes out). There are no details yet, what operations will be possible from t:connect (Bolus definitely, everything else unknown).
+虽然过去公司决定不允许外部设备控制他们的泵，但最近几年似乎发生了重大转变。 公司决定升级其t:slim X2泵以实现远程控制（通过t:connect应用程序），这意味着我们有望在未来通过AAPS控制泵。 新泵固件计划很快发布（今年或明年，在其无管路泵t:sport上市之前）。 目前尚不清楚t:connect将支持哪些操作（大剂量肯定可以，其他功能均未知）。
-**Hardware requirement for AAPS:** None. It seems to be BT enabled.
+**硬件要求 AAPS：** 无。 似乎启用了蓝牙。
-### Tandem: t:Mobi & t:slim X3 & t:Mobi Tubeless ([Homepage](https://www.tandemdiabetes.com/about-us/pipeline))
+### Tandem：t:Mobi、t:slim X3和t:Mobi无管路版（[官网](https://www.tandemdiabetes.com/about-us/pipeline)）
-**Loop status:** All 3 pumps will be Loop candidates.
+**闭环状态:** 所有3款泵都将成为闭环候选。
-Awaiting release in Europe.
+等待在欧洲发布。
-**Hardware requirement for AAPS:** None. It seems to be BT enabled.
+**硬件要求 AAPS：** 无。 似乎启用了蓝牙。
-### Willcare Insulin pump ([Homepage](http://shinmyungmedi.com/en/))
+### Willcare Insulin pump ([首页](http://shinmyungmedi.com/en/))
-**Loop status:** At the moment its not Loop candidate, but we were contacted by their staff and they interested in extending their pump to be loopable (at the moment I think its missing only get/set profile commands).
+**闭环状态:** 目前尚不具备闭环条件，但其工作人员已与我们联系，并表示有意扩展泵的闭环功能（目前仅缺少获取/设置配置文件的指令）。
-**Hardware requirement for AAPS:** None. It seems to be BT enabled.
+**硬件要求 AAPS：** 无。 似乎启用了蓝牙。
-**Comments:** Since company is interested in integration with AAPS, they might do implementation themselves.
+**备注：** 由于该公司有意与AAPS整合，可能会自行实现相关功能。
-## Pumps no longer sold (companies no longer operating)
+## 不再销售的泵（公司已停止运营）
### Animas Vibe
@@ -50,53 +50,53 @@ Awaiting release in Europe.
### Accu-Chek Insight
-**Comments:** End of support March 2025.
+**备注：** 支持终止于2025年3月。
-## Pumps that aren't Loopable
+## 无法闭环的泵
-### Medtronic Bluetooth
+### Medtronic 蓝牙
-**Comments:** Medtronic [withdrew](https://www.tidepool.org/blog/tidepool-loop-partner-update-ace-pumps).
+**评论：** Medtronic [已撤回](https://www.tidepool.org/blog/tidepool-loop-partner-update-ace-pumps)。
### Accu-Chek Solo
-**Comments:** No community success in communicating with the Solo pump.
+**备注：** 社区未能成功与Solo泵通信。
-### Ypsomed Pump
+### Ypsomed 泵
-**Comments:** Ypso added very heavy 3rd party encryption.
+**备注：** Ypso增加了非常严格的第三方加密。
-## Requirements for pumps being loopable
+## 泵实现闭环的要求
-**Prerequisite**
+**先决条件**
-- Pump has to support some kind of remote control. (BT, Radio frequency, etc)
-- Protocol is hacked/documented/etc.
+- 泵必须支持某种远程控制功能。 （蓝牙，无线电频率等）
+- 协议已被破解/记录/等。
-**Minimal requirement**
+**最低要求**
-- Set Temporary Basal Rate
-- Get Status
-- Cancel Temporary Basal Rate
+- 设置临时基础率
+- 获取状态
+- 取消临时基础率
-**For oref1(SMB) or Bolusing:**
+**对于oref1(超微大剂量)或大剂量给药：**
-- Set Bolus
+- 设置大剂量
-**Good to have**
+**最好有**
-- Cancel Bolus
-- Get Basal Profile (almost requirement)
-- Set Basal Profile (nice to have)
-- Read History
+- 取消大剂量
+- 获取基础率配置文件（几乎是必需条件）
+- 设置基础率配置文件（最好具备）
+- 读取历史记录
-**Other (not required but good to have)**
+**其他（不是必需的，但最好有）**
-- Set Extended Bolus
-- Cancel Extended Bolus
-- Read History
-- Read TDD
+- 设置扩展大剂量
+- 取消扩展大剂量
+- 读取历史记录
+- 读取 TDD
-### Other pumps support
+### 其他泵支持
-If you have any other pumps you would like to see status on, please contact us on discord.
\ No newline at end of file
+若您想了解其他泵的状态，请在Discord上联系我们。
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtronicPump.md
index 81a65283f4f9..e1355220c228 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtronicPump.md
@@ -4,190 +4,190 @@ orphan: true
* * *
-# Medtronic Pumps
+# 美敦力胰岛素泵
-The driver does not work with any newer models, including all models ending in G (530G, 600-series [630G, 640G, 670G], 700-series [770G, 780G], etc.).
+该驱动不适用于任何新型号，包括所有以G结尾的型号（530G、600系列[630G、640G、670G]、700系列[770G、780G]等）。
-The following model and firmware combinations are compatible:
+以下型号与固件组合兼容：
-- 512/712 (any firmware version)
-- 515/715 (any firmware version)
-- 522/722 (any firmware version)
-- 523/723 (firmware 2.4A or lower)
-- 554/754 EU release (firmware 2.6A or lower)
-- 554/754 Canada release (firmware 2.7A or lower)
+- 512/712（任何固件版本）
+- 515/715（任何固件版本）
+- 522/722（任何固件版本）
+- 523/723（固件 2.4A 或更低版本）
+- 554/754 欧盟版（固件 2.6A 或更低版本）
+- 554/754 加拿大版（固件 2.7A 或更低版本）
-You can find out how to check the firmware on the pumps at [OpenAPS docs](https://openaps.readthedocs.io/en/latest/docs/Gear%20Up/pump.html#how-to-check-pump-firmware-check-for-absence-of-pc-connect) or [LoopDocs](https://loopkit.github.io/loopdocs/build/step3/#medtronic-pump-firmware).
+您可在[OpenAPS文档](https://openaps.readthedocs.io/en/latest/docs/Gear%20Up/pump.html#how-to-check-pump-firmware-check-for-absence-of-pc-connect)或[LoopDocs](https://loopkit.github.io/loopdocs/build/step3/#medtronic-pump-firmware)中查看如何检查泵的固件版本。
-## Hardware and software requirements
+## 硬件和软件要求
-- **Phone:** The Medtronic driver should work with any android phone that supports Bluetooth connections. **IMPORTANT: Phone manufacturers Bluetooth implementations can vary so how each phone model behaves can vary. For example, some phones will handle enabling/disabling Bluetooth differently. This can impact the user experience when AAPS needs to reconnect to your Rileylink type device.**
-- **RileyLink Compatible Device:** Android phones cannot communicate to Medtronic pumps without a separate device to handle communications. This device will link with your phone via Bluetooth and with your pump via a compatible radio connection. The first such device was called a Rileylink but a number of other options are now available which can offer additional functionality.
+- **电话：** 美敦力驱动程序应适用于任何支持蓝牙连接的安卓手机。 **重要提示： 手机制造商的蓝牙实现方式可能有所不同，因此每种手机型号的表现也可能不同。 例如，某些手机处理启用/禁用蓝牙的方式会有所不同。 这可能会影响当AAPS需要重新连接到您的Rileylink类型设备时的用户体验。**
+- **RileyLink兼容设备：** 安卓手机无法直接与美敦力泵通信，需要额外的设备来处理通信。 该设备将通过蓝牙与您的手机连接，并通过兼容的无线连接与您的泵通信。 首个此类设备被称为Rileylink，但现在已有多种其他选择可提供额外功能。
- - Rileylink available at [getrileylink.org](https://getrileylink.org/product/rileylink916)
- - Orangelink available at [getrileylink.org](https://getrileylink.org/product/orangelink)
- - Emalink (multiple model options) available at [github.com](https://github.com/sks01/EmaLink)
- - Gnarl (some additional DIY required) details available at [github.com](https://github.com/ecc1/gnarl)
+ - Rileylink可在[getrileylink.org](https://getrileylink.org/product/rileylink916)获取
+ - Orangelink可在[getrileylink.org](https://getrileylink.org/product/orangelink)获取
+ - Emalink(多种型号可选)可在[github.com](https://github.com/sks01/EmaLink)获取
+ - Gnarl(需要额外DIY)详情请见[github.com](https://github.com/ecc1/gnarl)
-A comparison chart for the various Rileylink compatible devices can be found at [getrileylink.org](https://getrileylink.org/rileylink-compatible-hardware-comparison-chart)
+各款Rileylink兼容设备的对比图表可在[getrileylink.org](https://getrileylink.org/rileylink-compatible-hardware-comparison-chart)查看
(MedtronicPump-configuration-of-the-pump)=
-## Configuration of the pump
+## 配置您的泵：
-The following settings should be configured on the pump in order for AAPS to remotely send commands. The steps necessary to make each change on a Medtronic 715 are shown in brackets for each setting. The exact steps may vary based on pump type and/or firmware version.
+为便于AAPS远程发送指令，需在泵上配置以下设置。 美敦力715泵上更改每个设置所需的操作步骤已在各项设置后用括号标出。 具体步骤可能因泵型号和/或固件版本而异。
-- **Enable remote mode on Pump** (On the pump press Act and go to Utilities -> Remote Options, Select On, and on next screen do Add ID and add any random id such as 111111). At least one ID must be on the Remote ID list in order for the pump to expect remote communication.
-- **Set Max Basal** (On the pump press Act and got to Basal and then select Max 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.
-- **Set Max Bolus** (On the pump press Act and to to Bolus and then select Max Bolus) This is the largest bolus that the pump will accept. The maximum value permitted by the pump is 25.
-- **Set profile to Standard**. (On the pump press Act and go to Basal and then Select Patterns) The pump will only need one profile as AAPS will manage different profiles on your phone. No other patterns are required.
-- **Set Temporary Basal Rate type** (On the pump press Act and go to Basal and then Temp Basal Type). Select Absolute (not Percent).
+- **启用泵的远程模式**（在泵上按Act键，进入Utilities -> Remote Options，选择On，在下一屏幕选择Add ID并添加任意随机ID如111111）。 远程ID列表中必须至少有一个ID，泵才会接收远程通信。
+- **设置最大基础率**（在泵上按Act键，进入Basal然后选择Max Basal Rate）例如，将此值设置为标准最大基础率的四倍将允许400%的临时基础率。 泵允许的最大值为每小时34.9单位。
+- **设置最大单次剂量**（在泵上按Act键，进入Bolus然后选择Max Bolus）这是泵将接受的最大单次剂量。 泵允许的最大值为25单位。
+- **将配置文件设为标准**。 （在泵上按Act键，进入Basal然后选择Patterns）泵只需一个配置文件，因为AAPS将在您的手机上管理不同的配置文件。 无需其他模式。
+- **设置临时基础率类型**（在泵上按Act键，进入Basal然后选择Temp Basal Type）。 选择绝对量（非百分比）。
-## Medtronic Configuration of Phone/AAPS
+## 手机/AAPS的美敦力配置
-- **Do not pair RileyLink compatible device with the Bluetooth menu on your phone.** Pairing via the Bluetooth menu on your phone will stop AAPS from seeing your Rileylink Compatible device when you follow the instructions below.
-- Disable automatic screen rotation on your phone. On certain devices automatic screen rotation causes Bluetooth sessions to restart which would cause issues for your Medtronic pump.
-- There are two ways to configure your Medtronic pump in AAPS:
+- **不要通过手机蓝牙菜单配对RileyLink兼容设备。** 若通过手机蓝牙菜单配对，按照以下说明操作时将导致AAPS无法识别您的RileyLink兼容设备。
+- 禁用您手机上的自动屏幕旋转功能。 在某些设备上，自动屏幕旋转会导致蓝牙会话重新启动，这会给您的美敦力泵带来问题。
+- 在AAPS中有两种配置美敦力泵的方式：
-1. Using the setup wizard as part of a fresh install
-2. By selecting the cog icon beside the Medtronic selection in the pump selection option in Config Builder
+1. 使用新安装时的设置向导
+2. 通过在Config Builder的泵选择选项中点击美敦力选项旁的齿轮图标
-When configuring your Medtronic pump with the setup wizard it is possible that you will be prevented from completing setup because of Bluetooth issues (e.g. you cannot successfully connect to the pump). Should this happen you should select the virtual pump option in order to complete the configuration and allow for further troubleshooting by using option 2.
+使用设置向导配置美敦力泵时，可能会因蓝牙问题（例如无法成功连接泵）而无法完成设置。 若发生此情况，您应选择虚拟泵选项以完成配置，并通过使用选项2进行进一步故障排除。
-While setting up AAPS to work with your medtronic pump you need to set following items: (see picture above)
-
-- **Pump Serial Number**: Displayed on the back of your pump and starts with SN. You should only enter the 6 numbers shown without any alphabetic characters (e.g. 123456).
-- **Pump Type**: The model pump you are using (e.g. 522).
-- **Pump Frequency**: There are two options based on where your pump was originally distributed. Please check the [FAQ](#faq) if you are unsure which option to select):
- - for US & Canada, frequency used is 916 Mhz
- - for Worldwide, frequency used is 868 Mhz
-- **Max Basal on Pump (U/h)**: This needs to match the setting set on your pump (see Configuration of the pump above). Again this setting must be carefully selected as it will determine how much AAPS can deliver via your basal rate. This will effectively set the maximum temporary basal rate. As an example, setting this value to four times your maximum standard basal rate would allow a 400% Temporary Basal Rate. The maximum value permitted by the pump is 34.9 units per hour.
-- **Max Bolus on Pump (U)** (in an hour): This needs to match the setting set on your pump (see Configuration of the pump above). This setting should be carefully considered as it determines how large a bolus AAPS can ever set.
-- **Delay before Bolus is started (s)**: The number of seconds after a bolus is issued before the command is actually sent to the pump. This period of time allows the user to cancel the bolus in the event a bolus command is sent in error. It is not possible to cancel a bolus that has started via AAPS. The only way to cancel a bolus that has already started is to suspend the pump manually followed by resuming it.
-- **Medtronic Encoding**: Determines if the medtronic encoding is carried out. Selecting Hardware encoding (i.e. carried out by the Rileylink compatible device) is preferred as this results in less data being sent. Selecting Software encoding (i.e. carried out by AAPS) can help in the event frequent disconnects are seen. This setting will be ignored if you have firmware version 0.x on Rileylink devices.
-- **Battery Type (Power View)**: In order to correctly determine the remaining battery power level you should select the type of AAA battery in use. When a value other than simple view is selected AAPS will display the remaining calculated battery percentage level and volts. The following options are available:
+在设置AAPS与您的美敦力泵配合使用时，需要配置以下项目：(参见上图)
+
+- **泵序列号**：显示在泵背面，以SN开头。 只需输入显示的6位数字，无需输入任何字母字符（例如123456）。
+- **泵型号**：您正在使用的泵型号（例如522）。
+- **泵频率**：根据泵的原始销售地区有两种选项。 如不确定选择哪个选项，请查阅[常见问题](#faq)）：
+ - 美国及加拿大地区使用的频率为916 MHz
+ - 全球其他地区使用的频率为868 MHz
+- **泵上最大基础率（单位/小时）**：必须与泵上的设置保持一致（参见上文泵配置部分）。 此设置必须谨慎选择，因为它将决定AAPS能通过基础率输送多少胰岛素。 这将实际设定临时基础率的最大值。 例如，将此值设为标准最大基础率的四倍，将允许400%的临时基础率。 泵允许的最大值为每小时34.9单位。
+- **泵上最大单次剂量（单位）**（每小时）：必须与泵上的设置保持一致（参见上文泵配置部分）。 此设置需慎重考虑，因为它决定了AAPS能设置的单次剂量上限。
+- **单次剂量开始前延迟（秒）**：发出单次剂量指令后，实际发送至泵前的等待秒数。 这段延迟时间允许用户在错误发送单次剂量指令时取消操作。 已通过AAPS启动的单次剂量无法取消。 取消已启动单次剂量的唯一方法是手动暂停泵，然后恢复运行。
+- **美敦力编码**：决定是否执行美敦力编码。 首选选择硬件编码（即由Rileylink兼容设备执行），这样可减少数据传输量。 若出现频繁断开连接的情况，选择软件编码（即由AAPS执行）可能有所帮助。 如果您在Rileylink设备上使用0.x版本固件，此设置将被忽略。
+- **电池类型（电量显示）**：为准确判断剩余电量，请选择当前使用的AAA电池类型。 当选择非简易视图时，AAPS将显示计算得出的剩余电量百分比及电压值。 可选选项如下：
- 未选择 (简单视图)
- 碱性电池 (扩展视图)
- 锂电池(扩展视图)
- 镍锌电池(扩展视图)
- 镍氢电池 (扩展视图)
-- **Bolus/Treatments Debugging**: Select On or Off depending on requirements.
+- **单次剂量/治疗调试**：根据需求选择开启或关闭。
-- **RileyLink Configuration**: This option allows you to find and pair your Rileylink compatible device. Selecting this will show any nearby Rileylink compatible devices and the signal strength.
-- **Use Scanning** Activates Bluetooth scanning before connecting with your Rileylink Compatible devices. This should improve the reliability of your connection to the device.
-- **Show battery level reported by OrangeLink/EmaLink/DiaLink** This feature is only supported on newer link devices such as the EmaLink or OrangeLink. Values will be shown in the Medtronic tab in AnroidAPS.
-- **Set neutral temp basals** By default Medtronic pumps beep on the hour when a temporary basal rate is active. Enabling this option can help reduce the number of beeps heard by interrupting a temporary basal at the hour change in order to suppress the beep.
+- **RileyLink配置**：此选项可用于查找并配对您的Rileylink兼容设备。 选择此项将显示附近所有Rileylink兼容设备及其信号强度。
+- **启用扫描** 在与Rileylink兼容设备连接前启动蓝牙扫描功能。 这将提高设备连接的可靠性。
+- **显示OrangeLink/EmaLink/DiaLink报告的电池电量** 此功能仅适用于新型连接设备（如EmaLink或OrangeLink）。 数值将在AndroidAPS的美敦力标签页中显示。
+- **设置中性温度基础率** 默认情况下，美敦力泵在临时基础率激活时会每小时发出提示音。 启用此选项可通过在整点切换时中断临时基础率来减少提示音次数。
-## MEDTRONIC (MDT) Tab
+## 美敦力(MDT)标签页
- When AAPS is configured to use a Medtronic pump a MDT tab will be shown in the list of tabs at the top of the screen. This tab displays the current pump status information along with some Medtronic specific actions.
+ 当AAPS配置为使用美敦力泵时，屏幕顶部的标签列表中将显示一个MDT标签。 该标签显示当前泵状态信息以及一些美敦力特定操作。
-- **RileyLink Status**: The current status of the connection between your phone and Rileylink compatible device. This should show as Connected at all times. Any other status may require user intervention.
-- **RileyLink Battery**: The current battery level of your EmaLink or OrangeLink device. Dependent on selecting "Show battery level reported by OrangeLink/EmaLink/DiaLink device" in the Medtronic Pump Configuration menu.
-- **Pump Status**: The current status of the pump connection. As the pump will not be constantly connected this will primarily show the sleep icon. There are a number of possible other status including "Waking Up" when AAPS is trying to issue a command or other possible pump commands such as "Get Time", "Set TBR", etc.
-- **Battery**: Shows battery status based on the value chosen for Battery Type (Power View) in the Medtronic Pump Configuration menu.
-- **Last connection**: How long ago the last successful pump connection happened.
-- **Last Bolus**: How long ago the last successful bolus was delivered.
-- **Base Basal Rate**: This is the base basal rate that runs on pump at this hour in your active Profile.
-- **Temp basal**: Temp basal currently being delivered which can be 0 units per hour.
-- **Reservoir**: How much insulin is in reservoir (updated at least every hour).
-- **Errors**: Error string if there is problem (mostly shows if there is error in configuration).
+- **RileyLink状态**：显示手机与Rileylink兼容设备之间的当前连接状态。 这应始终显示为"已连接"。 任何其他状态都可能需要用户干预。
+- **RileyLink电量**：显示EmaLink或OrangeLink设备的当前电量。 取决于是否在美敦力泵配置菜单中选择"显示OrangeLink/EmaLink/DiaLink设备报告的电量"。
+- **泵状态**：显示泵连接的当前状态。 由于泵不会持续连接，这里主要会显示睡眠图标。 其他可能状态包括：AAPS尝试发送命令时的"正在唤醒"状态，以及其他可能的泵命令状态如"获取时间"、"设置临时基础率"等。
+- **电池**：根据美敦力泵配置菜单中"电池类型(电量显示)"选项的选择值显示电池状态。
+- **上次连接**：显示最近一次成功泵连接发生的时间间隔。
+- **上次大剂量**：显示最近一次成功输送大剂量的时间间隔。
+- **基础率**：这是您当前配置文件中泵在此小时运行的基础率。
+- **临时基础率**：当前正在输送的临时基础率，可能为0单位/小时。
+- **储药器**：储药器中的胰岛素量(至少每小时更新一次)。
+- **错误**：出现问题时显示的错误字符串(主要显示配置中的错误)。
-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)）
+- **RL统计**：显示RL统计信息（参见[下文](#rl-status-rileylink-status)）
(MedtronicPump-pump-history)=
-## Pump History
+## 泵历史记录
-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.
+泵历史记录每5分钟检索一次并存储在本地。 仅存储最近24小时的历史记录。 这为查看泵行为（如有需要）提供了便捷方式。 仅存储与AAPS相关的项目，不包括无关的配置功能。
(MedtronicPump-rl-status-rileylink-status)=
-## RL Status (RileyLink Status)
+## RL状态(RileyLink状态)
 
-The RL Status dialog has two tabs:
+RL状态对话框包含两个标签页：
-- **Settings**: Shows settings about the RileyLink compatible device: Configured Address, Connected Device, Connection Status, Connection Error and RileyLink Firmware versions. Device Type is always Medtronic Pump, Model would be your model, Serial number is configured serial number, Pump Frequency shows which frequency you use, Last Frequency is last frequency used.
-- **History**: Shows communication history, items with RileyLink shows state changes for RileyLink and Medtronic shows which commands were sent to pump.
+- **设置**：显示RileyLink兼容设备的设置信息：配置地址、连接设备、连接状态、连接错误和RileyLink固件版本。 设备类型始终为美敦力泵，型号即您的泵型号，序列号为配置的序列号，泵频率显示您使用的频率，最后频率为上次使用的频率。
+- **历史记录**：显示通信历史记录，其中带有RileyLink的项目显示RileyLink状态变更，美敦力项目显示发送给泵的指令。
## 手动操作
-When the Medtronic driver is used, two additional actions are added to Actions Tab:
+使用美敦力驱动时，操作选项卡会新增两个操作项：
-- **Wake and Tune Up** - In the event that AAPS hasn't connected to your pump for a sustained period (it should connect every 5 minutes), you can force a Tune Up. This will try to contact your pump, by searching all of the possible radio frequencies used by your pump. In the event a successful connection is made the successful frequency will be set as the default.
-- **Reset RileyLink Config** - If you reset your RileyLink compatible device you may need to use this action so that device can be reconfigured (frequency set, frequency type set, encoding configured).
+- **唤醒并调谐** - 若AAPS长时间未连接您的泵(本应每5分钟连接一次)，可强制进行调谐。 此操作将通过搜索您泵可能使用的所有无线电频率来尝试建立连接。 若成功建立连接，该成功频率将被设为默认值。
+- **重置RileyLink配置** - 若您重置了RileyLink兼容设备，可能需要使用此操作重新配置设备(设置频率、频率类型及编码配置)。
-## Important notes
+## 重要说明
-### Special attention in NS configuration needed
+### 需要特别注意NS配置
-AAPS is using serial number for synchronization and serial number is exposed to NS. Because knowledge of serial number of old Medtronic pump can be used to control the pump remotely take special care to hardening NS site preventing leakage of SN of your pump. See https://nightscout.github.io/nightscout/security/
+AAPS使用序列号进行同步，且该序列号会暴露给NS。 由于掌握旧款美敦力泵的序列号可能被用于远程控制泵，请特别注意强化NS站点防护，防止泵序列号泄露。 参见 https://nightscout.github.io/nightscout/security/
-### OpenAPS users
+### OpenAPS用户
-OpenAPS users should note that AAPS with Medtronic uses a completely different approach than OpenAPS. Using AAPS the primary method of interacting with th pump is via your phone. In normal use cases it is likely that the only time it is required to use the pump menu is when changing resevoirs. This is very different when using OpenAPS where at least some of a bolus is usually delivered via the quick bolus buttons. In the event the pump is used to manually deliver a bolus there can be issues if AAPS attempts to deliver one at the same time. There are checks to try and prevent issues in such cases but this should still be avoided where possible.
+OpenAPS用户须知：AAPS与美敦力泵配合使用的方案与OpenAPS完全不同。 使用AAPS时，与泵交互的主要方式是通过手机。 在常规使用场景下，通常仅需在更换储药器时使用泵菜单。 这与OpenAPS的使用方式截然不同——OpenAPS通常需要通过快速大剂量按钮来输送至少部分药量。 若通过泵手动输送大剂量时，AAPS若同时尝试输送药量可能导致冲突。 系统设有检查机制来预防此类问题，但仍应尽可能避免这种情况。
-### Logging
+### 日志记录
-In the event you need to troubleshoot your Medtronic pump function select the menu icon in the upper left corner of the screen, select Maintenance and Log Settings. For troubleshooting any Medtronic issues Pump, PumpComm, PumpBTComm should be checked.
+如需排查美敦力泵功能问题，请点击屏幕左上角菜单图标，选择"维护"和"日志设置"。 排查美敦力问题时，需勾选Pump(泵)、PumpComm(泵通信)、PumpBTComm(泵蓝牙通信)日志项。
-### Medtronic CGM
+### 美敦力CGM
-Medtronic CGM is currently NOT supported.
+美敦力CGM当前不受支持。
-### Manual use of pump
+### 手动操作泵
-You should avoid manually bolusing or setting TBRs on your pump. All such commands should be sent via AAPS. In the event manual commands are used there must be a delay of at least 3 minutes between them in order to reduce the risk of any issues.
+应避免在泵上手动输注大剂量或设置临时基础率。 所有此类指令均应通过AAPS发送。 若必须手动操作，每次操作间隔需至少3分钟以降低风险。
-### Timezone changes and DST (Daylight Saving Time) or Traveling with Medtronic Pump and AAPS
+### 时区变更、夏令时(DST)及携带美敦力泵与AAPS出行注意事项
-AAPS will automatically detect Timezone changes and will update the Pump's time when your phone switches to the new time.
+AAPS会自动检测时区变更，并在手机切换至新时间时更新泵的时间。
-Travelling east means you are going to be adding hours to the current time (ex. from GMT+0 to GMT+2) will not result in any issues as there will be no overlap (e.g. it won't be possible to have the same hour twice). Travelling west however can result in issues as you are effectively going back in time which can result in incorrect IOB data.
+向东旅行意味着您将在当前时间上增加小时数（例如 从GMT+0到GMT+2）不会产生任何问题，因为时间不会重叠（例如同一小时不会重复出现）。 但向西旅行可能导致问题，因为时间实际上会倒流，从而造成IOB数据错误。
-The issues seen when travelling west are known to the developers and work on a possible solution is ongoing. See https://github.com/andyrozman/RileyLinkAAPS/issues/145 for more detail. For now, please be aware that this issue may occur and carefully monitor when changing time zones.
+开发人员已知晓向西旅行时出现的问题，目前正在研究可能的解决方案。 详情参见 https://github.com/andyrozman/RileyLinkAAPS/issues/145。 目前请注意该问题可能发生，变更时区时需谨慎监测。
-### Is a GNARL a fully compatible Rileylink compatible device?
+### GNARL是否完全兼容Rileylink设备？
-The GNARL code fully supports all of the functions used by the Medtronic driver in AAPS which means it is fully compatible. It is important to note that this will require additional work as you will have to source compatible hardware and then load the GNARL code on to the device.
+GNARL代码完全支持AAPS中美敦力驱动器的所有功能，这意味着它是完全兼容的。 需注意：这需要额外操作，您必须获取兼容硬件并将GNARL代码加载至设备。
-**Note from author:** Please note that the GNARL software is still experimental and lightly tested, and should not be considered as safe to use as a RileyLink.
+**作者说明：** 请注意GNARL软件仍处于实验阶段且测试有限，其安全性暂无法与RileyLink相提并论。
(MedtronicPump-faq)=
-## FAQ
+## 常见问题解答
(MedtronicPump-what-to-do-if-i-loose-connection-to-rileylink-and-or-pump)=
-### What to do if I loose connection to RileyLink and/or pump?
+### 若与RileyLink和/或泵的连接中断该如何处理？
-There are a number of options to try and resolve connectivity issues.
+可尝试以下多种方法解决连接问题。
-- Use the "Wake Up and Tune" button in the ACT tab as detailed above.
-- Disable Bluetooth on your phone, wait 10 seconds and then enable it again. This will force the Rileylink device to reconnect to the phone.
-- Reset the Rileylink device. You must then use the "Reset Rileylink Config" button in the ACT tab.
-- Other users have found the following steps to be effective in restoring connectivity when other methods have not:
- 1. Restart the phone
- 2. *While* the phone is restarting restart the Rileylink device
- 3. Open AAPS and allow the connection to restore
+- 按照前文说明，使用ACT标签页中的"唤醒并调谐"按钮。
+- 禁用手机蓝牙10秒后重新启用。 这将强制Rileylink设备重新连接手机。
+- 重置Rileylink设备。 随后必须点击ACT标签页中的"重置Rileylink配置"按钮。
+- 其他用户发现，当常规方法无效时，以下步骤可有效恢复连接：
+ 1. 重新启动手机
+ 2. *在*手机重启期间同时重启Rileylink设备
+ 3. 打开AAPS并等待连接恢复
-### How to determine what Frequency my pump uses
+### 如何确定我的泵使用什么频率
-On the back of the pump you will find a line detailing your model number along with a special 3 letter code. The first two letters determine the frequency type and the last one determines color. Here are possible values for Frequency:
+泵背面标有型号及特殊三字母代码。 前两个字母决定频率类型，最后一个字母决定颜色。 以下是频率的可能取值：
-- NA - North America (in frequency selection you need to select "US & Canada (916 MHz)")
-- CA - Canada (in frequency selection you need to select "US & Canada (916 MHz)")
-- WW - Worldwide (in frequency selection you need to select "Worldwide (868 Mhz)")
\ No newline at end of file
+- NA - 北美地区（频率选择中需选"美国及加拿大(916 MHz)"）
+- CA - 加拿大（频率选择中需选"美国及加拿大(916 MHz)"）
+- WW - 全球范围（频率选择中需选"全球(868 MHz)"）
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md
index 639c5aa4e7dc..0ae1968d1aa5 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md
@@ -2,389 +2,389 @@
orphan: true
- - -
-# Medtrum Nano / 300U
+# 移宇（Medtrum）Nano/300U胰岛素泵
-These instructions are for configuring the Medtrum insulin pump.
+本说明用于配置移宇（Medtrum）胰岛素泵。
-This software is part of a DIY artificial pancreas solution and is not a product but requires YOU to read, learn, and understand the system, including how to use it. 只有你才能对自己的行为负责。
+本软件属于人工胰腺系统的DIY解决方案，并非商业产品，需要用户自行研习并全面掌握系统操作原理。 使用后果由您自行承担。
```{contents} Table of contents
:depth: 1
:local: true
```
-## Pump capabilities with AAPS
-* All loop functionality supported (SMB, TBR etc)
-* Automatic DST and timezone handling
-* Extended bolus is not supported by AAPS driver
+## AAPS支持的胰岛素泵功能
+* 支持所有闭环功能（包括SMB、TBR等）
+* 自动处理夏令时（DST）及时区
+* AAPS驱动程序不支持扩展大剂量功能
-## Hardware and Software Requirements
-* **Compatible Medtrum pumpbase and reservoir patches**
- - Currently supported:
- - Medtrum TouchCare Nano with pumpbase refs: **MD0201** and **MD8201**.
- - Medtrum TouchCare 300U with pumpbase ref: **MD8301**.
- - If you have an unsupported model and are willing to donate hardware or assist with testing, please contact us via discord [here](https://discordapp.com/channels/629952586895851530/1076120802476441641).
-* **Version 3.2.0.0 or newer of AAPS built and installed** using the [Build APK](../SettingUpAaps/BuildingAaps.md) instructions.
-* **Compatible Android phone** with a BLE Bluetooth connection
- - See AAPS [Release Notes](../Maintenance/ReleaseNotes.md)
-* [**Continuous Glucose Monitor (CGM)**](../Getting-Started/CompatiblesCgms.md)
+## 硬件和软件要求
+* **兼容的移宇(Medtrum)泵底板与储药器贴片**
+ - 当前支持：
+ - 移宇TouchCare Nano胰岛素泵（配套泵基座型号：**MD0201**及**MD8201**）
+ - 移宇TouchCare 300U胰岛素泵（配套泵基座型号：**MD8301**）
+ - 若您持有不受支持的型号，并愿意捐赠硬件或协助测试，请通过Discord[此处](https://discordapp.com/channels/629952586895851530/1076120802476441641)联系我们。
+* **已构建并安装AAPS 3.2.0.0或更高版本**，请参照[构建APK](../SettingUpAaps/BuildingAaps.md)说明进行操作。
+* **兼容的Android手机**（需具备BLE蓝牙连接功能）
+ - 请参阅AAPS[版本说明](../Maintenance/ReleaseNotes.md)
+* [**持续血糖监测仪（CGM）**](../Getting-Started/CompatiblesCgms.md)
-## Before you begin
+## 在您开始前
-**SAFETY FIRST** Do not attempt this process in an environment where you cannot recover from an error (extra patches, insulin, and pump control devices are must-haves).
+**安全第一** 请勿在无法从错误中恢复的环境中进行此操作（必须备有额外的贴片、胰岛素及泵控制设备）。
-**The PDM and Medtrum App will not work with a patch that is activated by AAPS.** Previously you may have used your PDM or Medtrum app to send commands to your pump. For security reasons you can only use the activated patch with the device or app that was used to activate it.
+**经AAPS激活的贴片将无法与PDM及移宇应用程序兼容。** 此前您可能使用过PDM或移宇应用程序向胰岛素泵发送指令。 出于安全考虑，已激活的贴片仅限用于激活时使用的设备或应用程序。
-*This does NOT mean that you should throw away your PDM. It is recommended to keep it somewhere safe as a backup in case of emergencies, for instance if your phone gets lost or AAPS is not working correctly.*
+*这并不意味着您应当丢弃您的PDM设备。 建议将其妥善保管作为应急备用，例如当手机遗失或AAPS运行异常时。*
-**Your pump will not stop delivering insulin when it is not connected to AAPS** Default basal rates are programmed on the pump as defined in the current active profile. As long as AAPS is operational, it will send temporary basal rate commands that run for a maximum of 120 minutes. If for some reason the pump does not receive any new commands (for instance because communication was lost due to pump - phone distance) the pump will fall back to the default basal rate programmed on the pump once the Temporary Basal Rate ends.
+**当未连接AAPS时，您的胰岛素泵不会停止输注胰岛素** 胰岛素泵将按照当前使用方案中设定的基础率持续输注。 只要AAPS处于运行状态，就会发送最长持续120分钟的临时基础率指令。 若因某些原因（如因胰岛素泵与手机距离过远导致通信中断）泵体未能接收到新指令，临时基础率结束后将自动恢复为泵体预设的基础率。
-**30 min Basal Rate Profiles are NOT supported in AAPS.** **The AAPS Profile does not support a 30 minute basal rate time frame** If you are new to AAPS and are setting up your basal rate profile for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and you will need to adjust your basal rate profile to start on the hour. For example, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, this will not work. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the Medtrum pump hardware itself supports the 30 min basal rate profile increments, AAPS is not able to take them into account with its algorithms currently.
+**AAPS不支持30分钟基础率方案。****AAPS配置方案不支持30分钟基础率时间间隔。**若您初次使用AAPS并首次设置基础率方案，请注意系统不支持半点起始的基础率设置，您需要将基础率方案调整为整点起始。 例如，若您设置了09:30开始、持续2小时至11:30结束的1.1单位基础率，该设置将无法生效。 您需要将这个1.1单位的基础率时间段调整为9:00-11:00或10:00-12:00。 尽管移宇胰岛素泵硬件本身支持30分钟基础率间隔设置，但AAPS当前算法尚无法兼容此类设置。
-**0U/h profile basal rates are NOT supported in AAPS** While the Medtrum pump does support a zero basal rate, AAPS uses multiples of the profile basal rate to determine automated treatment and therefore cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate.
+**AAPS不支持0U/h基础率方案设置**。虽然移宇胰岛素泵确实支持零基础率，但AAPS需基于基础率倍数进行自动化治疗计算，因此无法兼容零基础率设置。 可通过"断开泵连接"功能，或结合停用循环/临时基础率与暂停循环/临时基础率功能，实现临时零基础率设置。
## 设置
-CAUTION: When activating a patch with AAPS you **MUST** disable all other devices that can talk to the Medtrum pumpbase. e.g. active PDM and Medtrum app. Make sure you have your pumpbase and pumpbase SN ready for activation of a new patch.
+警告：使用AAPS激活贴片时，您**必须**禁用所有其他可与移宇泵基座通信的设备。 例如：正在使用的PDM及移宇应用程序。 请确保准备好您的泵基座及泵基座序列号，以便激活新贴片。
-### Step 1: Select Medtrum pump
+### 步骤1：选择移宇胰岛素泵
-#### Option 1: New installations
+#### 方式一：全新安装
-If you are installing AAPS for the first time, the **Setup Wizard** will guide you through installing AAPS. Select “Medtrum” when you reach Pump selection.
+若您首次安装AAPS，**设置向导**将引导您完成安装流程。 当进入泵体选择界面时，请选择"移宇"。
-If in doubt you can also select “Virtual Pump” and select “Medtrum” later, after setting up AAPS (see option 2).
+如有疑问，您也可先选择"虚拟泵"，待完成AAPS设置后再选择"移宇"（参见选项2）。
-
+
-#### Option 2: The Config Builder
+#### 选项2：配置构建器
-On an existing installation you can select the **Medtrum** pump in [Config Builder > Pump](#Config-Builder-pump):
+在现有安装中，您可通过[配置生成器 > 泵](#Config-Builder-pump)选择**移宇**胰岛素泵：
-On the top-left hand corner **hamburger menu** select **Config Builder**\ ➜\ **Pump**\ ➜\ **Medtrum**\ by selecting the **Enable button** titled **Medtrum**.
+在左上角**汉堡菜单**中选择**配置生成器** ➜ **泵** ➜ **移宇**，然后点击标有**移宇**的**启用按钮**。
-Selecting the **checkbox** next to the **Settings Gear** will allow the Medtrum overview to be displayed as a tab in the AAPS interface titled **Medtrum**. Checking this box will facilitate your access to the Medtrum commands when using AAPS and is highly recommended.
+勾选**设置齿轮**旁的**复选框**，即可在AAPS界面中显示名为**移宇**的标签页概览。 勾选此选项将便于您在使用AAPS时访问移宇相关指令，强烈建议启用。
-### Step 2: Change Medtrum settings
+### 步骤2：调整移宇设置
-Enter the Medtrum settings by tapping the **Settings Gear** of the Medtrum module in the Config Builder .
+点击配置生成器中移宇模块的**设置齿轮**即可进入移宇设置界面。
-#### Serial Number:
+#### 序列号:
-Enter the serial number of your pumpbase here as noted on the pumpbase. Make sure the serial number is correct and there are no spaces added (You can either use capital or lowercase).
+请在此处输入您泵基座上标注的泵基座序列号。 请确保序列号准确无误且未添加空格（字母大小写均可）。
-NOTE: This setting can only be changed when there is no patch active.
+注意：此设置仅在无激活贴片时方可修改。
-#### Alarm settings
+#### 警报设置
-***Default: Beep.***
+***默认设置：蜂鸣提示。***
-This setting changes the way that the pump will alert you when there is a warning or error.
+此设置将改变胰岛素泵在出现警告或错误时的警报方式。
-- Beep > The patch will beep on alarms and warnings
-- Silent > The patch will not alert you on alarms and warnings
+- 蜂鸣 > 贴片将通过蜂鸣声提示警报和警告
+- 静音 > 贴片将不会通过警报声或警告声提醒您
-Note: In silent mode AAPS will still sound the alarm depending on your phone's volume settings. If you do not respond to the alarm, the patch will eventually beep.
+注意：在静音模式下，AAPS仍会根据您手机的音量设置发出警报声。 若您未响应警报，贴片最终仍会发出蜂鸣声。
-#### Notification on pump warning
+#### 胰岛素泵警告通知
-***Default: Enabled.***
+***默认状态：启用。***
-This settings changes the way AAPS will show notification on non critical pump warnings. When enabled a Notification will be shown on the phone when a pump warning occurs, including:
- - Low battery
- - Low reservoir (20 Units)
- - Patch expiration warning
+此设置将改变AAPS对非关键性泵警报的提示方式。 当启用时，手机将在出现胰岛素泵警告时显示通知，包括：
+ - 电量不足
+ - 储药量不足（20单位）
+ - 贴片有效期警告
-In either case these warnings are also shown on the Medtrum overview screen under [Active alarms](#medtrum-active-alarms).
+无论何种情况，这些警告信息都将在移宇概览屏幕的[活动警报](#medtrum-active-alarms)项下显示。
(medtrum-patch-expiration)=
-#### Patch Expiration
+#### 贴片到期警告
-***Default: Enabled.***
+***默认状态：启用。***
-This setting changes the behavior of the patch. When enabled the patch will expire after 3 days and give an audible warning if you have sound enabled. After 3 days and 8 hours the patch will stop working.
+此设置将改变贴片的工作模式。 当启用此设置时，贴片将在3天后到期，并在开启声音提示的情况下发出声音警告。 3天8小时后，贴片将停止工作。
-If this setting is disabled, the patch will not warn you and will continue running until the patch battery or reservoir runs out.
+若禁用此设置，贴片将不会发出警告，并持续运行直至贴片电池耗尽或储药槽用尽。
-#### Pump expiry warning
+#### 胰岛素泵到期警告
-***Default: 72 hours.***
+***默认值：72小时。***
-This setting changes the time of the expiration warning, when [Patch Expiration](#medtrum-patch-expiration) is enabled, AAPS will give a notification on the set hour after activation.
+此设置将修改到期警告的时间：当启用[贴片到期](#medtrum-patch-expiration)功能时，AAPS会在激活后的设定小时数发出通知。
-#### Hourly Maximum Insulin
+#### 每小时最大胰岛素剂量
-***Default: 25U.***
+***默认值：25单位。***
-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).
+此设置将修改每小时的最大胰岛素输注量。 若超过此限制，贴片将暂停输注并发出警报。 可通过概览菜单中的[重置警报](#reset-alarms)按钮来解除警报。
-Set this to a sensible value for your insulin requirements.
+请根据您的胰岛素需求设置合理数值。
-#### Daily Maximum Insulin
+#### 每日最大胰岛素剂量
-***Default: 80U.***
+***默认值：80单位。***
-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).
+此设置将修改每日最大胰岛素输注量。 若超过此限制，贴片将暂停输注并发出警报。 可通过概览菜单中的[重置警报](#reset-alarms)按钮来解除警报。
-Set this to a sensible value for your insulin requirements.
+请根据您的胰岛素需求设置合理数值。
-#### Scan on Connection error
+#### 连接错误时扫描
-***Default: Off.***
+***默认状态：关闭。***
-Located under **Advanced Settings**.
+位于**高级设置**项下。
-Only enable if you have connection problems. If enabled the driver scans for the pump again before trying to reconnect to the pump. Make sure you have Location permission set to "Always allow".
+仅在出现连接问题时启用。 若启用此功能，驱动程序将在尝试重新连接胰岛素泵前再次进行扫描。 请确保将位置权限设置为"始终允许"。
-### Step 2b: AAPS Alerts settings
+### 步骤2b：AAPS警报设置
-Go to preferences
+前往偏好设置
-#### Pump:
+#### 胰岛素泵:
-##### BT Watchdog
+##### 蓝牙看门狗
-Go to preferences and select **Pump**:
+前往偏好设置并选择**胰岛素泵**：
-
+
-##### BT Watchdog
+##### 蓝牙看门狗
-This setting will try to work around any BLE issues. It will try to reconnect to the pump when the connection is lost. It will also try to reconnect to the pump when the pump is unreachable for a certain amount of time.
+此设置将尝试解决所有蓝牙低功耗(BLE)连接问题。 当连接中断时，系统将尝试重新连接胰岛素泵。 当胰岛素泵在一定时间内无法连接时，系统也将尝试重新建立连接。
-Enable this setting if you experience frequent connection issues with your pump.
+若您的胰岛素泵频繁出现连接问题，请启用此设置。
-#### Local Alerts:
+#### 本地警报：
-Go to preferences and select **Local Alerts**:
+前往偏好设置并选择**本地警报**：
-##### Alert if pump is unreachable
+##### 若胰岛素泵无法连接则发出警报
-***Default: Enabled.***
+***默认状态：启用。***
-This setting is forced to enabled when the Medtrum driver is enabled. It will alert you when the pump is unreachable. This can happen when the pump is out of range or when the pump is not responding due to a defective patch or pumpbase, for example when water leaks between the pumpbase and the patch.
+当移宇驱动程序启用时，此设置将强制启用。 当泵无法连接时，系统将发出警报。 当泵超出连接范围，或因贴片或泵座故障导致泵无响应时（例如泵座与贴片之间发生渗漏），系统将触发此警报。
-For safety reasons this setting cannot be disabled.
+出于安全考虑，此设置不可禁用。
-##### Pump unreachable threshold [min]
+##### 泵失联阈值[分钟]
-***Default: 30 min.***
+***默认值：30分钟。***
-This setting changes the time after which AAPS will alert you when the pump is unreachable. This can happen when the pump is out of range or when the pump is not responding due to a defective patch or pumpbase, for example when water leaks between the pumpbase and the patch.
+此设置用于调整移宇胰岛素泵失联后，AAPS系统触发警报的延迟时间。 当泵超出连接范围，或因贴片或泵座故障导致泵无响应时（例如泵座与贴片之间发生渗漏），系统将触发此警报。
-This setting can be changed when using Medtrum pump but it is recommended to set it at 30 minutes for safety reasons.
+使用移宇胰岛素泵时可调整此设置，但出于安全考虑建议保持30分钟默认值。
-### Step 3: Activate patch
+### 步骤3：激活贴片
-**Before you continue:**
-- Have your Medtrum Nano pumpbase and a reservoir patch ready.
-- Make sure that AAPS is properly set up and a [profile is activated](../DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md).
-- Other devices that can talk to the Medtrum pump are disabled (PDM and Medtrum app)
+**操作前须知：**
+- 请准备好您的移宇Nano泵座和储药贴片。
+- 请确保AAPS已正确设置并激活了[配置文件](../DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md)。
+- 其他可与移宇泵通信的设备（PDM和移宇应用）已被禁用
-#### 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.
+在AAPS界面中导航至[移宇标签页](#overview)，并点击右下角的**更换贴片**按钮。
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+如果已有贴片处于激活状态，系统将提示您先停用当前贴片。 请参阅[停用贴片](#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).**
+请按照提示操作，完成新贴片的填充和激活。 请注意 - 必须严格按提示步骤操作，仅在系统提示时才能将泵底座与储药贴片连接。 **必须严格遵照激活流程提示操作，仅当完成预充程序后系统提示时，方可将泵体佩戴至身上并插入导管。**
-##### Start Activation
+##### 开始激活
-
+
-At this step, double check your serial number and make sure the pumpbase is not connected to the patch yet.
+在此步骤中，请再次核对序列号，并确保泵底座尚未与贴片连接。
-Press **Next** to continue.
+点击**下一步**继续。
-##### Fill the patch
+##### 填充贴片
-
+
-Once the patch is detected and filled with a minimum of 70Units of insulin, press **Next** will appear.
+当检测到贴片并填充至少70单位胰岛素后，将出现**下一步**按钮。
-##### Prime the patch
+##### 预充贴片
-Do not remove the safety lock and press the needle button on the patch.
+请勿移除安全锁，并按下贴片上的针头按钮。
-Press **Next** to start prime
+点击**下一步**开始预充
-Once the prime is complete, press **Next** to continue.
+预充完成后，点击**下一步**继续。
-##### Attach Patch
+##### 安装贴片
-Clean the skin, remove stickers and attach the patch to your body. Remove safety lock and press the needle button on the patch to insert the cannula.
+清洁皮肤，移除贴纸，将贴片安装到身体上。 移除安全锁并按下贴片上的针头按钮以插入导管。
-Press **Next** to activate the patch.
+点击**下一步**激活贴片。
(medtrum-activate-patch)=
-##### Activate Patch
+##### 激活贴片
-When activation is complete, the following screen will appear
+当激活完成后，将出现以下界面
-Press **OK** to return to main screen.
+点击**确定**返回主界面。
-### Deactivate patch
+### 停用贴片
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+要停用当前激活的贴片，请进入AAPS界面中的[移宇标签页](#overview)，然后点击**更换贴片**按钮。
-
+
-You will be asked to confirm that you wish to deactivate the current patch. **Please note that this action is not reversible.** When deactivation is completed, you can press **Next** to continue the process to activate a new patch. If you are not ready to activate a new patch, press **Cancel** to return to the main screen.
+系统将要求您确认是否要停用当前贴片。 **请注意此操作不可逆。** 停用完成后，可点击**下一步**继续新贴片激活流程。 若尚未准备好激活新贴片，请点击**取消**返回主界面。
-If Android APS in unable to deactivate the patch (For instance because the pumpbase has already been removed from the reservoir patch), you may press **Discard** to forget the current patch session and make it possible to activate a new patch.
+若Android APS无法停用贴片（例如因泵底座已从储药贴片移除），可点击**丢弃**以终止当前贴片会话，从而激活新贴片。
-Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+停用完成后，点击**确定**返回主界面，或点击**下一步**继续新贴片激活流程。
-### 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.
+若贴片激活流程被中断（例如因手机电量耗尽），可通过进入AAPS界面中的[移宇标签页](#overview)并点击**更换贴片**按钮来恢复激活流程。
-
+
-Press **Next** to continue the activation process. Press **Discard** to discard the current patch session and make it possible to activate a new patch.
+点击**下一步**继续激活流程。 点击**丢弃**以终止当前贴片会话，从而激活新贴片。
-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.
+驱动程序将尝试检测当前贴片激活状态。 若检测成功，系统将从当前步骤继续激活流程。
## 概览
-The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
+该概览显示移宇贴片的当前状态。 同时包含更换贴片、重置警报和刷新状态的按钮。
-### BLE Status:
+### 蓝牙状态：
-This shows the current status of the Bluetooth connection to the pumpbase.
+此处显示与泵底座的蓝牙连接当前状态。
-### Last connected:
+### 上次连接:
-This shows the last time the pump was connected to AAPS.
+此处显示泵上次连接AAPS的时间。
-### Pump state:
+### 泵状态：
-This shows the current state of the pump. For example:
- - ACTIVE : The pump is activated and running normally
- - STOPPED: The patch is not activated
+此处显示泵的当前状态。 例如：
+ - 激活：泵已激活并正常运行
+ - 停止：贴片未激活
-### Basal type:
+### 基础率类型:
-This shows the current basal type.
+此处显示当前基础率类型。
-### Basal rate:
+### 基础率：
-This shows the current basal rate.
+此处显示当前基础率。
-### Last bolus:
+### 最近一次大剂量：
-This shows the last bolus that was delivered.
+此处显示最近一次输注的大剂量。
-### Active bolus:
+### 当前大剂量：
-This shows the active bolus that is currently being delivered.
+此处显示正在输注的当前大剂量。
(medtrum-active-alarms)=
-### Active alarms:
+### 当前警报：
-This shows any active alarms that are currently active.
+此处显示当前所有激活中的警报状态。
-### Reservoir:
+### 储药器:
-This shows the current reservoir level.
+此处显示当前储药器剩余药量。
-### Battery:
+### 电池:
-This shows the current battery voltage of the patch.
+此处显示贴片当前电池电压。
-### Pump type:
+### 泵类型：
-This shows the current pump type number.
+此处显示当前泵类型编号。
-### FW version:
+### 固件版本：
-This shows the current firmware version of the patch.
+此处显示贴片当前固件版本。
-### Patch no:
+### 贴片编号：
-This shows the sequence number of the activated patch. This number is incremented every time a new patch is activated.
+此处显示已激活贴片的序列号。 该编号在每次激活新贴片时递增。
-### Patch expires:
+### 贴片有效期：
-This shows the date and time when the patch will expire.
+此处显示贴片到期日期和时间。
-### Refresh:
+### 刷新:
-This button will refresh the status of the patch.
+此按钮将刷新贴片状态。
-### Change patch:
+### 更换贴片：
-This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+此按钮将启动更换贴片流程。 详见[激活贴片](#medtrum-activate-patch)获取更多信息。
-### 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. 例如 when suspended due to a maximum daily insulin delivery alarm.
+当存在可重置的激活警报时，警报按钮将显示在概览屏幕上。 按下此按钮将重置警报，若贴片因警报暂停，将恢复胰岛素输注。 例如 当日胰岛素最大输注量警报触发暂停时。
-
+
-Press the **Reset Alarms** button to reset the alarms and resume normal operation.
+请按**重置警报**按钮以清除警报并恢复正常运行。
-## Switching phone, export/import settings
+## 切换手机，导出/导入设置
-When switching to a new phone the following steps are necessary:
-* [Export settings](../Maintenance/ExportImportSettings.md) on your old phone
-* Transfer settings from old to new phone, and import them into AAPS
+更换新手机时必须执行以下步骤：
+* 在旧手机[导出设置](../Maintenance/ExportImportSettings.md)
+* 将设置从旧手机传输至新手机，并导入至AAPS
-The imported settings file has to be of the same patch session that you are currently using, otherwise the patch will not connect.
+导入的设置文件必须与当前使用的贴片会话相同，否则贴片将无法连接。
-After a settings import the driver will sync history with the pump, this can take a while depending on the age of the settings file.
+导入设置后，驱动程序将与泵同步历史记录，根据设置文件的生成时间，此过程可能需要一定时间。
-From AAPS version 3.3.0.0 onwards, the sync progress is shown in the the home screen: 
+自AAPS 3.3.0.0版本起，主屏幕将显示同步进度：
## 故障排除
-### Connection issues
+### 连接问题
-If you are experiencing connection timeouts or other connection issues:
-- In Android application settings for AAPS: Set location permission to "Allow all the time".
+若出现连接超时或其他连接问题：
+- 在AAPS的安卓应用设置中：将位置权限设为"始终允许"。
-### 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)
+若激活流程因手机电量耗尽或系统崩溃等原因中断。 可通过进入更换贴片界面，按此处所述步骤继续激活流程：[恢复中断的激活](#resume-interrupted-activation)
-### Preventing patch faults
+### 预防贴片故障
-The patch can give a variety of errors. To prevent frequent errors:
-- Make sure the pumpbase is properly seated in the patch and no gaps are visible.
-- When filling the patch do not apply excessive force to the plunger. Do not try to fill the patch beyond the maximum that applies to your model.
+贴片可能出现多种故障。 为避免频繁出现故障：
+- 请确保泵基座正确嵌入贴片且无可见缝隙。
+- 填充贴片时请勿对推杆施加过大压力。 请勿超过您所用型号的最大填充量进行填充。
-## Where to get help
+## 获取帮助途径
-All of the development work for the Medtrum driver is done by the community on a **volunteer** basis; we ask that you to remember that fact and use the following guidelines before requesting assistance:
+移宇驱动器的所有开发工作均由社区**志愿者**完成；请您在寻求帮助前谨记这一事实并遵循以下准则：
-- **Level 0:** Read the relevant section of this documentation to ensure you understand how the functionality with which you are experiencing difficulty is supposed to work.
-- **Level 1:** If you are still encountering problems that you are not able to resolve by using this document, then please go to the *#Medtrum* channel on **Discord** by using [this invite link](https://discord.gg/4fQUWHZ4Mw).
-- **Level 2:** Search existing issues to see if your issue has already been reported at [Issues](https://github.com/nightscout/AAPS/issues) if it exists, please confirm/comment/add information on your problem. If not, please create a [new issue](https://github.com/nightscout/AndroidAPS/issues) and attach [your log files](../GettingHelp/AccessingLogFiles.md).
-- **Be patient - most of the members of our community consist of good-natured volunteers, and solving issues often requires time and patience from both users and developers.**
\ No newline at end of file
+- **第0级：**查阅本文档相关章节，确保您已理解遇到问题的功能模块的正确运作方式。
+- **第一级：**若您遇到的问题无法通过本文档解决，请通过[此邀请链接](https://discord.gg/4fQUWHZ4Mw)加入**Discord**平台的*#Medtrum*频道寻求帮助。
+- **第二级：**请在[问题追踪](https://github.com/nightscout/AAPS/issues)中搜索现有问题，查看您的问题是否已被上报。若存在相关记录，请确认/评论/补充您的问题信息。 如果没有，请创建一个[新问题](https://github.com/nightscout/AndroidAPS/issues)并附上[您的日志文件](../GettingHelp/AccessingLogFiles.md)。
+- **请保持耐心——我们社区成员多为热心志愿者，问题的解决往往需要用户和开发者双方投入时间与耐心。**
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md
index 2b2599da3905..f7c26583a642 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md
@@ -4,230 +4,230 @@ orphan: true
# Omnipod DASH
-These instructions are for configuring the **Omnipod DASH** generation pump **(NOT Omnipod Eros)**, available as part of **AAPS** version 3.0.
+本说明适用于配置**Omnipod DASH**代泵**(非Omnipod Eros)**，该功能作为**AAPS** 3.0版本的一部分提供。
-## Omnipod DASH specifications
+## Omnipod DASH 规格说明
-These are the specifications of the **Omnipod DASH** ('DASH') and what differentiates it from the **Omnipod EROS** ('EROS'):
+以下是**Omnipod DASH**（简称"DASH"）的规格说明及其与**Omnipod EROS**（简称"EROS"）的主要区别：
-* The DASH pods are identified by a blue needle cap (EROS has a clear needle cap). The pods are otherwise identical in terms of physical dimensions.
-* DASH does not require a BLE link/bridge device (NO RileyLink, OrangeLink, or EmaLink needed).
-* The DASH's bluetooth connection is used only when needed, and connects to send command and disconnects right after!
-* No more "no connection to link device / pod" errors with DASH.
-* **AAPS** will wait for pod's accessibility to send commands.
-* On pod activation, **AAPS** will find and connect to a new DASH pod.
-* Expected range: 5-10 meters (YMMV).
+* DASH 储药器采用蓝色针头帽标识（EROS 使用透明针头帽）。 除标识外，两种储药器的物理尺寸完全一致。
+* DASH 无需蓝牙连接/桥接设备（不需要 RileyLink、OrangeLink 或 EmaLink）。
+* DASH 的蓝牙连接仅在需要时启用，完成指令传输后立即断开！
+* DASH 彻底消除了"无法连接桥接设备/储药器"的报错。
+* **AAPS** 将等待储药器可连接状态时发送指令。
+* 在储药器激活时，**AAPS** 将自动搜寻并连接新的 DASH 储药器。
+* 预期连接范围：5-10米（实际效果可能因环境而异）。
-WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue.
+警告：目前收到关于以下组合的蓝牙连接问题报告：**AAPS** / DASH / Android 15。 除非用户已查阅以下[**列表**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true)并确认其手机不在已知问题报告范围内，否则不应将**AAPS**与Android 15和DASH组合使用。 **AAPS**目前正在努力解决该问题。
-## Hardware/Software Requirements
+## 硬件/软件要求
-* DASH is identified by blue needle cap.
+* DASH 以蓝色针头帽为标识。
-* **Compatible Android phone** with a BLE Bluetooth connection
- Be aware that **AAPS** Omnipod Dash driver connects with the DASH via Bluetooth every time it sends a command, and it disconnects right after. The Bluetooth connection can be disturbed by other bluetooth devices linked to the phone that is running **AAPS**, like earbuds etc... (which might cause, in rare occasions, connection issue or pod errors/loss on activation or afterwards in some phone models), or be disturbed by it.
- - **Version 3.0 or newer of AAPS built and installed** using the [**Build APK**](../SettingUpAaps/BuildingAaps.md) instructions.
-* [**Continuous Glucose Monitor (CGM)**](../Getting-Started/CompatiblesCgms.md)
+* **兼容的安卓手机**需具备BLE蓝牙连接功能
+ 请注意，**AAPS**的Omnipod Dash驱动每次发送指令时都会通过蓝牙与DASH连接，并在完成后立即断开。 蓝牙连接可能会受到与运行**AAPS**的手机相连的其他蓝牙设备（如耳机等）的干扰（在极少数情况下，某些手机型号可能会出现连接问题或储药器激活时/激活后的错误/丢失），也可能干扰其他设备。
+ - **使用[**构建APK**](../SettingUpAaps/BuildingAaps.md)说明构建并安装AAPS 3.0或更高版本**。
+* [**持续血糖监测仪（CGM）**](../Getting-Started/CompatiblesCgms.md)
-The instructions below explain how to activate a new pod session. Wait to close to expiry of a current pod session before trying to connect **AAPS** with a new pod. Once a pod is is cancelled it cannot reused and the disconnection will be final.
+以下说明将指导您如何激活新的储药器会话。 请等待当前储药器会话接近到期时，再尝试将**AAPS**与新储药器连接。 储药器一旦被取消便无法重复使用，断开连接后将永久失效。
-## Before You Begin
+## 开始前的准备工作
-**SAFETY FIRST** - you should not try to connect **AAPS** to a pod for the first time without having access to extra pods, insulin, and phone devices are a must have.
+**安全第一** - 首次尝试将**AAPS**连接至储药器时，必须确保备有额外的储药器、胰岛素及通讯设备。
-**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM.
+**当AAPS的Dash驱动激活您的储药器后，Omnipod Dash PDM将不再需要。**此前用户可能需要通过PDM向DASH发送指令。 DASH 仅允许单一设备与其通信并发送指令。 成功激活储药器的设备将成为此后唯一获准与其通信的设备。 这意味着当您通过**AAPS**用安卓手机激活DASH后，**该储药器将无法再与您的PDM配合使用**。 您安卓手机中的**AAPS** Dash驱动现已作为您的PDM使用。
-*This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.*
+*这并不意味着您应该丢弃PDM，建议将其保留作为备用设备以应对紧急情况，例如手机丢失或AAPS运行异常时使用。*
-**Your pod will not stop delivering insulin when it is not connected to AAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod - phone distance) the pod will automatically fall back to default basal rates.
+**储药器在未连接AAPS时不会停止胰岛素输注**。 储药器激活时会根据当前生效的**配置文件**预设基础率参数。 只要**AAPS**正常运行，它就会发送最长持续120分钟的基础率指令。 当储药器因某些原因（如因储药器与手机距离过远导致通信中断）未能接收到新指令时，将自动切换至预设基础率模式运行。
-**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this im **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does support this feature.
+**AAPS配置文件不支持30分钟基础率时间框架。** 如果您是**AAPS**的新用户并首次设置基础率**配置文件**，请注意不支持以半小时为单位的基础率设置，仅支持整点设置。 例如，若您设有从09:30开始、持续2小时至11:30结束的1.1单位基础率，则无法在**AAPS**中完全复制该设置。 您需要将这个1.1单位的基础率时间段调整为9:00-11:00或10:00-12:00。 虽然DASH硬件本身支持30分钟基础率**配置文件**增量设置，但**AAPS**目前并不支持此功能。
-**0U/h profile basal rates are NOT supported in AAPS** While the DASH does support a zero basal rate, since **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. The lowest basal rate allowed in **AAPS** is 0.05U/h.
+**AAPS不支持0U/h的基础率配置.** 虽然DASH硬件支持零基础率设置，但由于**AAPS**依赖用户**配置文件**基础率的倍数进行自动治疗决策，系统无法在零基础率状态下运行。 可通过"断开泵连接"功能，或结合停用循环/临时基础率与暂停循环/临时基础率功能，实现临时零基础率设置。 **AAPS**允许的最低基础率为0.05单位/小时。
-## Selecting Dash in AAPS
+## 在AAPS中选择Dash
-There are **two ways**:
+有两种方式：
-### Option 1: New installations
+### 方式一：全新安装
-When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**. Select “DASH” when you reach Pump selection.
+首次安装**AAPS**时，**设置向导**将引导新用户了解**AAPS**的关键功能和安装要求。 当进入泵选择环节时，请选择“DASH”。
-When in doubt you can also select “Virtual Pump” and select “DASH” later, after setting up **AAPS** (see option 2).
+若不确定，您也可先选择"虚拟泵"，待**AAPS**设置完成后再切换至"DASH"（参见选项2）。
-### Option 2: The Config Builder
+### 选项2：配置构建器
-On an existing installation you can select the **DASH** pump from the Config builder:
+在现有安装中，您可以通过配置构建器选择**DASH**泵：
-On the top-left hand corner **hamburger menu** select **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**.
+点击左上角**汉堡菜单**，依次选择**配置构建器(1)** ➜ **胰岛素泵** ➜ **Dash** ➜ 通过选中**Dash(2)**单选按钮进入**设置齿轮图标(3)**。
-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**.
+勾选**设置齿轮图标(3)**旁的**复选框(4)**后，DASH菜单将作为标签页显示在**AAPS**界面中，标题为**DASH**。 勾选此选项后，您在使用**AAPS**时将能更便捷地调用DASH指令功能。
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**注意：** 您可在本文档的DASH设置章节找到更快捷访问[**Dash设置**](#dash-settings)的方法。
-### Verification of Omnipod Driver Selection
+### Omnipod驱动选择验证
-To verify that you have selected the DASH in **AAPS**, if you have checked the box (4), **swipe to the left** from the **Overview** tab, where you will now see a **DASH** tab on **AAPS**. If this box is left unchecked, you’ll find the DASH tab in the hamburger menu upper left.
+要确认您已在**AAPS**中选择了DASH，若您已勾选复选框(4)，从**总览**标签页**向左滑动**，即可在**AAPS**界面中看到新增的**DASH**标签页。 若未勾选此选项，您仍可在左上角汉堡菜单中找到DASH标签页。
-## Dash Configuration
+## Dash配置
-Please **swipe left** to the **DASH** tab where you will be able to manage all pod functions (some of these functions are not enabled or visible without an active pod session):
+请**向左滑动**至**DASH**标签页，您将在此管理所有储药器功能（部分功能需在储药器激活会话中才会启用或显示）：
- 'Refresh' pod connectivity and status, be able to silence pod alarms when the pod beeps
+ "刷新"（刷新储药器连接状态，并可在储药器发出警报时进行消音操作）
- 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+ "储药器管理"（激活、停用、测试蜂鸣音、查看使用记录）
### 激活Pod
-1. Navigate to the **DASH** tab and click on the **POD MGMT (1)** button, and then click on **Activate Pod (2)**.
+1. 请进入**DASH**标签页，点击**储药器管理(1)**按钮，然后选择**激活储药器(2)**。
-2. The **Fill Pod** screen is displayed. Fill a new pod with at least 80 units of insulin and listen for two beeps indicating that the pod is ready to be primed. When calculating the total amount of insulin you need for 3 days, please take into account that priming the pod will use about 3-10 units.
+2. 此时将显示**填充储药器**界面。 请在新储药器中装入至少80单位胰岛素，听到两声提示音后表明储药器已准备好进行初始化。 在计算3天所需胰岛素总量时，请注意储药器初始化过程将消耗约3-10单位胰岛素。
 
-Ensure that the new pod and the phone running **AAPS** are within close proximity of each other and click the **Next** button.
+确保新储药器与运行**AAPS**的手机保持近距离，然后点击**下一步**按钮。
-**NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. Click on the **Retry** button. In most situations activation will continue successfully.
+**注意**：若弹出错误提示_"未找到可用的待激活储药器"_（这种情况可能发生），请勿惊慌。 点击**重试**按钮。 在大多数情况下，激活程序将能继续顺利完成。
-3. On the **Initialize Pod** screen, the pod will begin priming (you will hear a click followed by a series of ticking sounds as the pod primes itself). A green checkmark will be shown upon successful priming, and the **Next** button will become enabled. Click on the **Next** button to complete the pod priming initialization and display the **Attach Pod** screen.
+3. 在**初始化储药器**界面，储药器将开始自检（您会听到"咔嗒"一声，随后是一连串滴答声，表明储药器正在进行自检程序）。 自检成功后会出现绿色勾选标记，此时**下一步**按钮将变为可点击状态。 点击**下一步**按钮完成储药器初始化，随后将显示**佩戴储药器**界面。
 
-4. Next, prepare the infusion site ready to receive the new pod. Wash hands to avoid any risk of infection. Clean the infusion site by either using soap and water or an alcohol wipe to disinfect and let the skin air dry completely before proceeding. Remove the pod's blue plastic needle cap. If you see something that sticks out of the pod or unusual, cancel the process and start with a new pod. If everything looks OK, proceed to take off the white paper backing from the adhesive and apply the pod to the selected site on your body. When finished, click on the **Next** button.
+4. 接下来，请准备好输注部位以佩戴新储药器。 洗手消毒以避免感染风险。 使用肥皂水或酒精棉片清洁输注部位进行消毒，待皮肤完全晾干后再继续操作。 移除储药器的蓝色塑料针头保护帽。 如发现储药器有异常突出物或异样，请中止流程并更换新储药器。 确认无误后，撕下白色背胶纸，将储药器贴敷至选定的身体部位。 操作完成后，点击**下一步**按钮。
-5. The **Attach Pod** dialog box will now appear. **click on the OK button ONLY if you are ready to deploy the cannula**.
+5. 此时将弹出**佩戴储药器**对话框。 **仅在您准备好部署导管时点击确定按钮**。
-6. After pressing **OK**, it may take some time before the DASH responds and inserts the cannula (1-2 minutes maximum). Be patient.
+6. 点击**确定**后，DASH可能需要一些时间才能响应并插入导管（最长等待1-2分钟）。 请耐心等待。
- *NOTE: Before the cannula is inserted, it is good practice to pinch the skin near the cannula insertion point. This ensures a smooth insertion of the needle and will decrease your chances of developing occlusions.*
+ *注意：在插入导管前，建议捏起导管插入点附近的皮肤。 这能确保针头顺利插入，并降低导管堵塞的发生概率。*
 
-7. A green checkmark appears, and the **Next** button becomes enabled upon successful cannula insertion. Click on the **Next** button.
+7. 导管成功插入后会出现绿色勾选标记，**下一步**按钮将变为可点击状态。 点击**下一步**按钮。
-9. The **Pod activated** screen is displayed. Click on the green **Finished** button. Congratulations! You have now started a new pod session.
+9. 此时将显示**储药器已激活**界面。 点击绿色**完成**按钮。 恭喜！ 您已成功开启新储药器使用周期。
-10. The **Pod management** menu screen should now display the **Activate Pod (1)** button *disabled* and the **Deactivate Pod (2)** button *enabled*. This is because a pod is now active and you cannot activate an additional pod without deactivating the currently active pod first.
+10. 此时**储药器管理**菜单界面应显示：**激活储药器(1)**按钮*不可用*，而**停用储药器(2)**按钮*可用*。 这是因为当前已有储药器处于激活状态，必须首先停用当前储药器才能激活新储药器。
- 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.
+ 点击手机返回键回到**DASH**标签页，该界面现在将显示当前使用中储药器的信息，包括基础率设定值、储药器剩余量、已输注胰岛素量、储药器报错及警报等内容。
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ 有关显示信息的更多详情，请参阅本文档[**DASH标签页**](#dash-tab)部分。
-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).
+建议在激活储药器后导出设置。 应在每次更换储药器时导出设置，并每月将导出文件备份至云存储。 参见[**导出设置文档**](../Maintenance/ExportImportSettings.md)。
(OmnipodDASH-deactivate-pod)=
### 停用Pod
-Under normal circumstances, the expected lifetime of a pod is three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of pod usage.
+正常情况下，储药器标准使用周期为3天（72小时），在触发过期警告后仍可继续使用8小时，总使用时长可达80小时。
-To deactivate a pod (either from expiration or from a pod failure):
+要停用储药器（无论是因到期还是故障）：
-1. Go to the **DASH** tab, click on the **POD MGMT (1)** button, on the **Pod management** screen click on the **Deactivate Pod (2)** button.
+1. 进入**DASH**标签页，点击**储药器管理(1)**按钮，在**储药器管理**界面点击**停用储药器(2)**按钮。
-2. On the **Deactivate Pod** screen, click on the **Next** button to begin the process of deactivating the pod. You will receive a confirmation beep from the pod that deactivation was successful.
+2. 在**停用储药器**界面，点击**下一步**按钮开始停用流程。 储药器将发出确认提示音，表示停用成功。
-3. A green checkmark will appear upon successful deactivation. Click on the **Next** button to display the pod deactivated screen. You may now remove your pod as the active session has been deactivated.
+3. 成功停用后将显示绿色勾选标记。 点击**下一步**按钮显示储药器已停用界面。 当前使用周期已终止，您现在可以移除储药器。
-4. Click on the green button to return to the **Pod Management** screen.
+4. 点击绿色按钮返回**储药器管理**界面。
-5. You are now on the **Pod Management** menu; press the back button on your phone to return to the **DASH** tab. Verify that the **Pod status:** field displays a **No active Pod** message.
+5. 您现在处于**储药器管理**菜单界面，按手机返回键可回到**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.
+**注意**：在执行**配置文件切换**时，DASH必须先暂停输注才能设置新的基础**配置文件**，因为输注功能可能被暂停。 详情请参阅故障排除章节中的[**输注暂停**](#delivery-suspended)部分。
-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**.
+此指令用于命令当前暂停中的储药器恢复胰岛素输注。 指令成功执行后，系统将根据当前激活的基础**配置文件**，按当前时间对应的基础率恢复胰岛素正常输注。 储药器将重新接受大剂量注射、**临时基础率**和**超微大剂量**指令。
-1. Go to the **DASH** tab and ensure the **Pod status (1)** field displays **SUSPENDED**, then press the **RESUME DELIVERY (2)** button to start the process to instruct the current pod to resume normal insulin delivery. A message **RESUME DELIVERY** will display in the **Pod Status (3)** field.
+1. 请进入**DASH**标签页，确认**储药器状态(1)**字段显示为**已暂停**，然后点击**恢复输注(2)**按钮启动流程，指示当前储药器恢复正常胰岛素输注。 **恢复输注**信息将显示在**储药器状态(3)**字段中。
 
-2. When the Resume delivery command is successful, a confirmation dialog will display the message **Insulin delivery has been resumed**. Click **OK** to confirm and proceed.
+2. 当恢复输注指令执行成功时，确认对话框将显示**胰岛素输注已恢复**的信息。 点击**确定**进行确认并继续操作。
-3. The **DASH** tab will update the **Pod status (1)** field to display **RUNNING,** and the **Resume Delivery** button will no longer be displayed
+3. **DASH**标签页将更新**储药器状态(1)**字段，显示为**运行中**，且**恢复输注**按钮不再显示。
-### Silencing Pod Alerts
+### 静音储药器警报
-*NOTE - The SILENCE ALERTS button is only available on the **DASH** tab when the pod expiration or low reservoir alert has been triggered. If the SILENCE ALERTS button is not visible and you hear beep sounds from the pod, try to 'Refresh pod status'.*
+*注意 - 仅当触发储药器过期或低药量警报时，**DASH**标签页才会显示静音警报按钮。 若未显示静音警报按钮但储药器发出提示音，请尝试"刷新储药器状态"。*
-The process below will show you how to acknowledge and dismiss pod beeps when the active pod time reaches the warning time limit before the pod expiration of 72 hours (3 days). This warning time limit is defined in the **Hours before shutdown** Dash alerts setting. The maximum life of a pod is 80 hours (3 days 8 hours), however Insulet recommends not exceeding the 72 hours (3 days) limit.
+以下流程将说明当储药器使用时间接近72小时（3天）有效期前的警告时限时，如何确认并消除储药器提示音。 该警告时限由**关机前小时数**的Dash警报设置定义。 储药器最长使用时限为80小时（3天8小时），但Insulet建议不要超过72小时（3天）的标准周期。
-1. When the defined **Hours before shutdown** warning time limit is reached, the pod will issue warning beeps to inform you that it is approaching its expiration time and pod change will be required soon. You can verify this on the **DASH** tab, the **Pod expires: (1)** field will show the exact time the pod will expire (72 hours after activation), and the text will turn **red** after this time has passed. Under the **Active Pod alerts (2)** field the status message **Pod will expire soon** is displayed. This also will trigger displaying the **SILENCE ALERTS (3)** button.
+1. 当达到设定的**关机前小时数**警告时限时，储药器将发出提示音，提醒您其即将到期，需要尽快更换储药器。 您可在**DASH**标签页进行确认：**储药器到期时间：(1)**字段会显示储药器失效的具体时间（激活后72小时），超过此时限后该文本将变为**红色**。 在**使用中储药器警报(2)**字段下会显示状态信息**储药器即将到期**。 同时会触发显示**静音警报(3)**按钮。
-2. Go to the **DASH** tab and press the **SILENCE ALERTS (2)** button . **AAPS** sends the command to the pod to deactivate the pod expiration warning beeps and updates the **Pod status (1)** field with **ACKNOWLEDGE ALERTS**.
+2. 请进入**DASH**标签页并点击**静音警报(2)**按钮。 **AAPS**向储药器发送指令以停用到期警告提示音，并将**储药器状态(1)**字段更新为**已确认警报**。
-3. Upon **successful deactivation** of the alerts, **2 beeps** will be issued by the active pod and a confirmation dialog will display the message **Activate alerts have been Silenced**. Click the **OK** button to confirm and dismiss the dialog.
+3. 当警报**成功停用**后，使用中的储药器会发出**2声提示音**，同时确认对话框将显示**警报已静音**的信息。 点击**确定**按钮确认并关闭对话框。
-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.
+4. 请进入**DASH**标签页。 在**使用中储药器警报**字段下，警告信息不再显示，且使用中的储药器将不再发出到期警告提示音。
(OmnipodDASH-view-pod-history)=
-### View Pod History
+### 查看 Pod 历史
-This section explains how to review your active pod history and filter by different action categories. The pod history tool allows you to view the actions and results committed to your currently active pod during its three days (72 - 80 hours) life.
+本节说明如何查看使用中储药器的历史记录，并按不同操作类别进行筛选。 储药器历史工具可让您查看当前使用中储药器在其3天（72-80小时）使用周期内执行的操作及结果记录。
-This feature is helpful in verifying boluses, TBRs and basal commands that were sent to the pod. The remaining categories are useful for troubleshooting issues and determining the order of events that occurred leading up to a failure.
+此功能有助于核验已发送至储药器的大剂量注射、临时基础率和基础率指令。 其余分类有助于故障排除，并确定导致故障发生的事件顺序。
-*NOTE:* **Only the last command can be uncertain**. New commands *will not be sent* until the **last 'uncertain' command becomes 'confirmed' or 'denied'**. The way to 'fix' uncertain commands is to **'refresh pod status'**.
+*注意：* **仅最后一条指令可能显示不确定状态**。 新指令*将不会被发送*，直到**最后一条"不确定"指令变为"已确认"或"已拒绝"**。 解决不确定指令的方法是执行**'刷新储药器状态'**操作。
-1. Go to the **DASH** tab and press the **POD MGMT (1)** button to access the **Pod Management** menu and then press the **Pod history (2)** button to access the pod history screen.
+1. 请进入**DASH**标签页，点击**储药器管理(1)**按钮进入**储药器管理**菜单，然后点击**储药器历史(2)**按钮访问历史记录界面。
@@ -237,259 +237,259 @@ This feature is helpful in verifying boluses, TBRs and basal commands that were
-2. On the **Pod history** screen, the default category of **All (1)** is displayed, showing the **Date and Time (2)** of all pod **Actions (3)** and **Results (4)** in reverse chronological order. Use your phone’s **back button 2 times** to return to the **DASH** tab in the main **AAPS** interface.
+2. 在**储药器历史**界面，默认显示**全部(1)**类别，按时间倒序排列所有储药器**操作(3)**及其**结果(4)**的**日期和时间(2)**。 按手机**返回键2次**可返回主**AAPS**界面的**DASH**标签页。
 
(OmnipodDASH-dash-tab)=
-## DASH Tab
+## DASH标签页
-Below is an explanation of the layout and meaning of the icons and status fields on the **DASH** tab in the main AAPS interface.
+以下说明主AAPS界面中**DASH**标签页的布局及图标与状态字段的含义。
-*NOTE: If any message in the **DASH** tab status fields report (uncertain), then you will need to press the Refresh button to clear it and refresh the pod status.*
+*注意：若**DASH**标签页状态字段中任何信息显示为（不确定），则需点击刷新按钮以清除该状态并更新储药器状态。*
-### Fields
+### 字段
-* **Bluetooth Address:** Displays the current bluetooth address of the connected Pod.
-* **Bluetooth Status:** Displays the current connection status.
-* **Sequence Number:** Displays the sequence number of the active POD.
-* **Firmware Version:** Displays the firmware version for the active connection.
-* **Time on Pod:** Displays the current time on the Pod.
-* **Pod expires:** Displays the date and time when the Pod will expire.
-* **Pod status:** Displays the Pod status.
-* **Last connection:** Displays time of last communication with the Pod.
+* **蓝牙地址：**显示当前连接的储药器的蓝牙地址。
+* **蓝牙状态：**显示当前连接状态。
+* **序列号：**显示当前使用中储药器的序列号。
+* **固件版本：**显示当前连接设备的固件版本号。
+* **储药器时间：**显示储药器当前时间。
+* **储药器到期时间：**显示储药器失效的日期和时间。
+* **储药器状态：**显示储药器当前状态。
+* **最后连接时间：**显示最近一次与储药器通信的时间。
- - *Moments ago* - less than 20 seconds ago.
- - *Less than a minute ago* - more than 20 seconds but less than 60 seconds ago.
- - *1 minute ago* - more than 60 seconds but less than 120 seconds (2 min)
- - *XX minutes ago* - more than 2 minutes ago as defined by the value of XX
+ - *刚刚* - 指20秒内的时间。
+ - *不到一分钟前* - 超过20秒但不足60秒。
+ - *1分钟前* - 超过60秒但不足120秒（2分钟）
+ - *XX分钟前* - 超过2分钟，具体时间由XX值确定
-* **Last bolus:** Displays the amount of the last bolus sent to the active pod and how long ago it was issued in parenthesis.
-* **Base Basal rate:** Displays the basal rate programmed for the current time from the basal rate profile.
-* **Temp basal rate:** Displays the currently running Temporary Basal Rate in the following format
+* **最近一次大剂量：**显示最近发送给使用中储药器的大剂量注射量，括号内为注射发生的时间。
+* **基础基础率：**显示当前时间根据基础率配置文件设定的基础输注速率。
+* **临时基础率：**以下列格式显示当前运行的临时基础率：
- - {Units per hour} @{TBR start time} ({minutes run}/{total minutes TBR will be run})
- - *Example:* 0.00U/h @18:25 ( 90/120 minutes)
+ - {单位/小时} @{临时基础率开始时间} （{已运行分钟数}/{临时基础率总运行分钟数}）
+ - *示例：* 0.00U/h @18:25 (90/120分钟)
-* **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.
-* **Active pod alerts:** Reserved for currently running alerts on the active pod.
+* **储药量：**当储药器剩余药量超过50单位时，显示"50+单位剩余"。 低于50单位时，将显示精确剩余药量。
+* **总输注量：**显示储药器已输送的胰岛素总量（单位）。 该数值包含激活储药器和管路填充所消耗的胰岛素。
+* **错误信息：**显示最近发生的错误。 请查阅[储药器历史记录](#view-pod-history)和日志文件以获取过往错误详情及更完整的信息。
+* **活动储药器警报：** 保留用于当前活动储药器上正在运行的警报。
### 按钮
- : Sends a refresh command to the active pod to update communication.
+ ：向活动储药器发送刷新指令以更新通信状态。
- * Use to refresh the pod status and dismiss status fields that contain the text (uncertain).
- * See the Troubleshooting section below for additional information.
+ * 用于刷新储药器状态并清除显示（不确定）的状态字段。
+ * 更多信息请参阅下文"故障排除"章节。
- : Navigates to the Pod management menu.
+ ：跳转至储药器管理菜单。
- : When pressed this will disable the pod alerts beeps and notifications (expiry, low reservoir..).
+ ：按下后将禁用储药器警报提示音和通知（如到期提醒、低药量警报等）。
- * Button is displayed only when pod time is past expiration warning time.
- * Upon successful dismissal, this icon will no longer appear.
+ * 该按钮仅在储药器时间超过到期警告时间后显示。
+ * 成功取消后，该图标将不再显示。
- : Resumes the currently suspended insulin delivery in the active pod.
+ ：恢复当前活动储药器中暂停的胰岛素输注。
-### Pod Management Menu
+### Pod 管理菜单
-Below is the meaning of the icons on the **Pod Management** menu accessed by pressing **POD MGMT (1)** button from the **DASH** tab.
+以下是**储药器管理**菜单中图标的含义，该菜单可通过在**DASH**标签页按下**储药器管理(1)**按钮进入。
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#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.
+* 2 - [**激活储药器**](#activate-pod)：对新储药器进行管路填充和激活操作。
+* 3 - [**停用储药器**](#deactivate-pod)：停用当前活动中的储药器。
+* 4 - **播放测试提示音**：按下时使储药器发出单次测试提示音。
+* 5 - [**储药器历史记录**](#view-pod-history)：显示活动储药器的操作历史记录。
(DanaRS-Insulin-Pump-dash-settings)=
-## Dash Settings
+## DASH设置
-The Dash driver settings are configurable from the top-left hand corner **hamburger menu** under **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. 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**.
+DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器(1)**→**胰岛素泵**→**DASH**→**设置齿轮图标(3)**进行配置，选择标有**DASH**的**单选按钮(2)**即可。 勾选**设置齿轮图标(3)**旁的**复选框(4)**，即可在**AAPS**界面中将DASH菜单显示为名为**DASH**的标签页。
-**NOTE:** A faster way to access the **Dash settings** is by accessing the **3 dot menu (1)** in the upper right hand corner of the **DASH** tab and selecting **Dash preferences (2)** from the dropdown menu.
+**注意：** 访问**DASH设置**的快捷方式是通过**DASH**标签页右上角的**三点菜单(1)**，然后从下拉菜单中选择**DASH偏好设置(2)**。
-The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below:
+以下是设置分组列表，您可通过切换开关启用或禁用下文所述的大多数选项：
-*NOTE: An asterisk (\*) denotes the default setting is enabled.*
+*注：带星号(*)表示默认启用该设置。*
-### Confirmation beeps
+### 确认提示音
-Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes.
+提供储药器对大剂量注射、基础率、超微大剂量(SMB)和临时基础率(TBR)输送及变更的确认提示音。
-* **Bolus beeps enabled:** Enable or disable confirmation beeps when a bolus is delivered.
-* **Basal beeps enabled:** Enable or disable confirmation beeps when a new basal rate is set, active basal rate is canceled or current basal rate is changed.
-* **SMB beeps enabled:** Enable or disable confirmation beeps when a SMB is delivered.
-* **TBR beeps enabled:** Enable or disable confirmation beeps when a TBR is set or canceled.
+* **启用大剂量提示音：** 控制大剂量输注时是否发出确认提示音。
+* **启用基础率提示音：** 控制设置新基础率、取消活动基础率或变更当前基础率时是否发出确认提示音。
+* **启用超微大剂量提示音：** 控制超微大剂量(SMB)输注时是否发出确认提示音。
+* **启用临时基础率提示音：** 控制设置或取消临时基础率(TBR)时是否发出确认提示音。
### 警报
-Provides **AAPS** alerts for pod expiration, shutdown, low reservoir based on the defined threshold units.
+当储药器达到过期、关机或根据设定阈值单位检测到低药量时，提供**AAPS**警报提示。
-*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. To MANUALLY dismiss the alert you must visit the **DASH** tab and press the **Silence ALERTS button**.*
+*请注意：自警报触发后与储药器首次通信时，AAPS将始终针对任何警报发出通知。 除非启用"自动确认储药器警报"功能，否则仅消除通知并不会消除警报状态。 要手动消除警报，必须访问**DASH**标签页并点击**静音警报按钮**。*
-* **Expiration reminder enabled:** Enable or disable the pod expiration reminder set to trigger when the defined number of hours before shutdown is reached.
-* **Hours before shutdown:** Defines the number hours before the active pod shutdown occurs, which will then trigger the expiration reminder alert.
-* **Low reservoir alert enabled:** Enable or disable an alert when the pod's remaining units low reservoir limit is reached as defined in the Number of units field.
-* **Number of units:** The number of units at which to trigger the pod low reservoir alert.
+* **启用过期提醒：** 控制是否在储药器达到设定的关机前小时数时触发过期提醒。
+* **关机前小时数：** 设定活动储药器关机前触发过期提醒警报的小时数。
+* **启用低药量警报：** 控制当储药器剩余药量达到"单位数值"字段中定义的低药量限值时是否触发警报。
+* **单位数值：** 触发储药器低药量警报的剩余药量单位数。
### 通知
-The Notification section allows the user to so select their preferred notifications and audible phone alerts when it is uncertain if TBR, SMB, or bolus, and delivery suspended events were successful.
+通知设置部分允许用户选择偏好的通知方式和手机提示音，用于在临时基础率(TBR)、超微大剂量(SMB)、大剂量注射或输注暂停事件是否成功执行存在不确定性时发出提醒。
-*NOTE: These are notifications only, no audible beep alerts are made.*
+*注：这些仅为手机通知，不会触发储药器声音提示。*
-* **Sound for uncertain TBR notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS** is uncertain if a TBR was successfully set.
-* **Sound for uncertain SMB notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS**is uncertain if an SMB was successfully delivered.
-* **Sound for uncertain bolus notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS**is uncertain if a bolus was successfully delivered.
-* **Sound when delivery suspended notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when suspend delivery was successfully delivered.
+* **启用临时基础率不确定通知提示音：** 当**AAPS**无法确认临时基础率(TBR)是否成功设置时，控制是否触发声音警报及视觉通知。
+* **启用超微大剂量不确定通知提示音：** 当**AAPS**无法确认超微大剂量(SMB)是否成功输注时，控制是否触发声音警报及视觉通知。
+* **启用大剂量不确定通知提示音：** 当**AAPS**无法确认大剂量是否成功输注时，控制是否触发声音警报及视觉通知。
+* **启用输注暂停通知提示音：** 当成功执行输注暂停时，控制是否触发声音警报及视觉通知。
-## Actions (ACT) Tab
+## 操作 (ACT) 标签页
-This tab is well documented in the main**AAPS**documentation but there are a few items on this tab that are specific to how the DASH differs from tube based pumps, especially after the processes of applying a new pod.
+该标签页在**AAPS**主文档中已有详细说明，但其中部分条目专门体现了DASH与管路泵的区别特性，特别是在更换新储药器后的操作流程方面。
-1. Go to the **Actions (ACT)** tab in the main **AAPS**interface.
+1. 请前往**AAPS**主界面中的**操作(ACT)**标签页。
-2. Under the **Careportal (1)** section the **Insulin** and **Cannula** fields will have their **age reset** to 0 days and 0 hours **after each pod change**. This is done because of how the Omnipod pump is built and operates. Since the pod inserts the cannula directly into the skin at the site of the pod application, a traditional tube is not used in Omnipod pumps. *Therefore after a pod change the age of each of these values will automatically reset to zero.* **Pump battery age** is not reported as the battery in the pod will always be more than the life of the pod (maximum 80 hours). The **pump battery** and **insulin reservoir** are self contained inside of each pod.
+2. 在**Careportal(1)**部分，**胰岛素**和**输注套管**字段的**使用时长**会在**每次更换储药器后**重置为0天0小时。 这是由于Omnipod胰岛素泵的构造和工作原理决定的。 由于储药器在敷贴时会直接将输注套管插入皮肤，Omnipod泵不使用传统导管。 *因此更换储药器后，这些数值的使用时长会自动归零。* **泵电池使用时长**不显示报告，因为储药器内置电池的寿命始终超过储药器使用期限（最长80小时）。 **泵电池**和**胰岛素储药器**均内置于每个储药器单元内部。
### 余量水平
-**Insulin Level**
+**胰岛素储药量**
-Insulin level displayed is the amount reported by DASH. However, the pod only reports the actual insulin reservoir level when it is below 50 units. Until then “Above 50 units” will be displayed. The amount reported is not exact: when the pod reports ‘empty’ in most cases the reservoir will still have some additional units of insulin left. The DASH overview tab will display as described the below:
+显示的胰岛素储药量为DASH报告的药量。 但储药器仅在剩余药量低于50单位时才会报告实际胰岛素储药量。 在此之前将始终显示"高于50单位"。 报告数值并不精确：当储药器显示"空"时，多数情况下储药器内仍会残留若干单位的胰岛素。 DASH概览标签页将显示如下内容：
- * **Above 50 Units** - The pod reports more than 50 units currently in the reservoir.
- * **Below 50 Units** - The amount of insulin remaining in the reservoir as reported by the Pod.
+ * **高于50单位** - 储药器报告当前药量超过50单位。
+ * **低于50单位** - 储药器报告的剩余胰岛素实际药量。
-Additional note:
- * **SMS** - Returns value or 50+U for SMS responses
- * **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units.
+补充说明：
+ * **短信查询** - 短信回复将返回实际数值或"50+单位"
+ * **Nightscout** - 当药量超过50单位时，会向Nightscout上传50的数值（14.07及更早版本）。 较新版本在药量超过50单位时将报告"50+"的数值。
## 故障排除
-### Delivery suspended
+### 输注暂停
- * There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
- * During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile**. If communication fails between the two commands, then delivery can stay suspended. When this happens:
- - There will be no insulin delivery, that includes Basal, SMB, Manual bolusing etc.
- - 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.
- - 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.
+ * 不再设有暂停按钮。 如需"暂停"储药器，可设置持续时间为X分钟的零值**临时基础率(TBR)**。
+ * 在执行**配置文件切换**时，DASH必须在设置新的基础率**配置文件**前暂停胰岛素输注。 若两条指令间通信失败，输注可能保持暂停状态。 当发生此情况时：
+ - 胰岛素输注将完全停止，包括基础率、超微大剂量(SMB)、手动大剂量等所有输注功能。
+ - 系统可能显示某条指令未确认的通知（具体取决于通信失败发生的时机）。
+ - **AAPS**将每15分钟尝试设置新的基础率配置文件。
+ - 若输注仍处于暂停状态（恢复输注失败），**AAPS**将每15分钟显示一次输注暂停的提醒通知。
+ - 若用户选择手动恢复输注，[**恢复输注**](#resuming-insulin-delivery)按钮将处于激活状态。
+ - 若**AAPS**自动恢复输注失败（当储药器无法连接、静音等情况发生时），储药器将每分钟发出4次蜂鸣、持续3分钟；若暂停状态超过20分钟仍未恢复，则每15分钟重复此警报模式。
+ * 对于未确认的指令，"刷新储药器状态"操作可予以确认或否决。
-**Note:** When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, **so you need to check !**
+**注意：**当听到储药器发出蜂鸣声时，切勿未经查看手机就假定输注会继续——输注可能仍处于暂停状态，**因此必须进行检查！**
-### Pod Failures
+### Pod 故障
-Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. A list of fault codes can be [**found here**](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause.
+储药器偶尔会因各种问题发生故障，包括储药器自身的硬件问题。 最佳做法是不要向Insulet公司报修，因为AAPS并非官方认可的使用方案。 故障代码列表可[**在此查阅**](https://github.com/openaps/openomni/wiki/Fault-event-codes)以帮助判断故障原因。
-### Preventing error 49 pod failures
+### 预防49号储药器故障
-This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. This is when the driver and Pod disagree on the actual state. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. The exact origin of a “49 pod failure” often is hard to trace. In situations that are suspected for this failure to occur (for instance on application crashes, running a development version or re-installation).
+该故障与指令对应的储药器状态错误或胰岛素输注指令执行出错有关。 此时驱动程序和储药器对实际状态的判断出现分歧。 出于内置安全机制，储药器会触发不可恢复的49号错误代码(0x31)，导致俗称"尖叫器"的状态——这种持续恼人的蜂鸣声只能通过在储药器背面指定位置打孔来停止。 "49号储药器故障"的具体成因通常难以追溯。 在怀疑可能发生此类故障的情况下（例如应用程序崩溃、运行开发版本或重新安装时）。
-### Pump Unreachable Alerts
+### 泵体失联警报
-When no communication can be established with the pod for a preconfigured time a “Pump unreachable” alert will be raised. Pump unreachable alerts can be configured by going to the top right-hand side three-dot menu, selecting **Preferences**\ ➜\ **Local Alerts**\ ➜\ **Pump unreachable threshold [min]**. Recommended value is alerting after **120** minutes.
+当超过预设时间仍无法与储药器建立通信时，系统将触发"泵体不可达"警报。 可通过右上角三点菜单配置泵体失联警报：选择**偏好设置**→**本地警报**→**泵体失联阈值[分钟]**进行设置。 建议将警报阈值设置为**120**分钟后触发。
-### Export Settings
+### 导出设置
-Exporting **AAPS** settings enables you to restore all your settings, and maybe more importantly, all your Objectives. You may need to restore settings to the “last known working situation” or after uninstalling/reinstalling **AAPS** or in case of phone loss, reinstalling on the new phone.
+导出**AAPS**设置可让您恢复所有配置参数，更重要的是能完整保留所有目标进度状态。 当需要恢复到"最后已知的正常状态"、或卸载重装**AAPS**后、以及手机丢失需在新设备上重新安装时，均可通过该功能还原设置。
-Note: The active pod information is included in the exported settings. If you import an "old" exported file, your actual pod will "die". There is no other alternative. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. In this case it is important to only use the recently exported settings file containing the pod currently active.
+注：当前使用中的储药器信息也会包含在导出设置中。 若导入"旧版"导出文件，您当前使用的储药器将"失效"。 别无他法。 在某些情况下（例如_计划性_更换手机时），您可能需要使用导出文件来恢复**AAPS**设置，**同时保留当前正在使用的储药器**。 在这种情况下，必须使用最近导出的、包含当前使用中储药器信息的设置文件。
-**It is good practice to do an export immediately after activating a pod**. This way you will always be able to restore the current active pod in case of a problem. For instance when moving to another backup phone.
+**最佳做法是在激活储药器后立即进行设置导出**。 如此可在出现问题时随时恢复当前使用中的储药器状态。 例如在切换到备用手机时。
-Regularly copy your exported settings to a safe place (as a cloud drive) that can be accessible by any phone when needed (e.g. in case of a phone loss or factory reset of the actual phone).
+请定期将导出的设置文件备份至云端等安全位置，确保任何手机在需要时（如设备丢失或恢复出厂设置时）都能随时获取。
-### Import Settings
+### 导入设置
-**WARNING** Please note that importing settings will possibly import an outdated Pod status. As a result, there is a risk of losing the active Pod! (see **Exporting Settings**). It is better to only try it when no other options are available.
+**警告** 请注意：导入设置可能会引入过期的储药器状态数据。 这将导致当前使用中的储药器存在失效风险！ （参见**导出设置**章节）。 建议仅在无其他解决方案时尝试此操作。
-When importing settings with an active Pod, make sure the export was done with the currently active pod.
+导入含激活状态储药器的设置时，请确认该导出文件包含当前使用中的储药器信息。
-**Importing while on an active Pod:** (you risk losing the Pod!)
+**在储药器激活状态下导入：**（可能导致储药器失效！）
-1. Make sure you are importing settings that were recently exported with the currently active Pod.
-2. Import your settings.
-3. Check all preferences.
+1. 请确保导入的是最近导出且包含当前使用中储药器信息的设置文件。
+2. 导入您的设置文件。
+3. 请核对所有偏好设置项。
-**Importing (no active Pod session)**
+**导入设置（无激活状态的储药器会话）**
-1. Importing any recent export should work (see above)
-2. Import your settings.
-3. Check all preferences.
-4. You may need to **Deactivate** the "non existing" pod if the imported settings included any active pod data.
+1. 导入任何近期导出的文件均可生效（参见上文说明）
+2. 导入您的设置文件。
+3. 请核对所有偏好设置项。
+4. 若导入的设置包含任何激活状态的储药器数据，您可能需要**停用**这个"不存在"的储药器。
-### Importing settings that contain Pod state from an inactive Pod
+### 导入包含非活跃状态储药器数据的设置文件
-When importing settings containing data for a Pod that is no longer active, AAPS will try to connect with it, which will obviously fail. You can not activate a new Pod in this situation.
+当导入包含已停用储药器数据的设置时，AAPS将尝试与其建立连接，这显然会导致失败。 在此情况下您将无法激活新储药器。
-To remove the old pod session “try” to de-activate the Pod. The de-activation will fail. Select “Retry”. After the second or third retry you will get the option to remove the pod. Once the old pod is removed you will be able to activate a new pod.
+要清除旧储药器会话，请"尝试"执行停用操作。 停用操作将会失败。 选择"重试"。 经过两到三次重试后，系统将提供移除储药器的选项。 待旧储药器移除后，即可激活新储药器。
-### Reinstalling AAPS
+### 重新安装AAPS
-When uninstalling**AAPS** you will lose all your settings, objectives and the current Pod session. To restore them make sure you have a recent exported settings file available!
+卸载**AAPS**时，所有设置、目标进度及当前储药器会话都将丢失。 请确保已备份最新导出的设置文件以便恢复！
-When on an active Pod, make sure that you have an export for the current pod session or you will lose the currently active pod when importing older settings.
+当使用激活状态的储药器时，请确保已备份当前储药器会话的导出文件，否则导入旧版设置将导致当前使用中的储药器失效。
-1. Export your settings and store a copy in a safe place.
-2. Uninstall **AAPS** and restart your phone.
-3. Install the new version of **AAPS**.
-4. Import your settings.
-5. Verify all preferences (optionally import settings again).
-6. Activate a new pod.
-7. When done: Export current settings.
+1. 请导出您的设置文件并妥善保存副本。
+2. 卸载**AAPS**并重启您的手机。
+3. 安装新版本的**AAPS**。
+4. 导入您的设置文件。
+5. 请核对所有偏好设置（可选择重新导入设置文件）。
+6. 激活新储药器。
+7. 操作完成后：请导出当前设置文件。
-### Updating AAPS to a newer version
+### 升级AAPS至新版本
-In most cases there is no need to uninstall. You can do an “in-place” install by starting the installation for the new version. This is also possible when on an active Pod session.
+多数情况下无需卸载旧版本。 您可直接安装新版本进行"就地升级"。 该操作在储药器激活状态下同样适用。
-1. Export your settings.
-2. Install the new **AAPS** version.
-3. Verify the installation was successful
-4. RESUME the Pod or activate a new pod.
-5. When done: Export current settings.
+1. 请导出您的设置文件。
+2. 安装新版**AAPS**。
+3. 请确认安装是否成功
+4. 恢复原储药器使用或激活新储药器。
+5. 操作完成后：请导出当前设置文件。
-### Omnipod driver alerts
+### Omnipod驱动警报
-Please note that the Omnipod Dash driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. A summary of the main alerts that you may encounter is listed below:
+请注意：Omnipod Dash驱动会在**概览页**显示多种特有警报，多数为提示性信息可手动关闭，部分警报会要求用户执行操作以消除触发警报的原因。 以下是您可能会遇到的主要警报摘要：
-* No active Pod session detected. This alert can temporarily be dismissed by pressing **SNOOZE** but it will keep triggering as long as a new pod has not been activated. Once activated this alert is automatically silenced.
-* Pod suspended Informational alert that pod has been suspended.
-* Setting basal **Profile** failed : Delivery might be suspended! Please manually refresh the Pod status from the Omnipod tab and resume delivery if needed.. Informational alert that the Pod basal **Profile** setting has failed, and you will need to hit *Refresh* on the Omnipod tab.
-* Unable to verify whether **SMB** bolus succeeded. If you are sure that the Bolus didn't succeed, you should manually delete the SMB entry from Treatments. Alert that the **SMB** bolus command success could not be verified, you will need to verify the *Last bolus* field on the DASH tab to see if **SMB** bolus succeeded and if not remove the entry from the Treatments tab.
-* Uncertain if "task bolus/TBR/SMB" completed, please manually verify if it was successful.
+* 未检测到活动的Pod会话。 该警报可通过点击**暂缓**临时关闭，但在新储药器激活前将持续触发。 该警报激活后将自动静音。
+* 储药器已暂停 提示性警报，表明储药器处于暂停状态。
+* 设置基础**配置文件**失败：输注可能已暂停！ 请从Omnipod标签页手动刷新储药器状态，必要时恢复输注。 提示性警报：储药器基础**配置文件**设置失败，需点击Omnipod标签页的*刷新*按钮。
+* 无法确认**超微大剂量**输注是否成功。 若确认大剂量未成功输注，请手动从治疗记录中删除该条超微大剂量记录。 警报提示：**超微大剂量**输注命令的成功状态无法验证，您需要检查DASH标签页的*最后大剂量*字段确认输注是否成功，若失败则需从治疗记录页删除该条目。
+* 无法确认"任务大剂量/临时基础率/超微大剂量"是否完成，请人工核验操作结果。
-## Where to get help for DASH
+## DASH系统求助渠道
-All of the development work for the DASH is done by the community on a **volunteer** basis; please keep this in mind and use the following guidelines before requesting assistance:
+DASH系统的所有开发工作均由社区**志愿者**无偿完成；在请求协助前，请谨记以下准则：
-- **Level 0:** Read the relevant section of this documentation to ensure you understand how the functionality with which you are experiencing difficulty is supposed to work.
-- **Level 1:** If you are still encountering problems that you are not able to resolve by using this document, then please go to the *#AAPS* channel on **Discord** by using [this invite link](https://discord.gg/4fQUWHZ4Mw).
-- **Level 2:** Search existing issues to see if your issue has already been reported at [Issues](https://github.com/nightscout/AndroidAPS/issues) if it exists, please confirm/comment/add information on your problem. If not, please create a [new issue](https://github.com/nightscout/AndroidAPS/issues) and attach [your log files](../GettingHelp/AccessingLogFiles.md).
-- **Be patient - most of the members of our community consist of good-natured volunteers, and solving issues often requires time and patience from both users and developers.**
+- **第0级：**查阅本文档相关章节，确保您已理解遇到问题的功能模块的正确运作方式。
+- **第1级：**若参照本文档仍无法解决问题，请通过[此邀请链接](https://discord.gg/4fQUWHZ4Mw)加入**Discord**平台的*#AAPS*频道寻求帮助。
+- **第2级：**在[问题追踪](https://github.com/nightscout/AndroidAPS/issues)页面搜索现有问题报告，确认您的问题是否已被记录。若存在相关报告，请补充说明您的情况。 如果没有，请创建一个[新问题](https://github.com/nightscout/AndroidAPS/issues)并附上[您的日志文件](../GettingHelp/AccessingLogFiles.md)。
+- **请保持耐心——我们社区成员多为热心志愿者，问题的解决往往需要用户和开发者双方投入时间与耐心。**
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodEros.md b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodEros.md
index 63061359446d..19ee0c9a87c3 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodEros.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodEros.md
@@ -2,488 +2,488 @@
orphan: true
- - -
-# AAPS Omnipod Insulin Pump Driver Documentation
+# AAPS Omnipod胰岛素泵驱动文档
-These instructions are for configuring the Omnipod Eros generation pump (**NOT Omnipod Dash**). The Omnipod driver is available as part of AAPS (AAPS) as of version 2.8.
+本指南适用于配置Omnipod Eros系列胰岛素泵（**不包含Omnipod Dash**）。 自AAPS 2.8版本起已集成Omnipod驱动功能。
-**This software is part of a DIY artificial pancreas solution and is not a product but requires YOU to read, learn, and understand the system, including how to use it. 只有你才能对自己的行为负责。**
+**本软件属于人工胰腺系统的DIY解决方案，并非商业产品，需要用户自行研习并全面掌握系统操作原理。 使用后果由您自行承担。**
```{contents}
:backlinks: entry
:depth: 2
```
-## Hardware and Software Requirements
+## 硬件和软件要求
-- **Pod Communication Device**
+- **Pod 通信设备**
-> Component that bridges communication from your AAPS enabled phone to Eros generation pods.
+> 该组件实现AAPS手机端与Eros系列储药器间的通信桥接功能。
>
> > -  [OrangeLink Website](https://getrileylink.org/product/orangelink)
> > -  [433MHz RileyLink](https://getrileylink.org/product/rileylink433)
-> > -  [Emalink Website](https://github.com/sks01/EmaLink) - [Contact Info](mailto:getemalink@gmail.com)
-> > -  DiaLink - [Contact Info](mailto:Boshetyn@ukr.net)
-> > -  [LoopLink Website](https://www.getlooplink.org/) - [Contact Info](https://jameswedding.substack.com/) - Untested
+> > -  [Emalink 网站](https://github.com/sks01/EmaLink) - [联系方式](mailto:getemalink@gmail.com)
+> > -  DiaLink - [联系方式](mailto:Boshetyn@ukr.net)
+> > -  [LoopLink官网](https://www.getlooplink.org/) - [联系方式](https://jameswedding.substack.com/) - 未经测试
--  **Mobile Phone Device**
+-  **移动电话设备**
-> Component that will operate AAPS and send control commands to the Pod communication device.
+> 该组件负责运行AAPS并向储药器通信设备发送控制指令。
>
-> > - Supported [Omnipod driver Android phone](#Phones-list-of-tested-phones) with a version of AAPS 2.8 and related components set up.
+> > - 支持运行AAPS 2.8版本及相关组件的[Omnipod驱动安卓手机](#Phones-list-of-tested-phones)。
--  **Insulin Delivery Device**
+-  **胰岛素输注设备**
-> Component that will interpret commands received from the Pod communication device originating from your AAPS enable phone.
+> 该组件负责解析来自AAPS手机端通过储药器通信设备传输的控制指令。
>
-> > - A new Omnipod pod (Eros generation - **NOT DASH**)
+> > - 全新Omnipod储药器（Eros系列 - **非DASH型号**）
-These instructions will assume that you are starting a new pod session; if this is not the case, please be patient and attempt to begin this process on your next pod change.
+本指南默认您正在启动新储药器会话；若非此情况，请保持耐心并在下次更换储药器时执行此流程。
-## Before You Begin
+## 开始前的准备工作
-**SAFETY FIRST** - do not attempt this process in an environment where you cannot recover from an error (extra pods, insulin, charged RileyLink, and phone devices are must-haves).
+**安全第一** - 请勿在无法处理突发故障的环境中操作（必须备有备用储药器、胰岛素、电量充足的RileyLink及手机设备）。
-**Your Omnipod PDM will no longer work after the AAPS Omnipod driver activates your pod**. Previously you used your Omnipod PDM to send commands to your Omnipod Eros pod. An Omnipod Eros pod only allows a single device to send communication to it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate an Omnipod Eros pod with your RileyLink through the AAPS Omnipod driver, **you will no longer be able to use your PDM with your pod**. The AAPS Omnipod driver with the RileyLink is now your acting PDM. *This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup, and for emergencies with AAPS is not working correctly.*
+**AAPS Omnipod驱动激活储药器后，您的Omnipod PDM将无法继续使用**。 此前您通过Omnipod PDM向Eros储药器发送指令。 Eros储药器仅允许单一设备与其建立通信连接。 成功激活储药器的设备将成为此后唯一获准与其通信的设备。 这意味着当您通过AAPS Omnipod驱动使用RileyLink激活Eros储药器后，**PDM将无法再控制该储药器**。 配备RileyLink的AAPS Omnipod驱动现已成为您的实际控制设备。 *这并不意味着您应该丢弃PDM，建议将其保留作为备用设备，以防AAPS运行异常时应急使用。*
-**You can configure multiple RileyLinks, but only one selected RileyLink at a time can communicate with a pod.** The AAPS Omnipod driver supports the ability to add multiple RileyLinks in the RileyLink configuration, however, only one RileyLink at a time can be selected to be used for sending and receiving communication.
+**可配置多个RileyLink设备，但同一时间仅能选择一个RileyLink与储药器通信。** AAPS Omnipod驱动支持在RileyLink配置中添加多个设备，但每次仅能启用一个RileyLink进行收发通信。
-**Your pod will not shut off when the RileyLink is out of range.** When your RileyLink is out of range or the signal is blocked from communicating with the active pod, your pod will continue to deliver basal insulin. Upon activating a pod, the basal profile defined in AAPS will be programmed into the new pod. Should you lose contact with the pod, it will revert to this basal profile. You will not be able to issue new commands until the RileyLink comes back in range and re-establishes the connection.
+**当RileyLink超出通信范围时，储药器不会停止工作。**若RileyLink超出有效距离或信号受阻无法与当前储药器通信，储药器仍将持续输注基础胰岛素。 激活储药器时，AAPS中设定的基础率配置文件将被写入新储药器。 若与储药器通信中断，设备将自动切换至此预设基础率方案运行。 在RileyLink重新进入通信范围并恢复连接前，您将无法发送新指令。
-**30 min Basal Rate Profiles are NOT supported in AAPS.** If you are new to AAPS and are setting up your basal rate profile for the first time please be aware that basal rates starting on a half hour are not supported and you will need to adjust your basal rate profile to start on the hour. For example, if you have a basal rate of say 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, this will not work. You will need to update this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the 30 min basal rate profile increments are supported by the Omnipod hardware itself, AAPS is not able to take them into account with its algorithms currently.
+**AAPS不支持30分钟间隔的基础率配置。** 若您初次使用AAPS并设置基础率，请注意系统不支持半点起始的基础率方案，需调整为整点起始的配置模式。 例如：若您设有1.1单位的基础率方案，起始时间为09:30并持续2小时至11:30结束，此配置将无法生效。 您需将该1.1单位基础率的时间范围调整为9:00-11:00或10:00-12:00。 虽然Omnipod硬件本身支持30分钟间隔的基础率配置，但AAPS算法目前无法兼容此类设置。
-## Enabling the Omnipod Driver in AAPS
+## 在AAPS中启用Omnipod驱动
-You can enable the Omnipod driver in AAPS in **two ways**:
+您可通过**两种方式**在AAPS中启用Omnipod驱动：
-### Option 1: The Setup Wizard
+### 选项一：通过设置向导启用
-After installing a new version of AAPS, the **Setup Wizard** will start automatically. This will also occur during in place upgrades. If you already have exported your settings from a previous installation you can exit the Setup Wizard and import your old settings. For new installations proceed below.
+安装新版AAPS后，**设置向导**将自动启动。 原地升级时也会触发此向导。 若您已从旧版本导出设置，可退出设置向导并导入原有配置。 新安装用户请继续以下步骤。
-Via the **AAPS Setup Wizard (2)** located at the top right-hand corner **three-dot menu (1)** and proceeding through the wizard menus until you arrive at the **Pump** screen. Then select the **Omnipod radio button (3)** .
+通过右上角**三点菜单(1)**中的**AAPS设置向导(2)**进入，逐步操作直至进入**泵**设置界面。 然后选择**Omnipod单选按钮(3)**。
>  
-On the same screen, below the pump selection, the **Omnipod Driver Settings** are displayed, under the **RileyLink Configuration** add your RileyLink device by pressing the **Not Set** text.
+在同一界面的泵选择区域下方，**Omnipod驱动设置**中显示**RileyLink配置**，点击**未设置**文字添加您的RileyLink设备。
-On the **RileyLink Selection** screen press the **Scan** button and select your RileyLink by scanning for all available Bluetooth devices and selecting your RileyLink from the list. When properly selected you are returned to the pump driver selection screen displaying the Omnipod driver settings showing your selected RileyLink with the MAC address listed.
+在**RileyLink选择**界面点击**扫描**按钮，通过搜索所有可用蓝牙设备并从列表中选择您的RileyLink进行配对。 成功选择后，系统将返回泵驱动选择界面，此时Omnipod驱动设置中会显示已选RileyLink及其MAC地址。
-Press the **Next** button to proceed with the rest of the **Setup Wizard.** It can take up to one minute for the selected RileyLink to initialize and the **Next** button to become active.
+点击**下一步**按钮继续完成**设置向导**其余步骤。所选RileyLink初始化可能需要长达一分钟，之后**下一步**按钮才会激活。
-Detailed steps on how to setup your pod communication device are listed below in the [RileyLink Setup Section](#rileylink-setup).
+具体设置储药器通信设备的步骤详见下文[RileyLink配置章节](#rileylink-setup)。
-**OR**
+**或**
-### Option 2: The Config Builder
+### 选项2：配置构建器
-Via the top-left hand corner **hamburger menu** under **Config Builder (1)** ➜**Pump**➜**Omnipod** by selecting the **radio button (2)** titled **Omnipod**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will display the Omnipod menu as a tab in the AAPS interface titled **POD**. This is referred to in this documentation as the **Omnipod (POD)** tab.
+通过左上角**汉堡菜单**进入**配置构建器(1)**➜**泵**➜**Omnipod**，选择标有**Omnipod**的**单选按钮(2)**。 勾选**设置齿轮图标(3)**旁的**复选框(4)**后，Omnipod菜单将作为**POD**标签页显示在AAPS界面中。 本文档中将其称为**Omnipod(POD)**标签页。
-> **NOTE:** A faster way to access the **Omnipod settings** can be found below in the [Omnipod Settings section](#omnipod-settings) of this document.
+> **注意：**更快捷访问**Omnipod设置**的方法请参阅本文档[Omnipod设置章节](#omnipod-settings)。
>
>  
-### Verification of Omnipod Driver Selection
+### Omnipod驱动选择验证
-*Note: If you have exited the Setup Wizard early without selecting your RileyLink, the Omnipod Driver is enabled but you will still need to select your RileyLink. You may see the Omnipod (POD) tab appear as it does below*
+*注：若您未选择RileyLink便提前退出设置向导，虽已启用Omnipod驱动，但仍需完成RileyLink设备选择。 您可能会看到Omnipod（POD）标签页如下所示*
-To verify that you have enabled the Omnipod driver in AAPS **swipe to the left** from the **Overview** tab, where you will now see an **Omnipod** or **POD** tab.
+要确认您已在AAPS中启用Omnipod驱动，请从**概览**标签页**向左滑动**，此时您将看到**Omnipod**或**POD**标签页。
-## Omnipod Configuration
+## Omnipod配置
-Please **swipe left** to the **Omnipod (POD)** tab where you will be able to manage all pod and RileyLink functions (some of these functions are not enabled or visible without an active pod session):
+请**向左滑动**至**Omnipod(POD)**标签页，您可在此管理所有储药器及RileyLink功能（部分功能需在储药器使用期间才会激活显示）：
->  Refresh Pod connectivity and status
+>  刷新储药器连接状态
>
->  Pod Management (Activate, Deactivate, Play test beep, RileyLink Stats and Pod history)
+>  储药器管理（激活/停用设备、播放测试提示音、查看RileyLink统计及输注历史）
(OmnipodEros-rileylink-setup)=
-### RileyLink Setup
+### RileyLink 设置
-If you already successfully paired your RileyLink in the Setup Wizard or steps above, then proceed to the [Activating a Pod Section](#activating-a-pod) below.
+若您已通过设置向导或上述步骤成功配对RileyLink，请直接前往下方[激活储药器章节](#activating-a-pod)。
-*Note: A good visual indicator that the RileyLink is not connected is that the Insulin and Calculator buttons on the HOME tab will be missing. This will also occur for about the first 30 seconds after AAPS starts, as it is actively connecting to the RileyLink.*
+*注：RileyLink未连接时，主页标签页的胰岛素和计算器按钮会消失，这是明显的视觉提示。 AAPS启动后约30秒内也会出现此现象，此时系统正在主动连接RileyLink。*
-1. Ensure that your RileyLink is fully charged and powered on.
+1. 请确保您的RileyLink已充满电并处于开机状态。
-2. After selecting the Omnipod driver, identify and select your RileyLink from **Config Builder (1)** ➜**Pump**➜**Omnipod**➜**Gear Icon (Settings) (2)** ➜**RileyLink Configuration (3)** by pressing the **Not Set** or **MAC Address (if present)** text.
+2. 选择Omnipod驱动后，通过**配置构建器(1)**➜**泵**➜**Omnipod**➜**齿轮图标(设置)(2)**➜**RileyLink配置(3)**路径，点击**未设置**或**MAC地址(如有显示)**文字来识别并选择您的RileyLink设备。
- > Ensure your RileyLink battery is charged and it is [positioned in close proximity](#optimal-omnipod-and-rileylink-positioning) (~30 cm away or less) to your phone for AAPS to identify it by its MAC address. Once selected, you can proceed to activate your first pod session. Use the back button on your phone to return to the main AAPS interface.
+ > 请确保您的RileyLink电量充足，并将其[紧贴放置](#optimal-omnipod-and-rileylink-positioning)（距离手机约30厘米以内），以便AAPS通过MAC地址识别设备。 选择完成后，即可开始激活首个储药器使用会话。 使用手机返回键回到AAPS主界面。
>
>  
-3. On the **RileyLink Selection** screen press the **Scan (4)** button to initiate a bluetooth scan. **Select your RileyLink (5)** from the list of available Bluetooth devices.
+3. 在**RileyLink选择**界面，点击**扫描(4)**按钮启动蓝牙搜索。 从可用蓝牙设备列表中**选择您的RileyLink(5)**。
>  
-4. After successful selection you are returned to the Omnipod Settings page listing your **currently selected RileyLink's MAC Address (6).**
+4. 成功选择后，系统将返回Omnipod设置页面，其中会显示**当前所选RileyLink的MAC地址(6)**。
> 
-5. Verify that in the **Omnipod (POD)** tab that the **RileyLink Status (1)** appears as **Connected.** The **Pod status (2)** field should show **No active Pod**; if not, please attempt the previous step or exit AAPS to see if this refreshes the connection.
+5. 请在**Omnipod(POD)**标签页确认**RileyLink状态(1)**显示为**已连接**，且**储药器状态(2)**栏应显示**无活跃储药器**。若未显示，请尝试重复上一步操作或退出AAPS以刷新连接。
> 
(OmnipodEros-activating-a-pod)=
-### Activating a Pod
+### 激活储药器
-Before you can activate a pod please ensure you have properly configured and connected your RileyLink connection in the Omnipod settings
+激活储药器前，请确保您已在Omnipod设置中正确配置并连接RileyLink设备。
-*REMINDER: Pod communication occurs at limited ranges for pod activation pairing due to security safety measures. Before pairing the Pod's radio signal is weaker, however after it has been paired it will operate at full signal power. During these procedures, make sure that your pod is* [within close proximity](#optimal-omnipod-and-rileylink-positioning) (~30 cm away or less) but not on top of or right next to the RileyLink.\*
+*重要提示：出于安全防护机制，储药器激活配对时的通信距离存在严格限制。 配对前储药器射频信号较弱，但成功配对后将恢复全功率信号传输。 操作过程中，请确保*储药器[紧贴放置](#optimal-omnipod-and-rileylink-positioning)（距离约30厘米以内），但避免直接叠放或紧靠RileyLink设备。
-01. Navigate to the **Omnipod (POD)** tab and click on the **POD MGMT (1)** button, and then click on **Activate Pod (2)**.
+01. 请进入**Omnipod(POD)**标签页，点击**储药器管理(1)**按钮，然后选择**激活储药器(2)**。
>  
-02. The **Fill Pod** screen is displayed. Fill a new pod with at least 80 units of insulin and listen for two beeps indicating that the pod is ready to be primed. When calculating the total amount of insulin you need for 3 days, please take into account that priming the pod will use 12 to 15 units.
+02. 此时将显示**填充储药器**界面。 请在新储药器中装入至少80单位胰岛素，听到两声提示音后表明储药器已准备好进行初始化。 计算3天所需胰岛素总量时，请注意储药器初始化将消耗12至15单位胰岛素。
> 
>
- > Ensure the new pod and RileyLink are within close proximity of each other (~30cm or less) and click the **Next** button.
+ > 请确保新储药器与RileyLink设备保持近距离（30厘米以内），然后点击**下一步**按钮。
-03. On the **Initialize Pod** screen, the pod will begin priming (you will hear a click followed by a series of ticking sounds as the pod primes itself). If RileyLink is out of range of the pod being activated, you will receive an error message **No response from Pod**. If this occurs, [move the RileyLink closer](#optimal-omnipod-and-rileylink-positioning) (~30 cm away or less) to but not on top of or right next to the Pod and click the **Retry (1)** button.
+03. 在**初始化储药器**界面，储药器将开始自检（您会听到"咔嗒"一声，随后是一连串滴答声，表明储药器正在进行自检程序）。 若RileyLink超出待激活储药器的有效范围，您将收到**储药器无响应**的错误提示。 遇到此情况时，请[将RileyLink移近](#optimal-omnipod-and-rileylink-positioning)储药器（保持30厘米以内距离，但勿直接叠放或紧贴），然后点击**重试(1)**按钮。
>  
-04. Upon successful priming a green checkmark will be shown and the **Next** button will become enabled. Click on the **Next** button to complete the pod priming initialization and display the **Attach Pod** screen.
+04. 初始化成功后，系统将显示绿色勾选标记，并激活**下一步**按钮。 点击**下一步**按钮完成储药器初始化，随后将显示**佩戴储药器**界面。
> 
-05. Next, prepare the infusion site of the new pod. Remove the pod's plastic needle cap and white paper backing from the adhesive and apply the pod to your usually selected site on your body. When finished, click on the **Next** button.
+05. 接下来，请准备好新储药器的输注部位。 撕除储药器塑料针帽及粘合衬底的白纸后，将其敷贴至您惯常选择的注射部位。 操作完成后，点击**下一步**按钮。
> 
-06. The **Attach Pod** dialog box will now appear. **ONLY click on the OK button if you are ready to deploy the cannula**.
+06. 此时将弹出**佩戴储药器**对话框。 **仅在准备部署软管时点击确认按钮**。
> 
-07. After pressing **OK**, it may take some time before the Omnipod responds and inserts the cannula (1-2 minutes maximum), so be patient.
+07. 点击**确认**后，Omnipod可能需要一些时间响应并插入软管（最长1-2分钟），请耐心等待。
- > If RileyLink is out of range of the pod being activated, you will receive an error message **No response from Pod**. If this occurs, move the RileyLink closer (~30 cm away or less) to but not on top of or right next to the Pod and click the **Retry** button.
+ > 若RileyLink超出待激活储药器的有效范围，您将收到**储药器无响应**的错误提示。 若出现此情况，请将RileyLink移近储药器（保持30厘米以内距离，但勿直接叠放或紧贴），然后点击**重试**按钮。
>
- > If the RileyLink is out of Bluetooth range or does not have an active connection to the phone, you will receive an error message **No response from RileyLink**. If this occurs, move the RileyLink closer to the phone and click the **Retry** button.
+ > 若RileyLink超出蓝牙范围或未与手机保持有效连接，您将收到**RileyLink无响应**的错误提示。 遇到此情况时，请将RileyLink移近手机后点击**重试**按钮。
>
- > *NOTE: Before the cannula is inserted, it is good practice to pinch the skin near the cannula insertion point. This ensures a smooth insertion of the needle and will decrease your chances of developing occlusions.*
+ > *注意：在插入导管前，建议捏起导管插入点附近的皮肤。 这能确保针头顺利插入，并降低导管堵塞的发生概率。*
>
> 
>
>  
-08. A green checkmark appears, and the **Next** button becomes enabled upon successful cannula insertion. Click on the **Next** button.
+08. 导管成功插入后会出现绿色勾选标记，**下一步**按钮将变为可点击状态。 点击**下一步**按钮。
> 
-09. The **Pod activated** screen is displayed. Click on the green **Finished** button. Congratulations! You have now started a new active pod session.
+09. 此时将显示**储药器已激活**界面。 点击绿色**完成**按钮。 恭喜！ 您已成功开启新的储药器使用会话。
> 
-10. The **Pod management** menu screen should now display with the **Activate Pod (1)** button *disabled* and the **Deactivate Pod (2)** button *enabled*. This is because a pod is now active and you cannot activate an additional pod without deactivating the currently active pod first.
+10. 此时**储药器管理**界面应显示为：**激活储药器(1)**按钮*已禁用*，而**停用储药器(2)**按钮*已启用*。 这是因为当前已有储药器处于激活状态，必须首先停用当前储药器才能激活新储药器。
- Click on the back button on your phone to return to the **Omnipod (POD)** 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.
+ 点击手机返回键回到**Omnipod(POD)**标签页，此时界面将显示当前储药器会话信息，包括基础率、储药器余量、已输注胰岛素量、设备报错及提醒等数据。
- For more details on the information displayed go to the [Omnipod (POD) Tab](#omnipod-pod-tab) section of this document.
+ 欲了解界面显示信息的详细说明，请参阅本文档[Omnipod(POD)标签页](#omnipod-pod-tab)章节。
 
-### Deactivating a Pod
+### 停用储药器
-Under normal circumstances, the life of a pod should run for three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of pod usage.
+正常情况下，储药器使用寿命为3天（72小时），触发过期警告后仍可延长使用8小时，总使用时长达80小时。
-To deactivate a pod (either from expiration or from a pod failure):
+要停用储药器（无论是因到期还是故障）：
-1. Go to the **Omnipod (POD)** tab, click on the **POD MGMT (1)** button, on the **Pod management** screen click on the **Deactivate Pod (2)** button.
+1. 请进入**Omnipod(POD)**标签页 → 点击**储药器管理(1)**按钮 → 在**储药器管理**界面选择**停用储药器(2)**功能。
>  
-2. On the **Deactivate Pod** screen, first, make sure the RileyLink is in close proximity to the pod but not on top of or right next to the pod, then click on the **Next** button to begin the process of deactivating the pod.
+2. 在**停用储药器**界面，请首先确保RileyLink设备靠近储药器（保持适当间距，避免直接叠放或紧贴），随后点击**下一步**按钮启动停用流程。
> 
-3. The **Deactivating Pod** screen will appear, and you will receive a confirmation beep from the pod that deactivation was successful.
+3. **停用舱**界面将显示，并且您会听到舱体发出的确认提示音，表示停用成功。
> 
>
- > **IF deactivation fails** and you do not receive a confirmation beep, you may receive a **No response from RileyLink** or **No response from Pod message**. Please click on the **Retry (1)** button to attempt deactivation again. If deactivation continues to fail, please click on the **Discard Pod (2)** button to discard the Pod. You may now remove your pod as the active session has been deactivated. If your Pod has a screaming alarm, you may need to manually silence it (using a pin or a paperclip) as the **Discard Pod (2)** button will not silence it.
+ > **如果停用失败**且未收到确认提示音，您可能会收到**未收到RileyLink响应**或**未收到Pod响应**的提示信息。 请点击**重试(1)**按钮以再次尝试停用。 如果停用持续失败，请点击**废弃Pod(2)**按钮以废弃Pod。 当前使用周期已终止，您现在可以移除储药器。 如果您的Pod发出警报声，您可能需要手动静音（使用别针或回形针），因为**废弃Pod(2)**按钮不会使其静音。
>
> >  
-4. A green checkmark will appear upon successful deactivation. Click on the **Next** button to display the pod deactivated screen. You may now remove your pod as the active session has been deactivated.
+4. 成功停用后将显示绿色勾选标记。 点击**下一步**按钮显示储药器已停用界面。 当前使用周期已终止，您现在可以移除储药器。
> 
-5. Click on the green button to return to the **Pod management** screen.
+5. 点击绿色按钮返回**Pod管理**界面。
> 
-6. You are now returned to the **Pod management** menu press the back button on your phone to return to the **Omnipod (POD)** tab. Verify that the **RileyLink Status:** field reports **Connected** and the **Pod status:** field displays a **No active Pod** message.
+6. 您现已返回**Pod管理**菜单，请按手机返回键回到**Omnipod(POD)**标签页。 请确认**RileyLink状态：**字段显示为**已连接**，且**Pod状态：**字段显示**无活动Pod**信息。
>  
-### Suspending and Resuming Insulin Delivery
+### 暂停和恢复胰岛素输注
-The process below will show you how to suspend and resume insulin pump delivery.
+以下流程将向您展示如何暂停和恢复胰岛素泵的输注。
-*NOTE - if you do not see a SUSPEND button*, then it has not been enabled to display in the Omnipod (POD) tab. Enable the **Show Suspend Delivery button in Omnipod tab** setting in the [Omnipod settings](#omnipod-settings) under **Other**.
+*注意 - 如果您没有看到"暂停"按钮*，说明该功能尚未在Omnipod(POD)标签页中启用显示。 在[Omnipod设置](#omnipod-settings)的**其他**选项下，启用**在Omnipod标签页显示暂停输注按钮**设置。
-#### Suspending Insulin Delivery
+#### 暂停胰岛素输注
-Use this command to put the active pod into a suspended state. In this suspended state, the pod will no longer deliver any insulin. This command mimics the suspend function that the original Omnipod PDM issues to an active pod.
+使用此命令将活动中的pod置于暂停状态。 在此暂停状态下，pod将停止输送任何胰岛素。 此命令模拟原装Omnipod PDM对活动pod发出的暂停功能。
-1. Go to the **Omnipod (POD)** tab and click on the **SUSPEND (1)** button. The suspend command is sent from the RileyLink to the active pod and the **SUSPEND (3)** button will become greyed out. The **Pod status (2)** will display **SUSPEND DELIVERY**.
+1. 请前往**Omnipod(POD)**标签页，点击**暂停(1)**按钮。 暂停指令已从RileyLink发送至活动pod，**暂停(3)**按钮将变为灰色不可用状态。 **Pod状态(2)**将显示**暂停输注**。
>  
-2. When the suspend command is successfully confirmed by the RileyLink a confirmation dialog will display the message **All insulin delivery has been suspended**. Click **OK** to confirm and proceed.
+2. 当RileyLink成功确认暂停指令后，将显示确认对话框，内容为**所有胰岛素输注已暂停**。 点击**确定**进行确认并继续操作。
> 
-3. Your active pod has now suspended all insulin delivery. The **Omnipod (POD)** tab will update the **Pod status (1)** to **Suspended**. The **SUSPEND** button will change to a new **Resume Delivery (2)** button
+3. 您当前使用的pod现已暂停所有胰岛素输注。 **Omnipod(POD)**标签页将更新**Pod状态(1)**为**已暂停**。 **暂停**按钮将变为新的**恢复输注(2)**按钮
> 
-#### Resuming Insulin Delivery
+#### 恢复胰岛素输注
-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.
+此指令用于命令当前暂停中的储药器恢复胰岛素输注。 命令成功处理后，胰岛素将根据当前时间从活动基础配置文件中恢复使用当前基础率进行正常输注。 Pod将重新接受大剂量、临时基础率和超微大剂量的指令。
-1. Go to the **Omnipod (POD)** tab and ensure the **Pod status (1)** field displays **Suspended**, then press the **Resume Delivery (2)** button to start the process to instruct the current pod to resume normal insulin delivery. A message **RESUME DELIVERY** will display in the **Pod status (3)** field, signifying the RileyLink is actively sending the command to the suspended pod.
+1. 请前往**Omnipod(POD)**标签页，确认**Pod状态(1)**字段显示为**已暂停**，然后点击**恢复输注(2)**按钮启动流程，指示当前pod恢复正常胰岛素输注。 **Pod状态(3)**字段将显示**恢复输注**信息，表明RileyLink正在向暂停中的pod发送该指令。
>  
-2. When the Resume delivery command is successfully confirmed by the RileyLink a confirmation dialog will display the message **Insulin delivery has been resumed**. Click **OK** to confirm and proceed.
+2. 当RileyLink成功确认恢复输注指令后，将显示确认对话框，内容为**胰岛素输注已恢复**。 点击**确定**进行确认并继续操作。
> 
-3. The **Omnipod (POD)** tab will update the **Pod status (1)** field to display **RUNNING,** and the **Resume Delivery** button will now display the **SUSPEND (2)** button.
+3. **Omnipod(POD)**标签页将更新**Pod状态(1)**字段显示为**运行中**，同时**恢复输注**按钮将变回显示**暂停(2)**按钮。
> 
-### Acknowledging Pod Alerts
+### 确认Pod警报
-*NOTE - if you do not see an ACK ALERTS button, it is because it is conditionally displayed on the Omnipod (POD) tab ONLY when the pod expiration or low reservoir alert has been triggered.*
+*注意 - 若未显示"确认警报"按钮，是因为该按钮仅在触发pod过期或储药器低量警报时，才会在Omnipod(POD)标签页中条件性显示。*
-The process below will show you how to acknowledge and dismiss pod beeps that occur when the active pod time reaches the warning time limit before the pod expiration of 72 hours (3 days). This warning time limit is defined in the **Hours before shutdown** Omnipod alerts setting. The maximum life of a pod is 80 hours (3 days 8 hours), however Insulet recommends not exceeding the 72 hour (3 days) limit.
+以下流程将指导您如何确认并消除活动pod在72小时(3天)有效期临近时发出的警报提示音。 此警告时限由Omnipod警报设置中的**关机前小时数**定义。 Pod最长使用寿命为80小时(3天8小时)，但Insulet建议不要超过72小时(3天)的限制。
-*NOTE - If you have enabled the "Automatically acknowledge Pod alerts" setting in Omnipod Alerts, this alert will be handled automatically after the first occurrence and you will NOT need to manually dismiss the alert.*
+*注意 - 若您已在Omnipod警报设置中启用"自动确认Pod警报"功能，该警报将在首次触发后自动处理，您无需手动消除警报。*
-1. When the defined **Hours before shutdown** warning time limit is reached, the pod will issue warning beeps to inform you that it is approaching its expiration time and a pod change will soon be required. You can verify this on the **Omnipod (POD)** tab, the **Pod expires: (1)** field will show the exact time the pod will expire (72 hours after activation) and the text will turn **red** after this time has passed, under the **Active Pod alerts (2)** field where the status message **Pod will expire soon** is displayed. This trigger will display the **ACK ALERTS (3)** button. A **system notification (4)** will also inform you of the upcoming pod expiration
+1. 当达到设定的**关机前小时数**警告时限时，pod将发出提示音，告知您其即将到期，需要尽快更换pod。 您可在**Omnipod(POD)**标签页核实：**Pod到期时间：(1)**字段会显示pod失效的具体时间（激活后72小时），超时后文字将变为**红色**；同时在**活动Pod警报(2)**字段下会显示状态信息**Pod即将到期**。 此时将显示**确认警报(3)**按钮。 系统通知(4)也会提醒您pod即将到期
>  
-2. Go to the **Omnipod (POD)** tab and press the **ACK ALERTS (2)** button (acknowledge alerts). The RileyLink sends the command to the pod to deactivate the pod expiration warning beeps and updates the **Pod status (1)** field with **ACKNOWLEDGE ALERTS**.
+2. 请前往**Omnipod(POD)**标签页，点击**确认警报(2)**按钮（确认警报）。 RileyLink向pod发送指令以停用pod到期警告提示音，并将**Pod状态(1)**字段更新为**已确认警报**。
> 
-3. Upon **successful deactivation** of the alerts, **2 beeps** will be issued by the active pod and a confirmation dialog will display the message **Activate alerts have been acknowledged**. Click the **OK** button to confirm and dismiss the dialog.
+3. 当警报**成功停用**后，活动pod会发出**2声提示音**，并显示确认对话框，内容为**活动警报已确认**。 点击**确定**按钮确认并关闭对话框。
> 
>
- > If the RileyLink is out of range of the pod while the acknowledge alerts command is being processed a warning message will display 2 options. **Mute (1)** will silence this current warning. **OK (2)** will confirm this warning and allow the user to try to acknowledge alerts again.
+ > 当确认警报指令处理期间RileyLink超出pod通信范围时，系统将显示包含2个选项的警告信息。 **静音(1)**将消除当前警告提示音。 **确定(2)**将确认此警告，并允许用户再次尝试确认警报。
>
> 
-4. Go to the **Omnipod (POD)** 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.
+4. 警报显示无法验证 **SMB** 追加剂量命令是否成功，您需要验证 OMNIPOD 选项卡中的“上次追加剂量”字段，以查看 **SMB** 追加剂量是否成功，如果未成功，请从治疗中删除该条目。请前往<0>Omnipod(POD)标签页，<0>活动Pod警报字段下已不再显示警告信息，且活动pod将不再发出到期警告提示音。
(OmnipodEros-view-pod-history)=
-### View Pod History
+### 查看 Pod 历史
-This section shows you how to review your active pod history and filter by different action categories. The pod history tool allows you to view the actions and results committed to your currently active pod during its three day (72 - 80 hours) life.
+本部分将向您展示如何查看活动pod的历史记录，并按不同操作类别进行筛选。 Pod历史记录工具可让您查看当前活动pod在其3天(72-80小时)生命周期内执行的操作及结果。
-This feature is useful for verifying boluses, TBRs, basal changes that were given but you may be unsure if they completed. The remaining categories are useful in general for troubleshooting issues and determining the order of events that occurred leading up to a failure.
+此功能可用于验证已执行但您不确定是否完成的大剂量、临时基础率和基础率变更。 其余类别通常有助于故障排查，并确定导致故障的事件发生顺序。
-*NOTE:* **Uncertain** commands will appear in the pod history, however due to their nature you cannot ensure their accuracy.
+*注意：* **不确定**指令会显示在pod历史记录中，但由于其特性，您无法确保其准确性。
-1. Go to the **Omnipod (POD)** tab and press the **POD MGMT (1)** button to access the **Pod management** menu and then press the **Pod history (2)** button to access the pod history screen.
+1. 请前往**Omnipod(POD)**标签页，点击**POD管理(1)**按钮进入**Pod管理**菜单，然后点击**Pod历史记录(2)**按钮访问pod历史记录界面。
>  
-2. On the **Pod history** screen, the default category of **All (1)** is displayed showing the **Date and Time (2)** of all pod **Actions (3)** and **Results (4)** in reverse chronological order. Use your phone’s **back button 2 times** to return to the **Omnipod (POD)** tab in the main AAPS interface.
+2. 在**Pod历史记录**界面中，默认显示**全部(1)**类别，按时间倒序列出所有pod**操作(3)**及其**结果(4)**的**日期和时间(2)**。 按手机**返回键2次**可返回主AAPS界面的**Omnipod(POD)**标签页。
>  
-### View RileyLink Settings and History
+### 查看RileyLink设置与历史记录
-This section shows you how to review the settings of your active pod and RileyLink along with the communication history of each. This feature, once accessed, is split into two sections: **Settings** and **History**.
+本部分将向您展示如何查看活动pod和RileyLink的设置参数，以及各自的通信历史记录。 此功能包含两个部分：**设置**和**历史记录**。
-The primary use of this feature is when your pod communication device is out of the Bluetooth range of your phone after a period of time and the **RileyLink status** reports **RileyLink unreachable**. The **REFRESH** button on the main **Omnipod (POD)** tab will manually attempt to re-establish Bluetooth communication with the currently configured RileyLink in the Omnipod settings.
+该功能主要用于当您的pod通信设备超出手机蓝牙范围一段时间后，**RileyLink状态**显示**RileyLink无法连接**的情况。 主界面**Omnipod(POD)**标签页上的**刷新**按钮会手动尝试与Omnipod设置中当前配置的RileyLink重新建立蓝牙连接。
-In the event the **REFRESH** button on the main **Omnipod (POD)** tab does not restore the connection to the pod communication device, please follow the additional steps below for a manual reconnection.
+若主界面**Omnipod(POD)**标签页的**刷新**按钮未能恢复与pod通信设备的连接，请按照以下步骤进行手动重连。
-#### Manually Re-establish Pod Communication Device Bluetooth Communication
+#### 手动重建Pod通信设备蓝牙连接
-1. From the **Omnipod (POD)** tab when the **RileyLink Status: (1)** reports **RileyLink unreachable** press the **POD MGMT (2)** button to navigate to the **Pod Management** menu. On the **Pod Management** menu you will see a notification appear actively searching for a RileyLink connection, press the **RileyLink stats (3)** button to access the **RileyLink settings** screen.
+1. 当**Omnipod(POD)**标签页的**RileyLink状态：(1)**显示**RileyLink无法连接**时，请点击**POD管理(2)**按钮进入**Pod管理**菜单。 在**Pod管理**菜单中，您将看到系统正在主动搜索RileyLink连接的通知，此时请点击**RileyLink统计(3)**按钮进入**RileyLink设置**界面。
>  
-2. On the **RileyLink Settings (1)** screen under the **RileyLink (2)** section you can confirm both the Bluetooth connection status and error in the **Connection Status and Error: (3)** fields. A *Bluetooth Error* and *RileyLink unreachable* status should be shown. Start the manual Bluetooth reconnection by pressing the **refresh (4)** button in the lower right corner.
+2. 在**RileyLink设置(1)**界面的**RileyLink(2)**区域，您可通过**连接状态与错误：(3)**字段确认蓝牙连接状态及错误信息。 此时应显示*蓝牙错误*和*RileyLink无法连接*状态。 请点击右下角的**刷新(4)**按钮，开始手动重新建立蓝牙连接。
> 
>
- > If the pod communication device is unresponsive or out of range of the phone while the Bluetooth refresh command is being processed a warning message will display 2 options.
+ > 当蓝牙刷新指令处理期间pod通信设备无响应或超出手机通信范围时，系统将显示包含2个选项的警告信息。
- - **Mute (1)** will silence this current warning.
- - **OK (2)** will confirm this warning and allow the user to try to re-establish the Bluetooth connection again.
+ - **静音(1)**将消除当前警告提示音。
+ - **确定(2)**将确认此警告，并允许用户再次尝试重新建立蓝牙连接。
> 
-3. If the **Bluetooth connection** does not re-establish, try manually turning **off** and then back **on** the Bluetooth function on your phone.
+3. 若**蓝牙连接**未能恢复，请尝试手动关闭手机蓝牙功能后再重新开启。
-4. After a successful RileyLink Bluetooth reconnection the **Connection Status: (1)** field should report **RileyLink ready**. Congratulations, you have now reconnected your configured pod communication device to AAPS!
+4. RileyLink蓝牙成功重新连接后，**连接状态：(1)**字段应显示**RileyLink就绪**。 恭喜！您已成功将配置的pod通信设备重新连接至AAPS系统！
> 
-#### Pod Communication Device and Active Pod Settings
+#### Pod通信设备与活动Pod设置
-This screen will provide information, status, and settings configuration information for both the currently configured pod communication device and the currently active Omnipod Eros pod.
+本界面将显示当前配置的pod通信设备及活动中的Omnipod Eros pod相关信息、状态和设置配置。
-1. Go to the **Omnipod (POD)** tab and press the **POD MGMT (1)** button to access the **Pod management** menu, then press the **RileyLink stats (2)** button to view your currently configured **RileyLink (3)** and active pod **Device (4)** settings.
+1. 请前往**Omnipod(POD)**标签页，点击**POD管理(1)**按钮进入**Pod管理**菜单，再点击**RileyLink统计(2)**按钮，即可查看当前配置的**RileyLink(3)**及活动pod**设备(4)**设置。
>  
>
> 
-##### RileyLink (3) fields
+##### RileyLink(3)字段
-> - **Address:** MAC address of the selected pod communication device defined in the Omnipod Settings.
-> - **Name:** Bluetooth identification name of the selected pod communication device defined in your phone's Bluetooth settings.
-> - **Battery Level:** Displays the current battery level of the connected pod communication device
-> - **Connected Device:** Model of the Omnipod pod currently communicating with the pod communication device
-> - **Connection Status**: The current status of the Bluetooth connection between the pod communication device and the phone running AAPS.
-> - **Connection Error:** If there is an error with the pod communication device Bluetooth connection details will be displayed here.
-> - **Firmware Version:** Current firmware version installed on the actively connected pod communication device.
+> - **地址：** Omnipod设置中定义的所选pod通信设备的MAC地址。
+> - **名称：** 手机蓝牙设置中定义的所选pod通信设备的蓝牙标识名称。
+> - **电池电量：** 显示已连接的pod通信设备的当前电量水平
+> - **已连接设备：** 当前与pod通信设备通信的Omnipod pod型号
+> - **连接状态**：pod通信设备与运行AAPS的手机之间的当前蓝牙连接状态。
+> - **连接错误：** 若pod通信设备蓝牙连接存在异常，相关错误详情将在此处显示。
+> - **固件版本：** 当前连接的pod通信设备上安装的固件版本。
-##### Device (4) fields - With an Active Pod
+##### 设备(4)字段 - 使用活动Pod时
-> - **Device Type:** The type of device communicating with the pod communication device (Omnipod pod pump)
-> - **Device Model:** The model of the active device connected to the pod communication device (the current model name of the Omnipod pod, which is Eros)
-> - **Pump Serial Number:** Serial number of the currently activated pod
-> - **Pump Frequency:** Communication radio frequency the pod communication device has tuned to enable communication between itself and the pod.
-> - **Last Used frequency:** Last known radio frequency the pod used to communicate with the pod communication device.
-> - **Last Device Contact:** Date and time of the last contact the pod made with the pod communication device.
-> - **Refresh button** manually refresh the settings on this page.
+> - **设备类型：** 与pod通信设备通信的设备类型（Omnipod pod泵）
+> - **设备型号：** 连接至pod通信设备的激活设备型号（当前Omnipod pod的型号名称，即Eros）
+> - **泵序列号：** 当前激活pod的序列号
+> - **泵频率：** pod通信设备为建立与pod间通信所调谐的无线电频率。
+> - **上次使用频率：** pod与pod通信设备进行通信时最后使用的无线电频率。
+> - **最后设备联系时间：** pod与pod通信设备最后一次建立联系的具体日期和时间。
+> - **刷新按钮** 手动刷新本页面的设置信息。
(omnipod-eros-rileylink-and-active-pod-history)=
-#### RileyLink and Active Pod History
+#### RileyLink与活动Pod历史记录
-This screen provides information in reverse chronological order of each state or action that either the RileyLink or currently connected pod is in or has taken. The entire history is only available for the currently active pod, after a pod change this history will be erased and only events from the newly activated pod will be recorded and shown.
+本界面按时间倒序显示RileyLink或当前连接pod所处的状态或执行的操作信息。 完整历史记录仅适用于当前活动pod，更换pod后该历史将被清空，系统仅记录并显示新激活pod的事件。
-1. Go to the **Omnipod (POD)** tab and press the **POD MGMT (1)** button to access the **Pod Management** menu, then press the **Pod History (2)** button to view the **Settings** and **History** screen. Click on the **HISTORY (3)** text to display the entire history of the RileyLink and currently active pod session.
+1. 请进入**Omnipod(POD)**标签页，点击**POD管理(1)**按钮进入**Pod管理**菜单，再点击**Pod历史(2)**按钮即可查看**设置**与**历史记录**界面。 点击**历史记录(3)**文字可查看RileyLink及当前活动pod会话的完整历史。
>  
>
> 
-##### Fields
+##### 字段
-> - **Date & Time**: In reverse chronological order the timestamp of each event.
-> - **Device:** The device to which the current action or state is referring.
-> - **State or Action:** The current state or action performed by the device.
+> - **日期和时间**：按时间倒序排列的每个事件的时间戳。
+> - **设备：** 当前操作或状态所指向的设备。
+> - **状态或操作：** 设备当前所处的状态或执行的操作。
(OmnipodEros-omnipod-pod-tab)=
-## Omnipod (POD) Tab
+## Omnipod(POD)标签页
-Below is an explanation of the layout and meaning of the icons and status fields on the **Omnipod (POD)** tab in the main AAPS interface.
+以下是对主AAPS界面中**Omnipod(POD)**标签页图标及状态字段布局与含义的说明。
-*NOTE: If any message in the Omnipod (POD) tab status fields report (uncertain) then you will need to press the Refresh button to clear it and refresh the pod status.*
+*注意：如果在Omnipod（POD）选项卡状态字段报告中任何消息显示（不确定），则需要按下刷新按钮以清除该状态并刷新pod状态。*
> 
-### Fields
+### 字段
-- **RileyLink Status:** Displays the current connection status of the RileyLink
+- **RileyLink状态：**显示RileyLink的当前连接状态
-- *RileyLink Unreachable* - pod communication device is either not within Bluetooth range of the phone, powered off or has a failure preventing Bluetooth communication.
-- *RileyLink Ready* - pod communication device is powered on and actively initializing the Bluetooth connection
-- *Connected* - pod communication device is powered on, connected and actively able to communicate via Bluetooth.
+- *RileyLink无法连接* - pod通信设备可能超出手机蓝牙范围、已关机或存在故障导致无法进行蓝牙通信。
+- *RileyLink 准备就绪* - pod 通信设备已开机，正在主动初始化蓝牙连接
+- *已连接* - pod通信设备已开机、连接并可通过蓝牙进行主动通信。
-- **Pod address:** Displays the current address in which the active pod is referenced
+- **Pod地址：**显示当前活动pod被引用的地址
-- **LOT:** Displays the LOT number of the active pod
+- **批号：**显示当前活动pod的批号
-- **TID:** Displays the serial number of the pod.
+- **TID：**显示pod的序列号。
-- **Firmware Version:** Displays the firmware version of the active pod.
+- **固件版本：**显示当前活动pod的固件版本。
-- **Time on Pod:** Displays the current time on the active pod.
+- **Pod时间：**显示当前活动pod的时间。
-- **Pod expires:** Displays the date and time when the active pod will expire.
+- **Pod有效期：**显示当前活动pod的到期日期和时间。
-- **Pod status:** Displays the status of the active pod.
+- **Pod状态：**显示当前活动pod的状态。
-- **Last connection:** Displays the last time communication with the active pod was achieved.
+- **最后连接时间：**显示最近一次与活动pod成功建立通信的时间。
-- *Moments ago* - less than 20 seconds ago.
-- *Less than a minute ago* - more than 20 seconds but less than 60 seconds ago.
-- *1 minute ago* - more than 60 seconds but less than 120 seconds (2 min)
-- *XX minutes ago* - more than 2 minutes ago as defined by the value of XX
+- *刚刚* - 指20秒内的时间。
+- *不到一分钟前* - 超过20秒但不足60秒。
+- *1分钟前* - 超过60秒但不足120秒（2分钟）
+- *XX分钟前* - 超过2分钟，具体时间由XX值确定
-- **Last bolus:** Displays the dosage of the last bolus sent to the active pod and how long ago it was issued in parenthesis.
+- **最后大剂量：**显示最近发送至活动pod的大剂量数值，括号内显示该剂量发出的时间间隔。
-- **Base Basal rate:** Displays the basal rate programmed for the current time from the basal rate profile.
+- **基础基础率：**显示当前时间根据基础率配置文件设定的基础输注速率。
-- **Temp basal rate:** Displays the currently running Temporary Basal Rate in the following format
+- **临时基础率：**以下列格式显示当前运行的临时基础率：
-- Units / hour @ time TBR was issued (minutes run / total minutes TBR will be run)
-- *Example:* 0.00U/h @18:25 ( 90/120 minutes)
+- 单位/小时 @ 临时基础率设定时间（已运行分钟数/临时基础率总运行分钟数）
+- *示例：* 0.00U/h @18:25 (90/120分钟)
-- **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below this value the exact units are displayed in yellow text.
+- **储药量：**当储药器剩余药量超过50单位时，显示"50+单位剩余"。 低于此值时，将以黄色文字显示精确单位值。
-- **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. *Note this is an approximation as priming and filling the pod is not an exact process.*
+- **总输注量：**显示储药器已输送的胰岛素总量（单位）。 *请注意这是近似值，因为pod的灌注和填充并非精确过程。*
-- **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history), [RileyLink history](#omnipod-eros-rileylink-and-active-pod-history) and log files for past errors and more detailed information.
+- **错误信息：**显示最近发生的错误。 检查[Pod历史记录](#view-pod-history)、[RileyLink历史记录](#omnipod-eros-rileylink-and-active-pod-history)以及日志文件，以查看过往错误和更详细信息。
-- **Active pod alerts:** Reserved for currently running alerts on the active pod. Normally used when pod expiration is past 72 hours and native pod beep alerts are running.
+- **活动储药器警报：** 保留用于当前活动储药器上正在运行的警报。 通常用于当pod超过72小时有效期且设备原生蜂鸣警报正在运行时。
-### Icons
+### 图标
-- **REFRESH:**
+- **刷新：**
> 
>
- > Sends a refresh command to the active pod to update communication
+ > 向当前活动pod发送刷新命令以更新通信
>
- > Use to refresh the pod status and dismiss status fields that contain the text (uncertain).
+ > 用于刷新储药器状态并清除显示（不确定）的状态字段。
>
- > See the [Troubleshooting section](#troubleshooting) below for additional information.
+ > 请参阅下方[故障排除章节](#troubleshooting)获取更多信息。
-- **POD MGMT:**
+- **POD管理：**
> 
>
- > Navigates to the Pod management menu
+ > 跳转至Pod管理菜单
-- **ACK ALERTS:**
+- **确认警报：**
> 
>
- > When pressed this will disable the pod expiration beeps and notifications.
+ > 按下此按钮将禁用pod过期蜂鸣声和通知。
>
- > Button is displayed only when pod time is past expiration warning time Upon successful dismissal, this icon will no longer appear.
+ > 该按钮仅在pod时间超过过期警告时间时显示 成功解除后，此图标将不再出现。
-- **SET TIME:**
+- **设置时间：**
> 
>
- > When pressed this will update the time on the pod with the current time on your phone.
+ > 按下此按钮将使用您手机的当前时间更新pod上的时间。
-- **SUSPEND:**
+- **暂停:**
- > 
+ > 
>
- > Suspends the active pod
+ > 暂停当前活动pod
-- **RESUME DELIVERY:**
+- **恢复输注：**
- > 
+ > 
>
- > > Resumes the currently suspended, active pod
+ > > 恢复当前暂停的活动pod
-### Pod Management Menu
+### Pod 管理菜单
-Below is an explanation of the layout and meaning of the icons on the **Pod Management** menu accessed from the **Omnipod (POD)** tab.
+以下是关于从**Omnipod (POD)**选项卡进入的**Pod管理**菜单中图标布局和含义的说明。
> 
@@ -491,307 +491,307 @@ Below is an explanation of the layout and meaning of the icons on the **Pod Mana
> 
>
- > Primes and activates a new pod
+ > 对新pod进行灌注和激活
- **停用Pod**
> 
>
- > Deactivates the currently active pod.
+ > 停用当前活动的pod。
>
- > A partially paired pod ignores this command.
+ > 部分配对的pod会忽略此命令。
>
- > Use this command to deactivate a screaming pod (error 49).
+ > 使用此命令可停用发出警报声的pod（错误代码49）。
>
- > If the button is disabled (greyed out) use the Discard Pod button.
+ > 如果该按钮被禁用（显示为灰色），请使用"废弃Pod"按钮。
-- **Play test beep**
+- **播放测试蜂鸣音**
> 
>
- > Plays a single test beep on the pod when pressed.
+ > 按下时会在pod上播放一次测试蜂鸣音。
-- **Discard pod**
+- **废弃pod**
> 
>
- > Deactivates and discards the pod state of an unresponsive pod when pressed.
+ > 按下时将停用并清除无响应pod的状态。
>
- > Button is only displayed when very specific cases are met as proper deactivation is no longer possible:
+ > 该按钮仅在满足特定条件时显示（当无法正常停用时）：
>
- > > - A **pod is not fully paired** and thus ignores deactivate commands.
- > > - A **pod is stuck** during the pairing process between steps
- > > - A **pod simply does not pair at all.**
+ > > - 一个**pod未完全配对**，因此会忽略停用命令。
+ > > - 一个**pod卡在**配对过程中的步骤之间
+ > > - 一个**pod完全无法配对。**
-- **Pod history**
+- **Pod历史记录**
> 
>
- > Displays the active pod activity history
+ > 显示活动pod的历史记录
-- **RileyLink stats:**
+- **RileyLink状态：**
> 
>
- > Navigates to the RileyLink Statistics screen displaying current settings and RileyLink Connection history
+ > 跳转至RileyLink统计界面，显示当前设置和RileyLink连接历史记录
>
- > > - **Settings** - displays RileyLink and active pod settings information
- > > - **History** - displays RileyLink and Pod communication history
+ > > - **设置** - 显示RileyLink和活动pod的设置信息
+ > > - **历史记录** - 显示RileyLink与Pod的通信历史
-- **Reset RileyLink Config**
+- **重置RileyLink配置**
> 
>
- > When pressed this button resets the currently connected pod communication device configuration.
+ > 按下此按钮将重置当前连接的pod通信设备配置。
>
- > > - When communication is started, specific data is sent to and set in the RileyLink > - Memory Registers are set > - Communication Protocols are set > - Tuned Radio Frequency is set
- > > - See [additional notes](#OmnipodEros-reset-rileylink-config-notes) at the end of this table
+ > > - 当通信启动时，特定数据将被发送并设置到RileyLink中 > - 设置内存寄存器 > - 设置通信协议 > - 设置调谐射频
+ > > - 请参阅本表格末尾的[补充说明](#OmnipodEros-reset-rileylink-config-notes)
-- **Read pulse log:**
+- **读取脉冲日志：**
> 
>
- > > Sends the active pod pulse log to the clipboard
+ > > 将活动pod的脉冲日志发送到剪贴板
(OmnipodEros-reset-rileylink-config-notes)=
-#### *Reset RileyLink Config Notes*
+#### *重置RileyLink配置说明*
-- The primary usage of this feature is when the currently active pod communication device is not responding and communication is in a stuck state.
-- If the pod communication device is turned off and then back on, the **Reset RileyLink Config** button needs to be pressed, so that it sets these communication parameters in the pod communication device configuration.
-- If this is NOT done then AAPS will need to be restarted after the pod communication device is power cycled.
-- This button **DOES NOT** need to be pressed when switching between different pod communication devices
+- 此功能主要用于当前活动的pod通信设备无响应且通信处于卡死状态时。
+- 如果pod通信设备关闭后又重新开启，则需要按下**重置RileyLink配置**按钮，以便在pod通信设备配置中设置这些通信参数。
+- 如未执行此操作，则在pod通信设备完成电源循环后必须重新启动AAPS。
+- 在不同pod通信设备之间切换时**无需**按下此按钮
(OmnipodEros-omnipod-settings)=
-## Omnipod Settings
+## Omnipod设置
-The Omnipod driver settings are configurable from the top-left hand corner **hamburger menu** under **Config Builder**➜**Pump**➜**Omnipod**➜**Settings Gear (2)** by selecting the **radio button (1)** titled **Omnipod**. Selecting the **checkbox (3)** next to the **Settings Gear (2)** will allow the Omnipod menu to be displayed as a tab in the AAPS interface titled **OMNIPOD** or **POD**. This is referred to in this documentation as the **Omnipod (POD)** tab.
+Omnipod驱动设置可通过左上角**汉堡菜单**中的**配置构建器**➜**泵**➜**Omnipod**➜**设置齿轮图标(2)**进行配置，选择标有**Omnipod**的**单选按钮(1)**即可。 勾选**设置齿轮图标(2)**旁边的**复选框(3)**，将使Omnipod菜单以**OMNIPOD**或**POD**标签页形式显示在AAPS界面中。 本文档中将其称为**Omnipod(POD)**标签页。
-**NOTE:** A faster way to access the **Omnipod settings** is by accessing the **3 dot menu (1)** in the upper right hand corner of the **Omnipod (POD)** tab and selecting **Omnipod preferences (2)** from the dropdown menu.
+**注意：** 访问**Omnipod设置**的快捷方式是通过点击**Omnipod(POD)**标签页右上角的**三点菜单(1)**，然后从下拉菜单中选择**Omnipod首选项(2)**。
-The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below:
+以下是设置分组列表，您可通过切换开关启用或禁用下文所述的大多数选项：
-*NOTE: An asterisk (\*) denotes the default for a setting is enabled.*
+*注意：星号(*)表示该设置的默认状态为启用。*
### RileyLink
-Allows for scanning of a pod communication device. The Omnipod driver cannot select more than one pod communication device at a time.
+允许扫描pod通信设备。 Omnipod驱动一次只能选择一个pod通信设备。
-- **Show battery level reported by OrangeLink/EmaLink/DiaLink:** Reports the actual battery level of the OrangeLink/EmaLink/Dialink. It is **strongly recommended** that all OrangeLink/EmaLink/DiaLink users enable this setting.
+- **显示OrangeLink/EmaLink/DiaLink报告的电池电量：** 报告OrangeLink/EmaLink/DiaLink的实际电池电量。 **强烈建议**所有OrangeLink/EmaLink/DiaLink用户启用此设置。
-- DOES NOT work with the original RileyLink.
-- May not work with RileyLink alternatives.
-- Enabled - Reports the current battery level for supported pod communication devices.
-- Disabled - Reports a value of n/a.
+- 不适用于原始RileyLink。
+- 可能不适用于RileyLink替代设备。
+- 启用 - 报告支持的pod通信设备的当前电池电量。
+- 禁用 - 报告值为"不适用"。
-- **Enable battery change logging in Actions:** In the Actions menu, the battery change button is enabled IF you have enabled this setting AND the battery reporting setting above. Some pod communication devices now have the ability to use regular batteries which can be changed. This option allows you to note that and reset battery age timers.
+- **在操作菜单中启用电池更换记录：** 若您已启用此设置及上述电池报告设置，则操作菜单中的电池更换按钮将被激活。 某些pod通信设备现在可以使用可更换的普通电池。 此选项可让您记录更换时间并重置电池使用计时器。
-### Confirmation beeps
+### 确认提示音
-Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes.
+提供储药器对大剂量注射、基础率、超微大剂量(SMB)和临时基础率(TBR)输送及变更的确认提示音。
-- **\*Bolus beeps enabled:** Enable or disable confirmation beeps when a bolus is delivered.
-- **\*Basal beeps enabled:** Enable or disable confirmation beeps when a new basal rate is set, active basal rate is canceled or current basal rate is changed.
-- **\*SMB beeps enabled:** Enable or disable confirmation beeps when a SMB is delivered.
-- **TBR beeps enabled:** Enable or disable confirmation beeps when a TBR is set or canceled.
+- ***启用大剂量提示音：** 设置是否在大剂量给药时播放确认提示音。
+- ***基础率提示音启用：** 设置是否在以下情况播放确认提示音：新基础率设定时、活动基础率取消时或当前基础率变更时。
+- ***超微大剂量提示音启用：** 设置是否在超微大剂量给药时播放确认提示音。
+- **启用临时基础率提示音：** 控制设置或取消临时基础率(TBR)时是否发出确认提示音。
### 警报
-Provides AAPS alerts and Nightscout announcements for pod expiration, shutdown, low reservoir based on the defined threshold units.
+当pod到期、关机或根据设定的阈值单位检测到储药器药量不足时，提供AAPS警报和Nightscout通知。
-*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. To MANUALLY dismiss the alert you must visit the Omnipod (POD) tab and press the ACK ALERTS button.*
+*请注意：自警报触发后与储药器首次通信时，AAPS将始终针对任何警报发出通知。 除非启用"自动确认储药器警报"功能，否则仅消除通知并不会消除警报状态。 要手动消除警报，必须访问Omnipod(POD)标签页并按下"确认警报"按钮。*
-- **\*Expiration reminder enabled:** Enable or disable the pod expiration reminder set to trigger when the defined number of hours before shutdown is reached.
-- **Hours before shutdown:** Defines the number hours before the active pod shutdown occurs, which will then trigger the expiration reminder alert.
-- **\*Low reservoir alert enabled:** Enable or disable an alert when the pod's remaining units low reservoir limit is reached as defined in the Number of units field.
-- **Number of units:** The number of units at which to trigger the pod low reservoir alert.
-- **Automatically acknowledge Pod alerts:** When enabled a notification will still be issued however immediately after the first pod communication contact since the alert was issued it will now be automatically acknowledged and the alert will be dismissed.
+- ***启用到期提醒：** 设置是否在达到关机前设定小时数时触发pod到期提醒。
+- **关机前小时数：** 设定活动储药器关机前触发过期提醒警报的小时数。
+- ***启用低药量警报：** 设置当pod剩余药量达到"单位数"字段中定义的低药量限制时是否触发警报。
+- **单位数值：** 触发储药器低药量警报的剩余药量单位数。
+- **自动确认Pod警报：** 启用后仍会发出通知，但在警报触发后首次与Pod建立通信连接时，系统将自动确认并消除该警报。
### 通知
-Provides AAPS notifications and audible phone alerts when it is uncertain if TBR, SMB, or bolus events were successful.
+当不确定临时基础率(TBR)、超微大剂量(SMB)或大剂量给药是否成功时，提供AAPS通知和手机声音警报。
-*NOTE: These are notifications only, no audible beep alerts are made.*
+*注：这些仅为手机通知，不会触发储药器声音提示。*
-- **Sound for uncertain TBR notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when AAPs is uncertain if a TBR was successfully set.
-- **\*Sound for uncertain SMB notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when AAPS is uncertain if an SMB was successfully delivered.
-- **\*Sound for uncertain bolus notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when AAPS is uncertain if a bolus was successfully delivered.
+- **不确定TBR通知的声音已启用:** 启用或禁用此设置，当AAPs不确定是否成功设置TBR时，触发声音警报和视觉通知。
+- ***不确定超微大剂量通知的声音已启用:** 启用或禁用此设置，当AAPS不确定是否成功输注超微大剂量时，触发声音警报和视觉通知。
+- ***不确定大剂量通知的声音已启用:** 启用或禁用此设置，当AAPS不确定是否成功输注大剂量时，触发声音警报和视觉通知。
### 其他
-Provides advanced settings to assist debugging.
+提供高级设置以协助调试。
-- **Show Suspend Delivery button in Omnipod tab:** Hide or display the suspend delivery button in the **Omnipod (POD)** tab.
-- **Show Pulse log button in Pod Management menu:** Hide or display the pulse log button in the **Pod Management** menu.
-- **Show RileyLink Stats button in Pod Management menu:** Hide or display the RileyLink Stats button in the **Pod Management** menu.
-- **\*DST/Time zone detect on enabled:** allows for time zone changes to be automatically detected if the phone is used in an area where DST is observed.
+- **在Omnipod标签页显示暂停输注按钮:** 在**Omnipod (POD)**标签页隐藏或显示暂停输注按钮。
+- **在Pod管理菜单中显示脉冲日志按钮:** 在**Pod管理**菜单中隐藏或显示脉冲日志按钮。
+- **在Pod管理菜单中显示RileyLink统计按钮:** 在**Pod管理**菜单中隐藏或显示RileyLink统计按钮。
+- ***启用夏令时/时区检测:** 当手机在实行夏令时的地区使用时，可自动检测时区变化。
-### Switching or Removing an Active Pod Communication Device (RileyLink)
+### 切换或移除正在使用的Pod通讯设备(RileyLink)
-With many alternative models to the original RileyLink available (such as OrangeLink or EmaLink) or the need to have multiple/backup versions of the same pod communication device (RileyLink), it becomes necessary to switch or remove the selected pod communication device (RileyLink) from Omnipod Setting configuration.
+随着原始RileyLink的多种替代型号(如OrangeLink或EmaLink)的出现，或需要拥有相同Pod通讯设备(RileyLink)的多个/备用版本，从Omnipod设置配置中切换或移除选定的Pod通讯设备(RileyLink)变得必要。
-The following steps will show how to **Remove** and existing pod communication device (RileyLink) as well as **Add** a new pod communication device. Executing both **Remove** and **Add** steps will switch your device.
+以下步骤将展示如何**移除**现有Pod通讯设备(RileyLink)以及**添加**新的Pod通讯设备。 执行**移除**和**添加**两个步骤将切换您的设备。
-1. Access the **RileyLink Selection** menu by selecting the **3 dot menu (1)** in the upper right hand corner of the **Omnipod (POD)** tab and selecting **Omnipod preferences (2)** from the dropdown menu. On the **Omnipod Settings** menu under **RileyLink Configuration (3)** press the **Not Set** (if no device is selected) or **MAC Address** (if a device is present) text to open the **RileyLink Selection** menu.
+1. 进入**RileyLink选择**菜单：点击**Omnipod(POD)**标签页右上角的**三点菜单(1)**，然后从下拉菜单中选择**Omnipod偏好设置(2)**。 在**Omnipod设置**菜单的**RileyLink配置(3)**下，点击**未设置**(若未选择设备)或**MAC地址**(若已选择设备)文字，打开**RileyLink选择**菜单。
>  
-### Remove Currently Selected Pod Communication Device (RileyLink)
+### 移除当前选定的Pod通讯设备(RileyLink)
-This process will show how to remove the currently selected pod communication device (RileyLink) from the Omnipod Driver settings.
+此流程将展示如何从Omnipod驱动设置中移除当前选定的Pod通讯设备(RileyLink)。
-1. Under **RileyLink Configuration** press the **MAC Address (1)** text to open the **RileyLink Selection** menu.
+1. 在**RileyLink配置**下，点击**MAC地址(1)**文字打开**RileyLink选择**菜单。
> 
-2. On the **RileyLink Selection** menu the press **Remove (2)** button to remove **your currently selected RileyLink (3)**
+2. 在**RileyLink选择**菜单中，点击**移除(2)**按钮以移除**当前选定的RileyLink(3)**
> 
-3. At the confirmation prompt press **Yes (4)** to confirm the removal of your device.
+3. 在确认提示中点击**是(4)**以确认移除您的设备。
> 
-4. You are returned to the **Omnipod Setting** menu where under **RileyLink Configuration** you will now see the device is **Not Set (5)**. Congratulations, you have now successfully removed your selected pod communication device.
+4. 您已返回**Omnipod设置**菜单，在**RileyLink配置**下现在会看到设备状态为**未设置(5)**。 恭喜，您已成功移除选定的Pod通讯设备。
> 
-### Add Currently Selected Pod Communication Device (RileyLink)
+### 添加当前选定的Pod通讯设备(RileyLink)
-This process will show how to add a new pod communication device to the Omnipod Driver settings.
+此流程将展示如何向Omnipod驱动设置中添加新的Pod通讯设备。
-1. Under **RileyLink Configuration** press the **Not Set (1)** text to open the **RileyLink Selection** menu.
+1. 在**RileyLink配置**下，点击**未设置(1)**文字打开**RileyLink选择**菜单。
> 
-2. Press the **Scan (2)** button to start scanning for all available Bluetooth devices.
+2. 点击**扫描(2)**按钮开始扫描所有可用的蓝牙设备。
> 
-3. Select **your RileyLink (3)** from the list of available devices and you will be returned to the **Omnipod Settings** menu displaying the **MAC Address (4)** of your newly selected device. Congratulations you have successfully selected your pod communication device.
+3. 从可用设备列表中选择**您的RileyLink(3)**，您将返回**Omnipod设置**菜单，此时会显示新选择设备的**MAC地址(4)**。 恭喜，您已成功选择Pod通讯设备。
>  
-## Actions (ACT) Tab
+## 操作 (ACT) 标签页
-This tab is well documented in the main AAPS documentation but there are a few items on this tab that are specific to how the Omnipod pod differs from tube based pumps, especially after the processes of applying a new pod.
+此标签页在主AAPS文档中有详细说明，但有几个项目专门说明Omnipod pod与管式泵的区别，特别是在完成新pod应用流程后的注意事项。
-1. Go to the **Actions (ACT)** tab in the main AAPS interface.
-2. Under the **Careportal (1)** section the following 3 fields will have their **age reset** to 0 days and 0 hours **after each pod change**: **Insulin** and **Cannula**. This is done because of how the Omnipod pump is built and operates. The **pump battery** and **insulin reservoir** are self contained inside of each pod. Since the pod inserts the cannula directly into the skin at the site of the pod application, a traditional tube is not used in Omnipod pumps. *Therefore after a pod change the age of each of these values will automatically reset to zero.* **Pump battery age** is not reported as the battery in the pod will always be more than the life of the pod (maximum 80 hours).
+1. 前往主AAPS界面中的**操作(ACT)**标签页。
+2. 在**Careportal(1)**部分，以下3个字段将在**每次更换pod后**将其**使用时长重置**为0天0小时：**胰岛素**和**套管**。 这是由于Omnipod胰岛素泵的构造和工作原理决定的。 **泵电池**和**胰岛素储药器**均内置于每个储药器单元内部。 由于储药器在敷贴时会直接将输注套管插入皮肤，Omnipod泵不使用传统导管。 *因此更换储药器后，这些数值的使用时长会自动归零。* **泵电池使用时长**不显示报告，因为储药器内置电池的寿命始终超过储药器使用期限（最长80小时）。
> 
-### Levels
+### 余量水平
-**Insulin Level**
+**胰岛素储药量**
-Reporting of the amount of insulin in the Omnipod Eros Pod is not exact. This is because it is not known exactly how much insulin was put in the pod, only that when the 2 beeps are triggered while filling the pod that over 85 units have been injected. A Pod can hold a maximum of 200 units. Priming can also introduce variance as it is not and exact process. With both of these factors, the Omnipod driver has been written to give the best approximation of insulin remaining in the reservoir.
+Omnipod Eros Pod中的胰岛素量报告不精确。 这是因为无法精确知道Pod中注入了多少胰岛素，只能通过填充Pod时触发的2声提示音来判断已注入超过85单位。 单个Pod最多可容纳200单位胰岛素。 初始化过程也可能引入误差，因为这不是一个精确的操作流程。 基于这两个因素，Omnipod驱动程序的编写旨在提供储药器中剩余胰岛素的最佳估算值。
-> - **Above 50 Units** - Reports a value of 50+U when more than 50 units are currently in the reservoir.
-> - **Below 50 Units** - Reports an approximate calculated value of insulin remaining in the reservoir.
-> - **SMS** - Returns value or 50+U for SMS responses
-> - **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units.
+> - **超过50单位** - 当储药器中当前胰岛素量超过50单位时，显示为50+U。
+> - **低于50单位** - 显示储药器中剩余胰岛素的估算值。
+> - **短信查询** - 短信回复将返回实际数值或"50+单位"
+> - **Nightscout** - 当药量超过50单位时，会向Nightscout上传50的数值（14.07及更早版本）。 较新版本在药量超过50单位时将报告"50+"的数值。
-**Battery Level**
+**电池电量**
-Battery level reporting is a setting that can be enabled to return the current battery level of pod communication devices, such as the OrangeLink, EmaLink or DiaLink. The RileyLink hardware is not capable of reporting its battery level. The battery level is reported after each communication with the pod, so when charging a linear increase may not be observed. A manual refresh will update the current battery level. When a supported Pod communication device is disconnected a value of 0% will be reported.
+电池电量报告是一项可启用的设置，用于返回Pod通讯设备（如OrangeLink、EmaLink或DiaLink）的当前电池电量。 RileyLink硬件无法报告其电池电量。 电池电量会在每次与Pod通讯后更新，因此充电时可能不会观察到线性增长。 手动刷新将更新当前电池电量。 当支持的Pod通讯设备断开连接时，将报告0%电量值。
-> - **RileyLink hardware is NOT capable of reporting battery level**
-> - **"Show battery level reported by OrangeLink/EmaLink/DiaLink" Setting MUST be enabled in the Omnipod settings to report battery level values**
-> - **Battery level reporting ONLY works for OrangeLink, EmaLink and DiaLink Devices**
-> - **Battery Level reporting MAY work for other devices (excluding RileyLink)**
-> - **SMS** - Returns current battery level as a response when an actual level exists, a value of n/a will not be returned
-> - **Nightscout** - Battery level is reported when an actual level exists, a value of n/a will not be reported
+> - **RileyLink硬件无法报告电池电量**
+> - **必须在Omnipod设置中启用"显示OrangeLink/EmaLink/DiaLink报告的电池电量"选项才能获取电池电量数值**
+> - **电池电量报告仅适用于OrangeLink、EmaLink和DiaLink设备**
+> - **电池电量报告可能适用于其他设备(RileyLink除外)**
+> - **SMS** - 当存在实际电量时返回当前电池电量作为响应，不会返回n/a值
+> - **Nightscout** - 当存在实际电量时报告电池电量，不会报告n/a值
(OmnipodEros-troubleshooting)=
## 故障排除
-### Pod Failures
+### Pod 故障
-Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. A list of fault codes can be found [here](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause.
+储药器偶尔会因各种问题发生故障，包括储药器自身的硬件问题。 最佳做法是不要向Insulet公司报修，因为AAPS并非官方认可的使用方案。 故障代码列表可[在此处](https://github.com/openaps/openomni/wiki/Fault-event-codes)查看，以帮助确定原因。
-### Preventing error 49 pod failures
+### 预防49号储药器故障
-This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. We recommend users to switch to the Nightscout client to *upload only (Disable sync)* under the **Config Builder**➜**General**➜**NSClient**➜**cog wheel**➜**Advanced Settings** to prevent possible failures.
+该故障与指令对应的储药器状态错误或胰岛素输注指令执行出错有关。 我们建议用户在**配置构建器**➜**通用**➜**NS客户端**➜**齿轮图标**➜**高级设置**下切换为仅上传模式(禁用同步)，以防止可能出现的问题。
-### Pump Unreachable Alerts
+### 泵体失联警报
-It is recommended that pump unreachable alerts be configured to **120 minutes** by going to the top right-hand side three-dot menu, selecting **Preferences**➜**Local Alerts**➜**Pump unreachable threshold \[min\]** and setting this to **120**.
+建议通过右上角三点菜单进入**偏好设置**➜**本地警报**➜**泵不可达阈值[分钟]**，将该值设为**120**来配置泵不可达警报。
(OmnipodEros-import-settings-from-previous-aaps)=
-### Import Settings from previous AAPS
+### 从之前的AAPS导入设置
-Please note that importing settings has the possibility to import an outdated Pod status. As a result, you may lose an active Pod. It is therefore strongly recommended that you **do not import settings while on an active Pod session**.
+请注意：导入设置可能会带入过期的Pod状态信息。 这可能导致您丢失正在使用的Pod。 因此强烈建议**在Pod使用期间不要导入设置**。
-1. Deactivate your pod session. Verify that you do not have an active pod session.
-2. Export your settings and store a copy in a safe place.
-3. Uninstall the previous version of AAPS and restart your phone.
-4. Install the new version of AAPS and verify that you do not have an active pod session.
-5. Import your settings and activate your new pod.
+1. 停用您当前的Pod会话。 确认您没有正在使用的Pod会话。
+2. 请导出您的设置文件并妥善保存副本。
+3. 卸载旧版AAPS并重启手机。
+4. 安装新版AAPS并确认没有正在使用的Pod会话。
+5. 导入您的设置并激活新Pod。
-### Omnipod driver alerts
+### Omnipod驱动警报
-please note that the Omnipod driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. A summary of the main alerts that you may encounter is listed below:
+请注意：Omnipod驱动程序在**概览标签页**会显示多种独特警报，其中大部分为信息类警报可忽略，但部分警报会提示用户需采取相应操作来解决触发警报的原因。 以下是您可能会遇到的主要警报摘要：
-#### No active Pod
+#### 无活动Pod
-No active Pod session detected. This alert can temporarily be dismissed by pressing **SNOOZE** but it will keep triggering as long as a new pod has not been activated. Once activated this alert is automatically silenced.
+未检测到活动的Pod会话。 该警报可通过点击**暂缓**临时关闭，但在新储药器激活前将持续触发。 该警报激活后将自动静音。
-#### Pod suspended
+#### Pod已暂停
-Informational alert that Pod has been suspended.
+提示性警报：Pod已暂停。
-#### Setting basal profile failed. Delivery might be suspended! Please manually refresh the Pod status from the Omnipod tab and resume delivery if needed..
+#### 基础率配置文件设置失败。 输注可能已暂停！ 请从Omnipod标签页手动刷新储药器状态，必要时恢复输注。
-Informational alert that the Pod basal profile setting has failed, and you will need to hit *Refresh* on the Omnipod tab.
+提示性警报：Pod基础率配置文件设置失败，您需要在Omnipod标签页点击*刷新*。
-#### Unable to verify whether SMB bolus succeeded. If you are sure that the Bolus didn't succeed, you should manually delete the SMB entry from Treatments.
+#### 无法确认超微大剂量是否成功输注。 若确认大剂量未成功输注，请手动从治疗记录中删除该条超微大剂量记录。
-Alert that the SMB bolus success could not be verified, you will need to verify the *Last bolus* field on the Omnipod tab to see if SMB bolus succeeded and if not remove the entry from the Treatments tab.
+警报：无法确认超微大剂量是否成功输注，您需要检查Omnipod标签页的*最后大剂量*字段确认输注状态，若失败需在治疗记录页删除该条目。
-#### Uncertain if "task bolus/TBR/SMB" completed, please manually verify if it was successful.
+#### 无法确认"任务大剂量/临时基础率/超微大剂量"是否完成，请人工核验操作结果。
-Due to the way that the RileyLink and Omnipod communicate, situations can occur where it is *uncertain* if a command was successfully processed. The need to inform the user of this uncertainty was necessary.
+由于RileyLink与Omnipod的通讯特性，可能出现*无法确定*指令是否成功执行的情况。 必须告知用户存在这种不确定性。
-Below are a few examples of when an uncertain notification can occur.
+以下是可能触发不确定通知的几种情况示例。
-- **Boluses** - Uncertain boluses cannot be automatically verified. The notification will remain until the next bolus but a manual pod refresh will clear the message. *By default alerts beeps are enabled for this notification type as the user will manually need to verify them.*
-- **TBRs, Pod Statuses, Profile Switches, Time Changes** - a manual pod refresh will clear the message. By default alert beeps are disabled for this notification type.
-- **Pod Time Deviation -** When the time on the pod and the time your phone deviates too much then it is difficult for AAPS loop to function and make accurate predictions and dosage recommendations. If the time deviation between the pod and the phone is more than 5 minutes then AAPS will report the pod is in a Suspended state under Pod status with a HANDLE TIME CHANGE message. An additional **Set Time** icon will appear at the bottom of the Omnipod (POD) tab. Clicking Set Time will synchronize the time on the pod with the time on the phone and then you can click the RESUME DELIVERY button to continue normal pod operations.
+- **大剂量** - 无法自动验证不确定的大剂量输注。 该通知将持续到下次大剂量输注，但手动刷新Pod可清除该消息。 *默认情况下，此类通知会启用警报提示音，因为需要用户手动进行确认。*
+- **临时基础率、Pod状态、配置文件切换、时间变更** - 手动刷新Pod可清除该消息。 默认情况下，此类通知类型禁用警报提示音。
+- **Pod时间偏差 -** 当Pod时间与手机时间偏差过大时，AAPS循环系统将难以正常运行并做出准确的预测和剂量建议。 若Pod与手机时间偏差超过5分钟，AAPS将在Pod状态中报告Pod处于暂停状态，并显示"处理时间变更"提示信息。 Omnipod（POD）标签页底部将额外显示**设置时间**图标。 点击"设置时间"将使Pod时间与手机同步，之后可点击"恢复输注"按钮继续正常Pod操作。
-## Best Practices
+## 最佳实践
(OmnipodEros-optimal-omnipod-and-rileylink-positioning)=
-### Optimal Omnipod and RileyLink Positioning
+### Omnipod与RileyLink的最佳摆放位置
-The antenna used on the RileyLink to communicate with an Omnipod pod is a 433 MHz helical spiral antenna. Due to its construction properties it radiates an omni directional signal like a three dimensional doughnut with the z-axis representing the vertical standing antenna. This means that there are optimal positions for the RileyLink to be placed, especially during pod activation and deactivation routines.
+RileyLink用于与Omnipod Pod通信的天线是433 MHz螺旋天线。 由于其结构特性，它辐射出全向信号，就像一个三维环形，z轴代表垂直立式天线。 这意味着RileyLink存在最佳摆放位置，特别是在Pod激活和停用过程中。
-> *(Fig 1. Graphical plot of helical spiral antenna in an omnidirectional pattern*)
+> *（图1. 螺旋天线全向辐射模式图示*）
-Because of both safety and security concerns, pod *activation* has to be done at a range *closer (~30 cm away or less)* than other operations such as giving a bolus, setting a TBR or simply refreshing the pod status. Due to the nature of the signal transmission from the RileyLink antenna it is NOT recommended to place the pod directly on top of or right next to the RileyLink.
+出于安全和保密考虑，Pod*激活*操作需在*较近距离（约30厘米以内）*完成，该距离要求比其他操作（如输注大剂量、设置临时基础率或单纯刷新Pod状态）更为严格。 由于RileyLink天线的信号传输特性，不建议将Pod直接放置在RileyLink正上方或紧贴其旁边。
-The image below shows the optimal way to position the RileyLink during pod activation and deactivation procedures. The pod may activate in other positions but you will have the most success using the position in the image below.
+下图展示了Pod激活和停用过程中RileyLink的最佳摆放方式。 Pod在其他位置也可能激活，但采用下图所示位置的成功率最高。
-*Note: If after optimally positioning the pod and RileyLink communication fails, this may be due to a low battery which decreases the transmission range of the RileyLink antenna. To avoid this issue make sure the RileyLink is properly charged or connected directly to a charging cable during this process.*
+*注：若在最佳摆放位置下仍出现Pod与RileyLink通信失败，可能是电池电量不足导致天线传输范围缩小。 为避免此问题，请确保RileyLink在此过程中电量充足或直接连接充电线。*
-## Where to get help for Omnipod driver
+## Omnipod驱动相关问题求助渠道
-All of the development work for the Omnipod driver is done by the community on a volunteer basis; we ask that you please be considerate and use the following guidelines when requesting assistance:
+Omnipod驱动的所有开发工作均由社区志愿者完成；请您在寻求帮助时遵循以下准则并保持体谅：
-- **Level 0:** Read the relevant section of this documentation to ensure you understand how the functionality with which you are experiencing difficulty is supposed to work.
-- **Level 1:** If you are still encountering problems that you are not able to resolve by using this document, then please go to the *#androidaps* channel on **Discord** by using [this invite link](https://discord.gg/4fQUWHZ4Mw).
-- **Level 2:** Search existing issues to see if your issue has already been reported; if not, please create a new [issue](https://github.com/nightscout/AndroidAPS/issues) and attach your [log files](../GettingHelp/AccessingLogFiles.md).
-- **Be patient - most of the members of our community consist of good-natured volunteers, and solving issues often requires time and patience from both users and developers.**
+- **第0级：**查阅本文档相关章节，确保您已理解遇到问题的功能模块的正确运作方式。
+- **第一级：** 若使用本文档仍无法解决问题，请通过[此邀请链接](https://discord.gg/4fQUWHZ4Mw)加入**Discord**平台的*#androidaps*频道寻求帮助。
+- **第二级：** 请先搜索现有问题，确认您的问题是否已被报告；若未发现相同问题，请新建[问题报告](https://github.com/nightscout/AndroidAPS/issues)并附上[日志文件](../GettingHelp/AccessingLogFiles.md)。
+- **请保持耐心——我们社区成员多为热心志愿者，问题的解决往往需要用户和开发者双方投入时间与耐心。**
diff --git a/docs/CROWDIN/zh_CN/DailyLifeWithAaps/Automations.md b/docs/CROWDIN/zh_CN/DailyLifeWithAaps/Automations.md
index c85c8125883f..560b3aea3c19 100644
--- a/docs/CROWDIN/zh_CN/DailyLifeWithAaps/Automations.md
+++ b/docs/CROWDIN/zh_CN/DailyLifeWithAaps/Automations.md
@@ -112,7 +112,7 @@
在选择**自动操作**中的负值时请小心。
```
-在选择“条件”中的负值（如“小于”）时需要谨慎。 For example:
+在选择“条件”中的负值（如“小于”）时需要谨慎。 例如：
diff --git a/docs/CROWDIN/zh_CN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md b/docs/CROWDIN/zh_CN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
index 6397e854f48d..d1d6178a1399 100644
--- a/docs/CROWDIN/zh_CN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
+++ b/docs/CROWDIN/zh_CN/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md
@@ -1,68 +1,68 @@
-# Custom Watchface Reference Document
+# 自定义表盘参考文档
-This page is for designers of new Watchfaces. It will list all the keywords and features available when you want to create or animate a new watchface.
+本页面向新表盘设计师提供参考。 本文将列出创建或制作动态表盘时可用的所有关键词和功能。
-- New features and keys available in Custom Watchface V2 (Wear apk 3.3.0 or above) are available [here](#cwf-reference-new-v2-features)
+- 自定义表盘V2版本（Wear apk 3.3.0及以上）的新功能和按键详见[此处](#cwf-reference-new-v2-features)
-## Custom Watchface Format
+## 自定义表盘格式
-Custom Watchface is an open format designed for AAPS and associated to the new "AAPS (Custom)" watchface available on Watch.
+自定义表盘是为AAPS设计的开放格式，关联至手表端新版"AAPS(自定义)"表盘。
-The Watchface file is a simple zip file, but to be recognized as a Watchface file, the zip file must contain the following files:
+表盘文件为简易zip压缩包，但需包含以下文件才能被识别为表盘文件：
-- One image file named CustomWatchface (can be bitmap files `CustomWatchface.jpg`, `CustomWatchface.png` or a vector `CustomWatchface.svg`). This file is the little icon used to select the watchface when you click on "Load Watchface" button, and also the image visible within AAPS Wear plugin.
-- One file named `CustomWatchface.json` (see [JSON structure](#cwf-reference-json-structure) below). This second file is the core file that will include all information required to design the watchface. This json file must be valid (it's probably the most tricky point when you edit manually this file within a text editor, because a missing or additional comma is enough to break the json format). This JSON file must also include a `"metadata"` block with a `"name"` key with not empty value. This will be the name of your custom watchface (see [Metadata settings](#cwf-reference-metadata-settings) below)
-- the size of this zip should be as small as possible (less than about 500kb). If this file is too big, it will just be blocked and not transmitted to the watch.
+- 一个名为CustomWatchface的图像文件（可为位图`CustomWatchface.jpg`、`CustomWatchface.png`或矢量图`CustomWatchface.svg`）。 该文件是点击"加载表盘"按钮时用于选择表盘的小图标，同时也是AAPS Wear插件中显示的图像。
+- 一个名为`CustomWatchface.json`的文件（参见下文[JSON结构](#cwf-reference-json-structure)）。 该核心文件包含设计表盘所需的全部信息。 该json文件必须格式正确（在文本编辑器中手动编辑时最易出错，缺失或多一个逗号都会破坏json格式）。 该JSON文件必须包含带非空`"name"`键的`"metadata"`区块。 这将作为自定义表盘的名称（参见下文[元数据设置](#cwf-reference-metadata-settings)）
+- 该zip文件应尽可能小（建议小于500KB）。 文件过大将被拦截，无法传输至手表。
-The zip file can also contain some additional resource files:
+zip文件还可包含额外资源文件：
-- Hardcoded file names for images that will be used used in standard views included in the watchface (like `Background`, `CoverChart`... see [List of hardcoded resource files](#cwf-reference-list-of-hardcoded-resource-files) below). All these files can be either `jpg`, `png` or `svg` format. but for most of them, you will have to use `png` or `svg` that manage transparency (jpg are smaller in size compared to png, but with no transparency). Note that the best quality associated to the smallest size will generally be with svg files (vector format).
-- Additional resource files with free names. These additional files can be either image files, or font files (`ttf` and `otf` format are accepted for fonts). Note that for these additional files, the `filename` (without extension) will be used as the keyValue, within JSON file, to specify where or when these files should be used.
- - image files are often used as background of text views or for dynamic animation (like battery level from 0% to 100%)
- - font files allow you to use dedicated fonts within your watchface
+- 表盘标准视图使用的硬编码图像文件名（如`Background`、`CoverChart`...参见下文[硬编码资源文件列表](#cwf-reference-list-of-hardcoded-resource-files)）。 所有文件均可采用`jpg`、`png`或`svg`格式。 但多数情况下需使用支持透明度的`png`或`svg`格式（jpg体积虽小于png但不支持透明）。 请注意，svg文件（矢量格式）通常能实现最佳画质与最小体积的结合。
+- 可自由命名的附加资源文件。 这些附加文件可为图像文件或字体文件（字体支持`ttf`和`otf`格式）。 请注意，这些附加文件的`文件名`（不含扩展名）将作为JSON文件中的keyValue，用于指定其使用位置或时机。
+ - 图像文件常用作文本视图背景或动态动画素材（如电量从0%到100%的变化效果）
+ - 字体文件支持在表盘中使用定制字体
(cwf-reference-json-structure)=
-## JSON Structure
+## JSON 结构
-JSON files can be edited in Notepad (or notepad++) text editor (prefer notepad++ that recognize JSON and use color formatting)
+JSON文件可通过记事本（或notepad++）文本编辑器编辑（推荐能识别JSON并支持彩色格式的notepad++）
-- it contains string keys `"string_key":` and key values that can be strings like `"key value"`, integer, boolean like `true`or `false` or block of data.
-- each value is separated by a comma `,`
-- A block of data starts by `{` and ends by `}`
-- the json file is a whole block so it starts by `{` and ends by `}`, and inside this file all embedded blocks are associated to a `"key"` that should be unique within the block
-- To improve readability of json file, it's generally indented (each new key is on a new line, each new block is shifted on the right by 4 spaces characters)
+- 文件包含字符串键`"string_key":`及键值，键值可为`"key value"`类字符串、整数、`true`/`false`布尔值或数据块。
+- 各键值间用逗号`,`分隔
+- 数据块以`{`开始，以`}`结束
+- json文件整体为数据块，以`{`起始、`}`结束，内部所有嵌套块均通过`"key"`关联（键名在块内须唯一）。
+- 为提升json文件可读性，通常采用缩进格式（每个新键换行显示，每个新块向右缩进4个空格字符）
(cwf-reference-metadata-settings)=
-### Metadata Settings
+### 元数据设置
-This block is the first block included into the json file and is mandatory. It contains all the information associated to this watchface, like the name, the author, the date of creation or update, the author version or the plugin version.
+该区块是json文件中首个且必须包含的区块。 该区块包含与此表盘相关的所有信息，如名称、作者、创建或更新日期、作者版本或插件版本。
-See below an example of metadata block:
+以下是元数据区块示例：
```json
"metadata": {
- "name": "Default Watchface",
- "author": "myName",
- "created_at": "07\/10\/2023",
+ "name": "默认表盘",
+ "author": "我的名字",
+ "created_at": "2023年10月7日",
"author_version": "1.0",
"cwf_version": "1.0",
- "comment": "Default watchface, you can click on EXPORT WATCHFACE button to generate a template"
+ "comment": "默认表盘模板，点击'导出表盘'按钮可生成"
},
```
-Note that `/` used for the date is a special character, so to be recognize correctly within json file, you have to put before an "escape" character `\`
+请注意，日期中的`/`是特殊字符，需在前添加转义符`\`才能被json正确识别。
-You can see in some json file an additional key `"filename"`, this key will be automatically created or updated when the custom watchface will be loaded within AAPS (it will be used to show to the user the zip filename within exports folder), so you can remove this key within metadata block.
+部分json文件中可能含额外键`"filename"`，该键会在自定义表盘加载至AAPS时自动生成或更新（用于在导出文件夹向用户显示zip文件名），因此可从元数据区块中删除此键。
(cwf-reference-general-parameter-settings)=
-### General parameter settings
+### 常规参数设置
-After the first block with metadata, you will set some general parameters (see [List of general parameters](#cwf-reference-list-of-general-parameters) below), this allow you to set Graph colors (Carbs, Bolus, BG values...), and also default colors for value in range, hyper or hypo (default colors of BG value and arrows)
+在首个元数据区块后，需设置常规参数（参见下文[常规参数列表](#cwf-reference-list-of-general-parameters)），用于配置图表颜色（碳水、大剂量、血糖值等）以及范围内/高/低血糖的默认颜色（血糖值及箭头的预设颜色）。
-See below an example of general parameters
+以下是常规参数示例：
```json
"highColor": "#FFFF00",
@@ -78,11 +78,11 @@ See below an example of general parameters
```
(cwf-reference-imageview-settings)=
-### ImageView settings
+### ImageView 设置
-Custom image can be tuned using correct filename associated to each ImageView included into custom watchface Layout, then the json block is only here to define the position, the size, if the view is visible or not, and optionally tune the color:
+自定义图像可通过匹配表盘布局中各ImageView的正确文件名进行调整，json区块仅用于定义位置、尺寸、可见性，并可选择性调整颜色：
-See below an example of an Image block for second_hand, (in this case there are no image included into zip file so default second hand image will be used, but tuned with a custom color.
+以下是秒针(second_hand)的图像区块示例（此例zip未包含图像文件，将使用默认秒针图像但应用自定义颜色）：
```json
"second_hand": {
@@ -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`
+要使秒针(second_hand)显示默认血糖颜色（低/中/高范围），只需将最后一行键值改为`bgColor`即可。
```json
"color": "bgColor"
@@ -102,9 +102,9 @@ To have second_hand colored with default BG color (lowRange, midRange or highRan
(cwf-reference-textview-settings)=
-### TextView settings
+### TextView 设置
-TexView have more available parameters compare to ImageView: you can tune rotation (integer value in degrees), textsize (integer value in pixel), gravity (to define if text value will be centered (default value), or aligned left or right), set the font, fontStyle and fontColor, and also background color of the TextView
+文本视图(TexView)参数比图像视图更丰富：可调整旋转角度（整数值/度）、字号（整数值/像素）、对齐方式（默认居中，可选左/右对齐），并支持设置字体、字型、文字颜色及文本视图背景色。
```json
"basalRate": {
@@ -121,7 +121,7 @@ TexView have more available parameters compare to ImageView: you can tune rotati
"fontColor": "#BDBDBD"
},
```
-Note that if you don't want to manage one view within your watchface, then put the `"visibility"` key to `"gone"` but also set size and position outside visible area like that:
+注意：若需隐藏表盘中的某个视图，除将`"visibility"`设为`"gone"`外，还需将其尺寸和位置调整至可视区域外，例如：
```json
"second": {
@@ -138,23 +138,23 @@ Note that if you don't want to manage one view within your watchface, then put t
"fontColor": "#BDBDBD"
},
```
-If size and position are within visible area, you can get some "flash" of the hidden value during the refresh of the watchface.
+若尺寸和位置位于可视区域内，表盘刷新时可能出现隐藏值的闪烁现象。
-If you want to customize background image of a text view, then you can use the key `"background":` and put the filename of image included into zip file as keyValue, you can also just change the background color using `"color:"` key.
+若需自定义文本视图背景图像，可使用键`"background":`并将zip内图像文件名设为键值，亦可直接通过`"color:"`键更改背景色。
```json
"background": "fileName"
```
-You also have 4 specific textViews (named freetext1 to freetext4) that have a specific parameter `"textvalue":` that can be used to set for example a label
+另有4个专用文本视图（命名为freetext1至freetext4），含特定参数`"textvalue":`，可用于设置标签等固定文本。
(cwf-reference-chartview-settings)=
-### ChartView settings
+### ChartView 设置
-Chart view is a very specific view that can share some parameters with ImageView or with TextView...
+图表视图是特殊视图，可共享部分图像视图或文本视图的参数...
-Standard settings for this view is very simple:
+该视图的标准设置非常简单：
```json
"chart": {
@@ -165,67 +165,67 @@ Standard settings for this view is very simple:
"visibility": "visible"
},
```
-The 2 additional parameters you can include for Chart view is a background color (default is transparent), using `"color"` key or a background image using `"background"` key.
+图表视图可添加的两个额外参数：通过`"color"`键设置背景色（默认透明），或通过`"background"`键设置背景图像。
(cwf-reference-how-to-build-watchface)=
-## How to build/design your first Watchface
+## 如何构建/设计您的首个表盘
-### Tools required
+### 所需工具
-- Text editor: My advice is to use NotePad++ (or equivalent) that is a simple text editor, but added value is you can see formatted text with color code, so it's easier to detect errors. any simple text editor will do the job. Since the purpose is to tune json information.
-- Image editor (bitmap and/or vector)
- - If you use Bitmap
- - Image editor should be able to manage transparency (required for all image above background), and png format (if you used bitmap image)
- - Background image can be in jpg format (smaller that png)
- - Image editor should allow you to measure in pixel graphical objects (can be a simple square) (top, left, width, height)
- - Image editor should be able to show you colors with RRVVBB code in hexadecimal
- - Image editor should be able to resize image to 400px x 400px (very important to work with this resolution)
- - If you use Vector
- - Vector image should be exported in svg format
+- 文本编辑器：建议使用NotePad++（或同类工具），作为简易文本编辑器，其优势在于可显示带颜色标记的格式化文本，便于错误排查。 任何简易文本编辑器均可胜任。 因需调整json信息。
+- 图像编辑器（位图/矢量图）
+ - 如果您使用位图
+ - 图像编辑器需支持透明通道处理（背景上层图像均需此功能），若使用位图则需兼容png格式。
+ - 背景图像可采用jpg格式（体积较png更小）。
+ - 图像编辑器需支持以像素为单位测量图形对象（如简单方形）的坐标参数（顶部、左侧、宽度、高度）。
+ - 图像编辑器需支持以十六进制RRVVBB代码显示颜色。
+ - 图像编辑器需能将图像调整为400px×400px分辨率（此分辨率至关重要）。
+ - 如果您使用矢量图
+ - 矢量图像应导出为svg格式。
-### Get template to not start from scratch
+### 获取模板以避免从零开始。
-When you want to design your first watchface, the best is to start by the default watchface (this will ensure you to have latest version with all available views correctly sorted)
+设计首个表盘时，最佳方案是从默认表盘开始（可确保获得含所有正确排序视图的最新版本）。
-- You can get zip file by clicking on "Export Template" button within Wear plugin and get zip file within AAPS/exports folder
-- Note that you will need to have a watch connected to AAPS to see Custom Watchface buttons (but watch is also required to check, test and tune your custom watchface)
+- 点击Wear插件中的"导出模板"按钮，即可在AAPS/exports文件夹获取zip文件。
+- 请注意：需连接手表至AAPS才能显示自定义表盘按钮（调试、测试及调整自定义表盘时亦需保持连接）。
-Default watchface is very simple and zip file will contains only the 2 files:
+默认表盘极为简洁，zip文件仅包含以下两个文件：
-- CustomWatchface.png (image of default watchface for WF selection)
+- CustomWatchface.png（用于表盘选择的默认表盘预览图）
- CustomWatchface.json
-### Organize your files within your computer
+### 在电脑中整理您的文件
-The easiest way to work is to have phone connected to the computer, and work with to specific folders:
+最便捷的操作方式是将手机连接电脑，并专注于两个特定文件夹：
-- one explorer opened on a specific folder that will have all files (json, bitmap images, vector images, fonts), and the CustomWatchface.zip file within it
-- another explorer (or navigation tree tuned) opened to have Phone/AAPS/exports folder available
+- 在专用文件夹（内含json文件、位图/矢量图、字体等所有素材）中打开资源管理器，并将CustomWatchface.zip文件置于其中。
+- 同时打开另一个资源管理器（或调整导航树）以访问Phone/AAPS/exports文件夹。
-That way working is very easy: each time you tune json file with a text editor, image with image editor (bitmap or vector) you have to just:
+如此操作极为简便：每次用文本编辑器修改json文件或用图像编辑器（位图/矢量图）调整图像后，仅需：
-1. save your modifications in each app
-2. drag and drop all files within CustomWatchface.zip file
-3. drag and drop CustomWatchface.zip into AAPS/exports folder of the phone
-4. send CustomWatchface to the watch to check the results
+1. 在各应用程序中保存修改内容。
+2. 将所有文件拖放至CustomWatchface.zip文件中。
+3. 将CustomWatchface.zip拖放至手机的AAPS/exports文件夹。
+4. 将CustomWatchface发送至手表以查看效果。
-### Initialize Watchface customization
+### 初始化表盘自定义设置
-First step you will have to define a watchface Name (necessary to select it easily for testing), and start to tune metadata keys at the beginning of json file
+首先需定义表盘名称（便于测试时快速选择），并开始调整json文件开头的元数据键值。
-Then you will have to define which information you want to show so which view should be visible or hidden.
+随后需设定要显示的信息，即确定哪些视图应显示或隐藏。
-- will you manage second or not?
-- do you want to design an analog watch or a digital watch (or both...)
+- 是否启用秒针显示？
+- 需设计模拟表盘、数字表盘或两者兼具？
-Now you can start to modify json file with the `"visibility":` key of each view set to `"visible"` or `"gone"` (if you want to keep or not the view)
+现在您可通过修改json文件中的`"visibility"`键值来设定每个视图为`"visible"`（显示）或`"gone"`（隐藏）。
-You can also start to tune approximativaly top, left margin and width height values to start organizing the watchface (these values will be tuned later using image editor)
+您还可先初步调整顶部、左侧边距及宽高数值来布局表盘（这些数值后续将通过图像编辑器精确校准）。
-Note: everything is design within a **400px x 400px rectangle**. So everything will be position in absolute coordinates within this size.
+注：所有设计均在**400px×400px矩形框**内完成。 因此所有元素均需在此尺寸范围内采用绝对坐标定位。
-When you design your first watchface, you have to know that everything is organized by layer from the Back to the Top, so each view (ImageView or TextView) can hide something that is behind...
+设计首个表盘时需注意：所有元素按从底层到顶层的顺序堆叠排列，因此每个视图（ImageView或TextView）都可能遮挡后方内容...
@@ -233,92 +233,92 @@ When you design your first watchface, you have to know that everything is organi
-Then within json file all views are sorted from the Back to the Top (this will help you to remember what is behind what...)
+json文件中所有视图均按从底层到顶层的顺序排列（便于您记忆各视图的遮挡关系...）
-If you design or tune your first custom watchface, start by simple things: change visibility of some views, include a dedicated background image without changing json file...
+若首次设计或调整自定义表盘，建议从简单操作入手：更改部分视图的可见性、添加专属背景图（无需修改json文件）...
-### Manage colors
+### 管理颜色
-Within json file, you will have several keys to specify colors: `"color"`, `"fontColor"`for views, but also `"highColor"`, `"midColor"`, `"lowColor"`, ... (see [List of General Parameters](#cwf-reference-list-of-general-parameters))
+json文件中包含多个颜色设定键：视图的`"color"`、`"fontColor"`，以及`"highColor"`、`"midColor"`、`"lowColor"`等（详见[通用参数列表](#cwf-reference-list-of-general-parameters)）。
-Colors are specified with a text field that starts by `#` followed by RRGGBB (Red, Green, Blue) values in hexadecimal format:
+颜色通过以`#`开头的文本字段指定，后接十六进制格式的RRGGBB（红绿蓝）值：
-- `"#FFFFFF"` is white, and `"#000000"` is black, `"#FF0000"` is red...
+- `"#FFFFFF"`为白色，`"#000000"`为黑色，`"#FF0000"`为红色...
-You can also include 2 additional values for alpha layer and specify a transparency level (AARRGGBB):
+还可添加2位Alpha通道值来设定透明度（AARRGGBB格式）：
-- `"#00000000"`is completely transparent, and `"#FF000000"` is completely opaque ( so `"#FF000000"` is equivalent to `"#000000"`)
+- `"#00000000"`表示完全透明，`"#FF000000"`表示完全不透明（因此`"#FF000000"`等同于`"#000000"`）
-You can also use the specific keyvalue `"bgColor"` to automatically use `"highColor"`, `"midColor"`, `"lowColor"` specified in general parameters according to BG Value:
+您还可使用特定键值`"bgColor"`，根据血糖值自动调用通用参数中设定的`"highColor"`、`"midColor"`、`"lowColor"`：
-- `"fontColor": "bgColor",` will automatically set the font color of the view according to BG Value
-- Note that `sgv` (for BG Value) and `direction` (for trend arrow) views automatically apply BG colors set into general parameters (for these 2 views, if you want to have different colors, you will have to use advanced [dynData](#cwf-reference-dyndata-feature) feature with one step color...)
+- `"fontColor": "bgColor",` 将根据血糖值自动设置视图的字体颜色
+- 注意：`sgv`（血糖值）和`direction`（趋势箭头）视图会自动应用通用参数中的血糖颜色设置（若需为这两个视图设定不同颜色，需使用进阶的[dynData](#cwf-reference-dyndata-feature)功能配合单阶颜色...）
-For more information concerning ImageViews and `"color":` key, see dedicated chapter [Tune image color](#cwf-reference-tune-image-color) below.
+有关ImageView及`"color":`键的详细信息，请参阅下文[调整图像颜色](#cwf-reference-tune-image-color)专章。
-### Include Hardcoded images
+### 嵌入硬编码图像
-the easiest way to start tuning your watchface is to include within zip file some images with a specific names (see [List of Hardcoded resource files](#cwf-reference-list-of-hardcoded-resource-files))
+调整表盘最便捷的方式是在zip文件中包含特定命名的图像（参见[硬编码资源文件列表](#cwf-reference-list-of-hardcoded-resource-files)）
-- Image should be in `.jpg`, `.png` or `.svg` format. but be careful, jpg doesn't manage transparency, so should be only used for background layer. For all intermediate layers (cover_chart, cover_plate, hands) use either `.png`or `.svg` image
+- 图像需采用`.jpg`、`.png`或`.svg`格式。 但需注意：jpg格式不支持透明度，因此仅适用于背景图层。 所有中间图层（如cover_chart、cover_plate、表针）请使用`.png`或`.svg`格式图像
-- If you have a vector image editor (like for example Illustrator), prefer this format that will produce small text files with `.svg` extension the best quality.
-- You should take care to use exact filename (including High/lower case)
+- 若您使用矢量图像编辑器（如Illustrator），建议优先选择`.svg`格式，该格式能生成体积小巧的文本文件且画质最佳。
+- 务必确保使用精确的文件名（含大小写敏感）。
-Now if you want a dedicated backgoung image, you only have to include within the zip file a file named `Background.jpg` (without changing anything else. send zip file into the watch and check result!.
+若需定制背景图，只需在zip文件中添加名为`Background.jpg`的文件（无需修改其他内容）。 将zip文件发送至手表并查看效果！
-If you want to customize hour_hand, minute_hand or second_hand for an analog watch, simply include `HourHand.png` (or `HourHand.svg`), `MinuteHand.png` and `SecondHand.png`.
+若需定制模拟表盘的时针、分针或秒针，只需添加`HourHand.png`（或`HourHand.svg`）、`MinuteHand.png`及`SecondHand.png`文件。
-- these images will automatically rotate around the center of the image, so the images should be set to 00:00:00 (and for a "full frame" analog watch, use a size of 400 x 400 px positioned at top 0 left 0)
+- 这些图像将自动绕其中心点旋转，因此图像需设置为00:00:00状态（若设计"全屏"模拟表盘，请使用400×400像素尺寸并定位在top 0 left 0位置）。
-You can also noticed within [List of Hardcoded resource files](#cwf-reference-list-of-hardcoded-resource-files) that for each image view, you have two additional hardcoded filenames `High` and `Low` (for example you can include other images named `BackgroundHigh.jpg` and `BackgroundLow.jpg` within zip file). then image will automatically change according to you BG level (within Range, Hyper or Hypo). See AIMICO watchface as example.
+您还可在[硬编码资源文件列表](#cwf-reference-list-of-hardcoded-resource-files)中注意到：每个图像视图均对应两个附加的硬编码文件名`High`和`Low`（例如可在zip文件中添加名为`BackgroundHigh.jpg`和`BackgroundLow.jpg`的其他图像）。 图像将根据您的血糖水平（正常范围、高血糖或低血糖）自动切换。 参见AIMICO表盘示例。
(cwf-reference-tune-image-color)=
-### Tune image color
+### 调整图像颜色
-`"color"` key can be used to tune default image color:
+`"color"`键可用于调整默认图像颜色：
-- applied on background view, it will set the background color (default black)
-- applied on cover_plate (simple dial) or hands, it will change the default image (white) by the color specified (including `"bgColor"`)
+- 应用于背景视图时将设定背景色（默认为黑色）
+- 应用于cover_plate（简易表盘）或表针时，将用指定颜色（含`"bgColor"`）替换默认图像（白色）
-When you apply `"color"` key on a bitmap image (`.jpg` or `.png`), color will apply an interesting effect on color saturation. So you will still recognize your bitmap.
+当您在位图图像（`.jpg`或`.png`）上应用`"color"`键时，颜色将对色彩饱和度产生独特效果。 因此您仍可识别位图原貌。
-Finally on `.svg` image file, `"color"`key will have no effect, consider color of vector files as hardcoded within the image. If you want to change colors, you will have to include several `svg` files, and use advanced [dynData](#cwf-reference-dyndata-feature) feature to change it
+最后，在`.svg`图像文件上，`"color"`键将不起作用，矢量文件的颜色被视为硬编码在图像中。 若需更改颜色，需包含多个`svg`文件，并使用高级[dynData](#cwf-reference-dyndata-feature)功能进行切换
-### Use additional fonts for TextViews
+### 为TextView使用附加字体
-Several defaults font are already available within wear apk (see font keys included into [key values](#cwf-reference-key-values) chapter). But if you want to use additional fonts not available as default, you can include additional fonts within zip file:
+穿戴应用已内置多种默认字体（参见[键值](#cwf-reference-key-values)章节中的字体键）。 但若需使用非默认的附加字体，可在zip文件中添加字体文件：
-- the 2 accepted font format are `.ttf` and `.otf` files
-- if you include a custom font within zip file, for example with a file named `myCustomFont.ttf`, then you will have to use the filename to use it within json file for a TextView:
+- 支持的两种字体格式为`.ttf`和`.otf`文件
+- 若在zip文件中添加自定义字体（例如名为`myCustomFont.ttf`的文件），则需在json文件中通过文件名指定TextView使用的字体：
```
"font": "myCustomFont",
```
-Keep in mind that some fonts can be included into big files (and you are limited to a maximum size for zip file). So if you only use very few characters (numbers, `.`, `,`), you can use free tools to remove unused characters (for example [here](https://products.aspose.app/font/generator/ttf-to-ttf)) and then reduce font size.
+请注意：部分字体文件体积较大（且zip文件存在大小限制）。 因此若仅使用极少量字符（数字、`.`、`,`），可用免费工具剔除未用字符（例如[此处](https://products.aspose.app/font/generator/ttf-to-ttf)），从而缩减字体体积。
(cwf-reference-advanced-features)=
-## Advanced features
+## 高级功能
(cwf-reference-preference-feature)=
-### Preferences Feature
+### 偏好设置功能
-CustomWatchface can automatically tune some watch preferences to have the correct visualization of the watchface (if authorization is given within Wear preferencesby the user).
+CustomWatchface可自动调整部分手表偏好设置，以确保表盘正确显示（前提是用户已在Wear偏好设置中授予权限）。
-But this feature should be used with care. Preferences are common with all other watchfaces. So several rules to respect with this feature:
+但此功能需谨慎使用。 偏好设置与所有其他表盘共用。 使用此功能需遵循以下规则：
-- never set preferences concerning hidden views
-- try to maximize the visible views
-- feel free to oversize the width of certain views:
- - TBR can be shown as percentage (small width, but also as absolute values much wider)
- - delta or avg delta with detailed information can be wide
- - same for iob2: this view can have total iob, but if detailed iob is selected, then text size can be very long
+- 切勿设置与隐藏视图相关的偏好设置
+- 尽量最大化可见视图
+- 可随意放大某些视图的宽度：
+ - TBR可显示为百分比（宽度较小）或绝对值（宽度较大）
+ - 含详细信息的delta或avg delta可设置较宽宽度
+ - iob2同理：该视图可显示总iob，若选择详细iob则文本可能极长
-If you still need some very specific settings to have a correct display (in example below, if there is not enough space for detailed iob, you can "force" this parameter to `false` of your watch, you can include within metadata block some settings constraint like that
+若仍需特定设置才能正确显示（如下例中详细iob空间不足时），可在元数据块中添加此类设置约束，例如将参数"强制"设为`false`
```json
"metadata": {
@@ -332,11 +332,11 @@ If you still need some very specific settings to have a correct display (in exam
},
```
-If user authorize custom watchface to modify watch parameter (setting within wear plugin) then Show detailed iob will be set to "disable", and locked to disable (no modification of this parameter possible, until authorization is disabled within wear plugin parameter, or another watchface is selected)
+若用户授权自定义表盘修改手表参数（通过Wear插件设置），则"显示详细iob"将被设为"禁用"状态并锁定（除非在Wear插件参数中撤销授权或切换其他表盘，否则无法修改此参数）
-- Note that when a user select a watchface, he can see the number of "required parameter" during watchface selection
+- 请注意：用户选择表盘时，可在选择界面查看"必要参数"的数量
-In example below Gota watchface has one required parameter. If authorization is not given it will be shown in white color, but authorization is given, then this parameter will be set and locked on the watch (in this case the number is in orange color)
+下例中Gota表盘需配置1个必要参数。 未获授权时该参数显示为白色；获授权后，参数将被设定并锁定（此时数字显示为橙色）
@@ -344,21 +344,21 @@ In example below Gota watchface has one required parameter. If authorization is
(cwf-reference-twinview-feature)=
-### TwinView Feature
+### 双视图功能
-Twin views provide an easy way to adjust the view position based on the visible views. This does not have the power of a layout entirely made up of LinearLayout, but can handle many common cases.
+双视图功能可根据可见视图轻松调整视图位置。 虽不具备完全由LinearLayout构建的布局功能，但能处理多数常见情况。
-In example below you can see AAPS (Cockpit) watchface with all views visible within settings, and the same watchface with "Show rig battery" disabled and "Show avg delta" disabled
+下例展示AAPS（驾驶舱）表盘：设置中所有视图均可见，以及关闭"显示设备电量"和"显示平均差值"后的同一表盘效果
-You can see that when one of the twin views is hidden, the other is shifted to be centered
+可见当双视图之一隐藏时，另一视图会自动居中显示
-in this example, you can see that within `"uploader_battery"` block, we have `"twinView":` key is added to define `"rig_battery"` view, and in `"rig_battery"` block `"twinView":` key define `"uploader_battery"` as twin. Then then additional key `"leftOffsetTwinHidden":` define the number of pixel to shift the view when twin is hidden.
+本例中，`"uploader_battery"`区块通过`"twinView":`键指定`"rig_battery"`视图为配对对象，而`"rig_battery"`区块的`"twinView":`键则反向指定`"uploader_battery"`为配对视图。 此外，`"leftOffsetTwinHidden":`键用于设定配对视图隐藏时本视图的像素左移量。
-To calculate this number, you can see that the difference between the leftMargin of each of the twin views is 50 pixels, so the offset to stay centered is half in one direction or the other.
+计算该数值时，可见双视图的leftMargin差值为50像素，故居中偏移量需按单方向差值的一半设定。
-If the twin views are positioned vertically, in this case you must use the key `"topOffsetTwinHidden":`
+若双视图为垂直排列，则需改用`"topOffsetTwinHidden":`键
```json
"uploader_battery": {
@@ -394,33 +394,33 @@ If the twin views are positioned vertically, in this case you must use the key `
```
(cwf-reference-dyndata-feature)=
-### DynData Feature
+### 动态数据功能
-DynData is the most powerful feature if you want to include some animation within you watchface, according to some internal values (like BG value, BG level, delta, % of battery... see list of available data [here](#cwf-reference-dyndata-key-values))
+DynData是最强大的功能，可根据内部数值（如血糖值、血糖水平、变化量、电池百分比等，可用数据列表见[此处](#cwf-reference-dyndata-key-values)）为表盘添加动画效果。
-To illustrate this feature, I will take the example of AAPS (SteamPunk) watchface:
+为说明此功能，现以AAPS（蒸汽朋克）表盘为例：
-In this watchface, we will have to manage the [rotation of BG value](#cwf-reference-background-management) (from 30 degrees to 330 degrees) on the right, the [dynamic range of avg_delta](#cwf-reference-avg-delta-management) (scale up to 5mgdl, 10mgdl or 20mgdl according to value), the [rotation of pointer](#cwf-reference-dynamic-rotation-management) that should be synchronized to the scale, and also the different layer of the views...
+该表盘需实现：右侧[血糖值旋转](#cwf-reference-background-management)（30度至330度）、[平均差值动态范围](#cwf-reference-avg-delta-management)（根据数值按5/10/20mgdl缩放）、[指针旋转](#cwf-reference-dynamic-rotation-management)（需与刻度同步），以及各视图层级控制...
-To be able to manage this Watchface, see below all the images included into the zip file:
+为配置此表盘，请参见压缩包内所有图片：
-Note: to be able to see the transparency, all these images are on a yellow background and surrounded by a red square
+注：为展示透明度，所有图片均采用黄色背景并添加红色边框
-- On the first row, Background.jpg and CoverPlate.png will be automatically mapped with associated view (default views filename), and steampunk_pointer.png will be managed by dynData
-- On the second row you see the 3 scales of dynamic range for avg_delta that will also be managed by dynData
-- On the third row, chartBackground.jpg will be linked manually within chart view, HourHand.png and finally MinuteHand.png files will be automatically mapped with associated views
+- 首行Background.jpg和CoverPlate.png将自动关联至对应视图（默认视图文件名），steampunk_pointer.png则由dynData控制
+- 次行显示avg_delta动态范围的3种刻度，同样由dynData调控
+- 第三行chartBackground.jpg将手动关联至图表视图，HourHand.png和MinuteHand.png文件则自动匹配对应视图
(cwf-reference-background-management)=
-#### **Background management**
+#### **背景管理**
-First, concerning BG value image, no choice here, it can only be in the background layer (otherwise it will be in front of the chart view and chart will not be visible!). So we will have to map BG value to the background, and then rotate background image according to BG value.
+首先，关于血糖值图像，此处别无选择——必须置于背景层（否则会遮挡图表视图导致不可见！） 因此需将血糖值映射至背景层，再根据血糖值旋转背景图像。
-Within `"background"` block, we will include 2 dedicated keys to make this rotation:
+在`"background"`区块中，我们将加入2个专用键实现旋转：
```json
"background": {
@@ -433,11 +433,11 @@ Within `"background"` block, we will include 2 dedicated keys to make this rotat
"visibility": "visible"
},
```
-`"dynData":` key will define which block should be used to define the animation (value, range, conversion...) here this block was named "rotateSgv" (choose an explicit name when you use this feature),
+`"dynData":`键指定定义动画的区块（数值、范围、转换等），本例使用名为"rotateSgv"的区块（使用此功能时请选用明确名称）
-`"rotationOffset": true,` will define that the expected animation according to value should be a rotation. (others available keys are `"leftOffset"` and `"topOffset"` if you want to create a slider)
+`"rotationOffset": true,`声明该数值动画应为旋转效果。 （若需创建滑动效果，还可使用`"leftOffset"`和`"topOffset"`键）
-Now we will go at the end of the file, after the last view:
+现在我们将跳转至文件末尾，最后一个视图之后：
```json
"second_hand": {
@@ -454,21 +454,21 @@ Now we will go at the end of the file, after the last view:
"maxData": 330
},
```
-You can see that after the latest view (`"second_hand"`), we added a new `"dynData": { ... }` block that will contains all the animations:
+可见在末视图(`"second_hand"`)之后，我们新增了`"dynData": { ... }`区块以容纳所有动画配置：
-The block defined within `"background"`view was named `"rotateSgv"`, it's the first block you will find into `"dynData"`!
+`"background"`视图内定义的区块命名为`"rotateSgv"`，这正是`"dynData"`中的首个配置区块！
-This block is simple: you have a first key named `"valueKey":` that will be used to define which value should be used. in this case `"sgv"` is a "keyValue" that defines BG value (note that in most cases the keyValue has the same name that the view that shows this information).
+该区块配置简明：首先通过`"valueKey":`键指定关联的数值来源。 此处`"sgv"`作为"keyValue"表示血糖值（注意多数情况下keyValue与显示该信息的视图同名）。
-Concerning BG value, default min data is set to 39mgdl and max data is set to 400mgdl (see [DynData reference key values](#cwf-reference-dyndata-key-values) below all available keyValues and associated min/max data values).
+血糖值的默认最小数据设为39mgdl，最大数据设为400mgdl（所有可用keyValue及对应最小/最大数据值详见下方[动态数据参考键值](#cwf-reference-dyndata-key-values)）。
-Within `"rotateSgv"` block the two additional keys (`"minData":` and `"maxData":`) will be used to tune min and max data to 30 and 330. With these min and max values, we will be able to directly use data value (without any conversion) to rotate background in degrees. In this situation all BG values above 330mgdl will be limited to 330, upper limit of the image.
+在`"rotateSgv"`区块中，另两个键(`"minData":`和`"maxData":`)用于将数据范围调整为30至330。 通过这些最小和最大值，我们可以直接使用数据值（无需转换）来旋转背景（以度为单位）。 在此设置下，所有高于330mgdl的血糖值都将被限制在图像上限330度。
-#### **Chart management**
+#### **图表管理**
-Default background of chart is transparent, so to hide BG scale included into background image, we will need to include a dedicated background image (this image will include the overall shadows of Steampunk watchface). The link to charBackground.jpg file is done with `"background":` key
+图表默认背景为透明，为遮盖背景图像中的血糖刻度，需添加专用背景图（该图含蒸汽朋克表盘的整体阴影效果）。 通过`"background":`键关联charBackground.jpg文件
-Of course, the sizing and positioning of the view must be done to the pixel!
+当然，视图的尺寸和定位必须精确到像素！
```json
"chart": {
@@ -482,15 +482,15 @@ Of course, the sizing and positioning of the view must be done to the pixel!
```
(cwf-reference-avg-delta-management)=
-#### **Avg delta management**
+#### **平均差值管理**
-To be able to manage dynamic range of avg delta, we will use the four freetext views. freetext1 will be used to manage the image scale, and freetext2 to freetext4 will be used to manage pointer rotation according to scale.
+为实现平均差值的动态范围调控，我们将使用四个自由文本视图。 freetext1用于调控刻度图像，freetext2至freetext4则根据刻度控制指针旋转。
**freetext1**
-As explain before, freetext views are in front of chart and in front of background, that's why we included transparent area to see these images (right side and bottom side of the image)
+如前所述，自由文本视图位于图表和背景层之上，因此我们设置了透明区域（图像右侧和底部）以显示这些图像。
-Note that the removed bottom part of these images has been used as background of chart to have a perfect integration.
+注意：这些图像被裁切的底部区域已用作图表背景，实现无缝融合效果。
```json
"freetext1": {
@@ -503,7 +503,7 @@ Note that the removed bottom part of these images has been used as background of
"dynData": "avgDeltaBackground"
},
```
-For this view we include the link to another `"dynData"`block named `avgDeltaBackground`. This block will manage avgDelta scale according to avgDelta value.
+该视图关联至另一个名为`avgDeltaBackground`的`"dynData"`区块。 此区块将根据avgDelta值调控avgDelta刻度。
```json
"avgDeltaBackground": {
@@ -521,24 +521,24 @@ For this view we include the link to another `"dynData"`block named `avgDeltaBac
"image8": "steampunk_gauge_mgdl_20"
},
```
-- `"valueKey":` will make the link with `"avg_delta"` value
-- min and max Data will also limit the range to the maximum value available within this watchface (from -20mgdl to 20mgdl). For mmol users, keep in mind that all internal values are always in mgdl within AAPS.
+- `"valueKey":`将关联`"avg_delta"`数值
+- minData和maxData同时会将范围限制在该表盘支持的最大值区间（-20mgdl至20mgdl）。 使用mmol单位的用户请注意：AAPS内部数值始终以mgdl为单位存储。
-Then we will see here how to manage dynamic background image according to value.
+随后我们将在此说明如何根据数值动态管理背景图像。
-`"invalidImage":` is the key to manage image to show when we have an invalid data (or missing data). Here we make the link to additional resource image including into zip file with 5 mgdl scale
+`"invalidImage":`键用于管理数据无效（或缺失）时显示的图像。 此处关联压缩包内含有5mgdl刻度的附加资源图像
-Then we will use a series of images, starting from `"image1":` to `"image8":`. The number of provided images will define the number of steps between `minData` and `maxData`.
+随后我们将使用从`"image1":`到`"image8":`的系列图像。 提供的图像数量将决定`minData`与`maxData`之间的分段阶数。
-- `image1` will define image to show when avg_delta is equal or close to `minData` and the image with the highest number (here `image8`) will be used to define the image that should be shown when avg_delta is equal or close to `maxData`
-- between -20mgdl and 20mgdl, the overall range is 40mgdl, divided by 8 (number of images provided), we will have 8 steps of 5mgdl
-- Now we can map background images according to avg_delta value, starting from the lowest values: between -20 and -15, and also between -15 and -10 we will use `steampunk_gauge_mgdl_20` for the scale, then between -10 and -5 `steampunk_gauge_mgdl_10`, and so on until +15 and +20 where we will again use `steampunk_gauge_mgdl_20` background image
+- `image1`设定avg_delta等于或接近`minData`时显示的图像，编号最大的图像（此处为`image8`）则设定avg_delta等于或接近`maxData`时的显示图像
+- 在-20mgdl至20mgdl范围内，总跨度为40mgdl，除以8（提供的图像数量）即得到8个5mgdl的递进步阶
+- 现在根据avg_delta值映射背景图像：从最低值开始，-20至-15及-15至-10区间使用`steampunk_gauge_mgdl_20`刻度图，-10至-5区间用`steampunk_gauge_mgdl_10`，以此类推直至+15至+20区间再次使用`steampunk_gauge_mgdl_20`背景图
(cwf-reference-dynamic-rotation-management)=
-**freetext2 to freetext4**
+**freetext2 到 freetext4**
-For these views will will combine dynamic images and rotation feature explained before:
+对于这些视图，我们将结合之前说明的动态图像与旋转功能：
```json
"freetext2": {
@@ -572,7 +572,7 @@ For these views will will combine dynamic images and rotation feature explained
"rotationOffset": true
},
```
-Here each view is dedicated to a specific scale (so is linked to a dedicated dynData block), you can also notice that `"rotationOffset":` key is enabled for these 3 views.Now take a look on the first dynData block:
+此处每个视图对应特定刻度（故关联独立dynData区块），可注意到这3个视图启用了`"rotationOffset":`键。现在查看首个dynData区块：
```json
"avgDelta5": {
@@ -594,19 +594,19 @@ Here each view is dedicated to a specific scale (so is linked to a dedicated dyn
"image8": "null"
},
```
-Here, even if dynamic range will be used only between -5 and +5 avg_delta data, it's important to keep the overall range of -20, +20mgdl to ensure that the pointer will be synchronize with the background during scale switches. That's why we keep the same overall range than for `avgDeltaBackground` and the same number of steps (8 images).
+此处尽管动态范围仅使用-5至+5的avg_delta数据，但必须保持-20至+20mgdl的整体范围，以确保指针在刻度切换时与背景同步。 因此我们保持与`avgDeltaBackground`相同的整体范围和分段数量（8张图像）。
-You can note that either `"invalidImage"` or several `"imagexx"` are with `"null"` key value (it could be any string not existing as a filename within zip file). When a filename is not found, then view background image will be transparent. So the setting ensure that pointer will only be visible for step 4 and step 5 (avg delta between -5mgdl and +5 mgdl), and will not be visible outside this range.
+请注意：`"invalidImage"`及部分`"imagexx"`使用了`"null"`键值（该值可为压缩包内不存在的任意字符串文件名）。 当文件名未找到时，视图背景图像将显示为透明。 该设置确保指针仅在阶数4和5（avg delta介于-5mgdl至+5mgdl）时显示，超出此范围则隐藏。
-Now we can see a new block `"rotationOffset":` that will have inside two keys `"minValue":` and `"maxValue":`. These values are used to make the conversion between internal data (in mgdl), and the angle rotation we want to have.
+现在可见新增的`"rotationOffset":`区块，内含`"minValue":`和`"maxValue":`两个键。 这些数值用于将内部数据（mgdl单位）转换为所需的指针旋转角度。
-- Steampunk watchface is designed to have maximum from -30 degrees to 30 degrees rotation for the pointer. So according to the scale (here from -5mgdl to 5mgdl), we will want to have 30 degrees for these values. Because `minData` and `maxData`are 4 times greater, then the corresponding minValues and maxValues are 4 * 30 degrees so -120 and +120 degrees. But for all rotation above or below +-30 degrees the pointer will be hidden (no image visible), and the pointer will only be visible for values between -5 and +5mgdl... So it's exactly what is expected here.
+- 蒸汽朋克表盘设计为指针提供-30度至30度的最大旋转范围。 因此根据当前刻度（此处为-5mgdl至5mgdl），这些数值将对应30度的旋转角度。 由于`minData`与`maxData`范围扩大4倍，对应的minValue和maxValue也需乘以4倍，即-120度至+120度。 但当旋转角度超出±30度范围时指针将隐藏（无图像显示），仅当数值处于-5至+5mgdl区间时指针可见。 这完全符合此处设计预期。
-The other dynData blocks are defined the same way to tune `"avgDelt10"`and `"avgDelta20"`
+其他dynData区块以相同方式定义，用于调整`"avgDelt10"`和`"avgDelta20"`。
-#### loop view
+#### loop视图
-in Steampunk watchface loop green and red arrows (for status) are disabled, this is also managed with a dedicated dynData block associated to loop view.
+蒸汽朋克表盘中，状态指示的绿色/红色循环箭头被禁用，该功能同样通过关联循环视图的独立dynData区块实现。
```json
"loopArrows": {
@@ -615,15 +615,15 @@ in Steampunk watchface loop green and red arrows (for status) are disabled, this
"image2": "redArrows"
}
```
-Because this block is only called by loop View, and default data managed by this view is loop information, then `"valueKey":` key is optional.
+由于该区块仅由循环视图调用，且该视图默认管理循环数据，故`"valueKey":`键可省略。
-Default `minData` and `maxData` for loop are defined to 0min and 28min, so with two images, all data values below 14 min will be shown with background `image1` and all data values above 14 min will be shown with `image2`. 14 min is exactly the threshold to switch from green arrow to red arrow.
+循环视图默认的`minData`和`maxData`设为0分钟和28分钟，使用两张图像时：低于14分钟的数据显示`image1`背景，高于14分钟则显示`image2`。 14分钟正是绿色箭头切换为红色箭头的临界值。
-In this example, `greyArrows`, `greenArrows` and `redArrows` files are not included into zip file, so these arrows are just removed (invisible), but you can use this block "as is" if you want to tune status arrows with custom background images.
+本例中，`greyArrows`、`greenArrows`和`redArrows`文件未包含在压缩包内，故这些箭头被移除（不可见），但若需用自定义背景图像调整状态箭头，可直接使用该区块配置。
-#### rig_battery and uploader_battery views
+#### rig电池与uploader电池视图
-To finish the overview of dynData feature, we will take a look on battery management. The idea here is to customize text color according to battery level (from 0 to 100%)
+为完成dynData功能的概览，我们将查看电池管理部分。 此处设计理念是根据电池电量（0%至100%）自定义文本颜色。
```json
"uploader_battery": {
@@ -659,11 +659,11 @@ To finish the overview of dynData feature, we will take a look on battery manage
"topOffsetTwinHidden": 13
},
```
-You can see here that these both views share the same `dynData` block named `batteryIcons`. It's possible because by default attached data is the one of the view (to without specifying a `"valueKey":` key within `batteryIcons` block, it will be applied with `uploader_battery` data or `rig_battery` data according to the view).
+可见这两个视图共享名为`batteryIcons`的同一`dynData`区块。 实现原理在于：默认关联视图自身数据（当`batteryIcons`区块未指定`"valueKey":`键时，将自动应用`uploader_battery`或`rig_battery`数据，具体取决于当前视图）。
-Note these two views also use TwinView feature explain [here](#cwf-reference-twinview-feature).
+请注意这两个视图还使用了[此处](#cwf-reference-twinview-feature)说明的TwinView功能。
-Now lets take a look on dynData block:
+现在让我们查看dynData区块：
```json
"batteryIcons": {
@@ -675,27 +675,27 @@ Now lets take a look on dynData block:
"fontColor5": "#000000"
},
```
-Here we use exactly the same logic that for dynamic background image, but with dedicated keys (`"invalidFontColor"` and `"fontColor1"` to `"fontColor5"` to specify 5 steps of 20% each one).
+此处采用与动态背景图像完全相同的逻辑，但使用专用键值（`"invalidFontColor"`及`"fontColor1"`至`"fontColor5"`来定义每20%为一个阶数的5个分段）。
-- `"fontColor1"` (dark red) will be used for all values below 20%, and white will be used for all values above this threshold.
-- If you want to lower the threshold to "below 10%", you just have to add 5 additional keys from `"fontColor6"` to `"fontColor10"` , but you can also adjust each color if you want progressive variation from green to yellow, orange and red...
+- `"fontColor1"`（深红色）将用于20%以下的所有数值，超过此阈值则使用白色。
+- 若需将阈值降至"10%以下"，只需新增`"fontColor6"`至`"fontColor10"`五个键值，也可通过逐级调整颜色实现从绿色到黄色、橙色直至红色的渐变效果。
(cwf-reference-dynpref-feature)=
-### DynPref Feature
+### DynPref功能
-Before reading this chapter, you have to understand how [dynData](#cwf-reference-dyndata-feature) works, because DynPref is an advanced usage of DynData: You will now be able to adjust each DynData block according to preferences set by the user:
+在阅读本章前，需先掌握[dynData](#cwf-reference-dyndata-feature)的工作原理，因DynPref是其高级应用：现在您将能根据用户偏好设置来调整每个DynData区块：
-To illustrate DynPref feature, we will use two example:
+为演示DynPref功能，我们将使用两个示例：
-- Steampunk watchface (simple use to include into the same watchface mgdl and mmol version, watchface will automatically switch according to unit selected into aaps).
-- AAPS V2 watchface will combine different preferences to be able to manage text color and background according to dark and match divider preferences.
+- 蒸汽朋克表盘（简易应用：通过同一表盘集成mgdl与mmol版本，根据aaps中选择的单位自动切换）。
+- AAPS V2表盘将结合多项偏好设置，实现根据暗色模式及匹配分隔线偏好来管理文本颜色与背景。
-#### Simple usage of dynPref within Steampunk watchface
+#### 蒸汽朋克表盘中dynPref的简易应用
-Within Steampunk, we have to set of images according to units: `background` image that will have BG scale and will turn according to BG value. and `freeText1` that contains dynamic scale according to avgDelta value.To be able to have one watchface that will automatically show correct units, we should select image according to unit selected.
+在蒸汽朋克表盘中，我们根据单位设置了两组图像：包含血糖刻度的`background`图像将随血糖值旋转。 以及根据avgDelta值动态调整刻度的`freeText1`。为实现表盘自动显示正确单位，需根据所选单位切换对应图像。
-To do that we will replace `dynData` key by a `dynPref`key within view block:
+为此，我们将在视图区块中用`dynPref`键替换`dynData`键：
```json
"background": {
@@ -708,9 +708,9 @@ To do that we will replace `dynData` key by a `dynPref`key within view block:
"visibility": "visible"
},
```
-Usage of `dynPref`keys will be very close to `dynData`keys explained in previous chapter
+`dynPref`键的用法与前一章所述`dynData`键高度相似
-Now we will take a look at the end of the json file, after `dynData` block:
+现在我们将查看json文件末尾，位于`dynData`区块之后的内容：
```json
"dynData": {
@@ -737,22 +737,22 @@ Now we will take a look at the end of the json file, after `dynData` block:
...
}
```
-You can see that the dynpref key defined within `background` view block (`"dynPref": "rotateSgv"`) exists into the `dynPref` json block included at the end of json file:
+可见定义于`background`视图区块的dynpref键（`"dynPref": "rotateSgv"`）已存在于json文件末尾的`dynPref`区块中：
-This block should contains a `"prefKey"`key that will define which preference should be used. In this example the key `"key_units"` is linked to units selected within AAPS on phone, and value is `"true"`if selected unit is mgdl, `"false"`if selected unit is mmol.
+该区块必须包含`"prefKey"`键，用于指定需调用的偏好设置项。 本示例中，键`"key_units"`关联手机端AAPS选择的单位，其值为`"true"`表示选择mgdl单位，`"false"`表示选择mmol单位。
-Then you will find two json blocks that will use "dynData" format, and that will be used according to selected preference
+随后您将看到两个采用"dynData"格式的json区块，系统将根据所选偏好设置调用对应区块。
-Note that the "HardCoded" file name for Background image is now replaced by a dynamic image that will be the same whatever the BG value (`Background_mgdl.png`file if key_units is "true", `Background_mmol.png` if key_units is false), and we also include an `"invalidImage" key to always have a background image even if no data has been received from the phone.
+请注意"HardCoded"背景图像文件名现已被动态图像替代（当key_units为"true"时使用`Background_mgdl.png`文件，为false时使用`Background_mmol.png`），同时添加了`"invalidImage"`键确保即使未收到手机数据也始终显示背景图像。
-#### Combine different preferences within dynPref with AAPS V2
+#### 在AAPS V2中整合dynPref的多项偏好设置
-Most of the time, when you set a preference, it's not to get "dynamic behaviour", but only the results according to what you select, but within dynPref, it's considered as a dynamic feature...
+多数情况下，设置偏好时并非为了获得"动态行为"，而仅是呈现所选结果——但在dynPref中，这被视为动态功能特性...
-- when in `dynData`you specify one full block of parameters (with images, fontColor, Color, ...), with `dynPref`, you will be able to combine each parameter according to one specific preference.
-- Here we will see how match divider preference will be associated to dark preference to show when it's enabled (true) white text on black background on dark watchface (dark parameter true) or black text on white background on light watchface (dark false)...
+- 当`dynData`需要指定包含图像、字体颜色、颜色等参数的完整区块时，`dynPref`则能根据特定偏好设置逐项组合各参数。
+- 此处将演示如何将分隔线偏好与暗色偏好关联：当启用时（true），暗色表盘（dark参数为true）显示黑底白字，浅色表盘（dark为false）则显示白底黑字...
-First lets see the beginning of json file:
+首先查看json文件起始部分：
```json
"dynPrefColor": "prefColorDark",
@@ -767,9 +767,9 @@ First lets see the beginning of json file:
"dynPref": "dark"
},
```
-`"dynPrefColor": "prefColorDark"` will specify the dynPref block of all default colors outside views. These colors will be tuned according to dark parameter within `"prefColorDark"`:
+`"dynPrefColor": "prefColorDark"`将指定视图外所有默认颜色的dynPref区块。 这些颜色将根据`"prefColorDark"`中的dark参数进行调整：
-And at the end, within the `dynPref` block, you will have a specific dynPref block for default colors:
+最终在`dynPref`区块内，您会看到针对默认颜色的专属dynPref区块：
```json
"prefColorDark": {
@@ -796,9 +796,9 @@ And at the end, within the `dynPref` block, you will have a specific dynPref blo
}
}
```
-The difference between this dynPref block and the other standard dynPref blocks used for views is that here you don't have a dynData block for each value of `"key_dark"` parameter, but only the list of main colors (`highColor`, `midColor` , ...)
+此dynPref区块与视图用标准区块的区别在于：此处未为`"key_dark"`参数的每个值配置dynData区块，仅列出主色列表（`highColor`、`midColor`等）
-Lets now take a look on items included into the "divider banner" (in example below `"basalRate"` view linked to `"matchDivider"` dynPref view:
+现在查看"分隔条"内的项目（如下例中关联`"matchDivider"` dynPref视图的`"basalRate"`视图）：
```json
"basalRate": {
@@ -812,7 +812,7 @@ Lets now take a look on items included into the "divider banner" (in example bel
"dynPref": "matchDivider"
},
```
-Then within dynPref block, you can see that Match divider parameter (`key_match_divider` key), include the 2 blocks "true" and "false", but these two blocks are only used to define that view will use either "dark" dynBlock (so exactly the same background and text color than the otherviews outside the banner), or "white" dynBLock that will set opposite colors for background and text...
+在dynPref区块中可见分隔线参数（`key_match_divider`键）包含"true"和"false"两个区块，这两个区块仅用于定义视图将采用"dark"动态区块（与横幅外其他视图完全相同的背景和文本颜色），或采用"white"动态区块（为背景和文本设置相反颜色）...
```json
"matchDivider": {
@@ -836,13 +836,13 @@ Then within dynPref block, you can see that Match divider parameter (`key_match_
}
},
```
-Note that here you are within a "dynData" block, then to define a color or a fontColor, you will use a dynData (not specified here), and a single step (`"color1"` and `'fontColor1'` are used)
+请注意此处位于"dynData"区块内，因此定义颜色或字体颜色时需使用dynData（本文未具体说明），并采用单一步骤（使用`"color1"`和`'fontColor1'`）
-- for all parameter other than `image` default "invalid value (if not set specifically by `"invalidColor"` key or `"invalidFontColor"` keys) will be `"color1"` and `"fontColor1"`.
+- 除`image`外，所有参数的默认"无效值"（若未通过`"invalidColor"`或`"invalidFontColor"`键专门设置）将采用`"color1"`和`"fontColor1"`。
-Then we will see a third example with iob views (`iob1` and `iob2`), where we will use smaller text for detailed iob and bigger text for total iob:
+接着我们将看到第三个示例——iob视图（`iob1`和`iob2`），其中详细iob数据使用较小字体，总iob数据使用较大字体：
```json
"iob1": {
@@ -869,7 +869,7 @@ Then we will see a third example with iob views (`iob1` and `iob2`), where we wi
"dynPref": "prefIob2"
},
```
-You will see within default view settings the text size (19 on `iob1` and 24 on `iob2`) and the two different `dynPref` block that should tune textsize (according to detailed iob parameter), and colors (according to dark parameter)
+在默认视图设置中可见文本大小（`iob1`为19，`iob2`为24），以及两个不同的`dynPref`区块：一个根据详细iob参数调整文本尺寸，另一个根据暗色参数调整颜色。
```json
"prefIob1": {
@@ -893,11 +893,11 @@ You will see within default view settings the text size (19 on `iob1` and 24 on
}
},
```
-You can see here that according to detailed iob parameter (`"key_show_detailed_iob"` key), when it's "true" then textsize is defined to a fix value bigger than default (24 instead of 19): this is done using textsize "step" feature, within only one value so one step... (note that for all parameter others than images,if invalidTextSize is not set, then textsize1 will be used for invalid data)
+此处可见：根据详细iob参数（`"key_show_detailed_iob"`键），当其为"true"时，文本尺寸被固定设置为比默认值更大的数值（24替代19）——这是通过仅含单值的文本尺寸"阶梯"功能实现的...（注意：除图像外所有参数，若未设置invalidTextSize，则无效数据将使用textsize1）
-Then "dark" dynPref block will be used to set colorand fontColor
+随后"dark"动态偏好区块将用于设置颜色与字体颜色
-In this example the dynData block that will be used for iob1 view will be if detailed IOB is enabled and dark enabled:
+本示例中，当详细IOB启用且暗色模式开启时，将调用以下dynData区块作用于iob1视图：
```
{
@@ -907,9 +907,9 @@ In this example the dynData block that will be used for iob1 view will be if det
},
```
-So the text will be inwhite on black background and the size 24 will replace default size of 19 set into the view
+因此文本将显示为黑底白字，且24号字体尺寸将替换视图中预设的19号默认尺寸。
-The dynData block that will be used for the same view iob1 if detailed IOB is disabled and dark disabled will be:
+当详细IOB禁用且暗色模式关闭时，作用于同一iob1视图的dynData区块为：
```
{
@@ -918,118 +918,118 @@ The dynData block that will be used for the same view iob1 if detailed IOB is di
},
```
-Now the text will be in black on white background with a size of 19
+此时文本将以白底黑字显示，并保持19号字体尺寸。
-#### Tips and tricks for dynPref
+#### dynPref使用技巧
-- You can combine as many pref than you want, but be careful, the number of blocks to describe can increase very fast (it's exponential): if you chain 3 parameters and you want to define all situations, you will have 8 blocks to describe, if each parameter has only 2 values...
-- Be careful to not build "infinite loop" (for example if dynpref1 block should be completed by dynpref2 block that should be completed by dynpref1 block...). In this case the dynpref blocks will be considered as invalid...
-- Do not forget to include the numéric index after the key (when you use for example `"textsize"`key within a view, you will have to use `"textsize1"`within the dynPref value block, because it's a "dynData" format, so linked to value with a single step in this case)
-- Only one key `"valueKey"` should be set for one view, so if the final `dynData` block is built from several `dynPref`blocks, do not include several `"valueKey"` (and associated `"minData"`, `"maxData"`, ...)
+- 您可以组合任意数量的偏好设置，但需注意描述区块数量会呈指数级增长：若串联3个参数且需定义所有情形（假设每个参数仅有2种取值），则需描述8个区块...
+- 注意避免构建"无限循环"（例如当dynpref1区块需由dynpref2区块补充，而dynpref2区块又需由dynpref1区块补充时...）。 此时这些dynpref区块将被视为无效...
+- 使用视图中的`"textsize"`键时，必须在dynPref值区块中使用`"textsize1"`（因其采用"dynData"格式，本例中仅关联单一步骤的值），切勿忘记在键名后添加数字索引。
+- 每个视图仅应设置一个`"valueKey"`键，因此若最终`dynData`区块由多个`dynPref`区块构建时，切勿包含多个`"valueKey"`（及其关联的`"minData"`、`"maxData"`等参数）。
(cwf-reference-new-v2-features)=
-### New Features in CustomWatchface V2 (AAPS V3.3.0 or above)
+### 自定义表盘V2的新功能（适用于AAPS V3.3.0及以上版本）
-Note that the watchfaces using these new features or views will require the latest wear apk built from 3.3.0 version of AAPS.
+请注意，使用这些新功能或视图的表盘需要基于AAPS 3.3.0版本构建的最新wear apk。
-If you use a zip "v2" with a watch that includes CustomWachface V1, you will have missing information or wrong content into the watchface.
+若在搭载CustomWatchface V1的手表上使用"v2"压缩包，表盘将出现信息缺失或内容错误。
-CustomWatchface V2 includes these new features:
+自定义表盘V2包含以下新功能：
-- [New Status view](cwf-reference-new-status-feature)
-- [New TempTarget view](cwf-reference-new-temp-target-feature)
-- [New Reservoir Level view](cwf-reference-new-reservoir-level-feature)
-- [New Formatting Feature](cwf-reference-new-formating-feature)
-- [Show External data for Follower](cwf-reference-show-external-datas) (up to 3 set of data within one single Watchface, for AAPS, AAPSCLIENT and AAPSCLIENT2)
+- [全新状态视图](cwf-reference-new-status-feature)
+- [全新临时目标视图](cwf-reference-new-temp-target-feature)
+- [全新储药器余量视图](cwf-reference-new-reservoir-level-feature)
+- [全新格式设置功能](cwf-reference-new-formating-feature)
+- [显示跟随者外部数据](cwf-reference-show-external-datas)（单个表盘最多可显示3组数据：AAPS、AAPSCLIENT和AAPSCLIENT2）
(cwf-reference-new-status-feature)=
-#### New Status view
+#### 全新状态视图
-The key of this view is `"status"` and associated block is automatically included into the template exported from wear apk "Custom Watchface V2" (built from AAPS 3.3.0 version or above)
+该视图的键为`"status"`，其关联区块已自动包含在wear apk"自定义表盘V2"（基于AAPS 3.3.0及以上版本构建）导出的模板中。
-This view was included into previous AAPS (NoChart), AAPS (BigChart) and AAPS (Large) previous existing watchfaces available and include a string value (built within wear apk).
+该视图已内置在早期AAPS（无图表）、AAPS（大图表）和AAPS（大号）等现有表盘中，并包含由wear apk构建的字符串值。
-These previous watchfaces has been removed and replaced by 3 new custom watchfaces in AAPS 3.3.0.
+AAPS 3.3.0版本中已移除这些旧表盘，替换为3款全新自定义表盘。
-- the minimum information is IOB value (always visible whatever IOB parameter into watch)
-- then you have detailed IOB values (BolusIOB|BasalIOB) if enabled within preferences
-- and BGI value (again if enabled within preferences)
+- 最低显示信息为IOB值（无论手表IOB参数如何设置始终可见）
+- 若在偏好设置中启用，则显示详细IOB值（大剂量IOB|基础率IOB）
+- 以及BGI值（同样需在偏好设置中启用）
-This `"status"` view is associated with `"key_show_loop_status"` key (within dynPref) to manage visibility.
+该`"status"`视图通过`"key_show_loop_status"`键（位于dynPref内）关联，用于管理可见性。
-This view could be managed in V1 using `"iob1"`, `"iob2"` and `"bgi"` existing views, but with the need of complex dynPref settings to manage spacing within each information according to different settings selected within Watch.
+该视图在V1版本中可通过`"iob1"`、`"iob2"`和`"bgi"`现有视图实现，但需配置复杂的dynPref设置来根据手表不同选项调节各信息间距。
(cwf-reference-new-temp-target-feature)=
-#### New TempTarget view
+#### 全新临时目标视图
-The key of this view is `"tempTarget"` and associated block is automatically included into the template exported from wear apk "Custom Watchface V2" (built from AAPS 3.3.0 version or above).
+该视图的键为`"tempTarget"`，其关联区块已自动包含在由wear apk"自定义表盘V2"（基于AAPS 3.3.0及以上版本构建）导出的模板中。
-It shows within watchface:
+表盘将显示以下内容：
-- Profile target (single value or min-max target values) (default color in white)
-- Loop adjusted target (default color in Green)
-- Temp Target defined by user (default color in Yellow)
+- 配置文件目标值（单值或最小-最大目标范围）（默认白色显示）
+- 闭环调整后的目标值（默认绿色显示）
+- 用户设定的临时目标值（默认黄色显示）
-This `"tempTarget"` view is associated with `"key_show_temp_target"` key (within dynPref) to manage visibility.
+该`"tempTarget"`视图通过`"key_show_temp_target"`键（位于dynPref内）关联，用于管理可见性。
-The DynData Key (associated with color information) is `"tempTarget"` (default DynData key associated with TempTarget View)
+动态数据键（关联颜色信息）为`"tempTarget"`（TempTarget视图默认关联的动态数据键）
-DynData value equals:
+动态数据值对应情况：
-- 0 (Profile Target),
-- 1 (Loop Target) or
-- 2 (User Temp Target)
+- 0（配置文件目标）
+- 1（闭环目标）或
+- 2（用户临时目标）
-Note that this view is also available for external data (see [below](cwf-reference-show-external-datas)) with `"tempTarget_Ext1"` and `"tempTarget_Ext2"` keys (View and DynData)
+请注意，该视图也适用于外部数据（参见[下方](cwf-reference-show-external-datas)），使用`"tempTarget_Ext1"`和`"tempTarget_Ext2"`键（视图及动态数据）。
(cwf-reference-new-reservoir-level-feature)=
-#### New Reservoir Level view
+#### 全新储药器余量视图
-The key of this view is `"reservoir"` and associated block is automatically included into the template exported from wear apk "Custom Watchface V2" (built from AAPS 3.3.0 version or above).
+该视图的键为`"reservoir"`，其关联区块已自动包含在由wear apk"自定义表盘V2"（基于AAPS 3.3.0及以上版本构建）导出的模板中。
-This view show Reservoir level (in `U`) with a White default color, Yellow if Warning Level, Red if Urgent Level
+该视图以白色（默认）显示储药器余量（单位`U`），警告级别为黄色，紧急级别为红色。
-This `"reservoir"` view is associated with `"key_show_reservoir_level"` key (within dynPref) to manage visibility.
+该`"reservoir"`视图通过`"key_show_reservoir_level"`键（位于dynPref内）关联，用于管理可见性。
-The DynData Keys associated with Reservoir Level are:
+储药器余量关联的动态数据键为：
-- `"reservoir"` (Default DynData Key associated with Reservoir Level view) associated with level in insulin `U`
- - Min Value is 0.0 U
- - Max Value is 500.0 U
-- `"reservoirLevel"`
- - 0 (Standard Level, White Color by default)
- - 1 (Warning Level, Yellow color by default)
- - 2 (Urgent Level, Red color by default)
+- `"reservoir"`（储药器余量视图默认动态数据键）关联胰岛素余量`U`
+ - 最小值为0.0单位
+ - 最大值为500.0单位
+- `"储药器余量"`
+ - 0（标准余量，默认白色显示）
+ - 1（警告余量，默认黄色显示）
+ - 2（紧急余量，默认红色显示）
-Note that this view is also available for external data (see [below](cwf-reference-show-external-datas)) with `"reservoir_Ext1"`, `"reservoir_Ext2"`, `"reservoirLevel_Ext1"` and `"reservoirLevel_Ext2"` keys (View and DynData).
+请注意，该视图也支持外部数据（参见[下方](cwf-reference-show-external-datas)），可通过`"reservoir_Ext1"`、`"reservoir_Ext2"`、`"reservoirLevel_Ext1"`和`"reservoirLevel_Ext2"`键（视图及动态数据）实现。
(cwf-reference-new-formating-feature)=
-#### New Formatting feature for DynData or DynPref
+#### 动态数据或动态偏好的新格式化功能
-You can now manage a custom formatting of raw values received by the watch and included in [dyndata key value table](#cwf-reference-dyndata-key-values) below.
+现在您可对手表接收的原始值进行自定义格式化，这些值已包含在下方的[动态数据键值表](#cwf-reference-dyndata-key-values)中。
-To illustrate how this feature works, lets take as an example AAPS (Large) watchface and look at the results according to "time ago value" and the new "status" view visible or not:
+为说明该功能运作方式，现以AAPS（大号）表盘为例，根据"时间间隔值"及"status"视图显示状态展示效果：
-- In first screenshot in the left, status view is visible (with IOB, detailed IOB and BGI), so only 1/3 of the line is available to show timestamp (very compact information with `1'`, and for uploader battery information `U: 55%`)
-- In second screenshot, now `status`view has been hidden in watch parameter, so you have a lot of place available to show full label for timestamp information and uploader battery (`1 minute ago` and `Uploader : 55%`)
-- In the third screenshot in the right, you have exactly the same setting within watch, but now timestamp has changed and is above "1". now the custom watchface is able to show the label updated with plural management (`2 minutes ago`)
+- 左侧首张截图中status视图可见（含IOB、详细IOB及BGI），故仅1/3行空间显示时间戳（极简格式如`1'`，上传器电量显示为`U:55%`）
+- 右侧截图中`status`视图已通过手表参数隐藏，因此有充足空间完整显示时间戳及上传器电量信息（`1分钟前`和`上传器：55%`）
+- 最右侧截图中手表设置完全相同，但时间戳数值已超过"1"。 此时自定义表盘可显示经复数处理的更新标签（`2分钟前`）
-I will not explain below how the whole views are managed within zip file (positioning of each view according to different settings), but I will only focus on the way we manage formatting feature and associated dynamic value within AAPS (Large) watchface.
+下文将不赘述zip文件中视图的整体管理逻辑（不同设置下各视图的定位方式），仅重点解析AAPS（大号）表盘中格式化功能与关联动态值的实现方法。
-**This feature requires "dynamic block"** (it can be either a `dynData` block or a `dynPref` block)
+**该功能需配合"动态区块"使用**（可以是`dynData`区块或`dynPref`区块）
-- For AAPS (Large) Watchface, we wanted to have the format tuned according to parameters (short or long format according to `status` view visibility) so we used a `dynPref` block for that.
+- 在AAPS（大号）表盘中，我们需根据参数（如`status`视图显隐状态）切换短/长格式，因此采用了`dynPref`区块实现。
-First lets start by the views:
+首先从视图结构讲起：
```json
"uploader_battery": {
@@ -1064,16 +1064,16 @@ First lets start by the views:
"fontColor": "#FFFFFF"
},
```
-here the most important key is `"dynValue"`: Having this key information will enable dynamic management of raw value. the boolean behind (true or false) will define if value should be "converted or not"
+此处最关键的是`"dynValue"`键：通过该键信息可实现原始值的动态管理。 后方布尔值（true/false）决定是否对数值进行"转换"
-- `false`: raw value will be use as it is without any limitation or conversion
-- `true`: raw value will be converted (using `minData` and `maxData` keys in dynData block and using `minValue` and `maxValue` defined in dynData)
+- `false`：直接使用原始值，不做任何限制或转换
+- `true`：原始值将根据dynData区块中的`minData`和`maxData`键，以及dynData中定义的`minValue`和`maxValue`进行转换
-For this watchface, raw values are used without any conversion, so for both views, `"dynValue"` key as been set to `false`.
+该表盘直接使用原始值未作转换，故两个视图的`"dynValue"`键均设为`false`。
-Now we will take a look on `"uploader"` block defined within `"dynPref"`:
+现在查看`"dynPref"`中定义的`"uploader"`区块：
```json
"uploader": {
@@ -1090,30 +1090,30 @@ Now we will take a look on `"uploader"` block defined within `"dynPref"`:
}
},
```
-By default `"uploader_battery"` view is linked to `"uploader_battery"` , so no need to add an explicit line with
+默认情况下`"uploader_battery"`视图已关联`"uploader_battery"`键，无需额外声明关联关系
-`"valueKey": "uploader_battery"` (min value 0, max value 100, and raw value is percentage of phone battery)
+`"valueKey": "uploader_battery"`（最小值0，最大值100，原始值为手机电量百分比）
-The formatting string is included into `"textvalue1"` key (`"textvalue1"`, `"textvalue2"`, etc keys are linked to `"textvalue"` key that could be included into `view` block)
+格式化字符串包含在`"textvalue1"`键中（`"textvalue1"`、`"textvalue2"`等键与可置于`view`区块的`"textvalue"`键关联）
-- `"textvalue"` key can be used with formatting information within the view block (in this situation format will be static, whatever the value or the settings)
-- If you want to modify formatting information according to settings or values, thenall dynData feature can be applied, and the dedicated keys are `"invalidTextValue"` key (without "formatting information" because value is not valid) and `"textvalue1"`, `"textvalue2"`... (and as many values that you want to manage steps between minData and maxData)
-- the additional `"dynPref"` keys are used to define other blocks for positioning variation and color variation depending on visible views, dark and matchDivider settings
+- `"textvalue"`键可在视图区块中使用格式化信息（此时格式为静态，不受数值或设置影响）
+- 若需根据设置或数值调整格式，可应用全部dynData功能，专用键为`"invalidTextValue"`（不含"格式化信息"因数值无效）及`"textvalue1"`、`"textvalue2"`...（可添加任意数量键值以管理minData与maxData间的分段）
+- 额外`"dynPref"`键用于定义其他区块，以根据视图显隐、暗色模式及分界器设置调整定位与色彩
-Concerning now the formatting string, syntax is the following: `%[flags][width][.precision]f`
+关于格式化字符串的语法规则如下：`%[flags][width][.precision]f`
-- `%` is the beginning of a formatting, `f` is the end and should be used for Double value conversion.
- - Note that if you want to use `%` character within your string, you will have to use `%%` to specify that it's not a formatting string but percentage character.
-- `[flag]` is optional, mainly can be `+` if you always want a sign before the number, or `(` if you want negative values in parentheses
-- `[width]` is optional, define the minimum number of characters to be written to the output
-- `[.precision]` used to define number of digits after radix point.
- - Note that values are Double so it's wise to always set a precision (to avoid a lot of characters after radix point due to kotlin precision)
+- `%`是格式化的起始符，`f`为结束符（专用于双精度浮点数转换）。
+ - 注意：若需在字符串中使用`%`字符，必须写成`%%`以表明此处为百分号而非格式化起始符。
+- `[flag]`为可选参数，常用`+`强制显示正负号，或用`(`使负值显示在括号内
+- `[width]`为可选参数，定义输出结果的最小字符数
+- `[.precision]`用于定义小数点后的位数。
+ - 注意：由于数值为双精度浮点型，建议始终设置精度（避免Kotlin精度导致小数点后出现过多字符）
-So in the above example `%.0f` will show Double value as an integer
+因此上例中`%.0f`会将双精度值显示为整数
-Let's now take a look on timestamp dynPref block to manage plural:
+现在查看管理复数形式的timestamp动态参数区块：
```json
"timestamp": {
@@ -1133,149 +1133,149 @@ Let's now take a look on timestamp dynPref block to manage plural:
}
},
```
-- here if `status` view is visible (so `"key_show_loop_satus"` key is `true`), a single format is used (`"textvalue1"`), with `'` as "unit"
-- if `status` view is hidden, you have 2 different format used one for 0 or 1 with singular, and another format for values above 2 with plural
- - `"minData"` and `"maxData"` are used to define the range and be sure the switch from singular to plural will be done between 1 and 2 values
- - Note that `"maxData"` (integer) has been set to 3 and not 2, just because Double data managed into the system is not integer, so a value a bit above or a bit lower 1 may have singular or plural format even if after rounding to integer, the value equals 1.
+- 当`status`视图可见时（即`"key_show_loop_satus"`键为`true`），采用单一格式（`"textvalue1"`），以`'`作为单位符号
+- 若`status`视图隐藏，则采用两种格式：0或1时使用单数形式，大于2时使用复数形式
+ - `"minData"`和`"maxData"`用于定义数值范围，确保单复数切换在1和2之间生效
+ - 注意：`"maxData"`（整数值）设为3而非2，因系统处理的双精度数据并非整数，故略高于或低于1的值经四舍五入后可能仍为1，但需按单复数格式区分显示。
-- For `timestamp` view, it's important to set `"dynValue"` key to `false`, otherwise because of formatting (singular/plural), all values above 3 will be limited to `3 minutes ago` with conversion using `maxData`...
+- 对于`timestamp`视图，必须将`"dynValue"`键设为`false`，否则因单复数格式化处理，所有大于3的值都会通过`maxData`转换被限制显示为`3分钟前`...
-**Additional comment concerning formatting feature**
+**关于格式化功能的补充说明**
-- keep in mind that the only dynamic values available are the one listed [here](#cwf-reference-dyndata-key-values)
-- All `BG` values are in mgdl unit, if you want to use formatting feature to show values in mmol units, you will have to manage mgdl to mmol conversion. Within a `dynData` or `dynPref` block, the key that should be used to name the block that will include `"minValue"`and `"maxValue"` for value conversion should be named `"dynValue": { ... }`. (see [Dyn Data Keys](#cwf-reference-dyndata-keys))
-- If within a view you want to use a static formatting string, with `"textvalue"` key to define format, and `"dynValue"` key to define usage of dynamic value, then you will have to also use a `"dynData"` or a `"dynPref"`block (even if empty), to be able to use formatting feature.
-- `"textvalue1"`, `"textvalue2"` to textvalue*n* can be used without formatting feature to replace double value step by a dedicated text label (for example with `"day_name"` key value and seven steps to define custom name of the dayx of the week, ... )
+- 请谨记：唯一可用的动态值仅为[此处](#cwf-reference-dyndata-key-values)列出的参数
+- 所有`血糖`值均以mg/dL为单位，若需通过格式化功能显示mmol/L单位，必须自行处理mg/dL与mmol/L的换算。 在`dynData`或`dynPref`区块中，用于定义包含数值转换`"minValue"`和`"maxValue"`的子区块必须命名为`"dynValue": { ... }`。 （参见[动态数据键](#cwf-reference-dyndata-keys)）
+- 若需在视图中使用静态格式化字符串（通过`"textvalue"`键定义格式，`"dynValue"`键启用动态值），则必须同时声明`"dynData"`或`"dynPref"`区块（即使留空）以激活格式化功能。
+- `"textvalue1"`、`"textvalue2"`至textvalue*n*可不启用格式化功能，用于将数值分段替换为特定文本标签（例如配合`"day_name"`键值，通过七个分段定义星期几的自定义名称等）。
-- For full documentation you can see [Class Formatter](https://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html)
+- 完整文档请参阅[Formatter类](https://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html)
(cwf-reference-show-external-datas)=
-#### Show External data for Follower
+#### 显示跟随者的外部数据
-Custom Watchface is now able to display on the same watchface up to 3 set of data: AAPS, AAPSCLIENT and AAPSCLIENT2
+自定义表盘现在可同时显示最多3组数据：AAPS、AAPSCLIENT和AAPSCLIENT2
-To use this feature, you need to:
+要使用此功能，您需要：
-- have at least 2 of the 3 following apps installed in phone (AAPS, AAPSCLIENT, AAPSCLIENT2)
-- enable Broadcast data in AAPSCLIENT and/or AAPSCLIENT2 to broadcast data to the main app used to sync with CustomWatchface (AAPS or AAPSCLIENT)
-- Use a CustomWatchface that implement Views with Key including `_Ext1` or `_Ext2` (see [Key and KeyValue reference](cwf-reference-key-and-keyvalue-reference) below)
+- 手机上需安装以下3个应用中的至少2个（AAPS、AAPSCLIENT、AAPSCLIENT2）
+- 在AAPSCLIENT和/或AAPSCLIENT2中启用数据广播功能，将数据广播至用于与CustomWatchface同步的主应用（AAPS或AAPSCLIENT）
+- 使用支持`_Ext1`或`_Ext2`键视图的CustomWatchface（参见下文[键与键值对照表](cwf-reference-key-and-keyvalue-reference)）
-Note that if main app in phone is AAPSCLIENT and secondary app which broadcast data is AAPSCLIENT2, you will have to enable `Switch external data in watchface` parameter within Custom Watchface dedicated parameter if you use a watchface which use standard views and Ext1 additional views (Ext1 is linked to AAPSCLIENT and Ext2 is linked to AAPSCLIENT2)
+请注意：若手机主应用为AAPSCLIENT且广播数据的次级应用为AAPSCLIENT2，当使用含标准视图及Ext1附加视图（Ext1关联AAPSCLIENT，Ext2关联AAPSCLIENT2）的表盘时，需在CustomWatchface专属参数中启用`切换表盘外部数据`选项。
-Additionally three new views (`"patient_name"` , `"patient_name_Ext1"` and `"patient_name_Ext2"` *) has been added to be able to automatically include patient name (set within AAPS preferences) within watchface (see example below)
+新增三个视图（`"patient_name"`、`"patient_name_Ext1"`及`"patient_name_Ext2"`*），用于在表盘中自动显示患者姓名（通过AAPS偏好设置配置，参见下方示例）。
(cwf-reference-key-and-keyvalue-reference)=
-## Key and KeyValue reference
+## 键与键值对照表
(cwf-reference-list-of-metadata-keys)=
-### List of Metadata keys
+### 元数据键列表
(cwf-reference-list-of-standard-metadata-keys)=
-#### List of Standard information metadata keys
+#### 标准信息元数据键列表
-| Key | Comment |
-| ------------------ | -------------------------------------------------------------------------------------------------------------- |
-| `"name"` | Name of custom watchface |
-| `"author"` | Name or pseudo of the author(s) |
-| `"created_at"` | Creation (or update) date, be careful `/` is a special character, so if you use it for the date put `\`before |
-| `"cwf_version"` | Watchface plugin compatible with the design of your watchface |
-| `"author_version"` | The author can specify here the version of his watchface |
-| `"comment"` | Free text that can be used to give some information or limitation of current watchface |
+| 键 | 备注 |
+| ------------------ | ---------------------------------------- |
+| `"name"` | 自定义表盘名称 |
+| `"author"` | 作者名称或笔名 |
+| `"created_at"` | 创建（或更新）日期，注意：`/`是特殊字符，若用于日期显示需在前添加`\`转义 |
+| `"cwf_version"` | 与您表盘设计兼容的表盘插件 |
+| `"author_version"` | 作者可在此指定其表盘的版本号 |
+| `"comment"` | 自由文本字段，用于说明当前表盘的功能信息或使用限制 |
(cwf-reference-preference-keys)=
-#### Preference keys
-
-| Key | Default value and Comment |
-| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `"key_show_detailed_iob"` | true will lock detailed IOB data on view `iob2`, then `iob1` (if visible and not replaced by an icon) will show iob total.
false will lock total iob on `iob2`view. can be used if the width of `iob2`is too small to show correctly detailed iob |
-| `"key_show_detailed_delta"` | false (only if design is not compatible with the width of detailed delta for `delta`and `avg_delta` views) |
-| `"key_show_bgi"` | true if your design requires `bgi` information |
-| `"key_show_iob"` | true if your design requires `iob1` or `iob2`views |
-| `"key_show_cob"` | true if your design requires `cob1` or `cob2`views |
-| `"key_show_delta"` | true if your design requires `delta` information |
-| `"key_show_avg_delta"` | true if your design requires `avg_delta` information |
-| `"key_show_temp_target"` | true if your design requires `tempTarget` information |
-| `"key_show_reservoir_level"` | true if your design requires `reservoir` information |
-| `"key_show_uploader_battery"` | true if your design requires `uploader_battery` (phone battery) information |
-| `"key_show_rig_battery"` | true if your design requires `rig_battery` information |
-| `"key_show_temp_basal"` | true if your design requires `basalRate` information |
-| `"key_show_direction"` | true if your design requires `direction` information (BG variation arrows) |
-| `"key_show_ago"` | true if your design requires `timestamp` information (minutes ago for last received BG) |
-| `"key_show_bg"` | true if your design requires `sgv` information (BG value) |
-| `"key_show_loop_status"` | true if your design requires `loop` information (loop status and ago) |
-| `"key_show_week_number"` | true if your design requires `week_number` information (loop status and ago) |
-| `"key_show_date"` | true if your design requires `Date`, `Month` or `Day of the week` information |
-
-#### Internal keys
-
-| Key | Comment and |
-| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `"filename"` | This key will be created (or updated) automatically when the watchface is loaded and will contains local zip filename within exports folder |
-| `"cwf_authorization"` | this key will be created (when the watchface is loaded) and updated each time authorization preference is changed in Wear settings, and it will be used to synchronize authorization to watch |
+#### 偏好设置键
+
+| 键 | 默认值与注释 |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
+| `"key_show_detailed_iob"` | true将锁定视图`iob2`上的详细IOB数据，此时`iob1`（若可见且未被图标替换）将显示IOB总量。
false则会在`iob2`视图上锁定IOB总量显示。 当`iob2`视图宽度过小无法正确显示详细IOB数据时可启用此选项 |
+| `"key_show_detailed_delta"` | false（仅当设计不兼容`delta`与`avg_delta`视图的详细差值宽度时使用） |
+| `"key_show_bgi"` | 若设计需要显示`bgi`信息则设为true |
+| `"key_show_iob"` | 若设计需要显示`iob1`或`iob2`视图则设为true |
+| `"key_show_cob"` | 若设计需要显示`cob1`或`cob2`视图则设为true |
+| `"key_show_delta"` | 若设计需要显示`delta`信息则设为true |
+| `"key_show_avg_delta"` | 若设计需要显示`avg_delta`信息则设为true |
+| `"key_show_temp_target"` | 若设计需要显示`tempTarget`信息则设为true |
+| `"key_show_reservoir_level"` | 若设计需要显示`reservoir`信息则设为true |
+| `"key_show_uploader_battery"` | 若设计需要显示`uploader_battery`（手机电量）信息则设为true |
+| `"key_show_rig_battery"` | 若设计需要显示`rig_battery`信息则设为true |
+| `"key_show_temp_basal"` | 若设计需要显示`basalRate`信息则设为true |
+| `"key_show_direction"` | 若设计需要显示`direction`信息（血糖变化箭头）则设为true |
+| `"key_show_ago"` | 若设计需要显示`timestamp`信息（最近血糖数据接收时间/分钟前）则设为true |
+| `"key_show_bg"` | 若设计需要显示`sgv`信息（血糖值）则设为true |
+| `"key_show_loop_status"` | 若设计需要显示`loop`信息（闭环状态及时间间隔）则设为true |
+| `"key_show_week_number"` | 若设计需要显示`week_number`信息（周数）则设为true |
+| `"key_show_date"` | 若设计需要显示`Date`、`Month`或`Day of the week`信息则设为true |
+
+#### 内部键
+
+| 键 | 注释 |
+| --------------------- | ------------------------------------------ |
+| `"filename"` | 此键将在表盘加载时自动创建（或更新），并包含导出文件夹中的本地zip文件名 |
+| `"cwf_authorization"` | 此键将在表盘加载时创建，并在Wear设置中每次更改授权偏好时更新，用于同步授权至手表 |
(cwf-reference-list-of-general-parameters)=
-### List of General parameters
-
-| Key | Comment |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `"highColor"` | `"#FFFF00"`(default Yellow): Color of BG value, trend arrows and bg value in graph if bg is above upper limit (Hyper) |
-| `"midColor"` | `"#00FF00"`(default Green): Color of BG value, trend arrows and bg value in graph if bg is within range |
-| `"lowColor"` | `"#FF0000"`(default Red): Color of BG value, trend arrows and bg value in graph if bg is below lower limit (Hypo) |
-| `"lowBatColor"` | `"#E53935"`(default Dark Red): Color of `uploader_battery` when value is low (below 20% tbc) |
-| `"carbColor"` | `"#FB8C00"`(default Orange): Color of Carbs points within graph |
-| `"basalBackgroundColor"` | `"#0000FF"`(default Dark blue): Color of TBR curve within graph |
-| `"basalCenterColor"` | `"#64B5F6"`(default Light blue): Color of Bolus or SMB points within graph |
-| `"gridColor"` | `"#FFFFFF"`(default White): Color of lines and text scale within graph |
-| `"pointSize"` | 2 (default): size of points in graph (1 for small point, 2 for big points) |
-| `"enableSecond"` | false (default): specify if watchface will manage seconds or not within `time`, `second` or `second_hand` views. it's important to be consistent between view visibility and this overall setting that will allow update every second of time information |
-| `"dayNameFormat"` | "E" (default): from "E" to "EEEE" specify dayname format (number, short name, full name) tbc |
-| `"monthFormat"` | "MMM" (default): from "M" to "MMMM" specify month format (number, short name, full name) |
+### 通用参数列表
+
+| 键 | 备注 |
+| ------------------------ | ------------------------------------------------------------------------------------------ |
+| `"highColor"` | `"#FFFF00"`（默认黄色）：当血糖值超过上限（高血糖）时，血糖值、趋势箭头及图表中血糖值的显示颜色 |
+| `"midColor"` | `"#00FF00"`（默认绿色）：当血糖值在范围内时，血糖值、趋势箭头及图表中血糖值的显示颜色 |
+| `"lowColor"` | `"#FF0000"`（默认红色）：当血糖值低于下限（低血糖）时，血糖值、趋势箭头及图表中血糖值的显示颜色 |
+| `"lowBatColor"` | `"#E53935"`（默认深红色）：当`uploader_battery`值过低（低于20%，待确认）时的显示颜色 |
+| `"carbColor"` | `"#FB8C00"`（默认橙色）：图表中碳水化合物数据点的显示颜色 |
+| `"basalBackgroundColor"` | `"#0000FF"`（默认深蓝色）：图表中TBR曲线的显示颜色 |
+| `"basalCenterColor"` | `"#64B5F6"`（默认浅蓝色）：图表中大剂量或超微大剂量数据点的显示颜色 |
+| `"gridColor"` | `"#FFFFFF"`（默认白色）：图表中线条和文本刻度的显示颜色 |
+| `"pointSize"` | 2（默认值）：图表中数据点的大小（1为小点，2为大点） |
+| `"enableSecond"` | false（默认值）：指定表盘是否在`time`、`second`或`second_hand`视图中处理秒数。 必须确保视图可见性与该全局设置保持一致，该设置将允许每秒更新时间信息 |
+| `"dayNameFormat"` | "E"（默认值）：从"E"到"EEEE"指定星期名称格式（数字、简称、全称），待确认 |
+| `"monthFormat"` | "MMM"（默认值）：从"M"到"MMMM"指定月份格式（数字、简称、全称） |
(cwf-reference-list-of-hardcoded-resource-files)=
-### List of HardCoded resource files
-
-For most images, High and Low suffix allow tuning of image according to BG level (in Range, Hyper or Hypo)
-
-| Filenames | Comment |
-| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| CustomWatchface | Image shown for watchface selection and within Wear plugin |
-| Background,
BackgroundHigh,
BackgroundLow | none (default black): Background image. background is always visible and default color is black if no image provided. Color can be modified to fit watchface design |
-| CoverChart,
CoverChartHigh,
CoverChartLow | none (default): Image in front of Chart (transparency should be available to see Chart behind) Can be used to limit boundaries of graph |
-| CoverPlate,
CoverPlateHigh,
CoverPlateLow | simple dial (default): image in front of all text values. transparency mandatory to see all values that are behind |
-| HourHand,
HourHandHigh,
HourHandLow | hour_hand (default): image of hour hand. a default image is provided and can be colored to fit analog design. Note axis for rotation will be the center of the image |
-| MinuteHand,
MinuteHandHigh,
MinuteHandLow | minute_hand (default): image of minute hand. a default image is provided and can be colored to fit analog design. Note axis for rotation will be the center of the image |
-| SecondHand,
SecondHandHigh,
SecondHandLow | second_hand (default): image of second hand. a default image is provided and can be colored to fit analog design. Note axis for rotation will be the center of the image |
-| ArrowNone | ?? (default): image shown when no valid arrow is available. |
-| ArrowDoubleUp | ↑↑ (default): image of double arrow up |
-| ArrowSingleUp | ↑ (default): image of single arrow up |
-| Arrow45Up | ↗ (default): image of fortyfive arrow up |
-| ArrowFlat | → (default): image of flat arrow |
-| Arrow45Down | ↘ (default): image of fortyfive arrow down |
-| ArrowSingleDown | ↓ (default): image of single arrow down |
-| ArrowDoubleDown | ↓↓ (default): image of double arrow down |
-
-For each above filenames, extension can be either `.jpg`, `.png` or `.svg`. But be careful, `.jpg`doesn't manage transparency (so most of the files should be with .png or .svg to not hide view that are behind...)
+### 硬编码资源文件列表
+
+对于大多数图像，High和Low后缀允许根据血糖水平（在范围内、高血糖或低血糖）调整图像
+
+| 文件名 | 备注 |
+| --------------------------------------------------------------- | ----------------------------------------------------------- |
+| CustomWatchface | 用于表盘选择和在Wear插件中显示的图像 |
+| Background,
BackgroundHigh,
BackgroundLow | 无（默认黑色）：背景图像。 若无背景图像，则始终显示默认黑色背景。 可修改颜色以适应表盘设计 |
+| CoverChart,
CoverChartHigh,
CoverChartLow | 无（默认值）：图表前景图像（需保持透明度以确保底层图表可见），可用于限定图表边界 |
+| CoverPlate,
CoverPlateHigh,
CoverPlateLow | 简易表盘（默认值）：所有文本值前方的图像。 必须保持透明度以确保后方所有数值可见 |
+| 时针、
高血糖时针、
低血糖时针 | hour_hand（默认值）：时针图像。 提供默认图像，可调整颜色以匹配模拟表盘设计。 注意：旋转轴心为图像中心点 |
+| MinuteHand,
MinuteHandHigh,
MinuteHandLow | minute_hand（默认值）：分针图像。 提供默认图像，可调整颜色以匹配模拟表盘设计。 注意：旋转轴心为图像中心点 |
+| SecondHand,
SecondHandHigh,
SecondHandLow | second_hand（默认值）：秒针图像。 提供默认图像，可调整颜色以匹配模拟表盘设计。 注意：旋转轴心为图像中心点 |
+| ArrowNone | ?? （默认值）：无有效箭头时显示的图像。 |
+| ArrowDoubleUp | ↑↑（默认值）：双上箭头图像 |
+| ArrowSingleUp | ↑（默认值）：单上箭头图像 |
+| Arrow45Up | ↗（默认值）：45度上箭头图像 |
+| ArrowFlat | →（默认值）：水平箭头图像 |
+| Arrow45Down | ↘（默认值）：45度下箭头图像 |
+| ArrowSingleDown | ↓（默认值）：单下箭头图像 |
+| ArrowDoubleDown | ↓↓（默认值）：双下箭头图像 |
+
+上述每个文件名可使用`.jpg`、`.png`或`.svg`扩展名。 但需注意，`.jpg`格式不支持透明度（因此多数文件应使用.png或.svg格式，避免遮挡后方视图...）
(cwf-reference-list-of-view-keys)=
-### List of View keys
+### 视图键列表
-This list is sorted from background to foreground this is very important when you organize your watchface to know this order because some image or text can be hidden by other images.
+此列表按从背景到前景的顺序排列，在组织表盘时了解此顺序非常重要，因为某些图像或文本可能被其他图像遮挡。
-Note: all keys including `_Ext1` or `_Ext2` at the end are new and dedicated for multi users Watchfaces.
+注意：所有以`_Ext1`或`_Ext2`结尾的键都是新增的，专用于多用户表盘。
-| Key | Type of view | Data attached | DynData Key |
+| 键 | 视图类型 | 关联数据 | 动态数据键 |
| -------------------------------------------------------------------------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| `"background"` | Image View | | |
| `"chart"` | Specific Chart View | Graphical curves | |
@@ -1308,7 +1308,7 @@ delta_Ext1
delta_Ext2
| `"day"` | Text View | DD date | day |
| `"week_number"` | Text View | (WW) week number | week_number |
| `"month"` | Text View | month name (cf. monthFormat) | |
-| `"loop"`
`"loop_Ext1"` *
`"loop_Ext2"` * | Text View | min ago since last run and status (color arrows in background), color arrows can be tuned with DynData | loop |
+| `"loop"`
`"loop_Ext1"` *
`"loop_Ext2"` * | Text View | 上次运行至今的分钟数及状态（背景色箭头），可通过DynData调整箭头颜色 | loop |
| `"direction"`
`"direction_Ext1"` *
`"direction_Ext2"` * | Image View | TrendArrows | direction |
| `"timestamp"`
`"timestamp_Ext1"` *
`"timestamp_Ext2"` * | Text View | integer (min ago) | timestamp |
| `"sgv"`
`"sgv_Ext1"` *
`"sgv_Ext2"` * | Text View | sgv value (mgdl or mmol) | sgv
sgvLevel
sgv_Ext1
sgvLevel_Ext1
sgv_Ext2
sgvLevel_Ext2 |
@@ -1317,52 +1317,52 @@ delta_Ext1
delta_Ext2
| `"minute_hand"` | Image View | | |
| `"second_hand"` | Image View | | |
-**View added in Custom Watchface V2.0 or above (available on AAPS 3.3.0 wear apk or above)*
+**自定义表盘V2.0及以上版本新增视图（需AAPS 3.3.0 wear apk或更高版本支持）*
(cwf-reference-list-of-json-keys)=
-### List of Json keys
+### Json键列表
(cwf-reference-common-keys)=
-#### Common keys
-
- that can be used on all view types (Text View, image View, graph view)
-
-| Key | type | comment / value |
-| ------------------------ | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `"width"` | int | width of view in pixel |
-| `"height"` | int | height of view in pixel |
-| `"topmargin"` | int | top margin in pixel |
-| `"leftmargin"` | int | left margin in pixel |
-| `"rotation"` | int | rotation angle in degrees |
-| `"visibility"` | string | see key value table |
-| `"dynData"` | string | key block name that will specify dynamic data to link and associated animation (colors, image, shift, rotation)
`"dynData": "customName",` (see below ) |
-| `"leftOffset"` | boolean | include this key with key value true to enable horizontal shift (positive or negative value) due to dynData value |
-| `"topOffset"` | boolean | include this key with key value true to enable vertical shift (positive or negative value) due to dynData value |
-| `"rotationOffset"` | boolean | include this key with key value true to enable rotation (positive or negative value) due to dynData value |
-| `"twinView"` | string | key of the other view (generally the other view also include the twinView parameter with the key of this view in it) |
-| `"topOffsetTwinHidden"` | int | number of pixel to shift view position vertically if twin view is hidden (positive or negative value)
topOffsetTwinHidden = (topOffset twinView - topOffset thisView)/2 |
-| `"leftOffsetTwinHidden"` | int | number of pixel to shift view position horizontally if twin view is hidden (positive or negative value)
leftOffsetTwinHidden= (leftOffset twinView - leftOffset thisView)/2 |
-| `"dynPref"` | string | key block name that will specify dynamic pref to link and associated animation (colors, image, shift, rotation)
`"dynPref": "customName",` (see below ) |
+#### 公共键
+
+ 可用于所有视图类型（文本视图、图像视图、图表视图）
+
+| 键 | 类型 | 注释/值 |
+| ------------------------ | ------- | -------------------------------------------------------------------------------------------- |
+| `"width"` | int | 视图宽度（像素） |
+| `"height"` | int | 视图高度（像素） |
+| `"topmargin"` | int | 上边距（像素） |
+| `"leftmargin"` | int | 左边距（像素） |
+| `"rotation"` | int | 旋转角度（度） |
+| `"visibility"` | string | 参见键值表 |
+| `"dynData"` | string | 指定关联动态数据及动画效果（颜色、图像、位移、旋转）的键区块名称
`"dynData": "customName",`（见下文） |
+| `"leftOffset"` | boolean | 包含此键并设为true可启用基于dynData值的水平位移（正值或负值） |
+| `"topOffset"` | boolean | 包含此键并设为true可启用基于dynData值的垂直位移（正值或负值） |
+| `"rotationOffset"` | boolean | 包含此键并设为true可启用基于dynData值的旋转（正值或负值） |
+| `"twinView"` | string | 另一视图的键（通常该视图也包含twinView参数，其中引用了本视图的键） |
+| `"topOffsetTwinHidden"` | int | 若孪生视图隐藏时垂直位移的像素数（正值或负值）
topOffsetTwinHidden = (孪生视图topOffset - 本视图topOffset)/2 |
+| `"leftOffsetTwinHidden"` | int | 若孪生视图隐藏时水平位移的像素数（正值或负值）
leftOffsetTwinHidden = (孪生视图leftOffset - 本视图leftOffset)/2 |
+| `"dynPref"` | string | 指定关联动态偏好设置及动画效果（颜色、图像、位移、旋转）的键区块名称
`"dynPref": "customName",`（见下文） |
(cwf-reference-textview-keys)=
-#### TextView keys
-
-| Key | type | comment |
-| -------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `"textsize"` | int | size of font in pixel (keep in mind that font can include top and bottom margin so the real text size will generally be smaller than the number of pixel set). Note that size should be smaller than view height to not be truncated |
-| `"gravity"` | string | see key value table |
-| `"font"` | string | see key value table for available fonts.
Can also be font filename (without extension) for fonts included into zip file |
-| `"fontStyle"` | string | see key value table |
-| `"fontColor"` | string | Manage color of the font
`"#RRVVBB"`: color code in RVB format, hexadecimal values #FF0000 is red
`"#AARRVVBB"`: AA include Alpha information (transparency), 00 is transparent, FF is opaque
`"bgColor"`: keyValue bgColor is an easy way to use highColor, midColor or lowColor according to BG value |
-| `"allCaps"` | boolean | true if you want text in uppercase (mainly day name or month name) |
-| `"background"` | string | `resource_filename` you can include a resource image as background of the text view (resource file will be resized to fit height and width of text view, but keeping image ratio). text value will be in front of background image.
- Note that this key can also be used for `chart` view to set a custom background to the chart, in front of background image |
-| `"color"` | string | Manage the color of view Background or tune color of image (if bitmap only)
`"#RRVVBB"`: color code in RVB format, hexadecimal values #FF0000 is red
`"#AARRVVBB"`: AA include Alpha information (transparency), 00 is transparent, FF is opaque
`"bgColor"`: keyValue bgColor is an easy way to use highColor, midColor or lowColor according to BG value
- For default embedded image (hand, dial) color will be applied directly, for bitmap image (jpg or png) this will apply a saturation gradient filter on imagae
- For svg this parameter will have no effect (color of svg files cannot be modified)
- Note that this key can also be used for `chart` view to set a custom background to the chart, in front of background image |
-| `"textvalue"` | string | Key specific to the 4 free text views included into the layout (from freetext1 to freetext4), this allow you to set the text that should be included (can be a label, or just `:` if you want to add a separator between hour view and minute view...)
-From Custom Watchface plugin v2 (AAPS 3.3), textvalue can be used to include a format string for the other textViews (to use with `dynValue` key and `dynData` or `dynPref`). for example |
-| `"dynValue"`* | boolean | true if you want to include raw value in (double). Useful with `texvalue` key if you want a dedicated format to show value |
+#### 文本视图键
+
+| 键 | 类型 | 备注 |
+| -------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `"textsize"` | int | 字体大小（像素）（请注意字体可能包含上下边距，因此实际文本大小通常小于设定的像素值）。 注意：字体大小应小于视图高度以避免被截断 |
+| `"gravity"` | string | 参见键值表 |
+| `"font"` | string | 可用字体参见键值表。
也可使用zip包内字体文件名（不含扩展名） |
+| `"fontStyle"` | string | 参见键值表 |
+| `"fontColor"` | string | 管理字体颜色
`"#RRVVBB"`：RVB格式色码（十六进制值，#FF0000为红色）
`"#AARRVVBB"`：AA含透明度（00全透明，FF不透明）
`"bgColor"`：键值bgColor可根据BG值自动选用highColor/midColor/lowColor |
+| `"allCaps"` | boolean | 若需文本大写（主要用于星期或月份名称）则设为true |
+| `"background"` | string | `resource_filename` 可将资源图片设为文本视图背景（资源文件将按比例缩放以适应文本视图尺寸）。 文本将显示在背景图前方。
- 注意：该键也可用于`图表`视图，为图表设置自定义背景（显示在背景图前方） |
+| `"color"` | string | 管理视图背景色或调整图像色彩（仅限位图）
`"#RRVVBB"`：RVB格式色码（十六进制值，#FF0000为红色）
`"#AARRVVBB"`：AA含透明度（00全透明，FF不透明）
`"bgColor"`：键值bgColor可根据BG值自动选用highColor/midColor/lowColor
- 默认嵌入图像（指针/表盘）将直接应用该色彩，位图（jpg/png）会叠加饱和度渐变滤镜
- 对svg文件无效（svg色彩不可修改）
- 注意：该键也可用于`图表`视图，在背景图前方设置自定义图表背景 |
+| `"textvalue"` | string | 布局中4个自由文本视图（从freetext1到freetext4）的专用键，用于设置要包含的文本（可以是标签，或仅`:`若需在小时视图和分钟视图间添加分隔符...）
+自Custom Watchface插件v2（AAPS 3.3）起，textvalue可包含其他文本视图的格式字符串（需配合`dynValue`键及`dynData`或`dynPref`使用）。 例如 |
+| `"dynValue"`* | boolean | 若需包含原始数值（双精度型）则设为true 若需用特定格式显示数值，与`texvalue`键配合使用 |
**Key added in Custom Watchface V2.0 or above (available on AAPS 3.3.0 wear apk or above)*
@@ -1370,24 +1370,24 @@ From Custom Watchface plugin v2 (AAPS 3.3), textvalue can be used to include a f
#### ImageView keys
-| Key | type | comment |
-| --------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `"color"` | string | Manage the color of view Background or tune color of image (if bitmap only)
`"#RRVVBB"`: color code in RVB format, hexadecimal values #FF0000 is red
`"#AARRVVBB"`: AA include Alpha information (transparency), 00 is transparent, FF is opaque
`"bgColor"`: keyValue bgColor is an easy way to use highColor, midColor or lowColor according to BG value
- For default embedded image (hand, dial) color will be applied directly, for bitmap image (jpg or png) this will apply a saturation gradient filter on imagae
- For svg this parameter will have no effect (color of svg files cannot be modified)
- Note that this key can also be used for `chart` view to set a custom background to the chart, in front of background image |
+| 键 | 类型 | 备注 |
+| --------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `"color"` | string | 管理视图背景色或调整图像色彩（仅限位图）
`"#RRVVBB"`：RVB格式色码（十六进制值，#FF0000为红色）
`"#AARRVVBB"`：AA含透明度（00全透明，FF不透明）
`"bgColor"`：键值bgColor可根据BG值自动选用highColor/midColor/lowColor
- 默认嵌入图像（指针/表盘）将直接应用该色彩，位图（jpg/png）会叠加饱和度渐变滤镜
- 对svg文件无效（svg色彩不可修改）
- 注意：该键也可用于`图表`视图，在背景图前方设置自定义图表背景 |
(cwf-reference-chartview-keys)=
#### ChartView keys
-| Key | type | comment |
-| -------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `"color"` | string | Manage the color of view Background or tune color of image (if bitmap only)
`"#RRVVBB"`: color code in RVB format, hexadecimal values #FF0000 is red
`"#AARRVVBB"`: AA include Alpha information (transparency), 00 is transparent, FF is opaque
`"bgColor"`: keyValue bgColor is an easy way to use highColor, midColor or lowColor according to BG value
- For default embedded image (hand, dial) color will be applied directly, for bitmap image (jpg or png) this will apply a saturation gradient filter on imagae
- For svg this parameter will have no effect (color of svg files cannot be modified)
- Note that this key can also be used for `chart` view to set a custom background to the chart, in front of background image |
-| `"background"` | string | `resource_filename` you can include a resource image as background of the text view (resource file will be resized to fit height and width of text view, but keeping image ratio). text value will be in front of background image.
- Note that this key can also be used for `chart` view to set a custom background to the chart, in front of background image |
+| 键 | 类型 | 备注 |
+| -------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `"color"` | string | 管理视图背景色或调整图像色彩（仅限位图）
`"#RRVVBB"`：RVB格式色码（十六进制值，#FF0000为红色）
`"#AARRVVBB"`：AA含透明度（00全透明，FF不透明）
`"bgColor"`：键值bgColor可根据BG值自动选用highColor/midColor/lowColor
- 默认嵌入图像（指针/表盘）将直接应用该色彩，位图（jpg/png）会叠加饱和度渐变滤镜
- 对svg文件无效（svg色彩不可修改）
- 注意：该键也可用于`图表`视图，在背景图前方设置自定义图表背景 |
+| `"background"` | string | `resource_filename` 可将资源图片设为文本视图背景（资源文件将按比例缩放以适应文本视图尺寸）。 文本将显示在背景图前方。
- 注意：该键也可用于`图表`视图，为图表设置自定义背景（显示在背景图前方） |
(cwf-reference-key-values)=
### Key values
-| Key value | key | comment |
+| Key value | key | 备注 |
| ---------------------------- | ---------- | --------------------------------------------------------------------------------- |
| `"gone"` | visibility | view hidden |
| `"visible"` | visibility | view visible in watchface (but visibility can be enable or disable in parameters) |
@@ -1412,7 +1412,7 @@ From Custom Watchface plugin v2 (AAPS 3.3), textvalue can be used to include a f
### DynData keys
-| Key | type | comment |
+| 键 | 类型 | 备注 |
| ------------------------- | ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `"dynData"` | block | define the block of all dynamic data blocks that will be used for the views. generally after the last view.
All the keys defined within this block will be used as key Value within view block:
`"dynData": { dynData blocks }`
and each block is defined by a custom name and several keys inside:
`"customName": { one dynData block }` |
| `"valueKey"` | string | name of dynamic data to use (generally same that associated view key).
If not existing, the default will be the values used for the view that uses this block.
for example you can define one block to customize battery level percentage without specifying valueKey, and then use the same block to customize uploader_battery and rig_battery |
@@ -1448,7 +1448,7 @@ From Custom Watchface plugin v2 (AAPS 3.3), textvalue can be used to include a f
### DynData key values
-| Key value | key | comment |
+| Key value | key | 备注 |
| ------------------------------------------------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `"sgv"`
`"sgv_Ext1"` *
`"sgv_Ext2"` * | valueKey | default minData = 39 mgdl
default maxData = 400 mgdl
- Note that real maxData is linked to your sensor and units are always in mgdl for internal values |
| `"sgvLevel"`
`"sgvLevel_Ext1"` *
`"sgvLevel_Ext2"` * | valueKey | default minData = -1 (Hypo)
default maxData = 1 (Hyper)
if BG is within Range = 0 |
@@ -1473,7 +1473,7 @@ From Custom Watchface plugin v2 (AAPS 3.3), textvalue can be used to include a f
### DynPref keys
-| Key | type | comment |
+| 键 | 类型 | 备注 |
| ---------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `"dynPref"` | block | define the block of all dynamic preference blocks that will be used for the views. Generally after the last view or after the dynData block.
All the keys defined within this block will be used as key Value within view block:
`"dynPref": { dynPref blocks }`
and each block is defined by a custom name and several keys inside:
`"customName": { one dynPref block }` |
| `"dynPref"` | string | *Within a view Block*
name of dynamic dynPref block to use (generally same that associated view key or associated preference). |
@@ -1491,7 +1491,7 @@ All keys included into [Preference keys](#cwf-reference-preference-keys) chapter
You can also you these additional key below included into AAPS (Custom) specific parameters:
-| Key | type | comment |
+| 键 | 类型 | 备注 |
| --------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `"key_units"` | boolean | *true*: if units selected on AAPS is mgdl
*false*: if units selected on AAPS is mmol |
| `"key_dark"` | boolean | *true*: to use a dark background
false: to use a light background
Note: this parameter is often use into previous AAPS watchfaces (AAPS, AAPS V2...) |
diff --git a/docs/CROWDIN/zh_CN/Getting-Started/CompatiblePumps.md b/docs/CROWDIN/zh_CN/Getting-Started/CompatiblePumps.md
index d80fca6ea5fd..c2b4ea37ebb0 100644
--- a/docs/CROWDIN/zh_CN/Getting-Started/CompatiblePumps.md
+++ b/docs/CROWDIN/zh_CN/Getting-Started/CompatiblePumps.md
@@ -29,6 +29,6 @@ AAPS可与多种胰岛素泵配合使用。 以下列表显示了当前支持
-  [OrangeLink Website](https://getrileylink.org/product/orangelink)
-  [433MHz RileyLink](https://getrileylink.org/product/rileylink433)
--  [Emalink Website](https://github.com/sks01/EmaLink) - [Contact Info](mailto:getemalink@gmail.com)
--  DiaLink - [Contact Info](mailto:Boshetyn@ukr.net)
--  [LoopLink Website](https://www.getlooplink.org/) - [Contact Info](https://jameswedding.substack.com/) - Untested
\ No newline at end of file
+-  [Emalink 网站](https://github.com/sks01/EmaLink) - [联系方式](mailto:getemalink@gmail.com)
+-  DiaLink - [联系方式](mailto:Boshetyn@ukr.net)
+-  [LoopLink官网](https://www.getlooplink.org/) - [联系方式](https://jameswedding.substack.com/) - 未经测试
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/Maintenance/ReleaseNotes.md b/docs/CROWDIN/zh_CN/Maintenance/ReleaseNotes.md
index 828c696b6dab..d072381b7e66 100644
--- a/docs/CROWDIN/zh_CN/Maintenance/ReleaseNotes.md
+++ b/docs/CROWDIN/zh_CN/Maintenance/ReleaseNotes.md
@@ -703,7 +703,7 @@ v3为新协议， 更加安全高效
(Releasenotes-important-notes-2-5-0)=
-### Important notes
+### 重要说明
- 请使用[Android Studio版本3.5.1](https://developer.android.com/studio/)或更高版本来[构建APK](../SettingUpAaps/BuildingAaps.md)或[更新](UpdateToNewVersion)。
- 如果您使用xDrip，[识别接收器](#xdrip-identify-receiver)必须设置。
diff --git a/docs/CROWDIN/zh_CN/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/zh_CN/Maintenance/UpdateToNewVersion.md
index 7bb5620c0ca2..6b4c49c8803f 100644
--- a/docs/CROWDIN/zh_CN/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/zh_CN/Maintenance/UpdateToNewVersion.md
@@ -4,7 +4,7 @@
由于医疗设备相关的法规，**AAPS**无法下载。 构建该应用供自己使用是合法的，但不得将副本提供给他人 详情请参阅[常见问题页面](../UsefulLinks/FAQ.md)。
-## Important notes
+## 重要说明
* 当有新版本发布时，请尽快更新至最新版本的 **AAPS**。
* 当有新版本可用时，**AAPS** 应用内会显示新版本的信息横幅。
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/zh_CN/SettingUpAaps/BuildingAaps.md
index dc55c6bd5240..7bd76351e312 100644
--- a/docs/CROWDIN/zh_CN/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/BuildingAaps.md
@@ -408,7 +408,7 @@ Android Studio现在将构建AAPS apk。 在右下角会显示“Gradle 构建
-Congratulations! 现在您已经构建了AAPS apk文件，接下来您将把这个文件传输到您的智能手机上。
+恭喜！ 现在您已经构建了AAPS apk文件，接下来您将把这个文件传输到您的智能手机上。
```{tip}
如果您认为将来可能会使用Android Wear智能手表，那么现在是构建AAPS Wear apk的最佳时机，以确保它与您的AAPS apk同步。
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md b/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md
index a8483909d365..b893821d5a18 100644
--- a/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md
@@ -380,7 +380,7 @@ min_5m_carbimpact的标准值：AMA算法为5，SMB算法为8。
## 胰岛素泵
-### BT Watchdog
+### 蓝牙看门狗
如有必要请激活蓝牙看门狗（例如，对于Dana泵）。 如果无法与泵建立连接，它将蓝牙关闭一秒钟。 这可能有助于解决某些手机上的蓝牙卡顿问题。
diff --git a/docs/CROWDIN/zh_CN/SupportingAaps/HowToEditTheDocs.md b/docs/CROWDIN/zh_CN/SupportingAaps/HowToEditTheDocs.md
index 37e40f9b1762..36c7afa75ba3 100644
--- a/docs/CROWDIN/zh_CN/SupportingAaps/HowToEditTheDocs.md
+++ b/docs/CROWDIN/zh_CN/SupportingAaps/HowToEditTheDocs.md
@@ -342,7 +342,7 @@ Markdown并非完全固化的标准规范，我们力求最大程度遵循该标
名词化（nominalisation）指对非实体事物（如过程、技术或情感）的命名形式。 名词化结构由动词派生而成。
-For example:
+例如：
| 动词 | 名词化 |
| --------- | ------------ |
diff --git a/docs/CROWDIN/zh_CN/UsefulLinks/DedicatedGoogleAccountForAaps.md b/docs/CROWDIN/zh_CN/UsefulLinks/DedicatedGoogleAccountForAaps.md
index f20206fbe8e6..abdb0f2b6725 100644
--- a/docs/CROWDIN/zh_CN/UsefulLinks/DedicatedGoogleAccountForAaps.md
+++ b/docs/CROWDIN/zh_CN/UsefulLinks/DedicatedGoogleAccountForAaps.md
@@ -144,4 +144,4 @@ Gmail将显示账户名称。它将要求你接受Gmail的条款和条件并确
-Congratulations! 恭喜！现在你已经创建了一个AAPS专用谷歌账户。 下一步是[构建AAPS应用](../SettingUpAaps/BuildingAaps.md)。
\ No newline at end of file
+恭喜！ 恭喜！现在你已经创建了一个AAPS专用谷歌账户。 下一步是[构建AAPS应用](../SettingUpAaps/BuildingAaps.md)。
\ No newline at end of file