> Dunno what was wrong but the T3 now receives the GPS fine with a nul-modem. But for communicating two-ways with other NMEA data acqusition devices, I'll likely either need that bridge,SerialFix or some patch in my code.
As I said, the bridge only solves part of the problem. I know that, when
communicating through Garmin protocol, some receivers work
bidirectionally with the RTS/CTS bridge, some not. Some only support a
part of the transfer types. That seems to be dependant on packet/buffer
sizes and protocol variants in Garmin's receivers. Please also note that
not all users are able to apply the RTS/CTS bridge to their cables. It's
easy for classical null-modem cabling, but not for all types of GPS-PDA
So your choice is to either fix the hardware handshake and buffer
problem with your own code, or recommend SerialFix to your users.
I am thankful to Rob Larson for this SerialFix, although I really think
PalmOne, who caused this problem, should have fixed it with a (free)
patch. Instead, they chose to ignore the issue (now for nearly two
years), and screw serial communication even more on the T5 and Treo650.