Activity Stream
192,331 MEMBERS
1195 ONLINE
GPSurl On YouTube Subscribe to our Newsletter GPSurl On Twitter GPSurl On Facebook GPSurl On Google+

Page 1 of 4 123 ... LastLast
Results 1 to 10 of 32
  1.     
    #1

    GPS Truck Consequences of WNRO for GO x20, x30, 7000, x40, x50 and 9000 using a Navcore Truck 9.702 and known solutions

    TomTom has released for all these models an update of the last navcore in force before April 6, 2019. The version has increased from 9.510 to 9.541, to correct the bug of WNRO. On the other hand, no update of the navcore Truck 9.702 has been proposed by TomTom, so that the problems of the GPS using this navcore have not been solved.

    [Login or Register to remove this advertisement]


    But fortunately, the saying "there are no problems, only solutions" is confirmed once more. Let's see what solutions have been found:

    A) The clock problem.



    The GO x20, x30 and 7000 are equipped with the SiRFStarIII chip and have no clock problem.

    The GO x40, x50 and 9000 are equipped with the GlobalLocate 2 chip and since April 6, 2019 their clock remains locked at 0:00. The solution is very simple: just replace the file "glgps" located in the folder "bin" by the one of the navcore 9.541.You can download it below:

    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.



    B) The satellite problem.



    The GO x40, x50 and 9000 normally have no satellite problem thanks to the "cbee.cbee" file located in the "ephem" folder. This file automatically updates the position of the satellites.

    N. B. If you delete the "ephem" folder, most GO x40/x50/9000 will still find the satellites!

    Many (but not all!) GO x20, x30 and 7000 have trouble finding satellites since April 6, 2019.

    Here are the solutions known to date:

    1) Preventive measures that may improve the situation:

    a) Replace the file "glgps" located in the folder "bin" by that of the navcore 9.541 (see above).

    b) Upgrade the original bootloader to the latest version (5.5285). To upgrade to bootloader version 5.5285, simply copy the "system" file contained in the "bootloader_5.5285.zip" archive to the navcore root. At the 1st restart, the bootloader will be upgraded.

    Attention, this upgrade is normally irreversible !!!

    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.


    N. B. Although I can not say that these two measures really improve the speed of discovery of satellites, they do not seem to slow down anyway. They can not harm.

    2) Proven method: follow TomTom recommendations and update the satellite position at least once a week.

    There are several ways to do this update:

    a) Update QuickGPSfix via TomTom Home.

    b) Update QuickGPSfix directly from TomTom's servers via the executable file "QuickGPSfix_SiRFStarIII.exe" ("QuickGPSfix_GlobalLocate2.exe" for the GO x40, x50 and 9000). Just download the archive "ephem_x20_X30.zip" ("ephem_x40_X50.zip" for the GO x40, x50 and 9000), unpack it, place the files "QuickGPSfix_SiRFStarIII.exe" ("QuickGPSfix_GlobalLocate2.exe" for GO x40, x50 and 9000) and "Conversion de la date" in the "ephem" folder, then double click on the executable.

    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.

    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.


    c) Update QuickGPSfix directly from TomTom's servers via an Android application that allows to use the internet connection (wifi or 3G/4G) of an Android smartphone (there is, to my knowledge, no equivalent application for iPhone) .

    If this solution interests you, you can download the tutorial below. It's written in French, but you will have no trouble understanding it by using Google Translate.

    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.


    N. B. This method was developed and tested with the navcore 9.702 SE that I have been using for years. If it does not work with yours, download mine (I did not put the "LoquendoTTS" and "voices" folders, because they only contain French voices):

    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.


    N. B. This navcore is set for the GO x20, x30 and 7000. To use it with a GO x40, x50 or 9000, you must replace the 4 files "\Config\model.txt", "\ephem\QuickGPSfix_SiRFStarIII.exe", "\extras\TTquickgpsfix\TTquickgpsfix-wrapper" and "\Height\height.cfg" by their equivalents for GO x40, x50 and 9000. You can find them in the folder "Modifications_pour_x40_x50".

    d) Perform a "coldboot" with a toothpick or a paper clip when there is again a problem with the satellites and it is not possible to update QuickGPSfix by the previous methods. To do this, you must unplug the GPS from the power supply before turning it off, then press in the "reset" hole. At the next restart, the time will be reset to 0:00, 2:00 or any other time (in fact, this is the time at which the GPS clock was last set) depending on the GPS model. If it's at 0:00, the real time will be automatically displayed again after a few minutes, as soon as the GPS has found the satellites. If it's 2:00 or the last clock setting time, it will have to be set manually. I didn't find a rational explanation for this phenomenon. I could only note it :-(.

    N. B. This method is only valid for GO x20, x30 and 7000.

    e) Systematically perform a coldboot every time the GPS starts. For that you have to use a small file called "suicide.dat". This file, which must be placed at the root of the navcore, contains a value representing a number of seconds. For "suicide.dat" to be effective, you must unplug the GPS from the power supply before turning it off, then wait at least the number of seconds indicated in the file before restarting the GPS. For more, see above in section d).

    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.


    N. B. By default, "suicide.dat" contains the value 10 (= 10 seconds delay before restarting the GPS), but everyone can adapt it to their preferences.

    f) For those who do not want to carry a toothpick or a paper clip (), but would like to use "suicide.dat" only when needed, so as not to have to wait several minutes every time they start their GPS, our friend speedy29 of the Italian forum GbcNet has created an option to enable or disable suicide.dat.

    You can download it below. Just unpack the "PowerOn_Off_Menu.zip" archive and copy the two "suicide" and "sdkregistry" folders to the root of the navcore. If the "sdkregistry" folder already exists, copy there the contents of the "sdkregistry" folder of the archive.

    The original version being in Italian, I translated it. "cambia in SPEGNIMENTO" and "cambia in STAND-BY" became "Enable SUICIDE" and "Disable SUICIDE". I set the number of seconds contained in the file "suicide.dat" to 10, but each can adapt it to his preferences. By default, I disabled "suicide.dat".

    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.


    3) The ultimate solution: update the firmware.

    All the solutions listed above to remedy the satellite problem are only palliatives, and they are more or less painful, because they force to regularly update the file containing the position of satellites (QuickGPSfix). They cure the disease but do not eradicate it. Now there is a solution that completely eliminates the problem. It's kind of a vaccine :-).

    Our friends at the German forum Digital Eliteboard found that by upgrading the firmware 3.2.4 to version 3.2.5 on GO x10, this solved their satellite discovery problem. We tried to transpose this solution on the GO x20/x30/7000, but unfortunately, this flashing was only possible with an old navcore 6.xxx, incompatible with GO x20/x30/7000. Several members of the forum have tested many versions of navcores 6.xxx, 7.xxx, 8.xxx and 9.xxx (I have personally spent a lot of time, like some others!), but the flashing still failed, and we despaired of succeeding, until... August 21st!

    Thanks to his tenacity and perseverance, our friend Lecter has finally found the right combination of a flashing tool and a navcore that works on the GO x20/x30/7000 and allows to update the firmware! Other members of the Digital Eliteboard forum (treysis and jungblume2005) have modified the update files so that they can be used on all models equipped with a SiRFStarIII chip and with any type of SD card.

    I did a lot of tests and deleted all superfluous files to get a minimalist version. As it also concerns the One v1, One New Edition, GO x10 and Rider 1 and 2, I added a splash screen for these models equipped with a 3.5 "or 4" screen. Then, our superprogrammer treysis has lightened the file "ttsystem" which allows to start the flashing process. This resulted in a very compact archive: 2.87 MB. You can download it below:

    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.


    Breaking news!

    Our friend jungblume2005 found a firmware even more recent than version 3.2.5: he found a version 3.6.0. Several members of the forum tested it, and we came to the following conclusion: this version generally allows to find 1-2 satellites more than version 3.2.5, but the synchronization time after a cold start is a little longer. So it's a personal choice: if you want your GPS to always synchronize as quickly as possible, choose version 3.2.5, if you prefer to wait maybe a little longer, but get the most satellites, take version 3.6.0. You can download it below (2.84 MB).

    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.


    N. B. The update procedure is exactly the same, regardless of the firmware version used, and it is possible to return from one version to another without any problem: at each new flashing, the version of the firmware used replaces the one that was currently in the GPS. This allows you to do your own comparative tests and choose the version you prefer.

    WARNING !!! This operation, although easy to perform, is not without risk!
    It is similar to updating the BIOS on a PC. It should not be interrupted before the end, otherwise the GPS could be permanently damaged. Fully charge the battery or connect the GPS to a power source to make sure it does not turn off before the firmware update is complete. The flashing process takes about 1 minute.

    The archive "Flash_FW_3.2.5.zip" contains the following 7 files:

    \Ttntools\FlashGPS.tool
    \Ttntools\sirfimg.bin
    \Ttntools\sirfimg.ver
    \splash.bmp
    \splashw.bmp
    \ttn
    \ttsystem

    1) Copy the archive to a folder on your hard drive and unzip it. A subfolder named "Flash_FW_3.2.5" will be created.

    2) Copy all the contents of the subfolder "Flash_FW_3.2.5" to the root of a blank SD card and insert it into the GPS after removing the current card if you use one.

    N. B. If you don't have a blank SD card, see below under "Flashing the firmware without a blank SD card".

    3) Start the GPS. When the flashing process starts, you will see an hourglass in the center of the screen with the message "Please wait" in several languages ​​and at the bottom of the screen the message "Flashing new GPS firmware...". A yellow progress bar will also be displayed throughout the flashing process and will become green at the end. When it's finished, the GPS will turn off by itself.

    N. B. Some GPS do not turn off automatically after flashing. In this case, simply press the "reset" hole with a toothpick or unfolded paper clip to turn off the GPS.

    4) Remove the card used for flashing and insert your old card into the GPS if you use one.

    5) Restart the GPS. If it does not start, briefly press the "reset" hole with a toothpick or unfolded paper clip.

    6) If the GPS does not find the satellites quickly after the first restart, press the "reset" hole again with a toothpick or paper clip and restart.

    Now you should no longer have satellite problems, even if you delete the "ephem" folder :-). In reality, after flashing, the GO x20/x30/7000 behaves exactly like the GO x40/x50/9000!

    If you look at the SD card, you will find that the "ttn" file and the "ttntools" folder are gone. It's normal. If you need to flash another GPS, copy the file and the folder again to the SD card.
    ----------------------------------------------------------
    Flashing the firmware without a blank SD card

    You can flash the firmware from the SD card currently used by your GPS or from its internal memory, provided it has at least 3 MB of available free space.

    1) Create a folder named "Backup" at the root of the SD card or internal memory.

    2) Select all the contents of the SD card or internal memory except the "Backup" folder.

    3) Do a "cut and paste" to move all the contents of the card or internal memory to the "Backup" folder. Be careful, do not confuse the "cut and paste", which consists of moving files and/or folders from one place to another, with the "copy and paste" which consists of duplicating them.

    N. B. You can create the "Backup" folder on your hard drive rather than on the SD card or internal memory of your GPS, then "cut and paste" to this folder. This is the same as saving the contents of the card or internal memory to the hard disk before erasing it.

    After this operation it should remain at the root of the SD card or internal memory only the "Backup" folder containing all the files that previously appeared at the root of the SD card or internal memory.

    4) Copy all the contents of the subfolder "Flash_FW_3.2.5" to the root of the SD card or internal memory.

    5) Follow step 3 of the procedure described above for using a blank SD card.

    6) After flashing, delete the 3 files that remained at the root of the SD card or internal memory, BUT NOT the "Backup" folder.

    The 3 files to delete are:

    \splash.bmp
    \splashw.bmp
    \ttsystem

    It should now remain at the root of the SD card or internal memory only the folder "Backup" containing all the files that you have copied there at the beginning by "cut and paste".

    7) Select all the contents of the "Backup" folder and "cut and paste" again to move all that contents to the root of the card or internal memory. You can then delete the empty "Backup" folder. If you have used a "Backup" folder on your hard disk, delete the remaining 3 files so that the SD card or internal memory is completely empty and copy there the contents of the "Backup" folder.

    8) Finally, follow steps 5 and 6 of the procedure described above for using a blank SD card.


    Edit: Since August 21, 2019 a really effective solution has been found!

    Edit: Since September 28, 2019, the firmware update for GO x20/x30/7000 is
    possible with any type of SD card!
    Charlie62 Reviewed by Charlie62 on . Consequences of WNRO for GO x20, x30, 7000, x40, x50 and 9000 using a Navcore Truck 9.702 and known solutions TomTom has released for all these models an update of the last navcore in force before April 6, 2019. The version has increased from 9.510 to 9.541, to correct the bug of WNRO. On the other hand, no update of the navcore Truck 9.702 has been proposed by TomTom, so that the problems of the GPS using this navcore have not been solved. But fortunately, the saying "there are no problems, only solutions" is confirmed once more. Let's see what solutions have been found: A) The clock problem. Rating: 5
    Last edited by Charlie62; 1st November 2019 at 10:10 AM.

  2. The Following 65 Users Say Thank You to Charlie62 For This Useful Post:
    [ Click To Expand ]

    30Jose (28th August 2019), adrianm (8th December 2019), Alfred_ML (23rd August 2019), antoniolurdes (25th July 2019), benci81 (24th January 2020), beraun (23rd August 2019), berkem (25th July 2019), bernardomdez (27th September 2019), Bertje34 (23rd August 2019), biggerdave (19th June 2019), briciola31 (25th October 2019), Bubu (7th July 2019), caam14 (24th January 2020), caulonia (27th January 2020), CCCOMEYCALLA (8th July 2019), chickenlicker22 (17th July 2019), chilindrin (8th September 2019), craphacker (3rd October 2019), d0m4n (8th August 2019), dave7037 (3rd July 2019), driekes (24th May 2020), fifinios (18th June 2019), florinpur (31st August 2019), fullequipe (27th July 2019), gijs (30th August 2019), gomenuje (14th September 2019), harmjan_baltes (31st October 2019), hes388 (11th December 2019), ibocan4777 (4th November 2019), Jeanet (18th June 2019), jimbobc (18th June 2019), joke (13th November 2019), jose.freitas (5th July 2019), kadaf (21st December 2019), kraguj (31st October 2019), KurtCobain (31st August 2019), Maa1506 (22nd April 2020), mace10001 (30th November 2019), manifold (22nd September 2019), marky1991 (17th October 2019), menta (19th June 2019), meskis (30th July 2019), miguelseguranca (26th September 2019), moki71 (28th November 2019), Momatz (6th October 2019), Nando Rola (21st July 2019), Obol (29th September 2019), onistimnotboris (22nd October 2019), Orni (26th September 2019), paco1967 (19th June 2019), pacoanaykiko (17th October 2019), paveu78 (1st September 2019), PeterHimself (19th June 2019), powermeta (18th August 2019), sergioverona20 (17th August 2019), stuntdouble (25th June 2019), the Maverick (25th June 2019), Timbaland (25th February 2020), tohis (28th August 2019), treysis (21st September 2019), victorgonzalez (21st July 2019), Xius27 (31st August 2019), yopy (25th September 2019), zielony406 (31st March 2020), Zurumbatico (20th July 2019)

  3.   Advertisements

  4.     
    #2
    Hi I used the preventitive measures and it worked, however when I go to "reset" it then crashes and then crashes on the start screen and wont go further than that.

    Will this be a navcore or map problem?

    Thanks for the help

  5. The Following 1 Users Say Thank You to gleaveri For This Useful Post:
    [ Click To Expand ]

    briciola31 (25th October 2019)

  6.     
    #3
    What is your GPS model, what navcore and map are you using, etc. ? Without any information on your configuration it's impossible to help you!

  7. The Following 3 Users Say Thank You to Charlie62 For This Useful Post:
    [ Click To Expand ]

    briciola31 (25th October 2019), Momatz (6th October 2019), Motocarletto (5th August 2019)

  8.     
    #4
    bom dia muito obrigado

    Single post IN ENGLISH will suffice: "good morning thank you very much" but why not just click the "Thanks" box

  9. The Following 1 Users Say Thank You to antoniolurdes For This Useful Post:
    [ Click To Expand ]

    briciola31 (25th October 2019)

  10.     
    #5
    berkem's Avatar
    @Charlie62,
    B) The satellite problem it does not work. Thanks now works..
    Last edited by berkem; 26th July 2019 at 12:23 AM.

  11. The Following 2 Users Say Thank You to berkem For This Useful Post:
    [ Click To Expand ]

    briciola31 (25th October 2019), Charlie62 (27th July 2019)

  12.     
    #6
    only 5 day work gps model go 930

  13. The Following 1 Users Say Thank You to miszcz1977 For This Useful Post:
    [ Click To Expand ]

    briciola31 (25th October 2019)

  14.     
    #7
    TomTom Master
    rusigor's Avatar


    Consequences of WNRO for GO x20, x30, 7000, x40, x50 and 9000 using a Navcore Truck 9.702 and known solutions
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    Update QuickGPSfix as shown in post #1

    PS You must do it regularly - 1-2 times a week.

  15. The Following 1 Users Say Thank You to rusigor For This Useful Post:
    [ Click To Expand ]

    briciola31 (25th October 2019)

  16.     
    #8
    Or use an alternative (paperclip, suicide.dat) if you are at the end of the World without internet connection...
    In this case, your Go930 will even work with a completely empty ephem folder!

  17. The Following 4 Users Say Thank You to Alfred_ML For This Useful Post:
    [ Click To Expand ]

    briciola31 (25th October 2019), Momatz (6th October 2019), Nando Rola (18th November 2019), pe1agp (13th August 2019)

  18.     
    #9
    Since 21.08.2019 there is the ultimate solution to fix the satellite problem of the x20/30/7000: Flashing the existing GPS firmware GSW3.2.4 to GSW3.2.5. Please read the posting # 1 / B point 3.
    Not only interesting for users of the Truck-NC 9.702, all older NC 9.xxx (like Rider or 9.501) are running after flashing the GPS firmware without problems.
    Last edited by Alfred_ML; 23rd August 2019 at 01:13 PM.

  19. The Following 4 Users Say Thank You to Alfred_ML For This Useful Post:
    [ Click To Expand ]

    briciola31 (25th October 2019), Momatz (6th October 2019), Nando Rola (18th November 2019), yopy (25th September 2019)

  20.     
    #10
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.
    Indeed, the firmware update from 3.2.4 to 3.2.5 solves the satellite problem with ALL navcores. I did exhaustive tests on a GO 720 and a GO 730 with the following official navcores (no modification and empty "ephem" folder): 9.510, 9.541, 9.701 and 9.702. There is no longer any problem with satellites. It's even possible to completely delete the "ephem" folder! After flashing, the x20/x30/7000 behave exactly like the x40/x50/9000.

    N. B. With the 9.541 the x20/x30/7000 that still have the 3.2.4 firmware have anyway no problem, because it's the only official navcore (except the 8.843 for Carminat TomTom) that solves the satellite problem.
    Last edited by Charlie62; 30th September 2019 at 04:53 AM.

  21. The Following 10 Users Say Thank You to Charlie62 For This Useful Post:
    [ Click To Expand ]

    biggerdave (30th August 2019), briciola31 (25th October 2019), Calamar_Gigante (1st January 2020), funkoligy (30th September 2019), joke (13th November 2019), livvy (24th September 2019), miszcz1977 (31st August 2019), Momatz (6th October 2019), Nando Rola (18th November 2019), pe1agp (23rd August 2019)

Page 1 of 4 123 ... LastLast

  Suggested Articles:

Amount:

Enter a message for the receiver:
BE SOCIAL
Consequences of WNRO for GO x20, x30, 7000, x40, x50 and 9000 using a Navcore Truck 9.702 and known solutions Consequences of WNRO for GO x20, x30, 7000, x40, x50 and 9000 using a Navcore Truck 9.702 and known solutions Consequences of WNRO for GO x20, x30, 7000, x40, x50 and 9000 using a Navcore Truck 9.702 and known solutions GPSurl On Facebook Consequences of WNRO for GO x20, x30, 7000, x40, x50 and 9000 using a Navcore Truck 9.702 and known solutions