topblog Ivoire blogs

03/01/2018

How to add Cruice control to Vito viano W639 using DAS Developer mode

This tutorial of How to add Cruice control to Vito viano W639 via DAS Developer mode

(Source from the internet ,TRY AT YOUR  OWN RISK)

Add cruisecontrol / limiter to your Vito/Viano W639 it’s configuration.
This should work for all W639 till AJ08

In DAS Developer mode tested version 10-2008)

Used with SD connect C4 multiplexer

In engine control unit:
Entwicklungen (Development data) ->F3
Password : flexecu ->F3
Steuergerate – Anpassungen (Control unit adaption) ->F3
Steuergerate-Anpassungen (Variantencoderierung) ->F3
VCD_Transporter->F3
a Pop-up tells you : “Mindest eine Codiereinstellung ist ungultig” confirm -> OK

Here you will find the option settings
write down the line that is blue.
For example : NSG or NAG_Klima_Wasserstandschalter

Now we search for the string that contains the same options + Tempomat and Begrenzer
So that will look like : NSG or NAG_Tempomat_v-Begrenzer_Klima_Wasserstandschalter
Once you find it , click it and confirm with ->F3
“Soll die Codierung in Steuergerat ubertragen werden ?”->F3
JA or YES->F2 to proceed

Now we log out the engine ecu and go to the :
Instrument Cluster ( Kombi instrument) (Magnetti Marelli)

Steuergerate-Anpassungen (Variantencoderierung) ->F3
Variantencoderierung Algemeine Daten->F3
Scroll down untill you see “Limiter” set to Ja or Yes ->F3
F2 -> F1 -> F1
Ansteuerungen -> Gesamstliste aller Ansteuerungen ->
Scroll down untill you see the line : Steuergeraet Resetten (PowerON-Modus) (FN_Reset_SG_Power_ON)
Press F3 and confirm again with F3
Now you will see the “Kombiinstrument” reboots

Cruise control coding is added succesfully to your W639 now

 

http://www.mbstartool.com/

18/11/2017

SD connect C4 LAN & WiFi Configuration Manual

Status: I’ve started up SDNC to see if the connection is okay, and it turns green when I connect the multiplexer via LAN, but when I try the wifi it stays red. It can also read out some data from the multiplexer so I am assuming the the multiplexer is working fine too

Error: If I connect it to a car, DAS keeps popping up the (1.1)-1.501.9500 error (as I understand that must be some kind of communication problem). The car’s wiring is fine as KTS 520 can communicate with it.

 

Solution:How to configure SD connect C4 LAN & WiFi to solve DAS fault (1.1)-1.501.9500.

 

Tool: a clone SD connect C4

 

Software: 2011/3 Xentry

 

Status: I’ve started up SDNC to see if the connection is okay, and it turns green when I connect the multiplexer via LAN, but when I try the wifi it stays red. It can also read out some data from the multiplexer so I am assuming the the multiplexer is working fine too

 

Error: If I connect it to a car, DAS keeps popping up the (1.1)-1.501.9500 error (as I understand that must be some kind of communication problem). The car’s wiring is fine as KTS 520 can communicate with it.

 

Photos:

See the ceaser test post results

sdconnect-caesar

see the error message DAS gives

sdconnect-das-error

SDConnect toolkit says that my mux is available, but when I click on the button in the middle I get an error message, with an error code 750. That button is supposed to be for searching for multiplexers. This kind of gives me the impression that something isn’t quite working right :S
In the toolkit admin, it displays a serial number, says the mux is available. See in the attachments.

sd-connect-toolkit sd-connect-toolkit2 sdconnect-toolkit-admin-1 sdconnect-toolkit-admin-2

 

 

Solution:

It’s working!!! (At least it’s working via LAN, have not tried WLAN yet.)

I can’t believe it :O

Changed value in cal.ini to PART_W (to be exact, didn’t need to change it, it was PART_W, just left it that way :P).

As for the rest of the instructions, I haven’t been able to follow them exactly. I also got a vid with instructions and it’s a little bit different (I’ll post it here if anyone needs though). For example the LAN IP address is 172.29.127.112, but it seems to be working that way. Also I haven’t been able to configure the “road WLAN”, because it doesn’t matter what I enter into the “key” field, it keeps saying that the key cannot be divided by 2 and therefore it is not hexadecimal

Hope this isn’t going to hinder my chances of using WLAN…

But I’m going to find out in a few anyway.

 

EDIT: Also tried with LAN IP: 172.29.127.119, it doesn’t make a difference. SDConnect works with both IP-s.

Damn….I clicked on the “Delivery condition” button in the SDconnect toolkit, and now I cannot turn on the WLAN on SDconnect. I think it wrote something into the MUX’s software :S

