On 12/06/2012 19:32, Tshepang Lekhonkhobe wrote:
When I connect my EVK-6T device on my USB port, a file /dev/ttyACM0 is
created, and I can run cat on it, which results in a bunch of NMEA
messages on stdout.
Not, if I run "rtkrcv -s" (rtklib 2.4.1), and then shutdown the server,
I can't see the output from the file any more. The only way I found how
to recover from that is either rebooting or running "minicom -o -D
/dev/ttyACM0" and then just quitting it. Powering on and off the device
doesn't work.
Here's a 'graphical' illustration:
wena@tshepang:~/src/rtklib_2.4.1/app/rtkrcv/gcc$ cat /dev/ttyACM0
$GPRMC,171152.00,A,2609.09296,S,02757.78034,E,0.054,,120612,,,A*6D
$GPVTG,,T,,M,0.054,N,0.100,K,A*23
...
^C
wena@tshepang:~/src/rtklib_2.4.1/app/rtkrcv/gcc$ ./rtkrcv -s
statup script ok
** rtkrcv ver.2.4.1 console (h:help) **
rtkrcv> shutdown
shutdown rtkrcv process ? (y/n): y
shutdown script ok
wena@tshepang:~/src/rtklib_2.4.1/app/rtkrcv/gcc$ cat /dev/ttyACM0
wena@tshepang:~/src/rtklib_2.4.1/app/rtkrcv/gcc$
Here's the relevant part in my config file:
inpstr1-path = ttyACM0:115200:8:n:1:off
And maybe this is relevant too:
inpstr1-type = serial
Does this have anything to do with the config, or is it something else
(e.g. my total cluelessness)?
Note that this also happens if I set the module to only output raw ubx
message.
This still happens, but it appears it's not an important issue, since
the device messages are still available to rtkrcv. Maybe the tool does
not do proper clean-up or something, who knows.
_______________________________________________
This message is sent to you from [email protected] mailing list.
Visit http://lists.osgeo.org/mailman/listinfo/foss-gps to manage your
subscription
For more information, check http://wiki.osgeo.org/wiki/FOSS-GPS
