Customizing MMI 3G+ Green Engineering Menu Screens

[DrGER]

The Green Engineering Menu (GEM) on MMI 3G High and Plus systems is implemented within a running Java virtual machine that gets its screen definitions from various configuration files in /mnt/efs-system/engdefs.

Inspection of the plain-text files in this directory show that many are used launch QNX shell scripts that appear as control elements in the GEM. For example, the GEM /version screen has a control called "Start Script":


Inspection of file AAAVersion.esd finds the following definition text:

script 
    value           sys 1 0x0100 "/scrips/pidin.sh" 
    label           "Start Script"

The script value specified here (/scrips/pidin.sh) does not exist on our 3G+ system, so we changed this to (new) QNX shell script /scripts/myScript.sh:

script 
    value           sys 1 0x0100 "/scripts/myScript.sh" 
    label           "Start myScript"

and restarted the MMI system. After restarting and entering the GEM, we find the label on the control is now "Start myScript":


The new shell script is stored in the /mnt/efs-system/scripts directory, and writes a system info file to a FAT32 formatted SD card in slot 1:

#!/bin/ksh
# Copy info to SD 1 if FAT32 mounted
xddir="$(mount | grep "/mnt/sdcard10" | sed 's,^/dev/sdcard10t1. on ,,;s/ type dos .*$//')"
mount -uw $xddir
if test -e "$xddir"
then
        echo "[INFO] Running myScript.sh $(date) / $(getTime)"

        mount -uw $xddir
        xssfile=${xddir}/sysstatus-$(getTime).txt
        echo "[INFO] Timestamp: $(getTime)" > $xssfile

        echo "[INFO] df -k -P" >> $xssfile
        df -k -P >> $xssfile

        echo "[INFO] pidin -aenA" >> $xssfile
        pidin -f aenA >> $xssfile

        echo "[INFO] sloginfo" >> $xssfile
        sloginfo >> $xssfile
        echo; echo "[INFO] OK to remove SD 1."
else
        echo "[INFO] No usable SD card found in slot 1 (${xddir})."
fi

Selecting the control launches the script and output is displayed in the MMI console:

and we find our new system status file written to the SD card (without having to run a special-purpose SD card script). Note that this script is not suitable for unmodified MMI 3G (High) systems, as they do not have the QNX binary for sed.

New bespoke screens can be added to the GEM /main list by adding a new Engineering Screen Definition (ESD) file to directory /mnt/efs-system/engdefs. The script above can be called from a new "MyScreen" with plain-text file MyScreen.esd:

screen  MyScreen        Main
        keyValue 
                value   String per 3 0x00120004
                label   "Software Train Name"  
        script 
                value   sys 1 0x0100 "/scripts/myScript.sh" 
                label    "Run myScript"

After restarting the system, we find the new screen entry in the GEM /main list:


Selecting the screen, we find:


And selecting the script control, we see output from the process displayed in the GEM Console:


Information on where to find various string and numeric version information is TBD. --g

[DrGER]

After inspecting the available GEM Engineering Screen Definition (ESD) files found on our MMI3GP system, I have a few more observations to add to the thread:

1) The screen order of the Main menu appears to be defined by the collating order of the ESD file names, given that AAAVersion.esd appears before other "Main" screen definitions. Modifying this file directly, however, changes the menu display order so that screen /version moves to the end of the list. I haven't determined yet why this should be the case.

2) GEM screens can display 11 single-line elements (numerical, strings, or script controls); additional elements are displayed on subsequent screens.

3) A new sub-screen can be added to an existing main-level screen by referencing the parent screen in the "Screen NewName ParentName" definition.

The current "Version" screen definition includes four "export" elements, a strings element, and a script element, followed by nine sub-screen references, which require a second page to display all screen elements. The Addressbook.esd files contains only five elements (two Choice elements, three Scripts).
Thus, appending our new MyScreen (sub)screen to /addressbook helps to minimize control interactions (scrolls/button presses) to access.

A ZIP archive installer for this new GEM screen is TBD. --g

[DrGER]

*** RESERVED ***