Navigator #12

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.

 

USB Hub and OBD2 transmitter installation

Navigator #11

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.

Following some new socket for the v2 of the case.

Navigator #10

The Navigator has been installed in the Nautilus, the case is a bit small but fit perfectly if inside the cage!

Now I just need to create the arm for the driver’s screen and fix the GPS antenna.

As the hardware is ready, I can start to improve the software and start to move from the Python mock to a C++ version.

Navigator 9: Case ready to be installed!

After some buck converters burned out (and few nights), I have been able to setup all the components inside the case, and is now ready to be installed on board of the Nautilus.

Navigator 8: case improvements

A first version of the case has been printed and “tested”. Printing single panels and using glue to assembly has been successful, the glue does a good job.

Anyway I decided to improve the design adding better supports for the internal components and several amendments to improve ventilation and easy access to the Raspberry Pi SD Card.

 

Navigator case: update

All the components have been delivered and the first sketch of the case printed:

  • the case need to be shorter in height to fit
  • all the components can be places, enough room
  • the case cannot be printer in one shot, so need to be broken in several components (to avoid any deformation)
  • some measurements need to be adjusted
  • buck converters have been tested and are stable

Navigator, designs.

Following some schematics about data and power connections.And the schematic for the computer enclosure, will include the Raspberry, some step down converters, the A/V card and a fan for cooling.

Powering is controlled by a switch for now. Ideally the fan will have his own controller and the power off action managed by the software.

Won’t be bad to add a front USB port and a door to access the sd card and maybe a small monitor.

Following some images from the enclouse design.

 

Navigator, update

Long time from the latest post about the Campervan Computer System: Navigator.

The last week end I spent some time testing the wiring on the camper, and I had to find out that the previous tests did not include the A/V card (for the rear camera), currently powered by the Raspberry Pi.

This means that the system can’t boot properly due to lack of power. Raspberry Pi is not able to power two devices from usbs.

The two current buck converters that I planned to use are too bulky and not powerful enough anyway, so I had to consider some solutions:

  1. Using only one monitor
  2. Using two monitors but one only is touch-screen
  3. Create a custom board to feed each board separately

Obviously the best solution is the one that requires more work: number 3.

Creating a custom board will drastically reduce the size of the converter, solve any powering issue (one converter that have a single output for each module).

The design is in progress, it may be done purchasing pre-made boards, but not sure because it seems unusual having a stable 3A output on 5v.

Meanwhile, I had the chance to test the navigation system, and is faster than I expected.

Also, the 3D printer has been delivered and I can start to design the casing!


Everything must fit in this space (boards, power supply, wiring, connectors and fans)

Elegoo Neptune 3, not bad at all for the price! Still waiting for the filaments.