Menu

#11 RCV-3000 multiple communication errors

open
RCV-3000 (1)
5
2020-07-11
2019-03-10
No

Trying to read from RCV-3000 (mark II) leads to a failure. Multiple errors are reported:

MTK Test OK
MTK Firmware: Version: 1, Release: AXN_3.8_3333_16080400, Model ID: 0000
10:39:00 ERROR: packet_wait() failed for packet PMTK182,3,2,
10:39:06 ERROR: packet_wait() failed for packet PMTK001,182,2,3
10:39:12 ERROR: packet_wait() failed for packet PMTK182,3,3,
10:39:18 ERROR: packet_wait() failed for packet PMTK182,3,4,
10:39:24 ERROR: packet_wait() failed for packet PMTK182,3,5,
10:39:30 ERROR: packet_wait() failed for packet PMTK001,182,2,3
10:39:36 ERROR: packet_wait() failed for packet PMTK182,3,6,
10:39:42 ERROR: packet_wait() failed for packet PMTK001,182,2,3
10:39:48 ERROR: packet_wait() failed for packet PMTK182,3,7,
10:39:54 ERROR: packet_wait() failed for packet PMTK182,3,8,
10:40:00 ERROR: packet_wait() failed for packet PMTK001,182,2,3
10:40:06 ERROR: packet_wait() failed for packet PMTK182,3,10,
10:40:12 ERROR: packet_wait() failed for packet PMTK001,182,2,3
10:40:18 ERROR: packet_wait() failed for packet PMTK182,3,11,
10:40:24 ERROR: packet_wait() failed for packet PMTK001,182,2,3

Any idea how to solve it?

Discussion

  • Niccolo Rigacci

    Niccolo Rigacci - 2019-03-11

    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.

     
    • Marcin Wolcendorf

      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.

       
  • Marcin Wolcendorf

    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?

     

    Last edit: Marcin Wolcendorf 2019-03-17
  • Marcin Wolcendorf

    Ping

     
  • Niccolo Rigacci

    Niccolo Rigacci - 2019-10-12

    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 documented.

     
    • Marcin Wolcendorf

      Hi,

      I will try that shortly.
      Is it possible, that GPS+GLONASS MTK chip has a different communication protocol?

      BR,
      M.W.

       
    • Marcin Wolcendorf

      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.

       
    • Marcin Wolcendorf

      Hi!

      Is there anything going on with this project, or have you abandoned it?

      BR,
      M.W.

       

Log in to post a comment.

MongoDB Logo MongoDB