@bpb
I have on my 3490LMT TrafficProvider.xml version 2.80 can you upload version 3.10?
60% people have problem with GTM36 and GTM26. Garmin has informed. Now just waiting for repair GTM FW.
@bpb
I have on my 3490LMT TrafficProvider.xml version 2.80 can you upload version 3.10?
Please do me a favor and share also v2.80 of the TrafficProvider.xml.
Not sure whether it was shared before
Edit: Never mind, found the attachment.
What is weird, why have 3490 and 3590 different versions and would they work on 3790?
Last edited by tom1807; 30th August 2012 at 06:16 AM.
there should have v 2.50 in some localized unit which not contain ecc
I experiment with webupdater and garmindevice.xml.
I found out this:
006B048201.bin = GTM FW for type 2 (5.50)
006B090100.gcd = GTM FW for type 3 (2.90)
Last edited by lolypop000; 1st September 2012 at 01:25 PM.
In my opinion seems to be no problem of FW, but tuning problem related to external factors, which can either be the radio transmitter, which can confirm whether or not going to the store and comparing with other gps with gtm 36, or can also be strange frequencies of local radio interferences. From what I understand the station tuning of your region should be the 98.90 mghz, but sometimes appear over 5 station, and worse, sometimes with different parameters, blurring the line correct. One of these screens appears with 9/e4/0/21 (33), parameters that impede tune with 9/e4/1/33. The question is how to solve it. Perhaps entering parameters to neutralize it in trafficproviders.xml, suddenly the path may be out there. In this case the problem is with the SID = 0 should be annulled, allowing the tune to the correct sid = 1, what contained in trafficproviders. Finally, the parameter of the incorrect SID can be stored in some memory of gps or GTM receiver, there would be a case of them clean. Had already suggested a thorough cleaning of nonvolatile memory, making a broad and general reset and try manual tuning, you did it? Discover which the region of these non volatile memories and replace them with other empty would be a possibility too ...
The 006B048201.bin and 006B090100.gcd are fw of two variations of models of GTM25 receivers..
@tom1807, why they have differents firmware family. The 1xxx and 37xx "old" firmware's not require ecc parameter to Traffic function and work with GTM that require (GTM 26,36,60) and with that not require (GTM 25, 35). The new firmware of the 24x5, 25x5, 3400, 3500 require ecc and only work with gtm 26, 36 , 60 with original signature, that have ecc (post 31) an dont work with Jetmouse signature (ecc=0). Lolypop case's and others seem to be of another order of causes..What is weird, why have 3490 and 3590 different versions and would they work on 3790?
Last edited by angelozip; 1st September 2012 at 06:09 PM.
DriveLuxe50, Nuvi 2689, Etrex 30x, Epix, VivoActive HR.
New nuvi 24x5, 25x5, 3400, 3500 work with GTM25 and GTM35 with original and with jetmous subscription.
It is different SW for different TMC Reciever:
006B048201.bin - GTM10/12&20/21 (old classic TMC for all FM radio 10/12 - 1 generation and 20/21 -2 generation)
006B090100.GCD - GTM25/35 (3 generation)
006B125700.GCD - GTM26/36 (4 generation)
006B139900.gcd - GTM60HD (HD traffic)
Last edited by Giomen; 3rd September 2012 at 02:13 AM.
Garmin, how much is 30 pieces of silver for Judas today? Were they worthy for crucifix of GPSPower?
Interesting, I compared the 2.90cc version with the 2.90ecc version.
The new Version carries the cc parameters and also the ecc Parameters, so the newer version should also work with GTM25/35
The information provided are newer, for example TMC China is listed now as Pay, 2.90cc lists this as free.
Also updated Provider names are listed now.
Can you upload cc and ecc version?
Bookmarks