I added a summation meter, but it reads in up to 10 Febuary and then it is stuck. I cannot see any of the meters not calling in on my problem meter list.

Summation Meters are handy for various reasons, two of which are:

1. Simplify. If you want to have more than one level of portions, for example if you want to divide the incomer energy minus all the metered shops between the unmetered shops based on square meterage, it is easier to make one summation meter that already takes all the other meters on the site into account, and then divide that meter between the shops in question.
   
2. Performance. Sometimes a meter account will have so many meters in it (typically if you go more than 11-20 meters on a meter account, for example if you want to look at the sum of all 300 stores in a chain store); that a normal profile graph screen on that account will not perform well. You can therefore create one Summation Meter on that meter account, which will work out the sum of the meters when the meter is 'called in', and then the sum is saved in the database against one meter (the summation meter). When you then add a Meter Account on this one Summation Meter, the profile graph will then perform very well again, because the system is not summating so many meters at run time. It is only looking at one.
   

To come back to your question:
Basically, when a summation meter 'calls in', it cannot go beyond the maxdate of the oldest component meter. Although, if a meter is uninstalled, it will go beyond that meter's maxdate, because that meter can never call in further again in the future.
I've looked through your list of component meters, and it seems there is one that is disabled, BUT NOT UNINSTALLED.
So, basically, what that means is that it is temporarily not shown on your problem meter list, but as soon as it is enabled again, it will read in again.
To make your summation meter carry on reading in beyond this point, uninstall that disabled meter to make it permanently disabled.

It is still stuck. I get an Output Error in the Communications Monitor.

Ok. When I looked in your Meter Read Log and I hover 'Output Problem' in the outcome column, I saw from the Tooltip that pops up that the value it tried to insert into the meter was too big.
You will also see the message if you do the Communications Monitor in debug mode:
java.lang.Exception: Completely unreasonable profile value: 98765XXX,2012-02-01 00:30:00.000,3281
Basically, the system checks your profile value for every half hour against the breaker size that is configured for the meter in Meter Details. In your case, this is still set to 60A. It should be the sum total of all the breaker sizes of all the meters in the summation meter account.

Tags: kl/hkw/hwater meter