On Windows 10 network traffic slowing down UI events

  Quick note (mostly to myself), when using a GigE camera make sure to enable software triggering.  I found out Labview's "IMAQdx Configure Grab" will stream images in the background even if the frames are not being used.  The network gets swamped with data, useless data, between the camera and the PC, at 1 billion bits per second.  Every time the camera has an image ready it sends it to the computer.  The computer swaps out the last image with the new one, but just keep it in memory.  It doesn't get displayed or even copied out of memory unless the "Grab image" is called.  To alleviate the bandwidth flood, set the camera trigger mode ON, and set the trigger source to Software Trigger.
This way the camera won't get an image until it is asked to get an image.  The IMAQdx property node is used to activate the software trigger.  The property node's "ActiveAttribute" must be set to "TriggerSoftware".  The property node's "ValueBool" is set to "True".  Follow this up with a "Grab" to get the image.  This way the network is only used when you want an image.

LabView Configure Grab and TriggerSoftware properrty node.  

  When the network card was flooded, Windows 10 was slow to respond to mouse clicks.  Some other HID functions, like key presses, would take over 20 seconds to be processed.  I guess that the network traffic had a higher event priority than the user interface events.  However, mouse movements always worked, clicks did not.  The problem vanished once the network traffic was squelched.