[ACK]

I have a 2018.03 Xentry XDOS and DAS installation on Windows 7 Pro 64-bit. I configured the LAN and wireless settings using SDconnect Administration Toolkit as per standard instructions. I set up the Road24h ad-hoc network. The SDconnect Administration Toolkit is able to see the C4 over a LAN connection or over WiFi. With or without the LAN cable connected between the Xentry laptop and C4, the SDconnect Toolkit is able to run diagnostics on the C4. With the LAN cable connected and the C4 connected to the vehicle, I can run diagnostics on the car. However, I just can't get Xentry Diagnostics or DAS to connect to the C4 over WiFi.

I read somewhere that you need to change Part T to Part W in cal.ini files in Xentry/bin and DAS/bin. I have done that and restarted my machine. But I still can't get Xentry Diagnostics or DAS to connect to the C4 mux over WiFi. Everything works fine if I use a LAN cable.

Any ideas what I should try next to get Xentry Diagnostics and DAS to work over WiFi? The C4 came with a NEC wireless pc card (NEC PA-WL/54AG or AtermWL54AG). I have a Netgear WG511T on order to rule out a bad wireless card.

[kiranabc]

Did you set up the right ip in the wlan Adapter?

After you have to select the SDConnect in the toolkit

best regards

[ACK]

Yes, I followed the standard SDconnect C4 network setup instructions. The toolkit can talk to the SDconnect C4 over WiFi with the green LAN cable removed. I can ping the C4 from the laptop running Xentry. But Xentry doesn't see the C4. I am using the ad-hoc network Road24h.

[kiranabc]

you check the ip in the wlan Adapter?

and put a fix ip in?

192 168 2 201?

best regards

[ACK]

you check the ip in the wlan Adapter?

and put a fix ip in?

192 168 2 201?

best regards

I have set up fixed IP's for the laptop and the SDconnect C4. They connect over an ad-hoc WiFi network. I will post screenshots from the toolkit later today.

I had to use a network other than 192.168.2.xxx. I use 192.168.2.xxx for my standard home network with all my laptops, storage arrays, smart devices, etc. I used 192.168.5.xxx instead for the Road24h ad-hoc network.

[kiranabc]

Forget there wilbe no Connection
just use the right ip

[ACK]

Forget there wilbe no Connection
just use the right ip

I have the SDconnect working on 192.168.5.xxx network. I can use any network in the private address range. The problem was not the IP address. Rather, it appears there were some extraneous network adapters that were causing issues. I followed instructions on the 28th post at to disable all unnecessary adapters. I cleaned up the registry according the 32nd post on the same thread. I set up the Road24h ad hoc network as described on the 2nd post on the above thread. And then I configured the MUX using SDconnect Administration Toolkit.

Xentry doesn't care what wireless IP address you use for the MUX. Xentry can talk to the MUX as long as you select the MUX using the TKtray icon.