Thread: iGO Speedcam (DISCUSSION)

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.

Hello.
I'm trying to position two radars very close together :
X,Y,TYPE,SPEED,DIRTYPE,DIRECTION
25.906520,43.756520,4,90,1,168
25.906590,43.756470,4,5,1,348

iGO Primo and iGO Luna see both locations, but iGO_NextGen_9.18.27.687519 ignores one of the locations.
If I increase the distance between the two locations (about 40 m) it's fine.
Am I doing something wrong?
Any advice is appreciated.

Spoiler: images

What you see on the screen does not matter. What is written in the speedcam.txt file is what actually counts. Also, deleting two points makes no difference for the alerts; you can just as easily create identical coordinates with different azimuths, for example:

25.906520, 43.756520, 4,90,1,168,
25.906520, 43.756520, 4,5,1,348

OSC separates these coordinates to make it easy to edit points on the map.

After the closure of BBS, the only thing that drivers in Spain are interested in is the position of seatbelt and mobile cameras (also fixed speed cameras). I have noticed that OSC also has it under the name 'Dummy'. In that category, will only those cameras be included or also others? In the tests I have done with route simulation on Android with Lockito, it works perfectly.


I meant: I wanted to say 'camera for phone control and seat belt use'

'camera for phone control and seat belt use' - Yes, that's it. And in other countries, this type of 30, for example, in Italy, corresponds to a surveillance camera.
OSC - Spain, we didn't add many types of alerts to the database, as it didn't make sense. For those traveling from France to Spain, there are enough notification types in the OSC database to avoid receiving a fine.