MTKBabel Activity
Brought to you by:
niccolo
Activity for MTKBabel
-
Marcin Wolcendorf posted a comment on ticket #11
Hi! Is there anything going on with this project, or have you abandoned it? BR, M.W.
-
Hi, I've increased the timeout to 25s, but it didn't help. The PMTK182,3,2 message from the GPS logger is not there. BR, M.W.
-
Hi, I will try that shortly. Is it possible, that GPS+GLONASS MTK chip has a different communication protocol? BR, M.W.
-
Niccolo Rigacci posted a comment on ticket #11
Hi, sorry for the tremendous delay of this answer! It seems that your device does not respond at the requests made by the program. In your debug log I see that the command "PMTK182,2,2" (get current log format) did not received the answer "PMTK182,3,2". You can try to increase the definition in the mtkbabel script: my $TIMEOUT = 5; Try someting about 10 (seconds) or more. May be your device is simply slower in response. Or may be your device does not respond at the MTK commands that are document...
-
MTKBabel released /mtkbabel/0.8.4/mtkbabel-0.8.4.tar.gz
-
-
-
Tagged release 0.8.4.
-
Workaround for Weeks Rollover Bug.
-
Ping
-
Hi, I do not know if you got my response; I'm sending it again: Command: mtkbabel -c -i -t -w -f trip.log.holux.date +%FT%T -p /dev/ttyUSB0 -s 38400 The problem is reproducible, happens every time; the errors are always the same. I do not think it has ever completed. I do not know if it matters, but this device is based on MTK3333, GPS + GLONASS chip. Anyhow - the logs are attached. BR, M.W.
-
Hi! Thanks for quick answer! Command: mtkbabel -c -i -t -w -f trip.log.holux.date +%FT%T -p /dev/ttyUSB0 -s 38400 The problem is reproducible, happens every time; the errors are always the same. I do not think it has ever completed. I do not know if it matters, but this device is based on MTK3333, GPS + GLONASS chip. Anyhow - the logs are attached. BR, M.W. PS. Do you need more information?
-
Hi! Thanks for quick answer! Command: mtkbabel -c -i -t -w -f trip.log.holux.date +%FT%T -p /dev/ttyUSB0 -s 38400 The problem is reproducible, happens every time; the errors are always the same. I do not think it has ever completed. I do not know if it matters, but this device is based on MTK3333, GPS + GLONASS chip. Anyhow - the logs are attached. BR, M.W.
-
Hi! What command produced that output? It seems the command used to set logging format... By the way: the problem is persistent? Always occurred? Occurs only sometimes? Does that command ever succeeded? Please re-run the command with max debug enabled (-d 7), copy all the debug messages and attach all the generated files.
-
RCV-3000 multiple communication errors
1