Thread: iGO Speedcam (DISCUSSION)

Dear teacher AF, sorry for the question, but I don’t understand why on section radars the closure must have a speed of 5 km, isn’t it enough to just close the section?.


I ask you this question because when I test a route in Spain with section speed cameras, in some "very few" it shows "section speed camera start." This happens with all the databases I have tested. Also, another question: with the old iGo Primo WinCE 9.6.5.306142 from June 2013, the initial section is correct, but the closing sometimes works fine, and other times it stays with the indication of section start at 5 km.

Hi, - 5 km/h is the signal for closing the average speed section.

PS If the speed on the screen is 5 km/h, then the section is closed. but!!! iGo Primo WinCE 9.6.5.306142, June 2013, knows nothing about 5 km/h and starts a new section at 5 km/h. It only works where conditions are created.

Friend, you responded while I was editing my post. (What a response speed!) And taking advantage of this new post, when the section doesn't close and the old Igo Primo gets stuck at a speed of 5km, should any entry in the sys. be modified? Although as I have told you before, in my road tests sometimes it works well and other times it keeps sounding the initial 5 km section.

I am only referring to some modification of the file "sys.txt", so that the closure is correct.

If the speed on the screen is 5 km/h, it means that the average speed section is over. The easiest way is to tap on the screen - the navigator icon and it closes.
PS
iGo Primo WinCE 9.6 - these or others are on android. At the peak of their activity, these programs had no problems closing the average speed section. It worked like this, opened and closed spc files, but now they are gone. And the spc files were updated 4 times a year. Who will undertake to implement the closure of medium-speed sections in the old programs. New programs 64 bit now.

Hi,
If you do not have this entry in sys:

use_road_speedlimit=1

For each type of notification. You will not be able to use speedcam_iTruck.txt or speedcam_Truck.txt . I wonder who should have answered this question, because it's not really addressed to me.

Originally Posted by pacodelgps

Good morning community,....

[Only registered and activated users can see links. ]

You are right AF, I don't have that entry in sys.txt, I have added it and will try it.
I didn't know anything about that entry, I was unaware of its usefulness.

Edit:

Everything is correct on Android and simulation with Lockito. I haven't deleted the 'save' folder and it has worked. Tonight I will try it with Wince and comment.

The problem in Wince has been solved, now it notifies perfectly.

Сoding and truck application

Lately, POI and KML files have practically replaced certain speedcam alerts, such as height limits, width limits, weight control, and other specific alerts needed only for trucks. This makes it possible to apply iTruck in VB coding—just like in the default pongo skin across all versions. I plan to release another version, VB iTruck, which will differ from NC iTruck as it won't include Weight Control and Dimension Limits. VB iTruck will alert about rear-facing radars. I think this is the right decision and code unification; this way, one standard code can be used for all vehicle types, both trucks and passenger cars.