1 Description

1.1 About VAG-Check

VAG-Check is an after market diagnostic-tool for VAG Group vehicles running on Windows Mobile based Personal Digital Assistant.

2 Getting Started

2.1 Software Installation

System Requirements

In order to use VAG-Check for Pocket PC, your handheld must meet the following minimum system requirements:

• Windows Mobile 6.0, Windows Mobile 5.0 or 2003se, 2003, 2002 for Pocket PC

• ARM-MIPS-SH3 processors

• ≥ 2 MB free storage memory (more storage memory needed for intensive log run)

• ≥ 16 MB Ram

• ≥ 256 colors, 240x320 or 240x240 pixel screen resolution

• RS232 Serial port or Bluetooth port (depends on OBD interface type)

Installation procedure

There are two ways to install VAG-Check on your PDA: PC Windows install procedure, manual installation.

Pre conditions:

• connect your PDA using sync cable (Serial or USB)

• wait until ActiveSync establish connection with your PDA

PC Windows install procedure:

from your PC start InstallationVAG-Check.exe program;

Press Next button.

Read Licence agreement and press “I Agree” to proceed

Choose destination folder and press Install button

Wait installation completion

Manual installation:

choose .cab file compatible with your PDA hardware (refer to your PDA user manual)

copy .cab file in an empty folder of your PDA

open File Explorer on your PDA,

select .cab folder

tap on .cab file and wait until procedure end.

2.2 Hardware Connection

Interface description

VAG-Check 2.x Series support two type of proprietary interfaces: serial (SmartVAG) and bluetooth (BlueVAG). Interface acts as a dongle and contains activation data for VAG-Check program. Interface are provided with status leds that informs user about working conditions.

Led status colors are explained in table below:

Note: after power connection interface performs internal test and led 1 blink from green to red color for about 1 second.

Connect interface to your PDA.

For serial interface, simply connect serial plug to PDA port, then connect OBD interface connector to vehicle socket, verify led status (green light stable).

For BlueTooth interface, switch ignition ON, connect OBD interface to OBD vehicle plug, verify led status (green light stable on and blue light blinking), establish pair connection from your PDA and Interface.

Please refer to the user manual of PDA to enable the Bluetooth connectivity. If the connection between your device and BlueVAG interface is successful, the blue LED of BlueVAG will be stable ON. Below, we provide a common procedure of software installation to set up your PDA. (For other PDA, the steps may be a little bit different. Bluetooth Manager is one of popular program used for Bluetooth device.)

1. Open “Bluetooth Manager” and establish new connection

2. Explore new Bluetooth device. Tap on “BlueVAG” device, and enter passkey (if your PDA ask for key enter: 1234)

   Select: “Explore a Bluetooth device” then Next	Tap on BlueVAG icon then Next
   Passkey 1234 (if needed)

3. Select Service and finish setup.

   Tap "Generic Serial" then Next

   Finish setup

4. Establish Connection

   Tap and hold on BlueVAG icon, then select Connect item

   Done!

Connection Verification

• Switch Ignition ON

• Select Program/Configuration menu item

• Select Port Settings folder

• Select COM Port

• Push on Test Interface button.

• Wait until test end.

If test is successful verified you should obtain a screen like following:

K1 & K2 Status Icon Description

Icon
	Test not completed
	Test completed and K lines not available
	Test completed K stuck high not ok
	Test completed K stuck low not ok
	Test completed successfully

CAN Status Icon Description

Icon
	Test not completed
	Test completed CAN -Bus not ready
	Test completed CAN-Bus gateway not found
	Test completed successfully

If test fails, messages as follows could be displayed:

2.3 Activation

VAG-Check OBD interface works as activation dongle. Users can activate software connecting interface and starting activate procedure.

Operations guide:

• Connect interface to Vehicle plug as explained in 2.2

• Select Program/Activate menu item

  
  

• Press Activate button and wait until activation key will be displayed

If activation fails following message could be displayed

3 Using VAG-Check

3.1 Logon

Connect hardware as explained in 2.2. Switch ignition ON. Select the unit you wish from Modules menu and wait until communication goes up. When connection will be active the text fields will display informations about selected unit.

During logon procedure it is not allowed to connect another units, it is instead possible to abort connection attempt tapping "Modules/Disconnect" on menu item or pressing on button. If connection attempt timeout and maximum number of retry exceed the program will display following message.

