Troubleshooting Eye4Software GPS Mapping Studio: Common Issues & Fixes

Troubleshooting Eye4Software GPS Mapping Studio — Common Issues & Fixes

1) GPS device not connecting

• Cause: Wrong COM port, driver missing, USB-serial adapter not recognized, or incorrect NMEA sentence filter.
• Fixes:
  1. Install/update GPS/USB-serial drivers (manufacturer/FTDI/Prolific).
  2. In Preferences → NMEA0183, select the correct COM port and baud (try 9600/19200/38400).
  3. Refresh port list after plugging adapter; restart app.
  4. Enable required NMEA sentences (e.g., \(GPGGA, \)GPVTG) and disable CRC only if unsupported.
  5. Test with a terminal app (PuTTY, GPS utility) to confirm device output.

2) Wrong position or low accuracy

• Cause: Poor satellite reception, RTK/ DGPS not configured, incorrect antenna placement, wrong datum.
• Fixes:
  1. Move to open sky; ensure antenna has clear view of horizon.
  2. Enable/use RTK or DGPS corrections if available; configure correction input properly.
  3. Verify datum/projection settings (WGS84 vs local datum) in Preferences → Units & Formats.
  4. Check EPE/HDOP values in GPS status and replace/repair antenna or cable if high.

3) Tracks/wps not aligning with basemap

• Cause: Projection mismatch, wrong world file, or incorrect coordinate units.
• Fixes:
  1. Confirm map projection and datum for both basemap and project (use WGS84 or set matching projection).
  2. When exporting/importing images, ensure generated world/projection files are used.
  3. Check units (degrees vs meters) in Preferences → Units & Formats.

4) Import/export file errors (GPX, KML, shapefiles)

• Cause: Unsupported format variant, corrupt file, wrong CRS.
• Fixes:
  1. Re-save using standard GPX/KML from another tool (QGIS, GPSBabel) if file fails.
  2. Verify coordinate reference system (CRS) and convert to WGS84 if needed.
  3. For shapefiles, ensure .shp, .shx, .dbf and .prj are present and valid.

5) Slow rendering or UI lag

• Cause: Large datasets, insufficient RAM/CPU, heavy overlays (photos, rasters).
• Fixes:
  1. Reduce visible layers; hide large rasters or split projects into smaller files.
  2. Increase display cache in Preferences if available; close other apps.
  3. Export large tracks and load only needed segments for editing.

6) Area/measurement discrepancies

• Cause: Wrong area units or calculation method (geodesic vs planar).
• Fixes:
  1. Set desired area units in Preferences → Units & Formats.
  2. Use geodesic (Vincenty) calculations for large areas — confirm software is set to use geodesic formulas.

7) Exported images missing overlays/world files

• Cause: Export options not enabled or permission issues.
• Fixes:
  1. When exporting view, enable generation of world/projection files.
  2. Check write permissions for output folder.
  3. Verify overlays are visible before export (they won’t appear if toggled off).

8) Unexpected crashes or errors on startup

• Cause: Corrupt settings, incompatible plugins, or outdated app version.
• Fixes:
  1. Update to latest Eye4Software release.
  2. Reset preferences/config (backup then remove config file).
  3. Reinstall application and run as administrator.

Quick diagnostic checklist

• Confirm device outputs NMEA (use terminal).
• Match datums/projections between layers (WGS84 preferred).
• Check COM/baud and drivers for GPS.
• Test with a small sample dataset to isolate performance issues.
• Update software and firmware (GPS and PC drivers).

If you’d like, I can generate step‑by‑step commands for checking NMEA output or a short checklist file you can print for field use.