Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
If you look at the commands.csv file it seems that the 'default' turn announcements are for manoeuvres to the left eg. "turn left" or "turn slightly left"
I would suspect that the system sets a flag for the turn. If the flag is set, the system changes the 'left' to 'right', then amends the announcement to suit.
The 'now turn left' does seem to work, although I have increased the 10 yds to 15 as it would announce the turn as you passed it.
Also the 'bear left' modification has proved incorrect as it is the 'left' bit which is the variable.
eg The 'turn slightly left' seems to be made up of a 'turn' and a 'slighty left' which makes it difficult to change this to 'bear left' we would get something like 'turn bear left' but it isn't working.
Hi,
- I just came home from the UK, after a few days of driving I slowly understood what was the problem with roundabouts there that I had to choose the lane by the time I entered the roundabout. That posted modification here does the trick, that's what I'll change too.
- about commands.csv: the last column which reads "turn left" is just text which is not processed. For "bear left" you have to make a new template, a copy of turn which says bear and use it in "slight_left" and "slight_right" with left and right as parameters. I'll leave the rest to you to find out
- for "turn left now" use "1" instead of "10". Lower "minsilence" if you want to hear it more, because with 3 if there wasn't at least 3 seconds of silence after the last announcement (at 100 or 50 meters), it'll be supressed.
Best regards,
Fable (of iGO if you haven't figured it out by now ;) )
Fable, I'm looking at adding the commands that drogg suggested earlier and found that the commands.cvs file has different commands for some of the turns than the commands_yd.cvs file has. E.G.
commands.cvs
,"50[X~1,near,minsilence=3]","*take","take %X %* in %dist %then1"
commands_yd.cvs
,"50[X~1,near,minsilence=3]","take %X %* in %dist %then1","turn left"
*take is the same as a previous line where *take was in the first column:
,"50[X>1,more,near]*take","TAKE %X %* IN %dist %then1","take %X %* in %dist %then1"
I don't think I really understand that . Why does the command_yd.cvs file have the 'turn left' text at the end of the lines where the command.cvs doesn't? Shpuldn't they be the same as it's only the voice that is different.
Just wondered if there was a reason for the inconsistancy. And is there any reason why some of the commands are in capital letters and other in small letters. e.g. in your example why it TAKE in capital letters?
I think I understand but could you please clarify with the following two example lines from Commands.csv.
,"500[more,set_1]*prepare_to_enter_roundabout","PREPARE_TO ENTER ROUNDABOUT IN %dist","prepare_to enter roundabout in %dist"
,"200[more,set_2]","*prepare_to_enter_roundabout","prepare_to enter roundabout in %dist"
Since the lines begin with a comma delimiter then I assume that there are four columns in total, the first being blank.
Am I also right in assuming that the fourth (last) column is just text which is not processed.
In which case the lines without comments become:
,"500[more,set_1]*prepare_to_enter_roundabout","PREPARE_TO ENTER ROUNDABOUT IN %dist",
,"200[more,set_2]","*prepare_to_enter_roundabout",
So *prepare_to_enter_roundabout holds the instruction "PREPARE_TO ENTER ROUNDABOUT IN %dist" from the previous line.
Therefore the lines would still function correctly if rewritten as:
,"500[more,set_1]","PREPARE_TO ENTER ROUNDABOUT IN %dist",
,"200[more,set_2]","PREPARE_TO ENTER ROUNDABOUT IN %dist",
And is the capitalisation important? Is this still Ok:
,"500[more,set_1]","prepare_to enter roundabout in %dist",
,"200[more,set_2]","prepare_to enter roundabout in %dist",
Have I made any incorrect assumptions along the way ?
Many thanks for the input, it is really appreciated. I think I've sorted the 'bear left' modification. Reports are its working fine.
I have created a template to cover the 'bear left' situations.
In commands_yd.csv, the template for turns is headed by the line "template turn",,, and terminated by three commas (,,,).
Ive copied the entire "template turn",,, paragraph (all lines from ["template turn",,,] to [,,,]) and changed each occurrence of 'take' and 'turn' to 'bear'. Thus it becomes "template bear",,, Then pasted this new paragraph between the lines [,,,] and ["roundabout_h",,"21",] adding this new paragraph to 'commands_yd.csv'
Then in the sections slight_left and slight_right, I've 'called' the new template.
eg "slight_left","call bear left","3",
"slight_right","call bear right","4",
If you try it and spot any problems, please let me know.
Be sure you have a 'bear.ogg' in the audio directory of the voice zip file.
I don't understand it fully yet but we're getting there. I know that 'template turn' should cover all possible turn situations, therefore 'template bear' should cover all possible bear left type situations where previously there was a 'turn slighly'. This now replaces all 'turn slightly left' announcements with 'bear left' instead. Excellent!
I agree with linknet, there are four columns. They are described at the beginning of the 'commands.csv' file.
"code","distance","vocal/iconid","text". Template instructions use column 1 and others. Announcements use 2 to 4 (column 1 is blank).
I am very impressed with iGO, its functionality, especially the level of customisation. Its all very good and can only get better.
I am slowly getting my head around how it all functions. Any additional info on formats and parameters would be most helpful.
I do have a few questions I hope you can answer...
Can lines be remmed out in 'commands.csv'?
- Anything I try seems to render the whole commands set silent.
- A comment could be put in like this: ,,,"this is a comment"
- It seems you can have blank lines in the file if you want to make it more readable.
What compression format do you use to compress the graphics?
I'll try to figure the rest out.
If you require any testing over here in the UK, I'll do what I can to assist.
Regards
Drogg _________________ If Hugo where iGO, you wouldn't be 'LOST'!
Great work drogg. I was just doing the same thing by adding an entire paragraph for the 'bear' turns but it wasn't working properly as I wasn't getting any command. I do have the bear.ogg file. I'll give it another go. Just get's a little tiring going for a drive to check if it works. Wife thinks I'm mad.
Still would like to know if the capitals letters have any significance in these commands.
Theres no need to go for a drive every time, although there is no substitute for testing in the field.
Try this...
Create a route that has a 'bear left/right' somewhere along it, but dont make the route toooo long. You could add POIs for the start and end points.
After caculation, tap 'Route' then hold down HardWare button 1 and tap 'Fly Over'. You will get a realistic demo with announcements so you can check if alls well. When you are happy with your results and things seem to work, you can then take it for a test drive to see if works well in the field.
Will test CAPITALS when I get a minute, and keep you posted.
Regards
Drogg _________________ If Hugo where iGO, you wouldn't be 'LOST'!
Had a look at your turn now announcement, keep up the good work.
However it doesn't cater for the next turn announcement where this follows closely on the original turn announcement.
The following seems to fix that and allows both "Turn Left" and "Turn Left Then Right" announcements.
(NB '~' should be a greater than sign)
"template generic",,,
,"100[then]","then %*",
,"300[then3]","then %*",
,"1000[more]","drive %dist","Drive %dist"
,"500[more,set_1]","prepare_to %* in %dist",
,"200[more,set_2]","prepare_to %* in %dist",
,"50[more,near]","in %dist %* %then", ,"10[more,near]","%* %then","turn left" ,"0[X=1,more,near]","%* %then",
,"0[more,near]","in %dist %* %then",
,"800[equal,minsilence=10,if_not_1]","prepare_to %* in %dist","Prepare to turnleft in %dist"
,"300[equal,minsilence=10,if_not_2]","prepare_to %* in %dist",
,"100[near,minsilence=3]","in %dist %* %then","prepare to turn left"
,"50[near,minsilence=3]","In %dist %* %then","turn left" ,"10[near,minsilence=1]","%* %then","turn left" ,,,
"template turn",,,
,"100[then1,X=1]","then next %*",
,"100[then1,X~1]","then %X %*",
,"100[then1,!X]","then %*",
,"100[then,X=1]","then take next %*",
,"100[then,X~1]","then take %X %*",
,"100[then]","then turn %*",
,"300[then3,X=1]","then take next %*",
,"300[then3,X~1]","then take %X %*",
,"300[then3]","then turn %*",
,"1000[more]","drive %dist","Drive %dist"
,"500[more,set_1]","prepare_to turn %* in %dist",
,"200[more,set_2]","prepare_to turn %* in %dist",
,"50[!X,more,near]","in %dist turn %* %then1",
,"50[X=1,more,near]","take next %* %then1",
,"50[X~1,more,near]","take %X %* in %dist %then1", ,"10[!X,more,near]","turn %* %then1","turn left"
,"10[X=1,more,near]","turn %* %then1","turn left"
,"10[X~1,more,near]","turn %* %then1","turn left" ,"0[!X,more,near]","in %dist turn %* %then1",
,"0[X=1,more,near]","take next %* %then1","not saying distance if close and no crossings between"
,"0[X~1,more,near]","take %X %* in %dist %then1",
,"800[equal,minsilence=10,if_not_1]","prepare_to turn %* in %dist","Prepare to turn left in %dist"
,"300[equal,minsilence=10,if_not_2]","prepare_to turn %* in %dist",
,"100[!X,near,minsilence=3]","in %dist turn %* %then1","prepare to turn left"
,"100[X=1,near,minsilence=3]","take next %* in %dist %then1","prepare to turn left"
,"100[X~1,near,minsilence=3]","take %X %* in %dist %then1","prepare to turn left"
,"50[!X,near,minsilence=3]","in %dist turn %* %then1","turn left"
,"50[X=1,near,minsilence=3]","take next %* %then1","turn left"
,"50[X~1,near,minsilence=3]","take %X %* in %dist %then1","turn left" ,"10[!X,near,minsilence=1]","turn %* %then1","turn left"
,"10[X=1,near,minsilence=1]","turn %* %then1","turn left"
,"10[X~1,near,minsilence=1]","turn %* %then1","turn left"
The additions to the original commands.csv and commands_yd.csv are shown in red.
Use the same for commands_ft but you will need to change the distances from yards (metres) to feet and miles.
The additions to the template section seem to be optional. It seems to work with or without these additions
Theres no need to go for a drive every time, although there is no substitute for testing in the field.
Try this...
Create a route that has a 'bear left/right' somewhere along it, but dont make the route toooo long. You could add POIs for the start and end points.
After caculation, tap 'Route' then hold down HardWare button 1 and tap 'Fly Over'. You will get a realistic demo with announcements so you can check if alls well. When you are happy with your results and things seem to work, you can then take it for a test drive to see if works well in the field.
Will test CAPITALS when I get a minute, and keep you posted.
Regards
Drogg
I know about the Fly Over feature but for some reason mine doesn't give the announcements - just flies over the route. There isn't a setting I have missed somewhere is there?
Posted: Today Post subject: Pocket GPS Advertising
We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
Forum FAQ
Search
Usergroups
Profile
Log in for private messages
Log in
that I had to choose the lane by the time I entered the roundabout. That posted modification here does the trick, that's what I'll change too.
. Why does the command_yd.cvs file have the 'turn left' text at the end of the lines where the command.cvs doesn't? Shpuldn't they be the same as it's only the voice that is different.
