Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - javajoedigital

Pages: [1]
1
Beta Testing / v2.51 - Forerunner 301 support
« on: April 23, 2005, 08:33:18 PM »
Just got an error message:  "Trouble decoding NASA png file - something about offset? - then it advised that I check that I have a current corona.dll file.  Currently unable to view satelite images.  Had been able to earlier in the evening.  This hit out of the blue -- bam!

Restarted Topofusion - still didn't seem to work - could not switch to satelite images.  Then -- bam!  Now I can again.  Seems to be working fine.

2
Beta Testing / v2.51 - Forerunner 301 support
« on: April 13, 2005, 09:44:36 PM »
MultiSport on Forerunner 301

Previous downloads from the Active Log did well. (reported previously).

Today used the MultiSport feature on the Forerunner.  Ran a few miles, used the MultiSport option and walked a mile as another sport.  Left it in the Active log (did not reset) and then downloaded to Topofusion - only the walking portion appeared in the log book dialog box.

Confirmed that both portions would download to Garmin's Training Center and to Sportsim without problem.

Went back and reset the forerunner to save the track and then downloaded to
Topofusion - this time the running portion and walking portion were both available to save as separate files.  Both running and walking files worked fine and was able to do climbing analysis without trouble.

3
Archived - Feedback and Comments / Forerunner 301
« on: April 11, 2005, 07:52:01 PM »
Updated to version 2.51 today.  Downloaded 2 tracks from the Forerunner 301 and they loaded well.  Edited one track and ended up crashing the program.  Restarted it and all was well. More to follow.

4
Archived - Feedback and Comments / Forerunner 301
« on: March 29, 2005, 12:29:42 AM »
I use Topofusion with Forerunner 201 and it worked very well. Linking with the Forerunner 301 requires editing out the abberant data points which fortunately are obvious in the track points list.  I presume these represent HR data.  The resulting track appears to be accurate.

Have had variable luck uploading waypoints to the device - problem seems to occur when I have other programs open which have also connected to the device.

Looking forward to full support of the 301.  Would be happy to beta test if that would help.

Pages: [1]