Intrigued, we decided to concentrate on Traccar and dig a little deeper. It sported a very good rating and its creators’ assurances of the high efficiency of the server. The latter caught our attention being free, written in Java and continuously supported. Our search yielded 3 names that appeared to best fit these prerequisites: OpenGTS, GPSWOX, and Traccar. Continuous support and comprehensive documentation.Functionality range covering our requirements,.Open Source code – to enable modifications of certain functionalities as the project develops,.Price – free tool being most preferable,.In our research, we set the following as priorities: Popular servers, opinions, pros and cons, are all available in abundance. Good old Google yields more than enough in terms of comparisons. How do you find a ready-made solution to meet your needs? This led us to turn our focus to finding what’s at our disposal in terms of ready-made servers meeting the requirements. More work for us, and higher cost to the client. The downside of a custom solution was lengthy and resource heavy process of implementation.Īdditionally, a custom made server would require thorough preparation, highly optimized source code and continuous support. This would let us avoid the issue, where we wouldn’t be able to implement a functionality due to Open Source server’s deficiencies. ![]() The obvious advantage here was full control over the server’s set of functionalities. First, we looked at the option of writing our own solution. Functionalities and requirements were put against capabilities each of the solutions had. To answer this we took the project apart for analysis. Is it better to create your own solution or use an Open Source server? Which one do you choose? We had to ask ourselves this very question when recently we got a project that required receiving information about devices’ location. We either develop our own solution to receive and send GPS data or use an existing service. There are two ways of creating mobile and web apps integrated with a geolocation server, like eg. ![]() In 2019 the prompt “Do you want the app to use this device’s location?” can pop up in a kids’ coloring app. 10-15 years ago hardly any apps used location. Is it a social app? Obviously, location is crucial. Still, it’s going to need location service. You might not even know it yet, your app might be at a stage where it’s just an inkling of a future idea. Note that some H02-based devices send a mix of text and binary messages. If your device is using H02 protocol (correct port 5013), decoded message text would start with *HQ, and end with a number sign ( #). If your device is using GPS103 protocol (correct port 5001), decoded message text would start with imei: and end with a semi-colon ( ). Note that there are some other protocols that use 7e, so it's not a guaranteed match. If your device is using Huabao protocol (correct port 5015), HEX samples will start and end with 7e. If protocol is text-based, you have to convert HEX to text first. Once you have some samples and you are sure those samples are from your device, you can try matching them with common patterns below or compare to test cases we have for various protocols: Find HEX message from the device in the log file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |