[diagnostic206]

Hello,
I read that the startkeycenter in 07.2018 is no longer needed. D A S is automatically activated when I activate Xentry Developer?

If I want to start D A S Sim, I get the message No langugage defined. What do I have to do?

Many Thanks

[DBCT]

Hello,
I read that the startkeycenter in 07.2018 is no longer needed. D A S is automatically activated when I activate Xentry Developer?

If I want to start D A S Sim, I get the message No langugage defined. What do I have to do?

Many Thanks

Did you add the normal DAS simulation parameters to the SimDAS call?

[diagnostic206]

Hello,
I read that the startkeycenter in 07.2018 is no longer needed. D A S is automatically activated when I activate Xentry Developer?

If I want to start D A S Sim, I get the message No langugage defined. What do I have to do?

Many Thanks

Did you add the normal DAS simulation parameters to the SimDAS call?

no which exactly?

[aaronmb83]

Thank you for this guide. I've followed the provided instructions but am still getting "Provided StartKey is invalid" when running ConfigSAssist and attempting to use the Xentry DeveloperV1.1.0 key generator and manually upload the StartKey. I continued following the other steps up through 10 (DAS 0 day) and then copied the standalone full size into the bin directory. I can launch the standalone but cannot change the language to English. I am using the Xentry_Diagnostics_OpenShell_18.7.4 file obtained via torrent and just let the installer do it's own thing. The one I installed did not have "Pass Through" in its name, perhaps I have the wrong installer? I obtained the torrent link for that one via another forum.

[JSL]

Thank you for this guide. I've followed the provided instructions but am still getting "Provided StartKey is invalid" when running ConfigSAssist and attempting to use the Xentry DeveloperV1.1.0 key generator and manually upload the StartKey. I continued following the other steps up through 10 (DAS 0 day) and then copied the standalone full size into the bin directory. I can launch the standalone but cannot change the language to English. I am using the Xentry_Diagnostics_OpenShell_18.7.4 file obtained via torrent and just let the installer do it's own thing. The one I installed did not have "Pass Through" in its name, perhaps I have the wrong installer? I obtained the torrent link for that one via another forum.

I don't know about the licence key issue, but to use english language you can launch DAS with -len switch, i.e. from either commandline or .bat:

DAS32R2sd.exe -len

The -l switch stands for language, en for english. You can use the -l switch for other languages as well.

[pesona]

@aaronmb83

there are two model of xentry diagnostic. you have to choose the installer based on your device.

1. Xentry_Diagnostics_OpenShell_18.7.4 installer is used with sdconnect device, xentry connect and MB VCI.
2. xentry Diagnostics passthru is used with passthru device e.g vas5054A

"Provided StartKey is invalid" error usually because of you don't run the "reg" file inside Old key loader for configassist

[aaronmb83]

Thank you for this guide. I've followed the provided instructions but am still getting "Provided StartKey is invalid" when running ConfigSAssist and attempting to use the Xentry DeveloperV1.1.0 key generator and manually upload the StartKey. I continued following the other steps up through 10 (DAS 0 day) and then copied the standalone full size into the bin directory. I can launch the standalone but cannot change the language to English. I am using the Xentry_Diagnostics_OpenShell_18.7.4 file obtained via torrent and just let the installer do it's own thing. The one I installed did not have "Pass Through" in its name, perhaps I have the wrong installer? I obtained the torrent link for that one via another forum.

I don't know about the licence key issue, but to use english language you can launch DAS with -len switch, i.e. from either commandline or .bat:

DAS32R2sd.exe -len

The -l switch stands for language, en for english. You can use the -l switch for other languages as well.

Great information and it worked. Thank you

---

@aaronmb83

there are two model of xentry diagnostic. you have to choose the installer based on your device.

1. Xentry_Diagnostics_OpenShell_18.7.4 installer is used with sdconnect device, xentry connect and MB VCI.
2. xentry Diagnostics passthru is used with passthru device e.g vas5054A

"Provided StartKey is invalid" error usually because of you don't run the "reg" file inside Old key loader for configassist

Thank you. I'm doing this is a favor for a friend of mine and didn't realize there was a difference in hardware.. I'm just the free IT guy after all He has the SD Connect hardware (judging from online pictures).

So, for a bit of good news, I was able to get the passthrough system licensed in ConfigAssist and appearing to work, but of course it complains about the missing SAE J2534 drivers and device because I'm assuming I don't have one to connect to it (drivers would likely be included in the hardware?).

So It looks like what I need is the openshell version, which is only available via mega in the OP, but if I download the torrent linked in this thread: https://cartechnology.co.uk/showthread.php?tid=38886 , is it safe to assume these same sets of instructions will work? That would be great news if so.

Now for the bad news which I'm assuming is unavoidable: I'm guessing these two systems cannot be installed concurrently, so I'm looking at another OS wipe and reinstall once I pull XDOS (Xentry OpenShell) version down?

Edit: Oddly enough I see that the original install package listed both XDOS and PassThru in the filename , but I don't recall seeing a menu to select one or the other when running start.exe. Note, running setup.exe on the ISO just asked me to use start.exe once the pre-requisites were done installing.

[Rik]

I have an exclamation mark on display adapter intel hd4000 in device manager and FN+ to increase and decrease the monitor dim bright dont work.
My laptop is a Lenovo X230 and none of the KB4093118 and KB4103718 updates are installed!!

[aaronmb83]

Reinstalled using the Mercedes-Benz Xentry.OpenShell.XDOS 2018.09 (18.9.4)
and the instructions provided here. The only thing I altered was using the 2221-45 file linked in the OP. Even though ConfigAssist is licensed , I'm getting an error regarding the 2221-45 when launching Xentry (both SIM and regular). Any thoughts? The filename I replaced under /Xentry/fusuko/eclipse/plugins was identical and I used the one from the rar.

Edit: Well I followed the instructions in the text file also linked in the OP and I think my critical mistake was not removing the old .jar files. I assumed if I renamed them then it wouldn't load the incorrect ones, but maybe it just loads all *.jar files within that directory at load? Hell if I know, but when I removed the old ones I was able to get them to load. Well, at least the SIM and regular version, not the ATK.

This has been quite a learning process. Will be connecting the sd-connect device tomorrow and am interested in seeing if Xentry and DAS will actually work at this point.

[W123]

Reinstalled using the Mercedes-Benz Xentry.OpenShell.XDOS 2018.09 (18.9.4)
and the instructions provided here. The only thing I altered was using the 2221-45 file linked in the OP. Even though ConfigAssist is licensed , I'm getting an error regarding the 2221-45 when launching Xentry (both SIM and regular). Any thoughts? The filename I replaced under /Xentry/fusuko/eclipse/plugins was identical and I used the one from the rar.

Edit: Well I followed the instructions in the text file also linked in the OP and I think my critical mistake was not removing the old .jar files. I assumed if I renamed them then it wouldn't load the incorrect ones, but maybe it just loads all *.jar files within that directory at load? Hell if I know, but when I removed the old ones I was able to get them to load. Well, at least the SIM and regular version, not the ATK.

This has been quite a learning process. Will be connecting the sd-connect device tomorrow and am interested in seeing if Xentry and DAS will actually work at this point.

Yes - even if the old one exists in the same folder under a different name, it is found and triggers that error.