Alfaobd Requirements

0 views

Skip to first unread message

Clidia Panahon

unread,

Aug 3, 2024, 12:02:33 PM8/3/24

to dysfeikillbe

The limitations of the demo version:

- Application run time limit of 15 minutes. Application returns to the first screen after 15 minutes of connection to a control unit.
- No active diagnostic procedures available
- The number of scanned gauges is limited by four
- The number of monitored parameters is limited by four
Other features are same as in the full version. No expiration is imposed on the application.

Note: if you purchase using the credit card option, the license code can be provided immediately after the order has been processed. The activation mail will be sent to you with a copy of the license code.

- Install the app on your PC, open it and switch to the About tab. Click on the "Purchase license on Paddle.com" button. The web purchase screen opens, see Method 1. In case of an issue contact in...@alfaobd.com

Note: License activattion as described is not supported on Windows XP. To activate the license on XP contact in...@alfaobd.com attaching the License request code from the About screen of the app.

First deactivate the license on the current PC. Open the app, switch to the About tab, click on the "Activate license (Paddle.com)" button, and click "Deactivate" on the activation window. Then, on the new PC, install and open the app and activate the license as described above with the same activation data.

In case your PC has crashed and you can't deactivate the license, contact in...@alfaobd.com to delete the old activation.

NOTE: The customers who purchased the license before Aug. 11th 2020, or the customers who purchased the license from the distributors, please use the old activation model. Use the "Send activation request" feature to send the Llicense request code to in...@alfaobd.com (Or just send the About screen photo or screenshot with the request visible).

1. OBDKey Bluetooth/USB/ WLAN This interface is a universal one supporting all listed ECUs, both K-Line and CAN-based. An additional advantage of the interface is that a firmware upgrade can be provided by the producer if necessary.

2. ELM327-based Bluetooth/USB/ WLAN interface. There are many suppliers of such interfaces, make sure the version is 1.3 and above. The interface supports all CAN and most of the K-Line units. A rule of thumb is that the K-Line units with connection baud rate less than 10400 bps is not supported. Because the quality of ELM327 clones is not stable, it is recommended to use tested interfaces (see www.alfaobd.com for details).

Note: The interfaces have only pin 7 of the OBD plug internally connected to K-line converter. Fiat uses pin 7 for connections to engine and automatic gearbox controls only. The K lines from other units are connected to other pins of the car OBD plug. To be able to diagnose those units you need to modify your interface. A simple solution is to weld all the K line pins inside the interface together to pin 7. DO NOT CONNECT AN INTERFACE MODIFIED THIS WAY to Alfa Mito/ Giulietta, Fiat 500/500L/ Grande Punto/Punto Evo/Ducato 250 (see an explanation below)!

If you do not want to make any changes to the interface itself, here is a drawing of a universal adapter cable. You will need a male and a female OBD plugs, a cable and an 8-position DIP switch. Note: this design does not include Viaggio, Dart, Freemont, Thema.

After successfully configuring connection to the WiFi interface node you need to set a static IP address for the configured WiFi network on the Android device. The IP address has to be different from the IP address used by the interface, but it has to belong to the same network. For example if the interface IP address is 192.168.1.10 with subnet mask of 255.255.255.0, you can set IP address for the configured WiFi connection as 192.168.1.11 with the subnet 255.255.255.0. See WLAN interface manual for details on IP address and port number used by the interface.

There are freely available utilities for enabling ad-hoc connections and configuring IP address of the connection. Here on the screenshots Wifi327 is the configured ad-hoc connection to WLAN interface:

The OBD interface used is selected in the "Interface" list. AlfaOBD verifies the type of the interface connected during connection to a car ECU. If a wrong interface selected in the preferences, AlfaOBD can correct the selection.

"Request Interbyte" is the time between bytes in a request. The parameter is relevant for OBDKey interface only, and it is not applicable for ABS5.3 and Bosch ME3.7.1, M1.7/2.7, MA 1.7 control units. The default setting should be OK in most cases, but if the connection is unstable try to adjust this parameter.

