http://www.auto-professionals.co.uk/ Sun, 03 May 2026 19:14:25 +0000 MyBB http://www.auto-professionals.co.uk/showthread.php?tid=24429 Thu, 23 Apr 2026 07:13:51 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=24429 Anybody knows if this interface works with DiagBox latest 2025/26 cars with DoiP and CanFD?
VXDIAG VCX SE PSA
Their site said yes but i ask "technician" and he says NO!
So hope someone her have experience with this.
Thanks.]]> Anybody knows if this interface works with DiagBox latest 2025/26 cars with DoiP and CanFD?
VXDIAG VCX SE PSA
Their site said yes but i ask "technician" and he says NO!
So hope someone her have experience with this.
Thanks.]]> http://www.auto-professionals.co.uk/showthread.php?tid=24173 Thu, 14 Dec 2023 17:22:46 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=24173 Can anyone tell me the original reference of the new PSA interface?]]> Can anyone tell me the original reference of the new PSA interface?]]> http://www.auto-professionals.co.uk/showthread.php?tid=19581 Fri, 07 Apr 2017 20:02:02 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=19581

auto-part-cirtroen-puegot-car-diagnose.jpg
File Type:
Downloaded:	44 times
Size:	5.86 KB

]]>

auto-part-cirtroen-puegot-car-diagnose.jpg
File Type:
Downloaded:	44 times
Size:	5.86 KB

]]> http://www.auto-professionals.co.uk/showthread.php?tid=18228 Mon, 11 Jul 2016 12:52:05 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=18228 I want to try to read the module my self and with help of the forum remove the crash data.
Thanks for looking at my post. ]]> I want to try to read the module my self and with help of the forum remove the crash data.
Thanks for looking at my post. ]]> http://www.auto-professionals.co.uk/showthread.php?tid=16020 Tue, 18 Aug 2015 09:39:45 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=16020
Here's a post for the purists of the PSA XS EVOLUTION ACTIA interface!

Edit your interface to make it equivalent to an original.

I do not will detail all the references of the components to be mounted on a clone or replace (resistors, capacitors and other IC), many of them are already known (full topic on French forum...) or easily identifiable with the "Marking code".

Let's start with the photos of a clone interface "made in china" to correct quality welds and good components placement.
Interface that is not a "FULL CHIP's", as you can see.



Circled in red, the locations to be equipped or components that are replaced:

Microprocessor PCB:





Relay PCB:






After an order with RS and Mouser:



We start by removing components "non-original" and clean (Lead free flux remover) PCB, and we get this:







we put in place new components then are welded



Once all components are in place and the two new PCB cleaned by LFFR, here's what we get:



Little comparison:

Microprocessor PCB:
Before:



After:



Before:



After:




Relay PCB:

Before:



After:



Before:



After:



The rendering is fairly obvious, but it's even more impressive on a good quality "FULL CHIP's", without printing!!!


Small technical explanation of the three components of the USB input of the microprocessor PCB, replaced on the clone interface of Chinese by capacitors and 0 ohm resistors:
In practice, it protects the USB input following this scheme:
With a fast common mode choke USB 1.1 and USB 2.0 associated with two TVS diodes for electrostatic discharge deletions.



Good change... Enjoy!!!


Regards.

List components reference.txt
File Type:
Downloaded:	16 times
Size:	1.08 KB

]]>
Here's a post for the purists of the PSA XS EVOLUTION ACTIA interface!

Edit your interface to make it equivalent to an original.

I do not will detail all the references of the components to be mounted on a clone or replace (resistors, capacitors and other IC), many of them are already known (full topic on French forum...) or easily identifiable with the "Marking code".

Let's start with the photos of a clone interface "made in china" to correct quality welds and good components placement.
Interface that is not a "FULL CHIP's", as you can see.



Circled in red, the locations to be equipped or components that are replaced:

Microprocessor PCB:





Relay PCB:






After an order with RS and Mouser:



We start by removing components "non-original" and clean (Lead free flux remover) PCB, and we get this:







we put in place new components then are welded



Once all components are in place and the two new PCB cleaned by LFFR, here's what we get:



Little comparison:

Microprocessor PCB:
Before:



After:



Before:



After:




Relay PCB:

Before:



After:



Before:



After:



The rendering is fairly obvious, but it's even more impressive on a good quality "FULL CHIP's", without printing!!!


