topblog Ivoire blogs

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

17/11/2017

Ktag 7.026 Reviews

Ktag 7.026 discussion at http://mhhauto.com/,See how do people think of this?

 

 

 

 

ktag 7.026 pcb

1

This 7.026 update is all ready available from EU. “Problem ” is resetting. NXP need replace when time to reset tokens, after 30 writing. That can do few times if have good skills and good tools for this.

 

2

when you turn 1 job down you will think l should off upgraded , alot more gpt connections on newer ecu,s

 

3

7.026 is the one with 3 NXP mcu’s . everyone with 30 writings. i use it allow. all working ok and i think by the time i will use all 90 writings a new tool will come.

 

4

if you need Denso Nec NBD family the only tool doing this 100% is my 7.026. 7.020 will NOT MAKE DENSO NEC NBD even 15%. there may be 1 or 2 of the ecus it can do but that’s it. and no one aside from us can offer you 7.026 as its socketed solution. anyone who tells you 7.020 can make denso nec nbd 100% is just gonna take your money

 

5

I have ktag 7.026. Tool is OK.

Although it requires a good coffee machine… my reworked ktag 6.070 is MUCH faster

 

6

Ktag firmware 7.026 have MCU for change

Ktag firmware 7.020 not reset CFG

 

7

Ktag 7.026 TOKENS 30 in 1 MCU

Ktag 7.020 UNLIMITED

 

8

This ktag has some nice features like toyota denso or VAG GPT edc17c74

 

9

some EU seller claims that he has version without tokens limit.

 

10

Ktag 7.026 Russian clone has fixed firmware with token count stopped.

I use kess and ktag. No any headache. No heating to unlock, no nxp changing.

11

For kess v2, As i know, for 5+ firmware, protocol files crypted individually for each original.

You can’t update different devices with same files.

Since Kess V2 4.036 a lot of protection added.

For ktag, i think, the same.

Take care before spend 2000+

 

In summary, there are good and bad reviews of ktag 7.026. Hint for you, do not rush into new versions. Time will tell you good or not. Before this, go for Ktag firmware 7.020.

 

See this

Ktag 7.020 test report:

Ktag 7.020 review: