Dave, Are you using the Garmin 010-10813-00 mini-b data cable or one that is home made? That message would indicate a bad cable or one that is not properly plugged into the side of the Nuvi. The Nuvi is either not recognizing the ID of the cable or the protocol it is receiving is wrong.
First of all, make sure you have power connected to the Nuvi through the back connector. Then make sure in the configuration you do not have both ports set to the same protocol. For your setup, Port B should be GARMIN and Port A as AUTO or KISS. The console is only available on Port A. However, you can set Port A to GARMIN and Port B to AUTO and put the Nuvi on Port A, but you will not be able to connect a computer to Port B. With the latter configuration, you could remove the port splitter cable and plug the Nuvi directly into the OT2. Larry K7YBZ --- In [email protected], "Dave" <d...@...> wrote: > > More information: > > The intermittent communication problem exists even when no rig is > attached. Can't reliably connect to send the message -Version and get a > response. The USB connection on the side of the Nuvi works fine when > connected to a computer for file exchange. Looks like there may be bad > solder connections on the pin 1 - 8 side of the RS-232 interface chip in > the Tracker2. I was using port B for the Nuvi and port A for the > programming interface, I might swap them and see if anything changes. > > Dave, KI4PSR > > > --- In [email protected], "Dave" <dave@> wrote: > > > > I am new to the Tracker2 Nuvi350 combination. The system seems to be > working properly, I can send and receive messages via APRS, I see > stations as waypoints on the map, etc. However I continue to get a > message 'This accessory is not supported', and I have to cycle power to > the Tracker2 to get the combination working again. Connectors all look > good, rig is Yaesu FT-8800at low power (5W) and outside of the shack > antenna, but still in the nearfield of the setup. Configuration or > jumper setting? Any ideas? > > > > Dave, KI4PSR > > > > (I tried to search for this problem but found no match, I apologize if > this subject has previously been beaten to death <g>.) > > >
