Меню

Cal 830 das номер ошибки

  • #2

заменить раму цезаря. cal 830 насколько вижу по инету — к этой неисправности не относится.

  • #3

в апдейтах первый пункт — очистить…
830 с таким серийным номером будет обязательно ;)

  • #4

Это рама Цезаря? Все 4?

sdconnect-K6R4008C1D-UI10.jpg

сообщение было автоматически прилеплено: Сен 10, 2019

Да не, серийник там …925) затер на фотке

  • #5

речь не про серийник, а по 830 ошибку. да, на картинке оно. нового только такого не бывает — это либо перемаркировка, либо б.у.

830 ошибка скорей всего из-за левых патчей и прочего, не имеющего отношения к CE RAM.

  • #6

Ок, буду заказывать микрухи и пересаживать. Пока есть ошибка по ext CE RAM, я думаю, ничего работать не будет.
830 вылезает только когда уже все возможности DAS по идентификации авто исчерпаны.

  • #8

Если не ошибаюсь память samsung можно заменить на issi IS61C5128AL-10TLI

  • #10

Если не ошибаюсь память samsung можно заменить на issi IS61C5128AL-10TLI

Вопрос решился заменой 4 микросхем памяти RAM. В моем мультике стояли ISSY IS61LV5128AL-10TLI, заменил на Samsung K6R4008C1D-UI10.

Источник

Tips and guides for DAS fault (1.1)-99.830.0 and error 830:

DAS-ERROR-CAL-830-4 DAS-ERROR-CAL-830-1 DAS-ERROR-CAL-830-2 DAS-ERROR-CAL-830-3

Tips and guides

The das standalone is a patch, the bin folder fixes are associated with the same version of the standalone patch.
They replace the bin folder to match the version of the standalone patch if you are not running the same version of Das

The only place the bin folder fixes belong is in the bin as I have stated in the past. These type of solutions are derived from the Abu Dhabi con men of self appointed experts (JC disciples).They create solutions, which creates new problems, then create solutions to the problems that they have created…it’s an endless cycle of regurgitating shit all in there own self contained bubble.

Every now and then someone escapes the bubble wanting know what the hell is going on

You need a patched das32r2.exe for the version of das you are running, nothing more nothing less.
You don’t need to rename it and have the original file for xentry and the patched as standalone, it will work for both
You don’t need to modify SimDas to point to the renamed patched version, it will work with the mod

All of these bullshit solutions come from the Abu Dhabi boys in there self contained bubble of shit!!!!

For those who are in the know, they will tell you that you don’t even need the modded file to be able to run it in standalone

Btw, I always have the solution, I was the first to mod it without bin folder bubble replacements.
I suggest you re-read your first post again, I just told you why you are getting that problem without directly telling you why
Regards
Impactops

December 17, 2018


car diagnostic tool , obd2 software

