TV Free fuer PC am RNS-E | Posts 32+

I've been working on Video In Motion for the RNS-E 2010 (model 193) for quite some time, but unfortunately, there isn't a known VIM hack available for it.

The RNS-E system reads the vehicle speed via the CAN bus using identifier 0x359 (in the Audi A3 8PA MJ 2011).
The speed is not determined by the first two bytes, but rather by bytes 3 and 4. These bytes count the rotational impulses of the wheels. Based on the wheel circumference and these impulses, the RNS calculates the vehicle's speed.

If the speed exceeds 5 km/h, the TV input is disabled, and a message appears indicating that the TV picture is turned off for safety reasons during driving. Additionally, the CAN messages sent to the CAN bus during TV mode are no longer transmitted. Only the two top buttons (Next and Previous) continue to send signals.

VIM can be easily disabled by blocking ID 0x359, but in that case, navigation will no longer function (the map and arrow will not move) because the RNS-E system perceives the vehicle as being stationary.

ID 0x359 does not need to be completely blocked; it is sufficient to no longer modify bytes 3 and 4 (no change means no rotational impulses, resulting in standstill). Furthermore, it is pointless to make the RNS-E believe that the speed is less than 5 km/h, as the navigation system will always lag behind.

Currently, I've implemented a solution where the ID is blocked or filtered only when the RNS-E is in TV mode.
If you switch to something else, like the radio, the navigation system will start working again.

In short, running "proper" VIM on the RNS-E 2010 is not possible .


Besides the CAN bus topic, I'm currently working on directly controlling the display of the RNS-E, meaning without using a TV input. If that works, we can completely eliminate the need for a Video Interface Module (VIM), because the display would simply be used as a monitor for something like a car PC. The display would then either show the RNS-E interface as usual, or it would display what's on the PC.

The components have been ordered, and I'll be able to provide more information next week...

Cool project .

CAN-Diagnose wrote:

Cool project+1

Do you mean VIM or the display driver?

[Translating...]

VIM

I haven't given up yet, and I am currently testing several scenarios with various modifications to ID 0x359.

Here's my update: VIM does not work with the RNS-E 2010+.

The speed signal must either be blocked or limited to 5 km/h. Both of these actions will cause the navigation system to stop working.


My solution for controlling the display is finally working!
Here's the translation:

"In other words, I have developed a converter board that directly controls the RNS-E display. The board is installed inside the RNS-E and connected to the main circuit board. I connect a Raspberry Pi to the board via HDMI."
"This allows me to use the RNS-E display with its full resolution on the Raspberry Pi, achieving a perfect pixel-by-pixel image (800x480)."
A multiplexer is mounted on the circuit board and switches between the RNS-E display connection and the Raspberry Pi display connection.

Currently, the switchover is controlled by a button, but in the future it will be done via CAN bus or radio control.

The nice thing about it is that VIM is no longer necessary because only the display of the RNS-E unit is being used for the media PC.