Modules/Other modules item allows to directly insert Control Unit number or select wished ECU from a preloaded list.

Direct Unit Set: Tap on ECU Number Edit control, insert a valid Control Unit number, press button to confirm;

Select ECU from List: Tap on ECU Selection List, search for wished Control Unit ( list is ascend sorted on ECU Number), press button to confirm choice.

Logon procedure could be influenced by Protocol parameters settings, see 4.3

3.2 Functions

As other vehicle tester systems (i.e. V.A.G. 1552) VAG-Check makes available a set of adjustment functions for Electronic Control Unit diagnosis. Functions codes and function labels are the same referred by vehicle Workshop Manual.

The following standard adjustment functions are available:

• 02 Read fault Codes

• 03 Actuators Test

• 04 Basic Settings

• 06 End Output

• 07 Recode

• 08 Read Measured Value Block

• 09 Single Reading

• 11 Adaptation

• 12 Login

• 16 Security Access

VAG-Check also makes available some advanced functions like:

• Advanced info (for KWP2000/CAN-Bus Unit)

• Live Data Log

• Live Data Graph

• Multi Measured Block Read

• Measures Shortcut

• CAN-Bus ECU List

3.2.1 02 Read fault Codes

Read fault Codes function displays list of the fault code recorded by unit since last code list reset.

Operations guide:

• Push button to force fault code reading

• Push button to delete Control Unit recorded fault code data.

• Tap and hold on Fault code list to open context popup menu.

  Fault code popup menu allows to:

  • clear fault window using "Clear" item (no command is sent to Control unit);

  • copy fault code data to clipboard using "Copy to Clipboard" item;

  • save fault code data to file using "Save" item.

If no fault code has been found, "No fault code" message is displayed.

3.2.2 03 Actuators Test

Actuators Test function allows to verify ECU output.

Operations guide:

• Press button to begin output sequence

• continue output sequence pressing button until it became grayed (sequence termination).

• Actuators Test sequence can be gracefully interrupt clicking button on upper right hand corner.

If connection isn't closed, interrupted sequence can be restarted at interrupt step selecting function again.

KWP2000/CAN-Bus units make available an advanced test sequence, during test VAG-Check can displays actuator real time measured values .


IMPORTANT: Please before using this function read carefully the Workshop Manual for your vehicle in order to find out preliminary procedures, list of Actuators and its sequence. On Airbag ECUs an improper use of Actuators Test function may cause unexpected results even making it impossible to start the vehicle again!

3.2.3 04 Basic Settings

This function allows to set basic state of some entities controlled by the unit.

Basic Settings function is very similar to read measured value block, the contents of each display block is the same but in Basic Settings mode reading the unit perform some entity calibration.

Operations guide:

• selected measures block index

  • tap on edit box, type Block Index number using keyboard

  • push on button to confirm Block Index inserted

Please refer workshop manual for your vehicle before using this function.

3.2.4 06 End Output

End Output function end Control Unit diagnostic session. See 3.4 for more details.

3.2.5 07 Recode

Recode function allows you to modify the "Soft code" and the "Shop number". Edit fields display current value and allow new values insertion.

Operations guide:

• select edit box

• insert new value using virtual keyboard

• push "Submit" button to confirm value insertion.

WARNING: the change of these values must be made with maximum shrewdness, because it could damage your vehicle. ARlab declines every responsibilities on any damages to persons or things produced by unsuitable use of the software.

3.2.6 08 Read Measured Value Block

Read Measured Value Block function allows to read digital and analog measured values block from control module. The program displays groups of four measurements.

Operations guide:

• selected measured block index

  • tap on edit box, type valid block (0..255) index number using keyboard, push on “set” button to confirm Block Index number inserted

  • tap on the arrow keys(Up increases - down decreases). Setup step rate of the up/down arrow buttons: Tap slow/fast label to select arrow step Slow = 1 unit per tap, fast= 10 unit per tap.

• Tap on red bullet to log data see 3.3.2

• Tap on button to graph data see 3.3.3

A short description of measures can be displayed tapping on the measurement unit text.

For better information about the group measures means and the type of measures read refer workshop manual of your vehicle.

The data refresh time depends on reading rate from the unit.

3.2.7 09 Single Read

Single Read Function is available only on some Kwp1281 units and allows to read one measured value from control unit. The program displays measure using large text font.

