MyDrive Connect misidentifies my VIA 1530 as a "VIA 125" and tells me that it will NOT update maps — TomTom Community

MyDrive Connect misidentifies my VIA 1530 as a "VIA 125" and tells me that it will NOT update maps

MyConnect Drive software version is 4.2.5.3734 and is configured to use the USA location.
I am based in USA.
I am sure that I have a VIA 1530TM because I still have the original box and the serial number on the box exterior matches the serial number on my device.
MyConnect tells me that I will no longer be getting any Map updates.
My VIA 1530TM came with Lifetime Traffic and Maps.
How can I get MyConnect driver to properly identify my VIA 1530TM??
Thanks

Comments

  • YamFazManYamFazMan Posts: 15,103 Superusers
    edited March 31
    Hi
    @geisendr

    The same Tomtom Devices have different Names & Model numbers in different World Trading zones

    Try....
    With MyDrive Connect running...
    Tap on the Gear Icon screen top right
    Tap on the General Tab
    On the Country Tab... Select 'United States (English)'
    Save setting... All should be well :)

    mem19vyyk5cu.png
    ATB YFM
  • Lel0763Lel0763 Posts: 1 [New Seeker]
    I have the same problem, but My TomTom already has the Country correct. I even changed it to United Kingdom and changed it back to United States, but the problem remains. Any other ideas?
  • DennjDennj Posts: 2 [Apprentice Traveler]
    Same here. I have a VIA 1410 / 1415 and MyDrive Connect says I have a Start20 I didn't notice at first and it updated and corrupted everything. I can't get it to identify my device, so I can't download new maps to fix it.
  • dhndhn Posts: 33,173 Superusers
    The same model is known by different names in various regions around the world. That shouldn't affect your ability to download appropriate maps, etc.

    Support:

    877-757-7137
    Monday - Friday: 9:30 a.m. to 6:00 p.m. EST
  • DennjDennj Posts: 2 [Apprentice Traveler]
    Okay, I deleted "corrupted map" and the device downloaded a new one under the model name Start20 ...had to do a soft-reset a couple of times. Works now. Thanks dhn
Sign In or Register to comment.

Who's Online3

3 Guests