Failure to communicate (-1)

[kuebk]

Hi,

I have an issue with HEX-NET working over WiFi (in infrastructure mode).
The device is configured correctly, ping to the HEX-NET ip address works, the device test in VCDS passes but in the end about 95% of attemps to connect to any control unit ends with "failure to communicate (-1)" error message.

Can you suggest any solution?

Regards.

 

[Shaun]

What type of car? Does it work reliably via USB? What are the ping times that you're seeing?

 

[kuebk]

Right now it's A4 B9 2019.
Yes it works reliably via USB.

C:\Users\kuebz>ping 192.168.88.108

Pinging 192.168.88.108 with 32 bytes of data:
Reply from 192.168.88.108: bytes=32 time=1ms TTL=64
Reply from 192.168.88.108: bytes=32 time=2ms TTL=64
Reply from 192.168.88.108: bytes=32 time=2ms TTL=64
Reply from 192.168.88.108: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.88.108:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

 

[Santos]

What version of windows are you running? Make sure your wifi is set to private. Ive had similar problems and it was windows being set to public. Once i flipped to private, it would communicate.

 

[kuebk]

It's windows 10, and wifi is configured as private. Anyway it occasionally works, so it must be something else.

 

[Uwe]

Anyway it occasionally works, so it must be something else.

What type of router are you using? Check its settings for the 2.4 GHz network. Some of them will use multiple frequency bands to increase speeds on the 2.4 GHz band. For example I've seen Netgear routers that have an option to run 2.4 GHz at "Up to 54 Mbps", "Up to 145 Mbps" and "Up to 300 Mbps". IIRC, these correspond to 802.11 b, g, and n. The first two work fine. The last one causes intermittent problems similar to the ones you've described. So if possible, try restricting it no more than 802.11g speeds.

-Uwe-

 

[kuebk]

So yesterday it started after many attempts it started to work as it was supposed to. Today, same story again.
Nothing has changed when it comes to network configuration.

It's a bit weird, when I launch the VCDS and click select I'm getting correct list of modules which are installed in the car but failure to communicate when trying to connect to specific module.

If it help I can attach tcp traffic dump from wireshark.

 

[Shaun]

Is this an HN2 interface? If so try [Options] -> [Bypass DoIP]

 

[kuebk]

No difference with DoIP bypass enabled.

IP traffic dump with HEX-NET: hex-net-fail.pcapng

 

[Shaun]

That doesn't indicate any sort of network problem, I see no dropped packets. Are you certain this works reliably via USB and isn't some type of intermittent problem on both? What does your [About] screen show for license status?

 

[kuebk]

Indeed, there is nothing crazy in this dump. If you like I can catch more packets - maybe you will notice something.
License status: "Valid / Activated -- Unlimited VINs"

No issues when working via USB.

 

[Shaun]

If you want you can try making a debug log. In VCDS do [Options] -> debug level = 1024 [Save] then reproduce the error. In Ross-Tech\VCDS\debug folder find any logs that made and email them to Support@Ross-Tech.com. You can reference this thread.

 

[kuebk]

Done.

 

[Eric]

The first two sets of debugs you sent had ignition OFF and DoIP ON.
The third set you sent still had DoIP ON (but ignition ON, progress!). The third set appears to have communicated correctly with most controllers that were detected in the very short gateway installation list, with the exception of 01-Engine.
Would you like to try a 4th time, this time with ignition ON and DoIP OFF?
I see some amount of network packets concatenation, but not to the extent that it should impair VCDS. If you feel this is network related, you may want to try disabling some of your (diagnostic-wise) superfluous network adapters:

MAC0: xxx Intel(R) Ethernet Connection (3) I218-LM204747C1CBE7 Intel(R) Ethernet Connection (3) I218-LM    
MAC1: xxx VMware Virtual Ethernet Adapter for VMnet1005056C00001 VMware Virtual Ethernet Adapter for VMnet1    
MAC2: xxx VMware Virtual Ethernet Adapter for VMnet8005056C00008 VMware Virtual Ethernet Adapter for VMnet8    
MAC3: xxx Bluetooth Device (Personal Area Network) xxx Bluetooth Device (Personal Area Network)    
MAC4: xxx Intel(R) Dual Band Wireless-AC xxx Intel(R) Dual Band Wireless-AC 7265    
MAC5: xxx Microsoft Wi-Fi Direct Virtual Adapter xxx Microsoft Wi-Fi Direct Virtual Adapter    
MAC6: xxx Microsoft Wi-Fi Direct Virtual Adapter #xxx Microsoft Wi-Fi Direct Virtual Adapter #2    
MAC7: xxx Dell Wireless 5809e Gobi(TM) 4G LTE Mobile Broadband Card xxx Dell Wireless 5809e Gobi(TM) 4G LTE Mobile Broadband Card

as VCDS needs to send a broadcast on every network when you are auto-detecting the interface.
There may be more network adapters on your PC but I only coded VCDS for 8 broadcasts/network adapters. This might be an issue with your current setup.
And/or you could enter the interface's IP directly in Options: currently it's at 192.168.88.110 .

 

[kuebk]

Here's what I did:
- disabled DoIP - no change (deebug logs emailed)
- disabled 2 network interfaces with DoIP enabled - no change
- disabled 2 network interfaces with DoIP disabled - works
- fixed ip - works

Thanks.

 

[kuebk]

Is there any chance to get it working with auto-detect ip enabled?

 

[Uwe]

Is there any chance to get it working with auto-detect ip enabled?

How about reserving an IP for it in your router's DHCP server? Then it will always be assigned that IP on your network and youi can keep that IP set in VCDS.

-Uwe-

 

[kuebk]

I work from multiple places which use different WiFi networks, so that's not an option.

 

[kuebk]

Is there any chance for this issue to be resolved?

 

[Eric]

I've bumped the max number of adapters in the source code to 16, but I'm not 100% sure you still won't have issues with DoIP as well.