Hi Ramesh, It is not a driver issue, but rather two pieces of software attempting to communicate with each other. It is difficult to say what is going on as the log files are just showing what we already know in that the Data Analysis client can't communicate to the main GUI application. This would be similar to pinging a server using an IP address and getting no response back. As I have not seen this issue before it is difficult to know where to start looking. The only time I have seen something similar is if I start the GUI before plugging in the EVM to USB and then attempt to run the Data Analysis. I would suggest always plugging in the EVM before starting the GUI application. This seems to be important for Win10. There could be some other piece of software installed that is blocking access to the socket by assigning or blocking a port for another purpose. If you open a cmd window and type in 'netstat' you will get a listing of all connections in use. The GUI uses port 11000, so after the GUI is started you would see something in netstat similar to: You should only see port 11000 when the GUI is started and not before. If you do, that could be the issue. When the Data Analysis properly finds the desired port a connection will be made for the application to communicate with the GUI and the netstat output will be similar to: The Data Analysis client needs to communicate to the main application at socket 11000 at the IP address shown. Best regards, Bob B
↧