Have just activated a new sensor this morning. The second in a fortnight as I'm trying to build up a month of roller coaster readings to show consultant at the end of year. It is recording my results but not producing a graph. Anyone else had this issue?
Give it a bit longer to settle. I have sometimes had some strange things show on the meter, like gaps in the graph, then "suddenly", it'll just sort itself out and literally, fill in the bnak spots.
If that's still happening on Monday, give Abbott a call. They're usually extremely helpful.
When you just start on a new sensor, then you will always have the time gap in your graph, from old sensor expiring to 1hour after you enabled your new sensor. Due to 'the ordinary rush of modern life', I have the rhythm to change my sensor every second Sunday morning, approx. 1 hour after breakfast.
This way I will typically be at home. Having a 'quiet' morning, with Sunday full breakfast routine and another sensor at the ready if I screw it up. (as I did once by scanning the old vs new twice, and the new were no longer recognized by the meter... ;o) And it enables me to measure the bg before breakfast, take my fast acting insulin for the meal, still measure then the bg again like 1 hour after the meal to control I did the right dosing. And then change the sensor right after. So I then will be ready to measure again before lunch/activities that day with the family and friends out in the wild.
For the full curves I guess you already by now download them to a computer from the meter?
You shouldn't have to. but have you tried connecting your reader to you laptop/pc, and looking at any graphs on the Abbott software?
Well i'm 48 hours in and still no graph! The sensor I had on previously worked just fine, and I have downloaded all the info. This one scans in the moment, but not continuously.
What is most frustrating, is that I had wanted a month of consecutive results for my next consultant meeting. Not going to get that now without forking out more money.
Abbot first thing in the morning it is. Grr!
I think that the graphs on the software package are just an enhanced version of what is displayed on the reader. It seems to me that it is the sensor that is at fault. Going into the event log in the settings option on the reader should show this and also an error code. Codes starting with ER3 are the usual ones. I have asked Abbott repeatedly for a list of error code meanings but sadly they don't seem to want to inform us all. We are after all only the poor dumb saps who are using their products
In my personal experience, connecting the reader to the software has cleared the odd issue. I'm not suggesting that replaces any requirement to inform Abbott of the experience to date with that sensor.
Regarding the error codes; I have a feeling that the Abbott telephone analysts probably don't have the lists on the desks themselves. My feeling is they go through a diagnostic decision tree on the support lines with us, being guided at each stage by their script/map. That's a standard approach, usually used to ensure a consistent approach, and consistent outcomes.
To be honest, I use that belief to help me prepare for any calls I need to make to them, to ensure I have the data they are likely to require to hand, including timed/dated examples of "unexpected" readings/conflicts/errors, so that I'm not frantically searching for examples whilst I'm on the line.
I have had several sensors replaced by Abbott, and have never had to request that happen or get into any arguments about it.
It isn't perfect, by a stretch, but it's an extremely valuable tool that I'm sure we each deploy slightly differently and have differing objectives and expectations of.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?