For this complaint code, please obtain the following:
- Pump SN
- Logfile
- Landscape Mode (Screenshot)
Problem
Smart device displays:
“Unable to start sensor. Please try again“, “Sensor start processing error”
“Incompatible sensor. This sensor cannot be used with this version of the app“
“Sensor already in use. The sensor you just scanned was started by another device and cannot be used“
“Unable to proceed to link with Freestyle Libre 3 sensor. Please connect to the internet and restart the CamAPS app. You can also try later but you should maintain connectivity to the internet.”
Error LBR004
Questions to be asked
- Is the user using a compatible phone running a compatible operating system
- Is the user using the most up to date version of the app.
- Is the user using a Huawei phone
- Please ask the user to submit logs.
- Was the message “Incompatible sensor…” displayed? (if YES, your sensor is not configured for use in your location or for use with CamAPS FX app (it has to be FreeStyle Libre 3); replace with a compatible sensor) https://www.diabetescare.abbott/support/manuals.html)
- Was the message “Sensor already in use…” displayed? ((If you have reinstalled the app and logged in with the same account, confirm the message and wait a few minutes. Your sensor cannot be used, if your sensor was started with either another app (e.g. FreeStyle Libre 3 app) or from another CamAPS FX account; replace the sensor)
- Was the message “Unable to start sensor. Please try again” or “Sensor start processing error”?
a. Are you using a recommended smart device and OS (https://www.diabetescare.abbott/support/manuals.html?
b. Are you using the most recent version of the CamAPS FX app (if NOT, update the app)
c. Is the NFC on your smart device turned on? Go to Settings>connections>NFC and payment> turn on (if already on, turn it off and back on again)
d. Check the location of NFC on your phone and rescan the sensor: follow ACTIONS below - Was the message “Unable to proceed to link with Freestyle Libre 3 sensor”
a. Are you using a recommended smart device and OS (https://www.diabetescare.abbott/support/manuals.html?
b. Are you using the most recent version of the CamAPS FX app (if NOT, update the app)
c. Check you are connected to the internet – unlink and relink to the wifi, by re-entering the wifi pairing key.
d. If still not resolved ‘Force Stop’ the app by going to Settings->Apps->CamAPS FX->Force stop on your smartphone; find CamAPS FX app on your phone home screen and log back in.
e. If the message is reoccurring despite the above, it is likely that the phone has not passed the cybersecurity integrity checks. - Was the message “Error LBR004”
a. Are you using a Huawei phone?
Questions to be documented
- NOTE pump SN, Phone model & OS;
- CamAPS FX version
Actions
- Turn NFC on (Settings>Connections>NFC and payment); if NFC is already on turn it off and back on
- Clear NFC cache (Settings > Apps, from top right menu select Show System Apps and find NFC, go to NFC>Storage> Clear cache)
- Go to App Main Menu >Start new sensor and follow instructions
- Scan the new sensor with the back of the smart device. NOTE: each smart device is different with regards to the location of the NFC area. You may have to touch the sensor with your smart device or move your device round over the senor very slowly until you learn the correct position; your phone will vibrate twice after successfully scanning the sensor. You may need to remove the phone case.
- Restart the smartphone or power cycle the smartphone.
- Uninstall the app through Google Play Store, restart smartphone and reinstall the app. NOTE your average Total Daily Insulin Dose over past 7 days and your weight before uninstalling the app, other settings and the learning will be restored from the cloud
- If the problem is not solved by the above steps replace the sensor. Refer to Abbott Diabetes Care for further information.
For Huawei phones follow the battery optimisation advice:
- Phone settings > Apps > Settings > Special access > Ignore battery optimisation
- Select allow
- Check that the app is allowed to work in the background
- Select allow for LOCATION
In Addition
- Phone settings > Battery > App Launch
- Select allow
- Check that the app is allowed to work in the background
- Select allow for LOCATION
Further options for bug fixes:
- General Connectivity Issues
- Huawei battery optimisation specific advice
- Android 10 specific advice
- Android 11 specific advice
Error Codes
LBR001 | MSG_UNKNOWN_ERROR | Internal error LBR001. Restart your smart device |
LBR002 | MSG_CRC_CHECK | Internal error LBR002. Restart your smart device |
LBR003 | MSG_CRC_CALC | Internal error LBR003. Restart your smart device |
LBR004 | TOO_BIG_GAP | Internal error LBR004. Restart your smart device |
LBR005 | MSG_WAKELOCK_ERROR | Internal error LBR005. Restart your smart device |
LBR006 | MSG_BAD_IDX_1 | Internal error LBR006. Restart your smart device |
LBR007 | MSG_BAD_IDX_2 | Internal error LBR007. Restart your smart device |
LBR008 | MSG_BAD_IDX_3 | Internal error LBR008. Restart your smart device |
LBR009 | MSG_BAD_IDX_4 | Internal error LBR009. Restart your smart device |
LBR010 | MSG_EXC_SAVE_INFO | Internal error LBR010. Restart your smart device |
LBR011 | MSG_START_SESS_ERR | Internal error LBR011. Restart your smart device |
LBR012 | DB_CREATION_FAIL | Internal error LBR012. Restart your smart device |
LBR013 | DB_DELETE_FAIL | Internal error LBR013. Restart your smart device |
LBR014 | DB_INTEGRITY_FAIL | Internal error LBR014. Restart your smart device |
LBR015 | DB_CONTEX_NULL | Internal error LBR015. Restart your smart device |
LBR016 | DB_OPEN_EXCEPTION | Internal error LBR016. Restart your smart device |
LBR017 | DB_GET_EXCEPTION1 | Internal error LBR017. Restart your smart device |
LBR018 | DB_GET_EXCEPTION2 | Internal error LBR018. Restart your smart device |
LBR019 | DB_INSULIN_FAILED | Internal error LBR019. Restart your smart device |
LBR020 | DB_INSULIN_EXCEPTION | Internal error LBR020. Restart your smart device |
LBR021 | DB_DEL_EXCEPTION | Internal error LBR021. Restart your smart device |
LBR022 | DB_DEL_EXCEPTION2 | Internal error LBR022. Restart your smart device |
LBR023 | HANDLER_STUCK | Internal error LBR023. Restart your smart device |
LBR024 | MSG_EXC_MSG_ACK | Internal error LBR024. Restart your smart device |
LBR025 | DB_DEL_EXCEPTION3 | Internal error LBR025. Restart your smart device |
LBR050 | MSG_SENSOR_6HOURS | Your sensor will end in less than 6 hours |
LBR051 | MSG_SENSOR_2HOURS | Your sensor will end in less than 2 hours |
LBR052 | MSG_SENSOR_30MINUTES | Your sensor will end in less than 30 minutes |
LBR053 | MSG_SENSOR_EXPIRED | Your sensor ended. You will not receive sensor glucose alerts |
LBR054 | MSG_URGENT_LOW | Urgent low glucose alarm |
LBR055 | MSG_LOW | Low glucose alert |
LBR056 | MSG_HIGH | High glucose alert |
LBR057 | MSG_FALL_RATE | Falling glucose alert |
LBR058 | MSG_RISE_RATE | Rising glucose alert |
LBR059 | MSG_SIGNAL_LOSS | Connection to your sensor has been lost. You will not receive sensor glucose alerts |
LBR060 | MSG_SENSOR_FAILED | Replace sensor. Your sensor is not working |
LBR061 | MSG_SENSOR_WARM_UP | Sensor warming up. Wait for 60 minutes |
LBR062 | MSG_URGENT_LOW_SOON | Urgent low glucose soon alert |
LBR063 | MSG_NO_READINGS | No sensor glucose readings alert. You will not receive sensor glucose alerts |
LBR064 | MSG_TEMP_LOW | Sensor too cold |
LBR065 | MSG_TEMP_HIGH | Sensor too hot |
LBR066 | MSG_CURR_SENSOR | The sensor you just scanned is already started |
LBR067 | MSG_WRONG_PIN | Unable to connect to sensor. Go to main menu, stop the previous sensor |
LBR068 | MSG_VITAMIN_C | Do not take high doses of vitamin C (more than 500mg per day) |
Trouble Shooting successful? | Yes → Close as service ticket in C4C No → Was customer already transferred from Abbott ADC to YPS?
|
---|---|
Complaint to open for: |
|
Addition: | Complaint Management reports case to 2nd level support |
Complaint Coding: | F106: Setup / Settings A525: CGM: pairing not possible |
Important
As soon as a troubleshooting was not successful, you have to open a complaint and you have to tell the patient to submit the logfile, a screenshot in Landscape Mode, the time of the error message (time / date) and the pump SN.
Images
Reasons behind
- Sensors other than FreeStyle Libre 3 are not compatible with CamAPS FX App
- FreeStyle Libre 3 sensors can only be used in a region specified in the ‘shipping code’
- FreeStyle Libre 3 sensor cannot be started again by CamAPS FX after it has been started by another app (e.g. FreeStyle Libre 3 app) or by the CamAPS FX app with a different login
- NFC communication is required to start the FreeStyle Libre 3 sensor
- CamAPS FX App conforms to high cybersecurity standards. Certain software running on the phone can make it appear “tampered with”. When the phone is plugged in to another device such as a laptop or desktop computer, it may be detected as “rooted”. Being “unlocked” (as is often the case with a second-hand phone), “tampered with” or “rooted” will prevent the phone from passing the online integrity checks.
- Force stopping the App refreshes the internet connection token on CamDiab cloud
- Huawei phones have a “power Genie” app that prevents the CamAPS FX app from staying open in the background.
FreeStyle Libre 3 Error List
Please refer the customer to Abbott Diabetes Care for the error codes listed below.
Code | Description | Possible Cause(s) | Interface | Display | App |
---|---|---|---|---|---|
365 | Replace Sensor Error | Sensor in Error State This error is logged once, immediately when Patch Failure is received via BLE from the Patch. If this corresponds to Patch event 11 (Algo error termination), then the corresponding extended error code is displayed, and Patch event 4011 will additionally be logged. If it corresponds to another error termination, then no extended error code will be displayed, and the corresponding Patch event 4xxx will additionally be logged. This may also be logged during activation when scanning a Sensor in error state | NFC BLE | Replace sensor screen Replace sensor system alarm | C |
366 | Sensor Fallout Error | The sensor has come off the patient – reinsert if possible This error is logged once, immediately when Insertion Detection Failure is received via BLE from the Patch. This corresponds to Patch Event 5, and will be logged along with 4005. | BLE | Sensor fallout screen | |
367 | Incompatible Sensor Type Error | The sensor scanned during Activation is not compatible with this Receiver – try the correct sensor type | NFC | Incompatible sensor screen | |
372 | Sensor Not Yours Error | Another sensor already in use by another Receiver has been scanned during Activation. | NFC | Sensor already in use screen | |
373 | Current Glucose Result DQ Error | The Current Glucose reading that was Viewed was determined by the algorithm to be invalid. Note: This is logged only when user Views a DQ reading, at most once per Sensor Life Count. | BLE | Results screen with Sensor Error | C |
380 | ESA is detected ESA marks the first 12 hours of data as having Invalid Data DQ errors. | Sensor reading is unusually low. Logged when the first Current glucose reading is received with ESA via BLE. Only logged once per Sensor. Note: If user is out of range of the Sensor during the 12 hours of ESA, this will not be logged. | BLE | Results screen with Sensor Error | |
4001 – 4xxx | Patch Reported Errors/Events | Patch Error Codes 1 – xxx This corresponds to error/event codes received from the Patch. The Patch error code (1-xxx) is prepended with a 4, logged in the database, and displayed to the user. Note: Not all Patch Errors will be displayed. Errors 1-4 and 6-7 are not stored or displayed in the event log. Patch Error 11 (4011) will be accompanied by 365, and Patch Error 5 (4005) will be accompanied by 366. See Patch Error spec for more information. |
Related issues
Issues with same labels
There is no content with the specified labels