Operations guide:

• select wished measure channel

• tap on single read channel index edit box, type valid channel value (0..99) using virtual keyboard

• press on arrow buttons (Up increases - down decreases).

• tap on the measurement unit label to display a description of the measure.

For better information about available measure to display refer workshop manual of your vehicle.

3.2.8 10 Adaptation

This option allows you modify values and settings in vehicle control modules (not all ECUs support this issue).

Adapt Operations guide:

• Select adaptation channel

  • select edit field, if it is not already active, it will be activated the virtual keyboard

  • insert a valid channel value (1..255)

  • tap arrows button to adjust channel index (up increases - down decrease). Increase or decrease step rate of the arrows buttons tapping on the slow/fast buttons: slow = 1 unit per tap, fast = 10 unit per tap.

• Push "Test" button to confirm inserted value, value will be verified by ECU and if it is ok it will be displayed as read value, also push-button "Set" becomes enabled

• push "Set" button to store value.

WARNING: any changes of adapt values must be made with maximum shrewdness, because it could damage your vehicle. ARlab declines every responsibilities on any damages to persons or things produced by unsuitable use of the software.

3.2.9 11 Login

Login Function allows to unlock unit for maintenance purpose.

Operations guide:

• Insert a valid code in Login text box

• press button to confirm inserted value.

Valid Login codes can be found in the Workshop manual for your car.

3.2.10 16 Security Access

Security Access function allows to unlock unit for maintenance purpose, can be used for some KWP2000/CAN-Bus control units.

Operations guide:

• insert a valid code in Code text box

• tap button to confirm Code.

Valid Security Access codes can be found in the Workshop manual for your vehicle.

3.3 Advanced Functions

3.3.1 Additional infos

Additional infos function is available only for KWP2000 and CAN-Bus control units. Press on button, it will appear on main window if control unit supports this features.

Operations guide:

• Tap on folder label to display wished information

3.3.2 Live Data Log

Ones of most useful advanced function of VAG-Check is Live Data Log. That function allows to save read measurement block values on a text file in csv format (csv is a text data format compatible with most popular spreadsheet programs).

Operations guide:

• tap on red circle to start data log;

• tap on blue square to stop data log;

• modify auto generated VAG-Check log data name, tapping on log file name edit box and type new file name (function is not available when log is running).

User can stop and restart log, on the same session (last saved file was the same and read data function was not closed) log data will be appended to last file, on another session VAG-Check will ask user for file rewrite.

VAG-Check saves data in sub-folder named as string concatenation of control unit VAG number and value specified by “Log Path” parameter in Program > Configuration > General screen (see 4.1).

Logged data can be review in various shape, user can import data into PC spreadsheet program, or display data using built-in “Display Graph” function (only for one track shortcut data see 3.3.5).

Display Graph

This function can display one value shortcut (3.3.5) logged data in graph shape. Display graph function is available also in offline mode (no ECU connected).

Tap on Functions > Display Graph menu item to open following screen.

Operations guide:

• tap on up green arrow to open file locate screen

• press button to open file

• press right green arrow to begin file play

• tap blue square icon to stop play

• tap yellow return back icon to return to roll back file

If reading .csv file is not compatible with graph function VAG-Check can display message like following:

Above message is displayed if read file didn't contains scales limit information, saved by VAG-Check shortcut data log function.

3.3.3 Live Data Graph

Read measured value block function allow to display data in graphic shape.

Tap on button to open graph screen. Check box enable or disable data track display. By default VAG-Check uses scales (min and max values are displayed on left axes of graph) based on measurement type, but sometimes to optimize graph viewing it is necessary user adjustment. Tap on button to open vertical scaling windows.

Modify scales Operations guide:

• change scales value

  • tap on edit and type new value

  • tap on arrows button near scales values

• tap on button to confirm modified values

• tap on button to abort scales modification

3.3.4 08 Multi Measured Value Block

VAG-Check can display up to three read measured value block simultaneously.

Operations guide:

• set block index in edit field

• push button to confirm

• change selected block index using arrows button (up arrow to increase, down arrow to decrease).

• Tap on red bullet to log data see 3.3.2

Note: only first left edit box is enabled at screen opening, when user insert a block on first edit, the second will be enabled, and when user will insert data in second edit then third edit will be active.

