diff --git a/docs/EN/Configuration/BG-Source.md b/docs/EN/Configuration/BG-Source.md index e3d2fe343562..81871dfa2c28 100644 --- a/docs/EN/Configuration/BG-Source.md +++ b/docs/EN/Configuration/BG-Source.md @@ -1,7 +1,7 @@ # CGMS/FGMS Configuration * [General](../Hardware/GeneralCGMRecommendation.md) -* [Data Smoothing](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) +* [Data Smoothing](../Usage/Smoothing-Blood-Glucose-Data.md) * [xDrip+Settings](./xdrip.md) * [Dexcom G7](../Hardware/DexcomG7.md) * [Dexcom G6](../Hardware/DexcomG6.md) diff --git a/docs/EN/Hardware/CgmNightscoutUpload.md b/docs/EN/Hardware/CgmNightscoutUpload.md index 38bd18ddec44..2ce94f1c77df 100644 --- a/docs/EN/Hardware/CgmNightscoutUpload.md +++ b/docs/EN/Hardware/CgmNightscoutUpload.md @@ -5,4 +5,4 @@ If you have any other CGM set up that sends your data to - In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). +- Select NSClient in [ConfigBuilder, BG Source](/Configuration/Config-Builder.md#bg-source). diff --git a/docs/EN/Hardware/DexcomG5.md b/docs/EN/Hardware/DexcomG5.md index 977af6764fc7..03e05494d922 100644 --- a/docs/EN/Hardware/DexcomG5.md +++ b/docs/EN/Hardware/DexcomG5.md @@ -2,45 +2,32 @@ ## If using G5 with xdrip+ -- If not already set up then download - [xdrip](https://github.com/NightscoutFoundation/xDrip) and follow - instructions on nightscout - ([G5](http://www.nightscout.info/wiki/welcome/nightscout-with-xdrip-and-dexcom-share-wireless/xdrip-with-g5-support). -- In xdrip go to Settings > Inter-app settings > Broadcast Data - Locally and select ON. -- In xdrip go to Settings > Inter-app settings > Accept Treatments and - select OFF. -- If you want to be able to use AAPS to calibrate then in xdrip - go to Settings > Interapp Compatibility > Accept Calibrations and - select ON. You may also want to review the options in Settings > - Less Common Settings > Advanced Calibration Settings. -- Select xdrip in ConfigBuilder (setting in AAPS). -- If AAPS does not receive BG values when phone is in airplane mode - use 'Identify receiver' as describe on [xDrip+ settings - page](../Configuration/xdrip.md) . +- You can safely download the [latest APK (stable)](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk) unless you want specific newly developed features. +- Setup xDrip+ with G5 following [these instructions](https://navid200.github.io/xDrip/docs/G5-Recommended-Settings.html). +- Setup xDrip+ reading the [xDrip+ settings page](../Configuration/xdrip.md) . +- Select xDrip+ in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). ## If using G5 with patched Dexcom app -- Download the apk from , and - choose the version that fits your needs (mg/dl or mmol/l version, - G5). - - - Folder 2.3 is for users of AAPS 2.3, folder 2.4 for users - of AAPS 2.5. - - Open on - your computer. Region will be visible in URL. +:::{admonition} Legacy apps +:class: warning +These apps are not compatible with recent Android versions. +::: +- Download the apk from , and choose the version that fits your needs (mg/dl or mmol/l version, G5). + + - Folder 2.4 was for users of AAPS 2.5 and above. + - Open on your computer. Region will be visible in URL. + ![Region in Dexcom G5 URL](../images/DexcomG5regionURL.PNG) - -- Stop sensor and uninstall the original Dexcom app, if not already - done. - + +- Force stop and uninstall the original Dexcom app, if not already done. + - Install downloaded apk - Start sensor -- Select Dexcom App (patched) in ConfigBuilder (setting in - AAPS). +- Select Dexcom App (patched) in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). - If you want to use xDrip alarms via local broadcast: in xDrip hamburger menu > settings > hardware data source > 640G /EverSense. diff --git a/docs/EN/Hardware/DexcomG6.md b/docs/EN/Hardware/DexcomG6.md index 4a77e51da0c0..a811d59747d2 100644 --- a/docs/EN/Hardware/DexcomG6.md +++ b/docs/EN/Hardware/DexcomG6.md @@ -6,41 +6,46 @@ ## General hints for looping with G6 -To use it safely, there are a few points to be aware of: +- Recent transmitters are called Firefly. Sensors cannot be restarted without removing the transmitter, which itself cannot be reset, they also do not generate raw data. -- If you are using a rebatteried or modded transmitter with xDrip+, the safest thing to do is **disable** preemptive restarts of the sensor that are anyway not needed for xDrip+. -- Pre-soaking of the G6 with factory calibration is likely to give variation in results. If you do pre-soak, then to get best results, - you will probably need to calibrate the sensor. +- If you are restarting sensors, ensure you are ready to calibrate and keep an eye on variation. -To learn more about the details and reasons for these recommendations read the [complete article](https://www.diabettech.com/artificial-pancreas/diy-looping-and-cgm/) published by Tim Street at -[www.diabettech.com](https://www.diabettech.com). +- Pre-soaking of the G6 with factory calibration is likely to give variation in results. If you do pre-soak, then to get best results, you will probably need to calibrate the sensor. + +Read more in the [article](https://www.diabettech.com/artificial-pancreas/diy-looping-and-cgm/) published by Tim Street at [www.diabettech.com](https://www.diabettech.com). ## If using G6 with xDrip+ +- If you are using a recent (Firefly) transmitter, preemptive restarts are **ignored**. +- If you are using a modded transmitter you do **not need** to use preemptive restarts. +- If you are using an old rebatteried transmitter, the safest thing to do is **disable** [preemptive restarts](https://navid200.github.io/xDrip/docs/Preemptive-Restart.html). Though, in this case you will have to use the G6 in non-[native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm.html) (which is unadvisable as it disables factory calibration and doesn't filter noisy readings), or else the sensor will stop after 10 days. - The Dexcom G6 transmitter can simultaneously be connected to the Dexcom receiver (or alternatively the t:slim pump) and one app on your phone. -- When using xDrip+ as receiver uninstall Dexcom app first. **You cannot connect xDrip+ and Dexcom app with the transmitter at the same time!** -- If you need Clarity and want to profit from xDrip+ alarms use the [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) with local broadcast to xDrip+. +- When using xDrip+ as receiver uninstall the Dexcom app first. **You cannot connect xDrip+ and Dexcom app with the transmitter at the same time!** +- If you need Clarity and want to profit from xDrip+ alarms use the [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) with local broadcast to xDrip+. You can also use xDrip+ as a companion app of the official Dexcom app, but you might experience delays in BG readings. - If not already set up, download [xDrip+](https://github.com/NightscoutFoundation/xDrip) and follow the instructions on [xDrip+ settings page](../Configuration/xdrip.md). -- Select xDrip+ in ConfigBuilder (setting in AAPS). -- Adjust settings in xDrip+ according to [xDrip+ settings page](../Configuration/xdrip.md) -- If AAPS does not receive BG values when phone is in airplane mode use 'Identify receiver' as describe on [xDrip+ settings - page](../Configuration/xdrip.md). +- Select xDrip+ in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). + +- Adjust settings in xDrip+ according to [xDrip+ settings page](../Configuration/xdrip.md) (DexcomG6-if-using-g6-with-build-your-own-dexcom-app)= ## If using G6 with Build Your Own Dexcom App -- As of December 2020 [Build Your Own Dexcom App](https://docs.google.com/forms/d/e/1FAIpQLScD76G0Y-BlL4tZljaFkjlwuqhT83QlFM5v6ZEfO7gCU98iJQ/viewform?fbzx=2196386787609383750&fbclid=IwAR2aL8Cps1s6W8apUVK-gOqgGpA-McMPJj9Y8emf_P0-_gAsmJs6QwAY-o0) (BYODA) also supports local broadcast to AAPS and/or xDrip+ (not for +- [Build Your Own Dexcom App](https://docs.google.com/forms/d/e/1FAIpQLScD76G0Y-BlL4tZljaFkjlwuqhT83QlFM5v6ZEfO7gCU98iJQ/viewform?fbzx=2196386787609383750) (BYODA) supports local broadcast to AAPS and/or xDrip+ (not for G5/ONE/G7 sensors!) + +![BYODA broadcast options](../images/BYODA.png) + - This app lets you use your Dexcom G6 with any Android smartphone. - Uninstall the original Dexcom app or patched Dexcom app if you used one of those previously (**do not stop** the currently running sensor) -- Install downloaded apk +- Install the downloaded apk - Enter sensor code and transmitter serial no. in patched app. - In phone settings go to apps > Dexcom G6 > permissions > additional permissions and press 'Access Dexcom app'. - After short time BYODA should pick-up transmitter signal. ### Settings for AAPS -- Select 'Dexcom App (patched)' in config builder. +- Select 'Dexcom App (patched)' in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). + - If you don't receive any values select any other data source, then re-select 'Dexcom App (patched)' to trigger the demand for permissions to establish the connection between AAPS and BYODA-broadcast. @@ -63,4 +68,4 @@ General Troubleshooting for CGMs can be found [here](./GeneralCGMRecommendation. ### New transmitter with running sensor -If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found at and [here](https://navid200.github.io/xDrip/docs/Remove-transmitter.html). +If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found [here](https://navid200.github.io/xDrip/docs/Remove-transmitter.html). If you opt for [this solution](https://youtu.be/tx-kTsrkNUM) instead, you must be careful to avoid [damaging sensor contacts](https://navid200.github.io/xDrip/docs/Petroleum-jelly-in-Dexcom-G6-Sensor.html) with the strip. diff --git a/docs/EN/Hardware/DexcomG7.md b/docs/EN/Hardware/DexcomG7.md index 4618a71192c2..b9e5243dcd93 100644 --- a/docs/EN/Hardware/DexcomG7.md +++ b/docs/EN/Hardware/DexcomG7.md @@ -30,7 +30,8 @@ After the warm-up phase, the values are displayed as usual in the G7 app. ### Configuration in AAPS For the configuration in AAPS -- Select 'BYODA' in the configuration generator - even if it is not the BYODA app! +- Select 'BYODA' in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source) - even if it is not the BYODA app! + - If AAPS does not receive any values, switch to another BG source and then back to 'BYODA' to invoke the query for approving data exchange between AAPS and BYODA. The smoothing of glucose values can be activated by enabling the "Average smoothing" or "Exponential Smoothing" plugin in the Config Builder. To disable select the "No Smoothing" option. @@ -38,15 +39,17 @@ The smoothing of glucose values can be activated by enabling the "Average smooth **Exponential Smoothing** **MUST** be enabled for meaningful use of the G7 values. -## 2. Xdrip+ (direct connection to G7) +## 2. xDrip+ (direct connection to G7) - Follow the instructions here: [Xdrip+ G7](https://navid200.github.io/xDrip/docs/Dexcom/G7.html) -- In AAPS select > Configuration > BG source > xDrip+. -Adjust the xDrip+ settings according to the explanations on the xDrip+ settings page [xDrip+ settings](../Configuration/xdrip.md) +- Select xDrip+ in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). + +- Adjust the xDrip+ settings according to the explanations on the xDrip+ settings page [xDrip+ settings](../Configuration/xdrip.md) + +## 3. xDrip+ (companion mode) -## 3. Xdrip+ (companion mode) +- Download and install xDrip+: [xDrip](https://github.com/NightscoutFoundation/xDrip) +- As data source in xDrip+ "Companion App" must be selected and under Advanced Settings > Bluetooth Settings > "Companion Bluetooth" must be enabled. +- Select xDrip+ in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). -- Download and install Xdrip+: [xdrip](https://github.com/NightscoutFoundation/xDrip) -- As data source in Xdrip "Companion App" must be selected and under Advanced Settings > Bluetooth Settings > "Companion Bluetooth" must be enabled. -- In AAPS select > Configuration > BG source > xDrip+. -Adjust the xDrip+ settings according to the explanations on the xDrip+ settings page [xDrip+ settings](../Configuration/xdrip.md) +- Adjust the xDrip+ settings according to the explanations on the xDrip+ settings page [xDrip+ settings](../Configuration/xdrip.md) diff --git a/docs/EN/Hardware/Eversense.md b/docs/EN/Hardware/Eversense.md index d09a2853abf7..8643220b08e2 100644 --- a/docs/EN/Hardware/Eversense.md +++ b/docs/EN/Hardware/Eversense.md @@ -4,6 +4,12 @@ The easiest way to use Eversense with AAPS is to install the EU or US modified [ **Warning: by uninstalling the old app, your local historical data older than one week will be lost!** -To finally get your data to AAPS, you need to install [ESEL](https://github.com/BernhardRo/Esel/releases) and enable "Send to AAPS and xDrip" in ESEL and "MM640g" as BG source in the [Configuration Builder](../Configuration/Config-Builder.md) in AAPS. As the BG data from Eversense can be noisy sometimes, it is good to enable "Smooth Data" in ESEL, which is better than enabling "Always use short average delta instead of simple delta" in AAPS. +- To get your data to AAPS, you need to install [ESEL](https://github.com/BernhardRo/Esel/blob/master/apk/debug/app-debug.apk) and enable "Send to AAPS and xDrip", disable "Send to NightScout". + +![ESEL Broadcast](../images/ESEL.png) + +As the BG data from Eversense can be noisy sometimes, it is good to enable "Smooth Data" in ESEL, which is better than enabling "Always use short average delta instead of simple delta" in AAPS. + +- Set "MM640g" as BG source in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). You can find the instruction for using xDrip with an Eversense [here](https://github.com/BernhardRo/Esel/tree/master/apk). diff --git a/docs/EN/Hardware/GeneralCGMRecommendation.md b/docs/EN/Hardware/GeneralCGMRecommendation.md index 1af337fb2448..21ec5e9122b6 100644 --- a/docs/EN/Hardware/GeneralCGMRecommendation.md +++ b/docs/EN/Hardware/GeneralCGMRecommendation.md @@ -13,6 +13,7 @@ whether or not you are using DIY CGM software or the official apps. - Do “enough” calibrations – on official apps, you will be prompted for once or twice per day checks. On DIY systems you may not be, and should be careful about continuing without calibrations. +- For sensors not requiring or not allowing calibration, check at least daily real blood sugar. AAPS will be as safe as your sensor readings are reliable. - If it all possible, calibrate with some of your readings in a lower range (4-5mmol/l or 72-90mg/dl) and some at a slightly higher level (7-9mmol/l or 126-160mg/dl) as this provides a better range for the @@ -21,7 +22,7 @@ whether or not you are using DIY CGM software or the official apps. ## Setting sensor (G6) When setting sensor, it is recommended not to press the inserter too -firmly in order to avoid bleeding. The sensor thread should not come +firmly in order to avoid bleeding. The sensor contacts should not come into contact with blood. After setting the sensor, the transmitter can be clicked into the sensor @@ -42,7 +43,7 @@ backfilled. ### Sensor Errors If recurring sensor errors occur try selecting a different body site to -set your sensor. The sensor thread should not come into contact with +set your sensor. The sensor contacts should not come into contact with blood. Often a "Sensor Error" can be corrected by immediate drinking and diff --git a/docs/EN/Hardware/Libre1.md b/docs/EN/Hardware/Libre1.md index 13bac9841ce9..3096f8443e6d 100644 --- a/docs/EN/Hardware/Libre1.md +++ b/docs/EN/Hardware/Libre1.md @@ -37,21 +37,20 @@ details. - You can safely download the [latest APK (stable)](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk) unless you need recent features, in which case you should use the latest [Nightly Snapshot](https://github.com/NightscoutFoundation/xDrip/releases). - Follow setup instructions on [xDrip+ settings page](../Configuration/xdrip.md). - You also need [OOP2](https://drive.google.com/file/d/1f1VHW2I8w7Xe3kSQqdaY3kihPLs47ILS/view) for Libre 1 US (and Libre 2 EU). -- Select xDrip+ for BG Source in ConfigBuilder (setting in AAPS). +- Select xDrip+ in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). ## 2. Using Glimp -- Glimp supports Miaomiao, Blucon and Bubble. -- You will need Glimp version 4.15.57 or newer. Older versions are not - supported. +- Glimp supports Miaomiao, Blucon and Bubble for Libre 1 and Libre 2 EU. +- You will need Glimp version 4.15.57 or newer. Older versions are not supported. - Install [Glimp](https://play.google.com/store/apps/details?id=it.ct.glicemia). -- Select Glimp for BG Source in ConfigBuilder (setting in AAPS). +- Select Glimp in in [ConfigBuilder, BG Source.](../Configuration/Config-Builder.md#bg-source) ## 3. Using Tomato - Tomato is the vendor app for Miaomiao. - Install [Tomato](http://tomato.cool/#download_page) and follow the vendor [instructions](http://tomato.cool/how-to-broadcast-data-to-android-aps/tips/). -- Select Tomato for BG Source in ConfigBuilder (setting in AAPS). +- Select Tomato in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). ## 4. Using Diabox @@ -60,4 +59,4 @@ details. ![Diabox](../images/Diabox.png) -- Select xDrip+ for BG Source in ConfigBuilder (setting in AAPS). +- Select xDrip+ in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). diff --git a/docs/EN/Hardware/Libre2.md b/docs/EN/Hardware/Libre2.md index 44e8205d0e87..0b8c4f83691e 100644 --- a/docs/EN/Hardware/Libre2.md +++ b/docs/EN/Hardware/Libre2.md @@ -34,7 +34,7 @@ xDrip+ doesn't support direct connection to Libre 2 US and AUS. - Follow [these instructions](https://www.minimallooper.com/post/how-to-setup-freestyle-libre-2-and-oop2-to-use-a-native-bluetooth-connection-in-xdrip) to setup xDrip+ but make sure to download [this latest OOP2](https://drive.google.com/file/d/1f1VHW2I8w7Xe3kSQqdaY3kihPLs47ILS/view) as the one in the document is obsolete. - Follow setup instructions on [xDrip+ settings page](../Configuration/xdrip.md). -- Select xDrip+ for BG Source in ConfigBuilder (setting in AAPS). +- Select xDrip+ in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). ## 3. Use Diabox @@ -42,7 +42,7 @@ xDrip+ doesn't support direct connection to Libre 2 US and AUS. ![Diabox](../images/Diabox.png) -- Select xDrip+ for BG Source in ConfigBuilder (setting in AAPS). +- Select xDrip+ in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). ## 4. Use Juggluco @@ -52,7 +52,7 @@ xDrip+ doesn't support direct connection to Libre 2 US and AUS. ![Juggluco broadcast to AAPS](../images/Juggluco_AAPS.png) -- Select xDrip+ for BG Source in ConfigBuilder (setting in AAPS). +- Select xDrip+ in in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). :::{admonition} Use with xDrip+ :class: note @@ -227,6 +227,9 @@ activation and make a new initial calibration. ### Step 5: Configure AAPS (for looping only) - In AAPS go to Config Builder > BG Source and check 'xDrip+' + +![xDrip+ BG Source](../images/ConfBuild_BG_xDrip.png) + - If AAPS does not receive BG values when phone is in airplane mode, use 'Identify receiver' as describe on [xDrip+ settings page](xdrip-identify-receiver). diff --git a/docs/EN/Hardware/Libre3.md b/docs/EN/Hardware/Libre3.md index fd7541dea5e2..0f9b4f69fe3c 100644 --- a/docs/EN/Hardware/Libre3.md +++ b/docs/EN/Hardware/Libre3.md @@ -58,7 +58,8 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d ### Step 4: Configure AndroidAPS -- In AndroidAPS go to Config Builder -> BG Source and check "xDrip+" +- Select xDrip+ in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). + - If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver" - Turn of Smoothing (done in Xdrip+ already) @@ -70,13 +71,13 @@ As of now, when using Libre 3 as a BG source, the "Always enable SMB" and "Enabl 1. Open Juggluco and note the serial number of the existing sensor -![Libre serial number](../images/libre3/step\_13.jpg) +![Libre serial number](../images/libre3/step/_13.jpg) 2. Now simply scan your new sensor with your phone’s NFC reader. Juggluco will display a notice if the process had been started successfully. 3. When you are ready to deactivate the old sensor, then open the Juggluco menu by clicking anywhere in the empty space in the upper left hand corner of the screen. 4. Select the exired sensor and tap "Terminate" -![Terminate sensor](../images/libre3/step\_14.jpg) +![Terminate sensor](../images/libre3/step/_14.jpg) Note: When two sensors are active Juggluco will send the most recent value from either sensor to xDrip+. If the sensors are not calibrated and reading BG similarly, this may result in jumpy BG values being reported to xDrip+. If you terminate the wrong sensor, you can reactivate it by simply scanning the sensor. diff --git a/docs/EN/Hardware/MM640g.md b/docs/EN/Hardware/MM640g.md index d6c645cddeab..ced2351e13ee 100644 --- a/docs/EN/Hardware/MM640g.md +++ b/docs/EN/Hardware/MM640g.md @@ -1,9 +1,10 @@ # For users of MM640g or MM630g -- If not already set up then download - [600SeriesAndroidUploader](https://pazaan.github.io/600SeriesAndroidUploader/) - and follow instructions on - [Nightscout](https://nightscout.github.io/uploader/setup/?h=uploader#medtronic-600-series-with-uploader). -- In 600 Series Uploader go to Settings > Send to xdrip+ and select ON - (tick). -- Select MM640g in ConfigBuilder (setting in AAPS). +- If not already set up then download [600SeriesAndroidUploader](https://pazaan.github.io/600SeriesAndroidUploader/) + and follow instructions on [Nightscout](https://nightscout.github.io/uploader/setup/?h=uploader#medtronic-600-series-with-uploader). +- In 600 Series Uploader go to Settings > Send to xDrip+ and select ON (tick). + +![600 series uploader](../images/600Uploader.png) + +- Select MM640g in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). + diff --git a/docs/EN/Hardware/PocTech.md b/docs/EN/Hardware/PocTech.md index b8bc77cee979..7b28982eab33 100644 --- a/docs/EN/Hardware/PocTech.md +++ b/docs/EN/Hardware/PocTech.md @@ -1,4 +1,4 @@ # For users of PocTech CT-100 - Install PocTech App -- Select PocTech App in ConfigBuilder (setting in AAPS) +- Select PocTech App in [ConfigBuilder, BG Source](../Configuration/Config-Builder.md#bg-source). diff --git a/docs/EN/Usage/Smoothing-Blood-Glucose-Data.md b/docs/EN/Usage/Smoothing-Blood-Glucose-Data.md index 504b823e277c..d23a986b1a8d 100644 --- a/docs/EN/Usage/Smoothing-Blood-Glucose-Data.md +++ b/docs/EN/Usage/Smoothing-Blood-Glucose-Data.md @@ -1,20 +1,33 @@ (Smoothing-Blood-Glucose-Data)= # Smoothing blood glucose data -If BG data is jumpy/noisy AAPS may dose insulin incorrectly resulting in high or low BG. If you observe errors in your CGM data it is important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. +If **BG** data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in highs or lows. If you observe errors in your CGM data it is important to disable the loop until the problem is resolved. Depending on your CGM, such issues may be due to the CGM configuration in **AAPS** (as explained further below); or CGM sensor site issue (which may require replacing the CGM sensor) Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. -Additionally, as of version 3.2, AAPS offers the option to smooth the data within AAPS. There are three options: +Additionally, as of version 3.2, AAPS offers the option to smooth the data within AAPS. There are three options available in the [Config Builder](../Configuration/Config-Builder.md). -##Exponential smoothing +![Smoothing](../images/ConfBuild_Smoothing.png) -This is the recommended option to start with as it is most aggressive in resolving noise and rewrites the most recent value. +## Exponential smoothing -##Average smoothing +This is the recommended option to start with as it is most aggressive in resolving noise and rewrites the most recent value. -This option works similar to back smoothing that was previously implemented on certain CGM platforms. It is more reactive to recent changes in BG value and therefore more prone to responding incorrectly to noisy CGM data. +## Average smoothing -##No Smoothing +This option works similar to back smoothing that was previously implemented on certain CGM platforms. It is more reactive to recent changes in BG value and therefore more prone to responding incorrectly to noisy CGM data. + +## No Smoothing + +Use this option only if your CGM data is being properly smoothed by your collector app before being transmitted to AAPS. + +## Suggestions to use smoothing + +| | Exponential | Average | None | +| ------------------------------------------------------------ | :---------: | :---------: | :---------: | +| G5 and G6 with BYODA
or xDrip+ **[native](https://navid200.github.io/xDrip/docs/Native-Algorithm.html)** | | If noisy | Recommended | +| Refurbished G5 and G6
with xDrip+ **[non-native](https://navid200.github.io/xDrip/docs/Native-Algorithm.html)** | If noisy | Recommended | | +| G7 | Recommended | | | +| Libre 1 or Juggluco | Recommended | | | +| Libre 2 and 3 from xDrip+ | | | Recommended | -Use this option only if your CGM data is being properly smoothed by your collector app beore being transmitted to AAPS. diff --git a/docs/EN/images/600Uploader.png b/docs/EN/images/600Uploader.png new file mode 100644 index 000000000000..3b2a45450a15 Binary files /dev/null and b/docs/EN/images/600Uploader.png differ diff --git a/docs/EN/images/BYODA.png b/docs/EN/images/BYODA.png new file mode 100644 index 000000000000..8fd7c347c916 Binary files /dev/null and b/docs/EN/images/BYODA.png differ diff --git a/docs/EN/images/ConfBuild_Smoothing.png b/docs/EN/images/ConfBuild_Smoothing.png new file mode 100644 index 000000000000..c3fa79b033b0 Binary files /dev/null and b/docs/EN/images/ConfBuild_Smoothing.png differ diff --git a/docs/EN/images/ESEL.png b/docs/EN/images/ESEL.png new file mode 100644 index 000000000000..8fae03382ec6 Binary files /dev/null and b/docs/EN/images/ESEL.png differ