- WinXP Pro SP2 running our fleet's Panasonic CF51 laptops with GPSGate v 1.10J installed
- Using Rayming's TripNAV 2.X USB GPS. Strictly an NMEA based device.
- 2 in house GPS aware Apps running and actively listening for NMEA data on GPSGate Output VCP's on COM ports 7 + 8 respectively
- GPSGATE NMEA data input VCP is pointed at either:
- USB GPS device NMEA output typcially configured for COM3 or
- ruggedized EVDO\1xrtt modem attached to physical serial port COM1
- Whenever GPSGate loses "sight" of the GPS device\driver and GPSGate threfore goes red, CPU utilitzation goes to 100%
- Scenarios under which this occurs are:
GPS USB device physically removed from USB port
GPS serial device physically removed from serial port
GPSGate input intentionally configured to point to a COM port with no GPS device attached
[/*][/list] As long as the Gate is green when the APps are listening and a valid NMEA stream is passing through - CPU utilization is fine. AS long as GPSGate is yellow - CPU util is fine.
We are also experiencing the strange behavior described in the forum below where, when we intentionally delete all GPSGate COM port configurations and pointers or GPSGate is initially not configured for any input ports - it then locks on COM1 during OS startup (which in our case = an EVDO based wireless network aircard operating within a ruggedized cable modem).
This also results in a red gate until the modem is attached (of course) and 100% CPU utilization.
Thx in advance for your help.