etrexdadnkids Posted January 24, 2015 Share Posted January 24, 2015 (edited) Kind of noob, done a few caches,, got a clone data cable now working ok. Some issues with chrome on plug in , ok on old internet explorer. When I transfer a few cach locations to device I see them appear on the waypoint list and get Transfer Complete on unit display no drama. So daughter and I thought we will load 3 caches, all done by same guy and they have ID nos that only differ by last digit of ID. All along a short walk, probably created at same time. First one goes in and I see it. Second one goes in and I don't see it. (just looks like the first only ) Third one in and no change to display ( still one entry, looks like first one still ) Open the only one there and its the last uploaded one ( the third one ) As the Display ony supports 6 leters/Nos the last digit must not be checked during upload and the SW overwrites a file that has the first 6 letters ( of 7 ) the same. The locations were.. GC5JVAH GC5JVAE GC5JVAB Display only says GC5JVA After upload of all three!!!!!! Any way round this code design oversight.... Edited January 24, 2015 by etrexdadnkids Quote Link to comment
+Gitchee-Gummee Posted January 24, 2015 Share Posted January 24, 2015 The problem is that the cache name (waypoint name) field is only 6 characters long, cache ID tags are 7 characters long -- with the GC prefix. If those caches are present in the unit, you need to alter the (name) field to reflect the proper cache. Drop the GC prefix, it is completely unnecessary -- all geocaches have that. Quote Link to comment
+NanCycle Posted January 24, 2015 Share Posted January 24, 2015 (edited) Kind of noob, done a few caches,, got a clone data cable now working ok. Some issues with chrome on plug in , ok on old internet explorer. When I transfer a few cach locations to device I see them appear on the waypoint list and get Transfer Complete on unit display no drama. So daughter and I thought we will load 3 caches, all done by same guy and they have ID nos that only differ by last digit of ID. All along a short walk, probably created at same time. First one goes in and I see it. Second one goes in and I don't see it. (just looks like the first only ) Third one in and no change to display ( still one entry, looks like first one still ) Open the only one there and its the last uploaded one ( the third one ) As the Display ony supports 6 leters/Nos the last digit must not be checked during upload and the SW overwrites a file that has the first 6 letters ( of 7 ) the same. The locations were.. GC5JVAH GC5JVAE GC5JVAB Display only says GC5JVA After upload of all three!!!!!! Any way round this code design oversight.... This unit (I have one) worked fine when only 6 characters were used in the GC codes. When they were running out of possible combinations and went to 7 characters, this is what happened. Before I got a more up to date unit, I wold edit the codes to remove the first G and then the rest of the code would fit. You can either live with this condition--if you're only doing a few caches occasionally-or upgrade to a more modern unit. Edit: typo Edited January 24, 2015 by NanCycle Quote Link to comment
etrexdadnkids Posted January 24, 2015 Author Share Posted January 24, 2015 [quote If those caches are present in the unit, you need to alter the (name) field to reflect the proper cache. I cant get the three in, they overwrite the previous one so only one there no matter how many times you try to load all three Quote Link to comment
etrexdadnkids Posted January 24, 2015 Author Share Posted January 24, 2015 Kind of noob, done a few caches,, got a clone data cable now working ok. Some issues with chrome on plug in , ok on old internet explorer. When I transfer a few cach locations to device I see them appear on the waypoint list and get Transfer Complete on unit display no drama. So daughter and I thought we will load 3 caches, all done by same guy and they have ID nos that only differ by last digit of ID. All along a short walk, probably created at same time. First one goes in and I see it. Second one goes in and I don't see it. (just looks like the first only ) Third one in and no change to display ( still one entry, looks like first one still ) Open the only one there and its the last uploaded one ( the third one ) As the Display ony supports 6 leters/Nos the last digit must not be checked during upload and the SW overwrites a file that has the first 6 letters ( of 7 ) the same. The locations were.. GC5JVAH GC5JVAE GC5JVAB Display only says GC5JVA After upload of all three!!!!!! Any way round this code design oversight.... This unit (I have one) worked fine when only 6 characters were used in the GC codes. When they were running out of possible combinations and went to 7 characters, this is what happened. Before I got a more up to date unit, I wold edit the codes to remove the first G and then the rest of the code would fit. You can either live with this condition--if you're only doing a few caches occasionally-or upgrade to a more modern unit. Edit: typo Is there easy way to do the edit? Quote Link to comment
+NanCycle Posted January 24, 2015 Share Posted January 24, 2015 Is there easy way to do the edit? Not so far as I know. And you will have to edit each one as you load it, then load & edit the next, etc., to avoid the overwriting you are experiencing. The inconvenience is part of what drove me to buy my etrex Legend HCx and my premium membership. Quote Link to comment
+MartyBartfast Posted January 25, 2015 Share Posted January 25, 2015 If you use GSAK it can change the codes for you automatically. Quote Link to comment
+ecanderson Posted January 25, 2015 Share Posted January 25, 2015 Specifically, you can use GSAK to just drop the unnecessary 'GC' off the front end of all of them before loading them to the unit. Since that leaves only 5 characters, you're good to go. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.