Before using the eDroplet application, it is imperative that you read this user manual. If something is unclear – then please ask on the group FB Droplet. Almost 100% of the problems are due to the fact that the user does not understand the principle of operation of the application and the principle of operation of libre sensors themselves.
We start by installing the eDropletNFC application.
Here you will always find an up-to-date link to download the latest version from the Google Play Store: -> the latest version.
Here you will always find an up-to-date link to download the latest version from the Apple Store: -> the latest version.
After downloading, installing and running we have the first and only screen:
As you can see the application on both types of operating systems looks the same.
At the top we have 3 buttons: Read, Re-Init and Activate.
Below them – status information field ("???| when no operation was performed.
Below – a large text box (light gray) where detailed information about what was done will appear.
At the bottom – space for the action indicator and two buttons: "Mail" and "Help".
Each of the main functions works identically: we click on the function button, apply the phone to the sensor, so that using NFC transmission to read data from it (and something written there if necessary) and then check the result on the phone screen – the status line and below it information report.
When you click on the button – at the bottom of the screen, the scan readiness indicator appears:
After scanning – reading the sensor, the application displays information about the performed action:
"NFC scan OK – test" – a correctly executed scan for the test function. If the scan was incorrect, it would be "NFC scan fail – test".
"Sensor: Libre 1 new" – a new type of sensor Libre 1. Currently, there are two types of sensor "Libre 1", both of which are supported in the nfc eDroplet application. Type "Libre 1" – that is, "old" – this, since the beginning of the market appearance and "Libre 1 new", a new type with pre-factory calibration appeared from last year.
"S/N" – sensor factory number
"ID" – identifier of sensor type and subtypes. The "old" type starts with "DF" and the new type begins with "A2".
"Status:" current sensor status. About him below.
"Age" – the time elapsed since the sensor was activated in minutes, hours and days.
"–end" – mark the end of the data presented after scanning.
Sensor statuses: These statuses indicate the different phases of the sensor's life. It starts with "01" – a pre-made or re-initiated sensor. "02" – sensor just activated. This phase lasts about 15 minutes to 60 minutes. "03" – active sensor that is acting and measuring glycemia. Lasts 14 days from the moment of activation of the sensor. "04" – The end phase lasts 12 hours after a 14-day period of sensor activity. "05" – sensor terminated (expired). Normal end of sensor operation after a period of 14 days. "06" – failure, sensor damaged, malfunction – this condition can occur at any time and is associated with the harm or malfunction of the sensor electronics.
The 60-minute "warm-up" period of the sensor when activated with the Librelink app or factory reader includes phase "02" and the first minutes of phase "03".
Order of actions:
- We are always the first to perform the "1 function. Read" – it allows you to check the status of the sensor, provide detailed information about it and determine what further actions can be carried out – this is in the last line of information.
- When we want to re-initiate the sensor, that is, restore it to the "factory novelty" state – we perform the function "2. Re-Init". This function recognizes the state of the sensor (even when it is in an emergency state – error "06") and makes changes to it to the state that the new sensor is removed from the package.
- If we want to activate the sensor – we perform the operation "3. Activation". Note here: activating the sensor in the application will make it impossible to read it with a factory reader, but only applications such as LibreLink, xDrip, DiaBox, Glimp, etc.
- "Mail" – if there is a problem – then before asking a question on the Facebook Droplet group – please click on the "Mail" icon (at the bottom of the screen) and send me a report of the application's work – it will help in finding a solution.
- "Help" – icon "?" – redirect from the application to this page 🙂
The problems are:
- Unable to install application -> the only reason is hardware. Either the hardware itself, that is, the smartphone is too old, does not have the required functions – then you need to replace it with a newer one, or the version of the operating system is too old – you need to update it to the latest, and if it does not help, then replace the phone with a newer version.
- The application works, but does not scan sensors -> practically possible only on Samsung phones where the battery was replaced. In the original batteries, the NFC antenna is in battery, so if you replaced it with the original one, nfc won't work. Replace the battery with the original one. To date, there has been no information about this type of problem with other phones.
Other problems do not exist. in the sense that there is no way to solve them:
- If the sensor is not read by some applications (or factory reader) after re-initialization or activation -> it will not be read until the developers of these applications change something in them. Any changes to the eDropletNFC application will not resolve this issue. I plan to write this application in the "Pro" version, which will be able to read such sensors (or at least a significant part of them) and which will have the full functionality of displaying glycemia – but it will take several weeks.
- If the sensor cannot be re-initialized and/or activated (for example, there is a recurring "Status: 06" error, or if the sensor automatically resets after some time to the status "Status:01" -> there is also no solution to this problem at this time. It is also unclear whether this will ever be solved. Simply, such a sensor will not continue to work.
And that's all 🙂
- Re-initialization of the sensor allows its use after the standard 14-day working time. However, it should be remembered that such a sensor may work worse, it may give indications deviating from the indications of the meter with values greater than in the main time.
- Re-initialization sets the sensor as it is set when it leaves the factory – that is, it is ready for 14 days. However, these next 14 days cannot always be achieved. As in the basic 14 days, the sensor refuses to continue working.
- This application, like all applications for DIY solutions, is published in the "is-like-is" mode, that is, the author assumes no responsibility for its operation, especially for what and how it will happen to the sensor modified by this application. The use of applications and sensors modified by this application is the sole responsibility of users.