Small technical explanation of the three components of the USB input of the microprocessor PCB, replaced on the clone interface of Chinese by capacitors and 0 ohm resistors:
In practice, it protects the USB input following this scheme:
With a fast common mode choke USB 1.1 and USB 2.0 associated with two TVS diodes for electrostatic discharge deletions.



Good change... Enjoy!!!


Regards.

List components reference.txt
File Type:
Downloaded:	16 times
Size:	1.08 KB

]]> http://www.auto-professionals.co.uk/showthread.php?tid=16003 Sat, 15 Aug 2015 18:58:14 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=16003
What for this program Free of this website and what VCI connector is used with it. PSA-UHDS
In the publisher's site I see other interesting programs. SMOK

Nice weekend AP.]]>
What for this program Free of this website and what VCI connector is used with it. PSA-UHDS
In the publisher's site I see other interesting programs. SMOK

Nice weekend AP.]]> http://www.auto-professionals.co.uk/showthread.php?tid=14940 Fri, 27 Mar 2015 11:14:25 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=14940
Here are some of the oscilloscope signal screenshots (Tektronix TDS 2012C) for those who want to try
 repair their EVO XS by understanding what they do ...!
This concerns the problems:
- No relay activation on electronic board of the same name,
- Failure to communicate on the vehicle computers,
Etc ...




The steering each relay is made with the two set of components: 8-bit serial-in, serial or parallel-out shift register with output
latches (HCT 595) + High Voltage, High Current Darlington Transistor Arrays (MC1413BDG or ULN2003).
The drivers are controlled by the PIC 16F684. To run this one in need of different signals
and various commands.

Description of ICP signals observed between the card and the Micro Relay:
- COM VPP control signal / 12Vdc supply to the input / MCLR of PIC
- COM VDD, control the 5Vdc power supply to the VDD input of PIC
- / CS, chip select signal PIC
- CLK signal of the clock of PIC
- SO, data signals for PIC





Screenshot COM VPP Control signal and VDD control signal on a functional interface:





COM VPP control signal/12VDC power goes from 0 to + 12Vdc of that connects the battery 12Vdc
on the relay card (jack connection on ODB).
COM VDD signal, it increases from 5Vdc to 0Vdc when the app is launched (I did the tests with lexia3 only)



During a diagnostic in GLOBAL TEST, that's what happens (warning on the screen of the oscilloscope, we see
signals of a non-functional interface):




Screenshot of clock signal CLK PIC on a functional interface:



The clock frequency is 6.45kHz.



Screenshot of clock signal CLK PIC on a non-functional interface:







Screenshot of clock signal CLK and /CS signal PIC on a functional interface:






Screenshot of clock signal CLK and /CS signal PIC on a non-functional interface:
Interface optocoupler 9871 A2 instead of 063N HCPL!






Screenshot of clock signal CLK and SO data signal PIC on a functional interface:







Screenshot of clock signal CLK and SO data signal PIC on a non-functional interface:
Interface optocouplers 9871 A2 instead of HCPL 063N!








Screenshot of /CS signal and SO data PIC signal on a functional interface:




In Hoping that this will be educational for some of you!


Best Regards.]]>
Here are some of the oscilloscope signal screenshots (Tektronix TDS 2012C) for those who want to try
 repair their EVO XS by understanding what they do ...!
This concerns the problems:
- No relay activation on electronic board of the same name,
- Failure to communicate on the vehicle computers,
Etc ...




The steering each relay is made with the two set of components: 8-bit serial-in, serial or parallel-out shift register with output
latches (HCT 595) + High Voltage, High Current Darlington Transistor Arrays (MC1413BDG or ULN2003).
The drivers are controlled by the PIC 16F684. To run this one in need of different signals
and various commands.

Description of ICP signals observed between the card and the Micro Relay:
- COM VPP control signal / 12Vdc supply to the input / MCLR of PIC
- COM VDD, control the 5Vdc power supply to the VDD input of PIC
- / CS, chip select signal PIC
- CLK signal of the clock of PIC
- SO, data signals for PIC





Screenshot COM VPP Control signal and VDD control signal on a functional interface:





COM VPP control signal/12VDC power goes from 0 to + 12Vdc of that connects the battery 12Vdc
on the relay card (jack connection on ODB).
COM VDD signal, it increases from 5Vdc to 0Vdc when the app is launched (I did the tests with lexia3 only)



