I've seen this a few times, and what appears to be happening is that /dev/pilot starts pointing to the 'wrong' ttyUSB device. When this happens you'll see the "pi_accept_to returned -202" messages (-202 means 'timeout' in pilot-link speak).
If this is a problem for you, you have two options: 1. choose /dev/ttyUSB0 or /dev/ttyUSB1, as appropriate for your pda, instead of /dev/pilot. 2. If you're running pilot-link-0.12.x, migrate to libusb syncing instead of usbserial. -- Gpilotd does not reply to all sync request https://launchpad.net/bugs/62310 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
