Settings:
Tracker ID: 352353084656914
Server host: 193.193.165.37
Server port: 32062
Device Category: Hardware
Device Type: Bitrek

The problem is that tracker can’t send gps data to those settings.
Receiving:
TASK MODEM: SSEND NO ANS
TASK MAYAK: MODEM CMD ERR: 138

Can you help, please?

  • dapi replied to this.
    IgorNikonorov changed the title to Tracker bitrek cicada (bitrek bi 310) can't send location info .

    IgorNikonorov Hello.
    First of all you should identify what kind of traker model you have. If it is Bitrek then in the units settings (Unit menu - Settings - Common Settings) you should select
    Device Category – Hardware
    Device Type – Bitrek (please make sure you specified this type)
    Also when configuring your tracker you can try to indicate DNS server format instead of IP format 193.193.165.37 (to see it, click the IP button next to the server value). You can read more information here https://forum.gps-trace.com/d/586-ip-and-dns-server-formats-in-the-application
    Also you can try to identify your tracker on id.wialon.net as one of the devices Bitrek. If your tracker is determined, take a screenshot, write down the name of the model of the tracker and the identified ID (may coincide with the IMEI, may be part of it with zero or without).
    After that, return to the application in the unit settings (unit menu - Settings - Common Settings), specify the determined model and ID. After that, configure the tracker on the defined server and port.
    In case the problem is not solved please write to us via support@gps-trace.com and mention your login, tracker IMEI and model.

        dapi
        Thank you for your answer.
        My tracker model is: “Bitrek BI 310 cicada”
        My settings exactly that you specify in your answer:
        Device Category: Hardware
        Device Type: BI 310 CICADA
        It seems that my tracker doesn’t support DNS that’s why I’m using IP: 193.193.165.37
        Port: 32062
        Unique ID: 352353084656914

        I already tried to identify Tracker ID with id.wialon.net and it’s OK tracker ID was in the list with ID: 352353084656914
        Also, I have tried to connect the tracker to https://flespi.io/ and there in logs, I received the error:

        error_text : "000238 [bitrek:57:4] in @tcp_login: {ext} TCP login: failed to parse device IMEI"
event_code : 102

        Also, I have grabbed HTTP package from my tracker that it sends to the server:

        IMEI=352353084656914&COPS=0,2,\x2225503\x22&GPGGA=085801.204,5022.9954,N,03022.8644,E,1,3,3.07,122.1,M,27.9,M,,*5C&GPGSA=A,2,16,10,21,,,,,,,,,,3.23,3.07,1.00*01&GPVTG=311.15,T,,M,0.04,N,0.07,K,A*39&GPZDA=085801.204,27,08,2020,,*59&sens[0200]=BI310 M16A VER 3.4&sens[0201]=8938003992736758861&sens[0100]=8&sens[0101]=254&sens[0102]=0&sens[0103]=110&sens[0104]=2&sens[0105]=87&sens[0106]=66&sens[0107]=22&sens[0108]=2&sens[0109]=42&sens[0110]=307&sens[0111]=0&sens[0112]=132&sens[0113]=10438&par[0100]=1&par[0101]=0&par[0104]=0&par[0200]=80&par[0201]=60&par[0202]=10&par[0203]=80&par[0204]=110&par[0206]=60&par[0207]=60&par[0211]=5&par[0212]=10&par[0213]=15&par[0215]=30&par[0500]=&par[0501]=&par[0502]=&par[0503]=&par[0504]=178.158.245.162&par[0505]=&par[0506]=38063*******&par[0512]=11111&par[0513]=25501&par[0514]=25503&par[0515]=25506&par[0516]=&par[0517]=&par[0518]=internet&par[0519]=&par[0520]=&par[0521]=&par[0522]=&par[0523]=&par[0524]=&par[0525]=&par[0526]=&par[0527]=&par[0528]=&par[0529]=&par[0530]=&par[0531]=&par[0532]=

        Maybe it helps with solving my problem.
        Thank you.

        • dapi replied to this.

            IgorNikonorov Hello.
            Unfortunately the protocol of your device does not coincide with the protocol of Bitrek devices that are supported by flespi, i.e. it will not work with flespi.
            But you can try to connect your device as one of devices of Legacy category.
            For this select in the units settings:
            Device Category - Legacy
            Device Type – Bitrek
            And then configure your device to:
            Server Host 193.193.165.166
            Port 20667
            Please write us back about the results.

                dapi
                I already tried to use the legacy category and Bitrek device the result was that the device was connecting to the server it was online, but geo-position was missed.
                But I used
                IP 193.193.165.166
                Port: 20700

                  Sorry but It seems that it works with
                  IP 193.193.165.166
                  Port: 20700

                  Only when position collated by BSM it’s not location.

                  Thank you for your help.

                  • dapi replied to this.