|What's new Home Download Documentation FAQ HowTo Forum Contact Us||Русский|
This version of manual is actual for FORScan Lite for Android version 1.3.* .
Current version of the application for Android works with Bluetooth, WiFi and USB adapters. Bluetooth Low Energy (BLE) adapters are not supported yet. Warning: bad quality clones that are not fully compatible with original ELM327 will not work. Also, some Bluetooth circuits in clone adapters may freeze on requests that return long data. It is strongly recommended to always try FORScan Demo before purchasing FORScan Lite.
All screenshots below are provided for Portrait mode, but Landscape mode is supported as well. Only phone screenshoots are provided by default. Tablet screenshots provided only if there is a significant difference in design or functionality.
The following FORScan Lite application behaviors have to be taken into consideration:
When application is started first time, two important operations must be executed: license check and setup connection to adapter.
1. License check. When application is started for the first time, it performs license check to make sure this is valid FORScan Lite install. User should not do anything but make sure the device is connected to the internet and it's google account is logged in. If FORScan Lite is unable to validate the license, the application may be closed. In this case, user needs to check internet connection and google account and run FORScan Lite again. License check is performed only once, so user can use application offline after the succesful validation. Sometimes, but not more often than 1-2 times per year, random license check may happen. If it happens, user should make sure device is connected to the internet and there is no any problem with google account.2. Adapter setup. By default on first run, FORScan uses demo adapter. Demo adapter emulates a vehicle to demonstrate FORScan abilities. In order to connect to real vehicle, user has to setup Bluetooth or WiFi adapter. Here is detailed instruction on how to do it:
Current progress and application status is indicated using color of the application icon at the upper left corner:
Standart network activity indicator shows when FORScan is trying to communicate with adapter and vehicle.
Navigation is standard for Android applications. Phone version has main screen, tablet version has main menu at the left side that is available on all pages and can be used for navigation. So navigation is slightly different for phone and tablet:
In case of phone devices user can move only up and down through hierarchy of screens. Navigation down is performed by tapping on an action button, list/menu item and so on. Navigation up is performed using standard Android back button, that is duplicated with back button at the left side of home icon:
In case of tablet devices user can switch between sections from any place of the application. Standard android back button works here as well, but there is no a duplicate back button at the left side of home icon. Instead of, tablet version offers a special navigation menu in subsections:
In this example, user has 3 ways to leave the Add PID screen: press Android back button and return to previous screen, tap on the "PID profile" text in the navigation menu at the top of the subsection and return to the parent subsection "PID profile", tap on any item in the main (left) menu and move to another section.
Sections are the same as in regular Windows version, except that there are no Tests and Service sections (this is main difference of Lite version from regular one). Detailed description of every section will be provided below.
Application is managed in a standard way: using action bar buttons/menu. Main screen has only 2 buttons: connect/disconnect and information. Buttons connect/disconnect are self-explaining. Pressing information button shows the About page:
Most important information on this page is version of the kernel that is displayed right after the version of FORScan Lite for Android. All versions of FORScan use the same kernel, so this version number is in sync with the one displayed on FORScan Web site everywhere (announcements, Change history etc).
Section item is the last one on the main screen, however it most important item on the first run. Here it is:
Vehicle screen keeps Adapter, vehicle and modules information:
The action bar has 2 buttons: Save and Service. The Save button calls Save menu that allows to save OR share the content of the section:
Note this Save menu structure is typical for FORScan Lite, these menus in other sections have the same organization:
Clear cache button - clears all vehicle caches. When FORScan Lite is connected to the vehicle first time, it does full scan of vehicle configuration and saves it to the cache. It may take quite significant time, but subsequent connections are established much faster. If the cache is cleared, FORScan Lite has to perform the full scan again. Besides, the cache may contain some info entered by user. This is why the button is marked in orange. In the meantime, PIDs profiles are not a part of cache, so they are not removed when this function is called.
Save debug info - this button is used to save internal FORScan debug info to the documents folder. This function should be used only if requested by FORScan Support Team. This option is designed to be used only if there is no mail client and/or Internet connection on the device. Otherwise, it is recommended to use Send debug info option (described below). Important note: by default the debug info is not collected. In order to collect it, the Debug setting in the Settings section must be set.
Send debug info - same function as above, but does send the debug info using Android email client or other application that supports sending files. It is preferred way to share debug information.
Remove debug info - this button clears all collected internal FORScan debug info.
The log screen keeps log information. The action bar has 2 standard buttons: Save and Clear log information:
Note: In contrast to the Windows version, where the log grows from the top to the bottom (most recent record is always at the bottom), in Android version the log grows from the bottom to the top (most recent record is always at the top).
This screen contains list of DTCs grouped by modules. Every group row displays Module name and 2 buttons at the right: Read DTC and Reset DTC.
The action bar contains the following buttons:
Every DTC in group is displayed in a short view - DTC code and brief description. In order to get more details about the error, you have to tap over the row. The following DTC Detail screen will be opened:
Note that some parts of the text are marked in blue (as hyperlinks). These are "hints". In order to get a hint, you should tap over the hyperlink (in example below, IAT keyword is tapped):
Dashboard, Table and Graph sections of FORScan Lite are organized in the same way. It consists of 2 parts: action bar with buttons and work area:
The work area contains gauges, every gauge displays data for a PID. A gauge has a scale and displays PID value in numeric and analog format, also it shows current measurement unit and PID name. Some PIDs cannot be represent in numeric format, so such PIDs have no scale, just PID name and text value.
Important feature is that you can select more PIDs that the Dashboard screen can display. You can then scroll up and down to see hidden PIDs. Also, if you tap over the PID on this screen, a PID description will appear for some time:
The action bar contains the following functional buttons:
The playpane contains:
The screen allows to change current module. Every module has its own set of PIDs. So when the module is changed, FORScan Lite loads a list of selected profile owned by the module.
Also, the PID profile screen allows to manage list of PIDs - add, remove, edit and sort PIDs. To remove a PID, you should click at the remove button at the left of the row. To edit a PID, you should tap on the row - and the PID Detail screen (described earlier) will be displayed. The list can be sorted using a special control in the right side of every row. You should tap over the control (or make long tap over the row), then move the selected row to another position. PIDs can be added using Add button from the action bar (described in more details below).
If you tap over a row, the PID details screen will appear:
This screen contains information about a parameter, also it can be used to changhe some PID output settings. User can change displayed units and min/max value for numeric PIDs. Min/Max values are used to build gauge scale and graph upper and lower limits. User can also change precision (digits after the decimal point) for every numeric parameter.
Hints in the Detailed description are work in the same way as in the DTC detail screen.
The action bar has the following buttons:
The add new PID screen looks as the following:
The work area of the screen represents all PIDs available for this module. You can select one or several PIDs by setting checkbox at the left side of every selected row. Tap over the row opens the PID Details screen described earlier. The screen has a search bar at the top, you can filter the list using the bar. For example, if you type RPM in the search bar, only PIDs that contain RPM in their name or description will be displayed.
Aggregated Output is a feature to display PIDs from several modules on the same screen. In order to use the feature, user needs to choose the virtual module All:
The virtual module All contains all parameters from all real modules. Every PID in the list is displayed with a prefix that points to the original module the parameter is taken from. While adding parameters to the profile, it is recommended to use the search bar at the top of the Add PID screen to simplify the PID search and selection. For example, if user types PCM, all PCM pids will be displayed as they contain PCM prefix in their description.
It must be counted that aggregated output has to switch between modules, buses and protocols. As a result, the output performance may drop very noticeable. Also in some cases the aggregated output may be practically useless, for example if user tries to out PIDs from HS and MS CAN modules on adapters with mechanical HS/MS CAN switch.
The table screen displays PIDs in a table format:
Other functionality of this section is identical to the one described in the Dashboard section.
The graph screen is designed to display PIDs in a graphical format that is most convenient for analysis:
Every graph also displays the current value of PID in numeric format at the top right corner, in the same color. It must be counted that the current value always means the most right visible point of the graph.
Other functionality of this section is identical to the one described in the Dashboard section.
The Tests screen is designed to execute tests. User interface is similar to other sections, but also contains a progress indicator and a tab bar right under the navigation pane:
The progress indicator shows a test progress. The tab bar contains at least two tabs: a Tests tab that contains a list of all available tests, and a Log tab that shows the test log. Other tabs may be added to the pane depending on a test's type, these tabs usually contain results of the test. The application may switch the tabs during the test in an automated mode to provide user with information that is most significant at the moment.Of course, user can also switch between tabs manually.
To run a test, user has to select a test by tapping on its line. Checkbox at the left of every line is a choice indicator. Now, when the test is selected, user has to press the Start button to run the test. This sequence of actions should prevent a launch of an occasional or wrong test. Besides, there is an Information button at the right of every test line. User can get information about test tapping on this button. This information is also displayed when users press start, to provide a chance to cancel the test if wrong one called.
The mode a test is executed in depends on its type and can be automated or interactive. In automated mode tests do not require any feedback from user, so application shows test results at the end and becomes ready for the next test. The Stop button is not usually available in this type of tests, except the cases when the procedure can be interrupted by user. Example of automated test final screen:
Interactive test requires a feedback from user in order to be completed. For this purpose such a test usually shows an interactive dialog that provides information necessary for decision making. Some tests show result but do not exit after completion and require user to break the test explicitly. In this case network activity indicator in the status bar is active and Stop button in the tool bar is available to stop the test:
In addition to the Start and Stop buttons described above, the tool bar contains the following buttons:
|Copyright © 2011-2018|