Unable to parse reading from meter:

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Reading realtime data from Classic or new CC128 model

All version of the app with the "Live Data" up to the current release have 
produced this error some time after I have left it running.

The connection is direct on my Micorosft Windows Home Server.

Regards

Ian.

Original issue reported on code.google.com by ipmitch...@gmail.com on 19 Feb 2009 at 7:51

Attachments:

• [CC Error Again With New Model.jpg](https://storage.googleapis.com/google-code-attachments/currentcostgui/issue-4/comment-0/CC Error Again With New Model.jpg)
• [CC Error With New Model.jpg](https://storage.googleapis.com/google-code-attachments/currentcostgui/issue-4/comment-0/CC Error With New Model.jpg)

[GoogleCodeExporter]

Thanks very much for your comment. I'd not seen this error before (I use MQTT to
connect to my CurrentCost meter, rather than a serial connection - so rely on 
people
such as yourself to point out these things to me).

The issue is that reading data from the CurrentCost meter's serial port isn't 
100%
reliable. Sometimes you get a garbled string, or an incomplete chunk of XML. 

The code currently exits when it encounters an error
(http://code.google.com/p/currentcostgui/source/browse/trunk/currentcostcomlive.
py#67) which
in hindsight is a little extreme - it would be more sensible to wait for another
update from the meter. 

I'm on holiday at the moment but will fix this when I get back.

Original comment by dale.l...@gmail.com on 21 Feb 2009 at 11:07

• Changed state: Accepted

[GoogleCodeExporter]

Dale,
Thankyou for the update.
One other small point is the live page has for the vertical scale KwHrs when it 
is 
of course only Watts or Kw for a live power reading.

Enjoy your holiday :)

Ian.

Original comment by ipmitch...@gmail.com on 21 Feb 2009 at 12:49

[GoogleCodeExporter]

Fixed - fix will be included in the next release

Original comment by dale.l...@gmail.com on 22 Feb 2009 at 7:55

• Changed state: Fixed