During a diagnostic in GLOBAL TEST, that's what happens (warning on the screen of the oscilloscope, we see
signals of a non-functional interface):




Screenshot of clock signal CLK PIC on a functional interface:



The clock frequency is 6.45kHz.



Screenshot of clock signal CLK PIC on a non-functional interface:







Screenshot of clock signal CLK and /CS signal PIC on a functional interface:






Screenshot of clock signal CLK and /CS signal PIC on a non-functional interface:
Interface optocoupler 9871 A2 instead of 063N HCPL!






Screenshot of clock signal CLK and SO data signal PIC on a functional interface:







Screenshot of clock signal CLK and SO data signal PIC on a non-functional interface:
Interface optocouplers 9871 A2 instead of HCPL 063N!








Screenshot of /CS signal and SO data PIC signal on a functional interface:




In Hoping that this will be educational for some of you!


Best Regards.]]> http://www.auto-professionals.co.uk/showthread.php?tid=14734 Thu, 05 Mar 2015 17:11:27 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=14734
Hi all, anyone got any info/documentation on these battery supply protection units on PSA vehicles.
Struggling to get full description of how they operate.
Had two in with faults where I needed to test around them.
Thanks...]]>
Hi all, anyone got any info/documentation on these battery supply protection units on PSA vehicles.
Struggling to get full description of how they operate.
Had two in with faults where I needed to test around them.
Thanks...]]> http://www.auto-professionals.co.uk/showthread.php?tid=14685 Mon, 02 Mar 2015 16:24:11 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=14685
Here HD pictures of original PSA PPI Interface. Enjoy !

Microprocessor electronic PCB:












Relays electronic PCB:






If your interface is not recognized on USB port (because you have try to flash with nlc software ....(fail)); reflash MB90F546GS with ISP prog:






If you don't use nlc software on this, check USB connector welds and USB6B1 (ESD protection component) and USBN9603/4-28M USB FS node controller with his 24MHz quartz


Regards.]]>
Here HD pictures of original PSA PPI Interface. Enjoy !

Microprocessor electronic PCB:












Relays electronic PCB:






If your interface is not recognized on USB port (because you have try to flash with nlc software ....(fail)); reflash MB90F546GS with ISP prog:






If you don't use nlc software on this, check USB connector welds and USB6B1 (ESD protection component) and USBN9603/4-28M USB FS node controller with his 24MHz quartz


Regards.]]> http://www.auto-professionals.co.uk/showthread.php?tid=13574 Tue, 18 Nov 2014 21:06:58 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=13574

20141118_135405.jpg
File Type:
Downloaded:	63 times
Size:	51.59 KB

]]>

20141118_135405.jpg
File Type:
Downloaded:	63 times
Size:	51.59 KB

]]> http://www.auto-professionals.co.uk/showthread.php?tid=7041 Sat, 19 Oct 2013 13:10:47 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=7041
Looking for equipment at good price to reprogram kilometers on Peugeot 208 (cable and software).

I have the original cable but the diagbox do not alow any kind of fix on kilometers

Do i have to reprogram the dashboard only or the bsi also?

Is xprog-m the best solution?

Thank you]]>
Looking for equipment at good price to reprogram kilometers on Peugeot 208 (cable and software).

I have the original cable but the diagbox do not alow any kind of fix on kilometers

Do i have to reprogram the dashboard only or the bsi also?

Is xprog-m the best solution?

Thank you]]> http://www.auto-professionals.co.uk/showthread.php?tid=7002 Wed, 16 Oct 2013 18:12:38 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=7002
I would like to buy new Lexia 3 PSA XS Evolution, but I have heard it has problems with Citroen C5, anyone knows about this?

Thanks.]]>
I would like to buy new Lexia 3 PSA XS Evolution, but I have heard it has problems with Citroen C5, anyone knows about this?

