Skip to content

RNS510 / Columbus not showing POI

Featured Replies

Even though my Columbus has installed a POI.DB3 file I cannot click onto the POIs to select any and they are not displayed in the map either.

Otherwise the HU is working fine.

Does anyone have a solution for this problem?

Not familiar with POI.DB3 but suspect it's a commercial program or user developed or knock off.

 

How POI import works is that VAG has a specification and each unit has to be specified within the parameter file that it uses to import the file into the unit. VW often didn't populate the file parameters as new units came out. Often with the VW website when it was up. there were moans about it not seeing the car. After VW pulled the plug on their website import for POIs, Seat mib2 standard units with wifi it didn't see the import. Both the commercial suppliers and developed apps were not working with this unit.

 

POInspector was the one I was using.

 

https://poinspect0r.blogspot.com/

 

With these package solution you have to load up your own POIs. I did provide documentation that the author of the program used:

 

https://www.seatcupra.net/forums/threads/uploading-speed-camera-safety-camera-user-pois.444799/#post-4780168

 

https://www.seatcupra.net/forums/resources/uploading-speed-camera-safety-camera-user-pois.12/

 

This package is backwards compatible but you have to put the work in yourself.

 

Back to story. Spanish Seat forum uses published Spanish speed cameras that were imported into the VAG format and distributed by the forum. The guy that did the work was one of the mods.

 

The missing infotainment identifiers were found by a German user. The system IDs appear in the firmware uploads so by studying those you can identify what is missing. There were / are two import files for the mib2 standard and high. 

 

I suspect that's the issue. it's a missing variant ID. I suspect you haven't got it. If you happen to have the firmware file for your system and visually check your POI import meta file I suspect you won't have the unit listed. Worth a check. Then go back to whoever supports POI.DB3 and say you need it added. Alternatively you could have the wrong upload.

 

The latest meta file looks like this:

 

#################################################################################
#   
# This is the description file for the Software Update of Volkswagen components
#
#################################################################################

[common]
Vendor = "Volkswagen"
Variant = "FM?-H-*-*-*"
Variant2 = "17206"
Variant3 = "17207"
Variant4 = "37206"
Variant5 = "37207"
Variant6 = "47203"
Variant7 = "47204"
Variant8 = "17216"
Variant9 = "17217"
Variant10 = "37212"
Variant11 = "37213"
Variant12 = "47208"
Variant13 = "47209"
Variant14 = "17212"
Variant15 = "37208"
Variant16 = "47205"
Variant17 = "17222"
Variant18 = "47210"
Variant19 = "17224"
Variant20 = "37214"
Variant21 = "17210"
Variant22 = "17220"
Variant23 = "17245"
Variant24 = "17246"
Variant25 = "17250"
Variant26 = "17251"
Variant27 = "17247"
Variant28 = "17252"
Variant29 = "17254"
Variant30 = "17255"
Variant31 = "17268"
Variant32 = "17269"
Variant33 = "17270"
Variant34 = "17271"
Variant35 = "47213"
Variant36 = "47214"
Variant37 = "47215"
Variant38 = "47216"
Region = "Europe"
Region2 = "RoW"
Region3 = "USA"
MetafileChecksum = "d3f9e1f47675003e96331df6202b162c7c407a88"

[common_Release_1]
Name = "MIB 2 High Personal POI"
Path = "./PersonalPOI/MIB2HIGH"
Variant = "FM?-H-*-*-*"
Region = "Europe"
Region2 = "RoW"
Region3 = "USA"

[common_Release_2]
Name = "MIB 2 Standard Delphi Personal POI"
Path = "./PersonalPOI/MIB2DE"
Variant = "17245"
Variant2 = "17246"
Variant3 = "17250"
Variant4 = "17251"
Variant5 = "17247"
Variant6 = "17252"
Variant7 = "17254"
Variant8 = "17255"
Variant9 = "17268"
Variant10 = "17269"
Variant11 = "17270"
Variant12 = "17271"
Region = "Europe"
Region2 = "RoW"
Region3 = "USA"

[common_Release_3]
Name = "MIB 2 Standard TechniSat Personal POI"
Path = "./PersonalPOI/MIB2TSD"
Variant = "17206"
Variant2 = "17207"
Variant3 = "37206"
Variant4 = "37207"
Variant5 = "47203"
Variant6 = "47204"
Variant7 = "17216"
Variant8 = "17217"
Variant9 = "37212"
Variant10 = "37213"
Variant11 = "47208"
Variant12 = "47209"
Variant13 = "17212"
Variant14 = "37208"
Variant15 = "47205"
Variant16 = "17222"
Variant17 = "47210"
Variant18 = "17224"
Variant19 = "37214"
Variant20 = "17210"
Variant21 = "17220"
Variant22 = "47213"
Variant23 = "47214"
Variant24 = "47215"
Variant25 = "47216"
Region = "Europe"
Region2 = "RoW"
Region3 = "USA"

[Signature]
signature1 = "9880af1b5d5456de15affd708b3b74b2"
signature2 = "3cf0dbe1d0baf902e43229a07cfb9281"
signature3 = "3c76dea04775d174ac4f937445ae538b"
signature4 = "84d056d12279144f13341a7ccec3a7a2"
signature5 = "39120b41cbf137351aa6a08c732b3521"
signature6 = "5a224666234d8700e6c46bf2a943452c"
signature7 = "b06daa662fc8d9a1aee981c0a5df7c1a"
signature8 = "4bcd566ead66604069d58ab0a9f77d14"

 

-----

 

It was two of those variants missing. The variants cover every mib unit to mib2. Either way if you have a copy of the firmware with the variants and check your import meta file and you are missing variants that's the issue.

 

That's the problem with knock off files doing the rounds they aren't kept up to date as well as breaking copyright of the POIs they are using.

 

 

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.