Thread: GTM36 and GTM26 problem with TMC on nuvi series 2xxx and 3xxx

Originally Posted by Giomen

You can publish it because we do not know that will be happened tomorrow In any case it is very interesting as fact for investigation...

Here: [Only registered and activated users can see links. ]

I apologize for the delay. Despite having the firmware of GTM60 duly changed since last year, the implementation in practice was done at a distance to a friend who lives in another city and that couldn't enable jetmouse signature in GTM60 of a nuvi 3590, according to images posted in this link: [Only registered and activated users can see links. ] (post 614)
So I waited the arrival of my newly acquired 3597 LMTHD with GTM60. With it in hand I could redo all tests personally to have more security in my conclusions. In addition I also have a 3490 for help.
The fw that came with the GTM60 is 2.10, exactly the same of the GTM of my friend. Thus it would be expected that my gtm60 have the same symptom that happened with gtm60 of my friend, ie, the signature could install normally but the receiver not tuned, showed error (see link). To my disappointment my GTM60 did not present the same mistake in 3597, was seeking the tune without tune, which is normal because I had not installed the signature yet, unlike what happened with the GTM60 in 3590 (then with 7.90 fw) of my friend, which allowed to install the signature jetmouse but the receiver did not search (in the Traffic Receiver Status screen, Rcvr mode of 3590 appeared 12-Error(.
From "older" information of other users, the GTM60 accept signature jetmouse normally, but another surprise: with the GTM60 plugged in 3597 (with firmware 4.20) all options related to inserting cable subscription were unavailable (appear in light grey). It was not possible to even have access to the cable ID, as typically occurs. In other words the gps firmware does not recognize the cable as GTM60 receiver, just as power cable. I found 2 solutions for this problem then: the first is to install the firmware already prepared ( luckily he has a utility). In reality it is only the 2.00 firmware, modified to 2.17, but with checkusum FE identical to the Garmin, what chance a quiet installation without any problem, exactly as if it were original, just copy to the RemoteSW folder. I changed this fw with tips and a tool of Giomen, tks! With this firmware installation the options Traffic appear normally on the gps and it is possible to install the signature. This problem occurred on my 3597 and with another user of a forum that had just bring a USA model identical to mine. Two cases with gps of the same origin, which allows asserting not be an isolated case.
The second solution is the most practical, since you have an older Garmin model available. Simply plug the cable GTM60 on a nuvi oldest (13xx or higher), in my case in a 3490, which installation options will appear normally. After the installation simply plug in all 3597 back to work, and traffic tuning options. Interesting is also that even deleting subscriptions Jetmouse options to reinstall them now are available at 3597, perhaps because the only signatures were hidden and not erased. This procedure has also been tested in practice with GTM60 in virgin cable of a nuvi 3597.
As a conclusion of my experiences can confirm once again that there is a direct relation between the gps firmware and the firmware of the cable GTMxx. it is not clear the different symptoms on 3490 and 3590 with the same firmware from GTM60, despite the 3590 firmware be olderr (7.90) to the current (8.20), on occasion of the test.
Another important detail: we know that there are differences among the firmwares of same models of garmin gps 2012 and 2013 for the market of the Americas and Europe/Australia. So far I have not read any user complaint on this issue, so it may be that he or refer versions of America or, more likely still, which is a specific block to Brazil or another. I believe that because there is a new field in Diagnosts Page of 3597, Developer Info/Traffic Receiver Dashboard which identifies the Country Code and Ecc, which defines exactly the country, may be that the identification activate this specific block. I have the impression that the Garmin has a certain fear of hackers in my country, but unfounded. The great *****ers are in Russia. lol ..