Latest Operational Comments.  9/30/2000
 
Strange and Inconsistent results and opertion noted with the MS5000.
1) If you go to Navigation>Address Book>Guidance,  the system most often puts you initially into ARROW GUIDANCE mode  but sometimes puts you into MAP mode at start.  The system should ALWAYS place you back into whatever the last tracking display you used.
2) When you get into the ARROW GUIDANCE mode as in item 1) above,  pressing MAP should get you into either MAP or SPLIT screen mode in rotation.  However,  if you press MAP while the system is still computing a route,  you will go to the screen with GUIDANCE on it.  Again,  consistent operation is the missing ingredient.
3) On the initial screen after you boot up and press OK,  there is an ADDRESS BOOK entry.  Yet,  you cannot enter an address here when you go to this screen.  In showing a number of people the MS5000 and asking they attempt to operate it without instruction,  (that is:  see what they do intuitively.) they always want to go to this screen and put in their address.  It should be possible to enter an address DIRECTLY into any address book screen and it should be obvious or INTUITIVE as to how to do it.
4)  When the SCALE goes beyond one mile,  the operating mode changes from TRACK UP to NORTH UP.  When you come back to a scale below 1 mile,  the mode should change back to TRACK UP.  It does not.
5)  On occasions when you are driving along the freeway and the map error gets so great that the system thinks it is "off the road",   then the system changes the TRACK UP mode to NORTH UP.  When the road comes back into position and the system realizes that it is "back on track",  the system does not change back to TRACK UP mode.
6)  When you go to the screen where you are allowed to input a SAVE CURRENT LOCATION,  the system a) may save the location,  but I cannot figure out where it goes and b) does not allow you as a part of the function to input an address or name to go with the current location.  In such cases,  the system should make a note that "whereever it is" is actually whatever address the user puts in.
7)  If you put an address into the system that includes a cross street intersection,  it is not possible to CHANGE the intersection to another intersection.  You must delete the entire address entry and re-enter it from start.
8)  If you input an address and enter GUIDANCE,  the system will not  allow you to go to function and split screen until the system is tracking on a roadway.  It should be possible to enter split screen mode (or any other) at any time from any other screen mode at any time.
9)  If you input an address and enter GUIDANCE,  the system will not allow you to press MAP and move between MAP, SPLIT, and ARROW screens until the system is tracking on a roadway.  It should be possible to move freely between these allowable modes at ANY time even if the displayed ARROW screen must be blank for lack of usable data.
10) There are many times when you press a button and the system is busy and gives NO RESPONSE to your button push.  BUT,  the system logs the request.  If you then press again (thinking your push was somehow lost),  the system will eventually see both button presses and do bad things.  button presses should result in a visible change in the display that the user can relate to the system having accepted his command.  There should never be a significant delay in presenting the fact that a button press has been accepted.
11)  On the displays of the addresses in the address log and in the prior destinations log:  The information on COUNTY is almost useless.  What a user needs to see on the first page is the NAME, ADDRESS, CITY, STATE.  The information on what county is redundant and need not appear at all.
12)  When I start a route from 6980 A C Smith Road,  Dawsonville Ga. to 4040 Royal Drive Kennesaw,  the system sets up a tortuous route.  First it goes from my address to Bannister Road to Hwy. 306 (good),  then it turns west on 306 (good),  then it starts taking you on all sorts of minor country roads instead of sending you down 306 to 369 to 20 to I575 to Bell's Ferry,  etc.  (This is NOT the "fastest" route.)  If I turn onto 369 westbound instead,  the new route is a good one.  Seems like "fastest" mode needs some work.
13)  The routing in the suburbs is mostly fine,  but  can be a bit strange.   I noticed that when I came from Downtown Atlanta heading to 4040 Royal Drive, Kennesaw,  the system wanted us to get off at Barrett Parkway  (about 4 miles from Kennesaw) and go up back roads to Kennesaw.  This despite the fact that Interstate 75 goes within maybe a mile of 4040 Royal Drive.  When we drove on past Barrett Parkway,  the recomputed route was fine.  I have seen this same phenomenon in three areas.  MS5000 seems to equate ALL Federal highways the same,  be they Interstate 75 or US41.  My Datus RouteFinder which also uses NavTech maps does a few odd things also,  but not this one.
14) As I was driving to the World Congress Center/Atlanta,  as I approached Luckie Street,  coming off I-75/85 Southbound,  the computer screen dropped out of split screen mode and displayed the full map.  From that moment,  the CPU was locked up completely.  When we parked 10 minutes later,  we had to shut the unit off via the power switch in the trunk.  This has only happened once and when power was restored,  so did normal operation.
15) The FUNCTION screen changes what it will allow you to do from time to time without explanation.  The function screen should stay the same and items not available in a particualar screen should be "greyed out".
16) Delete Destination is an EXTREMELY complex operation for such a simple task.  This function should be reviewed with a veiw toward making the procedure simple but secure.
17)

Miscellaneous notes about the VDO Dayton MS5000 automobile navigator system  9/20/2000

