Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 8 of 8
  1. #1
    Member
    Join Date
    Dec 2015
    Location
    Perth
    Posts
    15
    Rep Power
    0

    Default Repeated warnings and sys.txt editing.

    I seldom post because a search usually reveals what I am looking for but this time I have searched until my head hurts without any luck so I will have to ask.
    I have a Chinese car head unit with 10 inch screen running android that arrived with primo installed. I have it working almost as I want with these exceptions. I have enabled TTS using the google engine, street names work OK, my issue is with camera and school zone warnings, I cannot make sense of the sys.txt regarding repeated warnings. The spoken messages come from sys.txt as I can edit them and it reads what I have written.

    Before the speedcam cat section I have this:

    [warning]
    speedcam_enabled=1
    is_spoken=1
    speedcam_warning=1

    warn_distances="120:1000,90:690,70:690,50:690,30:540"
    ;skin_audio_path="speedcam_lt"
    ;skin_audio_path="speedcam_ru"
    speedcam_continuous_approach_beep_when_tonal=0
    ;overspeed_min_speech_repeat_delay=-1 ;do not repeat
    ;overspeed_min_tone_repeat_delay=-1 ;do not repeat

    Ignoring the commented out lines some of which point to audio files in Russian and Lithuanian I think?

    1: Does the general "warn_distances" override anything written in each speedcam category?

    This is my school zone section showing the times disabled temporarily (thanks to previous post) to test:

    ; S P E E D C A M - C A T : 9
    [speedcam_category:9]
    ;speedcam_snap_distance=50

    activated_spoken_type=speech
    activated_speech="School Zone Ahead"

    ;approach_beep_distances=150
    ;approach_beep_spoken_type=speech
    ;approach_beep_speech="School Zone Approaching"
    ;overspeed_spoken_type=none

    min_frc=5
    use_road_speedlimit=0

    ;warning_time_intervals_awa="Mo-Fr|7:30-9:00,Mo-Fr|14:30-16:00"

    so Question 2: WTF is speedcam_snap_distance
    3: Why do I get repeated "school zone" warnings on approach when the approach beep distance etc shouldn't be affecting anything?
    4: WTF is "min_frc=5"

    Thank you for taking the time to read this and apologies if the answers are given before but I could not find them.

    Edit, I have found an example sys.txt on here that has each speedcam category with it's own warning speeds and distances, and also after re-reading other posts I now seem to think that the approach_beep_distance is the distance after the warning that repeat announcements are made.
    If I am correct then to prevent repeat speech I need to increase this figure. I had been decreasing it?
    Last edited by crabber; 10th December 2017 at 08:20 AM.

  2.    Advertissements


  3. #2
    Master
    Join Date
    Apr 2014
    Location
    Taihape
    Posts
    175
    Rep Power
    136

    Default

    To answer some of your questions:
    1: it is my understanding the commands in each speedcam category override the ones in the [warning] section. I'm not certain about this so some experiment is called for.
    2. No idea what speedcam_snap_distance is but everything seems to work fine without it.
    3. You are correct, approach_beep_distances is the distance(s) at which the warning is repeated. Setting this to -1 may turn the repeat function off but you will need to test this.
    4. min_frc is a mystery to me, I have also seen it set to -1 and removing it altogether seems to make no difference.

    If you test any of these things please post your results.

    Good luck with your search

    Sent from my SM-A310Y using Tapatalk
    Last edited by Boki; 10th December 2017 at 08:46 PM. Reason: Removed unnecessary quote...

  4. #3
    Member
    Join Date
    Dec 2015
    Location
    Perth
    Posts
    15
    Rep Power
    0

    Default

    Thanks for your reply. I will try various settings in sys.txt to see what happens.
    Am I correct in thinking that the warn distance is triggered by (in my case) the warning distance and speed before the speedcam category entries, and the repeat distance is set by the approach beep distances? Because if so my first mistake was to set the latter figure lower, I thought this would cause a repeat at that distance, not every time that distance was passed from the warn point. I hope I have explained properly.

    It seems a good idea to make the sys.txt as simple as possible, so I will try removing lines completely to see what difference it makes. I hope that I am right in thinking that I have entries that only apply to a non TTS set up?
    Lastly I have no idea what the "skin" entries are for, something like this:
    skin_first_sound="Accident_Zone"
    skin_speed_sound_delay=140
    skin_repeat_sound="Accident_Zone"
    skin_repeat_distance=150
    skin_off_sound="speedcam_off"

    An explanation of this would be really helpful if anyone knows.

  5. #4
    Master
    Join Date
    Apr 2014
    Location
    Taihape
    Posts
    175
    Rep Power
    136

    Default

    You are correct; the warning distance is triggered by the "warn_distances=" command, and the repeat distance setting works exactly as you describe in your second post. You can have an overall setting in the [warning] section of sys.txt or you can have individual settings for each speedcam type in separate [speedcam_category:xx] sections.

    Each pair of numbers in the "
    warn_distances=" string (in your case "120:1000,90:690,70:690,50:690,30:540") is actual road speed to the left of the colon and warning distance to the right,

    How it works:
    The first setting in your string is 30:540 - because 30 is the lowest speed listed, you will not receive a warning when your actual road speed is less than 30 km/h.
    At 30 km/h or faster, the 30:540 rule takes effect and you will get the first warning 540 metres from the recorded position of the hazard.
    When your road speed increase to 50 or more the 50:690 rule takes effect and you now get the first warning 690 m before the hazard.
    The next two rules in your example, 70:690 and 90:690, have no effect because they specify the same warning distance as the 50:690
    Finally at speeds of 120 km/h or greater, the first warning will be 1000 m from the hazard.
    I have no idea if it is important in which order the rules are written , but in every example I have seen the highest speed is always written first

    I'm finding it difficult to write all this down clearly so i hope what i have said makes some sense to you.

    Just a note about testing; be aware that one or more of the .ini files within Primo may also contain some of these settings. If you don't override these in sys.txt they will continue to be applied so its worth extracting all the .ini files from data.zip to see whats lurking in them. Usual offender is data.zip\project_config\igo9.ini but there can be others.

    I too am still interested to know the use of "speedcam_snap_distance", "min_frc", and the assorted "skin_..." commands so if any other users reading this can clarify, please feel free to contribute your knowledge.
    Last edited by k1w1_123; 11th December 2017 at 01:52 AM. Reason: spelling and grammar

  6. #5
    Member
    Join Date
    Dec 2015
    Location
    Perth
    Posts
    15
    Rep Power
    0

    Default

    This is really useful information for me thanks again. I did not realise that a warning would not be triggered at any speed below the lowest figure, having this speed set high may not be a good idea for something like a red light camera, not that I am suggesting driving through lights at red!
    I wonder if the person that wrote my original warning_distances string understood what they were writing as surely the 70 and 90 speeds are not necessary as you describe that anything over 50 up to the higher figure is the same distance.
    Anyway I will look for other .ini files and report back once I have had time to test. Meanwhile I second your request for someone to enlighten me about the other questions.

  7. #6
    Important User Repeated warnings and sys.txt editing.
    Repeated warnings and sys.txt editing.Repeated warnings and sys.txt editing.Repeated warnings and sys.txt editing.Repeated warnings and sys.txt editing.
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,891
    Rep Power
    1364

    Default

    Quote Originally Posted by crabber View Post
    I wonder if the person that wrote my original warning_distances string understood what they were writing as surely the 70 and 90 speeds are not necessary as you describe that anything over 50 up to the higher figure is the same distance.
    The majority of settings are copied (without knowing what it does). Most people don't need more than one speed:distance setting. Having more than one just makes its hard to debug and understand. The format was created to allow multiple activations of an alert. Read [Only registered and activated users can see links. ]
    Last edited by osiris4isis; 11th December 2017 at 03:37 AM.
    Do not PM me with questions. That's what a forum is for.

  8. #7
    Member
    Join Date
    Dec 2015
    Location
    Perth
    Posts
    15
    Rep Power
    0

    Default

    Just a quick update to say that I haven't given up on this, I am still trying to understand all the settings. Thanks for the link above and yes I had read it (more than once) and although it contains much useful information it doesn't answer my specific questions about such things as snap distance and min frc. Unless I missed them!

    Because these alerts cannot be tested in demo mode I have installed a similar version on a Samsung Galaxy S6 running android version 7.0 This came from post 197 in the "everything in threes is perfect" thread and I was astonished how easy it was for a novice like me to install. Everything worked out of the box.
    I need the exercise so will probably experiment with the phone on my bike.

    I am trying to compare my igo9.ini and sys.txt in both units, using the same maps, poi and speedcam files. The alerts do seem to work a bit differently at different times which makes me think the units have a mind of their own. I have also noticed that the sys.txt and igo9.ini files contradict each other in my setup. An example is tmc http switched off in igo9.ini and on in sys.txt the online traffic works so I assume sys.txt does override in this case?
    Each alert point can be edited to trigger in one direction, both directions or have a red circle around them so I am wondering if the settings that I don't understand have anything to do with say the diameter of this warning circle? I will post if I eventually discover anything that makes sense.
    Last edited by crabber; 14th December 2017 at 06:26 AM.

  9. #8
    Important User Repeated warnings and sys.txt editing.
    Repeated warnings and sys.txt editing.Repeated warnings and sys.txt editing.Repeated warnings and sys.txt editing.Repeated warnings and sys.txt editing.
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,891
    Rep Power
    1364

    Default

    Quote Originally Posted by k1w1_123 View Post
    I too am still interested to know the use of "speedcam_snap_distance", "min_frc", and the assorted "skin_..." commands so if any other users reading this can clarify, please feel free to contribute your knowledge.
    Answer
    Spoiler: .

    This post requires you to click the "LIKE this post" button and hit F5 to read this content.
    A value of 5 means it's restricted to 5 or greater. A value of -1 means no restriction.

    "speedcam_snap_distance" seems to be default setting of 50 (meters?); don't know what it is right off hand
    Last edited by osiris4isis; 16th December 2017 at 05:40 AM.
    Do not PM me with questions. That's what a forum is for.

 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •