Newmodbus connect failures

[GoogleCodeExporter]

We are seeing eratic modbus connection issues, primarly at high system loads, 
although the exact cause is not yet determined. A work around for this is to 
reduce the cron interval to 2 or more minutes. This seems to reduce the 
pressure on the charge controller. The issue has been raised with midnite, but 
its a work in progress. If anyone can reproduce this bug reliably or can shed 
some light on it, kindly post something on the midnite forum, open source 
section.

A related issue is that the Wh and time in stage datapoints are currently 
premised upon once per minute connections, and result in inaccurate data when 
the controller is polled at intervals other then 60s. A fix for this is coming.

Original issue reported on code.google.com by [email protected] on 20 Sep 2013 at 11:29