|
What they are referring to is the phenomenon where connecting a serial device to the bottom port can trigger Activesync to start looking for a PC to sync with, never find one and just keep looking and looking. That is a high priority task, so the X5 slows to a crawl or locks up.
To avoid that, use this sequence (start with the GPS NOT plugged in to the X5):
1. Kill all running application (soft reset is a quick way).
2. Start the GPS software, get it set for COM1, then have it start the connection sequence.
3. Now plug in the serial GPS. It should connect and run just fine.
What happens is that only ONE application can use COM1 at a time. When you plug in the GPS first, there is activity on COM1 which triggers Activesync to start listening for the PC. The mapping software can't get through to the port, so it won't connect and as I said, A/S starts to tie up resources listining for an answer that is never going to come. You can't completely kill Activesync, so the only way to make it work is to tie up the port with the mapping software first, so that now Activesync can't see the port and doesn't trigger.
|