I took the time to update and improve the tracker firmware, including removing secret references. It is now running quite stably on an Arduino UNO and SIM808 EVB-V3.2.4.
However, some issues arose when adding a monitor: memory usage needs to be optimized, and the SIM808 EVB-V3.2.4 requires a manual startup each time, which isn’t practical for real-world use.
Next, I’ll optimize the memory usage and then switch to a more compact board, such as the Arduino Pro Micro, which has slightly more SRAM.
A new monitor and case have been installed for the Navigator. The multitouch monitor improves zooming and control in Organic Maps and includes a side panel for brightness adjustment.
The main Raspberry Pi board now features an extension HAT, which relocates all ports to the same side. This eliminates flimsy wiring, keeps the system more compact, and reduces depth in the case. As a result, the connections at the back are no longer stressed, making the entire setup far more stable than before.
While traveling in Norway, we had the chance to test the Go version. Although the launcher was running fine and the video stream was handled (after some effort) directly by the app, we noticed that Navit isn’t ideal for route planning or on-the-road location searches.
For instance, it was not possible to select a point without having a postal address, and the real-time location feature felt a bit awkward because the screen wouldn’t refresh until the point reached the edge of the map frame.
In the end, we switched to using OrganicMaps on our phones.
Since there don’t seem to be any good open-source or free options to replace Navit for desktop environments, I decided to switch to Android with LineageOS (Konstagang port).
This setup is essentially like having a phone, but it comes with its own pros and cons:
Cons:
Booting time is quite long, taking nearly a minute to load.
While the interface can be customized, it doesn’t allow for creating one entirely from scratch to meet specific needs.
Pro:
A wide selection of mobile-native apps (e.g., OBD2 interfaces, video recording, music players, sensor readers, etc.).
The ability to set up custom hardware buttons using the Raspberry Pi’s GPIO pinouts.
The overall scheme has been redesigned as well. An external USB hub now handles the screens, and a modem has been integrated directly into the Navigator case.
Additionally, an OBD2 Bluetooth scanner is activated via a relay connected to the Navigator’s switch.
Since a while without updates regarding the project, some news:
I decided to use Go instead of C++ for faster development and keep a reasonable lightweight. Main OS will be DietPi with i3, way more lighter than Raspian distros, even if need some more configuration, I am happy with this choice
The case and the connections need improvements, I want to merge most wires in a single socket.
There are some issues with the power feeding, powering the monitors outside the RPi does not seem to solve that, especially when all the peripherals are connected, may I will switch to a single screen.
