Updating old Garmin units

[Jan Horn]

PoiEditor is an is automated Download and install program for RHD. It will download the RHD files create the necessary folders unzip the files and create all the folders required and download the data to the gps using PoiLoader. You have the option to choose to install voice files or not. Change proximity limits and set grace limits. To explain "grace limits" we all know that law enforcement allows a few kmh over the limit before they prosecute for speeding. The program allow for a fixed number or percentage to be added to speed zones. The Gps will only warn you when you enter the proximity limit for as safety camera if you do it at a speed of more than 10kmh below the upper grace you set. For example if you set a grace limit of 9kmh or 7.5% for your 120kmh camera zones it would ad @129 to the name of the Poi. The gps would react with a single bong and a grey banner when you exceed 119kmh when entering or within the proximity zone. If you exceed 129kmh the banner will change to red and the unit will go mad.

[F.Viljoen]

"If you exceed 129kmh the banner will change to red and the unit will go mad."

Then your face will change to red and you will go mad!

[Trevor Rennison]

LOL guys!

So if I'm comfortable doing things manually, like I've always done, then I don't really need this program?

I like the idea of being able to change the grace limits as that suits my driving strategy. There's no grace at the moment and the unit starts to bong as soon as I go even 1km/h over the limit

I'll keep it in mind though as I can see me getting fed up with these constant reminders for being slightly over the limit. At that point I'll probably decide to download it.

Thanks for the advice guys, enjoy the rest of your Sunday.

[F.Viljoen]

What you can do is to:
use Notepad ++ to edit the files and change the 120 to 128.
rename the file. i.e. MT 120 to MT 128 should also work, will check.
Actually you should only get a bong when entering the proximity, regardless of what your speed is.

What is your cam directories names?

[fugglefeet]

The quick way to change the warning limit on the fixed cameras and mobile traps, is to use the Find and Replace function in your favourite text editor and here is how it works:-

Opening for example the MT100.gpx file and doing a Find for the following section of the waypoint information:-

Code: Select all

</name>

In the replace option the text that replaces it is:-

Code: Select all

@110</name>

This makes it possible for you to still travel 10km/h over the speed limit as per the vehicle speedometer but still be within the 10km/h grace limit allowed by the Traffic Inspectorate, since a vehicle's speedometer overreads by about 3 - 5km/h. In theory the following will be true, you will be able to travel between 113 -115km/h as per the vehicle's speedometer and then only will the GPSr start to bleat, bong and nag you are exceeding the speed limit at 110km/h. A bit OT but worth mentioning here is that there are tools and apps available which connects to a vehicle's engine management unit and it allows you to see the speed as recorded by the vehicle's speed sensor. Of interest is that I have compared the GPSr speed to that of the vehicle's speed sensor and the 2 corroborate each other.

Hope this helps

Darryl

P.S. This has to be done for all the Mobile Trap and Fixed Camera files in the 2 separate folders. A bit painful but worth the effort in the long run and still within the speed limit at that. This process takes me about 30 minutes from download to upload.

[Jan Horn]

There is a difference in changing the speed limit to a higher value and adding @xxx (the upper grace) you want to allow your self. When you increase speed the warning will still trigger when your enter the proximity. When the @xx is added the warning will only trigger when you are within 10kmh of the upper grace. My grace for120kmh zones are sett at 7% (128.4kmh) When traveling at anything below 118.4kmh no warnings are triggered and the unit is completely quiet. The only down side is that installing the sound speed warnings disable grace limit settings.
A screen shot of the change.

[F.Viljoen]

Thanks Darryl for that code tip.
I first posted to add a @speed with Notepad, but when I saw the hassle to add that using the point number, changed my mind.
So by changing the 100 to @110 should also work as with 100 Kmh Mobile Cam 1234 @110, but then your display will show the @ like @110 Mobile Cam 1234

[Jan Horn]

No It is added at the end of the name and will not show on the banner on the gps. (The continuous warning on the GPSr should be changed to single warning) The @ is an instruction I think for PoiLoader and I don't think it is loaded on the GPSr accept as an instruction of when to trigger the warning

[F.Viljoen]

Agree oom Jan if it's at the end it won't show on the display.
But if I add the @speed to the first digits, will it then display? Must test it.

i) @128 Fixed Cam 1234
ii) 120 Kmh Fixed Cam 1234 @128

If PoiLoader takes (i) @128 as speed, the display will then only be - Fixed Cam 1234

[Jan Horn]

I have never tried it but it may drop verything after the @ and I do not know if that point will then trigger. There was long discussions on this in the Garmap forum at the time but we lost that data when the forum was closed so we cannot refer back to it. My memory on that is not that clear on all that was discussed.. Both Tinus Srauss (Sandman) and Abri du Pllooy at the time wrote programs to add the @ to the name. Both programs evolved to be come fully automated downloading and installing the RSD (now RHD) on a GPSr.