guest
Home
3:33 am
March 17, 2010
Offline
You're right, the file does disappear -- I did try (accidentally) just that today, and no logs when I got home. Strange behaviour, but easy to avoid when one knows.
Denis Gionet, OGA Executive Member - Northern Ontario.
1:51 am
March 19, 2011
Offline
denisetdoris wrote:
So, if you find 5 caches, then do a Cancel Route, your 5 finds are also lost as well ? You would then have to do a Write Note or anything else to get the file back. Would those 5 found caches be in the new file ?
Hi Denis,
Yes, the 'Cancel Route' option causes the 'logs.txt' file to disapear. But it you then cause a write action (I did not test Notes specifically) the 'logs.txt' file is rewritten so your 5 found cache will be there when you log your finds on GC.com.
When the 'logs.txt' file is written it is basically a text version of the 'Magellan_Geocache_Extension.gpx' (MGE.gpx) file. Therefore it will contain all the records that are in the MGE.gpx file. When you log your finds to GC.com only records that have not been previously logged are uploaded to GC.com but the 'logs.txt' file will contain all records since the MGE.gpx file was created.
Graham.
1:21 am
May 5, 2011
Offline
I went out geocaching again this afternoon. Found two more, DNF one, logged them all. I was careful not to use the "Cancel Route" thing because of this thread, and when I got home was able to upload the file to gc.com and fill out the notes.
This should be an easy one for Magellan to fix now that Graham has figured it out for them.
---
San Francisco, CA
12:40 am
April 6, 2010
Offline
ShortcutHicksy wrote:
Hi David,
I have finally worked out what is causing the ‘logs.txt’ file to disappear.
Graham.
Like David said, awesome find Graham.
That explains what happened to me this morning.
I used the ‘Cancel Route’ option on my last find before going to a Geo Event and the compass stopped working, my settings went to default and the map & compass were spinning. After I re-calibrated the compass from the calibration page everything went back to normal but my logs.txt file was missing when I hooked up to the PC.
So after reading Graham's post a few minutes ago I logged another cache and my logs.txt file came back!
Again, Awesome find Graham. :cheer:
When in trouble or in doubt, run in circles, scream and shout
8:54 pm
March 20, 2010
Offline
Graham
Awesome find - I will get this to Eric immediately so they can address this issue. (Edited - I sure wish my fingers what type what my brain is thinking!!!) 😛
David
ShortcutHicksy wrote:
Hi David,
I have finally worked out what is causing the ‘logs.txt’ file to disappear.
If you select a cache and then select ‘Goto’ but then decide not to continue and use the ‘Cancel Route’ option to end the route the’logs.txt’ file will disappear. Basically whenever the ‘Cancel Route’ option is used the ‘logs.txt’ file will disappear.
The interesting thing is if you select another cache and select ‘Goto’ and subsequently mark the cache as found the ‘logs.txt’ file is rewritten.
So the bottom line is if the last action was to use the ‘Cancel Route’ option. When you connect to GC.com to log the finds the ‘logs.txt’ file will be missing. To get the file back mark any cache as found (DNF will most likely work also) and the ‘logs.txt’ file will be rewritten.
Please pass this onto Magellan.
Graham.
7:51 pm
March 17, 2010
Offline
So, if you find 5 caches, then do a Cancel Route, your 5 finds are also lost as well ? You would then have to do a Write Note or anything else to get the file back. Would those 5 found caches be in the new file ?
Denis Gionet, OGA Executive Member - Northern Ontario.
5:15 pm
March 19, 2011
Offline
Hi David,
I have finally worked out what is causing the ‘logs.txt’ file to disappear.
If you select a cache and then select ‘Goto’ but then decide not to continue and use the ‘Cancel Route’ option to end the route the’logs.txt’ file will disappear. Basically whenever the ‘Cancel Route’ option is used the ‘logs.txt’ file will disappear.
The interesting thing is if you select another cache and select ‘Goto’ and subsequently mark the cache as found the ‘logs.txt’ file is rewritten.
So the bottom line is if the last action was to use the ‘Cancel Route’ option. When you connect to GC.com to log the finds the ‘logs.txt’ file will be missing. To get the file back mark any cache as found (DNF will most likely work also) and the ‘logs.txt’ file will be rewritten.
Please pass this onto Magellan.
Graham.
5:12 pm
December 3, 2010
Offline
Same to me, after FW 4.83 there is no logs.txt file on my eX710 :dry:
3:40 pm
April 6, 2010
Offline
With the iPhone set the app for field notes instead of log, when you get to where a signal is available check your field notes on the app and resend the pending notes.
That's what I do anyway and until the firmware upgrade on the 710 is fixed I won't use the 'found' option on my 710.
When in trouble or in doubt, run in circles, scream and shout
3:08 pm
April 23, 2011
Offline
This is very frustrating to me.
I think I have tried everything I have read here.
Totally given up on VP as the portal for uploading.
Sometimes the log file is there, sometimes not.
When it's not, a write a note for a cache and magically it appears.
It takes too much time to mess with this though.
I have an iPhone and know I could log with the app, but the feature on the 710 to do this in the field is so much faster, especially in the middle of nowhere with bad cell reception.
Quicker, until you get back home and want to upload field notes.
12:21 pm
March 19, 2011
Offline
I deleted the Magellan_Geocache_Extension.gpx (MGE.gpx) file in my 710 (I was trying to avoid doing this).
I then bench tested all the different found branches on a cache I had previously found. In all cases the logs.txt and MGE.gpx file were created. I will now check it in the field with new caches.
If that all works I will reconstruct my MGE.gpx file and see if the fault reappears. If it does then possibly the MGE.gpx file is some how getting corrupted or maybe its size causes the fault. Or I may just give up and succumb to delete the MGE.gpx file all the time.
David,
As Matt pointed out above, when you use the hard button to bring up the cache details and then use the options button, lower RHS to mark the cache as found. The goto route is not cancelled and the ‘Find next closest Geocache?’ question doesn’t come up. These two routines do not run via this path, as they should after marking a cache as found. If you are in agreement please report to Magellan.
Graham.
7:32 am
March 19, 2011
Offline
warfieldm wrote:
I think I may have an inkling as to what's going on though. If you have the cache description shortcut set to one of your hard keys, there are two ways to access the Found function in the menu.
1) Hard key / Lower Right Menu / Found
2) Tap screen for 4 corners / Lower Right Menu / Found
These two do not do the same thing. It seems as though there are some routines missing for #1.
With #2, it marks the cache as found, cancels the route, and prompts for nearest cache.
With #1, it marks the cache as found only. Route is still active and does not prompt for nearest cache.
Matt, the thread title is a bit of a misnomer.
The faults is the 'logs.txt' file not being created after marking a cache as found since the firmware upgrade.
I thought I has tryed all those branches and got the same results no matter which way I went but will re-check.
Thank,
Matt.
4:27 am
April 12, 2011
Offline
Graham - Sorry, it's been too long and I can't remember. Haven't been using the notes file anyway.
I think I may have an inkling as to what's going on though. If you have the cache description shortcut set to one of your hard keys, there are two ways to access the Found function in the menu.
1) Hard key / Lower Right Menu / Found
2) Tap screen for 4 corners / Lower Right Menu / Found
These two do not do the same thing. It seems as though there are some routines missing for #1.
With #2, it marks the cache as found, cancels the route, and prompts for nearest cache.
With #1, it marks the cache as found only. Route is still active and does not prompt for nearest cache.
I haven't dug into this any further to see if this might be related to the field notes file isn't working properly.
10:35 am
March 19, 2011
Offline
warfieldm wrote:
Reloading did not resolve it. However, deleting the MGE file did resolve the old caches being repeated. Tagged a couple of caches as found and neither has a [time to find] stamp on it. Might just be because it was under a minute or some other criteria in the program routine. Still have the old MGE file if it needs to be sent on.
Hi Matt,
How is your unit going? Is it creating the logs.txt file since you deleted the MGE.gpx file. What size is the MGE.gpx file now and are you letting it grow or are you deleting it after uploading your finds to GC.com?
Graham.
10:28 am
March 19, 2011
Offline
denisetdoris wrote:
I discovered something last night after doing some testing. I couldn't get new geocaches I create to publish, because I had the Use SD Card option checked... this makes the unit get confused. I un-checked that box, and now the Publish New Geocaches works. However, my user notes were always found when there were new ones, and I've never deleted my MGE.gpx file, and it contains 229 records. So this may, or may not, be related. If you have that box checked, un-check it just for fun.
Hi Denis,
I'm not using the SD card. Thanks for the info on the number of records in your MGE.gpx file.
Graham.
7:57 pm
Hey, is there an echo in here? Hello Hello Hello Hello Hello 😛
6:44 pm
March 17, 2010
Offline
removing double post....
... p.s. Morel .... hahaahahha !
Denis Gionet, OGA Executive Member - Northern Ontario.
6:44 pm
March 17, 2010
Offline
I discovered something last night after doing some testing. I couldn't get new geocaches I create to publish, because I had the Use SD Card option checked... this makes the unit get confused. I un-checked that box, and now the Publish New Geocaches works. However, my user notes were always found when there were new ones, and I've never deleted my MGE.gpx file, and it contains 229 records. So this may, or may not, be related. If you have that box checked, un-check it just for fun.
Denis Gionet, OGA Executive Member - Northern Ontario.
4:56 pm
December 3, 2010
Offline
Just to set the numbers straight,
I do have the same problem.
2:08 pm
March 19, 2011
Offline
Hi David,
Just an update on the NO ‘logs.txt’ file creation after marking caches as found.
The problem is still happening and it makes no difference, which way I go through the branches (Add Comment and Find next Geocache). I have reinstalled the firmware to no avail. The software was obviously modified in this area to add the ‘Find next Geocache’ decision. As reported else ware in the forum this branch produces inconsistent results, sometime showing found caches, very few or no caches.
If Matt and I are the only ones reporting this fault another possible area that may be causing the fault is how the logs.txt file has been declared in the software. I do not delete the ‘Magellan_Geocache_Extension.gpx’ (MGE.gpx) file and is currently holds 168 found records. Therefore when the logs.txt file is to be written it has to have a size large enough to hold all the 168 found records. Depending on how is had been declared in the software it may not be large enough. I understand that most user clear the MGE.gpx file when they load new cache and therefore may not see the fault.
Matt may indicate whether he is still seeing the faults and if he has deleted the MGE.gpx file.
I’m keen to find a fix as the manual logging on my found caches on GC.com is wearing a bit thin.
I will delete the MGE.gpx file and see what happens.
Graham.
1 Guest(s)
