Spoken POI alerts for TomTom GO, Mobile, PocketPC and Palm

chicago · Occasional Visitor Joined: Jun 13, 2005 Posts: 4

I’ve followed the article and this thread with some interest and thought “maybe I can do that”. Thanks to Lutz for the original work and his swift reply to an e-mail query I had and also TomTomTim for the quick and dirty excel version (his words not mine) and step-by-step guide.

I’ve managed to produce a new data.chk file for my XDA IIs running TomTom Navigator v5 (build 4890) – female voice with maxed out volume at sample rate of 22,050Hz, 16 bit depth, mono (using sony sound forge v8 to both record and manipulate the files).

Here’s the table of original sound and its replacement:

Beep 1 ~ WARNING – approaching GATSO camera
Beep 2 ~ WARNING – approaching GATSO camera - 30 limit
Beep 3 ~ WARNING - approaching GATSO camera – 40 limit
Beep 4 ~ WARNING - approaching GATSO camera – 50 limit
Beep 5 ~ WARNING - approaching GATSO camera – 60 limit

Bell 1 ~ WARNING – approaching GATSO camera
Bell 2 ~ WARNING – approaching GATSO camera – 30 limit
Bell 3 ~ WARNING – approaching GATSO camera – 40 limit

Boing ~ WARNING – approaching GATSO camera – 50 limit
Bugle ~ WARNING – approaching GATSO camera – 60 limit
Cow ~ WARNING – approaching GATSO camera – 70 limit
Cuckoo ~ WARNING – approaching red light camera

Polite 1 ~ WARNING – approaching SPECS camera zone
Polite 2 ~ WARNING – approaching temporary camera
Polite 3 ~ credits

If you fancy testing this out, I’ve also produced updated files for the following:

Palm v 4.300 (2650)
Palm v 4.400 (2840)
Palm v 4.420 (2869)
Palm v 5.000 (4890)

GO v 4.300 (2830)
GO v 4.400 (2843)
GO v 4.420 (2852)
GO v 5.000 (4010)
GO v 5.100 (5158)

PPC v 4.400 (2850)
PPC v 5.000 (4890) my version

If you want to test this out, PM me with your e-mail address (indicating which model/version/build) and I'll send you an updated data.chk file

Once I know all versions work I can maybe look at producing bespoke solutions

Regards
chicago

chicago · Occasional Visitor Joined: Jun 13, 2005 Posts: 4

Whoops!!

OK so I'm crap at cut and paste. Here's what the Bells and boings should have been:

Bell 1 ~ WARNING – approaching mobile camera
Bell 2 ~ WARNING – approaching mobile camera – 30 limit
Bell 3 ~ WARNING – approaching mobile camera – 40 limit

Boing ~ WARNING – approaching mobile camera – 50 limit
Bugle ~ WARNING – approaching mobile camera – 60 limit
Cow ~ WARNING – approaching mobile camera – 70 limit

chicago

soweezy · Posted: Mon Jun 13, 2005 1:19 pm Post subject:

has anyone worked out safe distances to set for these alerts ?

I prefered checkpoint's "time till POI", distance to is a little harder to work out, especially for mobile cameras... just how close do you have to be to be zapped ?
_________________
SW

Garmin Zumo 390LM

W90BHP · Posted: Mon Jun 13, 2005 1:49 pm Post subject:

Work on the assumption that if you can see it, it can see you ;)

This logic fails for GATSOs that photograph you from behind - in that case you just have to remember you have seen it ;)

Martin
_________________
LG G4: Android 6 : Viewranger : CoPilot : Waze
TomTom Go 730T : Traffic subscription long expired
Nokia E61 : Nokia GPS : TomTom Navigator 6 : Retired from duty
iPAQ 3970 : Navman Sleeve : CoPilot 4 : Somewhere in the loft

Privateer · Posted: Mon Jun 13, 2005 3:02 pm Post subject:

Mobile laser units will work accurately up to 1,000 metres, although they normally zap you at a much closer distance.

I have my fixed camera alerts set to 400 metres. I have my mobile alerts set to 1,000 metres, which is 1,093 yards, or 0.621 miles i.e. over half a mile!

Regards,
_________________
Robert.
iPhone 6s Plus, iOS 14.0.1: iOS CamerAlert v2.0.7
TomTom GO Mobile iOS 2.3.1; TomTom (UK & ROI and Europe) iOS apps v1.29
Garmin Camper 770 LMT-D

soweezy · Posted: Mon Jun 13, 2005 4:40 pm Post subject:

Re: the script again...

tried someone elses data.chk file with TTTims Excel method

tested 3 files with it set to 11025, 16000 & 22050

it'll produces a new data file but when I copy that file to the PPC and start TT it still locks up Confused

how the hell are you lot making these files and getting them to work ? Rolling Eyes

_________________
SW

Garmin Zumo 390LM

lbendlin · Posted: Mon Jun 13, 2005 7:41 pm Post subject:

soweezy · Posted: Mon Jun 13, 2005 9:15 pm Post subject:

the data.chk files work in their original format, it's only when I create a modified version using the Excel script that TTN stops working

I'm using TTN 5 for PPC build 4890 and have tried 2 other data.chk files for my build with the same result, they work unmodified but don't when modified
_________________
SW

Garmin Zumo 390LM

MEBINI · Occasional Visitor Joined: Jun 14, 2005 Posts: 4

Hello, I have a GPS-BT but don´t work in TomTom 5 and i need to say how can i reprograming this GPS whit sirf demo, i think it is modefied the protocol, Thank you.

jpfrost · Occasional Visitor Joined: Mar 02, 2004 Posts: 20

I have copied the new data.chk file to my PPC and the only spoken warning i recieve is "mobile" for all the camera types - any ideas?

Jim-Bob · Posted: Wed Jun 15, 2005 12:16 pm Post subject:

Yeah. You need to go into warn when near POI and change the warning sounds to type each one is.

ScaredyCat · Regular Visitor Joined: Mar 09, 2005 Posts: 98

Since I don't use Excel, and there seemed to be a lot of folks having problems with useing the original Macro I've stuffed it into a nice lil app.

http://www.automated.it/ttg-poipatcher.html

Enjoy

SC

lbendlin · Posted: Sat Jun 18, 2005 6:40 pm Post subject:

Good stuff.

Just one remark - my code does not require selection of the data.chk version - you should be able to use any version .
_________________
Lutz

Report Map Errors here:
TomTom/TeleAtlas NAVTEQ

ScaredyCat · Regular Visitor Joined: Mar 09, 2005 Posts: 98

lbendlin · Posted: Sat Jun 18, 2005 7:56 pm Post subject:

Sorry I was not clear enough. It is very important to select the right build, but that is already guaranteed by the user when they specify the source file. Hence no need for the radio boxes.

The second bank is required for TTM.
_________________
Lutz

Report Map Errors here:
TomTom/TeleAtlas NAVTEQ

	PocketGPS
	Web