The LAN connection still works though, so the MUX is not blocked yet luckily….

 

Look here: SD Connect Compact 4 LAN & WIFI configuration

 

SD connect C4 LAN configuration

sd-connect-c4-configuration-lan sd-connect-c4-configuration-lan1 sd-connect-c4-configuration-lan2 sd-connect-c4-configuration-lan3 sd-connect-c4-configuration-lan4 sd-connect-c4-configuration-lan5 sd-connect-c4-configuration-lan6 sd-connect-c4-configuration-lan7

SD connect C4 WIFI configuration

 

sd-connect-c4-configuration-Wlan1 sd-connect-c4-configuration-Wlan2 sd-connect-c4-configuration-Wlan3 sd-connect-c4-configuration-Wlan4 sd-connect-c4-configuration-Wlan5 sd-connect-c4-configuration-Wlan6 sd-connect-c4-configuration-Wlan7 sd-connect-c4-configuration-Wlan8

 

 

 

OBDexpress

SD connect C4 LAN & WiFi Configuration Manual

Status: I’ve started up SDNC to see if the connection is okay, and it turns green when I connect the multiplexer via LAN, but when I try the wifi it stays red. It can also read out some data from the multiplexer so I am assuming the the multiplexer is working fine too

Error: If I connect it to a car, DAS keeps popping up the (1.1)-1.501.9500 error (as I understand that must be some kind of communication problem). The car’s wiring is fine as KTS 520 can communicate with it.

 

Solution:How to configure SD connect C4 LAN & WiFi to solve DAS fault (1.1)-1.501.9500.

 

Tool: a clone SD connect C4

 

Software: 2011/3 Xentry

 

Status: I’ve started up SDNC to see if the connection is okay, and it turns green when I connect the multiplexer via LAN, but when I try the wifi it stays red. It can also read out some data from the multiplexer so I am assuming the the multiplexer is working fine too

 

Error: If I connect it to a car, DAS keeps popping up the (1.1)-1.501.9500 error (as I understand that must be some kind of communication problem). The car’s wiring is fine as KTS 520 can communicate with it.

 

Photos:

See the ceaser test post results

sdconnect-caesar

see the error message DAS gives

sdconnect-das-error

SDConnect toolkit says that my mux is available, but when I click on the button in the middle I get an error message, with an error code 750. That button is supposed to be for searching for multiplexers. This kind of gives me the impression that something isn’t quite working right :S
In the toolkit admin, it displays a serial number, says the mux is available. See in the attachments.

sd-connect-toolkit sd-connect-toolkit2 sdconnect-toolkit-admin-1 sdconnect-toolkit-admin-2

 

 

Solution:

It’s working!!! (At least it’s working via LAN, have not tried WLAN yet.)

I can’t believe it :O

Changed value in cal.ini to PART_W (to be exact, didn’t need to change it, it was PART_W, just left it that way :P).

As for the rest of the instructions, I haven’t been able to follow them exactly. I also got a vid with instructions and it’s a little bit different (I’ll post it here if anyone needs though). For example the LAN IP address is 172.29.127.112, but it seems to be working that way. Also I haven’t been able to configure the “road WLAN”, because it doesn’t matter what I enter into the “key” field, it keeps saying that the key cannot be divided by 2 and therefore it is not hexadecimal

Hope this isn’t going to hinder my chances of using WLAN…

But I’m going to find out in a few anyway.

 

EDIT: Also tried with LAN IP: 172.29.127.119, it doesn’t make a difference. SDConnect works with both IP-s.

Damn….I clicked on the “Delivery condition” button in the SDconnect toolkit, and now I cannot turn on the WLAN on SDconnect. I think it wrote something into the MUX’s software :S

The LAN connection still works though, so the MUX is not blocked yet luckily….

 

Look here: SD Connect Compact 4 LAN & WIFI configuration

 

SD connect C4 LAN configuration

sd-connect-c4-configuration-lan sd-connect-c4-configuration-lan1 sd-connect-c4-configuration-lan2 sd-connect-c4-configuration-lan3 sd-connect-c4-configuration-lan4 sd-connect-c4-configuration-lan5 sd-connect-c4-configuration-lan6 sd-connect-c4-configuration-lan7

SD connect C4 WIFI configuration

 

sd-connect-c4-configuration-Wlan1 sd-connect-c4-configuration-Wlan2 sd-connect-c4-configuration-Wlan3 sd-connect-c4-configuration-Wlan4 sd-connect-c4-configuration-Wlan5 sd-connect-c4-configuration-Wlan6 sd-connect-c4-configuration-Wlan7 sd-connect-c4-configuration-Wlan8

 

 

 

OBDexpress