"Inter Request time" is logically connected with the "Response-Request time". The communication between AlfaOBD and ECU is serial, that means it proceeds by series of request - response cycles. After sending a request for data or action, AlfaOBD waits for a response from the ECU. Only after receiving the response within the timeout limit, AlfaOBD can send the next request. Even if no requests for data or action is made by AlfaOBD, still it has to keep sending "Tester present" (or "Keep alive") requests, otherwise the connection will be terminated by the ECU. Typical time of complete request-response cycle is about 200 ms. So the "Response-Request" parameter determines time between the end of ECU response and the next request ("keep alive" or a request for data). Normally you can set this parameter to zero, but sometimes to improve stability of communication it is recommended to increase the value. "Inter Request time" is the time between consecutive requests, it varies from 200 ms to 60 sec. A longer period might be of use when scanning for slow changing data, like engine coolant or passenger compartment temperature. If high Inter Request time is selected, AlfaOBD automatically sends "keep alive" messages to ECU between the requests for data to prevent communication breakdown. If total "Response-Request time" value and request-response cycle time are higher than "Inter Request" value selected, AlfaOBD built-in algorithm optimizes communication timing considering also the timeout defined in the data exchange protocol specifications.

"KW71-Interbyte" is only applicable for ABS5.3 and Bosch ME3.7.1, M1.7/2.7, MA 1.7 ECUs. The parameter is relevant for OBDKey interface only. The data exchange is different from the one described above, the communication proceeds byte-by-byte. The parameter defines the time between the moment AlfaOBD receives a byte from ECU and the moment it sends a byte to ECU. The default setting is usually fine, try to adjust it if connection is unstable.

To save the faults and system status data, check the "Log recording" checkbox. AlfaOBD will save all the data obtained in a text file which can be found in the /sdcard/Android/data/com.android.AlfaOBD/files/logs folder. The name of the file is _Info.log, the file can be opened with a text editor.

"Debug Data recording" checkbox is for support and debugging purposes only, it should be checked when AlfaOBD Software needs data for troubleshooting. AlfaOBD creates AlfaOBD_Debug.bin file in the /sdcard/Android/data/com.android.AlfaOBD/files/logs folder. You are advised to send this file to AlfaOBD Software for debugging if requested. The file contains data exchange between AlfaOBD and ECU. Normally the check box should be unchecked, because recording of the debug data creates substantial overhead.

Select a make, model, function, and electronic control unit (ECU) to diagnose. Pay attention to the notification of the adaptor you need to connect between the car OBD plug and the interface. The needed adaptor is displayed in the ECU list. The use of the adaptor (or corresponding modification of the interface) is absolutely necessary, no connection to ECU can be done without it.

It is recommended to check if any adaptor is needed BEFORE establishing connection to the interface and BEFORE actually selecting ECU to diagnose (open the ECU list but do not push on the desired ECU, just check if any adaptor is suggested for it). If you need to connect an adaptor, the connection to the interface will be lost anyways because you will have to disconnect it from the car OBD plug, thus turning the interface power off.

Hint: if communication cannot be established, turn the ignition key to Stop, wait 30 sec then turn key to MAR and retry connect. Try to reset the interface by taking it out of the OBD plug and inserting it back.

The status of communication is reflected in the status box. When communication has been established and the connected ECU has been verified, you can proceed with reading fault codes, running active diagnostics, or scanning sensor data at the next tabs. If AlfaOBD can not verify the connected ECU, it displays a warning message and asks whether you want to continue or terminate the connection, because the diagnostic can be unreliable or not relevant.

AlfaOBD verifies the connected ECU by the Fiat ISO code. If the ISO code is not known to AlfaOBD, you will see the warning. You have an option to continue diagnostic (with unpredictable result) or terminate the connection. Please use the option to email the unknown ISO code to AlfaOBD to include the code into the next AlfaOBD database update.

"Login with code card" is enabled for certain units only (engine control units, Body computer, Steering lock, TEG reader, Code control, Central Lock RF receiver). You have to login with Code Card when running some active diagnostic or configuration procedures on these units. Login with Code Card might be of use when, for example, there is a problem with immobilizer which prevents engine from starting. Connect to the corresponding engine control unit, enter 5-digit code from the Code Card supplied with your car and push "Login with code card". Engine control unit does not provide any information whether login is successful or not. Just try to start your car with the ignition key, but do not turn the key to Stop while starting the engine. If you turn key to Stop, login has to be repeated after turning the key to MAR.