Источник

  1. 28th January, 2015, 01:04 PM


    #1

    Hi i have installed xentry das 03.2014 version. After i made xentry and das registration i have error connection. I have try many bin files but same.
    When sdconnect recognise car voltage , cannt recognise vin so dosent make diagnose !Please help to resolve my problem !Regards

  2. 28th January, 2015, 11:36 PM


    #2

    Default

    What Patch are you using to run DAS standalone?

  3. 29th January, 2015, 10:28 PM


    #3

    Default

    No patch , different bin folders, include das standalone!

  4. 30th January, 2015, 08:28 AM


    #4

    Default

    Quote Originally Posted by kumbari
    View Post

    No patch , different bin folders, include das standalone!

    The das standalone is a patch, the bin folder fixes are associated with the same version of the standalone patch.
    They replace the bin folder to match the version of the standalone patch if you are not running the same version of Das

    The only place the bin folder fixes belong is in the bin as I have stated in the past. These type of solutions are derived from the Abu Dhabi con men of self appointed experts (JC disciples).They create solutions, which creates new problems, then create solutions to the problems that they have created…it’s an endless cycle of regurgitating shit all in there own self contained bubble.

    Every now and then someone escapes the bubble wanting know what the hell is going on

    You need a patched das32r2.exe for the version of das you are running, nothing more nothing less.
    You don’t need to rename it and have the original file for xentry and the patched as standalone, it will work for both
    You don’t need to modify SimDas to point to the renamed patched version, it will work with the mod

    All of these bullshit solutions come from the Abu Dhabi boys in there self contained bubble of shit!!!!

    For those who are in the know, they will tell you that you don’t even need the modded file to be able to run it in standalone

    Regards
    Impactops

  5. 30th January, 2015, 09:40 AM


    #5

    Default

    Quote Originally Posted by impactops
    View Post

    The das standalone is a patch, the bin folder fixes are associated with the same version of the standalone patch.
    They replace the bin folder to match the version of the standalone patch if you are not running the same version of Das

    The only place the bin folder fixes belong is in the bin as I have stated in the past. These type of solutions are derived from the Abu Dhabi con men of self appointed experts (JC disciples).They create solutions, which creates new problems, then create solutions to the problems that they have created…it’s an endless cycle of regurgitating shit all in there own self contained bubble.

    Every now and then someone escapes the bubble wanting know what the hell is going on

    You need a patched das32r2.exe for the version of das you are running, nothing more nothing less.
    You don’t need to rename it and have the original file for xentry and the patched as standalone, it will work for both
    You don’t need to modify SimDas to point to the renamed patched version, it will work with the mod

    All of these bullshit solutions come from the Abu Dhabi boys in there self contained bubble of shit!!!!

    For those who are in the know, they will tell you that you don’t even need the modded file to be able to run it in standalone

    Regards
    Impactops

    So do you have any solution or not?

  6. 30th January, 2015, 12:18 PM


    #6

    Default

    I always have the solution, I was the first to mod it without bin folder bubble replacements.

    Have I posted on this forum? what do you think?

    I suggest you re-read your first post again, I just told you why you are getting that problem without directly telling you why

    Regards
    Impactops

  7. The Following User Says Thank You to impactops For This Useful Post:

    kumbari (30th January, 2015)

  8. 30th January, 2015, 01:12 PM


    #7

    Default

    Quote Originally Posted by impactops
    View Post

    I always have the solution, I was the first to mod it without bin folder bubble replacements.

    Have I posted on this forum? what do you think?

    I suggest you re-read your first post again, I just told you why you are getting that problem without directly telling you why

    Regards
    Impactops

    Hi friend ! Can you help me to solve that problem ? If you need any skype write on pm ! Thanks !

  9. 30th January, 2015, 01:27 PM


    #8

    Default

    Quote Originally Posted by impactops
    View Post

    I always have the solution, I was the first to mod it without bin folder bubble replacements.

    Have I posted on this forum? what do you think?

    I suggest you re-read your first post again, I just told you why you are getting that problem without directly telling you why

    Regards
    Impactops

    As you write : ou need a patched das32r2.exe for the version of das you are running, nothing more nothing less.
    You don’t need to rename it and have the original file for xentry and the patched as standalone, it will work for both
    You don’t need to modify SimDas to point to the renamed patched version, it will work with the mod

    I cannt understand what happen becasue i have 2 c4 buy on different sellers , both have same serial : 101044. One has that problems on the fist time i used , and after no more problems ! the second one i buy one week ago and have the same symptoms but cannt resolve the problem !

 

Источник

Posts: 103
Threads: 12
Thanks Received: 7 in 6 posts

Thanks Given: 0
Joined: Apr 2015

Reputation:

229

14-07-2016, 16:12
(This post was last modified: 22-03-2017, 09:42 by Satria.)

it is time to move on. PartD is dead since 03-2016.
I deliberately delete this thread’s contents and only use it for my personal need. I suggest you to buy sdconnect or passthru to be used with latest xdos.
I apologize for all the inconvenience caused

Posts: 257
Threads: 4
Thanks Received: 0 in 0 posts

Thanks Given: 0
Joined: Nov 2015

Reputation:

882

[ please give me reputation with funny comments.]

Wrong forum for that. So like & thanks will have to do.

As for a funny comment, how about this? «Donald Trump for President of USA!»

Posts: 103
Threads: 12
Thanks Received: 7 in 6 posts

Thanks Given: 0
Joined: Apr 2015

Reputation:

229

