View previous topic :: View next topic |
Author |
Message |
Kremmen Pocket GPS Verifier
Joined: Mar 03, 2006 Posts: 7045 Location: Reading
|
Posted: Sun Dec 08, 2013 7:18 am Post subject: |
|
|
... or just put a "1" in the appropriate screen field :D
I think step 1 is I need to understand the Garmin logic. If I can get away just writing out the # line and it still produces overspeed warnings the I think it's job done ?
The current theory is, based on older Garmins and using my settings:
At 14 seconds away produce a camera warning.
If at 6 seconds away you are over the limit produce another warning.
Based on what you said about mobiles I want to investigate this as even with just one mobile warning intended I did used to get multiple warnings.
I should have some time next week. What I want to look at first is the distance between mobiles at the Target Roundabout because it used to go crazy there. I used to get up to 4 warnings back to back. [/list][/list] _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
|
|
Back to top |
|
|
m-a-r-k Regular Visitor
Joined: Jun 17, 2008 Posts: 80 Location: Highland
|
Posted: Sun Dec 08, 2013 4:27 pm Post subject: |
|
|
Kremmen wrote: | ... or just put a "1" in the appropriate screen field :D |
I could do that as well
Quote: | I think step 1 is I need to understand the Garmin logic. If I can get away just writing out the # line and it still produces overspeed warnings the I think it's job done ? |
Erm, I don't think so. It does produce overspeed warnings with just the # lines - at least on my old Garmin 350. That's the problem.
You only produce # lines when OverSpeed setting is zero, you produce # and @ lines when non-zero.
What I'm going to test should show if you need to output @ lines when OverSpeed is zero.
Quote: | I should have some time next week. What I want to look at first is the distance between mobiles at the Target Roundabout because it used to go crazy there. I used to get up to 4 warnings back to back. |
OK, no problem.
I'll get back to you on my test results. _________________ Mark B
Garmin nüvi 350
SW V6.20, GPS SW V3.00
City Navigator Europe NT 2018.10 |
|
Back to top |
|
|
Kremmen Pocket GPS Verifier
Joined: Mar 03, 2006 Posts: 7045 Location: Reading
|
Posted: Mon Dec 09, 2013 8:00 am Post subject: |
|
|
Thanks
If I get the time today I intend to load the latest database. I'll just run with the approach warning # set and see what happens.
If as you say, and you've got to be right as you've tested it, then the # line is all that is required and if that produces overspeeds then I'm stumped.
The camera I use for overspeed testing is normally OK on a Mon/Tue/Wed as 'everybody' does 60+ down this 50mph dual carriageway on the opposite direction to the camera.
However, sods law usually dictates that when I want to do some testing I'll get stuck behind someone doing 50
When I introduced the separate overspeed.wav it took 2 weeks before I could get above 50.
later :D _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
|
|
Back to top |
|
|
dales Frequent Visitor
Joined: May 04, 2008 Posts: 752 Location: Knaresborough, North Yorkshire.
|
Posted: Mon Dec 09, 2013 3:10 pm Post subject: |
|
|
I think the beauty of a separate overspeed.wav is that you can use a separate audio warning which contains some added 'bite' eg if you have overlooked the first warning for a gatso or redspeed camera. Also, its timing can be set to the user's preference.
If the Garmin is unwantedly repeating the first (proximity) alert whilst over the limit, try altering the settings eg under Tools...Settings...Proximity Points...Proximity Alerts...Change...Audio... You can set Single Tone or Continuous Tone on some Garmins.
Dales _________________ nuvi 2599LMT-D, oregon 700, basecamp, memory-map. |
|
Back to top |
|
|
Kremmen Pocket GPS Verifier
Joined: Mar 03, 2006 Posts: 7045 Location: Reading
|
Posted: Tue Dec 10, 2013 7:24 am Post subject: |
|
|
Stage 1 complete, Garmin is sat next to me on the desk :D
Stage 2 complete, new file loaded.
During code checking I found a bug that I've now sorted, but not released yet. May as well wait until testing is complete.
The bug is the way I'm handing Redlight cameras during the Overspeed separation. Some of them don't have a # or a @ and I'm writing them out to the wrong file or not writing them at all depending on the Overspeed selection.
I've now got just the # files on mine and I'll see how it goes with speed reminders. I know I won't get my bespoke Overspeed.wav cutting in as I now have no @ files.
The way the Overspeed works is the last process scans all the files and removes all the lines with a @ in to a separate single file called Overspeed .gpx which of course links to the overspeed.wav
Now just need to be able to overdo it on my test camera. _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
|
|
Back to top |
|
|
m-a-r-k Regular Visitor
Joined: Jun 17, 2008 Posts: 80 Location: Highland
|
Posted: Tue Dec 10, 2013 9:20 pm Post subject: |
|
|
More tests Wednesday and I'll confirm results. Problem I'm having is the same as yours - not being able to get over speed!
So far I've confirmed several things, I'm sure you're aware of them but doesn't help to clarify.
1. If there are no @ lines in the GPX file there is an approach warning and then 3 or 4 OverSpeed warnings, the last of which is often timed just as you've gone past the camera.
The Garmin is obviously putting in the OverSpeed warnings itself.
2. If there are @ lines you again get repeated OverSpeed warnings as expected. There doesn't really appear much difference between 1 & 2 with Approach set to 30 seconds.
3. If there are @ lines with values of 0 or 1 as the Proximity value then so far I've had 1 Approach warning and 1 OverSpeed warning.
I'm going to test this again but it is a VAST improvement on the 3 or 4 I was getting in 1.
Edited above to remove my misconceptions and added conclusion:
So what does all this mean for me?
A. Leaving out the @ lines when I set OverSpeed to zero doesn't work - I get multiple warnings when I should (in theory) get none. The code in CSV to GPX Converter may need to be amended here.
B. On my Garmin I'm not able to remove Over Speed warnings altogether and this also seems to be the conclusion elsewhere on the net.
C. Setting an OverSpeed value of 1 is the best compromise to reduce the Over Speed warnings and using the Overspeed sound file will also improve the situation. _________________ Mark B
Garmin nüvi 350
SW V6.20, GPS SW V3.00
City Navigator Europe NT 2018.10
Last edited by m-a-r-k on Thu Dec 12, 2013 1:57 pm; edited 1 time in total |
|
Back to top |
|
|
Kremmen Pocket GPS Verifier
Joined: Mar 03, 2006 Posts: 7045 Location: Reading
|
Posted: Wed Dec 11, 2013 7:38 am Post subject: |
|
|
Thanks
I'm now running with just # in the files. As a result, like you, I'm just getting a single warning when I'm my set distance from the camera (14 secs). So far so good and all cameras reported.
As above, sod's law kicked in yesterday and my one safe overspeed camera didn't get tested because I got stuck just at under 50 mph so no overspeed warning. I'm going to have to wait for that one. I'm not back in the office and therefore not passing that camera till Xmas eve so don't hold your breath
One bit of information for your No 1 is that Garmin stack up the warnings one behind each other so if it decides to issue 4 warnings then it can keep on going well past the camera. I think to be fair to Garmin if you are over the limit then giving repeated warnings is not to be scorned at. _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
|
|
Back to top |
|
|
M8TJT The Other Tired Old Man
Joined: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
|
Posted: Wed Dec 11, 2013 9:36 am Post subject: |
|
|
Kremmen wrote: | As above, sod's law kicked in yesterday and my one safe overspeed camera didn't get tested because I got stuck just at under 50 mph so no overspeed warning. I'm going to have to wait for that one. | As you are changing all sorts of parameters for the cameras, why don't you change the trap speed for your test cam down from 50MPH to 30MPH for testing purposes then you don't have to exceed the limit to trigger it? You wouldn't have to rely on a clear road then. Or even insert a slow 'test' cam local to you so you don't have to drive to the office to pass a cam? |
|
Back to top |
|
|
Kremmen Pocket GPS Verifier
Joined: Mar 03, 2006 Posts: 7045 Location: Reading
|
Posted: Wed Dec 11, 2013 2:45 pm Post subject: |
|
|
M8TJT wrote: | Kremmen wrote: | As above, sod's law kicked in yesterday and my one safe overspeed camera didn't get tested because I got stuck just at under 50 mph so no overspeed warning. I'm going to have to wait for that one. | As you are changing all sorts of parameters for the cameras, why don't you change the trap speed for your test cam down from 50MPH to 30MPH for testing purposes then you don't have to exceed the limit to trigger it? You wouldn't have to rely on a clear road then. Or even insert a slow 'test' cam local to you so you don't have to drive to the office to pass a cam? |
I could also use the GPS simulation mode to save driving.
Why didn't I think of that (answers on a postcard) _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
|
|
Back to top |
|
|
M8TJT The Other Tired Old Man
Joined: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
|
Posted: Wed Dec 11, 2013 2:58 pm Post subject: |
|
|
I thought of that too, but didn't know if Garmins alerted on speed cams in sim mode. iGO doesn't |
|
Back to top |
|
|
Kremmen Pocket GPS Verifier
Joined: Mar 03, 2006 Posts: 7045 Location: Reading
|
Posted: Wed Dec 11, 2013 4:24 pm Post subject: |
|
|
I'll let you know next week ................ _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
|
|
Back to top |
|
|
Kremmen Pocket GPS Verifier
Joined: Mar 03, 2006 Posts: 7045 Location: Reading
|
Posted: Thu Dec 12, 2013 11:22 am Post subject: |
|
|
Update
I managed to get a clear run yesterday. Unfortunately, and going against the reports above I had no second warnings even though I was doing 55+ approaching and going past a 50 camera. All I got was a single approach notification at 14 seconds.
With my previous # and @ lines I did get overspeed warnings, usually 2 of them.
I'm stumped _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
|
|
Back to top |
|
|
m-a-r-k Regular Visitor
Joined: Jun 17, 2008 Posts: 80 Location: Highland
|
Posted: Thu Dec 12, 2013 2:00 pm Post subject: |
|
|
What settings did you use to get no warnings - OverSpeed set to zero?
I've edited and amended the post I made above with my test results and conclusion. _________________ Mark B
Garmin nüvi 350
SW V6.20, GPS SW V3.00
City Navigator Europe NT 2018.10 |
|
Back to top |
|
|
Kremmen Pocket GPS Verifier
Joined: Mar 03, 2006 Posts: 7045 Location: Reading
|
Posted: Fri Dec 13, 2013 8:32 am Post subject: |
|
|
Yes I had Overspeed throughout set to zero. All I had was 14 seconds in Approach for all.
On first testing it does seem that a # marker in the GPX file will only produce a single one off warning at the proximity set.
Therefore it's the @ that is performing the continual overspeed warnings.
What I don't understand is that I cannot reproduce your No 1 above. With only a # I only get a single approach warning.
More testing needed .......
During this I'm attempting to get a DropBox shared folder going so you can get test versions. _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
|
|
Back to top |
|
|
m-a-r-k Regular Visitor
Joined: Jun 17, 2008 Posts: 80 Location: Highland
|
Posted: Fri Dec 13, 2013 11:31 am Post subject: |
|
|
This could simply be a difference in Garmin models and firmware.
Or just the lower approach setting of 14 doesn't give enough time for OverSpeed warnings to kick in? I wonder if you could test with 30s Approach time.
What is your setting on the device for Settings/Proximity Points/Alerts/Audio: Single Tone or Continuous?
I've downloaded your file, I won't be able to do much until next week however.
Do you have a separate OverSpeed sound file, in other words the OverSpeed GPX file?
Lots of questions
I'll get back. _________________ Mark B
Garmin nüvi 350
SW V6.20, GPS SW V3.00
City Navigator Europe NT 2018.10 |
|
Back to top |
|
|
|
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!
|
|
Back to top |
|
|
|