Thanks.]]> http://www.auto-professionals.co.uk/showthread.php?tid=6873 Tue, 08 Oct 2013 02:05:58 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=6873 Thanks]]> Thanks]]> http://www.auto-professionals.co.uk/showthread.php?tid=4628 Wed, 15 May 2013 11:38:53 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=4628 http://www.auto-professionals.co.uk/show...p?tid=4605
I am the author of this program.
How it works ? In fact the Lexia interface has an MCU (Fujistu MB90F546GS) and an external SPI eeprom (Spansion or Winbond 25Q40, 25Q80 or equivalent).
In the external SPI eeprom is stored the serial number of the interface, and it is only used with new (Evolution) bootloader.
The MCU has internal flash memory separated into 3 zones : the firmware zone (sector 0 to 4), a data zone (sector 5), and the bootloader zone (sector 6).
The firmware zone contains the 4.x.x firmware (4.3.0 for the actual version), the data zone is only used with the old non Evolution bootloader) to store the serial number of the interface, and the bootloader zone contains the necessary code to manage the USB connection with the computer and permits firmware update through USB with MAJAppCom.exe computer software.
The Evolution/non-evolution USB recognition on the computer only depends on the bootloader, which manage the USB connection with the computer. It exists 2 differents bootloader, the old one (year 2003), and the new one (year 2007). All interfaces are shipped with the 2003 bootloader, are not recognized as Evolution on the computer and are not compatible with diagbox >5.29. With the new bootloader the interface is recognized as "Evolution" on the computer, and is compatible with last diagbox version (7.xx) if the SPI eeprom contains valid serial number string.

It's why you need to reflash your interface (MCU and eeprom) to work with last diagbox versions. But the bootloader zone cannot be accessed and reprogrammed to the new version (Evolution) through USB with MAJAppCom.exe software. It's why until now the only way to update the interface to Evolution was to flash a complete 4.3.0 dump (firmware+data zone+Evolution bootloader) through the 12 pin connector, and dessolder/reprogram/resolder the SPI eeprom.

Because I use this MCU at work, I well know this MCU and I have all developpement tools to develop embeded microcode.
Thus I have developped a specific firmware :
This specific firmware can be dowloaded with MAJAppCom.exe through USB in the firmware zone of the MCU. When the download is finished, the bootloader jumps on the firmware to execute it. When executed, my firmware do 4 things :

- It checks if the interface is compatible for the update. Because some interface with very simplified hardware has incompatibilites and cannot works with Evolution bootloader. If the firmware detects this kind of interface, it does nothing to not brick the interface. So you can replace an official firmware.
- If the interface is compatible, the firmware totaly erases the internal bootloader zone (sector 6), and flash the new bootloader (the firmware embeds the 16ko size Evolution bootloader image)
- If the interface is compatible, the firmware erases the sector 5 (data zone), because it is not used with the new Evolution bootloader
- If the interface is compatible, the firmware updates the external SPI eeprom content to store a valid serial number string

These steps take approximatively 10 seconds, after that (the interface led blinks), you unplug/replug the interface, and it will be recognized as Evolution after new driver installation.
The last step is to replace this specific firmware in the firmware zone of the MCU with an official firmware to have the interface working normally. You can do that manually with MAJAppCom.exe, or lets diagbox updates automatically the interface with the last official firmware.

This update technique is totally new and unpublished. As you can see in the thread I talked about at the beginning of this message, some dishonnest peoples try to sell my work. To avoid this, I protect my firmware by customizing it with personnal information of all person which ask me this firmware. It's why now I always ask for complete name, complete postal address, and a true personnal mail address (from your provider, not yahoo/hotmail/live/gmail and so on), to store these informations in the firmware file (visible with hexadecimal editor), to avoid sharing and selling of this file. I send this firmware for free, but you have the possibility to do a paypal donation of the amount you want if you are happy. It's symbolic but it's just because this was a big job and because customize the firmware and send it to you takes a lot of time.

Advertisement 1 : Please note this firmware will not make miracles, if your interface doesn't communicate correctly with the car because of an hardware problem, the flash will not correct this problem. It will just permits to working interface to become compatible with last diagbox version, and will normally solves the bad interface detection from diagbox (you always need to unplug/plug your interface to do diagnosis).

Advertisement 2 : I sent this firmware to a lot of people on french forums, it works correctly, but you will use it at your own risk, and because I will probably receive a lot of request, I will be not able to do any support, thus for questions or problems, please post on the forum, other people which successfully flashed their interface will be able to help you. The firmware is normally reliable, but in case of flashing problem the only way will be to reflash it with the old hardware method, take care about this.

Regards

