Here are remedies of the following DAS error “Fault (1.2)-2.503.9901” using SD connect C4 multiplexer on Windows 7, the error started with version 2017.07 but figured upgrading to XDOS 2018.09 would have solved the issue but still occurring.
Multiplexer: SD connect C4
Operation system: Windows 7
Software: DAS
Version: DAS version 2018.07 upgrading to version 2018.09
The error: Fault (1.2)-2.503.9901
Initialization of diagnosis multiplexer failed.
Possible causes.
The link between the diagnosis multiplexer and the diagnosis socket is interrupted.
The link between the diagnosis multiplexer and the diagnosis unit is interrupted.
The voltage supply at the diagnosis socket (circuit 30 and (or) circuit 31) is faulty.
Note:
When using SDconnect check the connection status using the Toolkit.
The fault (1.2)-2.503.9901 usually happens because of:
The link between the diagnosis multiplexer and the diagnosis unit is interrupted.
Remedy:
1. use a good lan cable
2. set lan tcp/ip to:
ip address: 172.29.127.119
Subnet mask: 255.255.0.0
Wirless_IP_set to C4
Lan_IP_set to C4
you will see the status of connection happening in sdconnect toolkit in right bottom corner.
SOLUTION:
Solved by changing SDConnect from 21 to 04
Reference: XDOS SDconnect Configuration
To save an ad-hoc network and its network key on the guest computer (running Windows 7)
Note down the SSID, security type, encryption type and the key of the ad-hoc network. Disconnect your connection to any wireless network and switch off/disable your wireless device. Turn on/enable your wireless device but don’t connect to any network. (Thanks GK.)
Click on the network icon in the taskbar.
Click Open Network and Sharing Center > Manage Wireless Networks > Add.
Click “Manually create a network profile”. (This may look silly but we really are going to create an infrastructure network now.)
Enter the network name (SSID), security type, encryption type (if any) and the key that you noted in step 1.
Uncheck both checkboxes (“Start this connection automatically” and “Connect even if the network is not broadcasting”.)
[Note that you cannot have the connection start automatically. If you try to have it checked, step 10 will fail. A different way to start it automatically during system boot is described below.]
Click Next > Close. Your connection must appear in the list with the icon suggesting infrastructure (two big screens connected to a tube). Don’t worry about it.
Click Start, type in “cmd” in the search box, press Enter.
In the Command Prompt, type in “netsh wlan set profileparameter name=NetworkName ConnectionType=IBSS”, exactly as shown, without quotes, except you must substitute NetworkName with the SSID (network name) of your ad-hoc network.
If everything went well, you’ll see that the icon has now changed to an ad-hoc icon (three small screens connected to each other) in the Manage Wireless Networks window.
Turn on/enable your wireless device, and try connecting to the Ad-hoc network. You will notice that you no longer need to enter the network key.
To automatically connect to a saved ad-hoc network during Windows boot (can be applied to both guest and host computers running Windows 7)
Click Start > point to All Programs > right-click Startup > click Open. (You may choose Open All Users instead if you prefer).
Right-click an empty space and click New > Shortcut.
Type in “netsh wlan connect NetworkName”. Once again, NetworkName must be substituted with the SSID of your ad-hoc network.
Click Next and enter a fancy name such as “Connect to NetworkName” or something like that.
Click Finish and you’re done.
This shortcut will run when Windows starts up, giving you a very brief flash of the black command window, followed by your computer connecting to the ad-hoc network if it is available.
Tip: You can also pin the shortcut in your taskbar or copy it to the desktop to easily connect to the network any time you want. Note: You will probably need Administrator access to complete some of the steps above (in both procedures).
By Sarrukin
