Notes On The Term "Pc" In This Document
When this document was originally authored, the Windows™-based PC was the only non-handheld-device being used for comprehensive vehicle diagnostics. Desktop PCs and monitors on shop "push carts" were prevalent. Laptops were heavy, expensive, fragile, had a short battery life, and were not in widespread service-bay use.
Since then, laptops have gained tremendous strides and have taken on the role as primary service bay
PC with tablets and hand-held cell-phone-sized devices slowly gaining traction (e.g., Apple iPod/iPad, Samsung Galaxy, Microsoft Surface). Some of these devices have small screens (in relation to current laptops) which makes writing complex software (especially diagnostic software) difficult. Some diagnostic application providers are fielding, or thinking about fielding, limited functionalities of their main diagnostic applications on these devices.
This being noted, when the term "PC" is used in this document, most of the terminology will still apply to them. The main challenge we have with these devices lies in the size of the screen which affects the number of and placement of form elements on the screen, and the fact that these devices try to hide underlying fundamental operating system concepts like a "directory structure" for storing recorded vehicle data, application settings, and other user-oriented data.
If implementing an application for one of the small devices, take into consideration the strategies being discussed in this document along with the current software engineering architectures and conventions for those devices. Take care not to make the user interface so "busy" that the technician cannot read the data on the screen (which may be muddled with grease), and ensure all navigating screens remain intuitive. Also note that TMC's RP 1210 Update Task Force has recommended that no reprogramming/recalibration of an electronic control unit (ECU) be done wirelessly, which is important since most of these devices have built-in Bluetooth™ or WiFi (802.11) functionality.