From: Robert Lipe <robertlipe@us...> - 2004-06-04 14:38:25
Jon & Miki wrote:
> Here's the communications trace using the SPIII with the corrected command
> Rx Data:10 f8 0e 56 45 52 53 4d 41 50 31 20 4e 6f 6e 65 00 fb 10 03
> Tx Data:10 06 02 f8 00 00 10 03 : .....Capability 'V'. Type 21061
> Capability 'S'. Type 16717
> Capability 'P'. Type 8241
> [ERROR] PROTOCOL ERROR: Unknown tag/data [P/8241]
> Capability 'N'. Type 28271
We'll share the blame on this one between jeeps and Garmin. This is at
a point in link buildup where we aren't really speaking the protocol
fluently yet because this is where we're expecting the responses that
tells us which of the 13 (sigh) protocols to _really_ speak. So we're
kind of lock-stepped in a a "I'll send you this and expect that"
pattern. F8 is an undocumented packet type which we're incorrectly
assuming is an Protocol Capability Array response. Since this mystery
packet contains the string "VERSMAP1 None" we can see it's definitely
NOT a PCA and that's blowing us out of sync.
I'll try to make GPS_A100_Get gobble these extra packets up.