Log feature allow to save live data of all three blocks measures displayed (see 3.3.2 for log function explanation).

3.3.5 Measures Shortcut

Measures Shortcut screen allow to display a single value of a measured value block. Shortcut are referred to connected control unit type, so they are loaded on fly when ECU connection Hang up.

User can define its shortcut as explained in Appendix I.3.

If Measures Shortcut are defined a menu item like following is displayed:




Tap on Volt item to open shortcut screen:

3.3.6 Acceleration

Pressing on button (when available) allow access to Acceleration windows.

Acceleration function allow to measure the elapsed time to run a distance. Press button to begin time the test, and to terminate. button allow to switch between Km and miles measure unit.

Acceleration button is available if and only if groups contains a speed measurement reading.

3.3.7 ECU Scanner

This function scans every controllers in the vehicle to retrieve controller information -- VAG number, Component number, Soft. Coding, WSC, and Fault codes.

If Vehicle List 5.1 plugin is installed and a specific vehicle is chosen then scan will retrieve controller information of all plausible modules for vehicle selected. Otherwise scan function will be applied to all menu.txt file configured modules (this functions could take many minutes).

IMPORTANT: Some VW 2000-2001 models Airbag module (part number 6Q0-909-605-A) contains a firmware bug and can be damaged during scan operation. Please include Airbag in scan list if and only if you are sure about what you are doing. All damage are at your own risk!

Scan result can be saved tapping on scan list, a popup menu will allow to “Clear”, “Copy to clipboard” or “Save” retrieved data

3.3.8 CAN Functions

3.3.8.1 CAN Applications

CAN applications are a set of advanced features implemented by CAN Gateway ECUs.VAG-Check allows to:

• Activate Transport Mode, powering up most module;

• Deactivate Transport Mode, shutting down most modules;

• Clear All Stored fault, clear all the control modules without accessing individually.

  Simply press “Go” button and wait procedure end.

3.3.8.2 CAN ECU list

CAN-Bus Gateway ECUs makes available a list of installed units. This VAG-Check function allows to display the entire CAN ECU list. Malfunction code is displayed between round brackets on the right, 0000 means no malfunction detected.

3.4 Close Connection

User can close connection in three ways:

• tap on “Module” menu sub item named “Disconnect”, this item abort connection attempt also if connection is not already established;

• tap on “Function” menu sub item named “06 End Output”. It abort connection only when it is established, it is the same command available on 1552 V.A.G. tester;

• tap on disconnect shortcut button (on bottom right corner of main screen). This button is available only in connected mode and only when main screen is displayed.

4 Configuration

4.1 General

This section allows to modify some general purpose parameters.

• "Backlight always ON": check box to activate the backlight until program run;

• "Graph refresh Time": it is the refresh time of diagrams display;

• "Debug Level": set debug log levels , from 0 to 6. Debug level 0 means off, no files are generated, debug level 6 means verbose mode, all messages are saved on vclog<datetime>.txt files.

• "Language": field represents active user interface language, user could choose available language tapping on arrow button. Empty field means default language set (English);

• "Log dir": default save directory of measures log files

4.2 Port Settings

This folder allows to modify setup of serial communication. These parameters are important during connection.

Modify it in case of effective necessity due to difficult connection or unstable communication.

• "COM Port:": it is the communication port (customizable only for develop tests);

• "Test Interface": press on button to start verify interface state

• "Firmware Upgrade": press on button to start firmware upgrade procedure

4.2.1 Firmware Upgrade

These paragraph tell you how to download the latest interface dongle firmware revisions and

copy them to the OBD interface.

Operations guide:

1. Download the latest version of OBD Interface firmware (obd.bin) from www.arlab.it site

2. Copy obd.bin in VAG-Check folder of your PDA (i.e. /Program files/ARlab/VAG-Check/)

3. Push on "Firmware Upgrade" button, and locate obd.bin file

3. Press to confirm ( press to abort procedure)

4. Verify that interface is connected and powered on.

   
   

5. Press Start button.

6. If all is ok, procedure end with screen like following.

   
   

7. Press button to close screen.

   Now interface is upgraded and ready to use. User can verify firmware version using “Test interface” function. If interface procedure fails or firmware seems not upgraded properly, retry above procedure again. If problem persist contact ARlab support at support@arlab.it .

4.3 Protocol