Edit By Patrian
ANY Post who will cover something like this:
..."Hi NLC. Just i send you PM (or e-mail) for to give me my firmware, please send me"... (And any similar content):
They will REMOVED from the the AP Board!
Thanks for your Attention ppl! ]]> http://www.auto-professionals.co.uk/show...p?tid=4605
I am the author of this program.
How it works ? In fact the Lexia interface has an MCU (Fujistu MB90F546GS) and an external SPI eeprom (Spansion or Winbond 25Q40, 25Q80 or equivalent).
In the external SPI eeprom is stored the serial number of the interface, and it is only used with new (Evolution) bootloader.
The MCU has internal flash memory separated into 3 zones : the firmware zone (sector 0 to 4), a data zone (sector 5), and the bootloader zone (sector 6).
The firmware zone contains the 4.x.x firmware (4.3.0 for the actual version), the data zone is only used with the old non Evolution bootloader) to store the serial number of the interface, and the bootloader zone contains the necessary code to manage the USB connection with the computer and permits firmware update through USB with MAJAppCom.exe computer software.
The Evolution/non-evolution USB recognition on the computer only depends on the bootloader, which manage the USB connection with the computer. It exists 2 differents bootloader, the old one (year 2003), and the new one (year 2007). All interfaces are shipped with the 2003 bootloader, are not recognized as Evolution on the computer and are not compatible with diagbox >5.29. With the new bootloader the interface is recognized as "Evolution" on the computer, and is compatible with last diagbox version (7.xx) if the SPI eeprom contains valid serial number string.

It's why you need to reflash your interface (MCU and eeprom) to work with last diagbox versions. But the bootloader zone cannot be accessed and reprogrammed to the new version (Evolution) through USB with MAJAppCom.exe software. It's why until now the only way to update the interface to Evolution was to flash a complete 4.3.0 dump (firmware+data zone+Evolution bootloader) through the 12 pin connector, and dessolder/reprogram/resolder the SPI eeprom.

Because I use this MCU at work, I well know this MCU and I have all developpement tools to develop embeded microcode.
Thus I have developped a specific firmware :
This specific firmware can be dowloaded with MAJAppCom.exe through USB in the firmware zone of the MCU. When the download is finished, the bootloader jumps on the firmware to execute it. When executed, my firmware do 4 things :

- It checks if the interface is compatible for the update. Because some interface with very simplified hardware has incompatibilites and cannot works with Evolution bootloader. If the firmware detects this kind of interface, it does nothing to not brick the interface. So you can replace an official firmware.
- If the interface is compatible, the firmware totaly erases the internal bootloader zone (sector 6), and flash the new bootloader (the firmware embeds the 16ko size Evolution bootloader image)
- If the interface is compatible, the firmware erases the sector 5 (data zone), because it is not used with the new Evolution bootloader
- If the interface is compatible, the firmware updates the external SPI eeprom content to store a valid serial number string

These steps take approximatively 10 seconds, after that (the interface led blinks), you unplug/replug the interface, and it will be recognized as Evolution after new driver installation.
The last step is to replace this specific firmware in the firmware zone of the MCU with an official firmware to have the interface working normally. You can do that manually with MAJAppCom.exe, or lets diagbox updates automatically the interface with the last official firmware.

This update technique is totally new and unpublished. As you can see in the thread I talked about at the beginning of this message, some dishonnest peoples try to sell my work. To avoid this, I protect my firmware by customizing it with personnal information of all person which ask me this firmware. It's why now I always ask for complete name, complete postal address, and a true personnal mail address (from your provider, not yahoo/hotmail/live/gmail and so on), to store these informations in the firmware file (visible with hexadecimal editor), to avoid sharing and selling of this file. I send this firmware for free, but you have the possibility to do a paypal donation of the amount you want if you are happy. It's symbolic but it's just because this was a big job and because customize the firmware and send it to you takes a lot of time.

Advertisement 1 : Please note this firmware will not make miracles, if your interface doesn't communicate correctly with the car because of an hardware problem, the flash will not correct this problem. It will just permits to working interface to become compatible with last diagbox version, and will normally solves the bad interface detection from diagbox (you always need to unplug/plug your interface to do diagnosis).

Advertisement 2 : I sent this firmware to a lot of people on french forums, it works correctly, but you will use it at your own risk, and because I will probably receive a lot of request, I will be not able to do any support, thus for questions or problems, please post on the forum, other people which successfully flashed their interface will be able to help you. The firmware is normally reliable, but in case of flashing problem the only way will be to reflash it with the old hardware method, take care about this.

Regards

