+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: Mercedes Benz - Smart (https://cartechnology.co.uk/forumdisplay.php?fid=63)
+---- Thread: DAS CAL Error 830 C4 (/showthread.php?tid=70335)
DAS CAL Error 830 C4 - 6ergsm - 16-10-2022
Good moning,
decided to update my MB Diagnostic Laptop because my Release from 2014 don't fits for newer cars.
So I decided to install Xentry OpenShell 2021.06 LOGIN OFFLINE+HHT+DTS Monaco+Vediamo (Acronis) UPD 14.07.2022
Install startkey and config C4 Clone.
After tried to make connection to A169, in DAS came "CAESAR FIRMWARE loaded to RAM" and I got Error (1.5)-3.830.0. CAL error number 830.Caesar Com constructor failed twice (0 and 0) (row 227).
Search few forums to find a working solution. Tried to change cal.ini, cla.sli, cal_real.dll, changed das32r2sd.exe, copied complete bin directory but nothing solved this problem.
Maybe the Release is damaged so I deceides to take an other one BUT the same error.
Find another threat somebody change ceasar file but with less infos which one and where I find working ones?
Please help need also old cars working diagnostic
Thx
RE: DAS CAL Error 830 C4 - gcs190 - 16-10-2022
The problem is in that image and it is quite difficult to find out what is wrong in someone else's work, my advice: install it yourself from scratch.
RE: DAS CAL Error 830 C4 - motorotor - 17-10-2022
This problem is easy to solve. Do not listen to fools who do not understand the problem and how to solve it. Your plexor needs other blacklist files. Those files that you add will not suit you.
RE: DAS CAL Error 830 C4 - gcs190 - 17-10-2022
(17-10-2022, 07:09 AM)motorotor Wrote: This problem is easy to solve. Do not listen to fools who do not understand the problem and how to solve it. Your plexor needs other blacklist files. Those files that you add will not suit you.
FYI: DAS blacklist gives error 870, you need to learn a bit more of other people's work instead of just copying it. This way you would know how not to cause an error that became history with the XDOS versions.
See you later... IGNORANT!!!
RE: DAS CAL Error 830 C4 - motorotor - 17-10-2022
Judging by your answer, you do not quite understand how it works, because you only write about known problems. And this problem makes you stupor. Unlike you, I know how to solve it. There is no solution to this problem on the Internet, so this is causing you difficulty. Try to figure out how to solve it.
RE: DAS CAL Error 830 C4 - gcs190 - 17-10-2022
(17-10-2022, 11:07 AM)motorotor Wrote: Judging by your answer, you do not quite understand how it works, because you only write about known problems. And this problem makes you stupor. Unlike you, I know how to solve it. There is no solution to this problem on the Internet, so this is causing you difficulty. Try to figure out how to solve it.
After searching the net and in different forums, I have not only shared the solution for the old versions prior to XDOS, but I have also solved it for countless users, but when an XDOS image with SD Connect presents that problem, it is because the I think it did not know what it was doing and although the solution is easy, if the installer was able to create an insistent problem, everything else can have the same development, therefore spending time on such a precarious system is not worth it.
As I told the OP elsewhere: I am not going to waste my time or yours on a system that is so lacking.
EDIT:This discussion is unproductive, I already told the OP not to waste my time on a system that doesn't inspire confidence in me, fix it and at least the thread will have been of some use.
RE: DAS CAL Error 830 C4 - motorotor - 17-10-2022
The solution to this problem was not created by you, don't flatter yourself. At least I didn't see him. The working version has been used by me since 2016 and it does not depend on the assembly. This problem is directly related to the multiplexer. Different plexors use a different solution and if I encounter this problem during activation, I solve it in such a way that everything works. You, apart from words and crooked decisions, did not really offer anything here. I have been following your solutions closely for many years, but after a while I realized that they all have no value, so they were removed in my builds and replaced with more correct ones.
You couldn't even make a wi-fi fix properly, although it was all solved with just a few lines of code.
In my new versions, I will definitely add your name to the code and send you away. If you're smart enough to find it, you might be good at something. But I'm not sure if you have the skills to do it.