This section allows to setup some protocols parameters, usually default values are good for every conditions, but you could try to change it to improve speed and if communication is unstable or connection is not possible

• "Char interval": it is the wait time (in ms) between the reading of a character and the successive one; Could be important to decrease if communication is unstable!

• "Block interval": it is the wait time (in ms) between the reception of a block of data and the relative answer;

• "Initial delay": it is the waiting time before send the first reply for protocol.Change it if you have problem during connection procedure;

• "Use CAN-Bus Protocol":

4.4 Colors

This folder allows to modify chromatic aspect of the program.

Operations guide:

• choose a color tap on little colored square you wish

• select new color on choose color window

• press button.

Button "Save" allows to save the running setup on file, the button "Read", otherwise, allows to load setup from file.

In the section Main Window is displayed current color setup for the main window:

• "Window": background color of the main window

• "Label": foreground and background color of descriptions text

• "Value": foreground and background color of displayed values read from unit

The Details section dialog display current color setup for command windows (group dialog, single read, adaptation, etc):

• "Dialog": background color of functions windows;

• "Enabled label": foreground and background color of active option;

• "Disabled label": foreground and background color of inactive option;

4.5 Font

This section allows to setup font face and size used in measured value block display windows.

• "Group Font": font face name ;

• "Size": font size;

• "Example": font example window;

  
  

Font selection is available only for registered users!

5 Plugins

5.1 Vehicle List

Vehicle list plugin defines chassis data of most type of VAG vehicle. Data is stored in a compacted file that must be copied in “pics” sub folder of plugin directory. Vehicle List plugin can be installed in two ways: first set check box on installation procedure and follow screen instruction; second copy cab file to PocketPC and tap on it. During installation procedure system ask you for installation folder, you can set your favourite folder (i.e. SD, Compact flash, etc), after that you must set the same folder name on plugin folder as described in 4.1 (remarks: installation procedure will save data in “pics” subfolder of chosen folder, so plugin folder parameter must be set as the chosen folder i.e the parent of “pics” folder).

Vehicle List plugin enables two functions: Vehicle Selector and OBD Connector Locator.

5.1.1 Vehicle Selector

This function allows to select vehicle to check. After selection modules menu will display all plausible module available for vehicle type selected, also the main screen background will display a picture of vehicle chosen. Default selection is “blank”, no particular vehicle is selected and all configured modules can be connected.

User can define his vehicle types editing uservehiclelist.txt configuration file see Appendix I.4 for file format explanation.

Tips: Cause to image background some value labels may result hard to read. Tap on value label area to clear the view.

5.1.2 OBD Connector Locator

This function allow to display the placement of OBD connector. After vehicle type selection user can press button (if available) and open locator window, the placement of OBD connector will be pointed by a green arrow.

Appendix

I.Configuration Files

“data” folder contains some configuration files that allows:

• insert/update codes and types of fault (faultCode.txt, faultType.txt)

• modify number and type of connect units (menu.txt)

• define shortcut menu item (menu.txt)

1 Files Format

The configuration files are in ASCII format, every line are separated by characters < CR >< LF >. The file faultcode.txt contains a list of records of two fields <number> <string> separated from a space. The first record field must be a number, while all characters between the first space and line separator are considered as part of field string. The file faulttype.txt use the same format described for the faultcode.txt file.

The file menu.txt use the typical format of .ini file (section, groups of keys). For the detailed description of section/keys refer to descriptions contained in the file.

2 Control Unit menu definition

VAG-Check is distributed with a complete menu.txt file that contains all known control units. Anyway user can edit menu.txt file in order to create its preferred list of control unit. Menu.txt file use ini file format, control unit informations are grouped by [ControllerX] sections. In controller section you must specify control unit name and control unit address, valid address code could be found on your workshop manual. Each control unit name will be displayed and could be selectable in file menu.

Controller section syntax:

