Re: [Gpsbabel-misc] etrex yellow: connection not possible if cancelled before

[HomeRun4711 <hom...@go...>]

I had a look into the source code and found a
workaround. Is there some sort of busy-flag, that
indicates that data is transferred?
If yes, maybe this should be implemented to
catch this situation in some way.

I added a new command line parameter
"garmin,abort_transfer"
which sends the command represented by

"US Cmnd_Abort_Transfer;",

which is already present, but unused, in the first

struct COMMANDDATA COMMAND_ID[2]

Principle is the same as with "garmin,power_off" and
"US Cmnd_Turn_Off_Pwr;".

I just changed the names in GPS_Command_Off to get a
function GPS_Command_Abort_Transfer.
Very very rough, I don't have a clue of the garmin api :)

Well, after sending the command to abort the
transfer I can immediately start a transfer without
turning the unit off and on again. So it works.

Any comments?

Kind regards,
jones


Am 11.10.2010 15:14, schrieb Robert Lipe:
> On Mon, Oct 11, 2010 at 7:18 AM, HomeRun4711<hom...@go...>wrote:
>
> After switching on my unit it works like a charm.
>> But after cancelling a running download (Ctrl+C)
>> it's not possible to restart a download again.
>>
>
> I'm not terribly surprised.   This generation of hardware doesn't really
> have a concept of connection state.  It's probably hung in some kind of
> protocol retry loop while we're trying to start a conversation with it.   A
> reset really is the solution.
>
> RJL
>