The new releases of Cyclops Safety Camera with FID/MapID=2496 doesn't work with newer Garmin units. Garmin files with FID/MapID >= 2200 may need the GMA authentication. Avoid the need of GMA authentication by using patched GPI-files. This release will have original files and the ability to create 3 other flavors.
Now there's also South Africa included.
Original Cyclops Safety Camera files. November 3, 2011 (latest files but with Cyclops data not updated since Oct 27): [Only registered and activated users can see links. ]
Create matching "*safety_camera_*.unl" files with generated 25-character unlock code. Use JM v1.5 and generate with UnitID or CardID together with FID, PID, RgnID & VenID. Use the values for the set that you prefer.
My test seems to indicate that the "unl_" series with FID=65535 doesn't need any UNL-files with unlock codes.
Original files is posted above. Here's the patched sets to avoid GMA authentication problems in newer devices:
[Only registered and activated users can see links. ] Uses FID=700 as related to previous pietu releases. Just rename files without the heading "700_" and reuse all previously created UNL-files.
[Only registered and activated users can see links. ] Uses FID=900 and PID=9 to be closest match to earlier original Cyclops GPI-files before they changed from 900/9/r/v to 2496/9/r/v. Just rename files without the heading "900_" and reuse all previously created UNL-files.
[Only registered and activated users can see links. ] Uses the same FID, PID, RgnID & VenID as unlocked Tour Guides. Seems to work without UNL-files (the obvious goal of course).
[Only registered and activated users can see links. ] [Only registered and activated users can see links. ]
There's also a "CyclopsPatchSet.rar" attached with some VBScript files. They use ADODB objects to manipulate binary files.
It's a quick-and-dirty solution but works well during tests.
Some extra info about patch technique from [Only registered and activated users can see links. ]
Patching can be done by using a HexEditor and edit manually. I have hinted how to do that in earlier posts like [Only registered and activated users can see links. ].
To patch with different FIDs like 700, 900 and 65535 it makes sense to have some application or script to repeat that process. That's why there's some VBScripts attached in post [Only registered and activated users can see links. ]
The script takes a pre-created binary array from a "patch*.bin" file. VBScripting are not easy to create ByteArrays inside code so it's better to have a predefined file for the values and just copy & paste one file into another with the script.
Here we take FID=0xFFFF (65535), PID=0xFF (255), RgnID=0xFF (255) & VenID=0x00 (0).
The offset value 0x26 (38) to find the start address 0x2D (0x2D = 0x26 + 0x7) is marked in the picture. Seems like it's 0x26 for most Cyclops files and then this Cyclops file have FID starting at address 0x2D. FID hex-value 0xC0 and 0x09 should be swapped (little endianness) and 0x09C0 gives 2496 in decimal form. We want to overwrite 5 bytes with new values to circumvent the need of GMA and possibly even UNL files.
Here's the result after patching.
Last edited by catymag; 10th September 2012 at 12:17 PM.
Reason: restored post n links after cleaned thread
Here is a little C# application (CyclopSafetyCamera Tools v126.96.36.199) that gives you the information of a cyclop gpi file, and can change the FID's or unlock the file.
[Only registered and activated users can see links. ]
usage : use the "Load file to open a cyclop gpi file" or just drag and drop the cyclop gpi file on it.
When using the FID700 / FID900 / Unlock, a new file will be created in the same folder as the original file, and will be named : [original]_fid700.gpi [original]_fid900.gpi [original]_unlock.gpi
It has been made with the information found on this post, so credit are not for me (or just for having made an exe file :p).
Here is the link : [Only registered and activated users can see links. ]
Have fun using it.
Last edited by marcoqc; 21st November 2011 at 07:28 PM.
Reason: changed link for the executable