[; [ControllerX]  X = 1..255

 ; Text  = menu text and shorcut section prefix

 ; Address = controller address in decimal (ex: address=23) 
 ;or hexadecimal format (ex: address=0x17)
 ; Category = name of controller category family
 ;



[ControllerX]  X = 1..10
Text  = menu text and 
        shorcut section 
        prefix
Address = controller 
          address


Example:

[Controller1]
Text=Engine
Address=1

[Controller2]
Text=Instruments
Address=23

[Controller3]
Text=AC
Address=8

VAG-Check manage ECU modules in categories. Categories creation is very simple, edit menu.txt file and add “Category” key on all controller section of the same category.

Example:

[Controller1]
Text=Engine
Address=0x01
Category=Common

[Controller2]
Text=Instruments
Address=0x17
Category=Common

[Controller3]
Text=ABS Brakes
Address=0x03
Category=Common

...

[Controller6]
Text=Cent. Conv.
Address=0x46
Category=Common

[Controller7]
Text=Radio
Address=0x56
Category=Electronic

...

[Controller9]
Text=CAN Gateway
Address=0x19
Category=Common

...

[Controller12]
Text=Control Head
Address=0x07

[Controller13]
Text=Cent. Elect.
Address=0x09
Category=Electronic   

Controller section without category are inserted in main function menu.

Function menu can contains up to 12 elements.

Every Categories can contains up to 16 elements.

3 Shortcut definition

Editing file Menu.txt you could configure shortcut screen to display a single value of a measured value block. Shortcut are referred to a defined control unit, you could define up to 10 shortcuts for each control unit. For each shortcut you must define its name (that will be displayed as Shortcut menu item label), the group index and the index of the measure. Each shortcut will be displayed in special windows that can displays measured values in various shapes: digital, graphical, analog.

This Advanced Feature is enabled only for registered users.

Shortcut section syntax

Example:

; Shortcut definition
; [<Controller name as defined in key text of controller section>X] X = 1..10
;
; Text = menu text and window caption
; Graph = 0 no graph, 1 for line graph, 2 for dash graph
; NumTics = number of tics in dash graph  valid values >2 
; Group1..4 = Group index
; Index1..4 = index in group data 0..3
[Instruments1]
Text=Temperature
Group=2
Index=3

[Instruments2]
Text=Tank cont.
Group=2
Index=1
Graph=2
NumTics=5
Min=0
Max=55 Record and play data 

Shortcut windows contains buttons for data recording and playing. During connection you could capture displayed data and save it in to file that you can review in offline mode with "Display Graph" menu option.

4 User Vehicle List

UserVehicleList.txt file allow to define user vehicle data. All vehicle inserted will be selectable in vehicle list window 5.1.

UserVehicleList.txt file must be saved on “pics” sub folder of Plugin folder with all picture file that it refer.

Example:

; VAG-Check User's Vehicle list file
;
;
; [VehicleX] section (one per vehicle)
; ID = max 3 characters (from 01 to 10)
; Name  = max 15 characters
; Image = name of background image, without extension (BMP) in pics folder
; OBDImage = name of OBD locator image, without extension (BMP) in pics folder
; LabelBGColor = RGB Color for foreground label text (Hex value BBGGRR)
; LabelFGColor = RGB Color for background label text (Hex value BBGGRR)
; ValueBGColor = RGB Color for foreground value text (Hex value BBGGRR)
; ValueFGColor = RGB Color for background value text (Hex value BBGGRR)
; ECUList = Comma-separated list of addresses (max 125 addresses)
;
;  Maximum 250 chassis types
;
;
; Example:
; 
; [Vehicle1]
; ID=01
; Name=My Car
; ECUList=01,03,08,09,15,16,17,36,45,46,55,56
;
;
[Vehicle1]
ID=01
Name=MyCar
Image=A3
OBDImage=
ValueFGColor= 0000FF
ValueBGColor= 00FFFF
LabelBGColor= FFFF00
LabelFGColor= FF0000
ECUList=01,03,08,15,17,19,56

[Vehicle2]
ID=02
Name=MyWifeCar
Image=A2
OBDImage=Obd 
ECUList=01,03,08,17,19,56,34

II.Legal Notice

End User License Agreement

IMPORTANT- PLEASE READ CAREFULLY:

This ARLab End User License Agreement ("EULA") is a legal agreement between you the End User (whether an individual or a recognized legal entity) (the "LICENSEE") and ARlab for the ARlab software accompanying this EULA, which includes computer software and may include associated media, and "online" or electronic documentation ("SOFTWARE PRODUCT" or "SOFTWARE").

By exercising your rights to use the SOFTWARE PRODUCT, the LICENSEE agrees to be bound by the terms of this EULA. If the LICENSEE does not agree to the terms of this EULA, the LICENSEE may not use the SOFTWARE PRODUCT.

Copyright laws and international copyright treaties, as well as other intellectual property laws and treaties protect the SOFTWARE PRODUCT.

The SOFTWARE PRODUCT is licensed, not sold.

This software is NOT free!

Users can use limited version of this software for evaluation purposes without charge; for advanced features users must either purchase a license to use this program. Licensee may allow other users to evaluate copies of the unregistered Shareware. All evaluation users are subject to the terms of this agreement. If you want to use advanced features of this software a registration is required.

Activation

Activation section of the software allows to enable software. User self activate software using activation procedure and dongle interface.

User can activate the software on more machines with the same dongle.

1) GRANT OF LICENSE.

