Welcome to the AAPS documentation
AAPS is an open source app for people living with insulin-dependent diabetes that acts as an artificial pancreas system (APS) on Google Android smartphones. It uses an openAPS software algorithm which aims to do what a living pancreas does: keeping blood sugar levels within healthy limits by using automated insulin dosing (AID). Additionally, you need a supported and FDA/CE approved insulin pump, and a continuous glucose meter.
Interested? Read more about AAPS in the introduction.
Warning
IMPORTANT SAFETY NOTICE
The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. It is critically important that you only use a tested, fully functioning FDA or CE approved insulin pump and CGM for closing an automated insulin dosing loop. Hardware or software modifications to these components can cause unexpected insulin dosing, causing significant risk to the user. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, do not use these for creating an AAPS system.
Additionally, it is equally important to only use original supplies such as inserters, cannulas and insulin containers approved by the manufacturer for use with your pump or CGM. Using untested or modified supplies can cause CGM inaccuracy and insulin dosing errors. Insulin is highly dangerous when misdosed - please do not play with your life by hacking with your supplies.
Last not least, you must not take SGLT-2 inhibitors (gliflozins) as they incalculably lower blood sugar levels. The combination with a system that lowers basal rates in order to increase BG is especially dangerous as due to the gliflozin this rise in BG might not happen and a dangerous state of lack of insulin can happen.
Note
Disclaimer and Warning
All information, thought, and code described here is intended for informational and educational purposes only. Nightscout currently makes no attempt at HIPAA privacy compliance. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions.
Use of code from github.com is without warranty or formal support of any kind. Please review this repository’s LICENSE for details.
All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. Their use is for information purposes and does not imply any affiliation with or endorsement by them.
Please note - this project has no association with and is not endorsed by: SOOIL, Dexcom, Accu-Chek, Roche Diabetes Care, Insulet or Medtronic.
Home
- Introduction
- What is an “Artificial Pancreas System”?
- What does hybrid closed loop mean?
- How and why did looping start?
- What is Android APS (AAPS)?
- What are the basic components of AAPS?
- What are the advantages of the AAPS system?
- How does AAPS compare to MDI and open looping?
- How does AAPS compare to other looping systems?
- Does AAPS use artificial intelligence or any learning algorithm?
- Which system is right for me or my dependant?
- Is it safe to use open-source systems like AAPS?
- How can I approach discussing AAPS with my clinical team?
- Why can’t I just download AAPS and use it straight away?
- What is the connectivity of the AAPS system?
- How does AAPS get continually developed and improved?
- Who can benefit from AAPS?
- What benefits can I get?
Getting Started
- Preparing
- Guide to the AndroidAPS documentation
- First Steps
- Safety
- How quickly can I reduce my HbA1c without risking permanent damage?
- Key Principles
- Plan for delays and minor issues in getting everything set up and running
- Technology compatibility
- App build time
- Keystore & configuration settings export file
- Time to progress to full looping after building AAPS and setting up the loop
- Troubleshooting
- Section overview
- First Steps
- What are we going to build and install?
- How long will it take?
- Requirements
- Introduction to your AAPS profile
- Guide to the AndroidAPS documentation
Setting up AAPS
- Setting up the reporting server
- Building AAPS
- Installing AAPS
- Configuring the AAPS loop
- Completing the objectives
- Objective 1: Setting up visualization and monitoring, analysing basals and ratios
- Objective 2: Learn how to control AAPS
- Objective 3: Prove your knowledge
- Objective 4: Starting on an open loop
- Objective 5: Understanding your open loop, including its temp basal recommendations
- Objective 6: Starting to close the loop with Low Glucose Suspend
- Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets
- Objective 8: Adjust basals and ratios if needed, and then enable autosens
- Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB)
- Objective 10: Automation
- Go back in objectives
- Objectives in Android APS before version 3.0
Remote control and following
- Remote control
- Considerations when setting up remote control of AAPS for a child
- 1) SMS Commands
- SMS command safety
- Different types of SMS commands
- SMS commands tables
- Authentication or not?
- How to set up SMS commands
- Let’s get started!
- i) Now that the phone settings have been checked, in the AAPS app itself, use the left hand hamburger menu to navigate to Config Builder:
- ii) Enable “SMS communicator” by checking the boxes, then click the “cog” to get to the SMS communicator preferences screen:
- iii) On the preferences screen enable “allow remote commands via SMS”:
- iv) Enter the caregiver phone number(s). Include the country code and exclude the first “0” of the phone number, as shown in these examples:
- v) Choose a PIN which you (and any other caregivers) are going to use at the end of the authenticator code when the SMS command is sent.
- vi) On the preferences screen select “Authenticator setup”
- First steps using SMS commands
- Additional safety notes on SMS commands
- Delivering mealtime boluses through SMS commands
- SMS commands troubleshooting and FAQ
- Q: What can’t we do with SMS commands?
- Q: What happens if I change my mind about a command I have just sent?
- Q. Why am I getting multiple SMS texts of the same message?
- Q. I’ve just set up SMS commands and I am now getting far too many text messages. Can I reduce the frequency, or make them stop?
- Q. Why are SMS commands not working on my Samsung phone?
- Q. How can I fix issues with the Android Messages App?
- 2) NSClient
- 3) Nightscout
- 4) Smartwatches
- Following-only
Old-Getting started
- Safety first
- What is a closed loop system
- What is a closed loop system with AAPS
- Docs updates & changes
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- June 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- October 2020
- September 2020
- June 2020
- May 2020
- April 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
Old-What do I need
Old-How to Install AAPS
- New Building the APK
- Windows PC setup & building AAPS
- How to set up a dedicated Google account for AAPS
- Step-by-step guide to setting up a separate Google account and drive:
- Go https://account.google.com
- On the Gmail page enter your NEW dedicated account:
- Next enter your persona:
- Choose your NEW email address & password
- Enter a phone number which can receive Gmail’s SMS verification
- Enter the recovery email address,
- Finishing up the account.
- Customizing the new profile.
- Configuring the new Gmail account
- Open the Gmail website on both windows
- In the new Gmail account (bottom window) open Gmail settings…
- Setup forwarding…
- Verify the forwarded email address…
- Finally archive forwarded emails in the new dedicated account gmail(bottom window)
- Mount google drive(s) on your PC & Phone
- Prepare Nightscout for integration with AAPS
- Install Git on your computer
- Install Android Studio
- Set Git path in preferences
- Update to a new version or branch
- Troubleshooting
- Hints and Checks after update to AAPS 3.0
- Checks after update to AAPS 2.7
- Install git
- Troubleshooting Android Studio
- Release notes
- Android version and AAPS version
- Version 3.2.0
- Version 3.1.0
- Version 3.0.0
- Version 2.8.2
- Version 2.8.1.1
- Version 2.8.0
- Version 2.7.0
- Version 2.6.1.4
- Version 2.6.1.3
- Version 2.6.1.2
- Version 2.6.1.1
- Version 2.6.1
- Version 2.6.0
- Version 2.5.1
- Version 2.5.0
- Version 2.3
- Version 2.2.2
- Version 2.2
- Version 2.1
- Version 2.0
- Dev branch
Old-Component Setup
Old-Configuration
- Config builder
- Preferences
Old-AAPS Usage
- AAPS screens
- The Homescreen
- Bolus Wizard
- Action tab
- Insulin Profile
- Pump Status
- Care Portal
- Loop, AMA / SMB
- Profile
- Treatment
- BG Source - xDrip+, BYODA…
- NSClient
- Objectives
- Objective 1: Setting up visualization and monitoring, analysing basals and ratios
- Objective 2: Learn how to control AAPS
- Objective 3: Prove your knowledge
- Objective 4: Starting on an open loop
- Objective 5: Understanding your open loop, including its temp basal recommendations
- Objective 6: Starting to close the loop with Low Glucose Suspend
- Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets
- Objective 8: Adjust basals and ratios if needed, and then enable autosens
- Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB)
- Objective 10: Automation
- Go back in objectives
- Objectives in Android APS before version 3.0
- OpenAPS features
- Autosens
- Super Micro Bolus (SMB)
- Max U/h a temp basal can be set to (OpenAPS “max-basal”)
- Maximum total IOB OpenAPS can’t go over (OpenAPS “max-iob”)
- Enable AMA Autosens
- Enable SMB
- Enable SMB with COB
- Enable SMB with temp targets
- Enable SMB with high temp targets
- Enable SMB always
- Enable SMB after carbs
- Max minutes of basal to limit SMB to
- Enable UAM
- High temp-target raises sensitivity
- Low temp-target lowers sensitivity
- Advanced Settings
- Advanced Meal Assist (AMA)
- Overview of hard-coded limits
- COB calculation
- Sensitivity detection
- Profile switch
- Temp-targets
- Extended carbs
- Automation
- Autotune (dev only)
- Careportal (discontinued)
- Open Humans Uploader
- Automation with 3rd party apps
- Android auto
Old-General Hints
- Timezone traveling with pumps
- Time adjustment daylight savings time (DST)
- Accessing logfiles
- Accu-Chek Combo tips for basic usage
- Export/Import Settings
- xDrip engineering mode
Old-AAPS for children
Old-Troubleshooting
Old-FAQ
- FAQ for loopers
- General
- AAPS settings
- APS algorithm
- Other settings
- Frequent questions on Discord and their answers…
- My problem is not listed here.
- My problem is not listed here but I found the solution
- AAPS stops everyday around the same time.
- How to organize my backups ?
- I have problems, errors building the app.
- I’m stuck on an objective and need help.
- How to reset the password in AAPS v2.8.x ?
- How to reset the password in AAPS v3.x
- My link/pump/pod is unresponsive (RL/OL/EmaLink…)
- Build error: file name too long
- Alert: Running dev version. Closed loop is disabled
- Where can I find settings files?
- How to configure battery savings?
- Pump unreachable alerts several times a day or at night.
- Where can I delete treatments in AAPS v3 ?
- Configuring and Using the NSClient remote app
- I have a red triangle / AAPS won’t enable closed loop / Loops stays in LGS / I have a yellow triangle
- Can I move an active DASH Pod to other hardware?
- Procedure I follow in this:
- How do I import settings from earlier versions of AAPS into AAPS v3 ?
Old-Glossary
Old-Where to go for help
- Useful resources to read before you start
- Where to go for help
- Docs updates & changes
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- June 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- October 2020
- September 2020
- June 2020
- May 2020
- April 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
Old-For Clinicians
- For Clinicians
- The steps for building a DIY Closed Loop:
- How A DIY Closed Loop Works
- How data is gathered:
- How does it know what to do?
- Examples of AAPS algorithm decision making:
- Here are examples of the purple prediction lines, and how they might differ:
- Here are examples of different time frames that influence the needed adjustments to insulin delivery:
- Scenario 1 - Zero Temp for safety
- Scenario 2 - Zero temp for safety
- Scenario 3 - More insulin needed
- Scenario 4 - Low temping for safety
- Optimizing settings and making changes
- OpenAPS
- Summary
Old-How to help
- How to help
- How to translate the app and docs
- State of translations
- How to edit the docs
- General
- Code syntax
- Style Guide
- Contents
- 1. English language writing tips
- Use language that is appropriate for the reader
- Privacy/licensing concerns:
- Keep sentences short, get to the point
- Don’t be afraid to give instructions
- Mostly use active verbs, rather than passive verbs
- Avoid nominalisations
- Use lists where appropriate
- Mythbusting
- Optimising writing style by purpose
- 2. AAPS-specific writing/updating notes
- 3. Useful References
Old-Sandbox
Note
Disclaimer And Warning
All information, thought, and code described here is intended for informational and educational purposes only. Nightscout currently makes no attempt at HIPAA privacy compliance. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions.
Use of code from github.com is without warranty or formal support of any kind. Please review this repository’s LICENSE for details.
All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. Their use is for information purposes and does not imply any affiliation with or endorsement by them.
Please note - this project has no association with and is not endorsed by: SOOIL, Dexcom, Accu-Chek, Roche Diabetes Care or Medtronic