At one time my application would send out to a Garmin GPS18 the command "Garmin START SESSION REQ" . My application would wait for the "GARMIN START SESSION REPLY" before processing any other types of packets.
It appears that the garmin_gps.c driver does its own start session req, and eats up the session replies. This did not happen before, as my program was happy to wait for the reply.
It now waits FOREVER for a reply that was improperly eaten by the device driver.
In "NATIVE" mode I dont expect the driver to eat up any messages or packets.
In "GARMIN SERIAL MODE", I might expect some behind the scenes driver/device dialog to get communications going.
There is no changelog to explain. BUt it appears that the gps babel folks might have persuaded this alteration.
Log in to post a comment.