Maybe it doesn't recognise the encrypted Cyclops *.gpi files for some reason, but that seems unlikely. If the manual says that it is only possible to load custom poi files onto a CD R to create *gpi using POI Loader and transfer them to the unit that way, then maybe it's indication of that. However, as a 'Garmin' unit it would normally recognise Cylclops. Are you 100% sure:
* That you have used a fully unlocked cyclops file? Did you check your file with [Only registered and activated users can see links. ]? If you're not sure post the file or a screenshot of the PGFT result. Also you could try using a locked cyclops from [Only registered and activated users can see links. ] with the FID changed to 700 or 900 using PGFT and adding a [Only registered and activated users can see links. ] unlock code.
* That the manual doesn't have a separate section regarding Cyclops *gpi and their handling? Most Garmin units when new have a sample file of 'Garmin Safety Cameras' (cyclops) check your backups if you have any.
* That cyclops and other fully compiled *.gpi files won't load by simply burning them directly onto a CD R and introducing them to the unit that way?

If it's too much trouble or you're convinced cyclops won't work you can always load custom redlight/speed cam POIs such as the latest[Only registered and activated users can see links. ] and others using the POILoader/CD R method in the manual.