Freematics Traccar Edition

Anton Tananaev4 years ago

UDP is actually the correct option. Do you want to post your original config somewhere so we can take a look?

oriebirj4 years ago
Anton Tananaev4 years ago

So which one are you using? And also I don't see server address in either. Am I missing something?

oriebirj4 years ago

dont know why was getting and error from this page of too many requests...

you can consider the config.h
server I removed coz its my own and its not totally secured as I'm doing this tests
lets me know if you really need it

Anton Tananaev4 years ago

You could have at least provided demo server there as an example. As it is the configs are completely invalid because you removed pretty much the only thing that you actually need to configure.

oriebirj4 years ago

I was unable to reply sooner because since yesterday I keep on getting this too many requests errors from this page.

You are right, i could have done that. I removed it for security reasons, I hope you understand.
Sorry I didnt clearly mentioned.
Once I reach home later I will update and hopefully will be able to post it here, if I dont get this annoying errors.

oriebirj4 years ago

Now connection is finally solved.
Port forward screwed up.

but..

2021-11-01 22:03:28  INFO: [a9065d0b: freematics < 178.152.180.8] HEX: 453539313050473923303a3132353332372c32343a3336342c32303a2d302e33333b302e35383b312e33352c38323a34362c2a3335
2021-11-01 22:03:28  INFO: [a9065d0b] id: E5910PG9, time: 2021-11-01 22:03:28, lat: 0.00000, lon: 0.00000, course: 0.0
2021-11-01 22:03:33  INFO: [a9065d0b: freematics < 178.152.180.8] HEX: 453539313050473923303a3133303332372c32343a3336362c32303a2d302e33333b302e35383b312e33342c38323a34362c2a3332
2021-11-01 22:03:33  INFO: [a9065d0b] id: E5910PG9, time: 2021-11-01 22:03:33, lat: 0.00000, lon: 0.00000, course: 0.0
2021-11-01 22:03:38  INFO: [a9065d0b: freematics < 178.152.180.8] HEX: 453539313050473923303a3133353332372c32343a3336362c32303a2d302e33313b302e35373b312e33352c38323a34362c2a3335
2021-11-01 22:03:38  INFO: [a9065d0b] id: E5910PG9, time: 2021-11-01 22:03:38, lat: 0.00000, lon: 0.00000, course: 0.0
2021-11-01 22:03:43  INFO: [a9065d0b: freematics < 178.152.180.8] HEX: 453539313050473923303a3134303332372c32343a3336372c32303a2d302e33333b302e35373b312e33342c38323a34362c2a3333
2021-11-01 22:03:43  INFO: [a9065d0b] id: E5910PG9, time: 2021-11-01 22:03:43, lat: 0.00000, lon: 0.00000, course: 0.0

getting lat: 0.00000, lon: 0.00000 on both demo and own server.

:(

Anton Tananaev4 years ago

OK, it sounds like you are almost there. Zero coordinates usually indicate that the device doesn't have a location fix. Are you testing it outdoors with clear sky visibility?

oriebirj4 years ago

Yes I tried 2 things.
Cellular GNSS and after with external antenna connected placed device outside in clear sky.
Same result.

Anton Tananaev4 years ago

Initial cold fix might in some cases take up to 15 minutes or even more. If it still doesn't work, it could indicate some hardware problem. Would be good to get some GPS module output logging.

oriebirj4 years ago

Where can I get that log Anton?
I’m unable to get the SD working for some reason.
Men this is hardcore. At least one understand this properly, I hope!

Anton Tananaev4 years ago

I don't think it's logged by default. Just throwing some ideas. I don't actually know how to do it. You probably need to add some extra code to the firmware.

oriebirj4 years ago

Eheheheh
Cool. I’ll try to figure it out.
I remember reading something about this issue.
Will share if I find something relevant.