Hi there!
I have a u blox EVK-ML8 and a navilock NL-8012U. Both are GPS mouse connected via USB and I would like to get the gps logger running with it.
When I start the logger I’m stuck after:
nvidia@nvidia:/usr/local/driveworks/bin$ ./sample_imu_logger --driver=imu.uart --params=device=/dev/ttyACM0,baud=9600
Initialize DriveWorks SDK v0.6.67
Release build with GNU 4.9.2 from v0.6.0-rc7-0-g51bd3aa against Vibrante PDK v5.0.5.0
TimeSource: monotonic epoch time offset is 1534379754218388
TimeSource: PTP ioctl returned error. Synchronized time will not be available.
TimeSource: Could not detect valid PTP time source at 'eth0'. Fallback to CLOCK_MONOTONIC.
SDK: Resources mounted from /usr/local/driveworks-0.6/data/resources
nvrm_gpu: Bug 200215060 workaround enabled.
SDK: Create NvMediaDevice
egl::Display: found 2 EGL devices
egl::Display: use drm device: drm-nvdc
SDK: number of GPU devices detected 2
SDK: currently selected GPU device discrete ID 0
SAL: identified board as DrivePX2-TegraA
SensorFactory::createSensor() -> imu.uart, device=/dev/ttyACM0,baud=9600
EndpointTTY: started on /dev/ttyACM0
I have tried the IMU and GPS logger and bother provide the same result…
When I try:
sudo stty -F /dev/ttyACM0 raw -echo -echoe -echok
sudo cat /dev/ttyACM0
then I get this:
$GNGLL,3723.08308,N,12154.89100,W,010917.00,A,D*6B
$GNRMC,010918.00,A,3723.08304,N,12154.89103,W,0.067,,160818,13.17,E,D*1A
$GNVTG,,T,,M,0.067,N,0.125,K,D*3F
$GNGGA,010918.00,3723.08304,N,12154.89103,W,2,12,0.75,18.3,M,-29.8,M,,0000*4D
$GNGSA,A,3,10,32,20,27,21,14,08,24,48,51,,,1.58,0.75,1.39*1E
$GNGSA,A,3,82,67,68,83,81,66,,,,,,,1.58,0.75,1.39*1E
$GPGSV,4,1,13,08,34,299,37,10,67,007,45,11,00,316,,14,38,200,37*7D
$GPGSV,4,2,13,15,03,044,17,18,11,310,19,20,49,057,37,21,39,123,36*7A
$GPGSV,4,3,13,24,18,063,19,27,49,254,27,32,63,191,26,48,45,198,35*72
$GPGSV,4,4,13,51,44,157,35*4A
$GLGSV,3,1,09,66,17,042,14,67,62,002,40,68,43,257,29,75,00,014,*6D
$GLGSV,3,2,09,76,07,055,,77,00,108,,81,25,160,35,82,75,192,27*6A
$GLGSV,3,3,09,83,44,325,20*51
$GNGLL,3723.08304,N,12154.89103,W,010918.00,A,D*6B
$GNRMC,010919.00,A,3723.08302,N,12154.89104,W,0.036,,160818,13.17,E,D*1E
$GNVTG,,T,,M,0.036,N,0.066,K,D*3D
$GNGGA,010919.00,3723.08302,N,12154.89104,W,2,12,0.75,18.2,M,-29.8,M,,0000*4C
$GNGSA,A,3,10,32,20,27,21,14,08,24,48,51,,,1.58,0.75,1.39*1E
$GNGSA,A,3,82,67,68,83,81,66,,,,,,,1.58,0.75,1.39*1E
$GPGSV,4,1,13,08,34,299,37,10,67,007,45,11,00,316,,14,38,200,37*7D
$GPGSV,4,2,13,15,03,044,16,18,11,310,18,20,49,057,37,21,39,123,36*7A
$GPGSV,4,3,13,24,18,063,19,27,49,253,27,32,63,191,26,48,45,198,35*75
$GPGSV,4,4,13,51,44,157,35*4A
$GLGSV,3,1,09,66,17,042,14,67,62,002,40,68,43,257,29,75,00,014,*6D
$GLGSV,3,2,09,76,07,055,,77,00,108,,81,25,160,35,82,75,192,27*6A
$GLGSV,3,3,09,83,44,325,20*51
$GNGLL,3723.08302,N,12154.89104,W,010919.00,A,D*6B
$GNRMC,010920.00,A,3723.08301,N,12154.89105,W,0.018,,160818,13.17,E,D*1A
$GNVTG,,T,,M,0.018,N,0.033,K,D*31
$GNGGA,010920.00,3723.08301,N,12154.89105,W,2,12,0.75,18.1,M,-29.8,M,,0000*47
$GNGSA,A,3,10,32,20,27,21,14,08,24,48,51,,,1.58,0.75,1.39*1E
$GNGSA,A,3,82,67,68,83,81,66,,,,,,,1.58,0.75,1.39*1E
$GPGSV,4,1,13,08,34,299,37,10,67,007,45,11,00,316,,14,38,200,37*7D
$GPGSV,4,2,13,15,03,044,16,18,11,310,20,20,49,057,37,21,39,123,36*71
$GPGSV,4,3,13,24,18,063,18,27,49,253,27,32,63,191,26,48,45,198,35*74
$GPGSV,4,4,13,51,44,157,35*4A
$GLGSV,3,1,09,66,17,042,14,67,62,002,40,68,43,257,29,75,00,014,*6D
$GLGSV,3,2,09,76,07,055,,77,00,108,,81,25,160,35,82,75,192,27*6A
$GLGSV,3,3,09,83,44,325,21*50
which according to the documentation would mean that it works~
Can someone give me some help here please?
Do you know which specific NMEA message driveworks is looking for? (I couldn’t find it by looking into the code)
As a side comment I can get xgps to work fine!
If I run the pre recorder checker the GPS sensor is receiving some information:
SDK: Release NvMediaDevice
Driveworks SDK released
Report of 5000(ms) monitoring:
Sensor camera:
channel 0: frame read = 146, frame rate = 29.2(fps)
Sensor gps:
channel 0: data read = 5916, data rate = 1183.2(B/s)
Result: ok
when I start the recorder I’m told Wait For GPS…
If someone has an idea that would be great!
thank you very much for your support!!!