Hi everyone.

I now have TTS installed on my car unit which is running Primo 2.0, I did have the speed cameras working but after the installation of TTS they no longer appear. The speedcam text file is there and the 2 other files are created but no speed cameras are on the map.

Any ideas?

Thanks
Dan.

The installation of TTS voices should have no bearing on speed cameras. Maybe something else happened along the way.
Make sure (after a satellite lock) that the warning is enabled in settings. Also be aware that speed cameras may not show up (icon or warning) while in demo or simulation mode--only when outside and driving.

YT

There's an area that fills up SYS.TXT for speed camera settings, an example being:

[speedcam_category:0]
activated_min_speech_repeat_delay=-1
activated_speech="Attention. Fixed camera"
activated_spoken_type=speech
approach_beep_sound="!alert1"
approach_beep_spoken_type=none
overspeed_spoken_type=speech
warn_distances="150:2000,140:1800,130:1500,120:1400,110:1300,100:1200,90:1100,80:1000,60:700,50:600,40:500"

and also a section in system.ini:

[warning]
speedcam_warning="1"
speedlimit_warning="1"
speedlimit_warning_visual="1"
speedlimit_warning_voice="0"
speedwarn_alt_tolerance="100"
speedwarn_tolerance="100"

Does Primo need both?

Technically, nothing is needed in sys.txt for speedcameras in Primo. But it makes some people feel better to put a whole bunch of stuff there. Probably does no harm, but much of it may just be repeating default settings anyway...or settings already set within the program options. There are exceptions..such as customized warn_distances, if desired.
Anything in system.ini is dynamic and reflects the settings within the program, skin, settings that Primo itself has discovered for the hardware, some defaults from data.zip, and some settings from sys.txt.
System.ini should rarely or never be edited manually, since it IS dynamic, and a restart will sometimes revert the settings to what is set elsewhere anyway (unless the file is set to Read Only which is usually not a good thing).

Yurbuh Tuggly wrote:Technically, nothing is needed in sys.txt for speedcameras in Primo. But it makes some people feel better to put a whole bunch of stuff there. Probably does no harm, but much of it may just be repeating default settings anyway...or settings already set within the program options. There are exceptions..such as customized warn_distances, if desired.
Anything in system.ini is dynamic and reflects the settings within the program, skin, settings that Primo itself has discovered for the hardware, some defaults from data.zip, and some settings from sys.txt.
System.ini should rarely or never be edited manually, since it IS dynamic, and a restart will sometimes revert the settings to what is set elsewhere anyway (unless the file is set to Read Only which is usually not a good thing).

So are you saying I could further reduce the content of my SYS.TXT file as follows:-

Before:

[speedcam_category:0]
activated_min_speech_repeat_delay=-1
activated_speech="Attention. Fixed camera"
activated_spoken_type=speech
approach_beep_sound="!alert1"
approach_beep_spoken_type=none
overspeed_spoken_type=speech
warn_distances="150:2000,140:1800,130:1500,120:140 0,110:1300,100:1200,90:1100,80:1000,60:700,50:600, 40:500"

After

[speedcam_category:0]
activated_speech="Attention. Fixed camera"

And I would still get a spoken TTS warning about approaching a speedcam?

By the way am I right to assume that you can put any text in.

How does the system categories speedcams. I get mine for a site call PocketGPSWorld which issues regular updates. Pop the download into the correct primo folder and the primo files get generated at start up.

If you think your sys.txt is too big (a big one may affect startup speed, etc), you can certainly try trimming it down step by step, and as long as Primo is still doing what you want, then you did not need that entry! Or change the *_speech= *** to whatever you want and see what happens. Maybe nothing, which would mean the entry is ignored.

archercj wrote:How does the system categories speedcams.

Categories have changed between iGo8, Primo 1.1, and Primo 1.2/2.0.
If you use one that is not specifically up to date for the latest Primo, the worst that would happen is, for example, a TTS voice may say "Red Light Camera Ahead" when it might actually be a Section Camera or some other type, but you would still get a warning alert.

The speedcam file has a syntax as follows:-

X Y Type Speed DirType Direction
-2.10271 53.42484 3 30 1 242

Does the 'Type' field correspond to the '[speedcam_category:0]' in the sys.txt file

If so I only need about 4 categories and can change the spoken text accordingly

archercj wrote:X Y Type Speed DirType Direction
-2.10271 53.42484 [color="#FF0000"]3[/color] 30 1 242

Does the 'Type' field correspond to the '[speedcam_category:0]' in the sys.txt file

[color="#FF0000"]Yes.[/color]

X = longitude
Y = latitude
TYPE (iGo8) = type of speed camera ( 1 - fixed speed camera locations; 2 - combined red light and speed cameras; 3 - fixed red light camera locations; 4 - section camera positions; 5 - lasers, hand-held radars and other mobile speed camera locations; 6 - railway crossing; 7 - not constant mobile locations)
SPEED = speed limit in km/h
DIRTYPE = type of direction of the speedcam (0-all directions; 1-one direction; 2-both directions)
DIRECTION = direction in degrees (0-North; 90-East)

Here are the (newer) Categories for Primo:
1) Speed camera (type 1)
2) Built-In (permanent) speed camera (type 2)
3) Red light camera (type 3)
4) Average (Section) speed camera (type 4)
5) Mobile speed camera (type 5)
6) Railway junction (type 6)
7) Camera bus lane (Type 7)
8 ) Zone of high accident risk (type 8)
9) School zone (type 9)
10) Poe City (type 10)
11) Camera red signaling. (Type 11)
12) Toll booth (type 12)
13) Hospital, ambulance (type 13)
14) Fire station (type 14)
15) Congestion Charge Zone (Type 15)
31) Danger zone (type 31)