Remember, whatever you learn could help someone in the future. Please share the wealth.
Larry K7YBZ --- In [email protected], "Frank C." <fchri...@...> wrote: > > Just a slight improvement tonight. The OT2m and radio finally worked and I > got myself on the map with a fixed position about 2 hours North of me. A > local ham gave me the idea. > > Now to get the Nüvi to play nice... > > Regards, > > -Frank C. > > On Jul 15, 2010, at 19:53, Randy Love <rlov...@...> wrote: > > Well, Frank. donno what else either. > > You have tried powering the OT2m first, then the Nuvi, several times, > powering off and back on each on every attempt, correct? > I seem to remember having to do that sequence so the the OT2m would sense the > Nuvi and put it into FMI mode. > > I have 3 Nuvi/OT2m/T2-135 combos. Aside from double checking the pinouts, > don't know what else to tell you. > > Now, let's make sure of couple of things: > > 1) you are using the Garmin Data Cable for the Nuvi 350, the one with 00813 > in the part number, correct? > 2) you are using an OT2m (external to the radio), not a T2-135 placed inside > an Alinco DR-?35T, correct? > > If you answered no to 1, and you aren't using a Nuvi 350 ( or similar ), then > you possibly have the wrong FMI cable. > > If you answered no to 2, then double check the wiring on the DB9 connector. > Pins 2 and 3 are REVERSED between the T2-135 setup and the OT2m setup. In > either case, you can easily reverse the pins to see if that fixes it by > putting a null modem adapter between the OT2m and the Nuvi. If the pins are > incorrectly wired, it won't hurt anything as they are low level data signals. > > Quickly running out of suggests, but having 2 bad FMI cables is very unlikely. > > Gotta finish a couple of other items here for an MS150 Bike event this > weekend. > > 73, > Randy > WF5X > > > > On Thu, Jul 15, 2010 at 9:12 PM, Frank C. <fchri...@...> wrote: > > Thanks. I have two cables from Scott and neither work. The radio keys up just > fine but no transmitted signal from the OT2m > > Regards, > > -Frank C. > > On Jul 15, 2010, at 16:22, "k7ybz" <k7...@...> wrote: > > > Frank, > > Sorry, but I am out of idearrrsss. What I gave you is what I do to check my > setups. I have four Nuvi 350/OT2 combos plus GTRANS cables for that > occasional D710/NUVI combo, depending on what I need for those rushed support > activities, like Cycle Oregon or some other in which I have to have a quick > install in a 15 passenger rental van or the like. I am in the middle of > getting things ready for an event this weekend. > > If you know someone in your neck of the woods who has a similar setup, you > can try swapping equipment and cables until you find the answer. Otherwise > have Scott at Argent Data take a look. Scott usually chimes in when he is not > playing with ballons. > > Now that I think about it, I did have a DOA FMI cable that came from Garmin > via Argent Data. I already had a spare and put it to use immediately. I > wanted to see what the bump was all about so took the DOA one apart. That > reminds me too, I should order another one to have as a spare. > > Good luck, > > Larry > K7YBZ > > I will be flying tomorrow and have APRS in the plane. Check K7YBZ-11. > > --- In [email protected], "Frank C." <fchrist2@> wrote: > > > > Not sure what else to do. I thought, based off reading, that this was more > > plug n play. Seems the tracker2 doesn't auto-key?... > > > > Regards, > > > > -Frank C. > > > > On Jul 15, 2010, at 14:56, "Frank C." <fchrist2@> wrote: > > > > Larry, > > > > Yes to the Nüvi being powered via the cradle and the FMI in the side. > > The Nüvi has complete coverage as far as I can tell. It gives me 26' > > accuracy. > > > > As for the OT2m the activity light is solid green. > > > > Any other ideas? > > > > Regards, > > > > -Frank C. > > > > On Jul 15, 2010, at 14:33, "k7ybz" <k7ybz@> wrote: > > > > > > Not true on the firmware. FMI was supported nearly the entire OT2 > > production and well before 54740 dated Aug 2008. However, having the latest > > firmware installed in the OT2 is still a good idea. > > > > Frank, > > > > Just to make sure.... > > > > FMI usb end plugged into the NUVI 350 SIDE connector. > > Power supplied from the cradle to the rear connector. (I know you said yes > > to this, but another confirmation) > > I concur that the NUVI should be plugged into the B side of the OT2 and > > BMODE set to Garmin. Be sure to set AMODE to AUTO or someting other than > > GARMIN otherwise it "could" have unpredictable results. > > Obiously, the OT2 needs it own power. > > > > One solution has been to power up the Nuvi first and leave the OT2 > > unpowered until the NUVI has aquired a position, then turn on the OT2. > > > > If the OT2 activity light is blinking green about one flash per second, it > > is receiving GPS data. If the activity light is red, then there are > > problems. A caveat to that is that LED will be red until a valid GPS signal > > is received but that should not last more than two or three minutes > > depending on how long the NUVI has been off (I am talking several days to > > weeks here). The NUVI has to aquire one satelite before it can update its > > database on the other satelites. > > > > There is no way to run a continuity check on the FMI cable since that bump > > near the mini-b connector end is the level shifter. You would have to take > > the DE-9 connector apart and check the wiring, at least check that the > > colored wires are going to the correct pins. Other than that, you might > > have to send everything back to Scott and have him check it out for you. > > > > Larry > > K7YBZ > > > > --- In [email protected], Randy Love <rlove31@> wrote: > > > > > > On Thu, Jul 15, 2010 at 4:52 PM, Frank C. <fchrist2@> wrote: > > > > > > > > > > > > > > > > > > > On the Tracker2 i have firmware build 55076 and the Nüvi is version > > > > 6.20...If that helps at all. Right now I have the vehicle half torn > > > > apart so > > > > everything can be in one little area. > > > > > > > > > > I think that firmware isn't new enough to support the FMI cable. > > > Try updating to the latest firmware and try again. > > > > > > 73, > > > Randy > > > WF5X > > > > > >
