Phil
Posts:60
 |
| 03 Nov 2011 09:36 AM |
|
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.
|
|
|
|
|
Rolando
Posts:155
|
| 02 Nov 2011 11:37 AM |
|
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?
|
|
|
|
|
Boby
Posts:65
|
| 31 Oct 2011 04:18 PM |
|
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. |
|
|
|
|
rolando
Posts:155
|
| 28 Oct 2011 06:39 PM |
|
could you have the firmware 75.1.2?
I need it as soon as possible
regars
|
|
|
|
|
Mauricio
Posts:268
|
| 05 Apr 2010 10:00 AM |
|
| 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. |
|
|
|
|
bgarcia
Posts:155
|
| 02 Apr 2010 02:41 PM |
|
"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! |
|
|
|
|
Mauricio
Posts:268
|
| 26 Mar 2010 11:30 AM |
|
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. |
|
|
|
|
bgarcia
Posts:155
|
| 26 Mar 2010 11:14 AM |
|
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, |
|
|
|
|
SteveSwart
Posts:155
|
| 12 Jan 2010 08:07 AM |
|
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!! |
|
|
|
|
Mauricio
Posts:268
|
| 11 Jan 2010 12:59 PM |
|
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.
|
|
|
|
|
SteveSwart
Posts:155
|
| 11 Jan 2010 12:22 PM |
|
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 |
|
|
|
|
Tony
Posts:175
|
| 09 Jun 2009 01:16 PM |
|
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): |
|
|
|
|
bmazies
Posts:155
|
| 09 Jun 2009 01:13 PM |
|
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 |
|
|
|
|
Brandi
Posts:21
|
| 09 Jun 2009 10:16 AM |
|
| "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. |
|
|
|
|
Tony
Posts:175
|
| 10 Oct 2008 04:55 PM |
|
The following outlines latest firmware updates to the GO2/GO3/GO4 platform.
GO2 RF
Bug Fix: Set Driver id to 0 on when saving a log record if negative
Added strict GPS criteria to reduce erroneous high speed
Bug Fix: Set Driver id to 0 on when saving a log record if negative
In certain cases, product ID was being reset to 1
Checks RF card to determine if unit can be upgraded to ACK mode
Bug Fix: Possible data corruption on failed RF upload
GO2 LIVE
Added strict GPS criteria to reduce erroneous high speed
Heartbeat functionality added (unit will connect every 6 hours with ignition off)
Reduced modem logging
Added strict GPS criteria to reduce erroneous high speed
Heartbeat functionality added (unit will connect every 6 hours with ignition off)
Reduced modem logging
Added strict GPS criteria to reduce erroneous high speed
Heartbeat functionality added (unit will connect every 6 hours with ignition off)
Reduced modem logging
Added strict GPS criteria to reduce erroneous high speed
Heartbeat functionality added (unit will connect every 6 hours with ignition off)
Reduced modem logging
Added strict GPS criteria to reduce erroneous high speed
Heartbeat functionality added (unit will connect every 6 hours with ignition off)
Reduced modem logging
Added strict GPS criteria to reduce erroneous high speed
Heartbeat functionality added (unit will connect every 6 hours with ignition off)
Reduced modem logging
GO3 RF/Wi-Fi
Improved Reliability
Immobilization Support
Fixed Bug: Accident Data in incorrect format
Heartbeat functionality added (unit will connect every hour with ignition off)
Added Begin of Stop/End of Stop logging
Improved Reliability
Immobilization Support
Fixed Bug: Accident Data in incorrect format
Heartbeat functionality added (unit will connect every hour with ignition off)
Added Begin of Stop/End of Stop logging
Improved Reliability
Immobilization Support
Fixed Bug: Accident Data in incorrect format
Heartbeat functionality added (unit will connect every hour with ignition off)
Added Begin of Stop/End of Stop logging
Added additional Engine Management functionality
GO4 RF
Immobilization Support
CAN Bus Error Checking Implemented
Harsh Breaking support
Warning Beep on Harsh Brake (requires Checkmate 5.3.1 or newer)
Warning Beep on Idling (requires Checkmate 5.3.1 or newer)
Microchip Bootloader update via Main Firmware + Check for invalid Device ID
J1708 request retry algorithm improved to prevent potentially affecting the instrument cluster
Intermittent ignition detect in Caterpillar engines
Immobilization Support
Harsh Breaking support
Warning Beep on Harsh Brake (requires Checkmate 5.3.1 or newer)
Warning Beep on Idling (requires Checkmate 5.3.1 or newer)
Microchip Bootloader update via Main Firmware + Check for invalid Device ID
GO4 LIVE
In certain cases, modem may not power on
Warning Beep on Harsh Brake (requires Checkmate 5.3.1 or newer)
Warning Beep on Idling (requires Checkmate 5.3.1 or newer)
J1708 request retry algorithm improved to prevent potentially affecting the instrument cluster
Intermittent CDMA modem disconnect/reconnect while ignition is on (Multi-tech CDMA 2009 modem revision)
Intermittent ignition detect in Caterpillar engines
In certain cases, modem may not power on
Warning Beep on Harsh Brake (requires Checkmate 5.3.1 or newer)
Warning Beep on Idling (requires Checkmate 5.3.1 or newer)
GO4v2
J1939\CAN ignition detection algorithm improved to prevent potentially affecting the instrument cluster
VIN request on Honda supported
When "check engine" light is on, report both pending and confirmed engine codes
Resolves issue where ignition may not be detected in J1850 vehicle types
J1939\CAN ignition detection algorithm improved to prevent potentially affecting the instrument cluster
VIN request on Honda supported
When "check engine" light is on, report both pending and confirmed engine codes
Resolves issue where ignition may not be detected in J1850 vehicle types
Resolve rare connectivity issue while attempting to auto-detect the GSM network
Improved data filtering on fuel level readings (OBD\CAN)
Optimized debug logging
GO4v3
Latest Release Firmware: 82.1.11
Latest Development Firmware: 82.2.7
|
|
|
|
|