Avergae speed cams sticking

briwy · Lifetime Member Joined: Aug 04, 2004 Posts: 173

I think this has been mentioned before but I cant find it.

Camera warnings all working fine except the average speed cameras stick and wont go away for ages after passing them. Obviously this is very annoying with the beep constantly sounding.
It seems that they keep going until another camera position comes up.

Is there a way to cure this please??

Border_Collie · Posted: Thu Sep 04, 2008 1:21 am Post subject:

This is because the cameras come in threes. Tap a couple of times on the on screen warning and it should stop.
_________________
Formerly known as Lost_Property
And NO that's NOT me in the Avatar.

GerryC · Posted: Thu Sep 04, 2008 6:21 pm Post subject:

Isn't this because it can warn over the entire range of the average speed trap? It's a reminder that you are still in the capture zone as it isn't as important exactly what speed you are doing passing the camera - it's the speed between them that matters.

The last Specs camera in the line should be marked "end" which would switch off the warning. There can be any number of cameras in the line.
_________________
Gerry
TomTom730T
Cameralert for Android
Brodit ProClip mount

M8TJT · Posted: Thu Sep 04, 2008 6:41 pm Post subject:

The IGO/MIO software seems to assume that SPECS come in pairs. My Mio works fine if there are only two cams, switching off the average speed calculation at the second. If there are three cams, not only does the av speed not get calculated between two and three, but three switches it back into the av speed calc mode and there is no 'second' cam to switch it off. As the OP says, tap the alert icon a few times to get rid of it.
Pity realy that it has not been implemented better.
Hey Ho!!

mxmaciek · Posted: Fri Sep 05, 2008 10:35 am Post subject:

The reason is that for another countires average speed cams are in pairs only...

MaFt · Posted: Fri Sep 05, 2008 2:21 pm Post subject:

but other countries drive on the right and use kph yet the uk users still get to drive on the left and in mph... so why not the specs cameras? they are aware of it as i've mentioned it to them numerous times as well as my thoughts on how it could be implemented!

MaFt

neil01 · Posted: Fri Sep 05, 2008 5:13 pm Post subject:

If the cameras are marked as last, first, end or whatever, and this information is used by the application. I see a fundemantal flaw.

It assumes that there are no road junctions between the first and last cameras where people can leave or enter out of sequence.

Perhaps the routing should be amended so that you do not enter an average speed camera area at the 'wrong' position! (seriously though - as a software tester, I came accross even more stupid solutions to software problems)

M8TJT · Posted: Fri Sep 05, 2008 5:44 pm Post subject:

mxmaciek · Posted: Fri Sep 05, 2008 8:22 pm Post subject:

MaFt · Posted: Fri Sep 05, 2008 10:24 pm Post subject:

Sallyann · Lifetime Member Joined: Jun 23, 2006 Posts: 768

The long SPECS section on the A14 west of Cambridge has several sets of cameras. Between them are various junctions, laybys, petrol stations, services etc. I don't see how any GPS unit can have the logic to sort that lot out and give appropriate alarms.

As SPECS get extended to cover increasingly long sections of road, I think it will become impossible to track them all correctly.

That's why I convert SPECS cameras to conventional ones.

neil01 · Posted: Sun Sep 07, 2008 12:28 pm Post subject:

Sallyann · Lifetime Member Joined: Jun 23, 2006 Posts: 768

The whole business of monitoring SPECS cameras is fraught with difficulty.

Looking at the A14 section I mentioned before, there are six camera positions in each direction. The PGPSW database lists these as three separate sections - start-finish, start-finish, start-finish.

How do we know that they can't check the time elapsed between say the first and last, or second and fifth cameras?

For example when travelling north, #31962 is shown as the finish of one section and #29765 a mile further north is shown as the start of the next section. According to this there is no speed check between these two points, but I for one wouldn't risk it!

Perhaps MaFt could comment?

Sal

MaFt · Posted: Sun Sep 07, 2008 6:02 pm Post subject:

i theory they can calculate average speed between any and all of the points eg between 1 and 2, 1 and 4, 3 and 6... etc etc

so the 1st should be set at start, the last (6th) as end and the others as middle. at the moment though only drivesmart uses this start/end data but we may as well correct it. we've always logged directional data and it's only recently it has come into mainstream use!

MaFt

mxmaciek · Posted: Sun Sep 07, 2008 8:09 pm Post subject:

MaFt, I think that alghoritm should be slightly different:
iGo should NOT calculate the average between, instead, it should calculate and display average after 1st one. The stop of the calculation and/or finish of warning should be something like: crossed av speed cam, no next average speed on the drive direction within ... yards.
But - I think - there is nothing what you can do with the camera database, it's in the iGo's core somewhere.
Or, all junction-leave, or last in the set shoud be stopping the warning.
Unfortunately (for that case), there is no speed cam on each of the exits (i.e. M1 North leaving on 26...) Confused

	PocketGPS
	Web