Ottonavi HU: How to customize (a bit) the UI

Yup; even the old 2.78.10 we got on Prius has the same bug.

 

Gentlemen, start your engines!

Last week, a very knowledgeable friend of ours (who wants to remain anomymous for now) has sent us the Holy Grail:
a copy of the *official* RoadRover RRUI editor.
I don't know how it has been acquired but it seems legit.

The only problem was that the package was incomplete; in fact, not running at all...
So I took a closer look, figured out what was missing (basically around 2000 strings...) and crafted some C++ magic into it to fix it.
I finally managed this morning to make the whole thing run properly on a PC. I think...

The result is spectacular!
Here's a screenshot:



So now I'm sharing the joy with you to see what you artists can do with it.
Here's the package: http://dl.dropbox.com/u/63503986/RRUIEditor-v1.zip

This is a full blown official RoadRover RRUI editor that will let you build RRUI files in a very user friendly way.
Now you can truly see what the fields are, their meanings, the different options and possibilities, etc.
You can drag, copy controls, even add new ones, etc. You can customize almost everything.
It has also other features which I don't even know what they do yet. It even generates source code! He he.

BUT BEWARE: THERE ARE A FEW GLITCHES...
- it seems to mess up a bit with Aero on Windows7 (preview icons not working); may be it's my settings...
- there is some doc but it's very limited: see file RRUIEditor.txt
- editor is only in English for now; support for German or others would be very easy to add...
- it seems to crash when you try to access a few specific screens (MP4, VOICE) ; don't know why.
- it can read both RRUI version 4 and 5 but only outputs version 5; make sure you have an appropriate UI shell

The last problem is important for Ottonavi users with UI shell 2.78.10 which reads only version 4.
It means you won't be able to use those new RRUI files unless you upgrade your UI shell to a higher version.
Look at the post #1 (FAQ) if you want to upgrade.

The other possibility is I will try to add an option to the previous RRUITool so it can convert those version 5 files back to version 4.
That should not take too long.

In the mean time, enjoy!

 

The editor seems to show what's available for every car; doesn't mean it will work for Prius. In fact, I don't think so because this field is already there in 2.78.10 and it doesn't show up.

About the font, couldn't find anything... it seems to be stuck on Arial.
Although I know it's registering 4 fonts; probably for Windows underneath...
Unless we do surgery to Manager.exe or override the fonts altogether...
I know you wanted this...

