I had a ublox7 USB GPS working properly on my OmniTIK UPA-5HnD.
I upgraded to a NetMetal5 (922UAGS-5HPacD) with 1 additional RF interfaces in its PCIe slot.
Now the system gets the identification strings and the first set of GPS data from the GPS device and then stops working
(checked via serial termina in CLI - no more data on the port).
Closing and reopening the port gives again the 2 data sets and freezes again.
Both devices use ROS 6.32.3.
Any hints on this?
Do you use this one ?
http://www.amazon.com/Vk-172-G-mouse-glonass-Support-Windows/dp/B00NWEEWW8
What is show in /sy serial-terminal usb1 ? Do you receive any nmea messages ?
No, it’s an GPS mouse type with a UBX-G7020 GNSS chip, but it probably contains the same chip in different outdoor casing.
On the 922, on serial terminal I got only this:
$GPTXT,01,01,02,u-blox ag - www.u-blox.com*50
$GPTXT,01,01,02,HW UBX-G70xx 00070000 FF7FFFFFo*69
$GPTXT,01,01,02,ROM CORE 1.00 (59842) Jun 27 2012 17:43:52*59
$GPTXT,01,01,02,PROTVER 14.00*1E
$GPTXT,01,01,02,ANTSUPERV=AC SD PDoS SR*20
$GPTXT,01,01,02,ANTSTATUS=OK*3B
$GPTXT,01,01,02,LLC FFFFFFFF-FFFFFFFF-FFFFFFFF-FFFFFFFF-FFFFFFFD*2C
$GPRMC,224525.00,A,4543.54413,N,02114.71822,E,0.074,,290116,,,A*71
$GPVTG,,T,,M,0.074,N,0.137,K,A*25
$GPGGA,224525.00,4543.54413,N,02114.71822,E,1,07,1.01,101.3,M,36.8,M,,*5A
$GPGSA,A,3,29,25,31,21,02,12,26,,,,,,1.81,1.01,1.49*0E
$GPGSV,3,1,11,02,23,047,25,05,19,087,12,12,22,118,19,20,13,136,*7A
$GPGSV,3,2,11,21,25,200,33,25,62,117,22,26,19,303,41,29,79,323,33*74
$GPGSV,3,3,11,31,48,278,51,33,26,226,46,40,28,137,*45
$GPGLL,4543.54413,N,02114.71822,E,224525.00,A,A*66
After the first sequence, the NMEA data flow just hangs instead of delivering a NMEA data set every second.
If I exit serial-terminal, wait some 10 seconds and activate it again, I get the same sequence again (but a newer NMEA data set, since the time in $GPGGA and $GPGLL is updated). And then it hangs again.
The same device on an Omnitik works flawless.