DiagBox 7.57 – Automatic VIN Detection, Connectivity & Communication Issue

[Krazy8]

Hello,

I'm hoping someone can help me with an issue I'm having with my DiagBox installation.

I'm running DiagBox 7.57 on Windows 7 32-bit with a PSA XS Evolution-compatible interface (Reference 963830B). The interface is detected correctly by Windows, and the PSA Interface Checker reports:

Firmware: APPLI_XS_Fuji_P106138A V4.3.2 @ACTIA 03.01.14
Status: INIT OK

Before installing 7.57, I performed a fresh installation and followed the installation package exactly as supplied, updating all the way to DiagBox 7.83. However, on 7.83, automatic VIN detection did not work at all.

I then reinstalled DiagBox and updated only to 7.57. This improved things, as automatic VIN detection now starts and is able to read the VIN, but I am still experiencing two issues:

During automatic VIN detection, DiagBox displays a "Connectivity Unavailable" message stating that Internet and PSA access are unavailable. Instead of completing VIN detection offline, the process stops and asks me either to diagnose the connection or cancel. I was under the impression that DiagBox 7.57 should work offline, so I'm unsure why it is requesting an Internet connection.
After selecting the vehicle and attempting to perform a maintenance operation (ECU reset/service function), DiagBox displays a "Communication Error" and does not proceed.

Things I have already checked:

Windows detects the interface correctly.
PSA Interface Checker reports INIT OK.
Firmware version is APPLI_XS_Fuji_P106138A V4.3.2 @ACTIA 03.01.14.
APPDIAG.SYS exists in C:\AWRoot\bin\fi and is 192 bytes.
The interface is able to communicate well enough to identify the vehicle and read the VIN.
I have followed the installation package and update sequence exactly as provided.

Has anyone experienced DiagBox requesting an Internet connection during automatic VIN detection on what should be an offline installation? Could this be a software/configuration issue, or is there something else I should be checking?

Any advice or suggestions would be greatly appreciated.

[mickthemaverick]

Have you tested the kit on a different car?

[Paul-R]

How many different vehicles did you test VIN identification on for each of the Diagbox levels? I don't use my Diagbox very much nowadays but I do remember having the same problem with the VIN once. I think it was a Xsara Picasso but can't be sure. I recall seeing a post by wheeler (who knows a thing or two) and he said that even the genuine dealer installations sometimes don't auto-detect the VIN.

I haven't had the "Connectivity Unavailable" message but then I keep my Diagbox within the WiFi area of my house. Having said that I did once take my Diagbox out and didn't get any bleating about a connection problem.

I run Diagbox 7.58 which is mostly good enough for my 2015 308. The only problem I have is an inability to autodetect the type of engine ECU, which is quite easy to select, and being unable to add another ignition key. I was prepared to update to 7.62 if necessary but the higher you go up in the numbers, the more you find that certain facilities are withdrawn for local use and require not only a connection to the internet but access to the Stellantis servers. This may have been what you came up against. Incidentally I was able to add a key using a different diagnostic machine so never went beyond 7.58.

You will often see advice to switch the WiFi off on a clone Diagbox machine, even on this site. But when I spoke with Jim at Easydiagnostics he said to keep it on but not to accept any offer to connect to the servers or update. If you do accidentally click on yes then, provided you have made a copy of Appdiag.sys after a successful installation, then this can be rolled back.

[Krazy8]

How many different vehicles did you test VIN identification on for each of the Diagbox levels? I don't use my Diagbox very much nowadays but I do remember having the same problem with the VIN once. I think it was a Xsara Picasso but can't be sure. I recall seeing a post by wheeler (who knows a thing or two) and he said that even the genuine dealer installations sometimes don't auto-detect the VIN.

I haven't had the "Connectivity Unavailable" message but then I keep my Diagbox within the WiFi area of my house. Having said that I did once take my Diagbox out and didn't get any bleating about a connection problem.