(14-07-2016, 19:31)Diagnostix Wrote: [ please give me reputation with funny comments.]

Wrong forum for that. So like & thanks will have to do.

As for a funny comment, how about this?  «Donald Trump for President of USA!»

It looks like this is what i want. laughing with friends here 😀 😀
sorry oot

Posts: 103
Threads: 12
Thanks Received: 7 in 6 posts

Thanks Given: 0
Joined: Apr 2015

Reputation:

229

PartD (C3) is officially dead since xdos 03-2016 version Dead

I get many pm asking for latest xdos (xentry + das) for C3.

Sadly, i have to say officially since xdos 03-2016, partD aka C3 is strip away from xdos (xentry and das) vci driver dll.
that’s why you get CAL/CAESAR error code 830 in Xentry and DAS.
CAL 830 is CAL initialisaton of vci, failed.

for DAS to work, you can replace the new xdos caesar vci driver with the 12-2015 version and it is still work up to 09-2016. (please, I don’t support it)

for xentry to work, you have to replace the new caesar vci driver also and edit many java manifest plugins. 1087
the easy way is like some chinese seller do, replace the whole xentry with its 12-2015 brother. it is useless. what is the benefit of this trick only boost selling and make a fool for a busy mb mechanic.

so, IMHO, please keep partD (c3) for xentry xp.

The newer XDOS release strength is focus and deeper in online capabilities, remove ecu offline procedure one by one and the worst is, limited maximum vmax in some truck. (e.g in Bharat Benz from vmax 120 km/h to only vmax 80 km/h. for other mb truck, i will look at it when i have time)

just my 2 cents

Источник

четвертый день ставлю сам ,и не хрена не выходит, версия 11 2012 … а главное как таковых ошибок не показывает ,,, ругается на диск вываливает лог и заканчивает установку …. как я его только не форматировал ,, разными прогоми это делал ,,, в разных последовательностях , разные размеры , на разных буках а все одно и тоже …. конец установки и лог … даже установочные диски перекачивал … только вот жесткий не менял всегда один и тот-же …—

сам ЛОГ

——————————

Пожалуйста, распечатайте эту информацию и обратитесь с ней в Вашу службу технической поддержки !

Computer Name: ‘DAS-34C’, Lan-Id: , Country-code: 7, System: WLANMiniPCI

Original Partitioning

———————-

Total Size of Harddisk = 152627 MB

Number of Partitions = 4

1. Partition = STAR, size: 31289 MB, used: 4974 MB, available: 26315 MB

2. Partition = RECOVER, size: 12352 MB, used: 1752 MB, available: 10600 MB

3. Partition = WIS, size: 47050 MB, used: 2563 MB, available: 44487 MB

4. Partition = DAS, size: 47056 MB, used: 46 MB, available: 47010 MB

Available Free Space on Harddisk = 14880 MB

Current Partitioning:

———————

Total Size of Harddisk = 152627 MB

Number of Partitions = 4

1. Partition = STAR, size: 31289 MB, used: 4974 MB, available: 26315 MB

2. Partition = RECOVER, size: 12352 MB, used: 1752 MB, available: 10600 MB

3. Partition = WIS, size: 47050 MB, used: 2563 MB, available: 44487 MB

4. Partition = DAS, size: 47056 MB, used: 46 MB, available: 47010 MB

Available Free Space on Harddisk = 14880 MB

unsupported harddisk size for repartitioning

РАСПЕЧАТАЙТЕ ЭТО СООБЩЕНИЕ И НАПРАВЬТЕ ПО ФАКСУ В ВАШУ СЛУЖБУ ТЕХНИЧЕСКОЙ ПОДДЕРЖКИ !

Системный номер: _____________________

Номер предприятия: ________________________________________________________

Населённый пункт/страна: ________________________________________________________

Клиентский номер: _____________________

Системный язык: _____________________

————————

contents of partinfo.txt

————————

Paragon Log Results.

Date Generated: Fri Nov 09 14:40:21 2012

Script command: select disk 0

Script command: dDiskSize=

dDiskSize=152627

Script command: dNumParts=

dNumParts=4

Script command: select partition C

Script command: dSpaceUsed=

select disk 0

select partition Extended

