We have learned that a recent change in the firmware on the LifeScan Ultra2 meter has made this meter model incompatible with our PWR-08-06 GMAs. 

To give a little more detail: traditionally, all the LifeScan meters (Ultra, Ultra2, Ultra Mini, Ultra Easy) have transmitted a series of characters when a new measurement was available; this transmission was used to wake up our GMA.  Unfortunately, the recent firmware change on the Ultra2 has eliminated this transmission, resulting in the GMA failing to wake up.

Unfortunately, there are already too many of the problematic Ultra2 meters in circulation for LifeScan to change them; all we can do is steer our customers away from the problematic meters.

Fortunately, identifying the problematic meters is quite simple, and can be done by examining the serial number of the meter. For identification, the serial number of an Ultra2 has nine alphanumeric characters.  The only significant digit in this string for our purposes is the second-to-last character, which is the version code. 

Both Ultra2 and UltraBasic (Ultra Mini, Ultra Easy) use a Nine (9) digit serial number, as shown below,

at digit Eight (8) can be found the revision code.

The serial number can be found on the reverse of the meter and on the outside of the retail box

Below is the table of the meters as they stand

The vast majority of Ultra2 meters already in circulation are versions “A” and “B”, but all new ones being produced are version “C”, regardless of the geographic location where they are sold.

We suggest that any customers wanting to use the current GMA and needing to purchase a new meter be directed towards the UltraMini (UltraEasy).  We have been assured by LifeScan that they will not make similar changes in this model.  

In future Polytel^® GMA models, a pushbutton will allow use of version “C” Ultra2 meters; we believe that patient compliance could be reduced by needing to push a button for each transmission, and expect that UltraMini will continue to be the preferred meter for telehealth applications.

Though we were in no way responsible for this problem, we regret the inconvenience to our customers, and will strive to support  you in your efforts to continue deploying your telehealth solutions.