-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no updates are sent #76
Comments
Hi Chrescht, please check your unit key under Units -> [Your unit] -> Options -> Remote Key. It must match the key set in firmware (tracker.h):
You can delete units under Settings -> Branding -> Allowed IMEI I hope this helps. |
Thanks for your fast answer.
|
It normally works out of the box. The key is saved on the first connect from the tracker. So it's not required to deal with it. It is there to add additional security to your data and to make sure data is received from your device. It is strange that you got key saved differently, could be that you made some manual requests for your IMEI number or key mismatch just happened by itself? In case you are using default firmware, simply set key in the web interface:
to
Please check our user guide for full tracker manual: https://github.com/geolink/opentracker/blob/master/docs/OpenTracker%202.4%20User%20Manual%201.4.pdf |
Thanks, will try. |
@Chrescht 18V shouldn't have killed it, max on the spec is 32V. Is it recognised when connected via USB? |
Please check the Troubleshooting paragraph in the User Manual. You can try to force erase and see if you get a serial port (COM) when you connect the USB cable to your PC. Then you can reload some firmware on it. |
Success, thanks guys! First I tried method 2, no success, but the first reset method seemed to have done the trick, I set remote key in tracker.h, uploaded the current firmware, set the APN by sms, then finally saw the correct GPS position in the LIVE map. |
Hi there,
my issue is I can't see any updates on the live map.
I did set the APN by sms command, also finally got to see the tracker's debug messages, and one of them is talking about a wrong key. What key would that be?
Also:
I'd be really happy to get this sorted out.
ps: I have no debug file available now, but I can send it later.
The text was updated successfully, but these errors were encountered: