XT2469 Configuration Issue

Martha6 years ago

I've configured a few OBD devices XT2469 to Port #5138. I've also made sure that this UDP Port #5138 is allowed into the Traccar server I'm using, but I'm not receiving any information on the devices. I've check the log files multiple times during the day, but nothing.

I've read this post: https://www.traccar.org/forums/topic/xt2469-configuration/ so I added this line to the traccar.xml:
<entry key='xt2400protocol.config'>:wycfg pcr[0] 0016010304060708095793940a5813122e7d1714324a5a05</entry>
I tried connecting without this line as well, but I got no connection anyway. is this line needed?
I found another post that seems to have never modified the traccar.xml file: https://github.com/traccar/traccar/issues/3168

Martha6 years ago

There are other 2400 devices that have a ASCll firmware and not a Binary/Hex that the new XT2469 has. Do you mind clarifying if the port Traccar is using is dedicated for the XT2469 and not for other 2400 devices like the XT2460 or XT2450.

I'm using the #5138 port based on what this page indicated: https://www.traccar.org/devices/ -> Device: Xirgo XT2400 Series, Protocol: xt2400, Port: 5138

Anton Tananaev6 years ago

Do you see data from device(s) in the log?

Martha6 years ago

I do see other devices using other ports, but nothing from Port 5138. I've also verified that the UDP 5138 is open in the server I have Traccar installed in. I used the PortQuery utility (Portqry.exe) and I received test messages from PortQuery on Traccars' logs, but nothing from the XT2469 devices.

Is port 5138 dedicated to XT2469 (Binary/Hex)? I should probably receive some message anyhow, right?

Martha6 years ago

Update:
I'm now receiving data to the 5138 port:

2019-05-08 10:02:47  INFO: [d6dea1ff: 5138 < 162.244.250.195] HEX: 000b02501d815cd2e1860192934ffb39c5b2001c00b4000a074d03270f0600008d6b00dd8d001f025cd2e12c032000ec
2019-05-08 10:02:51  INFO: [d6dea1ff: 5138 < 162.244.250.195] HEX: 000b02501d015cd2e18701929341fb39c58f001c008c000a090903330c0900008d6b00dd8d001f025cd2e12c032000ed
2019-05-08 10:03:06  INFO: [d6dea1ff: 5138 < 162.244.250.195] HEX: 000b02501d0c5cd2e19901929341fb39c54300240000000a0bde0000100600008d8000dd7f001f025cd2e12c032000ee

But I don't see the device's info on the web app; I've added the OBD with its IMEI as identifier in the web app.
Am I missing something on the traccar.xml file?
I had this entry all this time:

entry key='xt2400protocol.config' :wycfg pcr[0] 0016010304060708095793940a5813122e7d1714324a5a05 /entry
Anton Tananaev6 years ago

Configuration doesn't seem correct.

Martha6 years ago

Are you referring to the entry line on traccar.xml? Is this entry required?

Anton Tananaev6 years ago

Configuration is required, most likely.

Martha6 years ago

I've just added all the configuration/commands I have on the devices for package receipts to the traccar.xml file as well

entry key='xt2400protocol.config'
        :wycfg pcr[0] 0016010304060708095793940a5813122e7d1714324a5a05
        :wycfg pcr[1] 01100103044106070809570a13122e171405
        :wycfg pcr[2] 0216010304191a1b1c1d1e1f20212223245813122e171405
        :wycfg pcr[3] 030e0103044a4b4c445813122e171405
        :wycfg pcr[15] 0f1101030406070809570a13122e1714536905
        :wycfg pcr[126] 7e090103040607086b6c05
        :wycfg pcr[127] 7f11010304060708131214156a171653186505
    /entry

I also send you (support@traccar.org) the complete list of configuration/commands I have on the OBD devices. Could you please take a look at it, what is it that I did incorrect?

Anton Tananaev6 years ago

Where did you find the configuration key?

Martha6 years ago

I got it from another post https://www.traccar.org/forums/topic/xt2469-configuration/ but I verified it that it exists on the java files. Is it something different?

Anton Tananaev6 years ago

How did you verify it exactly?

Martha6 years ago

I only checked if the reference/key actually exists on the java files by looking on the Traccar's Github repo, nothing else. Is it wrong?

Anton Tananaev6 years ago

Can you please provide a link to the place where you found the key.

Martha6 years ago