This EULA grants the LICENSEE the following permissions:

Installation and Use.

The LICENSEE is granted permission to use one registered copy of the licensed SOFTWARE on one single PocketPC

2) REPRODUCTION AND DISTRIBUTION.

The LICENSEE MUST NOT reproduce, distribute or make any copies of this SOFTWARE, or any of the accompanying material, for any purpose, except for making ONE copy for the LICENSEE'S own use - for backup purposes only.

3) DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.

a. Limitations on Reverse Engineering, Decompilation, and Disassembly.

The LICENSEE may not reverse engineer, decompile, or disassemble the SOFTWARE PRODUCT.

b. Software Transfer.

The rights granted under this EULA are personal to the LICENSEE only and are integral to the LICENSEE'S continued usage of the SOFTWARE PRODUCT.

The LICENSEE may not transfer, assign, sub-license or re-sell all or any of the rights granted under this EULA.

c. Termination.

Without prejudice to any other rights, ARlab may terminate this EULA if the LICENSEE fails to comply with the terms and conditions of this EULA. In such event, the LICENSEE must destroy ALL copies of the SOFTWARE PRODUCT and ALL of it's component parts.Where required by ARlab, the LICENSEE shall do all such things and acts, including but not limited to, signing a statutory declaration or affidavit verifying that the LICENSEE has destroyed ALL copies of the SOFTWARE PRODUCT and ALL of it's components in accordance with ARlab'S requirements following the termination of this EULA.

d. Other Restriction.

You may not rent or lease the SOFTWARE but you may transfer the SOFTWARE and accompanying written materials on a permanent basis provided you retain no copies and the recipient agrees to the terms of the agreement. You may not reverse engineer, decompile or disassemble the SOFTWARE. If the SOFTWARE is an update, any transfer must include the update and all prior versions in your possession.

4) COPYRIGHT.

All title to and copyrights in and to the SOFTWARE PRODUCT (including but not limited to any images, photographs, animations, video, audio, music, text, and "applets" incorporated into the SOFTWARE PRODUCT), and any copies of the SOFTWARE PRODUCT are owned by ARlab.

Copyright laws and international treaty provisions protect the SOFTWARE PRODUCT.

Therefore, the LICENSEE must treat the SOFTWARE PRODUCT like any other Copyrighted material.

5) LIMITED WARRANTY.

a. NO WARRANTIES.

The LICENSEE acknowledges that it has purchased the SOFTWARE PRODUCT "as is" and based upon the LICENSEE'S own knowledge, own requirements and needs, and not based upon any representation or warranty of ARlab.

ARlab expressly disclaims any warranty for the SOFTWARE PRODUCT. The SOFTWARE PRODUCT and any related documentation is provided "as is" without warranty of any kind, either express or implied, including, without limitation, the implied warranties or merchantability, fitness for a particular purpose, or non-infringement.

The entire risk arising out of use or performance of the SOFTWARE PRODUCT remains with the LICENSEE.

b. NO LIABILITY FOR CONSEQUENTIAL DAMAGES.

NO LIABILITY FOR CONSEQUENTIAL DAMAGES. IN NO EVENT SHALL ARlab BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION, DAMAGES FOR BUSINESS INTERRUPTION, LOSS OF PROFITS OR DATA, OR OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE OR DOCUMENTATION EVEN IF ARlab HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ARlab SHALL HAVE NO LIABILITY FOR ANY DATA READ, ACCESSED, STORED OR PROCESSED WITH THE SOFTWARE, INCLUDING THE COSTS OF RECOVERING SUCH DATA. IN NO CASE SHALL ARlab's LIABILITY EXCEED THE FEES PAID BY YOU FOR THE SOFTWARE. BECAUSE SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU.