Hello, which device should i use on platform https://m.gps-trace.com because on old platform i used Xexun TK102 and it worked, but now it doesn't work. I tried also "Xexun". This is format of my device from TCP dump:
1911121052,+4219xxxxxxxx,GPRMC,095205.000,A,4844.2960,N,1910.2270,E,1.39,227.05,121119,00,0000.0,A*46,F,,imei:357713005912412,126
in place of "xxxxxxxx" is my phone number

    MarekKapik
    Please, try again to connect your device using xexun protocol.
    If device sends '\n' at the end of the packet from your example - it should work now.

    Thank you. I selected "Xexun" device but it is still offline. I caught two packets. End of first packet (behind 126) are two bytes 0xCF and 0x7F. End of second packet (behind 126) are 0xEF, 0x6

    • namo replied to this.

      MarekKapik
      Please, try to connect your device again

        31 39 31 31 31 32 31 30 35 32
        2c 2b 34 32 31 39 30 35 30 31 32 36 30 39 2c 47
        50 52 4d 43 2c 30 39 35 32 30 35 2e 30 30 30 2c
        41 2c 34 38 34 34 2e 32 39 36 30 2c 4e 2c 31 39
        31 30 2e 32 32 37 30 2c 45 2c 31 2e 33 39 2c 32
        32 37 2e 30 35 2c 31 32 31 31 31 39 2c 30 30 2c
        30 30 30 30 2e 30 2c 41 2a 34 36 2c 46 2c 2c 69
        6d 65 69 3a 33 35 37 37 31 33 30 30 35 39 31 32
        34 31 32 2c 31 32 36 cf 7f

          Second packet:
          31 39 31 31 31 32 31 30 33 33
          2c 2b 34 32 31 39 30 35 30 31 32 36 30 39 2c 47
          50 52 4d 43 2c 30 39 33 33 31 39 2e 30 30 30 2c
          41 2c 34 38 34 34 2e 33 30 30 30 2c 4e 2c 31 39
          31 30 2e 31 39 36 30 2c 45 2c 30 2e 37 32 2c 31
          34 31 2e 34 38 2c 31 32 31 31 31 39 2c 30 30 2c
          30 30 30 30 2e 30 2c 41 2a 35 35 2c 46 2c 2c 69
          6d 65 69 3a 33 35 37 37 31 33 30 30 35 39 31 32
          34 31 32 2c 31 32 36 ef 06

            great, i am online now, but it gives wrong coordinates: 48.738333, 191.003566
            I am in Europe 😃

              MarekKapik
              That's because your tracker sends longitude as 1910.2270,E
              But according to NMEA specification longitude format is expected as dddmm.mmmm

                ok, its cheap china device. Could you parse it correctly please? I think there is more people with this device and it worked at old platform http://orange.gps-trace.com/

                • namo replied to this.

                  MarekKapik
                  Hey Marek!
                  Please check now - your device should have relocated to Europe.

                  Hi, I bought a new gps tracker (Xexun TK102-2) but the firmware is different from the previous one and I can't understand if GPRS is working properly because I can't configure it in the new android app.
                  what can I try to do?
                  thanks

                    Hi SistoDavideDiGruttola
                    Please provide more details:

                    1. how did you understand GPRS is worked or not, earlier, and what you see now?
                    2. how did you configure it earlier and what you tried now?
                    3. what android app you talking about?

                    namo now it works perfectly, thank you very much for great support

                    2 months later

                    Hi, i have same devices anda same problem. When select xexun (this received only coban protocol)
                    200105215203,+54911407xxxx,GPRMC,005239.000,A,3430.351,S,05840.770,W,000.0,000.0,060120,,,A*7C,F,,imei:359772032182422,10,111.1,F:4.79V,1,139,07554,054,11,0ABA,1ABC

                    y have this module and old(359772032182405) works in old plattaform and in this NOT. I tried many combinations, reducing imei to 12 digit... but device doesnt appears (only when send with manual packet sender coban protocol to this xexun port)

                    • namo replied to this.

                      JoseArcadioBuendia
                      Hello Jose!
                      Please connect your device to xexun channel, it should work on xexun protocol.
                      If something still will be wrong - check device's logs in toolbox and share parsing error details here.
                      Good luck!

                        6 days later

                        JoseArcadioBuendia
                        Well, then connect the device to my debug channel 193.193.165.37:25591, I will take a look

                          Write a Reply...