Curious Problem with Cork City Locale Geocaching Pocket Query

If you’re a premium member with Groundspeak’s then you will be aware of the ability to create pocket queries. These are really useful for throwing up to 1000 waypoints onto your GPSr for a days, or even a holidays caching.

As some of you know we were in Ireland recently (the reason for lack of posts) and I decided to take advantage of Stena Ferries free satellite wifi on the boat. I set a PQ for Cork and waited for it to build. When the query was ready I saved as usual to my shared Dropbox folder and then attached my Garmin 60CSx but despite loading fine onto my CacheBerry – the PQ just wouldn’y upload to the Garmin.

Puzzled, I tried an older PQ and verified that my script was working, as well as the Garmin was not having some kind of software fault. Next most obvious thing that occurred to me was perhaps the file was corrupted during download, after all it was a wireless connection via satellite on a moving ferry. I tested this theory by downloading the PQ again. Then I downloaded one I’d created earlier. The earlier one (Watford) worked, the Cork didn’t.

Then I decided to test the website PQ builder itself – maybe there was a technical problem. I checked the forums but there was nothing reported, so I posted a thread which didn’t go anywhere. I then tried creating an entirely new PQ of Leicester (never run before). I downloaded and Leicester loaded up onto my GPS no problem.

So there was something local to Cork which was borking my PQ which had to be in the file itself. I didn’t have much time left so I tried a splicing the file with my newly created Leicester PQ. I opened up the GPX file and chopped out the header:

<?xml version="1.0" encoding="utf-8"?>
<gpx xmlns:xsi="" xmlns:xsd="" version="1.0" creator="Groundspeak Pocket Query" xsi:schemaLocation="" xmlns="">
<desc>Geocache file generated by Groundspeak</desc>
<keywords>cache, geocache, groundspeak</keywords>
<bounds minlat="51.551967" minlon="-9.37105" maxlat="52.428967" maxlon="-7.593717" />
<?xml version="1.0" encoding="utf-8"?><gpx xmlns:xsi="" xmlns:xsd="" version="1.0" creator="Groundspeak Pocket Query" xsi:schemaLocation="" xmlns="">  <name>Cork</name>  <desc>Geocache file generated by Groundspeak</desc>  <author>Groundspeak</author>  <email></email>  <time>2010-06-16T03:12:46.2642819Z</time>  <keywords>cache, geocache, groundspeak</keywords>  <bounds minlat="51.551967" minlon="-9.37105" maxlat="52.428967" maxlon="-7.593717" />

and footer:


I then copied the remaining xml and pasted it below the header in the Leicester PQ, then saved this and zipped it back up.

I ran my script and and uploaded it to my 60CSx – it worked!

I can’t see anything wrong with the header info above but this is where the error seems to lie. Maybe it’s something to do with the coordinates in the boundary tag, or perhaps some hidden character I missed. Does anyone more technical in both xml and WGS84 Datum than me have an idea?

Oddly enough, subsequent PQs for Cork after we arrived worked too.

Just GPSBabel

A while ago I posted my frustrations with running GSAK on Linux, and how I’d found a way of getting the function to send to my Garmin 60CSx to work.

I thought I owed an update to anyone who read that to say I gave up on GSAK and now just use GPSBabel from the command line. Here’s the script I run:


NAME=`echo $GPXZIP | cut -f1 -d.`

unzip $GPXZIP
GPXFILE=`ls *.gpx`
for FILE in `echo $GPXFILE`; do
    gpsbabel -i gpx -f $FILE -o garmin -F usb:0

I called the script ‘’. I saved it in the directory where I save all my pocket queries are stored as zip files. When it comes to load them, I just hook up the Garmin and then run:

sudo ./

Works for me, but I never bothered with using GSAK for much more than sending the pocket queries – I’m not at the stage yet where I feel I have to create complicated queries to get a good caching experience.

Fixing A Bricked Garmin GPSmap 60CSx (Part 2)

In Part 1 I explained how my Garmin 60CSx booted up with a completely blank screen and doing a firmware update didn’t work – despite the update being successful. Now I’m going to tell you what I did do.

