Home Forums GPS Tracking Hardware Problem with integrating AIS -140 device (ITS protocol) with Traccar server

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #289
    Sunil HaridasSunil Haridas
    Participant

    Hi,

    We are using Traccar server to integrate AIS -140 based devices in India. I understand that AIS-140 (ITS) protocol is supported by Traccar . But we are facing problem with our integration. Earlier with Traccar installer on Ubuntu there was no data coming on the logs. We then compiled the latest source from Git and replaced the jar file in the existing installation and recently there was some junk data coming from the device but still the device is not able to send correct data to the server. The Traccar App is working correctly.
    We also created an account on demo.traccar.org and tried pointing the device there. Still there is no data coming.

    While checking further we find that the Login packet which is send first gets rejected by the server. Our tracking packet is compatible with the Traccar ITS protocol. So how can we configure the ITS decoder to ignore the Login packet so that Tracking packet is accepted anand dec. oded properly. Kindly suggest a solution. Thanks in advance.

    (1) Log File from our server (34.87.158.250 port 80) :

    2020-06-23 00:27:01 INFO: [aaa154f6] connected
    2020-06-23 00:29:38 INFO: [aaa154f6: its < 111.92.26.196] HEX: 0d0a
    2020-06-23 00:29:38 INFO: [aaa154f6: its < 111.92.26.196] HEX: 0d0a
    2020-06-23 00:29:44 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:29:45 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:29:46 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:29:46 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:29:46 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:29:46 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:30:01 INFO: [aaa154f6: its < 111.92.26.196] HEX: 0d0a
    2020-06-23 00:30:04 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:30:04 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:30:04 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:30:04 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:30:26 INFO: [aaa154f6: its < 111.92.26.196] HEX: 11110d0a
    2020-06-23 00:30:28 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:30:29 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:30:29 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:30:29 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:30:29 INFO: [aaa154f6: its < 111.92.26.196] HEX: fff4fffd06
    2020-06-23 00:30:37 INFO: [aaa154f6: its < 111.92.26.196] HEX: 04
    2020-06-23 00:30:37 INFO: [aaa154f6: its < 111.92.26.196] HEX: 040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404
    2020-06-23 00:30:37 INFO: [aaa154f6] disconnected

    (2) Log of test done on demo.traccar.org (40.112.128.183 Port: 80)

    [2020-06-25 14:45:22.452] OK
    [2020-06-25 14:45:22.462] AT+CIPSTART=2,”TCP”,”40.112.128.183″,”80″
    [2020-06-25 14:45:22.532]
    [2020-06-25 14:45:22.532] OK
    [2020-06-25 14:45:23.343]
    [2020-06-25 14:45:23.343] 2, CONNECT OK
    [2020-06-25 14:45:23.372] AT+CIPSEND=2
    [2020-06-25 14:45:23.412]
    [2020-06-25 14:45:23.412] > $,867157046499703,2863,12.870219,N,077.656509,E,,device.vltsecurity.com:5673,emergency.vltsecurity.com:5673,10,60,20,80,5.0,5.0,1.0,0.0,+919740335522,0,0,0,22,36,$E!
    [2020-06-25 14:45:24.333] 2, SEND OK
    [2020-06-25 14:45:24.372] SENT
    [2020-06-25 14:45:24.372] AT+CPMS=”SM”
    [2020-06-25 14:45:24.412]
    [2020-06-25 14:45:24.412] +CPMS: 0,20,0,20,0,20
    [2020-06-25 14:45:24.452]
    [2020-06-25 14:45:24.452] OK
    [2020-06-25 14:45:24.472] AT+CSQ
    [2020-06-25 14:45:24.482]
    [2020-06-25 14:45:24.482] +CSQ: 18,0
    [2020-06-25 14:45:24.512]
    [2020-06-25 14:45:24.512] OK
    [2020-06-25 14:45:24.532] AT+CENG?
    [2020-06-25 14:45:24.542]
    [2020-06-25 14:45:24.542] +RECEIVE,2,230:
    [2020-06-25 14:45:24.562] HTTP/1.1 400 Illegal character VCHAR=’,’
    [2020-06-25 14:45:24.612] Content-Type: text/html;charset=iso-8859-1
    [2020-06-25 14:45:24.652] Content-Length: 70
    [2020-06-25 14:45:24.687] Connection: close
    [2020-06-25 14:45:24.702] Server: Jetty(9.4.26.v20200117)
    [2020-06-25 14:45:24.732]
    [2020-06-25 14:45:24.732] <h1>Bad Message 400</h1>

    reason: Illegal character VCHAR=','

    [2020-06-25 14:45:24.820] +CENG: 3,0
    [2020-06-25 14:45:24.832]
    [2020-06-25 14:45:24.832] +CENG: 0,”404,71,09d0,2f10,31,35″
    [2020-06-25 14:45:24.882] +CENG: 1,”404,71,09d0,2f0f,26,14″
    [2020-06-25 14:45:24.912] +CENG: 2,”404,71,09d0,3302,43,12″
    [2020-06-25 14:45:24.962] +CENG: 3,”404,71,09d0,2f11,27,12″
    [2020-06-25 14:45:24.992] +CENG: 4,”,,0000,ffff,35,10″
    [2020-06-25 14:45:25.022] +CENG: 5,”404,71,09d0,2f60,00,09″
    [2020-06-25 14:45:25.072] +CENG: 6,”,,0000,ffff,00,06″
    [2020-06-25 14:45:25.102]
    [2020-06-25 14:45:25.102] OK
    [2020-06-25 14:45:25.102] AT+CIPSEND=2
    [2020-06-25 14:45:25.122]
    [2020-06-25 14:45:25.122] ERROR
    [2020-06-25 14:45:25.132] AT+CIPCLOSE=2,1
    [2020-06-25 14:45:25.182]
    [2020-06-25 14:45:25.182] 2, CLOSE OK
    [2020-06-25 14:45:25.202] AT+CIPSHUT
    [2020-06-25 14:45:25.492]
    [2020-06-25 14:45:25.492] SHUT OK
    [2020-06-25 14:45:25.502] GSM-CF
    [2020-06-25 14:45:25.522]
    [2020-06-25 14:45:25.522] NWFAILURE
    [2020-06-25 14:45:25.522] GSM-DF

    #290
    James JosephJames
    Keymaster

    Hi,

    Share the following information.

    1. The AIS140 device’s configuration (Server configuration) from the device check what it is and post it exactly as it is.

    2. You referred to login packets “Point that out in both the logs you shared in this topic above” please. Where do you see login packet in above logs.

    Also as we have already discussed these issues earlier, I would suggest you to please share exact information as requested and to take this on a step by step manner to avoid assumptions and conclusions.

    The best way to troubleshoot is to first rule out the possibilities !

    That being said, this is not a Traccar issue based on our understanding!

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.