et300 gps device

how to connect this et300 gps device , it is working with my car but i am unable to connect it with traccar,

can anyone help me ?

regards

http://p.globalsources.com/IMAGES/PDT/SPEC/860/K1149125860.pdf

https://www.youtube.com/watch?v=66hmQ5qZAfs

1. What ports have you tried?
2. Provide HEX samples.
3. Provide protocol documentation.

i have tried all the ports available in this below page , and also port forward them in my router .
https://www.traccar.org/clones/

how to provide hex samples , if it can be connected with traccar then only i can get the hex samples , am i right ?

and it is a chinese device so there is no documentations

all i got from the internet is those above links .

help

Yes, you need to configure it to report data to Traccar first.

what are the requirements to send the data first to the traccar server ?

is this pdf file helpful ?
http://p.globalsources.com/IMAGES/PDT/SPEC/860/K1149125860.pdf

what else do i need ?

somebody please help me ,

i am unable to connect it with traccar which i am running in my HASSIO , i have tried many different ports ,

one major problem i m facing is i dont have the device identifier or device id , i only have the IMEI of that device ,

is it possible to connect any gps device without its IDENTIFIER.

Share as many details as possible so we can be able to offer some sort of help.
how did you configure it?
have some hex samples?

after configuring many devices with little differences in identifier , now i am getting this hex code.

now can u help

2019-03-12 22:40:15  INFO: [2bccd7dd: 5036 < 1.187.84.187] HEX: 78781f1213030d010a0ec702f65bd2080fc2ec0015180194005b97002f74006a2e260d0a
2019-03-12 22:40:15  INFO: [2bccd7dd] disconnected
2019-03-12 22:40:15  INFO: [39dba606] connected
2019-03-12 22:40:15  INFO: [39dba606: 5036 < 1.187.84.187] HEX: 78780d010868003030894104006cb2950d0a
2019-03-12 22:40:25  INFO: [39dba606: 5036 < 1.187.84.187] HEX: 78780a134406040002006d14be0d0a
2019-03-12 22:40:35  INFO: [39dba606] disconnected
2019-03-12 22:40:36  INFO: [d99fd271] connected
2019-03-12 22:40:36  INFO: [d99fd271: 5036 < 1.187.84.187] HEX: 78780d010868003030894104006f800e0d0a
2019-03-12 22:40:45  INFO: [d99fd271: 5036 < 1.187.84.187] HEX: 78780a1344060400020070dfda0d0a
2019-03-12 22:40:55  INFO: [d99fd271] disconnected
2019-03-12 22:40:55  INFO: [1c73eac4] connected
2019-03-12 22:40:56  INFO: [1c73eac4: 5036 < 1.187.84.187] HEX: 78780d01086800303089410400724b6a0d0a
2019-03-12 22:41:13  INFO: [1c73eac4: 5036 < 1.187.84.187] HEX: 78780a1344060400020073ed410d0a
2019-03-12 22:41:16  INFO: [1c73eac4] disconnected
2019-03-12 22:41:16  INFO: [d578572c] connected
2019-03-12 22:41:16  INFO: [d578572c: 5036 < 1.187.84.187] HEX: 78780d01086800303089410400753fd50d0a
2019-03-12 22:41:41  INFO: [d578572c: 5036 < 1.187.84.187] HEX: 78780a1344060400020076baec0d0a
2019-03-12 22:41:41  INFO: [d578572c] disconnected
2019-03-12 22:41:42  INFO: [92816ee3] connected
2019-03-12 22:41:42  INFO: [92816ee3: 5036 < 1.187.84.187] HEX: 78780d0108680030308941040078e4300d0a
2019-03-12 22:41:45  INFO: [92816ee3: 5036 < 1.187.84.187] HEX: 78780a1344060400020079421b0d0a
2019-03-12 22:41:55  INFO: [92816ee3] disconnected
2019-03-12 22:41:56  INFO: [e171c98e] connected
2019-03-12 22:41:56  INFO: [e171c98e: 5036 < 1.187.84.187] HEX: 78780d010868003030894104007bd6ab0d0a

I would recommend you to carefully read documentation next time. Your device is using GT06 protocol, so correct port is 5023.

@Anton

thanks it worked ,
i have read many documents but didnt find any way to find those details and can u tell me what i left in the docs ?