A well-known issue with Sprinters is water leakage and condensation above the cabin roof. In our case, water has infiltrated through two main sources:
The antenna mount, which was repaired shortly after we purchased the van.
Condensation drips, which we only discovered a few weeks ago.
The water drips directly onto the dome light, which also houses the alarm controls. This has caused short circuits and accelerated oxidation of the circuit board.
Since condensation is difficult to eliminate entirely, I’ve decided to coat the board with a PCB sealant as a protective measure.
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.
Some problems with the tracker has been solved, and I am now able to log time and coordinates in a database. Following the amended design:
Using CloudFront to redirect the non-SSL traffic didn’t work so I manually setup my server to accept non-SSL traffic on specific paths and redirect any other traffic to HTTPS.
A quick test with a API (written in PHP) has been successful, and the GPS data and timestamp has been recorded into the database (MySQL).
The GPRS connection still unstable and I am not 100% satisfied by the library (SFRobot_SIM808) and most likely I will create my own one using the AT commands.
While setting up the software and infrastructure for the Tracker, some problems have been discovered.
The main one is that the Sim808 doesn’t use SSL, or isn’t reliable while using it.
I tried some different solutions:
Redirect non-https connections using CloudFront
Creating a custom PHP API on my running servers
Both solutions have been unsuccessful, also because seems that the module is stuck with HTTP/1, generating some more problems while sending complex messages.
Maybe a firmware upgrade could solve this issue, I will see this week.
Following a picture of the board that I am using: Sim808 Evb V3.2
