A little bugreport, if ecoach is still developed on: If running with heartrate monitor (i use the patched version from mvonweiss) sometimes it seems that heartrate monitor disconnects, or at least wont get saved (happened twice only, from 20 times, so no big deal). The problem is, that ecoach then only calculates the time where heartrate data is available, but should take the time where gps data is available, as the distance is taken from the gps. As example, if running 1 hour, 10 km, but heartrate monitor disconnects after 30 minutes, eCoach says you ran 30 minutes average speed 20km/h. It would be best if ecoach adds a dummy heartrate value, as heiaheia has the same problem, and this way it could be prevented. Now, if i see this, i manually add a dummy value for the heartrate with the latest time from gps.