Script command: dSpaceExtended

Script command: select partition C

Script command: dSpaceUsed=

dSpaceUsed=31289

Script command: dSpaceRemaining=

dSpaceRemaining=14880

select disk 0

Script command: Select Partition First

Script command: check

Script command: dPartitionUsed=

dPartitionUsed=4974

Script command: dPartitionRemaining=

dPartitionRemaining=26314

Script command: Select Partition Last

Script command: check

Script command: GetSelectedPartitionSize

14877

Script command: Select Partition First

Script command: GetLabel

Current Label: Star

Script command: PartSpace=

PartSpace=31289

Script command: dPartitionUsed=

dPartitionUsed=4974

Script command: dSpaceRemaining=

dSpaceRemaining=26314

Script command: GetLabel

Current Label: Recover

Script command: PartSpace=

PartSpace=12352

Script command: dPartitionUsed=

dPartitionUsed=1752

Script command: dSpaceRemaining=

dSpaceRemaining=10599

Script command: GetLabel

Current Label: WIS

Script command: PartSpace=

PartSpace=47050

Script command: dPartitionUsed=

dPartitionUsed=2563

Script command: dSpaceRemaining=

dSpaceRemaining=44486

Script command: GetLabel

Current Label: DAS

Script command: PartSpace=

PartSpace=47056

Script command: dPartitionUsed=

dPartitionUsed=46

Script command: dSpaceRemaining=

dSpaceRemaining=47009

—————————

contents of partcreate.txt

—————————

!file not present!

———————————-

contents of PARTITIONING_ERROR.TXT

———————————-

11-9-2012 14:40:02 ‘Partitioning’ Initialisation, DAS-34C, SD Compact 3 WLAN, WLANMiniPCI, Script_ver: 2012051013:00

====================================================================================================================

Line: 318 (Pre Log Start)

Line: 364 Operating System is: ‘Windows XP’

Line: 423 found: Service Pack 3

Line: 447 No Startparameter

Line: 691 (Pre Log End)

INFO: rel.file= Setup.ini; [Line: 4119] (Partitioning) ReadIniFile() ‘G:stardiagPartitioningSetup.ini’

INFO: rel.file= Setup.ini; [Line: 726] (Partitioning) C:ProgrammeParagon does not exist, has to be installed ini: 20120515 vers:

INFO: rel.file= Setup.ini; [Line: 755] (Partitioning) Paragon not installed

INFO: rel.file= Setup.ini; [Line: 859] (Partitioning) write version.txt: [partition version] update = 20120515

INFO: rel.file= checkPartitionsNew; [Line: 1604] (Partitioning) start

INFO: rel.file= get partitioninfo of HD-drive; [Line: 2020] (Partitioning) CMD: C:ProgrammeParagonLZSprogramscripts.exe par.: C:ProgrammeParagonLZSscripts2partinfo.psl -Wno -s -o c:Programmedasuinstpartinfo.txt

INFO: rel.file= get partitioninfo of HD-drive; [Line: 2039] (Partitioning) disk size: 152627, no of parts: 4, remaining hdd space: 14880

INFO: rel.file= get partitioninfo of HD-drive; [Line: 2063] (Partitioning) values extracted (partition 1):label:’ Star’, size: 31289, used: 4974, remaining: 26315

INFO: rel.file= get partitioninfo of HD-drive; [Line: 2069] (Partitioning) storing partition label in uppercase: STAR

INFO: rel.file= get partitioninfo of HD-drive; [Line: 2063] (Partitioning) values extracted (partition 2):label:’ Recover’, size: 12352, used: 1752, remaining: 10600

INFO: rel.file= get partitioninfo of HD-drive; [Line: 2069] (Partitioning) storing partition label in uppercase: RECOVER

INFO: rel.file= get partitioninfo of HD-drive; [Line: 2063] (Partitioning) values extracted (partition 3):label:’ WIS’, size: 47050, used: 2563, remaining: 44487

INFO: rel.file= get partitioninfo of HD-drive; [Line: 2069] (Partitioning) storing partition label in uppercase: WIS

INFO: rel.file= get partitioninfo of HD-drive; [Line: 2063] (Partitioning) values extracted (partition 4):label:’ DAS’, size: 47056, used: 46, remaining: 47010