Frustrated I googled a bit more and happened upon this forum post where someone had taken their 60CSx apart and posted photos. The topic here was a broken receiver but the images were useful to me nonetheless.

I decided to pop open my own device and have a look to see if anything came loose. I didn’t take pictures, though I wish I did now, however I can provide detailed steps I took below on taking the 60CSx apart.

Disclaimer – I am not a Garmin technician, and doing this may void your warranty. You may simply want to send it back to them for repair, but I didn’t have a warranty, I bought mine secondhand.

  1. Pop open the battery cover and unscrew the 4 screws on either side, plus the 2 screws at the top of the casing in the deeper holes.
  2. Carefully tug at the back casing to remove – it should come away fairly easily but you’ll need to tear the silicon gel which will affect how waterproof your device is afterwards.
  3. Io unplugged the power supply for the USB/serial connector, I couldn’t remove the other cable for the compression connector but I was able to get inside anyhow with care.
  4. The next part was to prise out the clear plastic chassis. This is quite tight and I actually broke one of the screw hinges. I found the best way was to slide the mini screwdriver down the side and push the side of the casing outwards until it popped out.
  5. After you have the chassis out it’s possible to lift and slide the motherboard and screen downwards, being careful to slide the antenna out of the shock absorber at the top.
Inside the Garmin GSPmap 60CSx
Inside the Garmin GSPmap 60CSx

It then became clear to me what problem was. I noticed as soon as I lifted the LCD screen – the flex connector at the back had come loose!

After reconnecting and putting the motherboard back into the casing, I used superglue to fasten the screw hinge back on the chassis and then No More Nails glue to affix the rubber back in place on the outer casing ( I don’t have any silicon gel to hand). Hopefully it’s going to be waterproof enough again – but I’m glad to say I once again have a fully functioning 60CSx.

I thought this post might be helpful for anyone who finds themselves one day with the same problem.

Fixing A Bricked Garmin GPSmap 60CSx (Part 1)

Last week I had a minor panic attack and bout of depression. After coming back from one of the 10 Year Lost and Found Geocaching events late at night, I dropped my Garmin GPSmap 60CSx on the floor, picked it up and thought nothing of it. The reason being is that the 60CSx is a rugged piece of equipment which can withstand a lot of shock and even full immersion – this one in particular in an unrelated incident has survived being tossed 20-30 feet in a field – hardly a dent on it.

However the next evening I was preparing to load a new pocket query onto the device and powered it up the screen was completely blank! Nothing was loading, I tried banging it, replacing batteries powering up with USB cable but I got nothing. So I did what any guy with insufficient technical gonads to handle this problem, I turned to Google.

My googly friend soon pointed me to this page by Brilliant Corners. Essentially the solution to a similar looking problem was the following method:

  1. Download the latest firmware file.
  2. Double click the .exe and extract the files.
  3. Since the unit won’t be recognized by the firmware updater on its own, use the following key combo: hold down the power button (on the top of the unit) and push the directional button in the up (“^”) position.
  4. While holding those buttons down, double click on the Updater.exe file.
  5. While still holding down the two buttons, make sure your GPS device is selected, and then click the “OK” button to start the firmware update.
  6. During the entire firmware update process you need to hold those buttons down. Then when the update is finished, release and reboot.

Now, this meant I had to boot into Windows Vista and suffer a myriad of updates and other crap until that was finished so I could get to the fix. I had already downloaded the firmware, but I found BC’s link was broken so I went to Garmin direct for 4.00. However, I hardly used Windows for connecting to my Garmin before, so I decided to download the Webupdater to give that a try – turns out the Webupdater worked automatically and using xImage I was able to grab a screenshot of the 60CSx’s ‘desktop’ to confirm it had worked.

But as the discerning amongst you can already tell, if I had to use xImage to take a snapshot of the device – I still couldn’t see past a blank screen. Queue desperate monologuing to my wife as she’s trying to catch up on Lost and reminds me I am speaking over the TV…

So, what did I do next? You’ll have to read Part 2 (coming soon)…