Separate names with a comma.
Discussion in 'Ateca' started by Tell, Jun 3, 2018.
Yes, has wifi (useless feature)
What we need to know is whether anyone else has had success with Poinspector with the latest Seat standard unit with Wi-Fi. Works with the others.
Re: not working on the latest Seat standard unit with wifi.
I emailed Radas who confirmed that he's had a few reports of the new navi unit (would be standard with wifi) recognising the data on SD but won't import it.... "there is no solution so far".
You could try one trick but he might have tried that already with people, that's to copy out the contents of a deeper directory from the SD card, put it on the route deleting the rest. This was a trick that you had to do with the MIB2 high at one stage. Not saying that's the solution but you could try it. Possibly doesn't tie up with what Radas said.
Produce the card as per normal as a standard navigation.
Then go to this directory:
F is your drive letter.
You will see
directory personalpoi and the metainfo2.txt file
Copy just these two back to your hard disk somewhere, delete what was on F completely so you have a blank SD card (this isn't the SD map card BTW)
Then copy the contents directory personalpoi and the metainfo2.txt file to the route of the SD card. This bypasses the check that the VW software does to decide whether it's a high or a standard. That check is in the code we bypass, so if it's failing on that check due to the unit having a new code it's bypassed and goes directly into import.
If that doesn't work then it's not that. It was an old issue that VW use to switch between the high and the standard unit on the website method messing up their list of IDs for the units. The high side in Radas program skips this check (in the musical chairs of the old VW site you had to do it like this yourself) but the standard side still uses the code in what he writes out although at one stage they got that wrong.
Radas might have got someone to try that, but it's worth a try.
I guess failing that once one of the commercial POI outfits have mastered what is going on, one can to learn from that, if it's not the above.
site working again
Nope... checked it. That's a hanging page that doesn't do anything. We had something like that posted up at the time when the original was removed on another website. Does the HTTP web stuff but nothing else since it's not connected to anything.
May be people have got Rada's program running on the 2019 Seat standard unit with wifi with Poinpsector. Shout either way so we can determine whether it's real or not.
Certainly works on everything else.
Tell, I am determined to get speed camera alerts on my Sat Nav. So, using https://free-speed-cam-updates.web2diz.net/volkswagen-speed-camera-download/ I downloaded Volkswagen 505.58 k updated 4/2019 and Volkswagen combined 3.33m updated 4/2019 unzipped them both onto the same sd card and plonked it into slot 2. After following the installation instructions it loaded 200 fixed cameras and 200 red light cameras but disappointingly no mobile cameras in my pol's. I have not road tested this yet but it looks promising as the icons show up on the maps I just hope that it sounds the alerts. Is this what you do or is it something new?
Those are pre-prepared files rather than taking the speed camera file data which has the x,y coordinates in them. The free files may not be up to date and may not have mobile sites in them which yours evidently don't. I think the Google ones are like that plus those in other satnavs. The definition of what a camera is fixed or mobile.
Poinspector reads these free or paid raw files and generates the upload to the car. It will upload any POI or user defined one. That's how I get my destinations in at accurate hiking spots rather fumbling with the cog wheel in DMS. Back on speed cameras I use the PocketGPSWorld subscription ones, £20 per year. They cover fixed and mobile cameras. For Europe you get four file files which cover the lot. UK fixed and mobile, Europe fixed and mobile. You download them... the rest is document on the thread. I use the GPX format for then, that's under the "other" option from memory. Poinspector needs a little bit of work on your behalf to set up the import frame, correct icon size which I cover then after that it's easy to update. That's all covered.
The only question I have yet to resolve is whether there is an issue with the latest standard Seat navigation unit, the one with Wi-Fi. Hearsay evidence of whether there is an issue or not or whether it is an operator error on somebodies part.
If you said you had that unit and poinspector turns out not to work then the file you had would be of use to the developer Radas to get it to work. You can test Poinspector on a small sample of records, I gave them on the thread or spend the £10 or whatever it is to get the program unlocked for larger records.
So question which Seat navigation unit do you have. Does it have WiFi as an option ?. All others we know are fine with the program.
Source Maps in Vag cars
In post 9 I talk about finding locations in Here We Go app as a good similarity to the maps in the car as Here Maps are the ones used in Vag navigation system, correction, although the Here Map branded website holds Vag map updates the maps are sourced differently for the standard Mib2 and Mib2 High (Plus, Discover Pro, Columbus).
Map source used by Vag in Europe (atleast):
Mib2 Standard - TomTom
Mib2 High - Here Maps
Important point if you are a map contributor and want to help improving these products via the edit and reporting tools:
Standard Mib2 - TomTom
Plus (Mib2 High) - Here Maps
Armed with this knowledge it explains why the two systems route you differently based on different data and different algorithms although the user interface is specified the same. Cross checking the cars maps with the sources it became apparent that the standard units maps were TomTom sourced, the jewel case for the SD card mentioning TomTom is also a give away.
Google Maps / Waze
For completeness Google Map errors / additions can be reported following this link for those that find issues with Waze & Google Maps cartography. Uses a similar method to TomTom of identifying issues by pointing at them.
Note MY19 / M20 Seat Cars - Standard Navi - POI import not working
It's now become well documented via the Spanish Club Seat Ateca site that the standard navi unit MY19 & MY20 with the build device part number finishing in 877 and 877A will not import user POIs whether generated by Poinspector, commercial or free Pois. The issues goes across to Leon units. The Mib2 High plus units are fine which we already knew. The issue is not related to the software serial number of the units (0512 / 0514) but part number finishing in 877 and 877A.
The part number can be obtained by
● Press the Infotainment MENU button and
then select Setup .
● In the System settings menu, press the
System information function button.
The top line shows the device part number. If that finishes with 877 or 877A then the unit will not import users Poi's. Seat have acknowledged the issue.
More details on the Spanish thread
There are a few red herrings on the thread about the Navigation Plus unit which relate to VW changing the file header, Poinpector takes care of that but commercial or free ones may not so you do the directory copy trick. It's not related to the map provider either which recently changed to TomTom for the standard unit. The real issue is the fault that Seat rolled out into the standard MY19 / M20 units with the part number code covered above.
That's the situation as of October 2019. The check can be carried out if in doubt with future releases.
Hi Tell, I have Discovery Pro in my VW. You wrote:
The MIB2 standard and high (Seat Plus) set at 0 for no warning, 1 for a warning warble. The MIB2 High at least computes your speed and distance to warble in time...
There is no known way to alert at a fixed distance, or at least earlier? At this moment my unit alerts me very late, I think.[/QUOTE]
In the Mib units whether standard or high (Discovery Pro) version 1 or 2 the unit itself works out based on your speed and distance from the camera when to warble. Approaching more slowly less distance, faster more distance - least my understanding although I have never tested that aspect. It was the pre Mib units where it was possible to alter the upload data to the unit to give you greater warning, people used SQL Lite to ammend the upload data - you find that on the internet. Radas the programmer of Poinspector catered for this by allowing you to enter that warning distance parameter but this has been reported to have no effect with the Mib units (that's 0 for no warbler, 1 for on, above 1 you could try but said to have no effect). You could try changing this but I think it will not make any difference as the unit works on speed too the fixed point.
I have in the past used SQL Lite to look at the file Poinspector generates verses what the old VW website program did following along what others did with the previous VW units that you find documented on the net. Poinspector makes a slight adjustment to the database but it is very small... did have that conversation with Radas but he pointed out it made no effect .
The other way of looking at it is that some of the speed camera POIs are not well digitised to location so there may be instances where the camera warning is not being triggered correctly since the camera has not be digitised to the correct location. The PocketGPSWorld ones you can inspect via their site. If there is one that is troubling you, you could check out the location as being correct.
Lastly the warble sound warning algorithm is within the firmware of the unit. I don't know whether VW may have changed that but I doubt you would want to go to the trouble of changing the firmware.
More likely than not if there is an issue I suspect it may be the quality of how well the speed camera database is digitised rather than anything else. The PocketGPSWorld ones people are happy with although it does have some phantom cameras in it but they tend to be in areas of speed restrictions where mobile camera unit have been entered as fixed and they are not there, but could be there on a different day. You can report the ones you don't like via the PocketGPSWorld website.
Hope that helps.
I have successfully imported speed cameras using the info here, POInspect0r and the Pocket GPS World database. I used the top radio button for MIB output. The second radio button gave an error on import (no data or similar).
The SD card contains subdirectories for TSD, HIGH and DE (from memory) but the head unit seems to pick one that works. Is that the case? I read the card directory format should not have this tree structure but you had to copy the contents of one of the MIB directories.
I do not seem to get a warning sound. I chose a distance of 100 (metres?). Does it have to be 1 to get the sound?
There is a lot of talk about MIB STD HIGH etc. that is really confusing. I have an April 2018 Arona. How do I (or anyone else trying this) tell what MIB unit I have? How do I find out what the different MIB units do? Google is not my friend on this.
The Arona is a mid2 standard. You pick mib2 standard as the export so you don't need to look in the directories, it does that for you.
Select 1 metre for the beeps. 0 metres means no beeps. Have it working on an Arona My 19. It will work.
The beep volume is at the same level as the navigation voice so you need to crank that up to the desired level. You press the right button with navigation destination in, juggle volume to get the navigation sound level up. Use the advanced and demo menu to take the car past a camera. Suspect you either got the navigation level down or the camera isn't set to 1 metre warnings. The actual advance time the unit computes from the cars speed to the POI. It's a phaser type of sound.
Thanks Tell. I tried just the contents of the TSD subdirectory on the SD card alone and changed the distance to 1. The demo gave the warning sound. It was the same sound I heard before. It is a pretty quiet non-descript warning signal, easily missed even with automatic lowering of media volume and Sophie's volume at acceptable levels. I wish we had Sophie actually saying "POI coming up".
My conclusion, at least for my car is that a distance of 1 or greater is OK, and you don't need to do anything with the SD card output files since the MIB software chooses the correct one from the three options.
Thanks for your work on this. POInspect0r makes it so easy.
Sophie is what we call the SatNav "Make a U turn if paaahsible"
Glad it's working for you now. The mix volume of the warning against "Sophie" may be down to the firmware version.
In the standard version the pronunciation is different to the high although same voice. She likes to call Pembroke Dock, Pembroke Duck in the standard, although in the high she gets it right . Not sure whether all Docks are Ducks.
Talking of mispronunciations, if it s Manchester she says Man-cheese-ter. But if its abbreviated to M'Cr, she says Manchester fine. I mean WTF?
She gets very posh for London and Paris though. Paris being Pa-ree
She talk Welsh in some places in Wales so Fishguard becomes Aber something.
I'm looking to do this and have just subscribed to PocketGPSWorld.
However, there are two files each for UK and EUR...... 'Consolidated by Type' and 'Speed Zoned Complete'. Which two do I need, please?
edit: Found it.... just re-read the post..... single file for UK and EUR in GPX format
Consolidated by type is what you need as you can only show so many POI’s on the Sat Nav.
Consolidation shows each camera type and all speeds for that camera types ie all Gatso, Mobile, Average etc.
Speed zones shows (I think) each type by speed type. So Gatso at 70mph, Gatso at 40mph, Mobile at 30mph etc as separate types. ie lots more POI’s which can’t all shown at once as they will be too many of them
Sent from my iPhone using Tapatalk
Yeah, I'd of loved being able to have it with the little icon and speed in the corner. But the Nav only allows so many POI displayed at once.