I don't know either. I originally set up the Trackers that were going to be working with Nuvi 350s to have port A as Garmin and port B as auto just so that flow was off. When I first tested the units, that worked. However, when the radios were installed and the system was tested, not a single tracker would talk to the nuvis. I worked several different setups until I actually put a spitter on one unit and programmed the Port B for Garmin and AUTO on Port A. Placing the Nuvi on Port B then worked. The other units were reconfigured and set up the same way and also worked. I had no problem with the units running a puck, of course.
When the ride is done, I will experiment more.
For those that would like to follow the ride, we are using tactical calls: COS1 through COS8, CON1, CON2, COML, COCA, COCB.
We know there will not be APRS coverage to an IGATE in several locations, but it doesn't do a bad job.
The route can be followed from here:
--- In email@example.com, Scott Miller <scott@...> wrote:
> It needs to be set to Garmin, not auto. Baud rate and autobaud are
> ignored in Garmin mode. I really can't think of anything that'd make it
> work on port B but not port A.
> k7ybz wrote:
> > I have had a problem with the trackers and nuvi 350's we are using on a
> > week long bicycle event, Cycle Oregon. I have not been able to get the
> > Nuvi 350 to run on Port A regardless of the OT2M settings: Auto or
> > Garmin, 9600, w/wo autobaud. I did make sure that both ports were not
> > programmed the same and that profile switching was disabled.
> > The only way I could get the Nuvi and Tracker to talk was through Port B
> > using a splitter cable. That was true for all four setups. I did have
> > one bad Garmin cable, but had a spare. I am not sure if there is
> > something with the build (latest release) or something else.
> > I am posting this now, but this will be the last day with internet
> > service for the next seven days unless I get lucky with wireless
> > somewhere at an overnight site. This will at least give everyone some
> > time to think about what the problem might be.
> > Larry
> > K7YBZ