DW_TIME_OUT for MTi-G-710-2A8G4


I have a MTi-G-710-2A8G4 GNSS receiver connected to the AGX over USB. When I try to read GPS frames with

dwSensorGPS_readFrame(&frame, DW_TIMEOUT_INFINITE, gpsSensor)

I get a DW_TIME_OUT. However, dwSensor_start(gpsSensor) returns a DW_SUCCESS.

The receiver works well since I could see the timestamp, lat and long using the official MTi software on a Windows machine.

Any idea what could be the issue?

Dear animeshramesh,

Could you please help to check if the module is works with driveworks sample ./sample_gps_logger?
Please see DriveWorks doc for instructions. Thanks.

Hi SteveNV,

Here are the logs after running the sample:

[09-07-2017 21:45:03] Platform: Detected DDPX - Tegra A
[09-07-2017 21:45:03] Initialize DriveWorks SDK v2.0.2081
[09-07-2017 21:45:03] Release build with GNU 4.9.4 from heads/buildbrain-branch-0-g36b127f against Drive PDK v5.1.0.2
[09-07-2017 21:45:03] TimeSource: monotonic epoch time offset is 1499153885543220
[09-07-2017 21:45:03] PTP Time is available from NVPPS Driver
[09-07-2017 21:45:04] Platform: number of GPU devices detected 1
[09-07-2017 21:45:04] Platform: currently selected GPU device integrated ID 0
[09-07-2017 21:45:04] SDK: Resources mounted from /usr/local/driveworks-2.0/data/
[09-07-2017 21:45:04] SDK: Create NvMediaDevice
[09-07-2017 21:45:04] egl::Display: found 1 EGL devices
[09-07-2017 21:45:04] egl::Display: use drm device: drm-nvdc
[09-07-2017 21:45:04] SensorFactory::createSensor() -> gps.xsens, device=0,frequency=100
[09-07-2017 21:45:06] XsensCapture: Xsens packets are not 128 bytes (140 bytes), When using USB interface, packets might jitter sometimes with up-to 15ms (known issue).As an alternative, you may use the UART interface. See documentation for details
[09-07-2017 21:45:06] SensorFactory::createSensor() -> gps.xsens, device=0,frequency=100
[09-07-2017 21:45:06] EndpointXsens: started for device 0
[09-07-2017 21:45:06] Draining XSense buffer
[09-07-2017 21:45:06] XSense buffer drained successfully

The sample stops generating logs after the last line. (probably due to the timeout)

The DriveWorks version is v2.0.2081, if that helps.

I believe any subsequent calls to dwSensorGPS_readFrame causes a DW_TIME_OUT since the very first call causes a DW_NOT_AVAILABLE.

Dear animeshramesh,

The DW GPS sample will only work if it receives a signal from the actual GPS.
Perhaps the error is caused by not receiving a signal from GPS.
Could you please test at a place where you can receive GPS signal?

Thanks. It is now resolved.

There was an issue with our antenna. It was incorrectly configured.