1) Really nice display.  Wide viewing angle,  clear and bright in sunlight.  About the best color automobile display I have seen.
2) The GUI is  structured,  but the many instances of inconsistent operation a) cause confusion and b) make it difficult  to use.
    a) Unless you are on a roadway -and- with a guidance route enabled,  SCREEN SPLIT does not work and there is no explanation message.
    b) Entry of a name and address is a VERY non intuitive sequence,  lengthy and prone to errors.  The entry sequence in a consumer product needs to be a) fill in the blanks (OK there),  b) All data entry  in a single screen (it now takes movement between about 5 screens to completely enter a name and address and store it and activate the route.) and c) with a "now go do it" button at the bottom of the page after everything is entered.
    c) Delete Destination is so complex that in three days of intermittent attempts,  I had not been able to get it to work.  I had to read the manual!.  (No.  I never read the manual with a new system UNTIL I  discover how intuitive the GUI is.)   A GUI on a consumer product should not be so complex that a person can have the screen of the information he wants to delete ON THE PAGE with the "DELETE DESTINATION" key and still not be able to delete it with a keystroke.
    d) The FUNCTION screen changes what functions it will let you do from time to time.  This is NOT A GOOD feature.   On consumer equipment,  (to promote quick learning and ease of use),  GUIs must operate in a consistent manner.  If a user clicks on a feature (such as SPLIT SCREEN),  the screen should split EVERY TIME even if there are no directions to display.  In such case,  the display should give an error message such as "Not in guidance mode.  No directions to display."  BUT.. It should stay in split screen mode with this message unitil/unless guidance mode is entered OR the user issues another command.   As it is,  the beginning user will simply think the feature is "broken" since it sometimes just "ignores" a command..
    e) Outside of the cities,  the algorithm can change your input address number (ex: 4547 Homer Lane) to (4570 Homer Lane) if it does not find your number in the range.  I believe it would be better to try and interpolate between two existing address and leave the input house number unchanged.  After the initial trip,  the user will be looking for the address HE put into the system.  He won't be looking for the changed address number.

3)  The keyboard entry system with the blanked out letters is really a nice feature.  Well designed,  easy to use and works well.
4) The unit was easy to install and the manual was adequate with respect to installation,  but brief.  This install is not a "do it yourself" install for most people.  It will be better in the future if auto companies come up with a uniform interface for vehicle nav systems.  Hopefully on a special connector.
5) Maps are excellent.  Default routing settings work well.  Algorithm should give a bit more weight to 4 lane state  expressways (as opposed to interstates) as compared with Federal Highways.  Example:  In North Georgia,  the system apparently gives fairly equal weight to Highway  US9 (Federal) than to the 4 lane expressway nearby (Georgia route 400) which runs parallel.  In this case,  the Federal Highway 9 is crowded,  twisty,  and a 2 lane road where Ga 400 is a high speed expressway.  VDO is not the only system to make this mistake!
6)  The existing day/night feature works very well.  Connecting the control wire to the low beam lights was not an option on my Cadillac SDV.   The low beam goes off when the high beam comes on.   I could not easily reach the parking light buss as it did not enter the underdash area.  Instead,  I connected it to the license tag lamp and tapped the day/nite control line in the trunk where the CPU is located.   Suggestion:  If the day/night input was an A/D converter input,   you could connect the wire to the instrument panel dimming buss (easy to find on the radio connector) and then set the VDO to trip from night to day on some  user setable analog voltage with hysterisis.  Even nicer would be an interface to the vehicle serial data bus.  I am sure VDO is already thinking along these lines.

Consumer User Graphical User Interface (GUI) Philosophy
by Joe Mehaffey
 

The design and implementation of "GUI technology for non-technical people is not rocket science.  However,  many computer engineers are so immersed in the technology that they fail to consider how confusing a GUI can be to people completely IN-experienced with  technology.  Toward improving "GUI for the masses" on the MS5000,  I offer the following guidelines.
1)  Consistency is a PRIME concern.  The same button on a page should ALWAYS give the same action.  It should not be possible to press a button one time and get one action,  press the same button at another time and get some different action and press the same button at a third time and get no action at all and then sometimes find the button MISSING entirely from its list.  Example:  The Split Screen Key in the FUNCTION menu.  Also,  the MAP key on the control gives similar inconsistent results depending on the situation.  If for some reason,  SPLIT KEY is an inappropriate function for a particular circumstance,  it should be grayed out and not just "missing" or fail to function when pressed.

As an example of what I am talking about:  The SPLIT SCREEN key should always be present when you are in MAP mode and should ALWAYS toggle to the next split screen mode EVEN IF there is nothing to display but a screen saying "no route directions available."  Similarly,  the MAP key on the control should always give the same predictable result when you press the button.   To do otherwise makes learning the system difficult and will cause lots of unnecessary technical support calls....  Not to mention user dissatisfaction.