INFO: rel.file= get partitioninfo of HD-drive; [Line: 2069] (Partitioning) storing partition label in uppercase: DAS

INFO: rel.file= writePartitionInfoToVersionFile(); [Line: 1952] (Partitioning) start

INFO: rel.file= writePartitionInfoToVersionFile(); [Line: 1978] (Partitioning) out

INFO: rel.file= dumpPartitionInfo(); [Line: 2106] (Partitioning) dumping var values

INFO: rel.file= dumpPartitionInfo(); [Line: 2119] (Partitioning) label:’ STAR’, size: 31289, remaining: 26315

INFO: rel.file= dumpPartitionInfo(); [Line: 2119] (Partitioning) label:’ RECOVER’, size: 12352, remaining: 10600

INFO: rel.file= dumpPartitionInfo(); [Line: 2119] (Partitioning) label:’ WIS’, size: 47050, remaining: 44487

INFO: rel.file= dumpPartitionInfo(); [Line: 2119] (Partitioning) label:’ DAS’, size: 47056, remaining: 47010

INFO: rel.file= dumpPartitionInfo(); [Line: 1684] (Partitioning) Copy Resize-Log = C:Programmedasuinst11-9-201214:40:21partcreate.txt

INFO: rel.file= ; [Line: 2248] (Partitioning) needsRepartitioning_Compact3W

INFO: rel.file= needsRepartitioning_Compact3W(); [Line: 2780] (Partitioning) start

INFO: rel.file= needsRepartitioning_Compact3W(); [Line: 2802] (Partitioning) unsupported harddisk size for repartitioning [55000,125000]

INFO: rel.file= needsRepartitioning_Compact3W(); [Line: 1696] (Partitioning) needsRepartioning() done = OK

INFO: rel.file= trace after check needsRepartioning(); [Line: 1721] (Partitioning) RetryCounter = 1

INFO: rel.file= isDrivePresent; [Line: 3986] (Partitioning) isDrivePresent([pDrive]’E:’)

INFO: rel.file= isDrivePresent; [Line: 3997] (Partitioning) drive is present

INFO: rel.file= isDrivePresent; [Line: 3986] (Partitioning) isDrivePresent([pDrive]’F:’)

INFO: rel.file= isDrivePresent; [Line: 3997] (Partitioning) drive is present

INFO: rel.file= isDrivePresent; [Line: 1782] (Partitioning) E: and F: present, checking labels

INFO: rel.file= getLabelOfVolumeCurrentlyMountedOnDrive; [Line: 4010] (Partitioning) getLabelOfVolumeCurrentlyMountedOnDrive([pDrive]’E:’)

INFO: rel.file= getLabelOfVolumeCurrentlyMountedOnDrive; [Line: 4022] (Partitioning) label: ‘WIS’

INFO: rel.file= getLabelOfVolumeCurrentlyMountedOnDrive; [Line: 1786] (Partitioning) E: label (already uppercased): ‘WIS’

INFO: rel.file= getLabelOfVolumeCurrentlyMountedOnDrive; [Line: 4010] (Partitioning) getLabelOfVolumeCurrentlyMountedOnDrive([pDrive]’F:’)

INFO: rel.file= getLabelOfVolumeCurrentlyMountedOnDrive; [Line: 4022] (Partitioning) label: ‘DAS’

INFO: rel.file= getLabelOfVolumeCurrentlyMountedOnDrive; [Line: 1790] (Partitioning) F: label (already uppercased): ‘DAS’

INFO: rel.file= getLabelOfVolumeCurrentlyMountedOnDrive; [Line: 1815] (Partitioning) RetryCounter = 1, lnResult = -7

INFO: rel.file= writePartInfo2(); [Line: 3446] (Partitioning) start

может всетаки жесткий ,,, просто пойду куплю а это не он …старался сам — не выходит …ну все делал , толку ноль и всегда кончается этим логом .

может знает кто..

Источник

0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии

А вот еще интересные материалы:

  • Яшка сломя голову остановился исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного где ошибка
  • Caa50021 ошибка office 365
  • Ca559 ошибка на коматсу

    • ➤