See my post here: http://www.audi-sport.net/xf/threads/2018-europe-maps-now-available.351412/#post-3138278just tried to download from my audi and the file is a jnlp and the car doesnt see the sd card, it stays greyed out?? Am i doing this wrong?
See my post here: http://www.audi-sport.net/xf/threads/2018-europe-maps-now-available.351412/#post-3138278just tried to download from my audi and the file is a jnlp and the car doesnt see the sd card, it stays greyed out?? Am i doing this wrong?
Tried @mcaddy app last night. Looks really useful but unfortunately on my B8.5 Audi S4 (tech pack high with HDD Sat Nav), it tells me "The crc of the release info is not correct" and doesnt work. Any ideas? Do I need to update my MMI firmware first, or is there a problem with the checksum that the app generated?
Can't say I have had any issues, they seem accurate within 5m or so.Has anyone noticed that the speed camera locations (using PocketGPSWorld database) are "out" by approx 50-100 meters or so?
Just wondering if its the accurary of the data relating to just cameras in my area, accuracy of the data in general, or whether the GPS is "out".
Cheers
AL
Don't think anybody figured out a way to do it.Due to get my facelift A3 on the 19th and will be adding the cameras right away.
I read through every post on the thread and noticed 1 or 2 have instructions for the notifications.
Would you mind sharing the steps to get notifications for the approaching the cameras? Couldn’t see any definitive instructions.
Don't think anybody figured out a way to do it.
More information coming soon but this will be a chargeable modification as I have invested significant time in development, testing and tooling.
Would be very interested if could be done for 2016 PFL if technically possibleMore information coming soon but this will be a chargeable modification as I have invested significant time in development, testing and tooling.
Edit: only tested on FL 2017+ vehicles so far.
PFL Testing is planned, just need access to a vehicle with Technology Pack.Would be very interested if could be done for 2016 PFL if technically possible
Good job anyway.
Just gonna leave this here
I must admit that I have not actually tested the arrival notifications option on its own as yet, I just dove straight in with my customised solution but need to compare both.Nice.
How does this differ from just uploading POI and setting up arrival notifications? Looks very similar.
Sent from my iPhone using Tapatalk Pro
DIS and Virtual Cockpit warning are impossible on the A3 and Q2 platforms with major works and without some loss of other functionality... basiclly you have to tell the car it’s a TT mk3.When I tried arrival notifications on the motorway it appears to give you more warning than on residential roads.
My main issue with arrival notifications is that it provides that warning even if you are not on the same road as the camera. Which is really annoying on the motorway when it alerts you to cameras on side roads etc.
If your approach solves that then you are on to a winner! Especially if you can get the message on the DIS rather than just the MMI
Sent from my iPhone using Tapatalk Pro
I wondered about this too, as I would think it could be a bit annoying when there are cameras on the motorway - especially if it would alert you for both sides.My main issue with arrival notifications is that it provides that warning even if you are not on the same road as the camera. Which is really annoying on the motorway when it alerts you to cameras on side roads etc.
Ok, so it would seem that I jumped the gun a bit on this modification. Knowing what I know about the MMI system and settings which the average person cannot access I updated my poi database and then made some hidden changes which I thought would actually tweak the system. It would seem however that these hidden changes did not affect anything at all and the arrival notification is actually working, and adaptive based on speed, "out of the box". So for residential streets and A roads the notification counts from around 90 yards. Motorway speeds the count is from 900 yards.I must admit that I have not actually tested the arrival notifications option on its own as yet, I just dove straight in with my customised solution but need to compare both.
There are two parts to this features testing:
1) residential speeds
2) motorway speeds
My solution works very well but I have to compare it to the arrival notification as I don’t want to rip anyone off. I tested residential speeds via the arrival notification today but still need to test this at motorway speeds. Will try to test tonight.
Advance warning beep (multi tone so not technically a beep) works on the Golf (and isn’t triggered by cams on the other side of the road) but only works if uploading to a German VW site and ticking the box for notifications - wonder if this would work on an A/S3 ?
This process of POI is very similar but I guess it’ll come down to the hardware.
Ok, so it would seem that I jumped the gun a bit on this modification. Knowing what I know about the MMI system and settings which the average person cannot access I updated my poi database and then made some hidden changes which I thought would actually tweak the system. It would seem however that these hidden changes did not affect anything at all and the arrival notification is actually working, and adaptive based on speed, "out of the box". So for residential streets and A roads the notification counts from around 90 yards. Motorway speeds the count is from 900 yards.
I am testing with the Pocketgps but I believe the thinkware and inforad are directional. Will test with them when I get the chanceInteresting. Do you have the details of the POI source you use that is directional. I use pocketgpsworld and it doesn’t seem to be directional.
Sent from my iPhone using Tapatalk Pro
I've just added speed cameras to my new A3 and come up against the exact same issue. If I use the files before editing the zoom level they load fine, but after editing to 30 I get the same message as you. Did you ever find a solution to this? I've tried notepad and notepad++ so far without success.Has anyone else had problems after editing the categories.pc file to change the max zoom level from 9 to 30? As soon as I do that it won't load in the car saying 'The update was interrupted'. I've tried a couple of different editors.
I did notice the file hashes.txt in the same directory contains the filesize and checksum of the categories.pc file and obviously I am changing both. My car is a July 2017 build S4.
When I was writing my C# Library to generate POI files for my Audi and I was surprised to see that the Checksums are not checked. Some might be but all the ones that I 'broke' didn't result in a rejection. Given that the Checksums where trivial to calculate I've done them but it seems they are not required.
If your interested, I've checked my code into GitHub (https://github.com/mcaddy/audipoi) I use it to create POI DBs and the associated Meta data without the need to use the Audi website, currently using this to build a POI file with 8 distinct types, all loaded from a single GPX file.
That's the one. I couldn't remember it of the top of my head but that's the app I tried. I'd be interested if you get the same error I did when connecting to my pocketgps account.Just reading this again. Mcaddy spotted when he was developing this that the checksums were not checked by Audi, but coded the correction anyway. I've never tried his app, but may give it a go.
AL