Activity Stream
248,443 MEMBERS
1636 ONLINE
GPSurl On YouTube Subscribe to our Newsletter GPSurl On Twitter GPSurl On Facebook GPSurl On Google+
GPS Week Number Rollover [WNRO] JUST Findings, Fixes, and Frustrations

Page 36 of 65 FirstFirst ... 26343536373846 ... LastLast
Results 351 to 360 of 641
  1.     
    #351
    Yes, there is already a thread that covers this subject at length...start reading
    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.

    GPS Week Number Rollover [WNRO] JUST Findings, Fixes, and Frustrations

    [Login or Register to remove this advertisement]


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

    Alfred_ML (26th May 2019)

  3.     
    #352
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    If you get access by shell, you should be able to use "cat /var/run/gpspipe" and read the NMEA messages. I suspect the chip is providing a wrong date, 19.7 years ago. At least this was the case on my Rider 2013, but with AR1520 GPS chip.
    In theory it should be possible to intercept the fopen call to the gpspipe fifo by the navigation software, read the data coming from gpspipe, detect the wrong date, correct it, feed it back into the navigation software, and be happy.
    On the Rider 2013 it's a bit simpler, because you can just tell the GPS driver which fifo to use and then write a bridge-application. That's what I did, unfortunately that won't work on GL1 devices. Already checked that. "gltt" provides no option to specify the output fifo.

    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    Even though I told you first you need an alternative software, I did it for my Rider 2013 myself now. You need BTconsole, and then you can connect to the shell via Bluetooth. I used that a lot to produce a fix for my Rider 2013.
    Last edited by treysis; 27th May 2019 at 06:18 AM.

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

    Momatz (28th May 2019)

  5.   Advertisements

    GPS Week Number Rollover [WNRO] JUST Findings, Fixes, and Frustrations
  6.     
    #353
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    6/5/2021 à 12:08:30

  7.     
    #354
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    6/5/2021 à 12:08:30


    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.


    so you claimed it was all nonsense and that the folder should just be emptied?

  8.     
    #355
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.


    6/5/2021 à 12:08:30

    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.


    so you claimed it was all nonsense and that the folder should just be emptied?

  9.     
    #356
    Guys & gals, I think a fix for GL1 devices is possible without help by TomTom. Unfortunately (or fortunately?) I don't own a GL1 device. So if somebody is willing to support me...but could take a couple of days...ideally you shouldn't be afraid of accessing the shell.

  10.     
    #357
    BMWdriver's Avatar
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    Thats right.
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    So you got a working Rider 2013 by inserting a new app between sw "ingsvcd" and NavCore ???
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    Really?
    The gpspipe is created by the init script, but the name is hardcoded in gltt and PNDNavigator.
    You cannot open the connection between pipe and PNDNavigator or between ttgps and pipe.
    (AFAIK)
    Q: pls provide a sample code to do this.

    Next task is to add 1024 weeks to get the right date. Not that simple, because there are leap years to take in account.
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    definitely
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    agreed

    $GPRMC is the ONLY NMEA-message that contains wrong data (date is ddmmyy with yy is 99 in these days).
    All other messages are correct on my One 2nd edition.
    Last edited by BMWdriver; 27th May 2019 at 10:00 PM.

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

    yopy (27th May 2019)

  12.     
    #358
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.
    Does your One v2 have a SiRFStarIII or Global Locate v1 chip?

  13.     
    #359
    BMWdriver's Avatar
    The sirf3 has no problems ;-)
    My one 2nd has a GL1.
    Unfortunately.

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

    Alfred_ML (27th May 2019)

  15.     
    #360
    BMWdriver's Avatar
    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    You can do first tries on your Rider 2013 by NOT creating a second pipe/fifo, just doing the patching of the open systemcall.

    I would be happy to give a try on my device.

Page 36 of 65 FirstFirst ... 26343536373846 ... LastLast

  Suggested Articles:

GPS Week Number Rollover [WNRO] JUST Findings, Fixes, and Frustrations

Tags for this Thread

Amount:

Enter a message for the receiver:
BE SOCIAL
GPS Week Number Rollover [WNRO] JUST Findings, Fixes, and Frustrations GPS Week Number Rollover [WNRO] JUST Findings, Fixes, and Frustrations GPS Week Number Rollover [WNRO] JUST Findings, Fixes, and Frustrations GPSurl On Facebook GPS Week Number Rollover [WNRO] JUST Findings, Fixes, and Frustrations