Edit By Patrian
ANY Post who will cover something like this:
..."Hi NLC. Just i send you PM (or e-mail) for to give me my firmware, please send me"... (And any similar content):
They will REMOVED from the the AP Board!
Thanks for your Attention ppl! ]]> http://www.auto-professionals.co.uk/showthread.php?tid=4605 Tue, 14 May 2013 08:57:42 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=4605
No need to send
No need to disassemble
No need to soldering]]>
No need to send
No need to disassemble
No need to soldering]]> http://www.auto-professionals.co.uk/showthread.php?tid=3079 Thu, 14 Mar 2013 18:57:14 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=3079
But this special error always returns. Now I´m thinking about the possibility to try an obd2 device with my handy an this app

Would it be really possible to delete error codes like the say in the description?

Best regard

inkaman]]>
But this special error always returns. Now I´m thinking about the possibility to try an obd2 device with my handy an this app

Would it be really possible to delete error codes like the say in the description?

Best regard

inkaman]]> http://www.auto-professionals.co.uk/showthread.php?tid=2967 Sat, 09 Mar 2013 22:18:42 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=2967
I have a problem with on of my PSA EVO kit.
It is from yellow people

The problem is that after choosing a car it does not recognize the VIN number (on another clone unit it does). After manual entering it has no connection to car modules.
Device is recognized in Windows XP normal. On working unit there is a clicking sound from relay, from broken one there is none.
I tested the unit on Diagbox 5.29, 6.36 and 7.06 and it does not work (the good one works normal).

Has some one any idea what this could be?

Here is image from Interface checker

]]>
I have a problem with on of my PSA EVO kit.
It is from yellow people

The problem is that after choosing a car it does not recognize the VIN number (on another clone unit it does). After manual entering it has no connection to car modules.
Device is recognized in Windows XP normal. On working unit there is a clicking sound from relay, from broken one there is none.
I tested the unit on Diagbox 5.29, 6.36 and 7.06 and it does not work (the good one works normal).

Has some one any idea what this could be?

Here is image from Interface checker

]]> http://www.auto-professionals.co.uk/showthread.php?tid=2847 Tue, 05 Mar 2013 14:03:48 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=2847
Where to buy Peugeot Planet Measure interface?

Features of this tool:

MULTIMETER
VOLTMETER AC/DC
AMMETER
OHMMETER
LED TEST
OSCILLOSCOPE
O2 SENSOR TESTER

Thanks

Best Regards]]>
Where to buy Peugeot Planet Measure interface?

Features of this tool:

MULTIMETER
VOLTMETER AC/DC
AMMETER
OHMMETER
LED TEST
OSCILLOSCOPE
O2 SENSOR TESTER

Thanks

Best Regards]]> http://www.auto-professionals.co.uk/showthread.php?tid=2383 Tue, 12 Feb 2013 16:39:55 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=2383 I have some questions about PSA EVO Interface,
Because it works on Citroen C5 and Peugeot 307?
It is the fault of the software or tool?
Actia PSA EVO Interface can be used?
Anything you should know before buying PSA EVO Interface clone?

Thanks and best regards

]]> I have some questions about PSA EVO Interface,
Because it works on Citroen C5 and Peugeot 307?
It is the fault of the software or tool?
Actia PSA EVO Interface can be used?
Anything you should know before buying PSA EVO Interface clone?

Thanks and best regards

]]> http://www.auto-professionals.co.uk/showthread.php?tid=2042 Wed, 30 Jan 2013 10:47:02 +0000 http://www.auto-professionals.co.uk/showthread.php?tid=2042
I would like to know if someone here have experience and / or would advice the usage of PSA XS interface to diagnose the PSA engines installed on different other auto brands (e.g. Ford, Mazda, etc.)
The question is if somebody did it so far, and if there are some adaptations needed in order to succeed and not destroying the interface itself or damage any of the car computers.

Any advice would be highly appreciated.
P.S. I'm interested in using the equipment for a Ford car using DV6 engine from PSA.

Best Regards,
laur.]]>
I would like to know if someone here have experience and / or would advice the usage of PSA XS interface to diagnose the PSA engines installed on different other auto brands (e.g. Ford, Mazda, etc.)
The question is if somebody did it so far, and if there are some adaptations needed in order to succeed and not destroying the interface itself or damage any of the car computers.

Any advice would be highly appreciated.
P.S. I'm interested in using the equipment for a Ford car using DV6 engine from PSA.

Best Regards,
laur.]]>