QuickGPSfix unavailable with map 860.3101...

mrlongest wrote:Tendriver
Tried that - no change - still no mention in TTHOME of any Quickgpsfix update being available. The ephem folders remain empty.

Don't know if there's any clue in something else I discovered. The ttgo.bif file has been altered (by TTHOME 'Operating...' ?) to list:
DeviceName=TomTom GO 520
DeviceVersionHW=GO 520
Whereas previously it showed
DeviceName=TomTom ONE XL
DeviceVersionHW=ONE XL
as in my old card.

Also the TomTom ONE XL on-screen “Current Configuration” info says:
Current Emulation: x40
BT: 1
TTS: on
Run in Save RAM Mode
Remove additional Files
Cleaning disabled
Delete old TMC Data
(Where does that info come from?)

I'm now really 'out-of-my-depth' now. I thought x40 means a GO x40 emulation. But TTHOME says it's a GO 520 unit = x20!
I'll stop 'muddying the waters' anymore and await your further advice...

On your card there is either a Config folder with several .txt files in it, or there are free standing .txt files in the root. 1 file is setconfig.txt. This file is giving you the odd reading. You can open it with notepad. Having the wrong device version listed could certainly cause the wrong files to be downloaded.

In this thread XXXXXXXXXX from the forum dated 2006, soon after the introduction of QuickGPSfix, it is suggested that QuickGPSfix only works on the newer GPS chip and not on the older SirfStar chip. If this is the case, then my search is ended, I won't be able to use QuickGPSfix on my GO 500. This may also solve your problem, mrlongest, as the card showing the device as a GO 520 shouldn't work either. If you look into the ttgo.bif and ttgo.bak files of each card you may see the following:

For the GO 520

ApplicationVersionVersionNumber=8302
ApplicationVersion=9738

For the One XL

ApplicationVersionVersionNumber=8010
ApplicationVersion=9369

If I'm correct, the easiest way to correct the GO 520 card would be to place a 'model.txt' file in the root with

A:8010
B:9369

in that file. It should modify your 'ttgo.*' files and the 'model.txt' file will disappear. I'm sure tendriver will correct me if I'm wrong.

Sorry, but links to other forums is not allowed.

pierrepeter wrote:In this thread XXXXXXXXXX from the forum dated 2006, soon after the introduction of QuickGPSfix, it is suggested that QuickGPSfix only works on the newer GPS chip and not on the older SirfStar chip. 1. If this is the case, then my search is ended, I won't be able to use QuickGPSfix on my GO 500. 2.This may also solve your problem, mrlongest, as the card showing the device as a GO 520 shouldn't work either. If you look into the ttgo.bif and ttgo.bak files of each card you may see the following:

For the GO 520

ApplicationVersionVersionNumber=8302 Incorrect values
ApplicationVersion=9738

For the One XL

ApplicationVersionVersionNumber=8010 Correct values
ApplicationVersion=9369

3. If I'm correct, the easiest way to correct the GO 520 card would be to place a 'model.txt' file in the root with

A:8010
B:9369

in that file. It should modify your 'ttgo.*' files and the 'model.txt' file will disappear. I'm sure tendriver will correct me if I'm wrong.

1. After more research, You may be right about your 500.
2. x20 units get QuickGPSfix updates.
3. The "GO 520" is coming from either a setconfig.txt file or a changed.txt file. A:B: values go in a version.txt file, not a model.txt.

Tendriver
Thanks. By using Windows search, found ‘config.txt’ file in the ‘text’ folder. Don't know how I missed that before! That clears that up satisfactorily.

Now back to my 'no QuickGPSfix problem'.
Have you found any reason for this yet?
It's of interest to note that I seem to have 'destroyed' the ability of my old card to get TTHOME QuickGPSfix updates anymore! The only fresh thing I did that I can think of was to use TTHOME to 'Operate my...' it showed as a GO 520 in the simulation, although remaining a ONE XL in the opening main menus (all as with new card). Also it's also impossible to use the ‘delete ephem folders' contents and update’ trick to get new ephem files anymore (which I've done in the past many times). Ugh!!
It seems TTHOME has altered some files in both my cards.
Can you throw any more light on this matter?

May I respectfully draw your and a pierrepeter’s attention to the thread I've just found “QuickGPSFix without TOMTOM HOME” in another forum (do a google search). Consequently I understand QuickGPSfix a little more.
Furthermore I downloaded the file from the first post by TTav134, followed the instructions and now I can manually obtain updates from the TomTom site using the relevant .cmd file for my GPS chipset. This workaround works for me, but I’d still like to understand why TTHOME can’t do it for me. That thread seems to suggest that the ‘device code’ is something TTHOME must look for.
But I’m not clear what my ‘device code’ is…(?)
Is there something else that TTHOME sees or doesn’t see that causing my (and pierrepeter’s) problems?