Sorry. :-(

 

Hello Mbarkh,

wow; lots of testing you have done!
I appreciate you take the time to post your experience; some interesting info.

As for the screens: the .rrrui file contains all the possible screens for many units/cars; not just the Ottonavi for Prius. So some of the screens will never be accessible or functional.

As for the MCU update tool: I experienced the same thing. To me, it was reassuring to find out that the old one can always do the job in case of problem.

As for Bluetooth quality, mine is OK; doesn't sound bad at all I was told.
But some people are complaining about the sound quality on the other side.
This may has to do with where you put your mic; I put mine on top of the steering wheel as recommanded by Toyota in their installation sheet.

As for Audio, the G2 unit only has the 3 bars: Bass, Middle, Treble.
This is hardware related (that's what the Audio chip is capable of) as reported by the MCU.
Even if you enable somehow the Equalizer screen, you will never get it to work because there is no hardware underneath to support it.

Question: you said: *BTW I note that on UI 2.78.10 you can adjust equalizer for every mode independent*
How did you get to that? Screenshot?

 

Ahhh...

RRUITool + RRUIEditor are going to be a nice pair of tools together.

My next step is to modify the RRUITool so we can convert the RRUIEditor .rrui files (which are version 0.5) to version 0.4.
This way we will be able to enjoy any skins on the UI Shell 2.78.10.
We won't need to install a new UI Shell.
I should be done tonight I think.

Using the RRUIEditor, I was able to complete almost 99% of the RRUI file format.
Take a look especially at the control styles at the end.
You can even customize the clock hands!

More later...



RRUI FILE
----------
Note: there are just a few fields that are still unknown; most probably they have no significant use.
For more hints about the meaning and the format of each field, take a look at the RRUIEditor.

There are 2 versions of the RRUI known so far: 0.4 et 0.5.
0.4 seems to be used for UI Shell 2.78.10.
0.5 has been used for other UI Shell after that.

The format of the file seems to have been based previously on TAGS.
But it also contains non-tagged sequences of bytes.
The TAGS and sequences are read serially from the beginning; no direct access.
A TAG is a sequence of 4 bytes that identifies the next sequence of <len> bytes as a particular data type.

Here are the 4 TAGS known to date.
TAG_ULONG32 00 len 00 00 // ULONG32 Unsigned Integer 32-bit len=4 bytes
TAG_SLONG32 01 len 00 00 // SLONG32 Signed Integer 32-bit len=4 bytes
TAG_STRING 02 len 00 00 // STRING Unicode string len chars
TAG_RECTANGLE 03 len 00 00 // RECTANGLE (X1,Y1,Width,Height) len=16 bytes (all unsigned integer)
BLOCK just a sequence of bytes (length depends on context)

RRUI FILE FORMAT
----------------------------------------------------------------------------
FILE HEADER
TAG_STRING UI Version number
TAG_ULONG32 ??????? (Always e8 00 00 00)
TAG_STRING UI Name (ex: black orange)
TAG_STRING UI Name in Chinese
TAG_ULONG32 ID Picture Cover (the id of the picture that appears when you select a skin)
TAG_STRING Copyright
TAG_ULONG32 size of the Picture Cover data
PICTURE_DATA data of the Picture Cover

SCREENS HEADER
TAG_ULONG32 ??????? (always 0 ?)
TAG_ULONG32 ??????? (may be number of active elements in the file)
TAG_SLONG32 Number of screens

SCREEN HEADER
TAG_ULONG32 ID of this Screen
TAG_ULONG32 ID of Picture background
TAG_RECTANGLE X1, Y1, Width, Height
TAG_ULONG32 SP1 // Control Window Style
1 CWS_3D_BORDER
2 CWS_OUT_TOP_TO_BOTTOM
4 CWS_OUT_BOTTOM_TO_TOP
8 CWS_OUT_LEFT_TO_RIGHT
10 CWS_OUT_RIGHT_TO_LEFT
20 CWS_ROUND_RECT
TAG_ULONG32 SP2 ???????? // always 0
TAG_ULONG32 SP3 ???????? // always 0
TAG_SLONG32 Number of ELEMENTS

ELEMENT HEADER
ULONG32 ID Element (if =0 don't display element)
ULONG32 ID Text to display (0= no text)
ULONG32 ID Picture Front Off
ULONG32 ID Picture Background Off
ULONG32 ID Picture Background ON
ULONG32 X1
ULONG32 X2
ULONG32 Y1
ULONG32 Y2
ULONG32 EP1 (Control Styles... see below...)
ULONG32 COLOR NORMAL (ex: 00 bb gg rr)
ULONG32 COLOR SELECTED
ULONG32 COLOR TOUCHED
ULONG32 EP2 -
00 00 00 00
xx Icon Span
xx Text Span
xx Border width (sometimes specific to element)
ULONG32 ID Picture Front ON
ULONG32 Ptr to FONT DATA 0=NO FONT DATA
[20 bytes ] Used only for version 0.5
Ex: 00 00 00 00 tt 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
(tt==tab order for icons, etc)
FONT_DATA Font data [76 bytes] (TYPEFACE=[18,70],FONTNAME,......,FONTWEIGHT=[0=dont care, 400,500,600, 900=bold], ITALIC[0,1])
ELEMENT HEADER...
.
.
.
ELEMENT HEADER...

SCREEN HEADER...
.
.
.
SCREEN HEADER...

PICTURES HEADER
SLONG32 Number of pictures
PICTURE HEADER
TAG_ULONG32 ID Picture
TAG_SLONG32 Width
TAG_SLONG32 Height
TAG_SLONG32 Size in bytes of picture data
PICTURE_DATA picture data: jpg or png file
TAG_STRING original name of the file
PICTURE HEADER...
.
.
.
PICTURE HEADER...

----------------------------------------------------------
CONTROL STYLES; (Bits that can be OR'ed together): 1,2,4,8,16,32...

Control Clock Style
CCS_SHOW_SECOND_HAND
CCS_DRAW_CENTER
CCS_DRAW_HAND_SHADOW

Control String Style
CSS_LEFT
CSS_CENTER
CSS_RIGHT
CSS_TEXT_SHADOW
CSS_TEST_ROUND_BK
CSS_LED_NUMBER

Control Picture Style
CPS_STRETCH
CPS_CENTER
CPS_STATIC
CPS_BORDER
CPS_STATE_H
CPS_STATE_V
CPS_STATE_DEMO
CPS_COLOR

Control Button Style
CBS_IMAGE_ON_LEFT
CBS_IMAGE_ON_RIGHT
CBS_IMAGE_ON_TOP
CBS_IMAGE_ON_BOTTOM
CBS_IMAGE_ON_CENTER
CBS_NO_TEXT
CBS_TEXT_LEFT
CBS_TEXTE_RIZGHT
CBS_TEXT_CENTER
CBS_TEXT_SHADOW
CBS_TEXT_GLOW
CBS_TEXT_ROUND_BK
CBS_TRANSPARENT
CBS_3D_BORDER
CBS_ROUND_BORDER
CBS_TRANS_INVALID
CBS_HOLD_ENABLE
CBS_CHECK_BOX
CBS_DRAW_CHECK_BOX
CBS_NOT_CUSTOMIZABLE

Control List Style
CLS_SLOT_3X2
CLS_SLOT_2X3
CLS_SLOT_4X2
CLS_SLOT_6X4
CLS_SLOT_3X6
CLS_FILL_BK
CLS_FILL_SELECT
CLS_TEXT_SHADOW
CLS_DRAW_GRID
CLS_COLOR_TABLE
CLS_2STR_IN_2LINE
CLS_2STR_IN_1LINE
CLS_3STR_IN_1LINE
CLS_4STR_IN_1LINE
CLS_SETTINZ

Control Ruler Style
CRS_NO_RULER

Control Mhz Style
CMS_SINGLE_BAR

Control Tab Style
CTS_NO_LINE
CTS_ONE_LINE
CTS_COMPACT
CTS_FIX_TABWIDTH
CTS_BUTTON_TOP
CTS_BUTTON_DOWN
CTS_BUTTON_LEFT
CTS_BUTTON_RIGHT
CTS_RESERVE
CTS_NO_BUTTON

Control Slider Style
CSS_DRAW_BK
CSS_DRAW_HANDLER
CSS_VERTICAL
CSS_TITLE_BOTTOM
CSS_TITLE_TOP
CSS_PROGRESS_BAR
CSS_NO_HANDLER
CSS_TITLE_LEFT

 

Ah ok; yes we knew about the separate eq sound levels.
I misunderstood; I thought you meant the Audio Advanced Settings which let you control the db for each input:






I tried the MP3 thing real quick on the other UI Shells; didn't work.
May be the picture format is important or some other settings...

 

It's a good question...

May be a few things can be enabled but nothing major.
The .rrui file is a layout of the UI but it also contains pointers to functions that are assumed to be available in the UI Shell.
So it depends also on the UI Shell (Manager.exe) you have.
The MCU job is to expose what's available in the hardware.
That's why it's specific to every unit model.
The UI Shell communicates with the MCU through the COMx ports.
The UI Shell seems to be coded for every possible hardware but enables only what you have.

If we would like to replace the UI Shell altogether,
one would only need to snif out the commands sent through the COMx ports and figure out what the protocol is.
In fact, the last beta UI Shell has a Console mode just for that.
Once we would know the protocol, we could write our own Manager.exe.

Talking about that, there was some experiment done by a Russian; look for Google Code RoadRover Reverse Engineering.
Here: roadrover - Reverse engineering of RoadRover software and new tool creation - Google Project Hosting

In the specific case of the equalizer bands,the G2 has the TEF6624 Audio chip so that means 3 bands equalizer only.
There is no way we will ever get 9 bands (working by hardware) even if we enable the RR screen itself.
Of course, doing it completely in software is a different story; that's a lot more work.
That would means replacing the UI Shell (Manager.exe).

As for temperature, speed, etc. that comes from the CAN-BUS; we were told it's not connected at all.

On the other hand, things like enabling the Keyboard should work. It's done entirely in software.
In fact, yesterday I tested it with the new UI Shell and it works.
Even with Bluetooth, you can actually do a search through Contacts with it.

Patching the Manager.exe is also a possibility; not so hard if we know where to look.
Even replacing Windows OS altogether is entirely possible; but that's a lot more work for sure.

Back to your questions, now that we have the RRUIEditor,
I think there is a chance we will find new little features especially if we upgrade to new UI Shells.
But can not be sure without experimenting further.

 

Done.
So here is a new version of the RRUITool: v0.9
Major changes:
- supports up to 10MB RRUI file (Germans create bigger files...
- RRUI file format documentation 99% complete (based on the new RoadRover Editor info)
- convert rrui files from v0.5 format to v0.4 (for UI Shell 2.78.10)
Here: http://dl.dropbox.com/u/63503986/RRUIToolv09.zip


And also here is a package that contains all the official RR skins converted to v0.4 format and all the custom skins we already have.
All tested and usable on 2.78.10 for those who do not wish to upgrade their UI Shell.
http://dl.dropbox.com/u/63503986/AllSkinsv04.zip

(The ones ending with a 4 means they were in the v0.5 format before)
That's 12 skins; which is actually the maximum the UI Shell can load anyway.

You can either copy all of them in the \StaticStore\I9\Skins folder or select them one by one from a USB stick or SD card.

Here's a sample:

 

Ahhh finally figured out why the RoadRover UI Editor was crashing on MP4 screens and others...

It turns out that some of the labels are not necessarily text; sometimes they are a reference to a graphic char in the font arialrr_1_08.ttf.
Like in the iPOD screen; the Pause, Backward and Forward buttons are graphic chars from the font itself.

So you need to install that font in the *fonts* directory when you edit the skin .rrui on the PC.
And the *fonts* directory should be at the same level of the RRUIEditor.exe.
Of course, you can also just copy the RRUIEditor.exe in the I9 folder since the skins are already there.
On the PC of course; not the unit.

Weird design may be from RR but hey that's how it works.

So when selecting a string for an element, you can also instead select one of those special chars.
Here's a screenshot:


BTW, I forgot to mention that now that we have the source code for the strings, it would be probably very easy to fix or change any string in the UI.
(Haven't tried yet but I'm thinking of building a universal LANG.DLL that would work for all the UI shells. Well in English only...)

So here is the new package for the fixed RoadRover UI editor along with the font you need:
http://dl.dropbox.com/u/63503986/RRUIEditorv-v2.zip