I run Diagbox 7.58 which is mostly good enough for my 2015 308. The only problem I have is an inability to autodetect the type of engine ECU, which is quite easy to select, and being unable to add another ignition key. I was prepared to update to 7.62 if necessary but the higher you go up in the numbers, the more you find that certain facilities are withdrawn for local use and require not only a connection to the internet but access to the Stellantis servers. This may have been what you came up against. Incidentally I was able to add a key using a different diagnostic machine so never went beyond 7.58.

You will often see advice to switch the WiFi off on a clone Diagbox machine, even on this site. But when I spoke with Jim at Easydiagnostics he said to keep it on but not to accept any offer to connect to the servers or update. If you do accidentally click on yes then, provided you have made a copy of Appdiag.sys after a successful installation, then this can be rolled back.

Thanks for the information. I've only tested it on one vehicle, as I don't have access to another vehicle at the moment. Do you think it's worth trying it with an Internet connection to see if the "Connectivity Unavailable" message disappears? I was under the impression that DiagBox 7.57 should work offline, so I'm not sure whether this behaviour is normal or if it points to an issue with my installation.

[Krazy8]

Have you tested the kit on a different car?

No, unfortunately not. I don't have access to another vehicle to test it on at the moment.

[Paul-R]

As you're having a problem anyway why not?

Did you make a copy of Appdiag.sys? Have you tried copying it back to overwrite the current Appdiag.sys?

[parnell]

Hello,

I'm hoping someone can help me with an issue I'm having with my DiagBox installation.

I'm running DiagBox 7.57 on Windows 7 32-bit with a PSA XS Evolution-compatible interface (Reference 963830B). The interface is detected correctly by Windows, and the PSA Interface Checker reports:

Firmware: APPLI_XS_Fuji_P106138A V4.3.2 @ACTIA 03.01.14
Status: INIT OK

Before installing 7.57, I performed a fresh installation and followed the installation package exactly as supplied, updating all the way to DiagBox 7.83. However, on 7.83, automatic VIN detection did not work at all.

I then reinstalled DiagBox and updated only to 7.57. This improved things, as automatic VIN detection now starts and is able to read the VIN, but I am still experiencing two issues:

During automatic VIN detection, DiagBox displays a "Connectivity Unavailable" message stating that Internet and PSA access are unavailable. Instead of completing VIN detection offline, the process stops and asks me either to diagnose the connection or cancel. I was under the impression that DiagBox 7.57 should work offline, so I'm unsure why it is requesting an Internet connection.
After selecting the vehicle and attempting to perform a maintenance operation (ECU reset/service function), DiagBox displays a "Communication Error" and does not proceed.

Things I have already checked:

Windows detects the interface correctly.
PSA Interface Checker reports INIT OK.
Firmware version is APPLI_XS_Fuji_P106138A V4.3.2 @ACTIA 03.01.14.
APPDIAG.SYS exists in C:\AWRoot\bin\fi and is 192 bytes.
The interface is able to communicate well enough to identify the vehicle and read the VIN.
I have followed the installation package and update sequence exactly as provided.

Has anyone experienced DiagBox requesting an Internet connection during automatic VIN detection on what should be an offline installation? Could this be a software/configuration issue, or is there something else I should be checking?

Any advice or suggestions would be greatly appreciated.

I had very similar issues with my car recently... the mistake I made was that I selected a C8 rather than a C8 CAN model.... this tiny error absolutely screws everything as the CAN models are more recent builds and so the tool expects a completely different configuration. I thought this meant an installation or a driver issue so I reinstalled everything and was incredibly frustrated before I chanced upon trying the CAN version.... lo and behold diagbox lit up like a Christmas tree....

Now if only I could solve my DPF issue...
Anyway hope that helps.
P.s. That "Connectivity Unavailable" thing means nothing - you should be avoiding any internet connection during the diagnosis.