Merged Lexia & Diagbox threads
-
- Forum Admin Team
- Posts: 39720
- Joined: 15 Sep 2015, 19:38
- x 6291
Re: Merged Lexia & Diagbox threads
This is just the Bluetooth add-on module (or a clone of it) used by PSA. It does not replace the VCI interface. It is offered in addition to the main VCI hardware.
Please Don't PM Me For Technical Help
Marc
Marc
-
- Posts: 339
- Joined: 07 Sep 2011, 11:03
- x 5
Re: Merged Lexia & Diagbox threads
Do I have to backup the APPDIAG.SYS before starting Diagbox for the very first time?
I was not paying attention (or should I say, I was paying attention to the installation instruction too much) and started Diagbox after installing 7.01 (default version) to update to 7.02 (which is done when Diagbox is started the first time).
I have not connected VCI to the vehicle or anything yet.
I was not paying attention (or should I say, I was paying attention to the installation instruction too much) and started Diagbox after installing 7.01 (default version) to update to 7.02 (which is done when Diagbox is started the first time).
I have not connected VCI to the vehicle or anything yet.
2006 C6 Exclusive 2.7HDi
1982 GSA Pallas
A couple of bikes
A boyracer car
1982 GSA Pallas
A couple of bikes
A boyracer car
-
- Posts: 339
- Joined: 07 Sep 2011, 11:03
- x 5
Re: Merged Lexia & Diagbox threads
Also, is there a list of Diagbox/Lexia update description for each revision? The latest is not always the best, in some cases...
Cheers.
Cheers.
2006 C6 Exclusive 2.7HDi
1982 GSA Pallas
A couple of bikes
A boyracer car
1982 GSA Pallas
A couple of bikes
A boyracer car
-
- (Donor 2020)
- Posts: 7490
- Joined: 08 Jun 2011, 18:04
- x 2626
Re: Merged Lexia & Diagbox threads
I was just looking down the list of stuff it's supposed to do according the ED's website Mark, as I said it seems to suggest it will do all that Lexia does.
I've had sod all luck with my Lexia, never been able to get it to do anything despite spending hours setting it up repeatedly, when I needed it most (to secondary bleed the ABS/ESP) I borrowed a Snap on kit from my neighbour's grandson which did the trick in no time.
I've had sod all luck with my Lexia, never been able to get it to do anything despite spending hours setting it up repeatedly, when I needed it most (to secondary bleed the ABS/ESP) I borrowed a Snap on kit from my neighbour's grandson which did the trick in no time.
Anyone who has never made a mistake has never tried anything new. (Albert Einstein)
-
- Forum Admin Team
- Posts: 39720
- Joined: 15 Sep 2015, 19:38
- x 6291
Re: Merged Lexia & Diagbox threads
Once it has activated and updated to 7.02, exit the programme and copy the file to a safe location.sonoramicommando wrote: ↑13 Mar 2018, 19:26 Do I have to backup the APPDIAG.SYS before starting Diagbox for the very first time?
I was not paying attention (or should I say, I was paying attention to the installation instruction too much) and started Diagbox after installing 7.01 (default version) to update to 7.02 (which is done when Diagbox is started the first time).
I have not connected VCI to the vehicle or anything yet.
Please Don't PM Me For Technical Help
Marc
Marc
-
- Forum Admin Team
- Posts: 39720
- Joined: 15 Sep 2015, 19:38
- x 6291
Re: Merged Lexia & Diagbox threads
yes they are very hit and miss Gibbo. I suspect the Bluetooth option is more robust with less to go wrong in terms of cable connections which can easily get strained. It will be interesting now these are coming onto the ‘user’ market as to whether they can do everything the VCI can do. I say this as Citroen have had these out since at least 2015 yet still have the main VCI in use.Gibbo2286 wrote: ↑13 Mar 2018, 19:33 I was just looking down the list of stuff it's supposed to do according the ED's website Mark, as I said it seems to suggest it will do all that Lexia does.
I've had sod all luck with my Lexia, never been able to get it to do anything despite spending hours setting it up repeatedly, when I needed it most (to secondary bleed the ABS/ESP) I borrowed a Snap on kit from my neighbour's grandson which did the trick in no time.
Please Don't PM Me For Technical Help
Marc
Marc
-
- Posts: 339
- Joined: 07 Sep 2011, 11:03
- x 5
Re: Merged Lexia & Diagbox threads
GiveMeABreak wrote: ↑13 Mar 2018, 20:15Once it has activated and updated to 7.02, exit the programme and copy the file to a safe location.sonoramicommando wrote: ↑13 Mar 2018, 19:26 Do I have to backup the APPDIAG.SYS before starting Diagbox for the very first time?
I was not paying attention (or should I say, I was paying attention to the installation instruction too much) and started Diagbox after installing 7.01 (default version) to update to 7.02 (which is done when Diagbox is started the first time).
I have not connected VCI to the vehicle or anything yet.
Phew... I'm on track then.
I installed some drivers and managed to get rid of all the yellow question mark devices in the devices list. Only couple of differences in the device list before and after, which are 1) Bluetooth bus enumerator and 2) Infineon trusted platform module.
Thanks.
2006 C6 Exclusive 2.7HDi
1982 GSA Pallas
A couple of bikes
A boyracer car
1982 GSA Pallas
A couple of bikes
A boyracer car
-
- (Donor 2020)
- Posts: 1877
- Joined: 19 Jan 2015, 18:42
- x 225
Re: Merged Lexia & Diagbox threads
GiveMeABreak wrote: ↑13 Mar 2018, 10:25 Excellent - I treat mine like a baby as I know how sensitive these things are! Good luck troubleshooting the AP fault.
Aren't they just... I think it spat it's dummy out after being used on the Xantia, maybe didn't enjoy being left in the freezing cold car overnight!
Either way it's working/worked long enough for me to ascertain that it's a glow plug/post heat related fault (plugs permanently supplied), joy of joys just hoping there's some simple explanation and not duff glow plugs!
'95 Xantia LX 1.9D-auto, Black, 118k
'97 306 XS 1.6i, Blaze Yellow, 24k
'96 ZX SX 1.9TD rolling shell, White, 81k
'97 306 XS 1.6i, Blaze Yellow, 24k
'96 ZX SX 1.9TD rolling shell, White, 81k
-
- Forum Admin Team
- Posts: 39720
- Joined: 15 Sep 2015, 19:38
- x 6291
Re: Merged Lexia & Diagbox threads
ok, so to deal with the TPM issue, you should be able to go into the BIOS and disable it from there. It was a security device used to protect / track the laptop used mainly in corporate systems. Once you have disabled the module, that should stop the exclamation mark and remove it from the device manager.sonoramicommando wrote: ↑13 Mar 2018, 21:10GiveMeABreak wrote: ↑13 Mar 2018, 20:15Once it has activated and updated to 7.02, exit the programme and copy the file to a safe location.sonoramicommando wrote: ↑13 Mar 2018, 19:26 Do I have to backup the APPDIAG.SYS before starting Diagbox for the very first time?
I was not paying attention (or should I say, I was paying attention to the installation instruction too much) and started Diagbox after installing 7.01 (default version) to update to 7.02 (which is done when Diagbox is started the first time).
I have not connected VCI to the vehicle or anything yet.
Phew... I'm on track then.
I installed some drivers and managed to get rid of all the yellow question mark devices in the devices list. Only couple of differences in the device list before and after, which are 1) Bluetooth bus enumerator and 2) Infineon trusted platform module.
Thanks.
Please Don't PM Me For Technical Help
Marc
Marc
-
- Posts: 339
- Joined: 07 Sep 2011, 11:03
- x 5
Re: Merged Lexia & Diagbox threads
GiveMeABreak wrote: ↑13 Mar 2018, 21:52 ok, so to deal with the TPM issue, you should be able to go into the BIOS and disable it from there. It was a security device used to protect / track the laptop used mainly in corporate systems. Once you have disabled the module, that should stop the exclamation mark and remove it from the device manager.
I don't have any exclamation marks now that I installed the driver - what I meant was I assumed either the bluetooth bus enumerator or TPM was the unknown device with the exclamation mark before I updated the driver.
Is Diagbox known to have an issue with TPM? Would it be best to disable this as you suggested as a proactive measure?
2006 C6 Exclusive 2.7HDi
1982 GSA Pallas
A couple of bikes
A boyracer car
1982 GSA Pallas
A couple of bikes
A boyracer car
-
- Forum Admin Team
- Posts: 39720
- Joined: 15 Sep 2015, 19:38
- x 6291
Re: Merged Lexia & Diagbox threads
No it will be fine left alone now the driver is installed and won’t affect anything.
Please Don't PM Me For Technical Help
Marc
Marc
-
- Donor 2023
- Posts: 7194
- Joined: 07 May 2009, 16:24
- x 1420
Re: Merged Lexia & Diagbox threads
Have you seen this blog Marc? I've just started reading my way through.
http://blog.obd2diy.fr/2017/12/28/solve ... -telecode/
http://blog.obd2diy.fr/2017/12/28/solve ... -telecode/
As I get older I think a lot about the hereafter - I go into a room and then wonder what I'm here after.
Inside every old person is a young person wondering what the hell happened.
"Trying is the first step towards failure" ~ Homer J Simpson
Inside every old person is a young person wondering what the hell happened.
"Trying is the first step towards failure" ~ Homer J Simpson
-
- Forum Admin Team
- Posts: 39720
- Joined: 15 Sep 2015, 19:38
- x 6291
Re: Merged Lexia & Diagbox threads
Yes I’ve probably read most of that in other places Paul. I find it easier for newer Diagbox owners to advise they keep to a lower Diagbox version where their cars do not need a higher version than open a can of worms about editing configuration files. It’s enough just to get Diagbox working at all in a lot of cases Paul so I personally won’t go into that on this forum
Another thing to consider is a user may need to revert to an earlier Diagbox version and would require copying these user-modified files backward and forwards; which is self-defeating because it would negate any changes and fixes introduced in later versions to fix bugs. It’s another reason why I stopped updating the change logs between versions of DB on the Wiki. The problem would often be a fix to update a previous bug in one module for certain vehicles, but at the same time, the update would introduce a new problem for another vehicle that worked fine in an earlier update! So you could end up copying the bugged versions of the modified config files back over to the newer version and undo the fixes made to cure the previous faults.
Another thing to consider is a user may need to revert to an earlier Diagbox version and would require copying these user-modified files backward and forwards; which is self-defeating because it would negate any changes and fixes introduced in later versions to fix bugs. It’s another reason why I stopped updating the change logs between versions of DB on the Wiki. The problem would often be a fix to update a previous bug in one module for certain vehicles, but at the same time, the update would introduce a new problem for another vehicle that worked fine in an earlier update! So you could end up copying the bugged versions of the modified config files back over to the newer version and undo the fixes made to cure the previous faults.
Please Don't PM Me For Technical Help
Marc
Marc
-
- Posts: 339
- Joined: 07 Sep 2011, 11:03
- x 5
Re: Merged Lexia & Diagbox threads
well, almost about to throw the towel.
the first thing it says when diagbox is started up, cannot find vehicle communication card etc. the tool has the green light comes up, blinks three times and stays on.
the first thing it says when diagbox is started up, cannot find vehicle communication card etc. the tool has the green light comes up, blinks three times and stays on.
2006 C6 Exclusive 2.7HDi
1982 GSA Pallas
A couple of bikes
A boyracer car
1982 GSA Pallas
A couple of bikes
A boyracer car
-
- Forum Admin Team
- Posts: 39720
- Joined: 15 Sep 2015, 19:38
- x 6291
Re: Merged Lexia & Diagbox threads
Ok, so you are running XP, make sure you have installed .net framework 3.5 from microsoft’s site:
https://www.microsoft.com/en-gb/downloa ... aspx?id=21
You need this in XP if you have not already installed it.
Unfortunately no 2 installs are the same because of the different user hardware and software, but stay with it
Also check the connections on the cables, sometimes the pins can get bent or become loose which may be causing the communication error.
https://www.microsoft.com/en-gb/downloa ... aspx?id=21
You need this in XP if you have not already installed it.
Unfortunately no 2 installs are the same because of the different user hardware and software, but stay with it
Also check the connections on the cables, sometimes the pins can get bent or become loose which may be causing the communication error.
Please Don't PM Me For Technical Help
Marc
Marc