Tendriver
Thanks. By using Windows search, found ‘config.txt’ file in the ‘text’ folder. Don't know how I missed that before! That clears that up satisfactorily.

Now back to my 'no QuickGPSfix problem'.
Have you found any reason for this yet?
It's of interest to note that I seem to have 'destroyed' the ability of my old card to get TTHOME QuickGPSfix updates anymore! The only fresh thing I did that I can think of was to use TTHOME to 'Operate my...'. It showed as a GO 520 in the simulation, although remaining a ONE XL in the opening main menus (all as with new card). Also it's also impossible to use the ‘delete ephem folders' contents and update’ trick to get new ephem files anymore (which I've done in the past many times). Ugh!!
It seems TTHOME has altered some files in both my cards.
Can you throw any more light on this matter?

May I respectfully draw your and pierrepeter’s attention to the thread “QuickGPSFix without TOMTOM HOME” in another forum (do a google search). Consequently I understand QuickGPSfix a little more.
Furthermore I downloaded the file from the first post by TTav134, followed the instructions and now I can manually obtain updates from the TomTom site using the relevant .cmd file for my GPS chipset. This workaround works for me, but I’d still like to understand why TTHOME can’t do it for me. That thread seems to suggest that the ‘device code’ is something TTHOME must look for.
But I’m not clear what my ‘device code’ is…(?)
Is there something else that TTHOME sees or doesn’t see that causing my (and pierrepeter’s) problems?

Apologies to NaviTotal for linking to another site; so many sites with different rules, I should have checked! On reading the article more closely it seems that those with the Sirf Star 2 chipset (GO Classic/300/500/700) cannot get QuickGPSfix but later models from 2006 which came with the Sirf Star3 chipset can. So my search has ended.

I got my A B numbers for the GO 520 from a well known readmenot.txt, but I may well have not have interpreted it right; I never did code breaking at school, and that text needs some very special talents (that I haven't got!) to understand it!

Of course, tendriver, you are perfectly correct regarding my model.txt and version.txt mistake.

I should like to thank you, tendriver, and all mods in all forums, for the time you spend and the patience you have dealing with queries. Thanks again.

mrlongest wrote:Tendriver
Thanks. By using Windows search, found ‘config.txt’ file in the ‘text’ folder. Don't know how I missed that before! That clears that up satisfactorily.

Now back to my 'no QuickGPSfix problem'.
Have you found any reason for this yet?
1. It's of interest to note that I seem to have 'destroyed' the ability of my old card to get TTHOME QuickGPSfix updates anymore! The only fresh thing I did that I can think of was to use TTHOME to 'Operate my...' it showed as a GO 520 in the simulation, although remaining a ONE XL in the opening main menus (all as with new card). Also it's also impossible to use the ‘delete ephem folders' contents and update’ trick to get new ephem files anymore (which I've done in the past many times). Ugh!!
It seems TTHOME has altered some files in both my cards.
Can you throw any more light on this matter?

2. May I respectfully draw your and a pierrepeter’s attention to the thread I've just found “QuickGPSFix without TOMTOM HOME” in another forum (do a google search). Consequently I understand QuickGPSfix a little more.
Furthermore I downloaded the file from the first post by TTav134, followed the instructions and now I can manually obtain updates from the TomTom site using the relevant .cmd file for my GPS chipset. This workaround works for me, but I’d still like to understand why TTHOME can’t do it for me. That thread seems to suggest that the ‘device code’ is something TTHOME must look for.
But I’m not clear what my ‘device code’ is…(?)
Is there something else that TTHOME sees or doesn’t see that causing my (and pierrepeter’s) problems?

1. TT Home will not, can not alter a device without the user's input.
2. I'm well aware of the thread you referenced. It makes our job very difficult when members look for help both here & elsewhere at the same time. Usually the member compounds the problem by taking this approach. If these cards were mine, I would delete everything, but the map, & reinstall the navcore using a basicpak & prepatched ttsystem /PNDNavigator download.

pierrepeter wrote:1. Apologies to NaviTotal for linking to another site; so many sites with different rules, I should have checked! On reading the article more closely it seems that those with the Sirf Star 2 chipset (GO Classic/300/500/700) cannot get QuickGPSfix but later models from 2006 which came with the Sirf Star3 chipset can. So my search has ended.

