Audi MHI2 RVC fullscreen patch: Difference between revisions

From MIB-Helper.com Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 32: Line 32:
  scp root@10.173.189.1:/mnt/system/etc/eso/production/displaymanager.json ~/MHI2_backup/displaymanager.json
  scp root@10.173.189.1:/mnt/system/etc/eso/production/displaymanager.json ~/MHI2_backup/displaymanager.json


== Changing FBAS stream size and position ==
== Modifications ==
That's easy. Duplicate the <code>displaymanager.json</code> file and call it <code>displaymanager.json.modified</code>. Now open the <code>displaymanager.json.modified</code> with text or code editor and look for section related to the rear view camera. It should look like this:
=== Changing FBAS stream size and position ===
That's easy. Duplicate the <code>displaymanager.json</code> file and call it <code>displaymanager_modified.json</code>. Now open the <code>displaymanager_modified.json</code> with text or code editor and look for section related to the rear view camera. It should look like this:


  #<-
  #<-
Line 87: Line 88:
  },
  },


== Adjusting textures ==
=== Changing opacity of PNG file ===
=== png ===
Duplicate the <code>2100002.png</code> file and call it <code>2100002_modified.png</code>. Open the <code>2100002_modified.png</code> file with image editor of your choice (GIMP, Photoshop...) and change opacity of the image to 25%.
''TODO''


=== kzb ===
=== Changing opacity of asset inside KZB container ===
''TODO''
''TODO''


== Uploading modified files to unit ==
== Uploading modified files to unit ==

Revision as of 13:03, 11 August 2025

Audi MMI MHI2 is set up in such a way that rear view camera is shown in split view. Camera stream is shown on the left side of the display, when the right side is occupied by parking sensors visualisation or AreaView image in equipped cars.

Audi MHI2 RVC fullscreen hack
Audi MHI2 RVC fullscreen hack

If your car is not equipped with AreaView (you have for example Audi A3 8V where AreaView was not available), you are stuck with RVC image not on fullscreen. Luckily there's a way around it!

Access MHI2 main unit file system

Connection

You can do this via WLAN, USB-to-Ethernet DLink DUB-E100 adapter, or via TX/RX connection from QuadLock.

Protocol

You can use TelNet (unit already supports it) or SSH (service needs to be installed via More Incredible Bash or MIB2 Toolbox).

Root user password

Root user password can be found in the Password_List_V4.0.pdf document from More Incredible Bash repo. You can also use More Incredible Bash to change the root password to harman_f for your convenience.

Backup original files

Local copy inside MHI2 unit

ssh root@10.173.189.1

mount -uw /net/mmx/mnt/app && mount -uw /net/mmx/mnt/system #enable filesystem write mode

cp /etc/eso/production/displaymanager.json /etc/eso/production/displaymanager.json.original

cp /eso/hmi/lsd/images/HMIEarlyAppsEvoHighScale/2100002.png /eso/hmi/lsd/images/HMIEarlyAppsEvoHighScale/2100002.png.original

Remote copy on your computer

mkdir ~/MHI2_backup

scp root@10.173.189.1:/mnt/app/eso/hmi/lsd/images/HMIEarlyAppsEvoHighScale/2100002.png ~/MHI2_backup/2100002.png

scp root@10.173.189.1:/mnt/system/etc/eso/production/displaymanager.json ~/MHI2_backup/displaymanager.json

Modifications

Changing FBAS stream size and position

That's easy. Duplicate the displaymanager.json file and call it displaymanager_modified.json. Now open the displaymanager_modified.json with text or code editor and look for section related to the rear view camera. It should look like this:

#<-

#this block configures the RVC
#	"norm": the norm to use, "AUTO", "NTSC_443", "NTSC_M", "PAL"
#	"deinterlace": the deinterlace mode "WEAVE", "BOB", "TEMP_FRAME", "TEMP_FIELD"
#	"source": x,y,w,h
#	"target": x,y,w,h 
#	"brightness": integer representing the brightness value
#	"color": integer representing the color value
#	"saturation": integer representing the saturation value
#	"hue": integer representing the hue value
 "rvc" : {
  "norm" : "AUTO",
  "deinterlace" : "WEAVE",
  "source":{
   "x": 96,
   "y": 48,
   "w": 528,
   "h": 384
  },
  "target":{
   "x": 0,
   "y": 54,
   "w": 528,
   "h": 384
  },
  "brightness": 0,
  "color": 0,
  "saturation": 0,
  "hue": 0
 },

We are going to change two things: source and target parameters. source defines how to crop the original video stream from the camera, and target defines where and how to display it.

Let's start with expanding the source view. RVC camera uses an analog NTSC stream. Full resolution of such video source is 720 by 480 pixel, so let's remove the original cropping and expand the field of view.

"source":{
 "x": 0,
 "y": 0,
 "w": 720,
 "h": 480
},

And now let's make sure that the image is stretched to the full width od the display..

"target":{
 "x": 0,
 "y": 0,
 "w": 800,
 "h": 438
},

Changing opacity of PNG file

Duplicate the 2100002.png file and call it 2100002_modified.png. Open the 2100002_modified.png file with image editor of your choice (GIMP, Photoshop...) and change opacity of the image to 25%.

Changing opacity of asset inside KZB container

TODO

Uploading modified files to unit