"Checkmate was unable to browse to the firmware folder" error when I try to create a firmware key. Any ideas? All files are in the firmware folder correctly. I even tried adding them back to their zip folder so one is extracted and the other is not.

UPDATE: If I login as admin, the application installed and allowed me to do the firmware key. However, the basis user I have setup to user that system to access GEOtab was removed from the group policy (no policy applied). I tried running the application again and get a application error now. Firmware key was created successfully as administrator, but I need the end users to be able to access GEOtab to view their vehicle data.

Thanks,

Brandi

It may be a permissions issue. Please ensure that you can browse to the following directories

XP:
C:\Documents And Settings\All Users\Application Data\Geotab\Checkmate\Firmware

VISTA:
C:\ProgramData\GEOTAB\Checkmate\Firmware

The firmware must be extracted from the zip file and placed in the folder shown above on the computer that is receiving the data (USB Radio Downloader, Ethernet Downloader Server, or Network Downloader):

Hi All

I'm a bit confused about the firmware above??? I downloaded the 65.5.9 firmware with the knowing I can just create a key and program the unit...
But thats where it stopped ;(
The file is a .DL24x64 extention, should it not be .dl, or a 128kb .dat file?

Please help...

Steve

Hi Steve,

You must download the firmware into the Firmware folder which should be located in C:\Documents and Settings\All Users\Application Data\Geotab\Checkmate if you have an XP or C:\Program Data\Geotab\Checkmate if you have Windows 7.
Then go to Checkmate->Vehicles and Devices->Troubleshooting & Accidents -> Create Firmware Upgrade Key
If you placed the file in the correct location you should see it listed.
Select it and click on next and the firmware key will be created.

Hi mauriciomuniz

Thank you for that, I tried above before but the file I initually downloaded was corrupt, thus this gave me endless issues... I downloaded the file now again and works 100%

BTW, Guys - thanks for 5.3.1 - its awesome, fast and clients love it!

Good work!!

3.3.1: GO2 RF - Released....
5.3.3: GO2ARF - Released...

We updated all our firmware last year in the fall as stated by our rep, it was necessary to rule out some issues.

We have 3.2.1 and 5.2.2 on our vehicles. I spoke with our rep yesterday since we are upgrading to the new 5.3.1 next week. I asked him if we needed to upgrade firmware as this was already a hassel to coordinate all our vehicles. He stated, no, that we had the most up to date firmware. But, now I saw this post and it was dated back to 2008??? I'm confused....Please let me know if I have reliable firmware. I do not want to proceed with an upgrade if there will be firmware conflicts within the program.

Thanks,

Hi bgarcia,

You will not experience any conflicts between your firmware and Checkmate 5.3.1; however we always recommend to have the GODevice firmware up to date with our latest released version because there are always improvements made with each release. You can do this update over the air by downloading the firmware files and storing them in the Checkmate firmware folder, this way each vehicle will update the next time it downloads data to your server.
As for the 2008 date, that was the date the initial firmware post was made, however if you see in the bottom you will see the last time the post was edited, January 2010.

"You can do this update over the air by downloading the firmware files and storing them in the Checkmate firmware folder, this way each vehicle will update the next time it downloads data to your server."

You mean on the machine controlling the keydownloader and NOT the server, I presume? We've been doing it the hard way (making a firmware key and schedules all vehicles to use ONE key at a time!). Any documentation on how to set this up? This would be SOO helpful.... Note, though...we have two different units. Meaning, I would have to put 2 versions of firmware out there...would there be a conflict on one key/vehicle receiving incorrect firmware, or will it recognize which it should recieve?


"As for the 2008 date, that was the date the initial firmware post was made, however if you see in the bottom you will see the last time the post was edited, January 2010." I just noticed that later on....d'oh!

The firmware must be stored in the firmware folder on the pc to which the radio downloader is connected to. Then next time the device connects to the downloader to send data it will recieve a firmware update. It will only update if it finds a newer firmware with the same product version, thus if you only put 5.3.3 and a device with 3.X.X connects it will not change its firmware to 5.3.3.

could you have the firmware 75.1.2?
I need it as soon as possible

regars

Rolando,
Is there a specific reason you are asking for 75.1.2?
A newer release version (75.1.8) is available for download in the first post of this thread.

Yes, I have a trouble with the conection between RF downloader and a device, if I download the information with the key, I Can take it and input to system, but, if I want to take the information from the device to the RF conection, I can not download. I thought is the firmware version of this device because all of the other devices have 75.1.2 and this device has 75.1.8
It this possible? or how can you help me?

Hi Rolando.

The firmware version should not affect whether it connects to the downloader.

There are a few reasons why this may be happening.

Is the downloader showing up as a service in Checkmate and/or under Administration -> Radio Downloaders ? If not, you may need to remove the device from the USB devices list on your computer, reinstall Checkmate, and then plug it in again.

If the service is running and the downloader shows up, is it set to the same channel as the channel the device(s) check for?

If it is the same channel, you may need to put the unit in test mode and diagnose what is going on (diagnostic beeps).

If not, you may need to change the device channel through either Checkmate or a programming key.