Tammy WA7TZ wrote... > When I had my dr-135 hooked up to my computer in > terminal mode and switched the T2-135 into Garmin > mode (using the amode Garmin command) the information > it is outputting and displaying on the screen changed from text > to ASCI characters that look like they are in the Wing Ding font. > I no longer get any response the T2-135 if I enter a keyboard > command.
I'm not sure what you were expecting when the port in the T2-135 was set to Garmin mode. While it might be interesting to look at it (with the baud rate set correctly) in a terminal program, it only becomes useful (for APRS) when connected to a Tracker 2... T2-135, OT2m, or T2-301. > The cable I was sent was the Garmin Mini B to Serial Pigtail P/N > 010-10813-00 Actually, that is the correct cable. You can actually make up your own FMI cable using a drawing from the files area... http://groups.yahoo.com/group/tracker2/files/ http://f1.grp.yahoofs.com/v1/IPkDTBiUkyUQsnTsDMfXa4a394GW3_cKOmTjOLqlrnwGYvgYXPISotQowDx35reKVTQMMFDPGdmSYlnJCR9khdwo_8Pl/NuviCable.jpg However, the one you have should connect directly to the T2-135 in the Alinco radio. > When I hooked my unmodified Nuvi 350 up as instructed in the > manual for FMI I don't get the Fleet option. I think this is the wrong > cable. The Nuvi must be powered via the cradle. It won't go into FMI mode if it's running on the internal battery. You should have it set to AMODE Garmin, but after you have done all of the programming, exit otwincfg.exe, just connect the Nuvi to the T2-135. 73 es cul - Keith VE7GDH -- "I may be lost, but I know exactly where I am!"