2)  Ease of use and learning must be given serious consideration.  Toward these goals,  the following guidelines are offered:
        a) The consistent use of color can be a tremendous aid to both initial learning and ease of use.  For instance:
                i)  Gray is usually used to indicate a blank field (or one with a default entry) where no entry is required (or possible).  Thus,  if a field is "grayed out" the user can ignore it.
                ii) White is usually used to indicate a field where a user entry is needed or optional or that the user can change.
                iii)    Red lettering or boxes usually indicate some sort of major warning.
                iv)    Yellow lettering (often with !) usually indicate a cautionary warning.
                v)     Instructions from the machine to user are often in Blue lettering.
                vi)    Responses from user input are usually in Black lettering.
                vii)   Gray lettering usually indicates that this is default input and cannot be changed.
        b)    Generally,  frequently used features should be accessible from the TOP menu.  Lesser used items can be found in a second menu level and IF ABSOLUTELY REQUIRED,  very infrequently used items can be on a third menu level.  (No more than two menu levels should be necessary in a system as simple as the MS5000.
        c)      In the case of the VDO MS5000,  it should be possible to click the MENU button and find entries like the ones below:
 
 
Enter New Navigation Address Trip Computer Logs
Retrieve Navigation Address SHOW MAP NOW
Edit Existing Navigation Address
Find Points of Interest Emergency Access
System Settings Standby
The above is a proposed setup for a first screen following the press of MENU.   Notice that the most frequently used items are listed first.


The next screen is for the "ENTER NEW NAVIGATION ADDRESS" screen.
 
Name: Country:  (Normally filled in by default and grayed out.)
City:                                                                   State:
Nr:                  Street:
Intersection (Optional):

 
Save New Address  Add Via Points Navigate from Present Position Save Address and Begin Navigation
Set Current Position as Dest. Address Cancel and Return
It should be possible to EDIT the information in the displayed address screen at anytime the screen is displayed and then press ANY of the "execute" buttons as appropriate for the occurrence.

The above is "typical" of an arrangement that most users find comfortable.   Notice that  entering an address and saving it,  entering a new address and not saving it to the address book  are all decision which can be made all on one page and with a LOT less button pushing than now.  I am sure I have overlooked something in the functionality,  but hopefully this will allow visualization of the concept.


d)    If a button should not be usable in a given situation,  the system should either "gray out" the button or give the user an explanatory error message and NOT just fail to do anything when pressed.  (Non technical people tend to think something is "broken" if they press an active button and nothing happens.)

e)  Incidentally,  there should be an easy  way to manually toggle from day to night mode and vice versa regardless of time of day.
f)   Time (and maybe date) should be displayed at all times and not just when navigating.  There appears to be plenty of screen space available.
g)  A glossary and context sensitive help should be provided for each symbol on every  screen.   (->*) is pretty cryptic for the average person to remember.
h)  Let the user enter and store a house number even if the database cannot use it.  Then when the user gets to the exact location,  he can click: "Set this location as address" and the system can remember this lon/lat  without benefit of the database house number.  The USER will still key on the address even though the database uses the lon/lat position reference.
i)  I cannot exactly tell when it happens or what causes it,  but if I set HEAD UP display,  periodically I find it back in NORTH UP mode.
j)  Sometimes I can use the cursor to store a waypoint and sometimes I cannot.  This is one of the inconsistent functionality problems.
k) When you are moving the cursor,  there should be an entry on the function menu for a) store waypoint,  b) execute waypoint as destination and c) both.  And..  It should ALWAYS work.  If you are in an area not covered by full mapping,  it should still work even if you must move the waypoint to the nearest applicable road.  (If the waypoint is automatically moved,  the user needs a message telling why.)  If in some instance,  it cannot be made to work,  then the user should get an error message saying why instead of the screen just going away and giving the user a false sense that "something good" has happened.
l)  When you RETRIEVE an address book address,  the default address display should give the NAME and ADDRESS.  As of now,  it gives something like:  Unincorporated Forsyth County,  Hwy 9.  If I put in three addresses on the same road,  all three entries look just alike unless I further examine still another optional menu level.
m) In most cases,   (in the USA for sure),  it is totally redundant to have to enter the COUNTRY into an address.  If the map contains only a single country,  then this country name should either be omitted entirely -or- it should be entered automatically by default and grayed out.
n) The cursor seriously overshoots when you release the pan key.  Panning should stop immediately when the key is released.
o) When some commands are issued,  there is a LONG pause with no indication that the command was received by the MS5000.  There should be some indication of "I'm thinking" so as to tell the user that all is well and that the command was received.   (How about putting a big hourglass on the screen in such instances?)   I find that often I think maybe I failed to press the button firmly and when I press a second time,  I end up executing a function  I did not intend.

Andy,  I hope these comments are accepted in the constructive manner intended.  The MS5000 "core functions" are excellent.  Excellent maps,  Excellent maps,  Excellent screen displays.  It would be a shame to hobble it with its current GUI on an ongoing basis.
 

Joe Mehaffey,  Computer Systems Engineering Consultant
770-889-5120