Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 1 of 4 123 ... LastLast
Results 1 to 10 of 38
  1. #1
    Junior Member
    Join Date
    Mar 2019
    Location
    Toulouse, France
    Posts
    2
    Rep Power
    0

    Default GPS Week Number Rollover (WNRO) issue with IGO Primo under WINCE

    Hi everyone,
    I have just realised today my GPS running Igo Primo 2.4 (Version 9.6.13.405512) under WIN-CE 6.0 is facing the WNRO issue.
    Today 2019/05/01, the GPS UTC date is displayed as 2099/09/15 (see screen shoot at [Only registered and activated users can see links. ]) and recorded trace files are dated 1999/09/15.
    Do other members face the same issue ?
    Is there a fix or a workaround?
    Is there a new Igo Primo 2.4 version that corrects the issue ?
    Thank you in advance for sharing your thoughts,
    FBLG

  2.    Advertissements


  3. #2
    iGO Enthusiast GPS Week Number Rollover (WNRO) issue with IGO Primo under WINCE
    GPS Week Number Rollover (WNRO) issue with IGO Primo under WINCEGPS Week Number Rollover (WNRO) issue with IGO Primo under WINCEGPS Week Number Rollover (WNRO) issue with IGO Primo under WINCEGPS Week Number Rollover (WNRO) issue with IGO Primo under WINCEGPS Week Number Rollover (WNRO) issue with IGO Primo under WINCEGPS Week Number Rollover (WNRO) issue with IGO Primo under WINCE
    Boki_Srb's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    48
    Posts
    4,068
    Rep Power
    2590

    Default

    No problem with my very old device (from 2007) and Primo 2.0 ("KIA" edition)
    Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search.
    NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click!
    [Only registered and activated users can see links. ] <- Click!

    Spoiler: obs
    Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.

  4. #3
    Member
    Join Date
    Dec 2008
    Location
    6464
    Age
    35
    Posts
    17
    Rep Power
    0

    Default

    need update the GPS FW . this is not the IGO issue. this is the Device GPS FW issue (GPS Week Number Rollover)

  5. #4
    Junior Member
    Join Date
    May 2014
    Location
    earth
    Posts
    4
    Rep Power
    0

    Default

    Hi everyone,

    I am running Igo Primo 2.4 (Version 9.6.13.405512) under WIN-CE on an old Mio C520T 2007 and I had the same problem as from April 09, 2019.

    For all of you who are facing the Week Number Rollover (WNRO) issue and before messing up with FW updates a.s.o., try this first in your "sys.txt" file:

    Add or modify accordingly:

    [timezone]
    sync_os_timezone=0
    sync_time=0
    use_auto=0

    Save and restart
    It worked for me and Primo is now working flawlessly (you might have to do a reset if it's not working at once).

  6. #5
    Junior Member
    Join Date
    May 2019
    Location
    Wiltshire, UK
    Posts
    2
    Rep Power
    0

    Default

    Is that really curing the problem though

    It seems to be saying do NOT sync the Win CE system time to the GPS - which you can do in the settings IIRC, somehow the GPS part needs updating to handle the [Only registered and activated users can see links. ] that happens every 19 and a half years or so...

  7. #6
    Member
    Join Date
    Sep 2018
    Location
    Bavaria
    Posts
    10
    Rep Power
    0

    Default

    Quote Originally Posted by OldMio View Post
    I am running Igo Primo 2.4 (Version 9.6.13.405512) under WIN-CE on an old Mio C520T 2007 and I had the same problem as from April 09, 2019.
    Hi!

    Do you have a menue on your MIO for using Igo Primo?

  8. #7
    Junior Member
    Join Date
    Aug 2015
    Location
    Slovakia
    Posts
    4
    Rep Power
    0

    Default

    Hi guys, I think I have the same problem after the rollover. I have a QL-FCS805 all-in-one stereo for my Ford Focus. It doesn't have the option to set a time and date manually, only allows me to change the time zone. Time and date is always synced via GPS. However, after the rollover, I don't have correct time displayed, I only see 00:00 which goes up to 00:01 and so on. Date is also messed up.

    Now, I have the option to "automatically start GPS app" in the background when the unit starts. For GPS app I use iGO 9.6.*. When I use this option, the time and date "synchronizes" with GPS app, however, it's still wrong - when I get to the WinCE OS, I see that it's years ahead - I guess that's the result of the rollover. This option doesn't need to be turned on for the time/date to sync, it's mostly so the GPS starts right up when I select it in the stereo menu.

    But, and this is very weird, when I start iGO from menu, I can see correct time and date in iGO. But only in iGO, when I go back to stereo menu, nothing...it's still messed up.

    I will try the settings mentioned above, but I think this is something in the system/hardware of the unit.

    Does anyone have any other thoughts on how to fix this? Is this a software thing (resetable in registry for example), or something encoded into hardware?
    Thanks for answers!

  9. #8
    GPSPower Helper GPS Week Number Rollover (WNRO) issue with IGO Primo under WINCE
    GPS Week Number Rollover (WNRO) issue with IGO Primo under WINCE
    costas3850's Avatar
    Join Date
    Dec 2009
    Location
    ro
    Age
    32
    Posts
    455
    Rep Power
    618

    Default

    The problem can be solved by firmware update.

    [Only registered and activated users can see links. ]
    TomTom can be updated with tomtom home or tomtom mydrive connect.
    [Only registered and activated users can see links. ] thaks to lexcomputers.
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]

  10. #9
    Junior Member
    Join Date
    May 2019
    Location
    Wiltshire, UK
    Posts
    2
    Rep Power
    0

    Default

    That is only a limited selection of devices and it is not obviously how it would apply to, say, an unknown Chinese IGO clone!

    There must be an existing fiddle factor for these WinCE devices that worked for the last 19.7 years (from some time in 1999 up to April 2019) which handled the fact that the clock had rolled-over one time - which now has to handle a second wrap-around. Perhaps it might be something as simple as a registry value that needs changing from 1 to 2 ...

  11. #10
    Junior Member
    Join Date
    Aug 2015
    Location
    Slovakia
    Posts
    4
    Rep Power
    0

    Default

    When I set my stereo to autostart navigation an with various combinations of these settings:
    [timezone]
    sync_os_timezone=0
    sync_time=0
    use_auto=0

    I actually managed to change the time on my unit. However, it is really only changed - not correct. Or, to be precise, it's correct when I start iGO and there is clock which shows correct time. When I close it, the stereo interface shows wrong time.

    It seems to me that when I force the stereo UI to use the "iGO time", then it would be only about finding the correct time zone settings. However, I don't know how to configure this in the sys.txt.
    There are settings in sys.txt (or actually system.ini in Primo) like "last_sync_time" and similar, where, when I put "some" time and date, it forces this to the stereo UI. This would be perfect, but I don't know how to set it to "now" - so it forces the current time and date that it gets from GPS. I hope at least someone understands this train of thoughts.

    Second observation is, that I can leave the above settings in their "default" mode, so they don't force anything to the system and then the stereo on boot (with navi autostart) shows some time and date, but completely wrong - years in the future, and it also seems that the difference between now and the time/date it's different every time, at least the hours are different - for example: at 7am it sets the clock to 1:32pm and the same happens at 3pm - it sets the clock to lets say 1:22pm. So it's not only hours that are different, but minutes as well, leaving some timezone difference out of question.


    My hope (aside from miraclously finding a new FW for my unit) is in the first scenario, finding some correct settings, to force the unit the current time and date. Any input on this would be very appreciated!

 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •