LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Ethernet/ip slow response on new PC

Hi folks,

I created a VI which uses the Ethernet/ip driver to control some variable frequency drive motors in the lab. The executable runs fine on the laptop where the program was devleoped, but the motor start/stop response has a long, inconsistent delay when run on a new Dell 7040 desktop. I thought the issue was the Windows 10 OS but I ran the program on a seperate laptop running Windows 10 and everything works fine, motors start/stop like they should. Anyone out there exeperienced a similar issue?

 

Jason

 

0 Kudos
Message 1 of 4
(3,694 Views)

Hi Jason,

 

That's a bit odd. How are the various computers connected to the frequency drive motors? Particularly, is there a difference in the network path from the laptop to the desktop? (If you take the Ethernet cable from the desktop and plug it into either of the laptops, do they still work the same way, or do they start exhibiting the delays?) Another thing worth checking into is to see what the difference between the network chipsets are. The desktop network driver might have some sort of network shaping software or a different Firewall/AV setup that is interfering with the Ethernet/IP driver. Those are the first things that occur to me.

William R.
0 Kudos
Message 2 of 4
(3,634 Views)

Thanks William.

 

After my first post I did find an updated Realtek driver for the board. The new driver did improve the situation but did not completely fix the problem.

 

Now the motors start/stop as they should with no delay but will not run continuously. The best way I can describe the current issue is the motors run in a "strobe" mode. Basically a continuous run/pause/run/pause mode. Since the updated driver did change my original problem, I believe the issue lies in the PC hardware/driver configuration and not related to my VI or the Ethernet driver.

 

If I'm able to solve the issue I'll update this post in case others run into a similar problem.

0 Kudos
Message 3 of 4
(3,621 Views)

If anyone is interested, this driver from Dell became available yesterday and solved the issue.

 

Chipset_Driver_78C1C_WN32_11.0.0.1158_A00.EXE

 

 

Message 4 of 4
(3,607 Views)