Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 10 of 10
  1. #1
    Master
    Join Date
    Dec 2015
    Location
    EU and Earth
    Posts
    81
    Rep Power
    65

    Default Igo Primo 9.6 trip duration time update

    Dear community,

    When I define a route, e.g. from Paris to London, IGO shows the remaining time to destination.
    My question is:

    Is there a way (sys.txt) to force a faster update of the remaining time?

    When I start the trip, it showns me for instance, 3:45 hours to destination, when on reality during the trip it is updating (very slowly) the remaining time.

    On highway I normally drive at 155 km/Hour (146 km/hour on the GPS) and on a 300 km distance the diference is +/- 35 minutes between first information (at departure) and final information (reaching the destination).

    Thanks for your help.

  2.    Advertissements


  3. #2
    iGO Moderator

    Boki_Srb's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    44
    Posts
    677
    Rep Power
    208

    Default

    I think that none of the devices does not own magical powers and is not clairvoyant
    In Primo can be defined average speed on three types of roads (city/motorway/highway...or something like that), but trip is dependent on many additional factors.

  4. #3
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,646
    Rep Power
    638

    Default

    Answer
    Spoiler: .

    This post requires you to click the "LIKE this post" button and hit F5 to read this content.
    "You know the very powerful and the very stupid have one thing in common. They don't alter their views to fit the facts. They alter the facts to fit the views." -DrWho

    Do NOT PM me with requests or for fixes to your problem. Post in thread instead. All communications in English only!

  5. #4
    Master
    Join Date
    Dec 2015
    Location
    EU and Earth
    Posts
    81
    Rep Power
    65

    Default

    the issue here is, when I drive fast (155 km/hour - at 146 km/hour on GPS speed) the ETA takes too long to update. If I drive half an hour at that speed, the software only takes me 3 or 4 minutes to ETA.

    I travel a lot driving, doing 300/400 kms and the ETA is never correct. Only when I'm almost at destination that the software gives an ETA most accurate.

  6. #5
    Master G-ulash's Avatar
    Join Date
    May 2014
    Location
    Yellow Brick Road
    Posts
    268
    Rep Power
    6

    Default

    That is strange because on WinCE I never had such issue and I have had many iGO 8 and Primo.
    Now I am on Android and tried some Primo, now on NextGen and my experience on all versions I tried, whatever OS, is that ETA on start may not be correct but gets more correct on driving. Also while driving the minutes update almost by the minute, so on real time. Standing still for a while and the time goes up by the minute, on driving minutes drop. Quite fluently so to speak.
    Are you sure your 9.6 is fully working and has no defective part in the program somewhere? Is it a cracked one? Is it a Primo for a specific device such as Clarion, working on a different device?
    Last edited by G-ulash; 24th September 2016 at 21:10.

  7. #6
    Master
    Join Date
    Dec 2015
    Location
    EU and Earth
    Posts
    81
    Rep Power
    65

    Default

    Quote Originally Posted by G-ulash View Post
    That is strange because on WinCE I never had such issue and I have had many iGO 8 and Primo.
    Now I am on Android and tried some Primo, now on NextGen and my experience on all versions I tried, whatever OS, is that ETA on start may not be correct but gets more correct on driving. Also while driving the minutes update almost by the minute, so on real time. Standing still for a while and the time goes up by the minute, on driving minutes drop. Quite fluently so to speak.
    Are you sure your 9.6 is fully working and has no defective part in the program somewhere? Is it a cracked one? Is it a Primo for a specific device such as Clarion, working on a different device?

    The version I have was mooded here with the help of the community but the base is an original Igo Primo SD card.
    I changed th skin and added some more commands to sys.txt
    The device is a dynavin module connected to the composition media of my VW golf km 7.

  8. #7
    Master G-ulash's Avatar
    Join Date
    May 2014
    Location
    Yellow Brick Road
    Posts
    268
    Rep Power
    6

    Default

    To rule out a memory issue, have you tried without a skin, DEM, buildings, etc, everything that uses (extra) memory?

  9. #8
    Master
    Join Date
    Dec 2015
    Location
    EU and Earth
    Posts
    81
    Rep Power
    65

    Default

    Quote Originally Posted by G-ulash View Post
    To rule out a memory issue, have you tried without a skin, DEM, buildings, etc, everything that uses (extra) memory?
    Nop ... have to test.
    Will come back after.

  10. #9
    Master
    Join Date
    Dec 2015
    Location
    EU and Earth
    Posts
    81
    Rep Power
    65

    Default

    Quote Originally Posted by G-ulash View Post
    To rule out a memory issue, have you tried without a skin, DEM, buildings, etc, everything that uses (extra) memory?
    Tested with clean sys.txt and skin, etc etc and the update time is the same. Today I made 900 km and I counted ...
    at 146km/hour GPS Speed, the update takes 5 minutes (12 kms run ...) to reduce in 1 minute to the trip. In one hour drive it takes off 10 minutes from the final ETA which is awful. I arrived 45 minutes earlier than first "projection", driving 2.5 hours.

  11. #10
    Master G-ulash's Avatar
    Join Date
    May 2014
    Location
    Yellow Brick Road
    Posts
    268
    Rep Power
    6

    Default

    Considering that primo calculates the driving time on the map ( and map data including speed limits), Primo not calculating based on your speedometer, it might be an idea to simply try another (the other -TomTom vs HERE)) mapset? In my region HERE rarely shows the correct speed limits - one of the reasons I prefer TomTom maps - while on vacation I noticed TT speed limits very often wrong. As I only did have one mapset loaded I could not compare, but speaking to acquaintances, I was told that HERE maps were better over there.


    Besides map data, all sorts of Primo settings can have a major impact on arrival time, like maximum speed for a category of vehicle (example: truck = 80 kmh) or the setting of normal or average driving speed. Can you go over your settings in a critical way, asking yourself if a setting is correct and could influence driving time?

 

 

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
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.