2. I got my A B numbers for the GO 520 from a well known readmenot.txt, but I may well have not have interpreted it right; I never did code breaking at school, and that text needs some very special talents (that I haven't got!) to understand it!

Of course, tendriver, you are perfectly correct regarding my model.txt and version.txt mistake.

I should like to thank you, tendriver, and all mods in all forums, for the time you spend and the patience you have dealing with queries. Thanks again.

1. No apology necessary. I'm afraid that I have to agree with your conclusion.

2. That readmenot.txt must be a relic. LOL!!

You are Welcome. Thank you for the kind comment.

tendriver
1. You clearly believe that TTHOME cannot have altered my card without my input. I am not aware that I have done anything that could have led to my problem, or for that matter could have changed my ttgo.bif file to show a GO 520 rather than the actual ONE XL. The ‘Operate my device’ function in TTHOME appears to have been my only significant input action. What else could I have inputted/done (wrong)?
Or is the TomTom company getting cleverer in identifying and reacting to the use of ‘unofficial/illegal’ navcores and maps?
2. My sincere apologies if I’ve given you offence by seeking to learn from more than one source at the same time. And honestly I haven’t compounded the problem. I simply proved to myself that the workaround does work (on a totally separate card as it happens). I’m an experienced practical professional engineer with an enquiring mind. I just wish to learn what could have gone wrong with these two cards to avoid a similar annoyance occurring in the future. I do truly appreciate that you are trying to help me with my problem. Any further ideas to offer?

I have other cards that run successfully with older maps. Of course I could reload the two problem cards, as you suggest, but then I would have failed to understand what went wrong, and it possibly could happen again.
I do sincerely appreciate your and the other moderators’ help in this forum – it’s definitely the best TomTom forum I’ve come across!

mrlongest wrote:tendriver
1. You clearly believe that TTHOME cannot have altered my card without my input. I am not aware that I have done anything that could have led to my problem, or for that matter could have changed my ttgo.bif file to show a GO 520 rather than the actual ONE XL. The ‘Operate my device’ function in TTHOME appears to have been my only significant input action. What else could I have inputted/done (wrong)?
1a. Or is the TomTom company getting cleverer in identifying and reacting to the use of ‘unofficial/illegal’ navcores and maps?
2. My sincere apologies if I’ve given you offence by seeking to learn from more than one source at the same time. And honestly I haven’t compounded the problem. I simply proved to myself that the workaround does work (on a totally separate card as it happens). I’m an experienced practical professional engineer with an enquiring mind. I just wish to learn what could have gone wrong with these two cards to avoid a similar annoyance occurring in the future. I do truly appreciate that you are trying to help me with my problem. Any further ideas to offer?

I have other cards that run successfully with older maps. Of course I could reload the two problem cards, as you suggest, but then I would have failed to understand what went wrong, and it possibly could happen again.
I do sincerely appreciate your and the other moderators’ help in this forum – it’s definitely the best TomTom forum I’ve come across!

1. I know so. You can make the ttgo.bif file read anything you wish by creating a ttgo.bak file. Notice the Device name, Device version & app in my 720 .bif. My app is 9.205.

DeviceName=TomTom GO 2010
DeviceVersionHW=GO 850
DeviceSerialNumber=
DeviceUniqueID=
RamDiskVersion=20100702
BootLoaderVersion=55274
LinuxVersion=547200
ApplicationVersionVersionNumber=8351

1a. No.

2. You haven't offended me. It just makes our job more difficult.

Sorry to come into this so late but I've just read it.

I only ever had the no Quickfix available through TTHome once. The fix was to get rid of the files ON THE PC under

C:\Documents and Settings\"USERNAME"\My Documents\TomTom\HOME\Download\complete\ephemeris

Leave the folder structure as is, but get rif of the Quickfix folders in ephemeris.

Went to TTHome and worked first time.

I had a lot of them which one would have after a while doing updates every week or few days. This might have been my problem, but I didn't bother to limit the num ber. I just deleted the lot and quickfix1 was generated to start again by TTHome.

Good luck and again, sorry it's late.

xose wrote:Sorry to come into this so late but I've just read it.

I only ever had the no Quickfix available through TTHome once. The fix was to get rid of the files ON THE PC under

C:\Documents and Settings\"USERNAME"\My Documents\TomTom\HOME\Download\complete\ephemeris

Leave the folder structure as is, but get rif of the Quickfix folders in ephemeris.

Went to TTHome and worked first time.

I had a lot of them which one would have after a while doing updates every week or few days. This might have been my problem, but I didn't bother to limit the num ber. I just deleted the lot and quickfix1 was generated to start again by TTHome.

Good luck and again, sorry it's late.

Thanx. This was suggested in posts 12 & 15, but did not solve the problem.